TPMS Performance and Tuning Worl(sliop Dave Leeic Dave Hamilton VTPTUNEV2.0 TPMS Performance and Tuning Contents 0.1 ICL endeavours toensure that theinformation in this document iscorrect but doesnot accept liability for any errors or omissions. f Thedevelopment of ICL products iscontinuous and published information may notbe c^umentup-to-date.Anyor mayparticularcontain facilitiesissue of anot productmaycontaindescribed here. It Is partimportant onlyoftheto checkf^ilitiesthe describedcurrent position in thiswith Statementsinthisdocument are notpartofa contract or a program product licence save in so f^ as they are incorporated intoa documentor licence byexpress reference, issue ofthis document does notentitle the recipient to access to or use ofthe products describedand such access or use may be subject to separate contracts or licences. This document was produced by :- SystemSupportCentre SystemSupportCentre. Internation^ Computers Limited International Computers Limited. Manchester. Bracknell. Copyright - International Computers Limited 1990. Contents 0.2 TPMSPerfbtmance andTuning VTPTUNE V2.0 Contents 1 Workshop introduction 1.1. Agenda. 1.3 1.2. Objectives. 1.5 1.2.1. Pre-requisites. 1.5 1.3. Woricshop manual. 1.7 1.4. Introduction to Tuning and Performance. 1.9 2 Design Practices 2.1. General areasfor consideration. 2.3 2.1.1. Main store. 2.3 2.1.2. OCP or millusage. 2.3 2.1.3. Disc transfers. 2.3 2.1.4. Datatransmission. 2.3 2.1.5. Standards of compatibility. 2.3 2.1.6. Diagnostics. 2.3 2.2. IDMS. 2.5 2.3. Conventionalfiles. 2.7 2.4. CAPS. 2.9 2.5. COBOL Programming. 2.11 2.6. Application Master programming. 2.13 2.7. INGRES and SQL 2.15 2.8. Order of Importance. 2.17 3 AVIM Resources and Response Times 3.1. Objectives. 3.3 3.2. The Information Needed. 3.5 3.2.1. Throughput. 3.5 3.2.2. Store Requirements. 3.5 3.2.2.1. Virtual Store. 3.5 3.2.2.2. Mainstore. 3.5 3.2.2.3. Locked Store. 3.7 3.2.2.4. RIRO. 3.9 3.2.2.5. Job Store Quota. 3.9 3.2.2.6. Working Set 3.9 J^.2.2.7. Polk:y Shared Quota. 3.9 3.2.3. DataAccessing. 3.11 3.3. Estimating Servicetimes and Response times. 3.13 3.3.1. AVM Sen^Time. 3.13 3.3.2. Estimating queuing times. 3.13 3.3.3. TP Response time. 3.17 3.3.4. Temfiinal Response time. 3.17 4 Performance Monitoring Tools 4.1. Introduction 4.3 4.1.1. When to monitor 4.3 C4.1.2. What can be monitored? 4.3 4.2. TPMS Periodic Statistics. 4.5 4.2.1. Generating the statistics 4.5 4.2.2. Outputting the statistics. 4.5 4.2.3. interpreting the statistics 4.7 4.2.3.1. ^hedulerstatistics: 4.7 4.2.3.1.1 Scheduler VM statistics 4.7 4.2.3.1.2 Message type statistKs 4.7 4.2.3.1.3 AVMTYPE statistics 4.9 4.2.3.2. ResponderStatistics 4.9 4.2.3.2.1 ResponderVM statistics 4.9 4.2.3.2.2 MessageType Statistics 4.9 4.2.3.2.3 Temninai Statistics 4.9 4.2.3.2.4 Screen Format Key Statistics 4.9 :VTPTUNEV2.0 TPMS Performance and Tuning Contents 0.3 4.2.3.2.5 Badge Statistics 4.9 4.2.4. Displays from control mode. 4.13 4.3. TPMS Statistics Paclcage 4.15 -4.3.1. Availability 4.15 4.3.2. What it provides 4.15 4.3.3. Collecting the statistics 4.15 4.3.4. Using the statistics 4.15 4.4. IDMS Statistics 4.19 4.4.1. Runtime statistics. 4.19 4.4.2. Trace statistics. 4.19 4.4.3. Utilisation statistics. 4.19 4.5. RIe Meters 4.23 4.6. UST USAGE 4.25 4.6.1. GIVE USAGE (GUS) 4.25 4.7. SYSTEM MONITOR 4.27 4.8. COBOL PATH ANALYSIS (COBRA) 4.29 4.9. PROGRAM_ACTlVmr_SAMPLER (PAS) 4.31 4.10. VME Capacity Management System (VCMS) 4.35 4.11. Suggested set of statistics 4.37 5 Service Management 5.1. Introduction 5.3 ( 5.1.1. The areas to consider are 5.3 5.2. DDS Prepares. 5.5 5.2.1. TPMS PREPARE PACKAGED SERVICE(TPMSPPS). 5.5 5.2.2. PREPARETP^ERVICE. 5.5 5.2.3. PREPARE APPLICATION. 5.7 5.3. Making the TP VMs available on service start 5.9 5.3.1. Checkpointing. 5.9 5.3.2. A BetterAlternative for Series 39 sites. 5.11 5.3.3. COBOL run-time code. 5.13 5.3.4. Load the code more quickly. 5.13 5.3.5. Load less code. 5.13 5.3.6. Parameterfile settings. 5.13 5.3.6.1. SQUOTA 5.13 5.3.6.2. MAXPRI&MINPRI 5.13 5.3.6.3. AViy^lME. 5.15 5.3.6.4. AVMMIN. 5.15 5.3.7. Balance the disc traffk: 5.15 5.3.8. Otherconsiderations. 5.17 5.4. Connectingthe network. 5.19 5.4.1. Connection to TP. 5.19 5.4.2. NTCR and SCT performance. 5.19 5.5. Cataloguecontention. 5.21 5.6. TPMS journal management 5.23 5.6.1. TPMS Cyclk;journal. 5.23 5.6.2. TPMS journal library management 5.23 5.6.3. Create the foltowing hooks for your TPMS servk:e. 5.25 5.6.4. For TPMS servk:es defined by a parameterfile 5.25 5.6.5. Forservk:es defined in a Data Dk:tionary 5.25 6 Tuning 6.1. Introduction to Tuning. 6.3 6.2. Areasfor Consideration. 6.5 6.3. Disctransfer priorities. 6.7 6.4. CVM. 6.9 6.4.1. Servk» time. 6.9 6.4.2. VSI's. 6.9 6.4.3. OCP contention. 6.15 6.4.4. Input-Outputs. 6.15 6.4.5. User hooks. 6.15 6.4.6. Number ofservices. 6.15 Contents 0.4 TPMSPerlbtmance andTuning VTPTUNEV2.0 0^ 6.4.7. Queue time. 6.15 6.5. AVM. 6.17 6.5.1. Service time. 6.17 6.5.2. VSIs. 6.17 6.5.3. OOP contention 6.27 6.5.4. Suspensions. 6.27 6.5.5. lOs 6.27 6.5.6. Timeouts. 6.27 6.5.7. Queue time 6.29 6.5.8. AVMTYPEs and AVM copies. 6.29 6.5.8.1. Mapping message tyjses toAVMTYPES. 6.29 6.5.8.2. Single application AVMTYPES. 6.31 6.5.8.3. Offload AVM. 6.33 6.5.8.4. Rolling AVMs. 6.33 6.5.9. Message slots. 6.35 6.6. RLESTORE TRANSFERS. 6.37 6.6.1. Serial files. 6.37 6.6.2. Indexed Sequential files. 6.37 6.6.2.1. Structure of IS files. 6.37 6.6.2.2. Buffers. 6.39 6.6.2.3. Overflow. 6.41 6.6.2.4. Overflow at end of file 6.43 6.6.2.5. Locking. 6.43 6.6.2.6. Multiblock transfers. 6.45 6.6.3. Hashed Random files. 6.45 6.6.4. IDMS. 6.47 6.6.4.1. Buffers. 6.47 6.6.4.2. Overflow. 6.47 6.6.4.3. Journals. 6.49 6.6.4.4. Locking. 6.49 6.6.5. Contention. 6.49 6.7. Communications. 6.51 6.7.1. VME Buffers. 6.51 6.7.2. Line utilisation. 6.51 6.8. Summary. 6.53 6.8.1. Twofurther things about store. 6.53 6.8.2. TP Parameter RIe Values 6.55 6.8.2.1. CTRLDAT 6.55 6.8.2.2. AVMTYPE 6.57 6.8.2.3. MT 6.57 6.8.3. LikelyCauses Of Problems. 6.59! 6.8.3.1. CVM 6.59 6.8.3.2. AVM 6.59 6.8.3.3. RIe 6.59 A Appendices A.1 A.1. Bibiiograpliy A.3 A.2. Queuingtimesfor muftiserver queues. A.5 A.3. Probability of exceeding queue sizes. A.7 VTPTUNE V2.0 TPMS Performanceand Tuning Contents 0.5 1. Workshop Introduction VTPTUNE V1.2 TPMS Performance and Tuning Page 1.1 o V-i n Pago1,2 TPMS Perfbmiance andTuning VTPTUNE VI .2 I.IJVgenda. 10.00 Coffee And Introduction. 10.10 Introduction ToTuning. 10.20 Design Practices. 11.05 Coffee 11.20 AVM resources and response times. 12.05 Perfbmnance Monitoring Tools. 13.00 Lunch 13;45 Service Management 14:30 Tuning. 15.30 Coffee. 15.45 Tuning Continued. 17.00 Close. VTPTUNEV1.2 TPMS Perfonnanoe and Tuning Page 1.3 Workshop Objectives After attending the workshop the attendee should be able to »>SIz*aTPIISMrvlc« ^-Monitor tha parfonnanca of a TPMS aarvica »>liivaatlgata tha cauaaa of parfonnanca problama »>Tuna a TPMS aarvica VTPT0030 Page 1.4 TPMSPerfbrmanceand Tuning VTPTUNEV1.2 1.2.0bjectives. The objectives of this workshop are to enable an attendee to:- — Size a TPMS servKe. — Monitorthe performance of a TPMS servk». — Investigate thecauses ofperformance problems. — Tune a TPMS servk». 1.2.1 .Pre-requisites. Abackground in maintaining and supporting TPMS servk»s. Attendance of the VITPF course with some practical experience is the best background. Some design or programming experience would be useful but is not essential. VTPTUNE VI .2 TPMS Performance and Turvng Page 1.5 r~) Page 16 IPMSPertbnnanceandTunino VIPTUNEVI^ 1.3.Workshop manual. This document isthe manual produced as part of the TPMS Performance and Tuning workshop.