EPILOG for VM Product Manual, V610publib.boulder.ibm.com/tividd/td/ITOfV/GC32-9237... · Product Manual EPILOG™ for VM Version 610 for VM and z/VM GC32-9237-00 January 2004 Candle

Product ManualEPILOG™ for VM

Version 610 for VM and z/VM

GC32-9237-00

January 2004

Candle Corporation100 North Sepulveda Blvd.

El Segundo, California 90245

2 EPILOG for VM Product Manual, Version 610

Registered trademarks and service marks of Candle Corporation: AF/OPERATOR, AF/REMOTE, Availability Command Center, Candle, Candle CIRCUIT, Candle Command Center, Candle Direct logo, Candle Electronic Customer Support, Candle logo, Candle Management Server, Candle Management Workstation, CandleLight, CandleNet, CandleNet Command Center, CandleNet eBusiness Platform, CandleNet Portal, CL/CONFERENCE, CL/SUPERSESSION, CommandWatch, CT, CT/Data Server, CT/DS, DELTAMON, DEXAN, eBA, eBA*ServiceMonitor, eBA*ServiceNetwork, eBusiness at the speed of light, eBusiness Assurance, eBusiness Institute, ELX, EPILOG, ESRA, ETEWatch, IntelliWatch, IntelliWatch Pinnacle, MQSecure, MQView, OMEGACENTER, OMEGAMON, OMEGAMON II, OMEGAMON Monitoring Agent, OMEGAMON Monitoring Agents, OMEGAVIEW, OMEGAVIEW II, PQEdit, Response Time Network, Roma, SitePulse, Solutions for Networked Applications, Solutions for Networked Businesses, TMA2000, Transplex, and Volcano.Trademarks and service marks of Candle Corporation: AF/Advanced Notification, AF/PERFORMER, Alert Adapter, Alert Adapter Plus, Alert Emitter, AMS, Amsys, AutoBridge, AUTOMATED FACILITIES, Availability Management Systems, Business Services Composer, Candle Alert, Candle Business Partner Logo, Candle Command Center/SentinelManager, Candle CommandPro, Candle eDelivery, Candle eSupport, Candle Insight, Candle InterFlow, Candle Managing what matters most, Candle Service Suite, Candle Technologies, CandleNet, CandleNet 2000, CandleNet Conversion, CandleNet eBP, CandleNet eBP Access for S.W.I.F.T., CandleNet eBP Administrator, CandleNet eBP Broker Access for Mercator or MQSI, CandleNet eBP Configuration, CandleNet eBP Connector, CandleNet eBP File Transfer, CandleNet eBP Host Connect, CandleNet eBP Object Access, CandleNet eBP Object Browser, CandleNet eBP Secure Access, CandleNet eBP Service Directory, CandleNet eBP Universal Connector, CandleNet eBP Workflow Access, CandleNet eBusiness Assurance, CandleNet eBusiness Exchange, CandleNet eBusiness Platform Administrator, CandleNet eBusiness Platform Connector, CandleNet eBusiness Platform Connectors, CandleNet eBusiness Platform Powered by Roma Technology, CandleNet eBusiness Platform Service Directory, Candle Vision, CCC, CCP, CCR2, CEBA, CECS, CICAT, CL/ENGINE, CL/GATEWAY, CL/TECHNOLOGY, CMS, CMW, Command & Control, Connect-Notes, Connect-Two, CSA ANALYZER, CT/ALS, CT/Application Logic Services, CT/DCS, CT/Distributed Computing Services, CT/Engine, CT/Implementation Services, CT/IX, CT/Workbench, CT/Workstation Server, CT/WS, !DB Logo, !DB/DASD, !DB/EXPLAIN, !DB/MIGRATOR, !DB/QUICKCHANGE, !DB/QUICKCOMPARE, !DB/SMU, !DB/Tools, !DB/WORKBENCH, Design Network, e2e, eBA*SE, eBAA, eBAAuditor, eBAN, eBANetwork, eBAAPractice, eBP, eBusiness Assurance Network, eBusiness at the speed of light, eBusiness at the speed of light logo, eBusiness Exchange, eBX, End-to-End, eNotification, ENTERPRISE, Enterprise Candle Command Center, Enterprise Candle Management Workstation, Enterprise Reporter Plus, ER+, ERPNet, ETEWatch Customizer, HostBridge, InterFlow, Candle InterFlow, Lava Console, Managing what matters most, MessageMate, Messaging Mastered, Millennium Management Blueprint, MMNA, MQADMIN, MQEdit, MQEXPERT, MQMON, NBX, NC4, NetGlue, NetGlue Extra, NetMirror, NetScheduler, New Times, New Team, New Readiness, OMA, OMC Gateway, OMC Status Manager, OMEGACENTER Bridge, OMEGACENTER Gateway, OMEGACENTER Status Manager, OMEGAMON/e, OMEGAMON Management Center, OSM, PathWAI, PC COMPANION, Performance Pac, Powered by Roma Technology, PowerQ, PQConfiguration, PQScope, Roma Application Manager, Roma Broker, Roma BSP, Roma Connector, Roma Developer, Roma FS/A, Roma FS/Access, RomaNet, Roma Network, Roma Object Access, Roma Secure, Roma WF/Access, Roma Workflow Access, RTA, RTN, SentinelManager, Somerset, Somerset Systems, Status Monitor, The Millennium Alliance, The Millennium Alliance logo, The Millennium Management Network Alliance, Tracer, Unified Directory Services, WayPoint, and ZCopy.Trademarks and registered trademarks of other companies: AIX, DB2, MQSeries and WebSphere are registered trademarks of International Business Machines Corporation. Citrix, WinFrame, and ICA are registered trademarks of Citrix Systems, Inc. Multi-Win and MetaFrame are trademarks of Citrix Systems, Inc. SAP is a registered trademark and R/3 is a trademark of SAP AG. UNIX is a registered trademark in the U.S. and other countries, licensed exclusively through X/Open Company Ltd. HP-UX is a trademark of Hewlett-Packard Company. SunOS is a trademark of Sun Microsystems, Inc. All other company and product names used herein may be trademarks or registered trademarks of their respective owners.

Copyright © January 2004, Candle Corporation, a California corporation. All rights reserved. International rights secured.

Threaded Environment for AS/400, Patent No. 5,504,898; Data Server with Data Probes Employing Predicate Tests in Rule Statements (Event Driven Sampling), Patent No. 5,615,359; MVS/ESA Message Transport System Using the XCF Coupling Facility, Patent No. 5,754,856; Intelligent Remote Agent for Computer Performance Monitoring, Patent No. 5,781,703; Data Server with Event Driven Sampling, Patent No. 5,809,238; Threaded Environment for Computer Systems Without Native Threading Support, Patent No. 5,835,763; Object Procedure Messaging Facility, Patent No. 5,848,234; End-to-End Response Time Measurement for Computer Programs, Patent No. 5,991,705; Communications on a Network, Patent Pending; Improved Message Queuing Based Network Computing Architecture, Patent Pending; User Interface for System Management Applications, Patent Pending.

NOTICE: This documentation is provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions set forth in the applicable license agreement and/or the applicable government rights clause.This documentation contains confidential, proprietary information of Candle Corporation that is licensed for your internal use only. Any unauthorized use, duplication, or disclosure is unlawful.

Contents 3

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Candle Customer Service and Satisfaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

What’s New in Version 610. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 1. System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21EPILOG for VM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Chapter 2. Solving Data Center Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Solving CPU Utilization Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Solving Workload Transaction Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Solving Paging and Storage Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Solving I/O Balancing Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40Solving Spooling Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Chapter 3. Producing Batch Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47EVREPT EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Reporter Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Chapter 4. Interpreting the Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Preliminary Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73Group Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77Resource Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Workload Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125User Request Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140Collector Keywords Needed for Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142

Chapter 5. Producing Graphs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Generating Character Graphs from within EPILOG. . . . . . . . . . . . . . . . . . . . . . . . . . .145Generating Graphs with GDDM/ICU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152Generating Graphs On a PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164Extracting Data with EVOBT EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170

Chapter 6. Maintaining the Datastore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Datastore Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182

Contents


The EVACCUM EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183The EVTDUMP EXEC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187The EVTLOAD EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191Creating an Automated Maintenance Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193

Appendix A. Applying Maintenance ZAPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195ZAP Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196Listing Applied Maintenance ZAPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197Applying Maintenance to the Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198Applying Maintenance to EPILOG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199

Appendix B. Data Dictionary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Data Dictionary Column Headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203Report Printing Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

List of Tables 5

Table 1. Symbols in Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Table 2. VM Systems Supported by OMEGAMON and EPILOG for VM Version 610 . . . . . . . . .17Table 3. Listing of Reporter Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Table 4. Sample Command Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50Table 5. Report Name Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Table 6. GRPD - Group Definition Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78Table 7. RBOT - Resource Bottleneck Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81Table 8. RCHP - Resource Channel Path Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82Table 9. RCPU - Resource CPU Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

Table 10. RDAS - Resource DASD Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86Table 11. REXP - Resource Expanded Storage Migration Report . . . . . . . . . . . . . . . . . . . . . . . . .88Table 12. RFRE - Resource Free Storage Activity Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90Table 13. RHLS - Resource High-Level Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92Table 14. RICO - Resource IUCV/VMCF Communications Activity Report . . . . . . . . . . . . . . . . . .97Table 15. RLPR - Resource LPAR Utilization Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100Table 16. RNSS - Resource Saved Segment/NSS Activity Report . . . . . . . . . . . . . . . . . . . . . . . .102Table 17. RPAG - Resource Paging Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105Table 18. RSCH - Resource Scheduler Storage Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107Table 19. RSEE - Resource Seek Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109Table 20. RSPO - Resource SPOOLing Activity Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111Table 21. RSTR - Resource Storage Management Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113Table 22. RSYS - Resource System Information Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115Table 23. RTDI - Resource Temporary Disk Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . .120Table 24. RTRA - Resource Transaction Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122Table 25. RVDS - Resource VDISK Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123Table 26. WBOT - Workload Bottleneck Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126Table 27. WCPU - Workload CPU Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129Table 28. WICO - Workload IUCV/VMCF Communications Activity Report . . . . . . . . . . . . . . . .131Table 29. WSTO - Workload Paging/Storage Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134Table 30. WSUM - Workload Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136Table 31. WTRA - Workload Transaction Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138Table 32. User Request Log Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141Table 33. Collector Keyword Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142Table 34. Sample OBTAIN Command Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171Table 35. Report Printing Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205Table 36. GRPD - Group Definition Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206Table 37. RBOT - Resource Bottleneck Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207Table 38. RCHP - Resource Channel Path Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209Table 39. RCPU - Resource CPU Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210Table 40. RDAS - Resource DASD Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212

List of Tables


Table 41. REXP - Resource Expanded Storage Migration Report . . . . . . . . . . . . . . . . . . . . . . . .213Table 42. RFRE - Resource Free Storage Activity Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214Table 43. RHLS - Resource High-Level Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215Table 44. RICO - Resource IUCV/VMCF Communications Activity Report . . . . . . . . . . . . . . . . .219Table 45. RLPR - Resource LPAR Utilization Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221Table 46. RNSS - Resource Saved Segment/NSS Activity Report . . . . . . . . . . . . . . . . . . . . . . . .223Table 47. RPAG - Resource Paging Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225Table 48. RSCH - Resource Scheduler Storage Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226Table 49. RSEE - Resource Seek Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228Table 50. RSPO - Resource SPOOLing Activity Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230Table 51. RSTR - Resource Storage Management Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231Table 52. RSYS - Resource System Information Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233Table 53. RTDI - Resource Temporary Disk Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . .237Table 54. RTRA - Resource Transaction Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238Table 55. RVDS - Resource VDISK Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239Table 56. WBOT - Workload Bottleneck Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240Table 57. WCPU - Workload CPU Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242Table 58. WICO - Workload IUCV/VMCF Communications Activity Report . . . . . . . . . . . . . . . .243Table 59. WSTO - Workload Paging/Storage Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244Table 60. WSUM - Workload Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245Table 61. WTRA - Workload Transaction Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246

List of Figures 7

FIGURE 1. EPILOG for VM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22FIGURE 2. The Transaction Activity Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26FIGURE 3. The Bottleneck Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27FIGURE 4. The CPU Activity Trend Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28FIGURE 5. The CPU Activity Report Highlighting T/V Ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29FIGURE 6. The Transaction Activity Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30FIGURE 7. The Workload Transaction Activity Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31FIGURE 8. The Workload Bottleneck Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32FIGURE 9. The Seek Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

FIGURE 10. The Workload IUCV/VMCF Communications Report . . . . . . . . . . . . . . . . . . . . . . . . . .33FIGURE 11. The High-Level Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35FIGURE 12. The Paging Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36FIGURE 13. The Storage Management Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36FIGURE 14. DASD Activity Report Example Showing High External Pages . . . . . . . . . . . . . . . . . . .37FIGURE 15. The Workload Paging/Storage Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38FIGURE 16. The Workload Transaction Activity Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40FIGURE 17. The Workload Bottleneck Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41FIGURE 18. The Seek Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42FIGURE 19. The High-Level Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43FIGURE 20. The Paging Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44FIGURE 21. The SPOOLing Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44FIGURE 22. The DASD Activity Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45FIGURE 23. REPORT and SET Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53FIGURE 24. Typical RDASD Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64FIGURE 25. RDAS Report Using DATEFORM and COMBINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65FIGURE 26. Workload Summary Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66FIGURE 27. Sample Separator Page Produced by the PAGESEP Command . . . . . . . . . . . . . . . . . .68FIGURE 28. PRODUCTS Command Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69FIGURE 29. Typical Copyright Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73FIGURE 30. Page 0 Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74FIGURE 31. Generic Report Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75FIGURE 32. Sample Group Definition Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77FIGURE 33. Sample Bottleneck Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80FIGURE 34. Sample Channel Path Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82FIGURE 35. Sample CPU Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83FIGURE 36. Sample DASD Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86FIGURE 37. Sample Expanded Storage Migration Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88FIGURE 38. Sample Free Storage Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90FIGURE 39. Sample High-Level Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92FIGURE 40. Sample IUCV/VMCF Communications Activity Report . . . . . . . . . . . . . . . . . . . . . . . . .97

List of Figures


FIGURE 41. Sample LPAR Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100FIGURE 42. Sample Named Saved Systems Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102FIGURE 43. Sample Paging Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104FIGURE 44. Sample Scheduler Storage Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106FIGURE 45. Sample Seek Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109FIGURE 46. Sample SPOOLing Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111FIGURE 47. Sample Storage Management Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113FIGURE 48. Sample System Information Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115FIGURE 49. Sample Temporary Disk Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119FIGURE 50. Sample Transaction Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121FIGURE 51. Sample VDISK Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123FIGURE 52. Sample Workload Bottleneck Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125FIGURE 53. Sample Workload CPU Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129FIGURE 54. Sample Workload IUCV/VMCF Communications Activity Report . . . . . . . . . . . . . . . .131FIGURE 55. Sample Workload Paging/Storage Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133FIGURE 56. Sample Workload Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136FIGURE 57. Sample Workload Transaction Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138FIGURE 58. User Request Log Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140FIGURE 59. Typical User Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141FIGURE 60. Generic Graph Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146FIGURE 61. Page 1 of Typical Line Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148FIGURE 62. Page 2 of Typical Line Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149FIGURE 63. Page 1 of Typical Bar Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150FIGURE 64. Page 2 of Typical Bar Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151FIGURE 65. Sample GraphTracking CPUBUSY, CPBUSY, and VIRTBUSY . . . . . . . . . . . . . . . . . .153FIGURE 66. Sample Chart Tracking ACTUSER, AVGUSER, and MAXUSER . . . . . . . . . . . . . . . . .154FIGURE 67. Sample Graph Tracking PCTBUSY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155FIGURE 68. Sample Graph Tracking RAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156FIGURE 69. Sample Graph Tracking Two Elements Against Each Other . . . . . . . . . . . . . . . . . . . . .157FIGURE 70. Sample Graph Tracking DASDBUSY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158FIGURE 71. Sample Graph Tracking DEVADDR and DASDIOREQ . . . . . . . . . . . . . . . . . . . . . . . .159FIGURE 72. Sample Pie Chart Depicting the Percent of Users Found . . . . . . . . . . . . . . . . . . . . . . .160FIGURE 73. Sample Bar Graph Depicting the Percent of Users Found . . . . . . . . . . . . . . . . . . . . . .161FIGURE 74. Sample OBTAIN Command File for PC Processing . . . . . . . . . . . . . . . . . . . . . . . . . . .164FIGURE 75. Sample Graph Tracking CPBUSY and VIRTBUSY . . . . . . . . . . . . . . . . . . . . . . . . . . .166FIGURE 76. Sample Graph Depicting Average Users and Active Users . . . . . . . . . . . . . . . . . . . . . .167FIGURE 77. Sample Graph Tracking DASD I/O, Paging I/O, and Swapping I/O . . . . . . . . . . . . . . .168FIGURE 78. Sample Graph of DASD, Paging, and Swapping of Service Time . . . . . . . . . . . . . . . .169FIGURE 79. OBTAIN Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171FIGURE 80. Output File for OBTAIN Using FORMAT(INT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177FIGURE 81. Output File for OBTAIN Using FORMAT(COL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178FIGURE 82. Output File for OBTAIN Using FORMAT(PC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179FIGURE 83. Using the Set Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180FIGURE 84. EVACCUM Input and Output Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186FIGURE 85. Execution of EVTDUMP EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190

List of Figures 9

FIGURE 86. Execution of EVTLOAD EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192FIGURE 87. ZAP Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196FIGURE 88. Typical Output of the EPILOG ZAP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197FIGURE 89. Typical Output of the Collector’s QUERY ZAPS Command . . . . . . . . . . . . . . . . . . . . .197FIGURE 90. Applying a ZAP to the Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198FIGURE 91. Applying a ZAP to Epilog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199


Preface 11

Preface

About This BookThis manual contains a detailed description of EPILOG® for VM. For information on installing EPILOG and customizing the Collector, refer to the OMEGAMON and EPILOG for VM Installation and Customization Guide.

Below is a description of the chapter contents of this manual:

Documentation SetThe documentation listed below is available for OMEGAMON and EPILOG for VM. Each manual in this documentation set contains a specific type of information to help you use the product.

Candle welcomes your comments and suggestions for changes or additions to the manual set. Please send a copy of the page or pages in question, marked with your comments, to the Information Development department at the address shown on the title page of this manual or use the comment form at the back of this book.

® OMEGAMON for VM User’s Guide

® OMEGAMON for VM Reference Manual

® OMEGAMON and EPILOG for VM Command Summary

® EPILOG for VM Product Manual

® OMEGAMON and EPILOG for VM Installation and Customization Guide

Chapter 1 Overview of EPILOG components.

Chapter 2 How to use EPILOG to solve data center problems.

Chapter 3 Detailed reference on Reporter commands and keywords.

Chapter 4 How to interpret the reports.

Chapter 5 How to generate graphic output.

Chapter 6 How to maintain the datastore.

Appendix A How to apply maintenance ZAPs.

Appendix B Data Dictionary.

P


Note: Refer to the OMEGAVIEW customization information regarding connecting to OMEGAMON, if you are planning to install OMEGAMON for VM with OMEGAVIEW.

EPILOG and OMEGAMON for VM are compatible with all levels of OMEGAVIEW.

Where to look for more informationFor more information related to Candle products, please see the

® technical documentation CD-ROM that came with your product

® technical documentation information available on the Candle web site at www.candle.com

® online help provided with your product

We would like to hear from youCandle welcomes your comments and suggestions for changes or additions to the documentation set. A user comment form, located at the back of each manual, provides simple instructions for communicating with the Candle Information Development department.

You can also send email to [email protected]. Please include EPILOG for VM Product Manual, Version 610 in the subject line.

https://www.candle.com/www1/techdocs/red.html

Preface 13

Adobe Portable Document Format

Adobe Portable Document Format

Printing this bookCandle supplies documentation in the Adobe Portable Document Format (PDF). The Adobe Acrobat Reader will print PDF documents with the fonts, formatting, and graphics in the original document. To print a Candle document, do the following:

1. Specify the print options for your system. From the Acrobat Reader Menu bar, select File > Page Setup… and make your selections. A setting of 300 dpi is highly recommended as is duplex printing if your printer supports this option.

2. To start printing, select File > Print... on the Acrobat Reader Menu bar.

3. On the Print pop-up, select one of the Print Range options for® All® Current page® Pages from: [ ] to: [ ]

4. (Optional). Select the Shrink to Fit option if you need to fit oversize pages to the paper size currently loaded on your printer.

Printing problems?The print quality of your output is ultimately determined by your printer. Sometimes printing problems can occur. If you experience printing problems, potential areas to check are:® settings for your printer and printer driver. (The dpi settings for both your driver and

printer should be the same. A setting of 300 dpi is recommended.)® the printer driver you are using. (You may need a different printer driver or the Universal

Printer driver from Adobe. This free printer driver is available at www.adobe.com.)® the halftone/graphics color adjustment for printing color on black and white printers (check

the printer properties under Start > Settings > Printer). For more information, see the online help for the Acrobat Reader.

® the amount of available memory in your printer. (Insufficient memory can cause a document or graphics to fail to print.)

For additional information on printing problems, refer to the documentation for your printer or contact your printer manufacturer.

Contacting AdobeIf additional information is needed about Adobe Acrobat Reader or printing problems, see the Readme.pdf file that ships with Adobe Acrobat Reader or contact Adobe at www.adobe.com.

Adding annotations to PDF filesIf you have purchased the Adobe Acrobat application, you can add annotations to Candle documentation in .PDF format. See the Adobe product for instructions on using the Acrobat annotations tool and its features.

http://www.adobe.com

Documentation Conventions



IntroductionCandle documentation adheres to accepted typographical conventions for command syntax. Conventions specific to Candle documentation are discussed in the following sections.

Panels and figuresThe panels and figures in this document are representations. Actual product panels may differ.

Required blanksThe slashed-b (b) character in examples represents a required blank. The following example illustrates the location of two required blanks.

beBA*ServiceMonitorb0990221161551000

Revision barsRevision bars (|) may appear in the left margin to identify new or updated material.

Variables and literalsIn examples of command syntax, uppercase letters are actual values (literals) that the user should type; lowercase letters are used for variables that represent data supplied by the user. Default values are underscored.

LOGON APPLID (cccccccc)

In the above example, you type LOGON APPLID followed by an application identifier (represented by cccccccc) within parentheses.

Note: In ordinary text, variable names appear in italics.

Preface 15


SymbolsThe following symbols may appear in command syntax:

Table 1. Symbols in Command Syntax

Symbol Usage

| The “or” symbol is used to denote a choice. Either the argument on the left or the argument on the right may be used. Example:

YES | NOIn this example, YES or NO may be specified.

[ ] Denotes optional arguments. Those arguments not enclosed in square brackets are required. Example:

APPLDEST DEST [ALTDEST]In this example, DEST is a required argument and ALTDEST is optional.

{ } Some documents use braces to denote required arguments, or to group arguments for clarity. Example:

COMPARE {workload} -REPORT={SUMMARY | HISTOGRAM}

The workload variable is required. The REPORT keyword must be specified with a value of SUMMARY or HISTOGRAM.

_ Default values are underscored. Example:

COPY infile outfile - [COMPRESS={YES | NO}]In this example, the COMPRESS keyword is optional. If specified, the only valid values are YES or NO. If omitted, the default is YES.

Candle Customer Service and Satisfaction


Candle Customer Service and Satisfaction

BackgroundTo assist you in making effective use of our products, Candle offers a variety of easy-to-use online support resources.

The Candle Web site provides direct links to a variety of support tools that include a range of services. For example, you can find information about training, maintenance plans, consulting and services, and other useful support resources. Refer to the Candle web site at www.candle.com for detailed customer service and support information.

Candle Customer Service and Satisfaction contactsYou will find the most current information about how to contact Candle Customer Support by telephone or e-mail on the Candle Web site. Go to the www.candle.com support section and find the link to Support Contacts, to locate your regional support center.

http://www.candle.com


What’s New in Version 610 17

What’s New in Version 610

Support for z/VM™ Candle is committed to supplying its customers with a performance monitoring package to support the most recent VM release.

® Version 610 installation drops support of VM/ESA release 2.4.0 and provides support for z/VM releases 3.1.0, 4.1.0, 4.2.0, 4.3.0, and 4.4.0 in both 32-bit and 64-bit images.

VM Systems Supported by Version 610OMEGAMON and EPILOG for VM Version 610 supports the following VM systems:

System RequirementOMEGAMON for VM Version 610 requires that the immediate-and-relative instruction facility be present in all z/VM images. If the relative branch instructions are not present, the product will fail with a PRG001 abend.

Important Notice About Future Releases

If you are using the OMEGAMON collector virtual machine to record unprocessed monitor data for purposes other than EPILOG reporting, you may be impacted by changes planned for future releases. For future compatibility, Candle recommends using the MONWRITE program for sites that want to access unprocessed CP MONITOR data. Please refer to the OMEGAMON and EPILOG for VM Installation and Customization Guide, Chapter 1 for further information about installing CP Monitor/Collector interface feature.

Table 2. VM Systems Supported by OMEGAMON and EPILOG for VM Version 610

Candle System Code IBM VM System IBM Release Level

Z310 z/VM 3.1.0

Z410 z/VM 4.1.0

Z420 z/VM 4.2.0

Z430 z/VM 4.3.0

Z440 z/VM 4.4.0

W


Corrective EnhancementsCorrective enhancements have been made in Version 610 for changes required by product maintenance through October 2003. The documentation has been updated where appropriate to reflect these enhancements.

What’s New in Version 610 19

Online DocumentationWith Version 600, Candle Corporation moved OMEGAMON for VM and EPILOG for VM manuals from IBM BookMaster to Adobe FrameMaker. This move was made to better enable us to address our customers’ needs by providing tools that enhance productivity.

One of the results of the move is that it is no longer possible to create BookManager versions of the OMEGAMON and EPILOG for VM manuals. However, the manuals remain available online in the Adobe PDF version on CD-ROM and are also available on the Candle Corporation Web site at www.Candle.com.



System Overview 21

System Overview

EPILOG for VM collects system performance information over a period of time, stores it, and allows you to produce historical resource reports, workload reports, and graphs to analyze your installation’s needs.

The reports and graphs help you analyze past events from different perspectives to gain the insights needed to maintain a smooth and efficient operation.

Chapter ContentsEPILOG for VM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22The Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23The Datastore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23The Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24The Data Extraction Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24The Data Accumulation Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

1

EPILOG for VM Components

22 EPILOG for VM Product Manual Version 610


OverviewEPILOG for VM has three components:

® The Collector

® The Datastore

® The Reporter

The figure below shows the relationship among these components.

FIGURE 1. EPILOG for VM Components

The OMEGAMON virtual machine is a directory configuration and is needed only when installing and applying maintenance ZAPs to EPILOG and the Collector.

System Overview 23


The CollectorThe Collector runs as a disconnected virtual machine. It gathers performance data by sampling the system to find the status of devices and workloads (virtual machines) and by interfacing with MONITOR. The Collector then writes the data to the datastore, where it is later read by the EPILOG Reporter. The Collector described here is the same one used for OMEGAMON® impact and bottleneck analysis.

Collector operation is based on three time intervals: the sampling interval, the validation interval, and the recording interval.

You can control which devices and workloads (virtual machines) the Collector monitors, the frequency that the Collector monitors them, and the frequency that the Collector writes the data to the datastore. These are controlled via Collector control statements in a CMS file called a control file. The Candle-supplied default control file is named COLLECT CONTROL.

How you control the Collector affects your options when using the Reporter. That is, you can report only on data that the Collector has previously collected. For example, if you tell the Collector to write to the datastore every two hours, the smallest reporting interval you can request on a report is two hours. Also, if you choose not to collect data for a device or user, you cannot report on that device or user. If you choose not to collect data for the third shift or for weekends, you cannot report on those periods.

Since you may not know what you want to report on in advance, familiarize yourself with the Collector first, so you will know all the options available. For Collector information, refer to the OMEGAMON and EPILOG for VM Installation and Customization Guide.

The DatastoreThe collector virtual machine owns the datastore minidisk. The Collector writes data to the datastore, and the EPILOG for VM Reporter reads data from the datastore. Because of the EPILOG’s historical nature, all versions of EPILOG are downward-compatible. That is, any EPILOG version is able to report historical data collected by previous EPILOG versions.

You determine the size of the datastore when you define the collector virtual machine. After installation, you maintain the datastore by compressing data into fewer records with longer sampling intervals, dumping data from the datastore to tape or disk, and, when necessary, restoring data from tape to a datastore. For information on maintaining the datastore, refer to “Maintaining the Datastore” on page 181.

Sampling interval This is the shortest interval, and indicates how frequently the Collector obtains performance data. At each sampling interval, the Collector checks the state of devices and workloads. The results of the Collector’s sampling provide the raw data on which Reporter calculations are based. The default is 2 seconds.

Validation interval This determines how frequently the Collector validates that users are still logged on and that devices are still online. The default is 60 seconds.

Recording interval This is the longest interval. It indicates how frequently the Collector writes data to the datastore and clears the sampling counters. This determines the minimum reporting COMBINE period. The default is 15 minutes.


24 EPILOG for VM Product Manual Version 610

The ReporterThe EPILOG Reporter lets you tailor and print historical reports based on EPILOG Collector data. The Reporter runs as a CMS application in the user’s virtual machine. It reads data from the EPILOG datastore.

You control the data (including devices and workloads) that the Reporter reports on. You can also control the reporting periods and the grouping of data via Reporter commands. Reporter commands are entered into a CMS file called a command file. Several sample command files have been included on the product tape. The Reporter allows you to print three types of reports:

The Data Extraction FacilityThe EPILOG data extraction facility allows you to select data from the EPILOG datastore and write it to a file where you can use the software product of your choice to analyze and display the data.

The data extraction facility formats its output files so they are suitable as input to the following types of processing:

® user-written mainframe programs

® mainframe statistical, graphic, or Reporter packages

® PC statistical, graphic, or Reporter packages

The data extraction facility is documented in “Extracting Data with EVOBT EXEC” on page 170.

The Data Accumulation FacilityThe data accumulation facility condenses the data in the active datastore. You can save significant DASD storage by using this facility to generate files with fewer records having longer recording intervals. You select the files to be condensed and the interval to be used in condensing the files. For your convenience, sample EXECs are provided to perform the accumulation function, dump active datastore files or condensed files, and load previously dumped files. To ensure that there is no loss of data, continuous data collection is maintained while these functions are being performed.

The accumulation facility is documented in “The EVACCUM EXEC” on page 183.

Resource Reports Provide performance information on system resources.

Workload Reports Show the impact a virtual machine or group of virtual machines had on a system resource.

Trend Graphs Lets you graph certain data to detect trends in system usage.

Solving Data Center Problems 25

Solving Data Center Problems

This chapter shows how to use EPILOG as a problem-solving tool and explores five typical performance problems that relate to system availability and response time. Each performance problem is investigated with a series of EPILOG reports that lead to one or more possible solutions. The investigations take into account the fact that different reports are available under different releases of VM.

The sample investigations in this chapter demonstrate EPILOG commands that generate specific reports. The general -instructions for using these commands are in “REPORT and SET - Generating Reports” on page 53.

Chapter ContentsSolving CPU Utilization Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Solving Workload Transaction Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Solving Paging and Storage Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Solving I/O Balancing Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Solving Spooling Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

2

Solving CPU Utilization Problems


Solving CPU Utilization Problems The following procedure is an example of how you might resolve a CPU utilization problem.

1. Several users call the data center claiming that response time is poor and seems to be getting worse each day. Your manager asks you to first substantiate the complaints, and then locate the cause or causes of the response time delays.

2. Validate the claims of poor response time by running the Transactions Activity Report. Insert the following command in a Reporter command file.

REPORT RTRA SDATE(09/01/90) EDATE(10/05/90) -

STIME(9) ETIME(17) CMB(2H)

The SDATE, EDATE, STIME, and ETIME keywords provide a system-wide transaction report spanning the hours of 9:00 AM to 5:00 PM from the 1st of January through the 5th of February. The COMBINE keyword causes the EPILOG for VM Reporter to summarize the data into two-hour intervals. Figure 2 is an example of the result.

FIGURE 2. The Transaction Activity Report

The output in Figure 2 indicates that trivial and non-trivial response time indicators have been creeping up over the last month (from .026 to .103, and from 1.195 to 2.301). The complaint is validated. Now the specific problem areas must be identified.

3. Run the Bottleneck Analysis Report to identify specific system bottlenecks.Use the following command to request last month’s data with the same time frame (9:00 AM to 5:00 PM) as the previous report, but with more detailed information (combine into one hour instead of two). Figure 3 is an example of the result.

REPORT RBOT LASTMONTH STIME(9) ETIME(17) CMB(1H)

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 3, 2003 DATA PROCESSED: 09/01/03 06:00 TO 10/05/03 18:00 HIGH LEVEL SUMMARY REPORT WLAVMXA PERFORMANCE INDICATOR MINIMUM AVERAGE MAXIMUM STANDARD DEVIATION BSERVATIONS --------------------------------------------------------------------------------------------------RESOURCE AVAILABILITY INDEX .961 .963 .966 .001 48 % CPU BUSY 10.874 12.498 13.915 .740 48 % VIRTUAL BUSY 5.684 6.486 7.246 .343 48 % PROCESSOR 0 BUSY 4.000 4.875 6.000 .39 48 % PROCESSOR 1 BUSY 5.000 6.125 8.000 .733 48 TOTAL/VIRTUAL RATIO 1.818 1.928 2.08 .071 48 TRIVIAL TRANSACTIONS / SEC .213 .239 .261 .01 48 NON-TRIVIAL TRANSACTIONS / SEC .019 .039 .069 .011 48 TRIVIAL TRANSACTION COUNT 192.000 215.062 235.000 9.879 48 NON-TRIVIAL TRANSACTION COUNT 17.000 35.312 62.0 10.331 48 AVERAGE LOGGED ON USERS 31.000 32.192 33.0 .700 48 ACTIVE USERS 15.600 16.511 20.533 1.487 48 % VM I/O WAIT .000 .000 .000 .000 48 % VM PAGE WAIT .000 .000 .000 .000 48 I/O / SEC 11.915 13.677 25.02 1.972 48 PAGE I/OS / SEC .000 1.502 61.469 8.897 48 % SPOOL SPACE IN USE 17.590 17.606 17.622 .010 48 % TEMP DISK SPACE IN USE .000 .595 .952 .466 48 % PAGING SPACE IN USE 12.153 17.539 19.555 3.144 48 % OF REAL STORAGE=SYSTEM FRE 25.902 26.122 27.025 .373 48 % OF REAL STORAGE=DPA 68.613 69.516 69.736 .373 48 % LOGICAL PROCESSOR BUSY 5.157 5.603 6.074 .206 48 % PHYSICAL PROCESSOR BUSY 3.438 3.735 4.050 .137 48



FIGURE 3. The Bottleneck Analysis Report

The report in Figure 3 indicates that, in this case, most of the wait time is spent waiting for the CPU (% CPU WAIT).

4. Generate either a line graph or a tabular report showing CPU activity to examine the CPU bottleneck in more detail. Use the following command to request the report for the last 3 months to see if there is a trend toward increased CPU activity.

REPORT RCPU SDATE(-90) STIME(9) ETIME(17) -

CMB(1H) GRAPH(LINE,CPUBUSY)

The SDATE keyword generates a report that begins three months (90 days) ago. STIME and ETIME limit the report to the hours of 9:00 AM to 5:00 PM. The GRAPH keyword provides a line graph that shows CPU usage. Figure 4 is an example of the result.

EPILOG FOR VM V610 PAGE 1RUN DATE:OCTOBER 6,2003 DATA PROCESSED:09/01/03 09:00 TO 09/30/03 17:00 COMBINE(1H) BOTTLENECK ANALYSIS REPORT WLVM --INTERVAL START-- % % IDLE % I/O PAGE % CF % SIM % CPU % USING % SAMPLE DATE TIME IDLE SVM WAIT WAIT WAIT WAIT WAIT WAIT CPU OTHER COUNT----<1>-----------------------------------------------------------------------------09/01/03 09:00 .7 .3 1.2 2.1 .8 .2 10.4 21.2 3.9 125009/01/03 10:00 .8 .4 1.3 1.3 1.3 .3 11.2 26.3 4.1 125009/01/03 11:00 .7 .2 2.3 1.2 1.4 .4 9.6 23.3 5.2 125009/01/03 12:00 .9 .3 1.2 3.7 1.3 .3 9.7 21.5 6.1 125009/01/03 13:00 .9 .1 1.4 2.8 1.2 .2 8.9 22.9 7.0 125009/01/03 15:00 1.0 .3 2.5 2.4 1.4 .4 12.9 27.1 5.3 125009/01/03 16:00 1.1 .1 2.5 2.5 .9 .1 11.9 23.4 6.2 125009/03/03 09:00 1.1 .2 2.1 3.5 1.3 .1 9.9 26.5 5.1 125009/03/03 10:15 1.2 .2 2.7 2.9 1.4 .2 11.4 25.3 9.2 1250 . . . . . . . . . . . .09/31/03 12:00 1.1 .2 2.3 3.3 1.1 .2 13.1 26.2 5.3 125009/31/03 13:00 1.3 .1 2.7 3.1 1.1 .3 14.3 27.4 6.2 125009/31/03 14:00 1.2 .2 2.4 4.0 1.1 .1 15.1 22.8 4.9 125009/31/03 15:00 1.3 .2 2.1 3.2 1.1 .4 14.9 23.8 6.5 125009/31/03 16:00 1.3 .1 2.3 4.1 1.1 .3 13.3 32.9 5.1 1250------------------------------------------------------------------------------------ 1.2 .2 2.1 3.0 33.3 .3 10.1 29.8 7.5 26010



FIGURE 4. The CPU Activity Trend Graph

The graph in Figure 4 is one of five pages generated by the above command. The X-axis represents time, and the Y-axis represents the total CPU percent used, which includes CP percent and virtual percent. You can identify a trend showing that CPU utilization has been increasing over the past three months.

Heavy CPU utilization is usually caused by an increase in operating system overhead (CP time) or an increase in virtual machine usage (virtual CPU time). Operating system overhead is caused by such processing as storage management, queue management for dispatching and scheduling, and I/O management. The more time the CPU spends managing the system, the less time it has to let virtual machines use the CPU.

5. To determine whether the increased CPU utilization was caused by increased operating overhead or increased virtual machine usage, check the T/V ratio on the tabular version of the CPU Activity Report. The T/V ratio is the ratio of total CPU usage (CP and virtual machine time) to virtual CPU usage (only virtual machine time).

CP Time + Virtual Machine Time ----------------------------------------------------- Virtual Machine Time

EPILOG FOR VM V610 DATA PROCESSED: 11/07/03 09:00 TO 02/05/03 17:00 PAGE 3RUN DATE: FEBRUARY 6, 2003 CPU ACTIVITY TREND (CPUBUSY) COMBINE(1H) |-------------------------------------------------------------------------------------------------- 100.00 + . . . | | . . . | .*** | . . . .** 91.00 + .*** | . . . .** | .**. .**** | . . . .*** *** | .*** 78.00 + . . . .**. .*** | .*** **** | . . . ***** | | **** . . . 65.00 + ******. .C | ***.. . .**** . . .P | . .**U | .* . . .B | *U 52.00 + ** . . .S | *Y | * . . . | * | . . . . 39.00 + . |*** . . . | | . . . | 26.00 + . . . | | . . . | | . . . 13.00 + | . . . | | . . . | O-------------------------------------------------------------------------------------------------- 10:00 16:00 14:00 12:00 10:00 16:00 . . . 09:00 15:00 13:00 15:00 13:00 11:00 09:00 15:00 13:00 11:00 17:00 15:00 13:00 11:00 17:00 . . . 10:00 16:00 14:00 16:00 14:00 12:00 10:00 16:00 14:00 09/03 09/03 09/04 09/05 09/06 09/06 . . . 09/12 09/13 09/14 09/15 09/16 09/17 09/18 09/21 09/22



A T/V ratio of 1 means that there is no system overhead. As this ratio increases beyond 1, it indicates that system overhead is growing. A T/V ratio of 2 means that system overhead has grown to equal the CPU usage of all virtual machines. Use the following command to generate a tabular CPU Activity Report that includes the T/V ratio. Figure 5 is an example of the result.

REPORT RCPU SDATE(9/1/90) STIME(9) ETIME(17) CMB(1H)

FIGURE 5. The CPU Activity Report Highlighting T/V Ratio

The report in Figure 5 shows that the T/V ratio is increasing only moderately and at a level below 2. If the T/V ratio were increasing rapidly and above 2, a CP subsystem might be causing this additional CPU overhead. In this case, there is no strong evidence that CP overhead is causing the CPU bottleneck.

The report also shows that two items are increasing along with the T/V ratio: the number of logged on users (LOGGED

ON AVG and LOGGED ON MAX) and the number of active users (ACTIVE USERS).

6. The investigation is complete. Since the CPU bottleneck appears to be caused by an increasing number of users, the following two actions provide possible solutions.® Redistribute the workload to another machine or to another shift.

® Upgrade the current CPU (hardware).

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 17, 2003 DATA PROCESSED: 09/11/03 12:21 TO 09/12/03 03:25 COMBINE (1H) ACTIVITY REPORT WLVM INTERVAL START- # CPU CP VIRT TOTAL/ USERS USERS IN -LOGGED ON- ACTIVE DIALED -LPAR UTILIZTION- DATE TIME CPUS % % % VIRT IN ELIGIBLE AVG MAX USERS USERS LOGICAL PHYSICAL RATIO QUEUE-<1>--------------------------------------------------------------------------------------------09/11/03 12:21 2 39 18 21 1.857 3 0 36 36 18 2 9.26 6.1709/11/03 13:00 2 51 23 28 1.821 3 0 36 36 18 2 8.91 5.9409/11/03 14:00 2 48 21 27 1.777 4 0 36 36 17 3 9.04 6.0309/11/03 15:00 2 69 28 41 1.682 4 0 65 70 31 2 9.08 6.0509/11/03 16:00 2 58 23 27 1.847 5 0 45 46 21 3 2.62 1.7509/11/03 18:00 2 61 25 26 1.696 5 0 47 49 22 3 2.69 1.7909/11/03 19:00 2 58 25 33 1.759 5 0 50 50 22 6 2.67 1.7809/11/03 20:00 2 69 28 41 1.682 3 0 65 70 31 2 2.71 1.8009/11/03 21:00 2 49 23 26 1.884 5 0 45 46 21 3 2.65 1.7709/11/03 22:00 2 65 32 33 1.969 6 0 66 71 33 2 2.47 1.6509/11/03 23:00 2 41 28 21 1.952 4 0 38 39 19 3 3.54 2.3609/12/03 00:00 2 78 36 42 1.857 3 0 66 71 37 3 2.48 1.6509/12/03 01:00 2 77 35 42 1.833 5 0 68 72 39 3 2.55 1.7009/12/03 02:00 2 79 38 41 1.926 5 0 72 75 40 3 2.55 1.7009/12/03 03:00 2 82 41 41 2.000 4 0 75 79 41 3 2.50 1.66 ----------------------------------------------------------------------------------------------- 2 64 31 27 1.878 5 0 56 61 32 3 4.29 2.86

Solving Workload Transaction Problems


Solving Workload Transaction ProblemsThe following procedure is an example of how you might resolve a workload transaction problem.

1. A reliable user from the Payroll Department calls the Data Center claiming that the response time yesterday was disastrous. He says that the degradation peaked between the hours of 2:00 PM and 4:00 PM.

2. A first step toward finding a solution is to examine the system transaction rate and response time during the afternoon hours mentioned by the user. Generally, you can expect a higher transaction rate to result in a slower response time.The Transaction Activity Report shows system-wide trivial and non-trivial transaction rates and response times. Run the Transaction Activity Report for the past week to see how yesterday compares with recent trends in transaction rates and response times. Insert the following command in a Reporter command file.

REPORT RTRA SDATE(-7) STIME(14) ETIME(16) CMB(2H)

The SDATE keyword provides a report that begins a week ago. STIME and ETIME are used to limit the report to the afternoon hours specified by the user. CMB(2H) is used to combine data into two-hour intervals, since you are only looking for a general trend. Figure 6 is an example of the result.

FIGURE 6. The Transaction Activity Report

The report in Figure 6 shows that yesterday’s (10/18/03) response times were not significantly greater than on any other day of the week. Based on this information, we can assume that this is a single-user problem, and not a system-wide problem.

3. Examine transaction activity for the user (workload) in question. (A workload is one or more virtual machines.) The Workload Transaction Activity Report shows the transaction rate and response time on a workload-by-workload basis. To obtain transaction activity information for the required user, enter the following command in the EPILOG command file.

REPORT WTRA YESTERDAY STIME(14) ETIME(16) -

SELECTIF(WORKLOAD,(=PAYROL1))

PAYROL1 is the user with the response time degradation. A relative date (YESTERDAY) is used, but an absolute date (10/18/03) could also have been used. Figure 7 is an example of the result.

Note: Relative dates can be especially useful when you know you will always want a report run from a specific relative time frame like yesterday. No matter when you run this report, you will always get yesterday’s activity.

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/12/03 14:00 TO 10/18/03 16:00 COMBINE(2H) TRANSACTION ACTIVITY REPORT WLVM --INTERVAL START-- -------TRIVIAL TRANSACTIONS------- ------NON-TRIVIAL TRANSACTIONS------ DATE TIME COUNT TRANS/SEC RESPONSE COUNT TRANS/SEC RESPONSE--<1>--------------------------------------------------------------------------------------------------------- 10/12/03 14:00 13565 1.512 1.018 1342 .079 3.059 10/13/03 14:00 13605 1.028 1.023 1089 .071 3.211 10/14/03 14:00 14021 .812 1.218 1241 .069 3.234 10/15/03 14:00 14221 .928 1.211 689 .071 3.302 10/16/03 14:00 14634 1.012 1.418 1023 .073 3.456 10/17/03 14:00 15605 1.013 1.452 707 .043 3.643 10/18/03 14:00 15702 .811 1.460 1421 .041 3.789-------------------------------------------------------------------------------------------------------------- 101353 1.017 1.337 7512 .063 3.385



FIGURE 7. The Workload Transaction Activity Report

The output in Figure 7 represents four pages of an eight-page (one page per recording interval) report generated by the above command. The report shows that the user (PAYROL1) experienced unacceptable response times between the hours of 14:30 and 15:30. The next step is to locate the major wait states for this workload.

4. Workload Bottleneck Analysis Report (WBOT) shows relative wait, busy, and idle-states at the potential bottlenecks for all virtual machines. If bottleneck data was collected for PAYROL1, you can determine why the response time for this virtual machine was degraded by locating the place where it spent most of its time either doing real work (high % CPU busy) or waiting (for various reasons). If bottleneck data collection was not turned on previously and this problem continues, enable collection for future reference by entering the following command in the Collector control file.

COLLECT BOTTLENECK (PAYROL1)

See the OMEGAMON and EPILOG for VM Installation and Customization Guide for more information on controlling data collection. Once data has been collected, the following command produces the four-page report in Figure 8.

REPORT WBOT YESTERDAY STIME(14:30) ETIME(15:30) -

SELECTIF(WORKLOAD(=PAYROL1))

EPILOG FOR VM V610 PAGE 3RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/18/03 14:30 TO 10/18/03 14:45 COMBINE(15M) WORKLOAD TRANSACTION ACTIVITY REPORT WLVM VM --------TRIVIAL TRANSACTIONS-------- --------NON-TRIVIAL TRANSACTIONS------- WORKLOAD COUNT TRANS/SEC RESPONSE COUNT TRANS/SEC RESPONSE-----<1>------------------------------------------------------------------------------------------------------ PAYROL1 123 2.534 .301 33 .231 4.021-------------------------------------------------------------------------------------------------------------- 123 2.534 .301 33 .231 4.021 EPILOG FOR VM V610 PAGE 4RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/18/03 14:45 TO 10/18/03 15:00 COMBINE(15M) WORKLOAD TRANSACTION ACTIVITY REPORT WLVM VM --------TRIVIAL TRANSACTIONS-------- --------NON-TRIVIAL TRANSACTIONS------- WORKLOAD COUNT TRANS/SEC RESPONSE COUNT TRANS/SEC RESPONSE-----<1>------------------------------------------------------------------------------------------------------ PAYROL1 142 1.997 .521 38 .211 4.894-------------------------------------------------------------------------------------------------------------- 142 1.997 .521 38 .211 4.894 EPILOG FOR VM V610 PAGE 5RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/18/03 15:00 TO 10/18/03 15:15 COMBINE(15M) WORKLOAD TRANSACTION ACTIVITY REPORT WLVM VM --------TRIVIAL TRANSACTIONS-------- --------NON-TRIVIAL TRANSACTIONS------- WORKLOAD COUNT TRANS/SEC RESPONSE COUNT TRANS/SEC RESPONSE-----<1>------------------------------------------------------------------------------------------------------ PAYROL1 151 2.220 .627 42 .219 4.629-------------------------------------------------------------------------------------------------------------- 151 2.220 .627 42 .219 4.629 EPILOG FOR VM V610 3 PAGE 6RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/18/03 14:30 TO 10/18/03 15:30 COMBINE(15M) WORKLOAD TRANSACTION ACTIVITY REPORT WLVM VM --------TRIVIAL TRANSACTIONS-------- --------NON-TRIVIAL TRANSACTIONS------- WORKLOAD COUNT TRANS/SEC RESPONSE COUNT TRANS/SEC RESPONSE-----<1>------------------------------------------------------------------------------------------------------ PAYROL1 162 1.992 .733 47 .187 6.011-------------------------------------------------------------------------------------------------------------- 162 1.992 .733 47 1871 6.011



FIGURE 8. The Workload Bottleneck Analysis Report

The most likely place for a bottleneck is in the CPU, paging, or I/O subsystem. The data collected with the Candle bottleneck function includes additional I/O device information. The information shows whether there is I/O contention and which five devices a user is waiting for most often.

In the current situation, the I/O subsystem (I/O WAITS) is the problem, and device 233 is causing the greatest amount of contention for this user. You can now either analyze the contention on device 233, or proceed to the problem “Solving I/O Balancing Problems” on page 40.

5. To analyze the contention on device 233 more thoroughly, run the Seek Analysis Report. This report can help detect the cause of an I/O bottleneck within the device selected by the SELECTIF keyword.If you have not been collecting seek data for the device, either turn on collection for the hours specified for future reference, or investigate other possible areas of I/O contention, such as channels (reports RCHN and RCHP) or DASD (report RDAS). To generate the report in Figure 9 you must first turn on collection for the specified time period:

COLLECT SEEKS DEV(233) ST(14:30) ET(15:30)

Issue the following command to generate the Seek Analysis Report in Figure 9.

REPORT RSEEK YESTERDAY ST(14:30) ET(15:30) -

SELECTIF(DEVADDR,(=233))

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/18/03 14:30 TO 10/18/03 14:45 COMBINE(15M) WORKLOAD BOTTLENECK ANALYSIS REPORT WLVM VM %CPU % % %SVM %PG %CF %SIM %CPU +------------------I/O WAITS-----------------+ SAMPLEWORKLOAD BUSY OTHER IDLE WAIT WAIT WAIT WAIT WAIT |DEV % |DEV % |DEV % |DEV % |DEV % | COUNT-<1>----------------------------------------------------------------------------------------------------------PAYROL1 11.2 12.3 36.4 1.0 7.1 16.1 .3 4.8 |233 10.4|240 0.1| 0 .0| 0 .0| 0 .0| 00-------------------------------------------------------------------------------------------------------------- 11.2 12.3 36.4 1.0 7.1 16.1 .3 4.8 900 EPILOG FOR VM V610 PAGE 2RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/18/03 14:45 TO 10/18/03 15:00 COMBINE(15M) WORKLOAD BOTTLENECK ANALYSIS REPORT WLVM VM %CPU % % %SVM %PG %CF %SIM %CPU +------------------I/O WAITS-----------------+ SAMPLEWORKLOAD BUSY OTHER IDLE WAIT WAIT WAIT WAIT WAIT |DEV % |DEV % |DEV % |DEV % |DEV % | COUNT-<1>----------------------------------------------------------------------------------------------------------PAYROL1 10.1 12.1 38.0 1.0 6.1 17.1 1.4 3.5 |233 8.1|682 2.2|240 0.4| 0 .0| 0 .0| 900-------------------------------------------------------------------------------------------------------------- 10.1 12.1 38.0 1.0 6.1 17.1 1.4 3.5 900 EPILOG FOR VM V610 PAGE 3RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/18/03 15:00 TO 10/18/03 15:15 COMBINE(15M) WORKLOAD BOTTLENECK ANALYSIS REPORT WLVM VM %CPU % % %SVM %PG %CF %SIM %CPU +-----------------I/O WAITS------------------+ SAMPLEWORKLOAD BUSY OTHER IDLE WAIT WAIT WAIT WAIT WAIT |DEV % |DEV % |DEV % |DEV % |DEV % | COUNT-<1>----------------------------------------------------------------------------------------------------------PAYROL1 9.2 14.8 32.9 4.0 7.1 16.1 .4 4.6 |233 8.5|221 1.4|682 1.0| 0 .0| 0 .0| 900-------------------------------------------------------------------------------------------------------------- 9.2 14.8 32.9 4.0 7.1 16.1 .4 4.6 900 EPILOG FOR VM V610 PAGE 4RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/18/03 15:15 TO 10/18/03 15:30 COMBINE(15M) WORKLOAD BOTTLENECK ANALYSIS REPORT WLVM VM %CPU % % %SVM %PG %CF %SIM %CPU +-----------------I/O WAITS------------------+ SAMPLEWORKLOAD BUSY OTHER IDLE WAIT WAIT WAIT WAIT WAIT |DEV % |DEV % |DEV % |DEV % |DEV % | COUNT-<1>----------------------------------------------------------------------------------------------------------PAYROL1 12.2 11.8 35.9 1.3 6.8 18.2 .3 2.8 |233 8.3|221 2.1|682 0.3| 0 .0| 0 .0| 829-------------------------------------------------------------------------------------------------------------- 12.2 11.8 35.9 1.3 6.8 18.2 .3 2.8 829



FIGURE 9. The Seek Analysis Report

Since I/O to a DASD device involves mechanical movement, much time may be spent moving to new locations on the DASD to perform I/O requests. To minimize the size of the moves and decrease seek time, it is best to keep your most utilized data concentrated in one area, usually at or near the center of the device. The “center of the device“ is dependent on the specific DASD device type being utilized.

The 227-280 DASD extent value on the Seek Analysis Report in Figure 18 indicates that user PAYROL1 is not located near the center of the device (DASD EXTENT). The location of PAYROL1 is a possible cause of the slow response time.

6. If the Workload Bottleneck Analysis Report in Figure 8 on page 32 had indicated that PAYROL1 was waiting on a service virtual machine (% SVM WAIT), you would have run the Workload IUCV/VMCF Communication Report instead of the Seek Analysis Report. Issue the following command to help you find the reason for a service virtual machine wait. Figure 10 is an example of the result.

REPORT WICO YESTERDAY STIME(14:30) ETIME(15:30)

The following figure is an example of the results:

FIGURE 10. The Workload IUCV/VMCF Communications Report

EPILOG FOR VM V610 PAGE 2RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/18/03 14:45 TO 10/18/03 15:00 COMBINE(15M) SEEK ANALYSIS REPORT WLVM DEVICE USERID VIRTUAL REAL DEVICE DASD EXTENT TOTAL SEEKS IN AVG MOVE AVG MOVEVOLSER ADDRESS ADDRESS TYPE EXTENT COUNT SEEKS EXTENT PER SEEK WITHIN EXTENT-------------------------------<1>----------------------------------------------------------------------------VM9 VMTEST 100 233 3380 300-539 240 93 83 23.3 23.3VM9 VMUTIL 191 233 3380 760-760 1 74 49 9.1 .0VM9 VMCH09 401 233 3380 1004-1007 4 103 63 8.0 .5VM9 VMFL07 401 233 3380 1008-1011 4 20 18 3.3 .3VM9 PAYROL1 191 233 3380 227-280 54 48 37 115.6 4.5 . . . . . . . . .VM9 VMUSER02 200 233 3380 50-99 50 101 82 6.2 2.9VM9 VMCH01 200 233 3380 140-169 30 25 21 4.4 1.3VM9 VMUSER01 200 233 3380 1050-1599 550 196 107 57.8 34.3VM9 VMFL03 100 233 3380 100-139 40 13 5 131.7 21.7-------------------------------------------------------------------------------------------------------------- 589 385 89.7 14.5

EPILOG FOR VM V610 PAGE 2RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/18/03 14:45 TO 10/18/03 15:00 WORKLOAD IUCV/VMCF COMMUNICATIONS ACTIVITY REPORT WLVM VM --------------- I U C V ----------------- --------------- V M C F ----------------- WORKLOAD SOURCE XFERS TARGET XFERS % ERR SOURCE XFERS TARGET XFERS % ERR--<1>---------------------------------------------------------------------------------------------------------CMSBATR5 0 0 .0 102 0 .0MVS 0 0 .0 0 0 .0MVSD 0 0 .0 0 0 .0PAYROL1 101 0 .1 0 0 .0PVM 0 0 .0 0 0 .0 . . . . . . . . .PVM02 0 0 .0 0 10 .0RSCS 0 0 .0 0 19 .0SQL/DS 0 370 .0 0 0 .0VMUTIL 0 09 .0 0 0 .0ZVMBATC 380 0 .0 0 0 .0------------------------------------------------------------------------------------------------------------- 481 479 .0 102 29 .0



The output in Figure 10 represents one page of a four-page (one page per recording interval) report generated by the above command. The value in the IUCV Source Xfers column shows that PAYROL1 sent many (101) IUCV requests. You know that PAYROL1 uses a database on the SQL/DS® virtual machine, so you might examine IUCV requests for the SQL/DS machine also. The number of IUCV requests is high (370). This high level of activity on the SQL/DS virtual machine suggests that SQL/DS is the service virtual machine that PAYROL1 is waiting for.

7. The investigation is complete. If I/O contention was detected on the Workload Bottleneck Analysis Report, move the user PAYROL1 from cylinder 10 to somewhere closer to the center of the device where more utilized data should be concentrated.If this device shows a high Percent Busy on the RDASD Report, you may want to move user PAYROL1’s 191 disk to another DASD.

If contention on the service virtual machine is the problem, try these three possible solutions:

® Allocate more resources to the SQL/DS service machine. Increase SHARE. Add or increase reserve pages, and/or allocate expanded storage to this machine.

® Allocate another SQL/DS service machine isolated for the payroll department.

® Continue to evaluate the SQL/DS virtual machine and PAYROL1’s application to make sure the application is using the SQL/DS structure efficiently.


Solving Paging and Storage Problems

Solving Paging and Storage ProblemsThe following procedure is an example of how you might resolve a paging or storage problem.

1. The performance analyst who runs the EPILOG High-Level Summary Report noticed that the wait percent for paging has been steadily increasing over the last few months. Since she knows that paging is crucial for good response time on VM, she wants to investigate the situation before the effects reach the users.

2. Begin the investigation by examining the High-Level Summary Report that was used by the performance analyst in discovering the paging problem. Typically, you will run this report daily or weekly for a convenient overview of the entire system and for rapid location of potential problem areas. Insert the following command in a Reporter command file and start EPILOG with this command file.

REPORT RHLS YESTERDAY STIME(6) ETIME(18)

Notice that the COMBINE keyword is not used in this command because the complete output is already combined into the Report Time interval (between the start and end times). Output consists of the average, maximum, minimum, standard deviation, and number of observations for all performance indicators for the entire selected time. Figure 11 is an example of the result.

FIGURE 11. The High-Level Summary Report

The report in Figure 11, shows that both the paging rate (PAGES/SEC) and page wait (% VM PAGE WAIT) are high. In order to analyze the problem further, we need to examine a report that shows the paging subsystem in more detail and the workloads that affect the paging subsystem.

3. Obtain more detailed information for all paging devices for this system by running the Paging Activity Report. Enter the following command in a Reporter command file.

REPORT RPAG YESTERDAY STIME(6) ETIME(18) -

CMB(1H) SORTBY(SERVTIME(D))

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/18/03 06:00 TO 10/18/03 18:00 HIGH LEVEL SUMMARY REPORT WLVM PERFORMANCE INDICATOR MINIMUM AVERAGE MAXIMUM STANDARD DEVIATION OBSERVATIONS----------------------------------------------------------------------------------------------------------- RESOURCE AVAILABILITY INDEX .971 .974 .977 .002 48 % CPU BUSY 18.428 22.307 34.538 3.403 48 % VIRTUAL BUSY 9.501 11.957 21.520 2.495 48 TOTAL/VIRTUAL RATIO 1.605 1.881 1.975 .080 48 Q1SEC .258 .320 .404 .037 48 Q2SEC 1.377 2.151 4.240 .677 48 AVERAGE LOGGED ON USERS 21.000 21.396 22.000 .494 48 ACTIVE USERS 7.067 7.468 8.933 .345 48 % VM I/O WAIT .000 .000 .000 .000 48 % VM PAGE WAIT 23.403 35.195 38.545 2.656 48 I/O / SEC 2.068 5.306 84.147 11.628 48 PAGES / SEC 101.002 167.052 192.904 12.171 48 % SPOOL SPACE IN USE 28.654 28.696 28.803 .048 48 % TEMP DISK SPACE IN USE .000 .000 .000 .000 48 % PAGING SPACE IN USE 9.749 10.675 14.256 .931 48 STORAGE EXTENDS / SEC 22.567 22.817 23.790 .273 48 % FREE STORAGE IN USE 40.684 48.963 60.982 5.479 48 % PRIME STORAGE IN USE .000 .000 .000 .026 48 % DYNAMIC PAGING AREA IN USE 2.868 3.937 5.147 .422 48 % SWAP SPACE IN USE 25.455 37.880 49.416 6.122 48



The relative date of YESTERDAY is used with a start time of 6:00 AM and an end time of 6:00 PM. The data is summarized into one-hour time intervals by the combine keyword, CMB.

The SORTBY keyword, which can be used on any field in either ascending or descending order, is an excellent way of pinpointing problem areas. On this report, paging devices are isolated by service time. The service time is being sorted in descending order, which causes those devices with the highest service times to appear at the top of the report. The report will identify the devices in the paging subsystem that are suffering from the most service time degradation. Figure 12 is an example of the result.

FIGURE 12. The Paging Activity Report

The report in Figure 12 represents one of 12 pages (one per combine period) generated by the above command. The report shows that the service time (DEVICE SERVICE TIME) is greatest on device 146, which is a SPOOLing device. We also notice the other paging areas on the system are almost full (EXTENT PERCENT FULL).

Once the paging areas are full, the SPOOLing areas start to handle the overflow. This can cause problems for paging because SPOOL pages are deleted randomly from different locations on the DASD, causing fragmentation in the SPOOLing subsystem. Pages that should be grouped together (one I/O, faster access), may be scattered on the DASD.

4. Investigate the usage of real memory by running the Storage Management Report (RSTR). Enter the following command in a Reporter command file. Figure 13 is an example of the result.

REPORT RSTR YESTERDAY STIME(6) ETIME(18) CMB(1H)

FIGURE 13. The Storage Management Report

EPILOG FOR VM V610 PAGE 4RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/18/03 09:00 TO 10/18/03 10:00 COMBINE(1H) PAGING ACTIVITY REPORT WLVM PAGING DEVICE DASD DEVICE DASD EXTENT DEVICE I/O’S DEVICE DEVICE SERVICE TYPE ADDRESS VOLSER TYPE EXTENT PERCENT FULL PER SECOND PERCENT BUSY TIME (MS)---------------------------------------------------------------------------------------------------<1>--------SPOOLING 146 VM7 3380 1000-1599 29 .05 .06 28.73PAGING 337 VM8 3380 300-539 91 2.09 .11 13.45PAGING 327 VM9 3380 300-539 92 2.12 .13 13.39-------------------------------------------------------------------------------------------------------------- 212 1.42 .10 18.52

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/18/03 06:00 TO 10/18/03 18:00 COMBINE(1H) STORAGE MANAGEMENT REPORT WLVM INTERVAL START ------- AVAILABLE LIST ----- DPA FRAME -- EXTEND -- CP PAGE FAULT/SEC UNSUCCESSFUL DATE TIME FRAMES <HIGH & LOW THRSHLD> FRAMES WAITS FRAMES WAITS PAGEINS SINGLE BLOCK DEMAND SCANS---<1>------------------------------------------------------------------------------------------------------10/18/03 06:00 604 101 16 7808 11 495 11 396 1.1 .5 3010/18/03 07:00 558 101 16 7808 9 485 9 87 .0 .0 2910/18/03 08:00 204 101 16 7808 6 487 7 55 .0 .0 4110/18/03 09:00 051 101 16 7808 16 488 3 50 .0 .0 2210/18/03 10:00 893 101 16 7808 13 486 7 67 .0 .0 2910/18/03 11:00 753 101 16 7808 18 495 6 62 .0 .0 3110/18/03 12:00 111 101 16 7808 21 496 3 167 .1 .0 3310/18/03 13:00 111 101 16 7808 26 499 8 337 .3 .1 2810/18/03 14:00 130 101 16 7808 25 492 9 20 .0 .0 2910/18/03 15:00 135 101 16 7808 29 493 10 23 .0 .0 2110/18/03 16:00 131 101 16 7808 17 493 12 40 .0 .0 2210/18/03 17:00 142 101 16 7808 19 492 11 20 .0 .0 26------------------------------------------------------------------------------------------------------------ 319 101 16 7808 18 5901 8 111 .13 .05 341



The report in Figure 13 shows a very low number of available pages on the available list. The pages on the available list are critical for good response time. The available list is the number of pages available for use when a page must be brought in from an external device to real memory. If there are no pages available, a page must be paged-out prior to the page-in. The extra step of paging-out prior to bringing a page into memory increases response time for a virtual machine waiting for that page.

The available list is replenished by the demand scan. There are multiple levels of demand scans, but essentially a demand scan is driven by the available list low threshold. The demand scan replenishes the available list to its high threshold. It continues to run until available pages reach the high threshold.

The AVAILABLE LIST THRSHLDs are load-dependent and are continually changing. Two other important fields on this report are the EXTEND WAITS and the FRAME WAITS. The DPA (Dynamic Paging Area) and free storage area (used for CP control blocks) obtain pages from the same pool of real memory. Therefore, tasks requiring these resources contend with each other. Tasks deferred because of contention for real memory are reported under the extend waits (Free Storage) and frame waits (DPA).

5. If you have expanded storage on your system, another area of interest for paging contention problems is the Expanded Storage Subsystem. The VM control program uses expanded storage as a paging area, but expanded storage can also be allocated to a virtual machine. Because expanded storage is a slower version of real memory, there is no mechanical delay such as seek time or latency (rotation delay). The only delay involved with expanded storage is the access time, which is a little slower than real memory, and the CPU overhead used to manage expanded storage. Insert the following command in the EPILOG for VM Reporter command file to run the Expanded Storage Migration Report. Figure 14 is an example of the result.

REPORT REXP YESTERDAY STIME(6) ETIME(18) CMB(1H)

FIGURE 14. DASD Activity Report Example Showing High External Pages

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 17, 2003 DATA PROCESSED: 09/17/03 12:00 TO 09/17/03 12:06 DASD ACTIVITY REPORT WLVM DEVICE DASD DEVICE PERCENT QUEUE TOTAL I/O DEVICE I/O’S SERVICE PENDING CONNECT DISCONNECTADDRESS VOLSER TYPE BUSY DEPTH REQUESTS PER SECOND TIME (MS) TIME (MS) TIME (MS) TIME (MS)---<1>----<2>------------------------------------------------------------------------------------------------- 146 CAN002 3380 .12 .00 18 .06 19.33 .78 14.78 3.78 151 OMON28 3380 .04 .00 9 .03 14.89 .67 1.44 12.78 161 RES 3390 .12 .00 23 .05 22.74 1.13 3.96 17.65 164 CAN001 3390 .36 .00 30 .10 35.80 .47 22.67 12.67 168 TSO001 3390 .24 .00 36 .12 19.72 5.06 3.06 11.61 169 TSO002 3390 .48 .00 130 .43 11.11 2.09 3.17 5.85 172 TSO006 3390 .07 .00 16 .05 12.87 .56 2.19 10.12 307 VM1 3380 .10 .00 8 .03 36.62 .37 3.87 32.37 313 VM2 3380 .05 .00 6 .02 27.33 .33 4.33 22.67 317 VM4 3380 24.75 .00 3059 7.31 33.86 .51 14.08 19.26 31A OMON25 3380 1.46 .00 284 .95 15.41 .48 4.67 10.27 337 CAN004 3380 .16 .00 28 .09 16.68 1.36 13.57 1.75 9C1 MP223D 3380 2.95 .00 355 1.18 24.94 1.55 10.41 12.99 9C3 MVSD21 3380 45.72 .00 7305 17.46 26.19 .51 4.70 20.98 9C4 OMSTG1 3380 2.62 .00 296 .99 26.58 .40 12.17 14.01 9C8 SV0002 3380 .11 .00 10 .03 34.00 2.90 1.90 29.20 9D0 VM9 3380 .10 .00 6 .02 47.83 3.33 8.17 36.33 D80 PAGE01 3375 2.11 .00 162 .54 39.10 .31 15.66 23.12 D82 VM0 3375 .07 .00 4 .01 50.25 5.50 22.25 22.50 D8A VM1 3375 .01 .00 1 .00 40.00 .00 2.00 38.00 D8B VMHP07 3375 .18 .00 42 .10 18.38 4.98 3.71 9.69-------------------------------------------------------------------------------------------------------------- 4.86 .00 11828 29.59 27.84 .59 7.69 19.56



The report in Figure 14 shows that there is frequent migration from expanded storage to an external storage medium (that is, 3380). Active users need pages in real memory or in expanded storage for a good response time and less page delay. The most alarming numbers on this report are the movements of expanded pages from active users. This movement requires taking a closer look at how the system and/or workloads are currently using expanded storage.

6. A workload can be one virtual machine or a group of virtual machines grouped by either user ID, account number, or distribution code. It is sometimes possible to redistribute a workload in order to decrease paging bottlenecks. The Workload Paging/Storage Report provides the information required to determine if redistribution is practical, and if so, which workload should be redistributed. Enter the following command in the Reporter command file to generate the report.

REPORT WSTO YESTERDAY STIME(6) ETIME(18)

CMB(1H) SORTBY(WSS,(D))

The WORKING SET SIZE column of the report is a projection of the number of pages required to run a workload. The projection is based on the number of pages required by the workload the last time it was dispatched and dropped from queue. Usually, the larger the working set size, the more the workload increases paging activity. The SORTBY keyword helps isolate the workloads with the largest working set sizes. Workloads with the greatest working set size will percolate to the top of this report. Figure 15 is an example of the result.

FIGURE 15. The Workload Paging/Storage Report

The report in Figure 15 represents one page of a 12-page (one page per combine interval) report generated by the above command. The output shows that there are a few workloads that have very large working set sizes. These workloads are prime candidates for redistribution.

EPILOG FOR VM V610 PAGE 3RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/18/03 09:00 TO 10/18/03 10:00 COMBINE(1H) WORKLOAD PAGING/STORAGE REPORT WLVM VM WORKING SET RESIDENT PAGE PAGE PAGE SWAP SWAP SWAP STORAGEWORKLOAD SIZE(PAGES) PAGES RATE/SEC READS WRITES RATE/SEC READS WRITES SIZE IN K-----------------<1>------------------------------------------------------------------------------------------MVSD 3166 3413 5.96 7967 6276 .26 3472 3976 24576MVS 3006 3170 4.80 8469 6466 .17 247 380 20572MVSA 2674 2668 2.40 502 190 .10 175 175 12288VMTST 832 832 2.00 109 67 .02 19 57 8192CMSBATR5 282 0 .00 0 0 .00 0 0 16384PAYROL1 178 0 .00 0 0 .00 0 0 16384VMADMIN 112 0 .00 0 0 .00 0 0 6144CMSBATCH 109 94 2.05 86 76 .07 133 133 2048RTMSF 104 88 2.11 15 16 .05 66 99 3072ISPVM 78 0 .00 0 0 .00 0 0 2048VMUTIL 70 70 3.01 49 43 .00 0 0 2048DIRMAINT 61 58 2.02 51 38 .00 0 0 2048VMUSER2 61 61 1.99 0 0 .00 0 0 7168PV 60 58 2.83 0 0 .01 128 109 1024 . . . . . . . . . . . .OPERV 41 34 1.06 0 0 .00 0 0 1024ZVMBATC 39 0 .00 0 0 .00 0 0 2048TAPOPRVM 39 0 .00 0 0 .00 0 0 1024VMCH01 32 32 .00 0 0 .00 0 0 1024DISKACNT 28 26 .00 0 0 .00 0 0 512PVM 20 20 .00 1 0 .00 0 0 1024RSCS 14 17 .00 0 0 .00 0 0 2048VMCH06 9 9 .00 0 0 .00 0 0 1024OPERATOR 1 0 .00 1 0 .00 0 0 3072-------------------------------------------------------------------------------------------------------------- 444 435 83.25 363 372 .71 269 437 89621



7. The investigation is complete. There are six solutions to consider in attempting to decrease the paging load caused by the first four workloads on the Workload Storage Activity Report.1. Off-load a number of these workloads to other VM machines or to a time of day when

paging is less of a factor.2. Use the tuning commands that are supplied with your VM system. These commands are

usually VM release-dependent and have different effects on different systems. Use STOBUF to manage storage consumption by virtual machines.

3. Move the SPOOL area to a place where the paging overflow can be handled in a more efficient manner. This can be done by allocating more SPOOL space in areas with less contention. Occasionally, you may also want to reorganize the SPOOL files on the SPOOL system to prevent fragmentation using the IBM SPTAPE command.

4. Increase the sizes of the paging areas so that there is no overflow to the SPOOLing subsystem. The optimal size of the paging area depends on which release of VM you are running. The differences are due to the way the pages are allocated on the paging areas. A moving cursor is used to allocate pages.While setting paging area size, you may also want to locate your paging areas in areas of less contention (on separate devices, control units, or channel paths). Moving the paging areas to the center of the DASD device is usually an efficient way of configuring your paging subsystem.

5. Reduce the real memory being used by the virtual machines with the largest working set sizes.

6. Possibly the last solution to consider because of the expense involved, is to add more real memory or faster paging devices (such as, expanded storage, cache controllers).

Solving I/O Balancing Problems


Solving I/O Balancing ProblemsThe following procedure is an example of how you might resolve an I/O balancing problem.

1. A user group project manager calls the data center to report that response time is not meeting the service level agreement for his group. You consult your records and find that the agreement was for a trivial response time of two seconds for the hours of 6:00 AM to 6:00 PM.

2. Begin investigating the problem by looking at the Workload Transaction Activity Report to verify the user’s complaint, and to understand the nature of the problem. Insert the following command in a Reporter command file.

REPORT WTRA THISMONTH DAY(WEEKDAY) -

STIME(0610) ETIME(1800) CMB(1H)

The THISMONTH, DAY, STIME, and ETIME keywords generate a report spanning the hours of 6:00 AM to 6:00 PM for weekdays of the current month. The CMB keyword causes the Reporter to summarize the data into one-hour intervals. The output for each hourly interval prints on a separate page. Figure 16 is an example of the result.

FIGURE 16. The Workload Transaction Activity Report

The report in Figure 16 spans one of these hourly intervals and is typical of the other pages of this run of the report. It is clear that most CMS workloads have exceeded their response-time service level. Now that the complaint is verified, you are ready to investigate specific bottleneck areas.

3. The Workload Bottleneck Analysis Report highlights specific problem areas on a workload-by-workload basis. Insert the following two commands in a Reporter command file to generate a report for the past week.

SET LASTWEEK DAY(WEEKDAY) STIME(0610) ETIME(1800) CMB(1H)

REPORT WBOT

The SET command is a convenient way to set reporting parameters. The settings will stay in effect for subsequent REPORT commands in the same Reporter command file.

EPILOG FOR VM V610 PAGE 32RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/05/03 10:00 TO 10/05/03 11:00 COMBINE(1H) WORKLOAD TRANSACTION ACTIVITY REPORT WLVM VM --------TRIVIAL TRANSACTIONS-------- --------NON-TRIVIAL TRANSACTIONS------ WORKLOAD COUNT TRANS/SEC RESPONSE COUNT TRANS/SEC RESPONSE------<1>--------------------------------------------------------------------------------------------- TDOV10 10231 .543 1.932 426 .230 3.991 TDOV11 11102 .552 1.893 92 .134 4.021 TDOV02 8932 .562 1.043 29 .238 3.092 TDOV03 12012 .443 3.009 241 .128 4.032 TDNY11 11010 .442 2.004 208 .156 4.067 TDNY10 790 .442 3.011 1242 .231 3.991 TDOV11 12010 .432 2.123 92 .333 3.098 TDLA02 534 .402 2.041 29 .272 4.021 TDLA03 9010 .401 2.018 241 .267 4.282 . . . . . . . . . USER03 8910 .461 1.324 217 .228 4.023 USER01 40 .422 1.932 2242 .321 5.991 USER11 83 .502 1.210 92 .303 5.021 USER02 5431 .624 1.343 29 .332 4.091 VMCH01 310 .631 1.714 241 .066 4.281 VMCH11 3202 .499 2.104 1235 .338 4.067 VMCH10 234 .324 3.021 1242 .201 3.991 VMFL02 13021 .298 3.010 72 .264 4.892 VMFL03 9341 .356 2.043 39 .252 4.382 VMFL07 26320 .321 2.014 241 .247 3.678 VMFL08 310 .398 2.004 227 .238 4.067------------------------------------------------------------------------------------------------------ 986563 .421 2.064 49242 .245 4.291



The LASTWEEK, DAY, STIME, and ETIME keywords generate a report that spans the hours of 6:00 AM to 6:00 PM for the past week, Monday through Friday. The CMB keyword causes the Reporter to summarize the data into one-hour intervals. The output for each hourly interval prints on a separate page. Figure 17 is an example of the result.

FIGURE 17. The Workload Bottleneck Analysis Report

The report in Figure 17 spans only one of these hourly intervals. The report shows that the I/O subsystem is the cause of most of the workload wait time. In particular, device addresses 218 and 232 are the most frequent locations of I/O wait states.

4. Further investigation of minidisk activity on devices 218 and 232 is required to determine the cause of the problem. Insert the following two commands in a Reporter command file to request the Seek Analysis Report.

REPORT RSEE SELECTIF(DEVADDR(=218)) SELECTIF(DEVADDR(=232))

In addition to the parameters included in this command, use the parameters on the SET command in the previous step. Data must have been collected previously in order to run the three reports used so far to solve this data center problem. The Collector commands that cause this data to be collected can either be included in the Collector control file or can be issued dynamically through the SMSG interface. The instructions for controlling the Collector are found in the OMEGAMON and EPILOG for VM Installation and Customization Guide.

Figure 18 is an example of the result:

EPILOG FOR VM V610 PAGE 10RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/08/03 15:00 TO 10/08/03 15:59 COMBINE(1H) WORKLOAD BOTTLENECK ANALYSIS REPORT WLVM VM %CPU % % %SVM %PG %CF %SIM %CPU +-------------------I/O WAITS-----------------+ SAMPLEWORKLOAD BUSY OTHER IDLE WAIT WAIT WAIT WAIT WAIT |DEV % |DEV % |DEV % |DEV % |DEV % | COUNT-<1>-------------------------------------------------------------------------------------------------------VMAA19 2.1 .6 2.6 .0 .1 .0 .9 14.3 | 206 .4| 234 .4| 0 .0| 0 .0| 0 .0| 3305VMAA21 3.2 .1 3.1 .1 .3 .0 4.8 4.9 | 218 2.6| 232 1.1| 206 .0| 227 .0| 0 .0| 3305VMB303 .3 .3 5.0 .0 .0 2.0 .1 .1 | 218 1.1| 0 .0| 0 .0| 0 .0| 0 .0| 3305VMC201 .2 .2 4.1 .4 .2 .0 .0 .0 | 0 .0| 0 .0| 0 .0| 0 .0| 0 .0| 3305VMC102 4.3 .2 0.4 .0 1.7 76.1 .8 2.3 | 232 1.2| 227 .0| 0 .0| 0 .0| 0 .0| 3305 . . . . . . . . . . . .PROFS 3.2 .2 4.2 .0 1.2 .0 .0 .0 | 218 2.1| 0 .0| 0 .0| 0 .0| 0 .0| 3305SQL/DS 4.1 .1 .2 .0 .9 .2 17.0 25.0 | 232 4.2| 234 1.3| 218 .2| 206 .1| 217 .1| 3305VMCH27 2.1 .1 3.2 .0 .3 .0 .0 .0 | 0 .0| 0 .0| 0 .0| 0 .0| 0 .0| 3307VMFL29 .2 .2 1.2 .3 .2 2.1 .3 7.9 | 232 5.3| 218 3.1| 234 .0| 227 .0| 0 .0| 3307VMFL29A .1 .0 .1 .2 .3 3.3 .0 .0 | 227 .0| 0 .0| 0 .0| 0 .0| 0 .0| 3307VMFL33 1.1 .3 .5 1.2 .1 .0 8.6 13.3 | 232 3.6| 218 1.2| 217 .2| 206 .1| 21B .0| 3307VMFL33A .9 .2 .3 2.1 .0 .1 .2 17.0 | 218 1.1| 0 .0| 0 .0| 0 .0| 0 .0| 3307----------------------------------------------------------------------------------------------------------- 4.1 .1 3.9 .8 .5 13.6 3.8 5.5 32053



FIGURE 18. The Seek Analysis Report

The report in Figure 18 shows that most of the seek activity is in page and SPOOL areas and the SQL/DS database.

5. The investigation is complete. At this installation, the potential for I/O problems was not investigated during a recent conversion to a new release of VM that included a DASD upgrade. Minidisks were moved onto the new volumes without considering seek activity to the disks and within the disks.Some I/O balancing may be done across all eight volumes since the reports show that paging, SPOOLing, and the database do many more I/Os than other CMS users. Separate the SPOOLing extents and the paging extents so that they reside on separate volumes. The database contention on the second volume is probably being caused by contention with other minidisks on that volume. Either move the database or move the most utilized minidisk to less utilized DASD.

Balancing the I/O across available volumes should remove the bottlenecks and solve the response time problem.

.* -------------------------- PBMRSEE1 ---------------------------EPILOG FOR VM V610 PAGE 2RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/18/03 14:45 TO 10/18/03 15:00 COMBINE(15M) SEEK ANALYSIS REPORT WLVM DEVICE USERID VIRTUAL REAL DEVICE DASD EXTENT TOTAL SEEKS IN AVG MOVE AVG MOVEVOLSER ADDRESS ADDRESS TYPE EXTENT COUNT SEEKS EXTENT PER SEEK WITHIN EXTENT-------------------------------<1>----------------------------------------------------------------------------VM9 VMTEST 100 233 3380 300-539 240 93 83 23.3 23.3VM9 VMUTIL 191 233 3380 760-760 1 74 49 9.1 .0VM9 VMCH09 401 233 3380 1004-1007 4 103 63 8.0 .5VM9 VMFL07 401 233 3380 1008-1011 4 20 18 3.3 .3VM9 PAYROL1 191 233 3380 227-280 54 48 37 115.6 4.5 . . . . . . . . .VM9 VMUSER02 200 233 3380 50-99 50 101 82 6.2 2.9VM9 VMCH01 200 233 3380 140-169 30 25 21 4.4 1.3VM9 VMUSER01 200 233 3380 1050-1599 550 196 107 57.8 34.3VM9 VMFL03 100 233 3380 100-139 40 13 5 131.7 21.7-------------------------------------------------------------------------------------------------------------- 589 385 89.7 14.5


Solving Spooling Problems

Solving Spooling ProblemsThe following procedure is an example of how you might resolve a spooling problem.

1. Over the past few weeks, response time has been increasing. Yesterday, the SPOOLing subsystem shut down because of a lack of SPOOLing space. Before reconfiguring the system, you want to establish whether or not these two events are related. It is possible that adding more SPOOL space will have a further negative impact on response time.

2. Run the High-Level Summary Report for the past two weeks. Enter the following command in the Reporter command file. Figure 19 is an example of the result.

REPORT RHLS SDATE(-14) STIME(0900) ETIME(1700) CMB(1H)

FIGURE 19. The High-Level Summary Report

The report in Figure 19 shows three problem areas:

1. There is a high percentage (87%) of SPOOL space in use. This is not surprising, but now you know that the problem is consistent.

2. There is no paging space defined.3. There is a high page wait (54%).These facts indicate that your system is paging to temporary space (SPOOLing area), and that there is probably contention for this space. You need to examine the paging and SPOOLing subsystems more thoroughly.

3. Run the Paging Activity Report. Enter the following command in the Reporter command file. Figure 20 is an example of the result.

REPORT RPAG SDATE(-14) STIME(0900) ETIME(1700) CMB(1H)

EPILOG FOR VM V610 PAGE 1RUN DATE: SEPTEMBER 3, 2003 DATA PROCESSED: 08/20/03 09:00 TO 09/03/03 12:15 COMBINE(1H) HIGH LEVEL SUMMARY REPORT WLAVMXA PERFORMANCE INDICATOR MINIMUM AVERAGE MAXIMUM STANDARD DEVIATION OBSERVATIONS --------------------------------------------------------------------------------------------------------------RESOURCE AVAILABILITY INDEX .964 .991 .993 .003 116 % CPU BUSY 2.279 8.143 33.761 5.317 116 % VIRTUAL BUSY .730 3.789 17.207 3.106 116 % PROCESSOR 0 BUSY .500 3.093 12.250 2.268 116 % PROCESSOR 1 BUSY .000 3.566 21.750 3.286 116 TOTAL/VIRTUAL RATIO 1.790 2.822 7.566 1.068 116 TRIVIAL TRANSACTIONS / SEC .226 .266 .355 .032 116 NON-TRIVIAL TRANSACTIONS / SEC .002 .021 .059 .014 116 TRIVIAL TRANSACTION COUNT 226.000 952.991 1278.000 133.131 116 NON-TRIVIAL TRANSACTION COUNT 6.000 75.793 211.000 48.762 116 AVERAGE LOGGED ON USERS 30.000 31.432 33.000 .955 116 ACTIVE USERS 13.667 15.539 19.700 1.556 116 % VM I/O WAIT .000 .000 .000 .000 116 % VM PAGE WAIT .000 .000 .000 .000 116 I/O / SEC 3.427 11.540 62.152 10.618 116 PAGE I/OS / SEC .001 .390 17.404 2.124 116 % SPOOL SPACE IN USE 17.134 17.390 17.659 .149 116 % TEMP DISK SPACE IN USE .000 .554 .952 .463 116 % PAGING SPACE IN USE 6.185 10.801 19.544 3.796 116 % OF REAL STORAGE=SYSTEM FREE 25.562 25.975 26.944 .309 116 % OF REAL STORAGE=DPA 68.694 69.663 70.076 .309 116 % LOGICAL PROCESSOR BUSY 1.059 3.422 10.099 2.226 116 % PHYSICAL PROCESSOR BUSY .706 2.281 6.733 1.484 116



FIGURE 20. The Paging Activity Report

The report in Figure 20 represents one page of a 112-page report generated by this command. The output shows that there are only two paging extents, and both are temporary space.

4. Run the Spooling Activity Report. Enter the following command in the Reporter command file. Figure 21 is an example of the result.

REPORT RSPO SDATE(-14) STIME(0900) ETIME(17) CMB(1H)

FIGURE 21. The SPOOLing Activity Report

The report in Figure 21 represents one page of a 112-page report generated by this command. The output shows that both SPOOL areas are consistently over 90% full (ALLOCATION % FULL).

5. Run the DASD Activity Report. Enter the following command in the Reporter command file. Figure 22 is an example of the result.

REPORT RDAS SDATE(-14) STIME(0900) ETIME(1700) CMB(1H)

EPILOG FOR VM V610. PAGE 77RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/13/03 14:00 TO 10/13/03 15:00 COMBINE(1H) PAGING ACTIVITY REPORT WLVM PAGING DEVICE DASD DEVICE DASD EXTENT EXTENT I/O’S PERCENT SERVICE TYPE ADDRESS VOLSER TYPE EXTENT PERCENT FULL PER SECOND BUSY TIME (MS)--<1>------------<2>---------<3>------------------------------------------------------------------------------TEMP SPACE 232 VMHP07 3380 420-474 91 .68 2.77 40.84TEMP SPACE 217 VMHP08 3380 350-882 92 .37 .56 14.91-------------------------------------------------------------------------------------------------------------- 91.5 3.49 1.29 22.11

EPILOG FOR VM V610 PAGE 77RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/13/03 14:00 TO 10/13/03 15:00 COMBINE(1H) SPOOLING ACTIVITY REPORT WLVM DEVICE DASD DEVICE ALLOCATION ALLOCATION USED AVAILABLE ALLOCATION ADDRESS VOLSER TYPE RANGE COUNT SLOTS SLOTS % FULL-----<1>------------<2>-------------------------------------------------------------------------------------- 217 VMHP08 3380 350-882 533 73554 6396 92.00 232 VMHP07 3380 420-474 55 7508 742 91.01------------------------------------------------------------------------------------------------------------- 588 81062 7138 91.51



FIGURE 22. The DASD Activity Report

The report in Figure 22 represents one page of a 112-page report generated by the above command. The most useful information on this report is that the two devices, VMHP07 and VMHP08, have high I/O queue counts (QUEUE DEPTH) and that their service times (SERVICE TIME) are greater than 40 milliseconds. As queue depth and service time increase, response times increase for users using the SPOOLing subsystem.

6. The investigation is complete. The user installed the VM system from the express tape and expected a fairly tuned environment. This was not the case. You usually cannot run a VM express system.Create multiple paging areas and isolate them from the SPOOLing areas. This prevents short paging operations from contending with longer SPOOLing operations. The result is a reduced number of I/Os to the SPOOLing areas. This reduces device queuing and service time to any one device and provides better paging and SPOOLing operations. The result is better response time to the user.

EPILOG FOR VM V610 PAGE 77RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/13/03 14:00 TO 10/13/03 15:00 COMBINE(1H) DASD ACTIVITY REPORT WLVM DEVICE DASD DEVICE PERCENT QUEUE TOTAL I/O DEVICE I/O’S SERVICE CONTROL UNIT CHANNELADDRESS VOLSER TYPE BUSY DEPTH REQUESTS PER SECOND TIME (MS) BUSY BUSY--<1>-----<2>------------------------------------------------------------------------------------------------- 185 PROD17 3380 .02 .00 64 .03 .03 .03 .00 186 PROD06 3380 .11 .00 154 .13 .10 .03 .00 187 PROD13 3380 .09 .00 128 .11 .10 .03 .00 188 OMON21 3380 .02 .00 33 .02 .01 .03 .00 18B COM003 3380 .19 .00 123 .12 .09 .03 .00 18C MP310A 3380 .08 .00 96 .09 .04 .00 .00 18D PROD10 3380 .07 .00 77 .05 .01 .03 .00 18E PROD16 3380 .02 .00 14 .02 .00 .03 .00 18F PROD11 3380 .04 .00 42 .04 .02 .00 .00 190 PROD02 3380 .03 .00 24 .02 .01 .00 .00 191 SYSXX3 3380 .03 .00 21 .02 .01 .06 .00 192 HSM003 3380 .03 .00 20 .02 .01 .03 .00 193 SYSXX1 3380 .03 .00 19 .02 .01 .03 .00 210 WORKB1 3380 .00 .00 0 .00 .00 .00 .00 211 VM3 3380 .58 .00 2025 .56 10.39 .00 .00 . . . . . . . . . 215 SYSB24 3380 .00 .00 0 .00 .00 .00 .00 216 MT310A 3380 .00 .00 0 .00 .00 .00 .00 217 VMHP08 3380 18.65 3.37 2195 11.61 42.59 .04 .02 218 VM2 3380 1.26 .56 3643 3.01 12.46 .04 .02 219 SQL002 3380 .00 .00 0 .00 .00 .00 .00 21A OMON22 3380 .00 .00 0 .00 .00 .00 .00 21B VM4 3380 .12 .01 174 .05 25.45 .00 .00 220 PDB001 3380 .00 .00 0 .00 .00 .00 .00 221 EPIL01 3380 .00 .00 0 .00 .00 .00 .00 222 QM0001 3380 .00 .00 0 .00 .00 .00 .00 223 VM1 3380 .15 .00 943 .26 5.87 .00 .00 230 SYSB26 3380 .00 .00 0 .00 .00 .00 .00 231 PROD01 3380 .00 .00 0 .00 .00 .00 .00 232 VMHP07 3380 14.89 3.02 91434 12.90 46.87 .06 .01 233 VMHP02 3380 2.43 1.03 4727 4.31 18.50 .06 .01 234 VMHP04 3380 1.72 2.73 3810 2.06 16.27 .06 .01 235 MVSB21 3380 .00 .00 0 .00 .00 .00 .00 236 SYSB23 3380 .00 .00 0 .00 .00 .00 .00-------------------------------------------------------------------------------------------------------------- 1.13 .91 332730 9.09 14.61 .01 .00



Producing Batch Reports 47

Producing Batch Reports

This chapter shows you how to run the EVREPT EXEC, how to create a command file, and how to use the commands that define EPILOG reports.

Chapter ContentsEVREPT EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

EVREPT EXEC Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49EVREPT EXEC Command File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Running the EVREPT EXEC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Generating a Sample Report[l . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Generating a Customized Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Reporter Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Reporter Command Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Short and Long Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Delimiters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Continuation Character . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Wildcard Character. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Comment Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

REPORT and SET - Generating Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53EVSET Global . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Report name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54CLEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54DATEFORM or DATEF(MMDDYY|DDMMYY|YYMMDD). . . . . . . . . . . . . . . . . . 55Datename. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55STARTTIME/STIME(time) and ENDTIME/ETIME(time) . . . . . . . . . . . . . . . . . . . . 56BAND|RANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56COMBINE(nnnc)/CMB(nnnc) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57REPORTIF/RIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57SELECTIF/SIF or REPORTIF(element(relation value[units]), ...) . . . . . . . . . . . . . . 58

3


SYSTEMID/SYSID(cccccccc) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59GRAPH(type,element) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59MAXSCALE(nn units). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59SCAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60USERGROUP(name|name(list)) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60ACCTGROUP(name|name(list)) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60DISTGROUP(name|name(list)) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61IPREFIX(prefix) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62SORTBY(element(A|D),...). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62SUMMARY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63TITLEn(text) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63TIMEZONE/TMZ(+|-time) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63REPORT of DASD Activity Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64REPORT of DASD Activity with Date Range Override Example . . . . . . . . . . . . . . 64SET Command Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65SET CLEAR Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65SET Group Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65SET Group with REPORT Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

PRTCNTL - Controlling Printer Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66FOLDON|FOLDOFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66LINES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

PAGESEP - Formatting the Separator Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66BLOCK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67TITLE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67TITLE2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67TITLE3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67DUPLICATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

CP - Communicating with CP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68CMS - Communicating with CMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68PRODUCTS - Looking Up Your EPILOG Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69ZAPS - Looking Up Your EPILOG Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69END - Exiting From the Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69


EVREPT EXEC

EVREPT EXECThe EPILOG for VM Reporter produces batch reports based on data obtained by the OMEGAMON Collector. The EVREPT EXEC generates batch reports according to the commands that you enter in a command file.

EVREPT EXEC SyntaxThe syntax for invoking the EVREPT EXEC includes the file identifier for the EVREPT command file, which contains commands that you specified. The syntax is illustrated below.

Where:

Note: If, during installation, you used a user ID or minidisk address for the Epilog Datastore that is different from the one specified in the EVREPT EXEC, you must modify the EVREPT EXEC. The procedure to do this is detailed in OMEGAMON and EPILOG for VM Installation and Customization.

EVREPT EXEC Command FileThe EVREPT EXEC command file contains the report name and other optional keywords that define a report. The command file identifier must follow the standard VM naming convention (fn ft fm) where:

There are several sample command files on the product tape. All of these files have the default filetype of COMMAND. You can use XEDIT or any file editor to modify the sample command files or create your own. shows all Reporter commands that you can enter in the command file. Command explanations appear in later sections of this chapter in the same sequence as they appear in this table

fn Specifies the CMS filename of the command file. This is the only required parameter.

? Displays online assistance for the EVREPT EXEC.

ft Specifies the CMS filetype of the command file. The default is COMMAND.

fm Specifies the CMS filemode of the command file. The default is A.

PRINT|DISK Specifies the destination of Reporter output. Use PRINT to send output to the virtual printer; use DISK to send output to disk with filetype REPORT and filemode A. The default is PRINT.

DMODE x Specifies the filemode of the output if the DISK option is specified. The default is A.

fn Specifies any filename. This parameter is always required.

ft Specifies any filetype. The default is COMMAND.

fm Specifies the filemode of any accessed disk. The default is A.

Table 3. Listing of Reporter Commands

Command Description

REPORT Generates reports and graphs

SET Defines report parameters globally

EVREPT fn [ft fm (PRINT|DISK DMODE x)]

EVREPT EXEC


Running the EVREPT EXECRun the EVREPT EXEC from CMS mode using the syntax described in “EVREPT EXEC Syntax” on page 49. If you are a new EPILOG user, you may find it helpful to first use EVREPT with a sample command file.

Generating a Sample Report[l

To generate a sample report using a Candle-supplied command file, type EVREPT followed by the name of a sample command file, as follows:

EVREPT DASDREP

This example generates a DASD report for yesterday between 2:00 and 3:00 PM.

The command file used in the sample is DASDREP COMMAND A. Only the filename is required since filetype of COMMAND and filemode of A are the defaults. The filename is required.

A list of sample command file names and the titles of the reports they generate appear in Table 4.

The sample command files provided on the product tape can be modified for your installation.

PRTCNTL Controls print characteristics

PAGESEP Creates a separator page

CP Provides the CP interface

CMS Provides the CMS interface

PRODUCTS Displays expiration date and version number

ZAPS Displays product maintenance

END Stops the Reporter

Table 4. Sample Command Files

Sample Command File Report Name

GRPREP Group Definition Report

RCPUREP CPU Activity Report

DASDREP DASD Activity Report

PAGEREP Paging Activity Report

WCPUREP Workload CPU Report

WSTRREP Workload Storage Report

WSUMREP Workload Summary Report

REPORTS All reports

Table 3. Listing of Reporter Commands

Command Description


EVREPT EXEC

Generating a Customized Report

To print a customized report, follow these steps:

1. Edit the command file.A. Include the Reporter commands and parameters as they apply to your installation.

See “REPORT and SET - Generating Reports” on page 53 for REPORT command keywords.

B. (Optional) If you find you are using the same parameters for several reports, you can use the SET command to globally set parameters for all REPORT commands in a command file. See “REPORT and SET - Generating Reports” on page 53 for SET command keywords.

2. Execute the command file using the EVREPT EXEC as described in “EVREPT EXEC Syntax” on page 49.

You can change EVREPT parameters dynamically when executing the EVREPT EXEC, or you can modify the default parameters by editing the EVREPT EXEC and changing the parameters there.

Enter EVREPT ? to obtain complete online syntax information for the EVREPT EXEC.

Reporter Commands


Reporter CommandsYou can print reports and control their content by using Reporter commands and keywords. Each command has a valid set of keywords that you can generally enter in any order. Specific cases where entry order affects command execution are noted in the keyword descriptions.

Reporter Command ConventionsThe following topics describe some general rules for entering commands, keywords, and operands.

Short and Long FormsThe Reporter uses only the first 72 characters per line. All commands and keywords have both short and long forms. Commands and keywords differ, however, in that keywords have several acceptable abbreviations and commands have only one acceptable abbreviation. You can enter any unambiguous abbreviation for a keyword. For example, you can shorten the keyword FRIDAY down to FRIDA, FRI, or even F, and it will be recognized because no other keywords of that type begin with F. However, you must enter the REPORT command as either REPORT or REP; an alternate form such as REPO is unacceptable.

DelimitersKeywords are separated from other keywords and their operands by one or more blank spaces, equal signs, commas, or parentheses. If you use parentheses, they must be balanced. An input line may not begin with a right parenthesis. For consistency, use blank spaces to separate keywords and parentheses to separate operands.

Operands that contain blanks or other delimiters must be enclosed in single quotes. Two consecutive single quotes are treated as a single quote in the operand. Also, an operand enclosed in quotes may not be continued from one line to another.

Continuation CharacterTo continue a command line, end it with a hyphen (-) preceded by a blank space. You may use as many lines as necessary to enter the command. The Reporter does not execute the command until it encounters a line that does not contain a hyphen. You cannot use a continuation character in a quoted string.

Wildcard CharacterYou can use the asterisk (*) as a wildcard character in certain operands such as user IDs, device addresses, and volume serial numbers. Any single character found in the position of the asterisk meets the selection criteria. For example, the following command defines an account group called PAYROLL as consisting of any account that begins with 01 and has 6 and 9 in positions 4 and 5.

SET ACCTGROUP(PAYROLL(01*69))

An asterisk in the last position matches any number of characters. For example, the next command defines a user group called SYSPROG as consisting of any user ID that begins with SYS, regardless of length.

SET USERGROUP(SYSPROG(SYS*))

You can use the asterisk in the last position to specify a particular number of characters, one per asterisk (*), by enclosing the operand in quotes. For example, the next command defines a distribution group called NYC as consisting of any DISTGROUP beginning with VMNY that is 6 characters long because the string is in quotes.

SET DISTGROUP(NYC(‘VMNY**’))


Reporter Commands

Comment LinesTo include comment lines in the command file, place an asterisk (*) in column 1 of the line. If you leave text to the right of the hyphen (continuation character), that text is treated as a comment.

REPORT and SET - Generating ReportsUse the REPORT command to select the report that you want to print as well as the dates, times, interval combinations, and sort sequence for the report.

Use the SET command to set report parameters globally. The SET command applies to all the REPORT commands that follow it in the command file. The SET command’s global settings save you from repeatedly entering dates, times, and combine values when you know they will apply to several REPORT commands.

The syntax and keywords for the SET command are the same as for the REPORT command, except where specified otherwise in the remainder of this chapter. A notable difference between REPORT and SET keywords is the use of the USERGROUP, ACCTGROUP, and DISTGROUP keywords. On the SET command, these keywords define a reporting group. On the REPORT command, these keywords report on the group.

EVSET GlobalYou can include one or more SET commands in the command file preceding the REPORT command(s), or if you find that you have certain SET commands that apply to all your command files (such as TIMEZONE), you can create an EVSET GLOBAL file to contain those SET command(s). Any commands contained in EVSET GLOBAL are executed before the commands contained in the command file. Commands in the command file override commands in EVSET GLOBAL. EVSET GLOBAL can reside on any accessed disk; if multiple files exist, the first file found in the search order is used.

SyntaxThe syntax for the REPORT and SET commands follows.

FIGURE 23. REPORT and SET Command Syntax

REPORT {report name} <REPORT only>REP {short form}SET [CLEAR] <SET only> [DATEFORM(mmddyy)] <SET only> [Datename] [STARTDATE(Gregorian|Julian|Relative)] [ENDDATE(Gregorian|Julian|Relative)] [DAYOFWK(ALL|day-spec)] [STARTTIME(time)] [ENDTIME(time)] [BAND|RANGE] [COMBINE(nnnc)] [REPORTIF(element(relation value units), ...)] [SELECTIF(element(relation value units), ...)] [SYSTEMID(cccccccc)] [GRAPH(type element)] [MAXSCALE(value scale)] [SCAN] [USERGROUP(name|name(list))] [ACCTGROUP(name|name(list))] [DISTGROUP(name|name(list))] [IPREFIX(prefix)] [SORTBY(element(A|D), ...)] [SUMMARY] [TITLEn(text)] [TIMEZONE(+ time)]

Reporter Commands


Keywords

This section explains REPORT and SET keywords and keyword operands. Keywords that do not apply to both commands are marked accordingly.

Report name

Selects the report you want to print (REPORT command only). The report name keyword must be the first keyword to follow the REPORT command The valid short and long versions of the report name keywords and the reports they print are described in Table 5.

CLEAR

Resets all previously set parameters to their initial value (SET command only). The CLEAR keyword has no parameters.

Table 5. Report Name Keywords

Valid Report Names Report Title

RBOTA (RBOT) Bottleneck Analysis Report

RCHPID (RCHP) Channel Path Activity Report

RCPU CPU Activity Report

RDASD (RDAS) DASD Activity Report

REXP Expanded Storage Migration Report

RFREE (RFRE) Free Storage Activity Report

RHLS High-level Summary Report

RICOM (RICO) IUCV/VMCF Communications Activity Report

RLPAR (RLPR) LPAR Activity Report

RNSS Saved System/DCSS Report

RPAGE (RPAG) Paging Activity Report

RSCHSTOR (RSCH) Scheduler Storage Report

RSEEK (RSEE) Seek Analysis Report

RSPOOL (RSPO) SPOOLing Activity Report

RSTRMGMT (RSTR) Storage Management Report

RSYSINFO (RSYS) System Information Report

RTDISK (RTDI) Temporary Disk Report

RTRAN (RTRA) Transaction Analysis Report

RVDISK (RVDS) V-disk Activity Report

GROUPDEF (GRPD) Group Definition Report

WBOTA (WBOT) Workload Bottleneck Report

WCPU Workload CPU Report

WICOM (WICO) Workload IUCV/VMCF Communications Activity Report

WSTORAGE (WSTO) Workload Storage Report

WSUMMARY (WSUM) Workload Summary Report

WTRAN (WTRA) Workload Transaction Report


Reporter Commands

DATEFORM or DATEF(MMDDYY|DDMMYY|YYMMDD)

Tells the Reporter how to interpret start and end dates (SET command only). DATEFORM applies to absolute and relative dates. DATEFORM applies to the STARTDATE and ENDATE keywords as well as all date variables reported.

If DATEFORM and start or end dates are included in the same SET command, DATEFORM should precede the dates. If DATEFORM is not first, the previously defined DATEFORM applies.

Datename

A generic keyword that specifies the date range for which you want performance data reported. If you do not specify a date range, the Reporter selects all records in the datastore. You can enter date ranges in one of the following keywords.

TODAY THISWEEK THISMONTH THISYEAR YESTERDAY LASTWEEK LASTMONTH LASTYEAR

STARTDATE/SDATE(Gregorian|Julian|Relative) and ENDDATE/EDATE(Gregorian|Julian|Relative)

A keyword that specifies the date range for which you want performance data reported. If you do not specify a date range, the Reporter selects all records in the datastore. You can enter Gregorian, Julian, or relative date ranges.

Gregorian mmddyy

mm/dd/yy

mm/dd (assumes current year)

dd (assumes current month, year)

The Reporter interprets the Gregorian date according to the DATEFORM keyword of the SET command. If you use slashes with Gregorian dates, leading zeros are not required.

Reporter Commands


DAYOFWK/DAY(ALL|WEEKDAY|WKDAY|WEEKEND|WKEND|, MONDAY|TUESDAY|WEDNESDAY|THURSDAY|FRIDAY|SATURDAY|SUNDAY)

Displays data for only the days specified. ALL is the default.

STARTTIME/STIME(time) and ENDTIME/ETIME(time)

Enter the time range with the STARTTIME and ENDTIME keywords. You must enter the time in 24-hour clock format. For example, 1:00 PM is 1300. Enter time in any of the following formats:

hhhhmm or h:mmhhmm or hh:mmhhmmss or hh:mm:ss

If you use a colon with the time, leading zeros are not required. Valid values are:

You may also use relative start and end times by using a plus or minus sign before a value. For example, STARTTIME(-1:00) means a start time one hour earlier than the current hour.

BAND|RANGEDetermines how the Reporter interprets the time selections. BAND is the default. BAND reports data between the start time and end time for each day separately. RANGE reports all data from the start time and date straight through till the end time and date.

For example, the following REPORT command generates a report for Monday from 09:00 to 17:00, Tuesday from 09:00 to 17:00, . . ., and Friday from 09:00 to 17:00.

REPORT RDAS LASTWEEK DAYOFWK(WEEKDAY) -

STIME(09:00) ETIME(17:00) BAND

Julian yyddd

yy 00 - 99

ddd 1 - 366

Relative: You can specify start and end dates relative to the current date by placing a plus (+) or minus (-) sign before the values. For example, SDATE(-7) means start reporting from 7 days prior to the current date.

If you enter a relative date with only one numeric value such as SDATE(-7), then the report considers that value as days. If, however, you enter a relative date with two or more values such as SDATE (+3/-1), then the DATEFORM in control is used. For example, if you set DATEFORM (DD/MM/YY), the Reporter adds 3 days to the current date and subtracts 1 from the months. Therefore, if the current date is April 24, the relative date would be March 27. Valid values are:

Months 1 - 12Days 1 - 31Years 0 - 99

Hours 0-23

Minutes 0-59

Seconds 0-59


Reporter Commands

However, the following REPORT command generates a report starting on Monday at 09:00 and continuing straight through to Friday at 17:00.

REPORT RDAS LASTWEEK DAYOFWK(WEEKDAY) -

STIME(09:00) ETIME(17:00) RANGE

COMBINE(nnnc)/CMB(nnnc)

Combines recording intervals into reporting periods. For example, if the recording interval is 15 minutes and you specify CMB(1H), the Reporter groups data into 1-hour reporting periods and generates a page break for each reporting period.

Valid values for nnn are 1–999. COMBINE with no value or 0 defaults to the time range (STIME to ETIME) of the report if it is 24 hours or less. If the report time range is more than 24 hours, the combine period is 24 hours (00:00 to 24:00).

Note:

1. The COMBINE value must be equal to or a multiple of the recording interval when input is coming from the active datastore. The COMBINE value must be equal to or a multiple of the COMBINE value used on the ACCUM command if input is coming from condensed files. Valid values for c are:

2. The default for COMBINE is the recording interval. The recording interval is set with the OPTIONS control statement in the Collector control file. See OMEGAMON and EPILOG for VM Installation and Customization for more information.

3. The COMBINE keyword can help generate reports whose time ranges span midnight. To report on the graveyard shift and generate one line per shift, use a command similar to the one below, making the necessary adjustments to the time and date ranges.REPORT RCPU CMB

SDATE(10/01/91) EDATE(10/31/91) STIME(23) ETIME(07)

4. COMBINE generates a report break when it encounters a change in the contents of a character field of a record. This break overrides page breaks that are the result of combining reporting intervals. For this reason, you will want to use discretion when changing character fields such as DEVADDR, VOLSER, and SYSID.

5. The COMBINE keyword effects CPU percentages in WCPU and WSUM reports as follows:– If COMBINE is used, CPU percentages shown will be totals.

– If COMBINE is not used, CPU percentages shown will be averages.

REPORTIF/RIF

Selects records from the datastore after COMBINE is performed if a condition you specify is satisfied. Besides the timing of when the selection is made, there is no difference between the operation of the REPORTIF and SELECTIF keywords. All operands function in the same manner for the two keywords and are documented under SELECTIF.

C Calendar monthsD DaysH HoursM Minutes

Reporter Commands


An example of when REPORTIF should be used rather than SELECTIF is if you want to report on users who were logged on for more than 2 hours yesterday. If you use this sample command, no records are selected.

REPORT WSUM YDAY SELECTIF(SESSTIME(>=2H)) COMBINE(1D)

In the sample, the logon time for each record is checked before the COMBINE(1D) operation, and since the default recording time is 15 minutes, no records pass the test of 2 hours. If the REPORTIF command were used, records would be checked after the COMBINE(1D) operation, and records would exist with a combined log-on period of greater than 2 hours.

SELECTIF/SIF or REPORTIF(element(relation value[units]), ...)

Selects a record from the datastore before any COMBINEs are performed if a condition you specify is satisfied.

Multiple occurrences of SELECTIF/REPORTIF keywords are logically ORed. That is, if the following two SELECTIFs are issued, the records selected will be those users starting with the letter A and also those starting with the letter Z.

SELECTIF(WORKLOAD(=A*))

SELECTIF(WORKLOAD(=Z*))

If multiple conditions are specified on a single SELECTIF/REPORTIF keyword, the conditions are logically ANDed.

If a SELECTIF/REPORTIF condition is not satisfied, the record is not selected. If no data elements meet the SELECTIF/REPORTIF criteria, only Page 0 prints for the report. For information on Page 0, see “Page 0 Format” on page 74.

element Specifies a data element of a report. See “Data Dictionary” on page 201 for a list of valid data elements.

relation Specifies a relational operator. It can be:

>. greater than

< less than

= equal

>=, => greater than or equal

<=, =< less than or equal

<>, >< not equal

value Specifies a valid value for the element. Numeric values are assumed to be in the units associated with the element. For example, if the element is device service time, the assumed units are milliseconds. Therefore, a value of 10.3 would be 10.3 milliseconds.

units Overrides the assumed units of the element. If you do not enter units, the Reporter uses the assumed units for the element. Valid numeric units are:

H HoursM Minutes (for elements defined as time type)S SecondsMS MillisecondsK ThousandsM Millions (for elements defined as storage type)


Reporter Commands

If you defined a group by using the GROUP keyword on a COLLECT statement in the Collector control file, you can select that group to appear on a report with the SELECTIF/REPORTIF keyword. For example, if your Collector control file contained

COLLECT USERID(NY* NJ*) GROUP(EASTDEV)

your Reporter command file might contain

REPORT WBOT SELECTIF(WORKLOAD(=EASTDEV))

Refer to “Examples” on page 63 for examples of the SELECTIF command.

SYSTEMID/SYSID(cccccccc)

Selects records for a specific processor. A single datastore may contain data from several processors. If you do not specify a system ID, the Reporter uses data from all processors in the datastore that meets the other selection criteria.

GRAPH(type,element)

Produces a trend graph of one element (column heading) of a report.

GRAPH cannot be specified with SORTBY or SUMMARY.

MAXSCALE(nn units)Establishes the maximum Y-axis value for a graph.

There should be no space between nn and units. For example, MAXSCALE(70MS) represents 70 milliseconds.

If units are omitted, the Reporter defaults to the units associated with the element. For example, if the element is device service time, the assumed units are milliseconds. Therefore, a value of 10.3 would be 10.3 milliseconds.

type Can be one of the following:

VBAR Vertical bar graphLINE Line graph

element Specifies a data element of a report. Valid element names depend on the report chosen. If you choose an element name that is not valid for the report, the trend graph report is suppressed and an error message is delivered to the user log. The list of valid element names for each report is provided in “Data Dictionary” on page 201.

The specified element is graphed versus the day and time of day observed. Observations are defined by the COMBINE parameter and the date and time ranges specified. For example, if you choose COMBINE(1H) and a time range of 9:00 to 18:00, then 9 observations are graphed. If you choose a SDATE(-7), a BAND time range of 9:00 to 18:00 and a COMBINE(9H), you would get one observation per day for seven days.

nn Specifies a real number in the appropriate units of the chosen graph element.units valid units are:

H HoursM MinutesS SecondsMS MillisecondsK Thousands

Reporter Commands


If the graphed data element exceeds MAXSCALE, the data is truncated and shown with double plus (++) signs.

SCAN

If specified on a REPORT command, this keyword checks the syntax of the REPORT command. If a syntax error is found, an error message is put into the user log. The REPORT command will not execute while it contains the SCAN keyword; remove SCAN from the command when you determine that there are no syntax errors in the command.

If specified on a SET command, this keyword checks the syntax of all the commands that follow it in the command file. The commands in the command file do not execute. Place the SET SCAN command as the first statement in your command file to check the syntax of all the commands in the file. Remove SCAN when you determine that the file contains no more errors.

USERGROUP(name|name(list))

If specified on a REPORT command, this keyword reports on a group of virtual machines as a single workload. The following is the syntax for USERGROUP when it is used on a REPORT command:

USERGROUP(name)

If specified on a SET command, this keyword defines a group of virtual machines that can later be reported on as one workload. The asterisk (*) may be used as a wildcard character to define a user group. The defined user group can be used with the WCPU, WICO, WSTO, and WSUM reports only. You can enter multiple SET USERGROUP commands in a command file, but can later reference only one user group per REPORT command. Here is the syntax for USERGROUP when it is used on a SET command:

USERGROUP(name(list))

Notes:

1. The USERGROUP keyword can be used with the SET and REPORT commands only, and is not OBTAIN-able.

2. The USERGROUP keyword can be used only with the WCPU, WICO, WSTO, and WSUM workload reports.

3. See “SET Group Example” on page 65 for an example of USERGROUP keyword usage.

ACCTGROUP(name|name(list))

If used on a REPORT command, this keyword reports on a group of accounts as a single workload. You can reference only one account group per REPORT command. The

name Specifies a 1–8 character name you assigned to the group by using the USERGROUP keyword on the SET command.

name A 1–8 character name you assign to the group.

list The list of users that make up the user group. Each member of the list must be separated from other list members by a blank or a comma.


Reporter Commands

ACCTGROUP keyword may be used only with the WCPU, WICO, WSTO, and WSUM workload reports.

The following is the syntax for ACCTGROUP when used on a REPORT command:

ACCTGROUP(name)

If used on a SET command, this keyword defines a group of account codes that can be reported on as one workload. The defined account group can be used with the WCPU, WICO, WSTO, and WSUM reports only. You can enter multiple SET ACCTGROUP commands in a command file, but can reference only one account group per REPORT command. The asterisk (*) may be used as a wildcard character to define an account group. Here is the syntax for ACCTGROUP if used on a SET command:

ACCTGROUP(name(list))

Notes:

1. The ACCTGROUP keyword can be used with the SET and REPORT commands only, and is not OBTAIN-able.

2. The ACCTGROUP keyword can be used only with the WCPU, WICO, WSTO, and WSUM workload reports.

3. See “SET Group Example” on page 65 for an example of ACCTGROUP keyword usage.

DISTGROUP(name|name(list))

If specified on a REPORT command, this keyword, reports on a group of distribution codes as a single workload. You can reference only one distribution group per REPORT command. The DISTGROUP keyword can be used only with the WCPU, WICO, WSTO, and WSUM workload reports.

The following is the syntax for DISTGROUP when used on a REPORT command:

DISTGROUP(name)

If specified on a SET command, this keyword defines a group of distribution codes that are reported on as one workload. The defined distribution code may appear on the WCPU, WICO, WSTO, and WSUM reports only. You can enter multiple SET DISTGROUP commands in a command file, but can reference only one distribution group per REPORT command. The asterisk (*) may be used as a wildcard character to define a distribution group.

name Specifies a 1–8 character name you assigned to the group.


list The list of accounts that make up the account group. Each member of the list must be separated from other list members by a blank or a comma.

name Specifies a 1–8 character name you assigned to the group.

Reporter Commands


The following is the syntax for DISTGROUP when used on the SET command:

DISTGROUP(name(list))

Notes:

1. The DISTGROUP keyword can be used with the SET and REPORT commands only, and is not OBTAIN-able.

2. The DISTGROUP keyword can be used only with the WCPU, WICO, WSTO, and WSUM workload reports.

3. See “SET Group Example” on page 65 for an example of DISTGROUP keyword usage.

IPREFIX(prefix)

If specified on a REPORT command, this keyword specifies the first two characters of the filenames to be used as input to this report. If specified on a SET command, this keyword specifies the first two characters of the filenames to be used as input to all subsequent REPORT commands.

The default is EV, which indicates that input is coming from files in the active datastore.

SORTBY(element(A|D),...)

Sorts a report by one or more specified columns. An ascending sort sequence is the default. You may sort by as many sortable columns as appear on the report you are sorting. A number will appear at the top of the column indicating if it is the primary (1) or secondary (2) sort field.

SORTBY and GRAPH are mutually exclusive.


list The list of distribution codes that make up the distribution group. Each member of the list must be separated from other list members by any number of blanks or a comma.

prefix Specifies the first two characters of the input filenames. If not specified, EV is used, and input comes from files in the active datastore.

The prefix AC can be used to request that input come from condensed files generated by an ACCUM command that used the default OPREFIX value of AC. Other prefixes may be used if files were condensed and the default OPREFIX prefix of AC was overridden.

element Specifies a data element of a report. See “Data Dictionary” on page 201 for a list of valid data elements.

A|D ”A” indicates ascending sort sequence. “D” indicates descending sort sequence. The default is ascending. The data type (character, numeric, hexadecimal) is inferred from the element name.

... indicates that you may specify sort sequences for up to 25 elements with this keyword.


Reporter Commands

SUMMARYGenerates a report containing only the data that appears on the “Summary” lines of the detail report. The result is a report with one line per reporting interval. Each line includes the date and start time for the reporting interval. Static output fields from the detailed report such as Device Type, Device Address, DASD Volser, Virtual Address and Real Address do not appear on the report when run with the SUMMARY keyword.

This keyword cannot be used with the GRAPH keyword, which assumes a summarization is needed by default.

This keyword cannot be used with all reports. You can specify the SUMMARY keyword with the following report names only: RDAS, RNSS, RPAG, RSEE, RSPO, RTDI, WBOT, WCPU, WICO, WSTO, WSUM, and WTRA. If specified on other reports, the option is ignored.

TITLEn(text)Creates titles for a report. The variable n specifies the spacing of the title and can take on the values blank, 2, or 3. For example, TITLE results in a single-spaced title; TITLE2 results in a double-spaced title; and TITLE3 results in a triple-spaced title. The text can be up to 70 characters. You can use multiple TITLEn keywords. For each TITLEn keyword, the text appears centered on a new line. Titles with spaces must be enclosed by quotes.

All input is translated to upper case. Therefore, titles always appear in upper case on reports regardless of how you enter them in the command file.

TIMEZONE/TMZ(+|-time)Adjusts the STARTTIME and ENDTIME relative to the time of day (TOD) clock genned in your system. Use a plus or minus value to offset the difference between your time zone and the time set in your system’s time of day clock. For example, if the time of day clock is set to Greenwich Mean Time and you want to report on 9:00 AM to 5:00 PM Eastern Standard Time, use STARTTIME(9:00) ENDTIME(17:00) TIMEZONE(+5) to adjust for the 5 hour difference between Greenwich Mean Time and Eastern Standard Time. In this example, if you did not adjust for this difference, the report would be for 4:00 AM to 12:00 PM Eastern Standard Time. In general, this value should be set to the same value specified on the ZONE keyword in your SYSTEM DMKSYS or HCPSYS macro. Enter time in any of the following formats:

If you use a colon, leading zeros are not required. The valid values for time are:

ExamplesThis section contains examples of the use of the REPORT and SET commands.

h or hh

hmm or hhmm or h:mm or hh:mm

Hours 0-23

Minutes 0-59

Reporter Commands


REPORT of DASD Activity ExampleThe following example of the REPORT command produces a DASD Activity Report for all real devices.

REPORT RDASD SDATE(-7) DAYOFWK(WEEKDAY) STIME (9) -

ETIME (12) SORTBY(DASDBUSY(D))

One row appears for each device. The DAYOFWK keyword produces a report for each interval starting with the first weekday that is at most 7 days prior to the day the command is issued. If you executed the command in this example on a Saturday, the first reports would begin on the prior Monday starting at 9:00 AM. The rows on the report are sorted by Busy Percent in descending order.

FIGURE 24. Typical RDASD Report

The following example of the SET command changes the date range default for all report commands that follow it to weekdays starting at most seven days prior.

SET DATEFORM(DDMMYY) SDATE(-7) DAY(WEEKDAY) -

STIME(9) ETIME (12)

The time range is set at 9:00 AM to 12:00 PM. Dates on reports following this command are in the format DD/MM/YY.

REPORT of DASD Activity with Date Range Override Example

The following example of the REPORT command overrides the date range set in the previous example with absolute dates. The SET DATEFORM in the prior example causes the Reporter to interpret the date range in this example as October 6, 2003 to October 10, 2003. Since the SET time range is 9:00 AM to 12:00 PM, the 3-hour combine interval causes one DASD report per day averaged over the 3 hours.

REP RDAS SDATE(6/10/90) EDATE(10/10/90) CMB(3H)

The first report is for October 6, 2003 starting at 09:00 AM.

EPILOG For VM V610 PAGE 1RUN DATE: OCTOBER 18, 2003 DATA PROCESSED 10/06/03 09:00 TO 10/06/03 09:15 DASD ACTIVITY REPORT WLVM DEVICE DASD DEVICE PERCENT QUEUE TOTAL I/O DEVICE I/Os SERVICE ADDRESS VOLSER TYPE BUSY DEPTH REQUESTS PER SECOND TIME(MS)-----------------------------<1>----------------------------------------------- 341 VMUSR5 3380 4.35 .20 4192 4.66 9.23 342 VMUSR3 3380 3.20 .01 1499 1.67 19.23 343 VMUSR7 3380 1.95 .00 1423 1.58 12.30 344 VMUSR9 3380 1.37 .00 716 .80 17.26 360 VMUSR1 3380 1.03 .00 839 .93 11.05 381 VMUSR2 3350 .80 .00 267 .30 27.00 382 VMUSR4 3350 .69 .00 248 .28 24.91 383 VMUSR6 3350 .57 .00 274 .30 18.79 . . . . . . . . . . . . . . .


Reporter Commands

FIGURE 25. RDAS Report Using DATEFORM and COMBINE

SET Command Example

The following is an example using the SET command.

SET CLEAR

SET CLEAR Example

This example of SET CLEAR command resets all parameters to their initial state. The second two commands show how to define workload groups with the SET command and how to report on them with the REPORT command.

SET USERGROUP (VMERS(DEV*,SYSA11,SYSA19,MANG04)) -

ACCTGROUP(PAYROLL(01*69)) -

DISTGROUP(NYC(‘VMNY**’))

SET Group Example

This example of the SET command defines a USERGROUP called VMERS, an ACCTGROUP called PAYROLL, and a DISTGROUP called NYC. VMERS consists of all user IDs beginning with DEV as well as user IDs SYSA11, SYSA19, and MANG04. PAYROLL consists of user IDs with account codes that start with 01 and have 6 and 9 in the fourth and fifth position. NYC consists of user IDs with distribution codes that begin with VMNY and have any character in the fifth and sixth position. See “Wildcard Character” on page 52 for information on wildcard usage.

REP WSUM SDATE(-3) EDATE(-2) STIME(7:00) -

ETIME(18:00) CMB(1H) USERGROUP(VMERS)

SET Group with REPORT Example

Since the previous SET command defined a USERGROUP called VMERS, the above REPORT command produces a Workload Summary Report that groups data on all members of the USERGROUP under one VM workload called VMERS. shows the resulting report.

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 18,2003 DATA PROCESSED 10/6/03 09:00 TO 10/13/03 12:00 COMBINE(3H) DASD ACTIVITY REPORT WLVM DEVICE DASD DEVICE PERCENT QUEUE TOTAL I/O DEVICE I/Os SERVICE ADDRESS VOLSER TYPE BUSY DEPTH REQUESTS PER SECOND TIME(MS)------------------------------------------------------------------------------- 341 VMUSR5 3380 5.58 .01 4295 4.77 11.69 342 VMUSR3 3380 2.17 .00 2211 2.46 8.84 343 VMUSR4 3380 4.91 .00 3247 3.61 13.61 344 VMUSR9 3380 1.37 .00 716 .80 17.26 360 VMUSR1 3380 1.03 .00 839 .93 11.05 381 VMUSR2 3350 .80 .00 267 .30 27.00 382 VMUSR4 3350 .69 .00 248 .28 24.91 383 VMUSR6 3350 .57 .00 274 .30 18.79 . . . . . . . . . . . . . . .

Reporter Commands


FIGURE 26. Workload Summary Report

PRTCNTL - Controlling Printer OutputThe PRTCNTL command controls printout characteristics for reports and the user log.

Syntax

Use the following syntax when issuing the PRTCNTL command.

The following are explanations for using the PRTCNTL keywords.

FOLDON|FOLDOFF

Controls the translation of mixed case text. FOLDON causes all characters to be upper case. FOLDOFF leaves lowercase characters as lower case.

LINES

Allows up to nn lines to print on a single page. The minimum number of lines is 24, and the default is 60 lines.

Examples

The following are examples of the PRTCNTL command.

The command PRTCNTL LINES(50) FOLDOFF limits a page to 50 lines and prints mixed case letters.

The command PRTCNTL FOLDON allows subsequent reports to have only uppercase text again.

PAGESEP - Formatting the Separator PageThe PAGESEP command constructs a boxed separator page at the point that the command is read. Use PAGESEP to design user specific separator pages between reports. You may specify any number of TITLE and BLOCK keywords on a single PAGESEP command as long as the output fits on the page. The output sequence follows the input sequence exactly.

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 21, 2003 DATA PROCESSED 10/18/03 07:00 TO 10/19/03 08:00 COMBINE(1H) WORKLOAD SUMMARY REPORT WLAVMHP VM CPU Total I/O Page I/O WORKING SET SPOOL I/O WORKLOAD SESSIONWORKLOAD PERCENT COUNT COUNT SIZE(PAGES) COUNT PRIORITY TIME-----------------------------------------------------------------------------------VMERS 17.80 10364 1932 46 3007 64 1:00:00

PRTCNTL [FOLDON|FOLDOFF] [LINES(nn)]


Reporter Commands

Syntax

Use the following syntax when using the PAGESEP command.

Keywords

The following are descriptions for the PAGESEP keywords.

BLOCK

Formats character string in block letters centered on the page.

TITLE

Formats character string as a single-spaced, centered separator title.

TITLE2

Formats character string as a double-spaced, centered separator title.

TITLE3

Formats character string as a triple-spaced, centered separator title.

DUPLICATE

Specifies n separator pages should be produced in a row.

Note: If the title contains spaces, you must enclose the title in quotes.

Example

The following command causes System Administration, followed by TREND in block letters, followed by Reports to be printed on the separator page.

PAGESEP TITLE(‘System Administration’) BLOCK(trend) -

TITLE(Reports)

The above example of the PAGESEP command produces the separator page shown in Figure 27 .

PAGESEP [BLOCK(c1... c12)] [TITLE(‘c1... c70’)] [TITLE2(‘c1... c70’)] [TITLE3(‘c1... c70’)] [DUPLICATE(n)]

Reporter Commands


FIGURE 27. Sample Separator Page Produced by the PAGESEP Command

CP - Communicating with CPThe Reporter has a CP interface that allows you to issue CP commands during Reporter execution. Typically, you would use the CP SPOOL command to control printer parameters such as:® output class® number of copies® distribution code or user ID to receive output® RSCS/JES2 node name® form name

Syntax

Here is the format of the CP command:

CP cccccccc

Example

The following SPOOL command can be issued from within EPILOG.

CP SPOOL E COPY 2

CMS - Communicating with CMSThe Reporter has a CMS interface that allows you to issue any CMS subset command during Reporter execution.

Syntax

Use the following syntax to issue CMS commands from a Reporter command file.

ccccccc You may enter any CP command in the command file. (See example below.) For more information on the CP command, refer to the IBM CP Command Reference Manual.

* SYSTEM ADMINISTRATION ** ** ***** **** ***** * * *** ** * * * * ** * * * ** * * * * * * * * * ** * **** ***** * * * * * ** * * * * * * * * * ** * * * * * ** * * ** * * * ***** * * *** ** ** REPORTS **********************************************************************************

CMS cccccccc


Reporter Commands

Example

The following access command can be issued from a Reporter command file.

CMS ACCESS 111 Z

PRODUCTS - Looking Up Your EPILOG VersionThe PRODUCTS command shows the expiration date and version level of EPILOG. There are no operands with this command. PRODUCTS produces the output shown in Figure 28 . Note that the only product on the report is EPILOG for VM.

FIGURE 28. PRODUCTS Command Output

ZAPS - Looking Up Your EPILOG MaintenanceThe ZAPS command documents the maintenance (ZAPS) applied since you installed EPILOG. There are no operands with this command.

The format of output from the ZAPS command is:

END - Exiting From the ReporterThe END command terminates Reporter processing. There are no operands for the command. Use the END command anywhere before the end of a command file to terminate processing before the Reporter reaches the end of the command file. If the Reporter does not encounter an END command in the command file, processing continues until it reaches the end-of-file condition.

EPILOG FOR VM REPORT V610 10/06/03 09:08:00 Page 1 Copyright (C) 1987, 1988, 1989, 1990, 1991, 1995, 2002, 2003 CANDLE CORP. C U R R E N T P R O D U C T S ------------- --------------- EPILOG/VM VERSION 610

EPILOG FOR VM REPORT V610 10/06/03 09:08:00 Page 1Copyright (c) 1987, 1988, 1989, 1990, 1991, 1995, 2002, 2003 Candle Corp. ZAPS Applied: EVnnnRnn Version nn EVnnnRnn Version nn EVnnnRnn Version nn

EVnnnRnn Version nn version number of the associated ZAP ZAP number R for regular ZAP or S for special ZAP release number of product product identification code

Reporter Commands


Interpreting the Reports 71

Interpreting the Reports

This chapter gives explanations and examples of the Resource and Workload reports that you can print with EPILOG.

Chapter ContentsPreliminary Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Copyright Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Page 0 Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Generic Report Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Group Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77GRPD - Group Definition Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Resource Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79RBOT - Resource Bottleneck Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80RCHP - Resource Channel Path Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82RCPU - Resource CPU Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83RDAS - Resource DASD Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85REXP - Resource Expanded Storage Migration Report . . . . . . . . . . . . . . . . . . . . . . . . 87RFRE - Resource Free Storage Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89RHLS - Resource High–Level Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91RICO - Resource IUCV/VMCF Communications Activity Report. . . . . . . . . . . . . . . . . 96RLPR - Resource LPAR Activity Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99RNSS - Resource Saved Segment/NSS Activity Report . . . . . . . . . . . . . . . . . . . . . . . 102RPAG - Resource Paging Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104RSCH - Resource Scheduler Storage Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106RSEE - Resource Seek Analysis Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108RSPO - Resource SPOOLing Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110RSTR - Resource Storage Management Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112RSYS - Resource System Information Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115RTDI - Resource Temporary Disk Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 119RTRA - Resource Transaction Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121RVDS - Resource VDISK Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

4


Workload Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125WBOT - Workload Bottleneck Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125WCPU - Workload CPU Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128WICO - Workload IUCV/VMCF Communications Activity Report . . . . . . . . . . . . . . . 130WSTO - Workload Paging/Storage Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132WSUM - Workload Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Data Collection Requirements: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Sample Workload Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136WTRA - Workload Transaction Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

User Request Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Collector Keywords Needed for Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142


Preliminary Pages

Preliminary PagesThe following information is provided for each report:

® short and long names of the report

® purpose and uses of the report

® an example of typical report output

® column heading descriptions and release indicators

® a referral to the data dictionary table(s) for field name specifications you will need when using certain REPORT command options or when creating a data file to be used with other software packages

When examining examples of report output, keep the following facts in mind:

® Asterisks in a report field indicate that the number was too large to be displayed.

® If the last line of output on the report is a summary line, each data item on the summary line is an average, maximum, minimum, or total, depending on the nature of the data in that column. Values appearing in the main body of a report are often report-interval averages of sampling-interval data. Values appearing in the summary line of a report are recalculated from the original sampling-interval data. They are not calculated from the averages appearing in the columns above.

EPILOG produces resource reports, workload reports and trend graphs. For information on resource reports, see “Resource Reports” on page 79. For information on workload reports, see “Workload Reports” on page 125. For information on trend graphs, see “Generating Character Graphs from within EPILOG” on page 145.

Copyright PageA copyright page is printed each time EPILOG is invoked and tells you the percent full of the datastore. It precedes all reports and the user log. Figure 29shows a typical copyright page.

FIGURE 29. Typical Copyright Page

EPILOG FOR VM - !CANDLE CORPORATION COPYRIGHT 1987, 1995, 2002, 2003AN UNPUBLISHED WORK BY CANDLE CORPORATION. ALL RIGHTS RESERVED. USE PERMISSIBLE BY LICENSE ONLY. 05-000000-00000-00 . . EPILOG/VM VERSION 610 EPILOG ACTIVE DATASTORE IS 20 PERCENT FULL

Preliminary Pages


Page 0 FormatA report parameter page (Page 0) is printed each time the Reporter executes a REPORT command and is the first page of every report. The primary purpose of page 0 is to show you the SET and REPORT command parameters in effect at the time that you printed the report. Page 0 conveniently allows you to see the portion of the command file that controlled the report. Figure 30shows the layout of page 0.

FIGURE 30. Page 0 Layout

The boxes in this figure show variable data. The variable data items are:

user TITLE The title that you entered with either the TITLE, TITLE2, or TITLE3 keyword.

date The date the report was printed.

subsequent TITLEs The title that you entered with either the TITLE, TITLE2, or TITLE3 keyword.

report name The Candle name of the report.

name The Candle name of the report.

REPORT command options & SET options

Selection options expressed in the REPORT or SET command. These include items such as STARTTIME, ENDTIME, COMBINE, and SELECTIF.

report defaults The options and their values which come from the report defaults.

group name When applicable, the name you defined for either a user group, account group, or distribution group.

EPILOG for VM V610

RUN DATE: date

user TITLE Page 0

subsequent TITLEs

REPORT name OPTIONS:

report name REPORT OPTIONS LOG

REPORT command options & SET options

DEFAULT:

SELECTED:

report defaults

group name


Preliminary Pages

Generic Report LayoutEach report has its own data elements and column headers. However, all reports follow the general layout shown in Figure 31.

The number of pages per report is a function of the number of intervals covered by the date and time range and the type of report itself. The number of intervals may be controlled by the COMBINE keyword.

FIGURE 31. Generic Report Layout

The boxes in Figure 31 represent variable data. The variable items are:

user TITLE A title you entered with either the TITLE, TITLE2, or TITLE3 keyword.

# The sequential page number of the report.

subsequent TITLEs A title you entered with either the TITLE, TITLE2, or TITLE3 keyword.

date Run Date is the date the report was printed. Data Processed are the actual dates the data was processed. The format of these dates is controlled by the DATEFORM keyword.

EPILOG for VM V610

Run Date: date

Page #user TITLE

subsequent TITLEs

Data Processed: date time To date time COMBINE

report name SYSTEMID( )

column headers

sort order line

row of data

row of data

summary line

Preliminary Pages


date time The time of the first record processed and the time of the last record processed.

COMBINE() The COMBINE value used, if any.

report name The name of the report.

SYSTEMID() The system ID used, if any.

column headers The column headings that describe the data.

sort order line A dotted line showing the numbered sort orders as specified by the SORTBY keyword. The first column sorted contains <1>, the second column sorted contains <2>, and so on.

row of data A row of data elements. For reports that are sorted by date and time, there is one row per combine period.

summary line A row of values summarizing the output for a report period. Values are recalculated from original sampling data. They can be averages, totals, maximums, or minimums as is appropriate for the data in the columns above.


Group Report

Group Report

GRPD - Group Definition Report

Purpose:

The Group Definition Report shows how virtual machines have been grouped for data collection. Virtual machines may be grouped by user IDs, account codes, or distribution codes.

The COMBINE keyword does not apply to this report. If included, EPILOG will ignore it and continue processing. This report is available in all VM environments.

Uses:

Use this report to see how the Collector is grouping virtual machines, which may be grouped by user IDs, account codes, or distribution codes, and are defined in the Collector control file.

Virtual machines are grouped to decrease the space requirements needed to store collection data, or to group virtual machines with similar workload characteristics. For example, if you knew all your PROFS users had an account code of 8765, you could group them together.

Data Collection Requirements:

Collect appropriate data for this report. Table 33 on page 142 contains the keyword(s) required on the COLLECT statement in the Collector control file in order to produce each report.

FIGURE 32. Sample Group Definition Report

Short Name: GRPD

Long Name: GROUPDEF

EPILOG FOR VM V610 PAGE 1 RUN DATE: OCTOBER 13, 2003 DATA PROCESSED: 10/08/03 21:07 TO 10/13/03 10:00 GROUP DEFINITION REPORT WLAVMHP DATE TIME GROUP NAME TYPE OF GROUPING GROUP ENTITIES ---------------------------<1>----------------------------------------------------------- 01/08/03 09:47 INFOCTR USERID INFO**** 01/08/03 09:47 OVERHEAD USERID DIR***** OPERAT** PVM***** RSCS**** SYS***** VM****** 01/08/03 09:47 PROFS1 USERID PROFS1** 01/08/03 09:47 PROFS2 USERID PROFS2** 01/08/03 09:47 PROFS3 USERID PROFS3** 01/08/03 09:47 PROFS4 BOTTLENECK PROFS4** 01/08/03 09:47 PROFS5 USERID PROFS5** 01/09/03 11:25 DEV ACCTCODE DEV***** 01/09/03 11:25 NYC DISTCODE NYC***** 01/12/03 09:05 PAYROLL USERID VMPAY1 VMPAY2 VMPAY3

Group Report


Table 6. GRPD - Group Definition Report

Columm Header

Field Name Unit Field Length

Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

Interval Start Date Time

DATETIME STCK 08 CHAR Date and time when Collector started recording data for the group.

Group Name GRPNAME 08 CHAR Y Name of group specified in the Collector control file.

Type Of Grouping

GRPTYPE INTG 12 CHAR Y Shows how a workload is grouped. Types of groups are: user ID, account code, distribution code, or bottleneck.

Group Entities RANGE1 08 CHAR The first designation for the user IDs, account codes, or distribution codes that make up the group.

SYSID 08 CHAR Y System ID for entire report appears in upper right portion of report heading.


Resource Reports

Resource ReportsResource reports provide performance information on a particular real system device. A list of the resource reports follows:

“RBOT - Resource Bottleneck Analysis Report” on page 80

“RCHP - Resource Channel Path Activity Report” on page 82

“RCPU - Resource CPU Activity Report” on page 83

“RDAS - Resource DASD Activity Report” on page 85

“REXP - Resource Expanded Storage Migration Report” on page 87

“RFRE - Resource Free Storage Activity Report” on page 89

“RHLS - Resource High–Level Summary Report” on page 91

“RICO - Resource IUCV/VMCF Communications Activity Report” on page 96

“RLPR - Resource LPAR Activity Report” on page 99

“RNSS - Resource Saved Segment/NSS Activity Report” on page 102

“RPAG - Resource Paging Activity Report” on page 104

“RSCH - Resource Scheduler Storage Report” on page 106

“RSEE - Resource Seek Analysis Report” on page 108

“RSPO - Resource SPOOLing Activity Report” on page 110

“RSTR - Resource Storage Management Report” on page 112

“RSYS - Resource System Information Report” on page 115

“RTDI - Resource Temporary Disk Activity Report” on page 119

“RTRA - Resource Transaction Activity Report” on page 121

“RVDS - Resource VDISK Activity Report” on page 123

Resource Reports


RBOT - Resource Bottleneck Analysis Report

Purpose:

The Bottleneck Analysis Report provides information regarding users in a wait state on the dispatch list during the reporting period.

This information includes the percentage of users that fall into each of seven wait-state conditions; the percentage of users using the CPU; and the percentage that fall into the other state. The other state occurs when a user is in the dispatch list but no wait state condition has been flagged in the VMDBK. (There is one VMDBK for each uniprocessor user ID in the system.)

Uses:

This report points at the types of waits the system is encountering. It will help you determine which resources need to be tuned in order to provide better service.


Appropriate data must be collected as input to this report. Table 33 on page 142 contains the keyword(s) required on the COLLECT statement in the Collector control file in order to produce each report.

FIGURE 33. Sample Bottleneck Analysis Report

Short Name: RBOT

Long Name: RBOTA

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 22, 2003 DATA PROCESSED: 10/17/03 09:00 TO 10/17/03 17:00 BOTTLENECK ANALYSIS REPORT WLAVM01 --INTERVAL START-- % % IDLE % I/O % PAGE % CF % SIM % CPU % USING % SAMPLE DATE TIME IDLE SVM WAIT WAIT WAIT WAIT WAIT WAIT CPU OTHER COUNT----<1>----------------------------------------------------------------------------------------------- 10/17/03 09:00 .0 .0 25.0 .0 .0 .0 25.0 .0 50.0 4 10/17/03 09:15 25.0 .0 25.0 .0 .0 .0 25.0 .0 25.0 4 10/17/03 09:30 .0 .0 33.3 .0 .0 33.3 .0 .0 33.3 3 10/17/03 09:45 20.0 .0 20.0 .0 .0 .0 20.0 .0 20.0 5 10/17/03 10:00 20.0 .0 20.0 .0 .0 .0 40.0 .0 20.0 5 10/17/03 10:15 .0 .0 33.3 .0 .0 .0 33.3 .0 33.3 3 10/17/03 10:30 14.3 .0 14.3 .0 .0 .0 57.1 .0 14.3 7 10/17/03 10:45 16.7 .0 .0 .0 .0 16.7 50.0 .0 16.7 6 10/17/03 11:00 .0 .0 25.0 .0 .0 25.0 25.0 .0 25.0 4 10/17/03 11:15 50.0 .0 16.7 .0 .0 .0 16.7 .0 16.7 6 10/17/03 11:30 20.0 .0 20.0 .0 .0 20.0 20.0 .0 20.0 5 10/17/03 11:45 14.3 .0 14.3 .0 .0 28.6 28.6 .0 14.3 7 10/17/03 12:00 .0 .0 25.0 .0 .0 .0 25.0 .0 50.0 4 10/17/03 12:15 25.0 .0 25.0 .0 .0 .0 .0 .0 50.0 4 10/17/03 12:30 33.3 .0 16.7 .0 .0 .0 16.7 .0 33.3 6 10/17/03 12:45 57.1 .0 14.3 .0 .0 .0 14.3 .0 14.3 7 10/17/03 13:00 57.1 .0 14.3 .0 .0 .0 .0 .0 28.6 7 10/17/03 13:15 33.3 .0 16.7 .0 .0 .0 33.3 .0 16.7 6 10/17/03 13:30 40.0 .0 20.0 .0 .0 .0 20.0 .0 20.0 5 10/17/03 13:45 16.7 .0 33.3 33.3 .0 .0 .0 .0 16.7 6 10/17/03 14:00 28.6 .0 14.3 .0 .0 .0 42.9 .0 14.3 7 10/17/03 14:15 16.7 .0 .0 .0 .0 16.7 50.0 .0 16.7 6 10/17/03 14:30 20.0 .0 20.0 .0 .0 .0 40.0 .0 20.0 5 10/17/03 14:45 25.0 .0 25.0 .0 .0 .0 25.0 .0 25.0 4 10/17/03 15:00 50.0 .0 12.5 .0 .0 .0 25.0 .0 12.5 8 10/17/03 15:15 50.0 .0 16.7 .0 .0 .0 33.3 .0 .0 6 10/17/03 15:30 40.0 .0 20.0 .0 .0 .0 20.0 .0 20.0 5 10/17/03 15:45 16.7 .0 16.7 .0 .0 16.7 16.7 .0 33.3 6 10/17/03 16:00 42.9 .0 14.3 14.3 .0 .0 14.3 .0 14.3 7 10/17/03 16:15 50.0 .0 16.7 .0 .0 .0 16.7 .0 16.7 6 10/17/03 16:30 .0 .0 16.7 .0 .0 .0 66.7 .0 16.7 6 10/17/03 16:45 20.0 .0 40.0 .0 .0 .0 20.0 .0 20.0 5 ---------------------------------------------------------------------------------------------------- 28.0 .0 18.3 1.7 .0 4.6 26.3 .0 21.1 175


Resource Reports

Table 7. RBOT - Resource Bottleneck Analysis Report

Columm Header


Data Type

KeywordsDescription

SO

RT

GR

AP

H

RIF

/SIF




Sample Count

SYSSMPL INTG 04 UBIN Y Y The number of samplings recorded by the Collector during the reporting period.

% Using CPU

USEDCPUP 08 FLTD Y Y Y The percentage of virtual machines using the CPU.

% CF Wait WAITCFSP 08 FLTD Y Y Y The percentage of virtual machines in the dispatch list found to be in a console function simulation wait state.

% CPU Wait WAITCPUP 08 FLTD Y Y Y The percentage of virtual machines in the dispatch list found to be in a CPU wait state.

% Idle WAITIDLP 08 FLTD Y Y Y The percentage of virtual machines in the dispatch list found to be in an idle wait state.

% Idle SVM Wait

WAITIDSP 08 FLTD Y Y Y The percentage of virtual machines in the dispatch list found to be in a service virtual machine wait state.

% I/O Wait WAITIOP 08 FLTD Y Y Y The percentage of virtual machines found to be in an I/O wait state.

% Other WAITOTHP 08 FLTD Y Y Y The percentage of virtual machines in the dispatch list not found in any of the above wait states.

% Page Wait WAITPAGP 08 FLTD Y Y Y The percentage of virtual machines in a wait state found to be in a page wait state.

% Sim Wait WAITSIMP 08 FLTD Y Y Y The percentage of virtual machines in the dispatch list found to be in an instruction simulation wait state.

Resource Reports


RCHP - Resource Channel Path Activity Report

Purpose:

The Channel Path Activity Report displays channel information for the entire system for the recording interval. The information includes the channel path ID number and the percent busy for the path during the recording period.

Uses:

Use this report to help balance devices along the various channel paths. The busiest channel paths will appear at the top of the report. To examine the busiest channel paths, use the following keyword options on the REPORT RCHP command: SORTBY(CHPBUSYP(D)



FIGURE 34. Sample Channel Path Activity Report

Short Name: RCHP

Long Name: RCHPID

Table 8. RCHP - Resource Channel Path Activity Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

% CHP Busy CHPBUSYP 08 FLTD Y Y The percentage of time that this channel path was in use during the reporting interval.

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 27, 2003 DATA PROCESSED: 10/26/03 00:00 TO 10/26/03 00:15 CHANNEL PATH ACTIVITY REPORT WLAVM01 -INTERVAL START- SAMPLE CHANNEL %CHP CHANNEL %CHP CHANNEL %CHP CHANNEL %CHP DATE TIME COUNT PATH ID BUSY PATH ID BUSY PATH ID BUSY PATH ID BUSY------------------------------------------------------------------------------------------------------10/26/03 00:00 180 00 .00 10 3.33 20 .00 30 .00 01 12.22 11 11.11 21 .00 31 .00 02 3.33 12 5.00 22 .00 32 .00 03 8.89 13 .00 23 .00 33 .00 04 3.33 14 1.67 24 .00 34 .00 05 .00 15 3.33 25 .00 35 .00 06 6.67 16 3.33 26 .00 36 .00 07 6.67 17 .00 27 .00 37 .00 08 .00 18 .00 28 .00 38 .00 09 .00 19 .00 29 .00 39 .00 0A .00 1A .00 2A .00 3A .00 0B .00 1B .00 2B .00 3B .00 0C .00 1C .00 2C .00 3C .00 0D .00 1D .00 2D .00 3D .00 0E .00 1E .00 2E .00 3E .00 0F .00 1F .00 2F .00 3F .00


Resource Reports

RCPU - Resource CPU Activity Report

Purpose:

The CPU Activity Report helps identify changes in CPU resources and actual CPU consumption over a specified time frame.

Uses:

Logged, active, and max users along with CPU% help you plan for additional workloads.

The queue counts help you determine what types of workload you are running on the system.

The Total/Virt Ratio shows the amount of processor overhead used by CP. As the Total/Virt Ratio goes up, the ratio of CP (overhead) work to virtual machine work increases. Keep the Total/Virt Ratio number as low as possible.



FIGURE 35. Sample CPU Activity Report

Channel Path ID

CHPID ADDR 02 SUBI Y The channel path identification number.


DATETIME STCK 08 CHAR The starting date and time for this reporting interval.


Short Name: RCPU

Long Name: RCPU


EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 17, 2003 DATA PROCESSED: 10/11/03 12:21 TO 10/12/03 03:25 COMBINE (1H) CPU ACTIVITY REPORT WLAVM01 -INTERVAL START- # CPU CP VIRT TOTAL/VIRT USERS USERS IN --LOGGED ON-- ACTIVE DIALED -LPAR UTILIZATION- DATE TIME CPUS % % % RATIO IN QUEUE ELIGIBLE AVG MAX USERS USERS LOGICAL PHYSICAL-<1>--------------------------------------------------------------------------------------------------------------10/11/03 12:21 2 30 23 7 4.116 5 0 39 40 13 0 9.26 6.1710/11/03 13:00 2 31 23 7 4.191 5 0 40 41 13 0 8.91 5.9410/11/03 14:00 2 30 22 7 4.184 5 0 39 40 13 0 9.04 6.0310/11/03 15:00 2 32 24 8 4.208 5 0 37 38 11 0 9.08 6.0510/11/03 16:00 2 15 11 4 3.898 3 0 36 37 11 0 3.96 2.6410/11/03 17.00 2 11 8 3 3.701 3 0 36 36 11 0 2.62 1.7510/11/03 18:00 2 11 8 3 3.560 3 0 36 36 11 0 2.69 1.7910/11/03 19:00 2 11 8 3 3.743 3 0 36 36 11 0 2.67 1.7810/11/03 20:00 2 11 8 3 3.695 2 0 36 36 11 0 2.71 1.8010/11/03 21:00 2 11 8 3 3.641 3 0 36 36 11 0 2.65 1.7710/11/03 22:00 2 10 7 3 3.668 3 0 35 36 11 0 2.47 1.6510/11/03 23:00 2 13 9 4 2.984 3 0 35 36 11 0 3.54 2.3610/12/03 00:00 2 10 7 3 3.742 2 0 36 36 11 0 2.48 1.65 ----------------------------------------------------------------------------------------------------------------- 2 17 13 3 3.876 3 0 36 41 12 0 4.29 2.86

Resource Reports


Table 9. RCPU - Resource CPU Activity Report

Columm Header


Data Type

Keywords Description

SO

RT

GR

AP

H

RIF

/SIF

Active Users ACTUSER 08 FLTD Y Y Y Number of users who had any activity since the last sampling interval.

Logged On Avg AVGUSER 08 FLTD Y Y Y Average number of users logged on.

CP % CPBUSY 08 FLTD Y Y Y Percentage of CPU utilized by CP.

CPU % CPUBUSY 08 FLTD Y Y Y Total CPU utilization (CP and virtual combined). If you are running multiple processors, this value is the sum of CPU utilization for all processors and can be greater than 100%.

# CPUs CPUNUM 08 FLTD Y Y Number of active processors.


DATETIME STCK 08 CHAR Time of day at start of reporting interval.

Dialed Users DIALUSER 08 FLTD Y Y Y Number of users who are dialed to VM.

Users in Eligible

ELIGUSER 08 FLTD Y Y Y Average number of users waiting in the eligible list.

LPAR Utilization Logical

LPARBUSY 08 FLTD Y Y Y Percentage of time this LPAR was busy based on the number of available logical processors.

Logged On Max

MAXUSER INTG 08 FLTD Y Y Y Maximum number of users logged on during reporting interval.

LPAR Utilization Physical

PHYSBUSY 08 FLTD Y Percentage of time this LPAR was busy based on the number of physical processors in the system.

SYSID 08 CHAR Y Y Y System ID for entire report appears in upper right portion of report heading.


Resource Reports

RDAS - Resource DASD Activity Report

Purpose:

The DASD Activity Report shows you information about activity on Direct Access Storage Devices. For DASD dedicated to V=R or V=F guests, only DASD activity intercepted by CP is shown. If all dedicated DASD activity is wanted for a V=R or V=F guest, you must run a performance monitor on that guest.

To obtain information for a channel-path environment, run the Channel Path Activity Report (RCHP).

Uses:

This report helps you balance DASD loads across your system. This report can also help determine if an I/O performance problem is caused by a DASD device, a control unit, or a channel. By comparing the QUEUE DEPTH, the CONTROL UNIT BUSY, and the CHANNEL BUSY, you can quickly locate the bottleneck.

The service time components of pending time, connect time, and disconnect time are shown. This information allows Performance Analysts to gain a better understanding of DASD performance (to look for trends and potential problems, or as an additional tool in analyzing through-put problems).

Note: CP uses suspend-resume channel programming to CP-owned volumes. I/O counts are not incremented when a resume sub-channel instruction is issued to the device. As a result, I/O counts will appear to be lower than expected, especially when compared to Percent Busy.



Total/Virt Ratio TVRATIO 08 FLTD Y Y Y Ratio of total CPU time to virtual CPU time.

Users in Queue USERQ 08 FLTD Y Y Y Average number of users waiting in queue to be dispatched.

Virtual % VIRTBUSY 08 FLTD Y Y Y Virtual CPU percent. Amount of CPU utilized by virtual machines in real problem state.

Short Name: RDAS

Long Name: RDASD

Table 9. RCPU - Resource CPU Activity Report (continued)

Resource Reports


FIGURE 36. Sample DASD Activity Report

Note: Use of SELECTIF or REPORTIF keywords of the REPORT or SET commands include the selection of four-digit device addressees. This could affect the output of the RDAS report.

Table 10. RDAS - Resource DASD Activity Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

Connect Time CONNTIME MSEC 08 FLTD Y Y Y Average time this device was in CONNECT state during the reporting interval.

Percent Busy DASDBUSY INTG 08 FLTD Y Y Y Percentage of time the device was found busy.

Queue Depth DASDQUE INTG 08 FLTD Y Y Y Average number of I/Os queued on the device.

Total I/O Requests

DASIOREQ INTG 08 FLTD Y Y Y Number of I/Os started on this device.


DATETIME STCK 08 CHAR Y Y Date and time when Collector started recording data for the device.

Device Address DEVADDR ADDR 02 SUBI Y Y Y Real address of device.

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 17, 2003 DATA PROCESSED: 10/17/03 12:00 TO 10/17/03 12:06 DASD ACTIVITY REPORT WLAVM01 DEVICE DASD DEVICE PERCENT QUEUE TOTAL I/O DEVICE I/O’S SERVICE PENDING CONNECT DISCONNECTADDRESS VOLSER TYPE BUSY DEPTH REQUESTS PER SECOND TIME (MS) TIME (MS) TIME (MS) TIME (MS)---<1>----<2>-------------------------------------------------------------------------------------------- 146 CAN002 3380 .12 .00 18 .06 19.33 78 14.78 3.78 151 OMON28 3380 .04 .00 9 .03 14.89 .67 1.44 12.78 161 RES 3390 .12 .00 23 .05 22.74 1.13 3.96 17.65 164 CAN001 3390 .36 .00 30 .10 35.80 .47 22.67 12.67 168 TSO001 3390 .24 .00 36 .12 19.72 5.06 3.06 11.61 169 TSO002 3390 .48 .00 130 .43 11.11 2.09 3.17 5.85 172 TSO006 3390 .07 .00 16 .05 12.87 .56 2.19 10.12 307 VM1 3380 .10 .00 8 .03 36.62 .37 3.87 32.37 313 VM4 3380 .05 .00 6 .02 27.33 .33 4.33 22.67 317 VM2 3380 24.75 .00 3059 7.31 33.86 .51 14.08 19.26 31A OMON25 3380 1.46 .00 284 .95 15.41 .48 4.67 10.27 337 CAN004 3380 .16 .00 28 .09 16.68 1.36 13.57 1.75 9C1 MP223D 3380 2.95 .00 355 1.18 24.94 1.55 10.41 12.99 9C3 MVSD21 3380 45.72 .00 7305 17.46 26.19 .51 4.70 20.98 9C4 OMSTG1 3380 2.62 .00 296 .99 26.58 .40 12.17 14.01 9C8 SV0002 3380 .11 .00 10 .03 34.00 2.90 1.90 29.20 9D0 VM9 3380 .10 .00 6 .02 47.83 3.33 8.17 36.33 D80 PAGE01 3375 2.11 .00 162 .54 39.10 .31 15.66 23.12 D82 VM0 3375 .07 .00 4 .01 50.25 5.50 22.25 22.50 D8A VM1 3375 .01 .00 1 .00 40.00 .00 2.00 38.00 D8B VM7 3375 .18 .00 42 .10 18.38 4.98 3.71 9.69--------------------------------------------------------------------------------------------------------- 4.86 .00 11828 29.59 27.84 .59 7.69 19.56


Resource Reports

REXP - Resource Expanded Storage Migration Report

Purpose:

The Expanded Storage Migration Report displays information on the movement of pages from expanded storage to auxiliary storage (DASD).

The information shows how the migrations are distributed among active users, NSS/saved segments, the system, and all users. The term migration as used here is synonymous with movement in one direction, from expanded to auxiliary storage. The term block is used to represent 4K.

Uses:

You can use the report to examine the current utilization of expanded storage and then to determine whether more or less expanded storage is needed. If a resource (such as virtual system, CP, or system address) is being changed by page migration, you can change this by making changes to the current expanded storage configuration.


Device I/Os Per Second

DEVIOSEC INTG 08 FLTD Y Y Y I/Os per second to this device (I/O rate).

Device Type DEVTYPE INTG 04 CHAR Y Y Type of device (for example: 3380, 3350, or 3375).

Disconnect Time

DISCTIME MSEC 08 FLTD Y Y Y Average time this device was in DISCONNECT state during the reporting interval.

Pending Time PENDTIME MSEC 08 FLTD Y Y Y Average time this device was in PENDING state during the reporting interval.

Service Time (ms)

SERVTIME MSEC 08 FLTD Y Y Y Average service time for this device in milliseconds.


DASD Volser VOLSER INTG 06 CHAR Y Y DASD volume serial number.

Short Name: REXP

Long Name: REXPAND0.

Table 10. RDAS - Resource DASD Activity Report (continued)

Resource Reports



FIGURE 37. Sample Expanded Storage Migration Report.

Table 11. REXP - Resource Expanded Storage Migration Report

Columm Header Field Name Unit Field Length

Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF



Migrated Blocks Avg Age Change

EXPBKAGE INTG 08 FLTD Y Y Y The change in average age of all blocks migrated from expanded storage, in seconds.

Blocks Migrated EXPBKMIG INTG 08 FLTD Y Y Y The number of blocks migrated from expanded storage.

System Block Count

EXPMIGCP INTG 08 FLTD Y Y Y The number of blocks migrated from CP.

Dormant User Block Count

EXPMIGDM INTG 08 FLTD Y Y Y The number of blocks migrated from dormant users.

Active User Block Count

EXPMIGND INTG 08 FLTD Y Y Y The number of blocks migrated from active users.

Number of Migrations

EXPMIGS INTG 08 FLTD Y Y Y The number of invocations for expanded storage migration.

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 1, 2002 DATA PROCESSED: 10/27/03 05:00 TO 10/27/03 20:30 COMBINE(1H) EXPANDED STORAGE MIGRATION REPORT WLAVM01 ---------COUNT OF BLOCKS MIGRATED------------ -INTERVAL START- NUMBER OF BLOCKS MIGRATED BLOCKS GUEST BLKS DATE TIME MIGRATIONS MIGRATED AVG AGE CHANGE DORMANT USERS ACTIVE USERS NSS/DCSS SYSTEM ALLOCATED--<1>----------------------------------------------------------------------------------------------------------10/27/03 05:00 0 0 .0 0 0 0 0 010/27/03 06:00 61 15063 .0 9266 1266 3237 1294 45542410/27/03 16:08 0 0 .0 0 0 0 0 010/27/03 17:00 0 0 .0 0 0 0 0 010/27/03 18:00 0 0 .0 0 0 0 0 010/27/03 19:00 0 0 .0 0 0 0 0 010/27/03 20:00 0 0 .0 0 0 0 0 0--------------------------------------------------------------------------------------------------------------- 61 15063 .0 9266 1266 3237 1294 455424


Resource Reports

RFRE - Resource Free Storage Activity Report

Purpose:

The Free Storage Activity Report displays information on the utilization of real CP page frames. The information includes the percentage of storage in use, the largest block available, and the average and maximum number of pages extended.

Uses:

Each time the storage management system performs an extend to obtain more free storage, all other storage activity is suspended. A primary goal in free-storage management is therefore to limit the number of extends performed without over-allocating free storage. If you over-allocate free storage, you remove frames from the Dynamic Paging Areas (DPA). The DPA is critical for virtual machine pages, and therefore important to virtual machine response time. You can use this report to monitor the number of extends being performed over specified periods. It will also show you statistics for other system activity that is relevant to free-storage management.



NSS/DCSS Block Count

EXPMIGSS INTG 08 FLTD Y Y Y The number of blocks migrated from all the saved systems combined.

Guest Blocks Allocated

EXPMIGVS INTG 08 FLTD Y Y Y Average number of blocks allocated to guests during the interval (for example: users, guests).

SYSID 08 CHAR System ID for entire report appears in upper right portionof report heading.

Short Name: RFRE

Long Name: RFREE


Resource Reports


FIGURE 38. Sample Free Storage Activity Report

Table 12. RFRE - Resource Free Storage Activity Report

Columm Header

Field Name

Unit Field Length

Data Type

Keywords

DescriptionS

OR

T

GR

AP

H

RIF

/SIF



Free Frame Requests

FSTRFREQ INTG 08 FLTD Y Y Y The total number of free-storage extends during the reporting interval.

Free Frame Returns

FSTRFRRT INTG 08 FLTD Y Y Y The total number of free-storage extend releases during the interval.

Free Storage Requests

FSTRREQS INTG 08 FLTD Y Y Y The total number of free-storage requests during the reporting interval.

Free Storage Returns

FSTRRETS INTG 08 FLTD Y Y Y The total number of free-storage releases during the reporting interval.

Subpool List Count Regular

FSTRSBLK INTG 08 FLTD The number of frames in the regular free-storage subpool list during the reporting interval.

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 17, 2002 DATA PROCESSED: 10/21/03 18:38 TO 10/22/03 00:00 FREE STORAGE ACTIVITY REPORT WLAVM01 -INTERVAL START- --FREE STORAGE-- ---FREE FRAME---- %REAL --SUBPOOL CALLS- -SUBPOOL LIST COUNT- V=R DATE TIME REQUESTS RETURNS REQUESTS RETURNS STORAGE REGULAR V=R REGULAR V=R FREE SIZE--<1>-------------------------------------------------------------------------------------------------10/21/03 18:38 215877 215827 80 88 3.92 215745 0 1149 0 010/21/03 18:45 539874 539871 151 154 3.88 539679 0 1293 0 010/21/03 19:00 444250 444200 134 131 3.92 444128 0 1299 0 010/21/03 19:15 469170 469241 132 140 3.82 469054 0 1122 0 010/21/03 19:30 618381 618339 175 176 3.80 618220 0 996 0 010/21/03 19:45 831624 831632 151 145 3.88 831534 0 1121 0 010/21/03 20:00 838489 838573 150 153 3.84 838149 0 1081 0 010/21/03 20:15 766094 766033 175 165 3.96 765798 0 1275 0 010/21/03 20:30 633793 634028 119 128 3.85 633551 0 1151 0 010/21/03 20:45 466110 466113 113 111 3.88 465839 0 1125 0 010/21/03 21:00 785554 785564 107 110 3.84 785356 0 1092 0 010/21/03 21:15 568146 568140 133 124 3.95 568088 0 1431 0 010/21/03 21:30 630639 630606 160 163 3.92 630355 0 1308 0 010/21/03 21:45 433849 433795 124 127 3.88 433691 0 1195 0 010/21/03 22:00 592279 592207 122 122 3.88 592078 0 1154 0 010/21/03 22:15 474333 474329 138 139 3.87 474115 0 1223 0 010/21/03 22:30 624201 624153 199 181 4.09 623861 0 1387 0 010/21/03 22:45 709825 709860 147 156 3.98 709523 0 1250 0 010/21/03 23:00 677589 677460 170 161 4.09 677161 0 1214 0 010/21/03 23:15 669499 669661 199 205 4.01 669222 0 1241 0 010/21/03 23:30 879259 879449 198 203 3.95 878730 0 1202 0 010/21/03 23:45 907386 906835 216 202 4.13 905992 0 1193 0 0 ---------------------------------------------------------------------------------------------------- 13776221 13775916 3293 3284 3.92 13769869 0 26502 0 0


Resource Reports

RHLS - Resource High–Level Summary Report

Purpose:

The High-Level Summary Report provides summary information for several system-wide performance indicators and is available in all VM environments. The information for each indicator includes the minimum, average, maximum, and standard deviation values during a reporting interval.

When you compare the output for two or more indicators, keep in mind that the average and standard deviation values are not computed in the same way as the minimum and maximum values. Average and standard deviation values are compiled from data over the entire reporting interval. A minimum or maximum value represents one low or high reading that occurred during a particular recording interval. The minimum value for one performance indicator probably did not occur during the same recording interval as the minimum value for a different performance indicator.

An example of the impact of this difference is that the sum of the values of % Processor 1 Busy and % Processor 2 Busy may not equal the value of % CPU Busy.

All output for the reporting interval is printed on a single page.

Subpool Calls Regular

FSTRSUBP INTG 08 FLTD Y Y Y The number of calls for V=R free storage that were handled by the V=R free-storage subpool list.

Subpool List Count V=R

FSVRSBLK INTG 08 FLTD The number of frames in the V=R free storage subpool list as set at system gen time.

% Real Storage

REALSPCT 08 FLTD Y Y Y The percent of real storage being used as free storage during the reporting interval.


V=R Free Size

VRFRESIZ INTG 08 FLTD The total number of frames of free storage reserved for the V=R guest at system gen time.

Short Name: RHLS

Long Name: RHLS

Table 12. RFRE - Resource Free Storage Activity Report (continued)

Resource Reports


Uses:

This report is a good starting point when attempting to tune your system. Use it to determine if the various system indicators lie within their expected thresholds.

When you use the OBTAIN command to extract data that appears on this report, you will be using element names associated with row information, rather than column information as is the case with most other reports.

Do not use the COMBINE keyword with this report. The high-level summary statistics have already been combined over the entire selected report period.



FIGURE 39. Sample High-Level Summary Report

Table 13. RHLS - Resource High-Level Summary Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

Active Users ACTUSER 08 FLTD This statistic appears on the CPU Activity Report and represents the number of users who had any activity during the sampling interval.

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 22, 2002 DATA PROCESSED: 10/17/03 09:00 TO 10/17/03 17:00 HIGH-LEVEL SUMMARY REPORT WLAVM01 PERFORMANCE INDICATOR MINIMUM AVERAGE MAXIMUM TANDARD DEVIATION OBSERVATIONS----------------------------------------------------------------------------------------------------- RESOURCE AVAILABILITY INDEX .966 .972 .977 .003 32 % CPU BUSY 64.460 87.923 93.612 6.541 32 % VIRTUAL BUSY 26.881 53.268 67.427 9.060 32 TOTAL/VIRTUAL RATIO 1.380 1.685 2.398 .210 32 TRIVIAL TRANSACTIONS / SEC 2.091 2.230 2.599 .108 32 NON-TRIVIAL TRANSACTIONS / SEC .499 .677 .811 .078 32 TRIVIAL TRANSACTION COUNT 1882.000 2006.937 2339.000 96.881 32 NON-TRIVIAL TRANSACTION COUNT 449.000 609.281 730.000 70.480 32 LOGGED ON USERS 31.000 36.437 38.000 1.523 32 ACTIVE USERS 8.733 12.267 14.733 1.223 32 % VM I/O WAIT .000 2.743 5.263 .954 32 % VM PAGE WAIT .000 .249 5.263 1.032 32 I/O / SEC 47.789 184.628 3291.482 567.275 32 PAGE I/Os / SEC 1.817 26.421 72.188 19.145 32 % SPOOL SPACE IN USE 45.677 47.063 47.251 .411 32 % TEMP DISK SPACE IN USE 2.000 2.000 2.000 .000 32 % PAGING SPACE IN USE 10.821 16.676 23.404 3.641 32 % OF REAL STORAGE=SYSTEM FREE 27.680 30.791 33.078 1.390 32 % OF REAL STORAGE=DPA 98.407 98.407 98.407 .000 32 % LOGICAL PROCESSOR BUSY 2.332 4.337 12.113 2.867 32 % PHYSICAL PROCESSOR BUSY 1.554 2.891 8.076 1.911 32


Resource Reports

Logged On Users

AVGUSER 08 FLTD This statistic appears on the CPU Activity Report and represents the average number of users logged on during the sampling period.

% CPU Busy CPUBUSY 08 FLTD This statistic appears on the CPU Activity Report and represents the percent of the CPU being utilized. CPU usage includes that used by CP and by virtual machines. If you are running multiple processors, this value is the sum of CPU utilization for all processors and can be greater than 100%.


DATETIME STCK 08 CHAR This statistic is available on all reports and represents the date and time when the Collector started recording data.

Page I/Os / Sec DEVIOSEC INTG 08 FLTD This number represents the system-wide I/O paging rate. Related statistics appear on the Paging Activity Report on a volume-by-volume basis.

% Logical Processor Busy

LPARBUSY 08 FLTD Percentage of time this LPAR was busy based on the number of available logical processors.

Non-Trivial Transaction Count

NTRVCNT INTG 08 FLTD Related statistics appear on the Transaction Activity Report. This number represents the total number of non-trivial transactions processed during the reporting interval.

Table 13. RHLS - Resource High-Level Summary Report (continued)

Resource Reports


Non-Trivial Transactions / Sec

NTRVRATE 08 FLTD Related statistics appear on the Transaction Activity Report. This number represents the average number of non-trivial transactions processed per second during the reporting interval.

% Paging Space In Use

PCTPAGE 08 FLTD Related statistics appear on the Paging Activity Report on a volume-by-volume basis. This number represents the average system-wide percent of paging space in use.

% SPOOL Space In Use

PCTSPOL 08 FLTD This statistic appears on the SPOOLing Activity Report and represents the percent of SPOOL space in use for the entire system.

% Temp Disk Space In Use

PCTTDSK 08 FLTD This statistic appears on the Temporary Disk Activity Report and represents the percent of temporary disk space in use for the entire system.

% Physical Processor Busy

PHYSBUSY 08 FLTD Percentage of time this LPAR was busy based on the number of physical processors in the system.

% Processor n Busy

PRC00 -PRC07

INTG 08 FLTD The percent busy for each processor, assuming a MP system (up to eight processors: PRC00 - PRC07).



Resource Reports

Resource Availability Index

RAI 08 FLTD The Resource Availability Index is a statistic that summarizes how the resource met the demands placed on it during the reporting interval. The range is 0 - 1. 0 and 1 are limits, not possible values. 0 would mean the resource was never available; 1 would mean the resource was always available when needed. This RAI statistic is derived in the following way:1 - (((elig + q1) / (cpubusy/100))/user)Where:

The number displayed for RAI is useful as a comparative value for trend analysis. If the RAI value starts to drop over a period of time, you can view the individual components used to derive the RAI statistic. These components can be tracked by using the RHLS and RCPU reports.

% of Real Storage = DPA

SYSDPAP 08 FLTD This statistic represents the percentage of real storage available to the Dynamic Paging Area.

% of Real Storage = System Free

SYSFREEP 08 FLTD This statistic appears on the Free Storage Activity Report and represents the number of V=R free storage pages plus the number of free pages that are in use.


elig the average number of users in the eligible list.

q1 the average number of users in queue 1.

user the average number of users that had activity during the sampling interval.

Resource Reports


RICO - Resource IUCV/VMCF Communications Activity Report

Purpose:The Resource IUCV/VMCF Communications Activity Report provides information on IUCV (Inter-User Communication Vehicle) and VMCF (Virtual Machine Communication Facility) activity.

IUCV transfers data between two virtual machines or between a virtual machine and the CP system service. VMCF transfers data between two virtual machines only. IUCV and VMCF usage is increasing in VM. Both of these services allow multiple virtual machines to share and communicate with common resources on other virtual machines in a VM environment.


Trivial Transactions / Sec

TRVRATE 08 FLTD Related statistics appear on the Transaction Activity Report. This number represents the total number of trivial transactions processed during the reporting interval.

Total/Virtual Ratio

TVRATIO 08 FLTD The Total/Virtual Ratio appears on the CPU Activity Report and represents the ratio of total CPU usage to Virtual CPU usage.

% Virtual Busy VIRTBUSY 08 FLTD This statistic appears on the CPU Activity Report and represents the percent of the CPU used by virtual machines in real problem states.

% VM I/O Wait WAITIOP 08 FLTD This statistic represents the percent of all virtual machines in an I/O wait state.

% VM Page Wait

WAITPAGP 08 FLTD This statistic represents the percent of all virtual machines in a page wait state.

Short Name: RICO

Long Name: RICOM



Resource Reports

Uses:Use this report to determine where your heaviest and where your lightest IUCV activity is occurring. Then make sure that the pages are locked in the areas of heaviest activity and unlocked in the areas of lightest activity. Locking system code that makes heavy use of IUCV and/or VMCF provides improved performance for those virtual machines using IUCV or VMCF system services.



FIGURE 40. Sample IUCV/VMCF Communications Activity Report

Table 14. RICO - Resource IUCV/VMCF Communications Activity Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

BLOCKIO %Err

BLKIOEP 08 FLTD Y Y Y The percent of error when using CP system service, BLOCKIO.

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 22, 2002 DATA PROCESSED: 10/17/03 09:00 TO 10/17/03 17:00 IUCV/VMCF COMMUNICATIONS ACTIVITY REPORT WLAVM01 -INTERVAL START- -MSGALL-- ---MSG--- ---RPI--- -BLOCKIO- -MONITOR- -IUCV/VM- -VMCF/VM- ---CCS--- -SIGNAL-- DATE TIME XFER %ERR XFER %ERR XFER %ERR XFER %ERR XFER %ERR XFER %ERR XFER %ERR XFER %ERR XFER %ERR--<1>---------------------------------------------------------------------------------------------------------10/17/03 09:00 0 .0 0 .0 0 .0 0 .0 14 .0 14 .0 2 .0 0 .0 0 .010/17/03 09:15 0 .0 0 .0 0 .0 0 .0 92 .0 120 .0 26 .0 28 .0 0 .010/17/03 09:30 0 .0 0 .0 0 .0 0 .0 112 .0 131 .0 8 .0 19 .0 0 .010/17/03 09:45 0 .0 1 .0 0 .0 0 .0 88 .0 101 .0 312 .0 12 .0 0 .010/17/03 10:00 0 .0 0 .0 0 .0 0 .0 110 .0 126 .0 240 .0 16 .0 0 .010/17/03 10:15 0 .0 0 .0 0 .0 0 .0 104 .0 104 .0 138 .0 0 .0 0 .010/17/03 10:30 0 .0 0 .0 0 .0 0 .0 105 .0 254 .0 110 .0 149 .0 0 .010/17/03 10:45 0 .0 2 .0 0 .0 0 .0 91 .0 103 .0 80 .0 10 .0 0 .010/17/03 11:00 0 .0 0 .0 0 .0 0 .0 126 .0 130 .0 8 .0 4 .0 0 .010/17/03 11:15 0 .0 0 .0 0 .0 0 .0 102 .0 122 .0 160 .0 20 .0 0 .010/17/03 11:30 0 .0 0 .0 0 .0 0 .0 108 .0 108 .0 138 .0 0 .0 0 .010/17/03 11:45 0 .0 0 .0 0 .0 0 .0 222 .0 222 .0 2 .0 0 .0 0 .010/17/03 12:00 0 .0 0 .0 0 .0 0 .0 310 .0 310 .0 12 .0 0 .0 0 .010/17/03 12:15 0 .0 0 .0 0 .0 0 .0 138 .0 138 .0 186 .0 0 .0 0 .010/17/03 12:30 0 .0 0 .0 0 .0 0 .0 102 .0 102 .0 108 .0 0 .0 0 .010/17/03 12:45 0 .0 0 .0 0 .0 0 .0 122 .0 122 .0 222 .0 0 .0 0 .010/17/03 13:00 0 .0 0 .0 0 .0 0 .0 300 .0 300 .0 382 .0 0 .0 0 .010/17/03 13:15 0 .0 0 .0 0 .0 0 .0 264 .0 264 .0 300 .0 0 .0 0 .010/17/03 13:30 0 .0 1 .0 0 .0 0 .0 356 .0 357 .0 36 .0 0 .0 0 .010/17/03 13:45 0 .0 0 .0 0 .0 0 .0 176 .0 176 .0 640 .0 0 .0 0 .010/17/03 14:00 0 .0 0 .0 0 .0 0 .0 324 .0 324 .0 94 .0 0 .0 0 .010/17/03 14:15 0 .0 0 .0 0 .0 0 .0 166 .0 166 .0 58 .0 0 .0 0 .010/17/03 14:30 0 .0 0 .0 0 .0 0 .0 142 .0 142 .0 110 .0 0 .0 0 .010/17/03 14:45 0 .0 0 .0 0 .0 0 .0 56 .0 56 .0 40 .0 0 .0 0 .010/17/03 15:00 0 .0 0 .0 0 .0 0 .0 126 .0 126 .0 352 .0 0 .0 0 .010/17/03 15:15 0 .0 0 .0 0 .0 0 .0 136 .0 136 .0 12 .0 0 .0 0 .010/17/03 15:30 0 .0 0 .0 0 .0 0 .0 90 .0 90 .0 466 .0 0 .0 0 .010/17/03 15:45 0 .0 0 .0 0 .0 0 .0 90 .0 258 .0 220 .0 168 .0 0 .010/17/03 16:00 0 .0 1 .0 0 .0 0 .0 240 .0 241 .0 1376 .0 0 .0 0 .010/17/03 16:15 0 .0 0 .0 0 .0 0 .0 192 .0 192 .0 1150 .0 0 .0 0 .010/17/03 16:30 0 .0 0 .0 0 .0 0 .0 98 .0 98 .0 1574 .0 0 .0 0 .010/17/03 16:45 0 .0 0 .0 0 .0 0 .0 142 .0 142 .0 318 .0 0 .0 0 .0-------------------------------------------------------------------------------------------------------------- 0 .0 5 .0 0 .0 0 .0 4844 .0 5275 .0 8880 .0 426 .0 0 .0

Resource Reports


BLOCKIO Xfers

BLKIOXF INTG 08 FLTD Y Y Y Number of transfers between CP system service, DASD BLOCKIO, and other virtual machines.

CCS VM %Err

CCSEP 08 FLTD Y Y Y The percent of error when using CP system service, CCS

CCS VM Xfers

CCSXF INTG 08 FLTD Y Y Y Number of transfers between CP system service, CCS, and other virtual machines.


DATETIME STCK 08 CHAR The start date and time for this reporting interval.

MONITOR %Err

MONEP 08 FLTD Y Y Y The percent of error when using CP system service, MONITOR.

MONITOR Xfers

MONXF INTG 08 FLTD Y Y Y Number of transfers done for CP system service, MONITOR.

MSGALL %Err

MSGALLEP 08 FLTD Y Y Y The percent of error when using CP system service, MSGALL.

MSGALL Xfers

MSGALLXF INTG 08 FLTD Y Y Y Number of message transfers done for CP system service, MSGALL.

MSG %Err MSGEP 08 FLTD Y Y Y The percent of error when using CP system service, MSG.

MSG Xfers MSGXF INTG 08 FLTD Y Y Y Number of message transfers done for CP system service, MSG.

RPI %Err RPIEP 08 FLTD Y Y Y The percent of error when using CP system service, RPI.

RPI Xfers RPIXF INTG 08 FLTD Y Y Y Number of transfers done for CP system service, RPI.

SIGNAL %Err SIGNALEP 08 FLTD Y Y Y The percent of error when using CP system service, SIGNAL.

Table 14. RICO - Resource IUCV/VMCF Communications Activity Report (continued)


Resource Reports

RLPR - Resource LPAR Activity Report

Purpose:

The LPAR activity report provides utilization statistics for each Logical Partition. All of the standard EPILOG reporting commands and options are available for use with the RLPR report.

The EPILOG High Level Summary (RHLS), CPU Activity (RCPU), and System Information (RSYS) reports are extended to include LPAR-related information.

See the appropriate charts in “Data Dictionary” on page 201 for information about the LPAR-related fields in the various EPILOG reports. The information in the charts is useful for generating and interpreting EPILOG reports, and for utilizing the OBTAIN facility.

Uses:

The LPAR activity is particularly useful for Performance Analysts who want to monitor the effectiveness of their LPAR configuration from a historical perspective.

SIGNAL Xfers SIGNALXF INTG 08 FLTD Y Y Y Number of transfers between CP system service, SIGNAL, and other virtual machines.


IUCV VM %Err

VMIUCVEP 08 FLTD Y Y Y The percent of error when using IUCV between two virtual machines.

IUCV VM Xfers

VMIUCVXF INTG 08 FLTD Y Y Y Number of transfers done by IUCV between two virtual machines.

VMCF VM %Err

VMVMCFEP 08 FLTD Y Y Y The percent of error when using VMCF between two virtual machines.

VMCF VM Xfers

VMVMCFXF INTG 08 FLTD Y Y Y Number of transfers done by VMCF between two virtual machines.

Short Name: RLPR

Long Name: RLPAR


Resource Reports



You must specify “COLLECT SYSTEM” in your COLLECT CONTROL file to collect EPILOG LPAR data. The CVOVDATA DCSS must be defined for LPAR collection of EPILOG data to occur. The CVOVDATA DCSS is also required for OMEGAMON LPAR reporting.

FIGURE 41. Sample LPAR Activity Report

Table 15. RLPR - Resource LPAR Utilization Report


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

Logical CPU% LPARBUSY 08 FLTD Y Y Y Utilization of the system based on the number of logical processors available. Computed as: (Dispatch time / Elapsed time) * Number of LPs

Dispatch Time LPARDISP SECS 08 FLTD Y Y Y Total amount of time that all of the logical processors for this LPAR were busy during the reporting interval.

Number Processors LPARLPCT INTG 08 FLTD Y Y Y Number of logical processors assigned to this LPAR.

Name LPARNAME 08 CHAR Y Y Assigned name of the logical partition.

Number LPARNUM INTG 01 UBIN Y Y Assigned logical partition number.

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 17, 2002 DATA PROCESSED: 10/11/03 20:21 TO 10/11/03 21:00 COMBINE (1H) LPAR UTILIZATION REPORT WLAVM01 NUMBER LOGICAL PHYSICAL PARTITION DISPATCH NAME NUMBER STATUS WEIGHT WAIT PROCESSORS CPU% CPU% OVERHEAD TIME---<2>--------<1>----------------------------------------------------------------------------------------- MVSA 1 ACTIVE 500 NO 3 49.82 49.82 .00 00:52:18 MVSG 2 ACTIVE 300 NO 2 37.50 25.00 .00 00:26:15 VMES 3 ACTIVE * 100 NO 2 9.26 6.18 .00 00:06:29 MVSB 4 ACTIVE 100 NO 2 9.52 6.35 .00 00:06:40---------------------------------------------------------------------------------------------------------- 87.35 .00 01:31:43


Resource Reports

LPAROVER CSEC 08 FLTD Y Y Y VM 1.2.0 or higher and LPAR management facility. Amount of logical CPU busy which was due to LP dispatching overhead.

Partition Overhead LPAROVHD PCT 08 FLTD Y Y Y VM 1.2.0 or higher and LPAR management facility. Percentage of overhead time across all logical processors.

Status LPARSTAT 08 CHAR Y Y Y Status of the logical partition during the reporting interval. Can be ACTIVE or INACTIVE. The partition that was used to collect the LPAR data will have an asterisk (*) appended (for example, “ACTIVE “).

Wait LPARWAIT 04 CHAR Y Y Y Status of the WAIT bit for the logical processors within this LPAR. If any LP has the WAIT bit ON, this field will contain “YES”.

Weight LPARWGHT INTG 08 FLTD Y Y Y Average weight of all logical processors defined for this LPAR. The weight values for dedicated processors will be 1000.

Physical CPU% PHYSBUSY 08 FLTD Y Y Y Utilization of the system based on the number of physical processors available. Computed as: (Dispatch time / Elapsed time) * Number of CPUs

Table 15. RLPR - Resource LPAR Utilization Report (continued)

Resource Reports


RNSS - Resource Saved Segment/NSS Activity Report

Purpose:

The Saved Segment/NSS Activity Report provides information on the system-wide utilization of saved segments and named saved systems.

A saved segment is an area of virtual storage outside the address range of a virtual machine. A named saved system is a system that has been saved on a disk along with all the information needed to resume execution and provide an efficient means of IPLing the system. Both saved segments and named saved systems can be shared or non-shared, and read or read/write accessed.

Uses:

You can use this report to help cluster heavily used saved segments into common segments, and to identify those segments that are not being used.



FIGURE 42. Sample Named Saved Systems Activity Report

Short Name: RNSS

Long Name: RNSS

Table 16. RNSS - Resource Saved Segment/NSS Activity Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF


DATETIME STCK 08 CHAR Date and time when Collector started recording data.

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 19, 2002 DATA PROCESSED: 10/14/03 00:00 TO 10/14/03 08:00 COMBINE(8H) NAMED SAVED SYSTEMS ACTIVITY REPORT WLAVM01 SEGMENT SPOOL --- CREATION --- ------ USERS ------ PAGES PAGES PAGE PAGES PAGES NAME ID DATE TIME SHARED NON-SHARED SAVED DEFINED FAULTS RESIDENT STOLEN-------------------------------------------------------------------------------------------------------CMS 17 10/09/03 23:20 865 0 526 526 200 98 1077CMSINST 4 07/27/03 21:29 865 0 81 81 1 1 4MONDCSS 2 07/27/03 20:47 32 0 0 0 43 16 0OMEGAMON 16 10/07/03 04:33 96 0 128 128 0 34 0CVOVDATA 19 10/20/03 21:40 128 0 256 256 28 34 100------------------------------------------------------------------------------------------------------- 1986 0 991 991 272 183 1181


Resource Reports

Creation Time SNTCRTIM 08 STCK The date and time that the SPOOL file was created.

Segment Name SNTNAME 08 CHAR Y The name of the saved segment or NSS.

Users Non-Shared

SNTNUSRS INTG 08 FLTD Y Y Y The number of users who access the saved segment or NSS with a private copy.

Pages Saved SNTPAGCT INTG 08 FLTD Y Y Y The number of pages saved for this segment.

Pages Resident SNTRESPG INTG 08 FLTD The number of pages in memory for this saved system during this interval.

Page Faults SNTSHFLT INTG 08 FLTD Y Y Y The number of page faults generated in a shared saved segment and named saved system.

SPOOL ID SNTSPFID INTG 08 FLTD Y The ID number of the SPOOL file.

Pages Stolen SNTSTOLN INTG 08 FLTD Y Y Y The number of pages that were moved from real memory to external storage while being used, either by the demand scan, trim, or free-storage scan process.

Pages Defined SNTSTRCT INTG 08 FLTD Y Y Y The number of pages defined for this saved system.

Users Shared SNTSUSRS INTG 08 FLTD Y Y Y The number of users having shared access to the saved segment or NSS.


Table 16. RNSS - Resource Saved Segment/NSS Activity Report (continued)

Resource Reports


RPAG - Resource Paging Activity Report

Purpose:

The Paging Activity Report shows what paging subsystems are allocated, where they are defined, and how they are being used. If question marks appear in the Paging Type field or the Device Type field, the Reporter could not identify the device or paging type, but still reports data on it.

Uses:

Use the report to manage your paging systems and to detect paging bottlenecks. Excessive I/Os per second, Percent Busy, or Service Time are key indicators of paging bottlenecks.

Use the Extent Percent Full field to find out how much paging space is being used. This helps you ensure proper DASD allocation for paging. If the percent full numbers are low, you may have over-allocated DASD space for paging. If the percent full numbers are approaching 100%, you may run out of paging space. It is best to examine Extent Percent Full for a peak period to ensure that you do not erroneously lower paging disk allocation.



FIGURE 43. Sample Paging Activity Report

Notes:

1. These fields apply to a device. Therefore, paging subsystems with the same Device Address will have the same numbers in the last three fields.

2. When the same device address appears more than once in the RPAG report, the values on the summary line may appear to be incorrect. The values will not be a sum or average of all values in the column. This occurs because the values on each line are device-level statistics. The values from only one line entry for each device are used to produce the summary line values.

Short Name: RPAG

Long Name: RPAGE

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 2003 DATA PROCESSED: 10/08/03 13:00 TO 10/08/03 14:00 COMBINE(1H) PAGING ACTIVITY REPORT WLVM PAGING DEVICE DASD DEVICE DASD EXTENT DEVICE I/O’S DEVICE DEVICE SERVICE TYPE ADDRESS VOLSER TYPE EXTENT % FULL PER SECOND PERCENT BUSY TIME (MS)---<1>-----------<2>--------<3>----------------------------------------------------------------------------- PAGING 0 X-STOR 0-2048 78.72 18.59 .00 .00 PAGING 9E8 VMPK07 3380 1195-1434 44.52 1.66 3.92 23.68 PAGING 9FA VMXA10 3380 300-539 41.28 1.65 4.12 24.92 SPOOLING 9E5 VMPK04 3380 1000-1599 27.41 .37 .58 15.44------------------------------------------------------------------------------------------------------------ 34.85 22.28 2.15 3.87


Resource Reports

3. Use of SELECTIF or REPORTIF keywords of the REPORT or SET commands include the selection of four-digit device addressees. This could affect the output of the RPAG report.

Table 17. RPAG - Resource Paging Activity Report


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF



Device Address DEVADDR ADDR 02 SUBI Y Y Real address of paging DASD.

Device Type DEVTYPE INTG 04 CHAR Y Y Type of DASD (for example: 3370 or 3380).

DASD Extent ENDCYL INTG 08 FLTD Y Y Y End extent allocated for paging on a device.

Extent % Full EXTFULL INTG 08 FLTD Y Y Y Percentage of page slots in use.

Paging Type PAGETYPE INTG 16 CHAR Y Y Type of paging.

Device Percent Busy

PCTBUSY INTG 08 FLTD Y Y Y The percentage of time DASD was found busy during the time frame.

Service Time SERVTIME MSEC 08 FLTD Y Y Y The average time it took to complete an I/O operation to a paging space.

Device Service Time

SERVTIME MSEC 08 FLTD Y Y Y The average time it took to complete an I/O operation.

DASD Extent STARTCYL INTG 08 FLTD Y Y Y Start extent allocated for paging on a device.


DASD Volser VOLSER INTG 06 CHAR Y Y Volume serial number of paging DASD.

Resource Reports


RSCH - Resource Scheduler Storage Report

Purpose:

The Scheduler Storage Report provides information relating to scheduler queues and the parameters used for the dispatching process with multiple virtual machines. The information includes the paging rate, storage and paging weights, and user counts and expansion indexes for short, medium, and long-running users. The expansion index indicates how much longer it takes a user to run in a queue than it would if this were not a multi-user environment.

Uses:

Use this report to determine the storage contention between virtual machines from different scheduler queues.



FIGURE 44. Sample Scheduler Storage Report

Short Name: RSCH

Long Name: RSCHSTOR

EPILOG FOR VM V610 PAGE 1 RUN DATE: OCTOBER 1, 2003 DATA PROCESSED: 10/23/03 12:55 TO 10/25/03 20:35 COMBINE(1H) SCHEDULER STORAGE REPORT WLAVM01 -INTERVAL START- SYSTEM AVG STOR PAGE --- E1 LIST ---- --- E2 LIST ---- --- E3 LIST ---- DATE TIME PAGEIN TIME INDEX INDEX #USERS EXPINDEX #USERS EXPINDEX #USERS EXPINDEX--<1>--------------------------------------------------------------------------------------------------- 10/23/03 12:55 1 .0 17 0 0 1 0 1 0 1 10/23/03 13:00 7 .0 156 0 0 4 0 4 0 4 10/23/03 14:00 11 .0 307 0 0 5 0 5 0 5 10/23/03 15:00 4 .0 905 0 0 5 0 5 0 5 10/23/03 16:00 3 .0 1049 0 0 5 0 5 0 5 10/23/03 17:00 1 .0 384 0 0 2 0 2 0 2 . . . . . . . . . . . . . . . . . . 10/25/03 00:00 43 .1 725 20 0 4 0 4 0 4 10/25/03 01:00 15 .1 747 7 0 4 0 4 0 4 10/25/03 02:00 6 .1 701 0 0 4 0 4 0 4 10/25/03 03:00 0 .1 694 0 0 4 0 4 0 4 10/25/03 04:00 2 .1 693 0 0 4 0 4 0 4 10/25/03 05:00 2 .1 712 0 0 4 0 4 0 4 10/25/03 06:00 4 .1 735 0 0 4 0 4 0 4 10/25/03 07:00 4 .1 758 2 0 4 0 4 0 4 10/25/03 08:00 4 .1 771 0 0 4 0 4 0 4 10/25/03 09:00 3 .1 759 0 0 4 0 4 0 4 10/25/03 10:00 6 .1 786 2 0 4 0 4 0 4 10/25/03 11:00 4 .1 830 0 0 4 0 4 0 4 10/25/03 12:00 6 .1 791 1 0 4 0 4 0 4 10/25/03 13:00 8 .1 747 0 0 4 0 4 0 4 10/25/03 14:00 6 .1 724 1 0 4 0 4 0 4 10/25/03 15:00 18 .1 814 11 0 4 0 4 0 4 10/25/03 16:00 157 .1 877 146 0 4 0 4 0 4 10/25/03 17:00 119 .1 1206 68 0 6 0 6 0 6 10/25/03 18:00 172 .0 933 81 0 4 0 4 0 4 10/25/03 19:00 117 .1 895 86 0 4 0 4 0 4 10/25/03 20:00 159 .1 815 100 0 4 0 4 0 4-------------------------------------------------------------------------------------------------------- 2234 1.7 29486 1182 0 159 0 159 0 159


Resource Reports

Table 18. RSCH - Resource Scheduler Storage Report


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

Avg Time AVGPGRD SECS 08 FLTD Y Y Y The average elapsed time in seconds that it takes to read one page.


DATETIME STCK 08 CHAR The date and time on which this reporting interval started.

E1 List Exp Indx EXPINDX1 INTG 08 FLTD Y Y Y The expansion index for short running users in the E1 queue.

E2 List Exp Indx EXPINDX2 INTG 08 FLTD Y Y Y The expansion index for medium-running users in the E2 queue.

E3 List Exp Indx EXPINDX3 INTG 08 FLTD Y Y Y The expansion index for long-running users in the E3 queue.

E1 List # Users EXPUSER1 08 FLTD Y Y Y The number of short running users in the eligible list for the E1 queue.

E2 List # Users EXPUSER2 08 FLTD Y Y Y The number of medium-running users in the eligible list for the E2 queue.

E3 List # Users EXPUSER3 08 FLTD Y Y Y The number of long-running users in the eligible list for the E3 queue.

System Pagein PAGERATE INTG 08 FLTD Y Y Y The number of pages per second being read in by the system.

Page Index PAGINDEX INTG 08 FLTD Y Y Y The system resource weight for paging. Used by the scheduler to decide how much of a bottleneck the paging resources are.

Resource Reports


RSEE - Resource Seek Analysis Report

Purpose:

The Seek Analysis Report provides information on I/O requests to minidisks across a specific DASD device. The seek information is gathered according to the physical location of the minidisk on the real device.

The collection of seek data is disabled by default. It is a good idea to collect seek data for short time intervals because of the large quantity of data involved. When you need to collect seek data, set the HOURS option on the COLLECT SEEKS command in the Collector control file. For example, the following command will result in seek data being collected for 5 minutes beginning at 9:00 AM and 10:00 AM.

COLLECT SEEKS VOLUME(cccccc) HOURS(09:00 - 09:05)

COLLECT SEEKS VOLUME(cccccc) HOURS(10:00 - 10:05)

Uses:

You can use this report to determine the optimal location for a minidisk on a DASD device or to decide if certain users should be removed from an over-utilized device.



Stor Index STGINDEX INTG 08 FLTD Y Y Y The system resource weight for storage. Used by the scheduler to decide how much of a bottleneck the paging resources are.


Short Name: RSEE

Long Name: RSEEK

Table 18. RSCH - Resource Scheduler Storage Report (continued)


Resource Reports

FIGURE 45. Sample Seek Analysis Report

Table 19. RSEE - Resource Seek Analysis Report


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

Avg. Move Per Seek AVGMOVE INTG 08 FLTD Y Y Y Average number of cylinders that were skipped for a seek into this minidisk.

Avg. Move Within Extent

AVGMVEXT INTG 08 FLTD Y Y Y Average number of cylinders that were skipped for a seek within this minidisk.


DATETIME STCK 08 CHAR Date and time on which this reporting interval started.

Real Address DEVADDR ADDR 02 SUBI Y Y The address of the real DASD device.

Device Type DEVTYPE INTG 04 CHAR Y Y The type of real DASD device.

DASD Extent ENDCYL INTG 08 FLTD Y Y Y The cylinder or block number on the real DASD device where the minidisk ends.

Extent Count NUMCYLS INTG 08 FLTD Y Y Y Difference between the start and end extents of this minidisk.

EPILOG FOR VM V610. PAGE 1 RUN DATE: OCTOBER 10, 2003 DATA PROCESSED: 10/09/03 10:15 TO 10/09/03 10:30 SEEK ANALYSIS REPORT WLAVM01 DASD USERID VIRTUAL REAL DEVICE DASD EXTENT TOTAL SEEKS IN AVG MOVE AVG MOVE VOLSER ADDRESS ADDRESS TYPE EXTENT COUNT SEEKS EXTENT PER SEEK WITHIN EXTENT-----------------------------<1>--------------------------------------------------------------------- . . . . . . . . . . . . . . . VM9 SYSTEM 100 146 3380 300-539 240 1197 1197 1.6 1.6 VM2 SYSMNTXA 318 318 3380 0-2655 2656 1 1 134.0 134.0 VM2 $SYSTST 191 318 3380 1554-1603 50 27 0 611.3 .0 VM2 VMUTIL 191 318 3380 760-760 1 22 16 113.5 .0 VM2 SYSTEM 400 318 3380 1004-1007 4 178 177 .0 .0 VM1 SYSTEM 200 327 3380 1000-1599 600 27 27 2.3 2.3 VM1 SYSTST 191 327 3380 227-280 54 32 32 1.0 1.0 VM0 SYSTEM 100 337 3380 300-539 240 3572 3572 1.3 1.3 VM0 VMTST D97 337 3380 0-885 886 13 13 .0 .0----------------------------------------------------------------------------------------------------- 5069 5035 5.1 1.3

Resource Reports


RSPO - Resource SPOOLing Activity Report

Purpose:

The SPOOLing Activity Report displays information about the configuration and utilization of the SPOOLing subsystem datasets.

Configuration information includes the real device address, volume serial number, device type, starting and ending location, and the total number of cylinders or blocks. Utilization information includes the number of used slots, the number of available slots, and the percentage of space in use.

Total Seeks SEEKS 08 FLTD Y Y Total number of seeks to this minidisk.

Seeks In Extent SEEKSEXT INTG 08 FLTD Y Y Y The number of seeks made from one cylinder of the minidisk to another cylinder of the same minidisk.

DASD Extent STARTCYL INTG 08 FLTD Y Y Y The cylinder or block number on the real DASD device where the minidisk begins.


Virtual Address VCUU ADDR 02 UBIN Y Y The virtual address of this minidisk.

DASD Volser VOLSER INTG 06 CHAR Y Y The volume serial number for the real DASD device.

Userid WORKLOAD 08 CHAR Y Y The user ID of the user linked to this minidisk. If this area of the device is not allocated to a user, this field is set to SYSTEM.

Short Name: RSPO

Long Name: RSPOOL

Table 19. RSEE - Resource Seek Analysis Report (continued)


Resource Reports

Uses:

SPOOLing is performed on system-owned devices that have TEMP allocation defined (SPOL). You can use the SPOOLing Activity Report to find where the SPOOLing areas are located and to get an idea of how much of that space is being used. You will probably find the Extent Percent Full statistic to be the most helpful output field on this report.

Note: The CP Paging subsystem also uses TEMP space if no more dedicated paging space is available. Pages being used by the Paging subsystem are included with pages being used by the SPOOLing subsystem when statistics are calculated for this report.



FIGURE 46. Sample SPOOLing Activity Report

Table 20. RSPO - Resource SPOOLing Activity Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

Extent Count ALLOCCNT INTG 08 FLTD Y Y Y The number of cylinders or blocks allocated for the SPOOLing extent.

Available Slots AVAILSLT 08 FLTD Y Y Y The number of slots available at the time the sample was taken.



EPILOG VM V610 PAGE 1RUN DATE: SEPTEMBER 28, 2003 DATA PROCESSED: 09/09/03 04:00 TO 09/09/03 04:15 SPOOLING ACTIVITY REPORT WLAVM01 DEVICE DASD DEVICE DASD EXTENT USED AVAILABLE EXTENT ADDRESS VOLSER TYPE EXTENT COUNT SLOTS SLOTS PERCENT FULL---<1>--------<2>----------------------------------------------------------------------------------- 217 VMHP01 3380 350-882 533 32902 47048 41.15 310 VMPF02 3380 350-882 533 33905 46045 41.15 312 VMTS03 3380 350-882 533 32847 47103 41.08 811 VMUS02 3380 400-749 350 22207 30293 42.20 814 VMSY09 3380 400-749 350 21693 30807 41.32 917 VMSY08 3380 400-749 350 21409 31091 40.78---------------------------------------------------------------------------------------------------- 2649 164963 232387 41.52

Resource Reports


RSTR - Resource Storage Management Report

Purpose:

The Storage Management Report provides information on real storage utilization for your entire VM system. The information includes available list thresholds, page faults, DPA and CP paging activity, and unsuccessful demand scans made to replenish the available list. The available list is a list of pages currently not being used by the system that will be used to hold a page in storage when one is needed. The high and low thresholds are dynamic and change according to the load.

Uses:

Use this report to assist in planning for future real storage management.

If there are no pages on the available list when a page fault occurs for a virtual machine, that virtual machine must sit in a page-wait state until a page frame becomes available. Monitoring the available list can indicate whether or not storage is responsible for a slow response time.

Device Address DEVADDR ADDR 02 SUBI Y Y Real address of the device where SPOOLing space is allocated.

Device Type DEVTYPE INTG 04 CHAR Y Y Device type for the real device.

DASD Extent ENDCYL INTG 08 FLTD Y Y Y The ending cylinder or block number for the SPOOLing extent.

Extent Percent Full

PERFULL 08 FLTD Y Y Y Percentage of space in use at the time the sample was taken.

DASD Extent STARTCYL INTG 08 FLTD Y Y Y The starting cylinder or block number for the SPOOLing extent.


Used Slots TOTUSLOT INTG 08 FLTD Y Y Y The number of used slots at the time the sample was taken.

DASD Volser VOLSER INTG 06 CHAR Y Y Volume serial number for the real device.

Short Name: RSTR

Long Name: RSTRMGMT

Table 20. RSPO - Resource SPOOLing Activity Report (continued)


Resource Reports



FIGURE 47. Sample Storage Management Report

Table 21. RSTR - Resource Storage Management Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

Available List Frames

AVLFRAMS INTG 08 FLTD Y Y Y The number of frames currently on the available list. This number will be higher than the high threshold at IPL time.

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 10, 2002 DATA PROCESSED: 10/09/03 00:00 TO 10/09/03 09:00 STORAGE MANAGEMENT REPORT WLAVM01 -INTERVAL START- ------ AVAILABLE LIST ----- DPA FRAME -- EXTEND -- CP -PAGE FAULT/SEC- UNSUCCESSFUL DATE TIME FRAMES<HI & LOW THRESHOLDS> FRAMES WAITS FRAMES WAITS PAGEINS SINGLE BLOCK DEMAND SCANS-<1>----------------------------------------------------------------------------------------------------------10/09/03 00:00 299 282 196 7808 0 96 0 46 .0 .0 010/09/03 00:15 326 282 196 7808 0 88 0 23 .0 .0 010/09/03 00:30 336 282 196 7808 0 86 0 18 .0 .0 010/09/03 01:00 241 227 141 7808 0 93 0 591 .0 .2 010/09/03 01:15 217 210 124 7808 0 87 0 178 .1 .1 010/09/03 01:30 251 210 124 7808 0 88 0 18 .0 .0 010/09/03 01:45 239 210 124 7808 0 87 0 3773 .1 .1 010/09/03 02:00 216 210 124 7808 0 95 0 171 .1 .1 010/09/03 02:15 223 210 124 7808 0 88 0 38 .0 .0 010/09/03 02:30 213 210 124 7808 0 91 0 54 .0 .0 010/09/03 02:45 218 210 124 7808 0 90 0 61 .0 .0 010/09/03 03:00 213 210 124 7808 0 94 0 96 .0 .0 010/09/03 03:15 224 210 124 7808 0 93 0 7749 .0 .0 010/09/03 03:30 265 210 124 7808 0 91 0 641 .0 .0 010/09/03 03:45 274 210 124 7808 0 90 0 21 .0 .0 010/09/03 04:00 228 210 124 7808 0 91 0 87 .0 .0 010/09/03 04:15 221 210 124 7808 0 92 0 25 .0 .0 010/09/03 04:30 250 210 124 7808 0 93 0 122 .0 .0 010/09/03 04:45 326 327 241 7808 0 105 0 1377 .1 .1 010/09/03 05:00 329 327 241 7808 0 108 0 873 .5 .4 010/09/03 05:15 302 326 241 7808 0 100 0 1940 1.4 .5 010/09/03 05:30 299 297 211 7808 0 104 0 1404 .9 .5 010/09/03 05:45 279 271 185 7808 0 101 0 519 .3 .2 010/09/03 06:00 278 270 185 7808 0 100 0 402 .3 .1 010/09/03 06:15 271 270 185 7808 0 106 0 1344 1.0 .4 010/09/03 06:30 277 270 185 7808 0 103 0 2031 1.6 .6 010/09/03 06:45 277 270 185 7808 0 102 0 712 .5 .2 010/09/03 07:00 276 270 185 7808 0 103 0 554 .4 .2 010/09/03 07:15 279 271 185 7808 0 101 0 230 .2 .1 010/09/03 07:30 270 270 185 7808 0 107 0 403 .2 .1 010/09/03 07:45 269 270 185 7808 0 105 0 233 .2 .1 010/09/03 08:00 272 270 185 7808 0 106 0 305 .2 .1 010/09/03 08:15 273 270 185 7808 0 105 0 289 .2 .1 010/09/03 08:30 280 270 185 7808 0 106 0 279 .2 .1 010/09/03 08:45 293 270 185 7808 0 105 0 205 .2 .0 0-------------------------------------------------------------------------------------------------------------- 266 327 124 7808 0 3400 0 26812 .3 .1 0

Resource Reports


Available List High Threshold

AVLHGHTH INTG 08 FLTD Y Y Y The high threshold for the available list replenishment subsystem.

Available List Low Threshold

AVLLOWTH INTG 08 FLTD Y Y Y The low threshold for the available list replenishment subsystem.

Frame Waits AVLWAIT INTG 08 FLTD Y Y Y The number of tasks that cannot be executed because they are waiting for a frame.

Page Faults/Sec Block

BLOKFLTS INTG 08 FLTD Y Y Y The average number of page faults per second for a block of pages during the reporting interval.



DPA Frames DPAFRAMS INTG 08 FLTD Y Y Y The number of frames allocated to the dynamic paging area.

Unsuccessful Demand Scans

DSCNFAIL INTG 08 FLTD Y Y Y The number of times the demand scan was invoked and could not replenish the available list to its threshold.

Extend Frames EXTFRAMS INTG 08 FLTD Y Y Y The number of frames used by free-storage management.

Extend Waits EXTWAIT INTG 08 FLTD Y Y Y The number of deferred pages waiting for a frame.

CP Pageins PGFAULTS INTG 08 FLTD Y Y Y The number of pages read in for CP.

Page Faults/Sec Single

SINGFLTS INTG 08 FLTD Y Y Y The average number of page faults per second for single-page reads during the reporting interval.

SYSID 08 CHAR System ID for entire report appears in upper right portion of report heading.

Table 21. RSTR - Resource Storage Management Report (continued)


Resource Reports

RSYS - Resource System Information Report

Purpose:

The System Information Report displays hardware and software configuration information. The Collector virtual machine updates the database when it detects a change in the system configuration, or if the Collector is stopped and restarted.

Uses:

This report verifies that applied configuration changes have actually taken place. The contents of the report remain static most of the time since system reconfiguration is done infrequently. It is also a good idea to run this report after an abnormal system termination to obtain the CP abend code.

Note: Candle does not recommend using the COMBINE keyword with this report.

Data Collection Requirements:Appropriate data must be collected as input to this report. Table 33 on page 142 contains the keyword(s) required on the COLLECT statement in the Collector control file in order to produce each report.

FIGURE 48. Sample System Information Report

Short Name: RSYS

Long Name: RSYSINFO

Table 22. RSYS - Resource System Information Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

Abend Code ABNDCODE BYTE 08 CHAR CP abend code (only if previous IPL ended with an abnormal termination).

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 17, 2002 DATA PROCESSED: 10/11/03 12:21 TO 10/11/03 12:28 SYSTEM INFORMATION REPORT WLAVM01 OPERATING SYSTEM: z/VM 4.1 SERVICE LEVEL: 0101 TIME OF IPL: 05/09/03 14:41 CPU MODEL: 2064 TIME OF LAST ABEND: ABEND CODE: REAL STORAGE (GENNED): 64M ACTUAL STORAGE: 64M V=R STORAGE AREA: 0K V=R FREE STORAGE: 0K CP TRACE TABLE: 02K EXPANDED STORAGE: 28M NON-PAGEABLE PAGES: 829 PAGEABLE PAGES: 15684 SIZE OF RESIDENT CP: 1532K LPAR INFORMATION PHYSICAL PROCESSORS: 3 LOGICAL PROCESSORS: 2 LPAR NAME (NUMBER): VMES (3) DISPATCH INTERVAL: DYNAMIC LOGICAL PROCESSORS: 1 2 DISPATCH WEIGHT 100 100 WAIT FLAG NO NO CAPPING NO NO

Resource Reports


Actual Storage<2GB

AREALSTR BYTE 08 FLTD The real storage minus any offline (unusable) storage frames. Applies to storage below 2 GB.

Actual Storage AREALSTG BYTE 08 FLTD The real storage minus any offline (unusable) storage frames. Value is 0 for 32-bit images. Applies to all storage for 64-bit images.

Expanded Storage Size

CPEXPSTR INTG 08 FLTD The number of megabytes of expanded storage attached to this machine.

Size of Resident CP

CPSIZE INTG 08 FLTD The number of bytes occupied by the resident CP.

CP Trace Table CPTRACE INTG 08 FLTD The number of megabytes occupied by the CP trace table.

CPU Model CPUMODEL FLAG 02 UBIN Type of CPU being run (for example: 2064).



Time of IPL IPLTIME 08 STCK Date and time of most recent IPL.

Logical Processor CAPPING status

LPARCAPS FLAG 01 BITF CAPPING status for each LP. Each bit in this byte represents the CAPPING status of the corresponding LP (for example, if bit 3 is on, it indicates that LP 3 has CAPPING set to ON).

Dispatch Interval LPARINTV INTG 02 MSEC The dispatching interval for all LPARs. A data value of x’FFFF’ indicates dynamic.

Logical Processors

LPARLPCT INTG 02 UBIN Number of logical processors assigned to this LPAR.

LPAR Name LPARNAME 08 CHAR Name of this logical partition.

LPAR Number LPARNUM INTG 01 UBIN Number of this logical partition.

Table 22. RSYS - Resource System Information Report (continued)


Resource Reports

Physical Processors

LPARPHYS INTG 02 UBIN Number of CPUs in the physical partition.

Logical Processor WAIT status

LPARWAIT FLAG 01 BITF WAIT status for each LP. Each bit in this byte represents the WAIT status of the corresponding LP (for example, if bit 3 is on, it indicates that LP 3 has its WAIT status set to ON).

Logical Processor 1 Dispatch Weight

LPARWT1 INTG 02 UBIN Weight value for the logical processor. A value of x’FFFF’ indicates a dedicated processor.














Resource Reports




Non-Pageable Pages

NPAGECNT INTG 08 FLTD The number of pages of storage not available for paging.

Operating System

OPSYSREL FLAG 08 BITF Version and release of the host VM operating system.

Pageable Pages PAGECNT INTG 08 FLTD The number of pages of storage available for use by the paging subsystem.

Real Storage<2GB (genned)

REALSTR BYTE 08 FLTD The number of megabytes of storage genned at system gen time. Applies only to storage below 2 GB.

Real Storage (genned)

AREALSTG BYTE 08 FLTD The number of megabytes of storage genned at system gen time. Value is 0 for 32-bit images. Applies to all storage for 64-bit images.

Service Level SERVLVL 08 CHAR Maintenance service level of the host VM operating system.


Time of Last Abend

TERMTIME 08 STCK Date and time of CP abend (only if previous IPL ended with an abnormal termination).

V=R Free Storage

VRFRESZ BYTE 08 FLTD The number of megabytes set aside for virtual machine free storage.

V=R Storage Area

VRSIZE BYTE 08 FLTD The number of megabytes set aside for virtual machines.



Resource Reports

RTDI - Resource Temporary Disk Activity Report

Purpose:

The Temporary Disk Activity Report displays information on the configuration, utilization, and availability of temporary disks.

A temporary disk is used in VM to define a dynamic minidisk that is released when the user terminates the session or detaches the device. Temporary disks allow applications that occasionally require extra disk space to run without requiring the system to permanently assign the space to the user.

The configuration information displayed for each area of temporary disk space includes the real device address, the volume serial number, device type, starting and ending location, and the total number of cylinders or blocks. The utilization information displayed for each area includes the percentage of cylinders or blocks that are being used at the time the Collector sampling was taken. The availability information includes the total number of cylinders or blocks that can be allocated and the largest contiguous area of storage available for allocation.

The report displays information for each area reserved for temporary disks on system-owned volumes only.

Uses:

The Extent Percent Full field can help you determine when the amount of TDISK space needs to be increased. Insufficient TDISK space can become a productivity problem.



FIGURE 49. Sample Temporary Disk Activity Report

Short Name: RTDI

Long Name: RTDISK

EPILOG VM V610 PAGE 1RUN DATE: OCTOBER 18, 2003 DATA PROCESSED: 10/09/03 04:00 TO 10/09/03 04:15 TEMPORARY DISK ACTIVITY REPORT WLAVM01 DEVICE DASD DEVICE DASD EXTENT EXTENT LARGEST TOTAL EXTENT ADDRESS VOLSER TYPE EXTENT COUNT PERCENT FULL EXTENT AVAILABLE---<1>--------<2>----------------------------------------------------------------------------------- 234 VMSY01 3380 300-399 100 23.00 67 77 235 VMSY03 3380 100-399 300 36.00 92 198 340 VMSY02 3380 300-399 100 20.00 49 80 344 VMTD01 3380 400-449 50 21.00 33 39 632 VMTD03 3380 300-349 50 19.00 11 40 633 VMTD02 3380 400-449 50 19.00 17 40---------------------------------------------------------------------------------------------------- 650 23.00 92 79

Resource Reports


Table 23. RTDI - Resource Temporary Disk Activity Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

Extent Count ALLOCCNT INTG 08 FLTD Y Y Y The total number of cylinders or blocks allocated for the temporary disk extent.



Device Address

DEVADDR ADDR 02 SUBI Y Y Real address of the device where the temporary disk is allocated.

Device Type DEVTYPE INTG 04 CHAR Y Y Y Device type of the real device.

DASD Extent ENDCYL INTG 08 FLTD Y Y Y The ending cylinder or block number for the temporary disk extent.

Largest Extent LAREXTAV INTG 08 FLTD The largest number of available cylinders or blocks that could be used to allocate a minidisk during the reporting period.

Extent Percent Full

PERFULL 08 FLTD Y Y Y Percent of space in use at the time of the Collector sampling. If more than one sampling was taken during the reporting interval, this is an average of the sampling percents.


DASD Extent STARTCYL INTG 08 FLTD The starting cylinder or block number for the temporary disk extent.

Total Extent Available

TOTEXTAV INTG 08 FLTD Y Y Y The total number of available cylinders or blocks.

DASD Volser VOLSER INTG 06 CHAR Y Y The volume serial number of the real device.


Resource Reports

RTRA - Resource Transaction Activity Report

Purpose:

The Transaction Activity Report displays information relative to trivial and non-trivial transactions when executed. A trivial transaction is a transaction that can be processed in one CPU time slice. A non-trivial transaction requires two or more time slices.

Information on trivial and non-trivial transactions is displayed separately and includes the count of transactions, the average number of transactions completed per second, and the average number of seconds required to complete each transaction.

Uses:

You can use this report to monitor response time service levels.



FIGURE 50. Sample Transaction Activity Report

Short Name: RTRA

Long Name: RTRAN

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 10, 2003 DATA PROCESSED: 10/09/03 00:00 TO 10/09/03 09:00 TRANSACTION ACTIVITY REPORT WLAVM01 --INTERVAL START-- --------TRIVIAL TRANSACTIONS------- ------NON-TRIVIAL TRANSACTIONS------ DATE TIME COUNT TRANS/SEC RESPONSE COUNT TRANS/SEC RESPONSE--<1>----------------------------------------------------------------------------------------------- 01/09/03 00:00 1723 1.914 .025 137 .152 .287 01/09/03 00:15 1720 1.911 .025 140 .156 .219 01/09/03 00:30 1733 1.926 .023 132 .147 .206 01/09/03 01:00 1754 2.056 .037 19 .022 3.010 01/09/03 01:15 1802 2.002 .028 68 .076 .671 01/09/03 01:30 1759 1.954 .023 103 .114 .319 01/09/03 01:45 1711 1.901 .024 169 .188 .811 01/09/03 02:00 1722 1.913 .025 134 .149 .267 01/09/03 02:15 1722 1.913 .024 139 .154 .259 01/09/03 02:30 1727 1.919 .025 135 .150 .271 01/09/03 02:45 1713 1.903 .025 146 .162 24.399 01/09/03 03:00 1741 1.935 .024 167 .186 .343 01/09/03 03:15 1736 1.929 .022 256 .284 2.305 01/09/03 03:30 1733 1.926 .023 165 .183 .348 01/09/03 03:45 1737 1.930 .022 143 .159 .278 01/09/03 04:00 1738 1.931 .022 148 .164 .263 01/09/03 04:15 1710 1.900 .025 166 .184 2.281 01/09/03 04:30 1710 1.900 .025 195 .217 18.000 01/09/03 04:45 1974 2.193 .022 340 .378 4.064 01/09/03 05:00 2241 2.490 .019 181 .201 .263 01/09/03 05:15 2226 2.473 .019 183 .203 .912 01/09/03 05:30 2242 2.491 .018 158 .176 .290 01/09/03 05:45 2255 2.506 .018 155 .172 .315 01/09/03 06:00 2251 2.501 .018 147 .163 .281 01/09/03 06:15 2239 2.488 .019 188 .209 16.390 01/09/03 06:30 2264 2.515 .018 166 .184 .256 01/09/03 06:45 2226 2.473 .019 180 .200 .269 01/09/03 07:00 2271 2.523 .017 152 .169 .280 01/09/03 07:15 2279 2.532 .018 140 .156 21.958 01/09/03 07:30 2239 2.488 .019 174 .193 5.439 01/09/03 07:45 2250 2.500 .019 149 .166 .275 01/09/03 08:00 2278 2.531 .018 166 .184 .278 01/09/03 08:15 2240 2.489 .018 203 .226 6.513 01/09/03 08:30 2294 2.549 .017 160 .178 6.273 01/09/03 08:45 2269 2.521 .018 175 .194 .289---------------------------------------------------------------------------------------------------- 69229 2.201 .021 5579 .177 3.611

Resource Reports


Table 24. RTRA - Resource Transaction Activity Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF




NTRVCNT INTG 08 FLTD Y Y Y The number of non-trivial transactions that took place during the reporting interval.

Non-Trivial Transactions/ Sec

NTRVRATE 08 FLTD Y The average number of trivial transactions per second during the reporting interval.

Non-Trivial Transactions Response

NTRVRESP 08 FLTD Y Y Y The average number of seconds needed to complete one non-trivial transaction during the reporting interval.


Trivial Transaction Count

TRVCNT INTG 08 FLTD Y Y Y The number of trivial transactions that took place during the reporting interval for uniprocessor virtual machines.

Trivial Transactions/ Sec

TRVRATE 08 FLTD Y Y Y The average number of trivial transactions per second during the reporting interval for uniprocessor virtual machines.

Trivial Transactions Response

TRVRESP 08 FLTD Y Y Y The average number of seconds needed to complete one trivial transaction during the reporting interval for uniprocessor virtual machines.


Resource Reports

RVDS - Resource VDISK Activity Report

Purpose:

The VDISK Activity Report displays information about virtual disk in storage activity and usage. Applications using VDISKs will see a dramatic decrease in wall-clock time for I/O operations, with the side effect of increased CPU utilization and paging activity. All of the standard EPILOG reporting commands and options are available for use with the RVDS report.

See the appropriate chart in “Data Dictionary” on page 201 for information about the fields in the EPILOG RVDS reports. The information in the chart is useful for generating and interpreting EPILOG reports, and for utilizing the OBTAIN facility.

Uses:

The VDISK Activity Report is useful to Performance Analysts to monitor the performance and utilization of VDISK activity.


You must specify “COLLECT VDISK” in your COLLECT CONTROL file to collect EPILOG. VDISK data. The CVOVDATA DCSS must be defined for VDISK collection of EPILOG data to occur.

FIGURE 51. Sample VDISK Activity Report

Short Name: RVDS

Long Name: RVDISK

Table 25. RVDS - Resource VDISK Activity Report

Columm Header

Field Name

Unit Field Length

Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

FBA-512 Blocks

BLOCKS INTG 08 FLTD Y Y Y Number of simulated 512 byte blocks allocated for this V-disk.

Virtual Address DEVADDR ADDR 02 SUBI Y Y The V-disk virtual device address.

EPILOG FOR VM V610RUN DATE: JULY 4, 2003 DATA PROCESSED: 07/01/03 09:00:00 TO 07/01/03 10:00:00 PAGE 1 VDISK RESOURCE REPORT COMBINE (1H) CREATOR VIRTUAL FBA-512 RESIDENT PAGE PAGE PGRDS/ PGWRS/ VIOS/OWNER ADDRESS BLOCKS PAGES READS WRITES SECOND SECOND SECOND LINKS TDISK TIME-------------------------------<1>--------------------------------------------------------------------TDNY00 0192 2048 80.21 143028 9216 39.73 2.56 3.12 1 YES 01:00:00TDNY21 0999 512 24.33 41238 1996 15.91 0.77 4.11 2 NO 00:43:12TDNY26 0490 4096 35.26 8784 4392 2.44 1.22 0.21 8 NO 01:00:00TDNY28 1111 2048 0.00 4042 12312 1.22 3.42 1.95 1 NO 01:00:00------------------------------------------------------------------------------------------------------ 8704 32.45 197082 27916 14.71 2.08 9.39

Resource Reports


Time ELAPSE SECS 08 FLTD Y Y Y Elapsed time during this reporting interval that the V-disk existed.

Links LINKS INTG 08 FLTD Y Y Maximum number of users linked to the V-disk.

PGRDs / Second

PGRDRATE

INTG 08 FLTD Y Y Y Average page read operations (primary plus expanded) per second for this V-disk.

Page Reads PGREADS INTG 08 FLTD Y Y Y Number of page read operations (primary plus expanded) performed for this V-disk.

Page Writes PGWRITES INTG 08 FLTD Y Y Y Number of page write operations (primary plus expanded) performed for this V-disk.

PGWRs / Second

PGWTRATE

INTG 08 FLTD Y Y Y Average page write operations (primary plus expanded) per second for this V-disk.

Resident Pages RESPAGES INTG 08 FLTD Y Y Y Average number of pages (primary plus expanded) resident during the reporting interval.

TDisk TDISK 04 CHAR Y Y Indicates whether this V-disk is a dynamically created temporary disk. The value can be YES or NO.

Creator / Owner

USERID 08 CHAR Y Y Userid of the virtual machine that created or owns the V-disk.

VIOs / Second VIORATE INTG 08 FLTD Y Y Y Average number of virtual I/O operations per second for this V-disk.

Table 25. RVDS - Resource VDISK Activity Report (continued)


Workload Reports

Workload ReportsWorkload reports show the effect that workloads are having on system resources. A workload is one or more virtual machines, guest machines, users, or user IDs. For example, a single MVS guest system is a workload, or all service virtual machines may be grouped into a workload.

A list of all the workload reports follows.

“WBOT - Workload Bottleneck Analysis Report” on page 125

“WCPU - Workload CPU Report” on page 128

“WICO - Workload IUCV/VMCF Communications Activity Report” on page 130

“WSTO - Workload Paging/Storage Report” on page 132

“WTRA - Workload Transaction Activity Report” on page 137

“WSUM - Workload Summary Report” on page 135

WBOT - Workload Bottleneck Analysis Report

Purpose:The Workload Bottleneck Analysis Report provides wait-state information for one or more virtual machines.

By default, the collection of wait-state data is turned off in the Collector control file because of the resources required to collect this data. When you need to collect wait-state data, you can limit the amount of data being collected by selecting a subset of user IDs, or by grouping user IDs into one record per interval. The USERGROUP, DISTGROUP, and ACCTGROUP keywords are not supported on this report.

Uses:

Use this report as a first step in determining why a workload is not meeting its service level objective. The report will point to the resources that should be examined further.



FIGURE 52. Sample Workload Bottleneck Analysis Report

Short Name: WBOT

Long Name: WBOTA

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 10, 2003 DATA PROCESSED: 10/09/03 09:00 TO 10/09/03 09:15 WORKLOAD BOTTLENECK ANALYSIS REPORT WLAVM01 VM %CPU % % %SVM %PG %CF %SIM %CPU +-------------I/O WAITS------------+ SAMPLEWORKLOAD BUSY OTHER IDLE WAIT WAIT WAIT WAIT WAIT |DEV % |DEV % |DEV % |DEV % |DEV % | COUNT-<1>---------------------------------------------------------------------------------------------MVSD 22.2 1.0 51.7 .0 1.0 .0 .0 22.4 |16B .5|331 .1| 0 .1| 0 .0| 0 .0| 875------------------------------------------------------------------------------------------------- 22.2 1.0 51.7 .0 1.0 .0 .0 22.4 875

Workload Reports


Table 26. WBOT - Workload Bottleneck Analysis Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF




% CPU Busy USEDCPUP 08 FLTD Y Y Y The percentage of time this workload was using the CPU.

% CF Wait WAITCFSP 08 FLTD Y The percentage of time this workload was in a console function wait state.

% CPU Wait WAITCPUP 08 FLTD Y Y Y The percentage of time this workload was in a CPU wait state.

% Idle WAITIDLP 08 FLTD Y Y Y The percentage of time this workload was idle during the reporting interval.

% SVM Wait WAITIDSP 08 FLTD Y Y Y The percentage of time this workload was idle due to a service machine wait.

% Other WAITOTHP 08 FLTD Y Y Y The percentage of time this workload was in wait state other than those mentioned above.

% Page Wait WAITPAGP 08 FLTD Y Y Y The percentage of time this workload was found in a page wait state.

% Sim Wait WAITSIMP 08 FLTD Y Y Y The percentage of time this workload was in an instruction simulation wait state.

I/O Waits Dev (1)

WBODEV1 ADDR 02 SUBI The device address of the device with the highest I/O wait percent for this workload.


Workload Reports

I/O Waits % (1)

WBODEV1P 08 FLTD Y Y Y The I/O wait percent of the device with the highest I/O wait percent for this workload.

I/O Waits Dev (2)

WBODEV2 ADDR 02 SUBI The device address of the device with the second highest I/O wait percent for this workload.

I/O Waits % (2)

WBODEV2P 08 FLTD Y Y Y The I/O wait percent of the device with the second highest I/O wait percent for this workload.

I/O Waits Dev (3)

WBODEV3 ADDR 02 SUBI The device address of the device with the third highest I/O wait percent for this workload.

I/O Waits % (3)

WBODEV3P 08 FLTD Y Y Y The I/O wait percent of the device with the third highest I/O wait percent for this workload.

I/O Waits Dev (4)

WBODEV4 ADDR 02 SUBI The device address of the device with the fourth highest I/O wait percent for this workload.

I/O Waits % (4)

WBODEV4P 08 FLTD Y Y Y The I/O wait percent of the device with the fourth highest I/O wait percent for this workload.

I/O Waits Dev (5)

WBODEV5 ADDR 02 SUBI The device address of the device with the fifth highest I/O wait percent for this workload.

I/O Waits % (5)

WBODEV5P 08 FLTD Y Y Y The I/O wait percent of the device with the fifth highest I/O wait percent for this workload.

VM Workload

WORKLOAD 08 CHAR Y Y One or more virtual machines grouped by user ID, account code, or distribution code.

Table 26. WBOT - Workload Bottleneck Analysis Report (continued)

Workload Reports


WCPU - Workload CPU Report

Purpose:

The Workload CPU Report displays information on CPU utilization by users or groups of users.The report shows CPU utilization in two ways:

® CPU Percent shows the percentage of CPU resources used by a workload.

® CPU Seconds shows the seconds of CPU used by a workload.

The report further breaks down CPU usage into its CP, virtual, and vector components.

Notes: The COMBINE keyword effects CPU percentages as follows:

– If COMBINE is specified, each workload’s CPU utilization is expressed as a percentage of the sum total of the interval time of all the active workloads during the combine interval. The total of all workloads for the interval may exceed 100% if more than one CPU in the complex is active during the combine interval.

– If COMBINE is not specified, each workload’s CPU utilization is expressed as a percentage of the interval time that the workload was found active.

Uses:

Use the Workload CPU Report to isolate bottlenecks in CPU availability. Sort the output by CPU percentage in descending order to quickly view the users who consumed the most CPU cycles.

It is helpful to use the REPORTIF keyword to show only those users who consume an excessive percentage of the CPU.

Examine the session time to analyze the impact that a user has on the system. For example, if the CPU percentage for a user was 10% for a reporting interval, yet the session time was half that of the reporting period, then the user actually used 20% of the CPU while the user was logged on.



Short Name: WCPU

Long Name: WCPU


Workload Reports

FIGURE 53. Sample Workload CPU Report

Table 27. WCPU - Workload CPU Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

CP Percent CPPCT 08 FLTD Y Y Y Percent of total CPU used by the system to manage this workload.

CP Seconds CPSECS SECS 08 FLTD Y Y Y Total CP seconds used by this workload (to nearest second).

CPU Percent CPUPCT 08 FLTD Y Y Y Percent of total CPU utilized by this workload.

CPU Seconds CPUSECS INTG 08 FLTD Y Y Y Total CPU seconds used by this workload (to nearest second).



EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 10, 2003 DATA PROCESSED: 10/09/03 09:00 TO 10/09/03 09:15 WORKLOAD CPU REPORT WLAVM01 VM CPU CP VIRTUAL CPU CP VIRTUAL SESSION WORKLOAD PERCENT PERCENT PERCENT SECONDS SECONDS SECONDS TIME --<1>-------------------------------------------------------------------------------------- $VCOLLHP 2.54 1.86 .68 22.84 16.75 6.09 00:15:00 CMSBATCH .00 .00 .00 .00 .00 .00 00:15:00 CPRM .00 .00 .00 .00 .00 .00 00:15:00 DATAMOVE .04 .01 .03 .37 .12 .25 00:15:00 DCSP29 .00 .00 .00 .00 .00 .00 00:15:00 DEV 5.49 1.88 3.61 49.41 16.93 32.48 02:30:00 DIRMAINT .07 .04 .04 .65 .32 .33 00:15:00 DISKACNT .00 .00 .00 .00 .00 .00 00:15:00 DOSRES 11.27 6.61 4.66 101.44 59.50 41.94 00:15:00 GCS .00 .00 .00 .03 .03 .00 00:15:00 GCSTEST .00 .00 .00 .03 .03 .00 00:15:00 ISPVM .00 .00 .00 .00 .00 .00 00:15:00 OPERATOR .63 .18 .45 5.69 1.64 4.05 00:15:00 OPERSPOV .37 .25 .12 3.33 2.27 1.05 00:15:00 OPERVSE .25 .25 .01 2.28 2.22 .06 00:15:00 OPERVTAM .86 .41 .45 7.70 3.68 4.01 00:15:00 PVM 1.59 .77 .82 14.35 6.95 7.40 00:15:00 PVM2 4.40 .23 4.17 39.58 2.05 37.53 00:15:00 PVM3 4.38 .22 4.16 39.40 1.95 37.45 00:15:00 RSCS 5.45 .83 4.62 49.02 7.45 41.57 00:15:00 SMART 2.02 1.77 .24 18.14 15.96 2.17 00:15:00 STSP01 1.38 .97 .41 12.40 8.71 3.69 00:15:00 SYSTEM .00 .00 .00 .00 .00 .00 00:00:00 TDBB04 .00 .00 .00 .00 .00 .00 00:15:00 TDNYCICS .31 .07 .24 2.77 .63 2.13 00:06:00 VCOLLECT 2.64 1.89 .75 23.78 17.04 6.74 00:15:00 VMUTIL .03 .01 .02 .30 .09 .20 00:15:00 . . . . . . . . . . . . . . . . . . . . . . . . ------------------------------------------------------------------------------------------- 65.44 20.21 45.23 588.98 181.93 407.05 07:00:00

Workload Reports


WICO - Workload IUCV/VMCF Communications Activity Report

Purpose:

The Workload IUCV/VMCF Communications Activity Report provides information on IUCV (Inter-User Communication Vehicle) and VMCF (Virtual Machine Communication Facility) activity for one or more virtual machines. IUCV transfers data between two virtual machines, and between a virtual machine and the CP system service. VMCF transfers data between two virtual machines only.

The information on the report includes IUCV and VMCF transfer counts and error percents for each user.

Uses:

Use this report to find out which workloads are utilizing the most IUCV and VMCF resources. If the workload (SQLDS for example) is over-utilized, you might want to configure another workload to offset the number of IUCV or VMCF calls.

Session Time SESSTIME SECS 08 FLTD Y Y Total time this workload was logged on (to nearest second).


Virtual Percent VIRTPCT 08 FLTD Y Y Y Percent of virtual CPU utilization for the workload specified.

Virtual Seconds VIRTSECS SECS 08 FLTD Y Y Y Total virtual CPU seconds used by this workload (to nearest second).

Vector Seconds WKLVECTO MSEC 8 FLTD Y Y Y The number of seconds used in the vector facility by this workload.

Vector Overhead

WKLVECTU MSEC 8 FLTD Y Y Y The number of seconds used to load and unload the vector facility for this workload.

VM Workload WORKLOAD

08 CHAR Y Y User or group of users specified by GROUP keyword.

Short Name: WICO

Long Name: WICOM

Table 27. WCPU - Workload CPU Report (continued)


Workload Reports



FIGURE 54. Sample Workload IUCV/VMCF Communications Activity Report

Table 28. WICO - Workload IUCV/VMCF Communications Activity Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF




IUCV Source Xfers

WKLISEVM INTG 08 FLTD Y Y Y The number of IUCV data transfers that were sent by this virtual machine during this reporting interval.

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 10, 2003 DATA PROCESSED: 10/09/03 09:00 TO 10/09/03 09:15 WORKLOAD IUCV/VMCF COMMUNICATIONS ACTIVITY REPORT WLAVM01 VM ------------- I U C V -------------- ------------- V M C F ------------ WORKLOAD SOURCE XFERS TARGET XFERS % ERR SOURCE XFERS TARGET XFERS % ERR-<1>---------------------------------------------------------------------------------------$VCOL 0 0 .0 0 0 .0CMSBATR5 0 0 .0 0 0 .0CVGEN 0 0 .0 0 0 .0DEV 0 0 .0 0 0 .0DISKACNT 0 0 .0 43 43 .0GRICFOIL 0 0 .0 95 95 .0ISPVM 0 0 .0 0 0 .0MVS 0 0 .0 0 0 .0MVSD 0 0 .0 0 0 .0OMGEN 0 0 .0 0 0 .0OPERATOR 0 0 .0 0 0 .0OPERV 0 0 .0 0 0 .0PVM 0 0 .0 124 66 .0PVM 0 0 .0 196 3 .0PVM2 0 0 .0 0 0 .0PVM3 0 0 .0 0 0 .0RSCS 0 0 .0 0 19 .0RTMSF 0 0 .0 47 47 .0SYSDUMP1 0 0 .0 0 0 .0SYSTEM 0 0 .0 72 0 .0TDQMWP02 0 0 .0 0 0 .0V/SIE 0 0 .0 0 0 .0VCOL 532 532 .0 0 0 .0VMSPR6 0 0 .0 0 0 .0VMUTIL 0 0 .0 0 0 .0VMTST 0 0 .0 0 0 .0BATC 0 0 .0 0 0 .0REPRT 0 0 .0 0 0 .0------------------------------------------------------------------------------------------- 532 532 .0 577 273 .0

Workload Reports


WSTO - Workload Paging/Storage Report

Purpose:

The Workload Paging/Storage Report shows how much of the paging and storage resources are being used by the workloads.

Uses:

In most VM systems, the largest contributor to poor performance is the paging subsystem. Excessive paging causes I/O operations to take longer, as well as reduce the amount of CPU available to users. The Workload Paging/Storage Report can be used to determine how workloads affect the paging subsystem.

Key items to look at are working set size and resident pages. Generally, users with large working set sizes have more impact on the paging system than users with smaller working set

IUCV Target Xfers

WKLISTVM INTG 08 FLTD Y Y Y The number of IUCV data transfers that were received by this virtual machine during this reporting interval.

IUCV % Err WKLIUCVE 08 FLTD Y Y Y The percent of errors for IUCV for this virtual machine during this reporting interval.

VMCF % Err WKLVMCFE 08 FLTD Y Y Y The percent of errors for VMCF for this virtual machine during this reporting interval.

VMCF Source Xfers

WKLVSEVM 08 FLTD Y Y Y The number of VMCF data transfers sent by this virtual machine during this reporting interval.

VMCF Target Xfers

WKLVSTVM INTG 08 FLTD Y Y Y The number of VMCF data transfers received by this virtual machine during this reporting interval.

VM Workload WORKLOAD 08 CHAR Y Y One or more user IDs. Multiple user IDs can be grouped by user ID, account code, or distribution code.

Short Name: WSTO

Long Name: WSTORAGE

Table 28. WICO - Workload IUCV/VMCF Communications Activity Report (continued)


Workload Reports

sizes. The number of resident pages shows the actual number of pages that were in memory for each user at the time of the sampling. Normally, the working set size and resident pages are close. The exceptions are when a user has been dormant for a while and has few or no pages in storage. The other exception is when a user has V=R or locked pages assigned.



FIGURE 55. Sample Workload Paging/Storage Report

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 10, 2003 DATA PROCESSED: 10/09/03 13:40 TO 10/09/03 13:44 WORKLOAD PAGING/STORAGE REPORT WLAVM01 VM WORKING SET RESIDENT PAGE PAGE PAGE ------EXPANDED STORAGE------ STORAGE WORKLOAD SIZE(PAGES) PAGES RATE/SEC READS WRITES PAGING DEDICATED MOVEMENT SIZE IN K---<1>--------------------------------------------------------------------------------------------------------- $VCOLLVM 10 214 .02 346 377 2 0 4 6144 BOOKMGR 54 54 .01 47 176 0 0 1 4096 CLSS07 84 23 .09 2012 1865 5 0 12 3072 CMSBATR5 31 0 .01 127 150 0 0 0 4096 DISKACNT 87 85 .15 3193 3179 6 0 65 4096 EREP 36 0 .00 0 36 0 0 0 4096 GCS 92 91 .07 1534 1358 5 2 45 12288 GRICFOIL 36 0 .00 0 36 0 0 0 4096 GRICSERV 853 985 .02 299 550 1 0 2 14336 ISPVM 50 46 .03 629 527 3 1 31 3072 OMGEN 36 0 .00 0 36 0 0 0 4096 OPERATOR 49 16 .04 0 97 1 0 4 2048 OPERV 36 0 .00 0 36 0 0 0 4096 PVM 86 3 .02 428 439 0 0 2 8192 PVM 57 11 .04 769 999 2 0 3 6144 PVM2 50 6 .03 549 671 1 0 2 12288 PVM3 41 3 .02 369 524 1 0 2 2048 RSCS 149 146 .05 22 135 18 1 23 8192 TDNY03 97 3 .05 777 825 3 0 5 4096 TDNY12 94 26 .11 1187 1306 8 0 21 4096 TDNY43 97 28 .05 33 0 21 0 71 4096 TDNY54 90 21 .25 456 519 17 0 41 4096 TDOV23 86 11 .12 671 771 6 0 13 4096 TDOV23 68 13 .13 1905 1931 7 0 18 4096 TDOV24 102 2 .04 629 655 2 0 4 4096 TDOV33 76 18 .13 1272 1995 10 0 25 4096 TDOV64 53 8 .06 956 985 4 0 11 4096 TDOV64 63 4 .06 336 334 5 0 10 4096 TDOV79 79 61 .20 115 320 10 0 36 4096 TDOV89 95 3 .04 676 634 2 0 4 4096 TDQM02 90 7 .08 969 813 6 0 14 4096 TDQM03 94 7 .04 219 251 3 0 6 4096 TDQM08 70 8 .07 1116 940 4 0 10 4096 TDQM72 86 12 .07 808 721 6 0 16 4096 TSGM01 81 25 .08 930 1163 5 0 12 4096 TSGM11 96 32 .14 1032 805 9 0 20 4096 TSGM54 80 28 .06 1092 1045 6 0 11 4096 TSGM84 154 145 .10 54 89 8 0 48 4096 . . . . . . . . . . . . . . . . . . . . TSNY78 49 1 .02 180 410 1 0 2 4096 VMUTIL 343 328 .00 0 0 0 0 0 6144 VTAM 38 22 .02 322 327 6 0 24 3072 BATC 0 0 .00 0 0 0 0 0 0 1FB 89 6 .03 279 394 2 0 6 4096 3CGM 76 25 .12 253 318 6 0 12 4096 4FHF 49 0 .02 308 424 1 0 2 4096--------------------------------------------------------------------------------------------------------------- 93 27 86.76 62562 75335 4 0 13 7062

Workload Reports


Table 29. WSTO - Workload Paging/Storage Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF




Page Rate/Sec PAGERATE 08 FLTD Y Y Y The rate of page-ins and page-outs for this workload (in pages/sec.).

Page Reads PAGREADS INTG 08 FLTD Y Number of page reads over the specified period of time.

Page Writes PAGWRTS INTG 08 FLTD Y Y Y Number of page writes over the specified period of time.

Resident Pages

RESPAGES 08 FLTD Y Y Y The current number of pages physically in main storage for this workload.

Storage Size in K

STORSIZE BYTE 08 FLTD Y Y Y Average storage size for this workload.

Exp Stor Attached

WKLXATT INTG 08 FLTD Y Y Y The number of megabytes of expanded storage attached to this workload.

Exp Stor Movement

WKLXMOV INTG 08 FLTD Y Y Y The number of expanded pages moved for this workload.

Exp Stor Paging

WKLXPAG INTG 08 FLTD Y Y Y The number of expanded storage blocks allocated to this workload by CP for paging.

VM Workload WORKLOAD 08 CHAR Y Y User or group of users specified by GROUP keyword.

Working Set Size(Pages)

WSS 08 FLTD Y Y Y A user’s projected working set size. This value is calculated each time a user drops from queue, and is based on the number of pages referenced during the last stay in queue.


Workload Reports

WSUM - Workload Summary Report

Purpose:

The Workload Summary Report shows summary information about the four major resource concerns: CPU, I/O, paging, and storage.

Notes: The COMBINE keyword effects CPU percentages as follows:

– If COMBINE is specified, each workload’s CPU utilization is expressed as a percentage of the sum total of the interval time of all the active workloads during the combine interval. The total of all workloads for the interval may exceed 100% if more than one CPU in the complex is active during the combine interval.

– If COMBINE is not specified, each workload’s CPU utilization is expressed as a percentage of the interval time that the workload was found active.

Uses:

It is helpful to use the Workload Summary Report in conjunction with the resource reports. For example, if you found a bottleneck with a particular resource, you could use this report to isolate that bottleneck to a particular user. Sort the report by the problem area to quickly find the workload that is causing the bottleneck.

The working set size(pages) is used by the VM scheduler to assign a dispatch priority to a user. In general, a smaller working set size enables a user to obtain CPU resources faster than a user with a large working set size. The performance of a specific user or group can be affected by either changing the working set size for that user or, a much easier task, changing the scheduler bias associated with the working set size.

Session time for a user should be examined when trying to analyze the impact that the user has on the system. For example, if the CPU percentage for a user was 10% for a reporting interval, yet the session time was half that of the reporting period, then the user actually used 20% of the CPU while the user was logged on.

Data Collection Requirements:Appropriate data must be collected as input to this report. Table 33 on page 142 contains the keyword(s) required on the COLLECT statement in the Collector control file in order to produce each report.

Short Name: WSUM

Long Name: WSUMMARY

Workload Reports


FIGURE 56. Sample Workload Summary Report

Table 30. WSUM - Workload Summary Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF





Page I/O Count PAGIOCNT INTG 08 FLTD Y Y Y Total page transfers.

Session Time SESSTIME SECS 08 FLTD Y Y Total logon time for this workload (to nearest second).

SPOOL I/O Count

SPLIOCNT INTG FLTD Y Y Y Total I/O count for all unit record devices for this workload.

EPILOG FOR VM V610 PAGE 1RUN DATE: OCTOBER 19, 2003 DATA PROCESSED: 10/05/03 07:00 TO 10/05/03 07:59 COMBINE(1H) WORKLOAD SUMMARY REPORT WLAVM01 VM CPU TOTAL I/O PAGE I/O WORKING SET SPOOL I/O DASD I/O UNIT REC I/O OTHER I/O SESSIONWORKLOAD PERCENT COUNT COUNT SIZE(PAGES) COUNT COUNT COUNT COUNT TIME-<1>------------------------------------------------------------------------------------------------------$VCOLLVM 1.60 213 20 125 70 146 0 67 01:00:00BATCH .04 0 1 21 5 0 0 0 01:00:00BOOKMGR .00 25 0 46 0 24 0 1 01:00:00CLSS07 1.28 11 18 115 0 10 0 1 01:00:00CMSBATR5 .00 0 0 290 0 0 0 0 01:00:00CS .00 0 1 1 5 0 0 0 01:00:00CVGEN .00 0 1 415 5 0 0 0 01:00:00DATAM4 .02 496 0 24 453 48 0 448 01:00:00DCCS11 .00 0 0 30 0 0 0 0 01:00:00DEV .00 0 6 88 0 0 0 0 03:15:00DGTMASTR .00 0 1 13 5 0 0 0 01:00:00DIRM4 .02 203 15 95 23 198 0 5 01:00:00DISKACNT .01 199 1 24 0 199 0 0 01:00:00DOS 4.44 35098 75 669 1 13834 0 21264 03:00:00EREP .02 411 0 17 0 411 0 0 01:00:00GCS .00 0 0 1 0 0 0 0 01:00:00GCSTEST .00 0 0 13 0 0 0 0 01:00:00GRICFOIL .02 148 0 59 0 120 0 28 01:00:00GRICSERV .17 1676 51 168 28 1663 0 13 01:00:00OMGEN .00 0 1 1 5 0 0 0 01:00:00OPERATOR .00 0 0 1 71 0 0 0 01:00:00OPERX 1.01 698 0 94 0 0 0 698 01:00:00PUBSAUTH .00 0 0 44 0 0 0 0 01:00:00RSCS .00 0 0 88 0 0 0 0 01:00:00STATGS1 .30 742 0 163 0 0 0 742 00:56:00SYSTEM .00 0 27 0 0 0 0 0 01:00:00TAPOPRVM .00 0 0 48 5 0 0 0 01:00:00VMUTIL 18.49 8 0 194 0 4 0 4 01:00:00VTAM 8.71 10975 0 507 0 0 0 10975 01:00:00VTAMTEST 1.34 10829 0 277 0 0 0 10829 01:00:00BATC .00 0 0 27 0 0 0 0 01:00:00----------------------------------------------------------------------------------------------------- 37.47 61732 218 147 676 16657 0 45075 35:11:00


Workload Reports

WTRA - Workload Transaction Activity Report

Purpose:

The Workload Transaction Activity Report provides information on transaction response time for one or more users. The information includes the response time, number of transactions per second, and transaction counts for each user or group of users. The information is displayed separately for trivial and non-trivial transactions.

Because of the large quantity of data collected for transaction analysis, you are urged to select a subset of user IDs, or group user IDs into one record per interval in the Collector control file. The USERGROUP, DISTGROUP, and ACCTGROUP keywords are not supported on this report.

Uses:

Use this report to help determine if the various workloads are meeting their service level objectives.

Total I/O Count TOTIOCNT INTG 08 FLTD Y Y Y Total number of I/O requests over the specified interval.

DASD I/O Count

WKLVDIO INTG 08 FLTD Y Y Y The number of virtual start I/Os issued to DASD devices by this workload during this reporting interval.

Other I/O Count

WKLVOIO INTG 08 FLTD Y Y Y The number of I/Os issued to other devices by this workload during this reporting interval.

Unit Record Count

WKLVUIO INTG 08 FLTD Y Y Y The number of virtual Start I/Os issued to unit record devices by this workload during this reporting interval.

VM Workload WORKLOAD 08 CHAR Y Y User or group of users specified with GROUP keyword.


WSS 08 FLTD Y Y Y Average working set size for this workload.

Short Name: WTRA

Long Name: WTRAN

Table 30. WSUM - Workload Summary Report (continued)

Workload Reports




FIGURE 57. Sample Workload Transaction Activity Report

Table 31. WTRA - Workload Transaction Activity Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF






NTRVRATE 08 FLTD Y Y Y The average number of trivial transactions per second during the reporting interval for this workload.


NTRVRESP 08 FLTD Y Y Y The average number of seconds needed to complete one non-trivial transaction during the reporting interval for this workload.


EPILOG FOR VM V610 PAGE 1 RUN DATE: OCTOBER 10, 2003 DATA PROCESSED: 10/08/03 16:15 TO 10/08/03 16:30 WORKLOAD TRANSACTION ACTIVITY REPORT WLAVM01 VM ---TRIVIAL TRANSACTIONS----- ----NON-TRIVIAL TRANSACTIONS---- WORKLOAD COUNT TRANS/SEC RESPONSE COUNT TRANS/SEC RESPONSE-------<1>---------------------------------------------------------------------------- TDOV02 0 .000 .000 3 .003 30.352 TDOV03 21 .023 .155 21 .023 17.219 TDOV04 28 .031 .136 10 .011 4.800 TDOV10 4 .004 .171 10 .011 13.145 TDOV11 6 .007 .097 289 .321 .394-------------------------------------------------------------------------------------- 59 .013 .141 333 .074 2.240


Workload Reports


TRVCNT INTG 08 FLTD Y Y Y The number of trivial transactions that took place during the reporting interval for this workload.


TRVRATE 08 FLTD Y Y Y The average number of trivial transactions per second during the reporting interval for this workload.


TRVRESP 08 FLTD Y Y Y The average number of seconds needed to complete one trivial transaction during the reporting interval for this workload.


User Request Log


User Request LogThe user request log (also called the input and message log) is a quick way to find syntax errors. The Reporter produces a log each time you run the EPILOG Reporter. For each report run, the log documents the following:

® every command entered

® all error messages

® number of records read

® number of records selected

® number of records rejected and the rejection reasons

® start date and time

® end date and time

The Reporter writes the user log to disk. You have the option of printing it, viewing it, or editing it. The user log is defined by a FILEDEF statement in the EVREPT EXEC. The default name of the user log file is:

fn LOG A\

Figure 58 shows the general form of the User Request Log.

FIGURE 58. User Request Log Format

The first line of each page contains the date the reports were produced, the product name and version, and the page number. Each command that is read from the command file creates an entry in the user log. An asterisk in column 1 indicates an error message.

To see a typical log, refer to Figure 59.

fn The EVREPT EXEC uses the filename of the command file as the filename of the user log. This lets you easily associate each user log with the command file to which it pertains.

Run Date MM/DD/YY EPILOG for VM V610 User Request Log Page 1 Command text* ERROR messages, if anyDEFAULTS, that apply to this commandSORT SEQUENCE, if applicablexxxx Records Read xxxxxx SelectedFunction Start date time End date time Command text


User Request Log

FIGURE 59. Typical User Log

Table 32 shows the information that is documented in the user log for each EPILOG command.

Table 32. User Request Log Summary

Command Text Error Msg Default Sort Seq Records Read

Function Start End

REPORT X X X X X X

SET X X

ACCUM X X X

OBTAIN X X

CONTROL X X X

PAGESEP X X

PRODUCTS X X

ZAPS X X

EPILOG FOR VM - CANDLE CORPORATION COPYRIGHT 1987, 1991, 1995, 2002, 2003 WORK BY CANDLE CORPORATION. ALL RIGHTS RESERVED. USE PERMISSIBLE BY LICENSE ONLY. 05-051669-04397-03EPILOG FOR VM INPUT AND MESSAGE LOG V610 1/03/03 19.32.23 PAGE 1COPYRIGHT (C) 1987, 1991, 1995, 2002, 2003 CANDLE CORP.SET TITLE ‘DASD REPORT FOR YESTERDAY BETWEEN 2 AND 3 PM’SET TITLE2 ‘THIS REPORT IS SORTED BY VOLSER AND THEN DASD I/O REQUESTS’SET SORTBY(VOLSER(A),DASDBUSY(D))SET STIME(14) ETIME(15)REPORT RDAS CMB(1H) SDATE(-1) DEFAULT: BAND DATEFORM(MMDDYY) 320 RECORDS READ 320 SELECTED FUNCTION START 10/03/03 19:32:22 END 19/03/03 19:32:23END

Collector Keywords Needed for Reports


Collector Keywords Needed for ReportsYou must enter the appropriate keywords in the Collector control file in order to run a particular report. The table below contains the following information:

® the short name for each report® the keyword(s) needed on the COLLECT/INCLUDE statement in order to collect data for

the report® whether or not MONDCSS must be installed in order to collect data for the report

Table 33. Collector Keyword Requirements

Report COLLECT Keyword MONDCSS

GRPD GROUP (Include USERID, ACCT, or DISTRIB list.)

RBOT SYSTEM X

RCHP CHANNEL X

RCPU SYSTEM X

RDAS DEVICE

REXP STORAGE X

RFRE STORAGE X

RHLS SYSTEM X

RICO SYSTEM X

RLPR SYSTEM

RNSS STORAGE X

RPAG DEVICE

RSCH SYSTEM X

RSEE SEEKS (Include device, type, volume or ALL.) X

RSPO DEVICE

RSTR STORAGE X

RSYS SYSTEM X

RTDI DEVICE

RTRA SYSTEM X

RVDS VDISK

WBOT BOTTLENECK

WCPU ACCOUNT, USERID, DISTR

WICO ACCOUNT, USERID, DISTR

WSTO ACCOUNT, USERID, DISTR

WSUM ACCOUNT, USERID, DISTR

WTRA TRANSACTION X

Producing Graphs 143

Producing Graphs

This chapter describes the three methods available for generating graphic output from EPILOG data.® Use the REPORT command with the GRAPH keyword to generate a graph from within

EPILOG.

® Create a sequential file with the OBTAIN command, and then use GDDM/ICU™ to generate a graph using the sequential file as input.

® Create a sequential file with the OBTAIN command, and then use a PC software package to generate a graph using the downloaded sequential file as input.

Chapter ContentsGenerating Character Graphs from within EPILOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Using MAXSCALE with GRAPH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Generic Report Format for Trend Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Examples of Trend Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Generating Graphs with GDDM/ICU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Multi-line Chart of CPU Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Multi-line Chart of Logged-on Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Line Chart of Paging Device Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Line Chart of Resource Availability Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Scatter-line Chart of Paging Rate/CPU Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Bar Chart of DASD Device Activity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Bar Chart of Ten Most Active DASD Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Pie Chart of Wait Reasons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Stacked Bar Chart of Wait Reasons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Using GDDM/ICU to Generate Sample Charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Generating Graphs On a PC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Using OBTAIN to Extract Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Downloading the OBTAIN Output File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Sample Graphs Generated on a PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Extracting Data with EVOBT EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

5


Running the EVOBT EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170OBTAIN Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171OBTAIN Command Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

report-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172date-range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173time range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173BAND|RANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173COMBINE(nnc) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173REPORTIF(element(relation value units), ...) . . . . . . . . . . . . . . . . . . . . . . . . . . . 173SELECTIF(element(relation value units), ...) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173SUMMARY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173SYSTEMID(cccccccc) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174ELEMENTS(field-name, ...) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174IPREFIX(prefix) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174OUTFILE(fn ft fm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174FORMAT(INT|COL|PC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174REPLACE|APPEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175TIMEZONE(+/-nnnn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Output Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Output Files Generated by FORMAT(INT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Output Files Generated by FORMAT(COL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Output Files Generated by FORMAT(PC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Command File Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179


Generating Character Graphs from within EPILOG

Generating Character Graphs from within EPILOGEPILOG for VM lets you graph certain data to detect trends in system usage. Trend graphs are particularly useful to view data that covers long periods.

To print a graph on a mainframe printer, use the GRAPH keyword with the REPORT command. See “Examples of Trend Graphs” on page 148.

Only certain data can be graphed. See “Data Dictionary” on page 201 to find which data elements can be graphed for each report.

You cannot use the GRAPH keyword with the SORTBY or SUMMARY keywords.

Using MAXSCALE with GRAPHThe MAXSCALE keyword, which sets the maximum scale for the Y-axis of the graph, is only used with the GRAPH keyword.

If a graph report takes several pages, the Y-axis may vary from page to page, depending on the maximum Y-axis value for a page. MAXSCALE sets the maximum Y-axis value so that reports spanning several pages have a constant Y-axis value. If MAXSCALE is exceeded, the point where it is exceeded is marked with double plus (++) signs and the Reporter prints the actual value below the graph.

Generic Report Format for Trend GraphsThe boxed objects in Figure 60 on page 146 denote variable data that can be found in a graph. If a variable data item is not valid for a specific graph, that area of the graph is left blank.



FIGURE 60. Generic Graph Layout

The following information describes the data that may appear on a graph.

TITLES Titles you entered with the TITLE, TITLE2, or TITLE3 keywords of the REPORT or SET command.

# Page number of the report. If a single REPORT command generates multiple graphs, each graph appears on a separate page and is sequentially numbered.

date time The three dates are, respectively, the date the graph was printed, the date and time of the first record processed, and the date and time of the last record processed.

CMB( ) The combine period used to establish an observation. This is the unit of measure for the X-axis. If you did not specify combine in the REPORT or SET command, then this field is blank.

EPILOG for VM V610 first user TITLE line Page #

subsequent TITLE lines

Run Date: date Data Processed: date time To date time CMB ( )

Where: SYSTEMID ( ) graph identifier

report standard title

operand

Y-axisscale time continuity bar

g vr aa rp ih a b l e

sca le

graph displayline or bar chart

time scale data

MAXSCALE of nn was exceeded, The maximum value

observed was NNN on date at time



SYSTEMID() This only appears if the SYSTEMID keyword is used.

graph identifier This identifies what is being graphed. For example, if you are graphing DASIOREQ (Total I/O Requests), this identifies the device that the graph pertains to.

report standard title Name of the report and the graph variable.

operand USERGROUP, ACCTGROUP, or DISTGROUP, if used. Applicable to Workload Reports only.

Y-axis scale Multiplier for Y-axis values. For example, times 10 indicates multiply all Y-axis values by 10.

time continuity bar A visual aid to show X-axis time scale discontinuity.

The four symbols that can appear on the line have the following meanings:

|-----| Denotes that average to long time periods of continuous graphic output appear below.

H Denotes short periods of graphic output.

blank Denotes that breaks in graphic output appear below. These breaks are caused by a break in time requested by the REPORT command.

M Denotes that breaks in graphic output appear below. These breaks are caused by missing data. However, breaks at the beginning or end of the reporting period are indicated by graphic output starting after starttime and/or ending before endtime.

graph variable The report element being graphed.

scale Units for the Y-axis. The Reporter sets the maximum Y-axis value according to the highest value being reported unless you use the MAXSCALE keyword to set the maximum Y-axis value.

graph display The actual graph. The graph may be a line graph or vertical bar chart, depending on which you chose. The Reporter determines the size of the graph according to how many lines are left after all header, title, scale, and footer lines have been used from the defined PAGESIZE (see PRTCNTL).

time scale data The time and date covered by observations. The time scale is three lines:® start time of the observation (hour and minute)® end time of the observation (hour and minute)® date of the observation (month and day, but in DATEFORM order)

nnn MAXSCALE values. Only appears when the largest value exceeds MAXSCALE.

NNN The maximum value observed.

date The date when the Reporter observed the maximum value.

time The time when the Reporter observed the maximum value.



Examples of Trend GraphsIn line graphs, actual data points are plotted as asterisks (*), while connecting lines are plotted with periods.

The following command produces a line graph of total I/O requests from 6:00 AM to 6:00 PM for three days.

REP RDAS GRAPH(LINE,DASIOREQ) COMBINE(3H) -

STARTTIME(06:00) ENDTIME(18:00) -

SD(5/9/90) ED(5/11/90)

The Reporter produces a separate graph for each device. Figure 61 on page 148 and Figure 62 on page 149 result from this REPORT command.

FIGURE 61. Page 1 of Typical Line Graph

EPILOG FOR VM V610 PAGE 1RUN DATE: OCT 16,2003 DATA PROCESSED: 10/09/03 10:10 TO 10/11/03 18:00 COMBINE(3H) DASD ACTIVITY TREND (DASIOREQ) WHERE: DEVADDR IS 1A1 Y-AXIS TIMES 10 | |-------------------| |---------------------------| |-----------| 720.00 + * | . . | . . | *. . . 630.00 + . . . | . . . | . . . | . . . 540.00 + . . . * | . . . .. | . . . . . | . . . . .D 450.00 + . . . . .A | . . . . .S | . . . . .I | . . . . .O 360.00 + . . . . .R | .. . . .E | * . . .Q | . . . 270.00 + . . . | . . . | . . . | . . . 180.00 + . . . | . . . | . . . * | . . . . 90.00 + . * . . . | . ...... .... . . . | * ... . . . | * * O--------------------------------------------------------------------- 10:10 12:00 15:00 06:00 09:00 12:00 15:00 06:00 09:00 12:00 15:00 18:00 09:00 12:00 14:59 18:00 08:59 12:00 10/09 10/09 10/10 10/10 10/10 10/10 10/10 10/11 10/11 |---| OR H INDICATES TIME BANDS, M SHOWS MISSING DATA.



The first line of each graph contains dashes, Hs, blanks, and/or Ms. This line serves as a visual aid to help you identify breaks in time (as in from one day to the next) in the graphic output that appears below. The visual aid supplements the information in the time scales beneath the X-axis. If there are discrepancies between the two, rely on the time scales.

In Figure 63, two valid breaks in time occur between 18:00 on the evening of one day and 06:00 on the morning of the following day, as requested by the command that generated the graph.

FIGURE 62. Page 2 of Typical Line Graph

The following command produces vertical bar graphs of the data shown in the previous two figures.

REP RDAS GRAPH(VBAR,DASIOREQ) COMBINE(3H) -

STARTTIME(06:00) ENDTIME(18:00)

EPILOG FOR VM V610 PAGE 2RUN DATE: OCT 16, 2003 DATA PROCESSED: 10/09/03 10:10 TO 10/11/03 18:00 COMBINE(3H) DASD ACTIVITY TREND (DASIOREQ) WHERE: DEVADDR IS 1B1 Y-AXIS TIMES 10 | |-------------------| |---------------------------| |------------| 176.00 + * | .. | .. | . . 154.00 + . . | * . . | . . . . | . . . . 132.00 + *. . . . . | . . . | . . . | . . .D 110.00 + . . .A | . . .S | . . .I | . . .O 88.00 + . . .R | . . .E | . . .Q | . . . 66.00 + . *.......* *.... | *. ... ...* | .... ... | ..*. 44.00 + | | | 22.00 + | | | O---------------------------------------------------------------------- 10:10 12:00 15:00 06:00 09:00 12:00 15:00 06:00 09:00 12:00 15:00 18:00 09:00 12:00 14:59 18:00 08:59 12:00 10/09 10/09 10/09 10/10 10/10 10/10 10/10 10/11 10/11 |---| OR H INDICATES TIME BANDS, M SHOWS MISSING DATA.



Figure 61 and Figure 63 show the same data in two different formats. Figure 62 and Figure 64 also show the same data in different formats.

FIGURE 63. Page 1 of Typical Bar Graph

Notice the variation in the maximum Y-axis value of Figure 63 and Figure 64. The Reporter scales the Y-axis according to the highest value recorded. The Reporter scales the width of the bars according to the amount of data being graphed.

EPILOG FOR VM V610 PAGE 1RUN DATE: Oct 16, 2003 DATA PROCESSED:10/09/03 10:10 TO 10/11/03 18:00 COMBINE(3H) DASD ACTIVITY TREND (DASIOREQ) WHERE: DEVADDR IS 1A1 Y-AXIS TIMES 10 | |-------------------| |---------------------------| |-----------| 720.00 + ***** | ***** | ***** ***** | ***** ***** 630.00 + ***** ***** | ***** ***** | ***** ***** | ***** ***** 540.00 + ***** ***** ***** | ***** ***** ***** | ***** ***** ***** | ***** ***** *****D 450.00 + ***** ***** *****A | ***** ***** *****S | ***** ***** *****I | ***** ***** *****O 360.00 + ***** ***** *****R | ***** ***** *****E | ***** ***** ***** *****Q | ***** ***** ***** ***** 270.00 + ***** ***** ***** ***** | ***** ***** ***** ***** | ***** ***** ***** ***** | ***** ***** ***** ***** 180.00 + ***** ***** ***** ***** | ***** ***** ***** ***** ***** | ***** ***** ***** ***** ***** | ***** ***** ***** ***** ***** 90.00 + ***** ***** ***** ***** ***** ***** | ***** ***** ***** ***** ***** ***** ***** | ***** ***** ***** ***** ***** ***** ***** ***** | ***** ***** ***** ***** ***** ***** ***** ***** O---------------------------------------------------------------------- 10:10 12:00 15:00 06:00 09:00 12:00 15:00 06:00 09:00 12:00 15:00 18:00 09:00 12:00 14:59 18:00 08:59 12:00 10/09 10/09 10/09 10/10 10/10 10/10 10/10 10/11 10/11 |---| OR H INDICATES TIME BANDS, M SHOWS MISSING DATA.



FIGURE 64. Page 2 of Typical Bar Graph

EPILOG FOR VM V610 PAGE 1RUN DATE: OCT 5, 2003 DATA PROCESSED: 10/09/03 10:10 TO 10/11/03 18:00 COMBINE(3H) DASD ACTIVITY TREND (DASIOREQ) WHERE: DEVADDR IS 1B1 Y-AXIS TIMES 10 | |-------------------| |---------------------------| |------------| 176.00 + | ***** | ***** | ***** 154.00 + ***** | ***** ***** | ***** ***** | ***** ***** 132.00 + ***** ***** | ***** ***** ***** | ***** ***** ***** | ***** ***** *****D 110.00 + ***** ***** *****A | ***** ***** *****S | ***** ***** *****I | ***** ***** *****O 88.00 + ***** ***** *****R | ***** ***** *****E | ***** ***** *****Q | ***** ***** ***** 66.00 + ***** ***** ***** ***** ***** ***** | ***** ***** ***** ***** ***** ***** ***** ***** | ***** ***** ***** ***** ***** ***** ***** ***** ***** | ***** ***** ***** ***** ***** ***** ***** ***** ***** 44.00 + ***** ***** ***** ***** ***** ***** ***** ***** ***** | ***** ***** ***** ***** ***** ***** ***** ***** ***** | ***** ***** ***** ***** ***** ***** ***** ***** ***** | ***** ***** ***** ***** ***** ***** ***** ***** ***** 22.00 + ***** ***** ***** ***** ***** ***** ***** ***** ***** | ***** ***** ***** ***** ***** ***** ***** ***** ***** | ***** ***** ***** ***** ***** ***** ***** ***** ***** | ***** ***** ***** ***** ***** ***** ***** ***** ***** O---------------------------------------------------------------------- 10:10 12:00 15:00 06:00 09:00 12:00 15:00 06:00 09:00 12:00 15:00 18:00 09:00 12:00 14:59 18:00 08:59 12:00 10/09 10/09 10/09 10/10 10/10 10/10 10/10 10/11 10/11 |---| OR H INDICATES TIME BANDS, M SHOWS MISSING DATA.

Generating Graphs with GDDM/ICU


Generating Graphs with GDDM/ICUThis section shows how to generate sample graphic output using the IBM Graphical Data Display Manager/Interactive Chart Utility, GDDM/ICU Version 2.1. First you use a sample OBTAIN command file to extract data from the EPILOG datastore. Next, you use GDDM to generate graphs with the extracted data and the nine sample chart definitions that are shipped with EPILOG on the product tape.

To extract data from the EPILOG datastore, follow the instructions for using the OBTAIN command in “Extracting Data with EVOBT EXEC” on page 170.

The following sections contain sample OBTAIN command files and matching charts generated by GDDM/ICU. The name of the sample OBTAIN command file appears at the top of each labelled box. Each OBTAIN command extracts the data needed by GDDM/ICU to generate the corresponding chart.

The following sample charts are included in this section:

® Multi-line Chart of CPU Utilization

® Multi-line Chart of Logged-on Users

® Line Chart of Paging Device Load

® Line Chart of Resource Availability Index

® Scatter-line Chart of Paging I/O Rate vs. CPU Utilization

® Bar Chart of DASD Device Activity

® Bar Chart of Ten Most Active DASD Devices

® Pie Chart of Wait Reasons

® Stacked Bar Chart of Wait Reasons

A set of GDDM/ICU instructions for generating any of these nine sample charts is included at the end of this section.

Multi-line Chart of CPU Utilization

When the EVOBT EXEC executes this command file, it creates the sequential data file RCPU1 DATA A. GDDM/ICU uses this datafile to produce a graphic chart similar to the one below.

You may need to edit the sample command file before executing it if no data has been collected at your site for the date and time range specified.

RCPU1 COMMAND A

SET FORMAT(COL) YESTERDAY STIME(8) ETIME(15) CMB(1H) OBTAIN RCPU ELEMENTS(CPUBUSY,CPBUSY,VIRTBUSY) REPLACE - OUTFILE(RCPU1 DATA A)END



Figure 65 tracks the three elements (CPUBUSY, CPBUSY, and VIRTBUSY) requested by the OBTAIN command file. Descriptions for these elements appear in “RCPU - Resource CPU Activity Report” on page 83. The start time of each interval is displayed on the X-axis, and the CPU utilization percent is displayed on the Y-axis.

FIGURE 65. Sample GraphTracking CPUBUSY, CPBUSY, and VIRTBUSY

Multi-line Chart of Logged-on Users

When the EVOBT EXEC executes this command file, it creates the sequential data file RCPU2 DATA A. GDDM/ICU uses this datafile to produce a graphic chart similar to the one in Figure 66 on page 154.

RCPU2 COMMAND A

SET FORMAT(COL) YESTERDAY STIME(8) ETIME(15) CMB(1H) OBTAIN RCPU ELEMENTS(ACTUSER,AVGUSER,MAXUSER) REPLACE - OUTFILE(RCPU2 DATA A)END



You may need to edit the sample command file before executing it if no data has been collected at your site for the time range specified.

Figure 66 tracks the three elements (ACTUSER, AVGUSER, and MAXUSER) requested by the OBTAIN command file. Descriptions for these elements appear in “RCPU - Resource CPU Activity Report” on page 210. The start time of each interval is displayed on the X-axis, and the count of logged-on users is displayed on the Y-axis.

FIGURE 66. Sample Chart Tracking ACTUSER, AVGUSER, and MAXUSER



Line Chart of Paging Device Load

When the EVOBT EXEC executes this file, it creates the sequential data file RPAG1 DATA A. GDDM/ICU uses this datafile to produce a graphic chart similar to the one in Figure 67 on page 155.


Figure 67 tracks the element PCTBUSY over the time period requested by the OBTAIN command file. A description for this element appears in “RPAG - Resource Paging Activity Report” on page 225. The start time of each interval is displayed on the X-axis, and the device busy percent is displayed on the Y-axis. Each point on the line represents the average device busy percent for all paging devices on the system.

FIGURE 67. Sample Graph Tracking PCTBUSY

RPAG1 COMMAND A

SET FORMAT(COL) YESTERDAY STIME(8) ETIME(15) CMB(1H) OBTAIN RPAG ELEMENTS(PCTBUSY) REPLACE SUMMARY - OUTFILE(RPAG1 DATA A)END



Line Chart of Resource Availability Index

When the EVOBT EXEC executes this file, it creates the sequential data file RHLS1 DATA A. GDDM/ICU uses this datafile to produce a graphic chart similar to the one in Figure 68.


Figure 68 tracks the element RAI (Resource Availability Index) over the requested time period. The Resource Availability Index graph shows the trend in system-wide resource availability. The index measures the percent of active intervals that logged-on virtual machines are in a wait state. A value of 1 is ideal; a value of 0 indicates that no virtual machine gets a resource without entering a wait state.

FIGURE 68. Sample Graph Tracking RAI

RHLS1 COMMAND A

SET FORMAT(COL) YESTERDAY STIME(8) ETIME(16) CMB(1H) OBTAIN RHLS ELEMENTS(RAI) REPLACE - OUTFILE(RHLS1 DATA A)END



Scatter-line Chart of Paging Rate/CPU Utilization

When the EVOBT EXEC executes this file, it creates the sequential data file RHLS2 DATA A. GDDM/ICU uses this datafile to produce a graphic chart similar to the one in Figure 69.


Figure 69 tracks the two elements requested by the OBTAIN command file against each other. Descriptions for these elements appear in “RHLS - Resource High–Level Summary Report” on page 215. The scatter chart shows a correlation between the rate of CPU utilization and the number of paging I/O requests per second.

FIGURE 69. Sample Graph Tracking Two Elements Against Each Other

RHLS2 COMMAND A

SET FORMAT(COL) YESTERDAY STIME(8) ETIME(16) CMB(1H) OBTAIN RHLS ELEMENTS(IOPERSEC,CPUBUSY) REPLACE - OUTFILE(RHLS2 DATA A)END



Bar Chart of DASD Device Activity

When the EVOBT EXEC executes this file, it creates the sequential data file RDAS1 DATA A. GDDM/ICU uses this datafile to produce a graphic chart similar to the one in Figure 70.

You may need to edit the sample command file before executing it if no data has been collected at your site for the time range (YESTERDAY, STIME(16), ETIME(24)) specified.

Figure 70 tracks the element DASDBUSY over the time period requested by the OBTAIN command file. A description for this element appears in “RDAS - Resource DASD Activity Report” on page 212. Each bar represents the average device-busy percents of all DASD devices on the system.

FIGURE 70. Sample Graph Tracking DASDBUSY

RDAS1 COMMAND A

SET FORMAT(COL) YESTERDAY STIME(16) ETIME(24) CMB(1H) OBTAIN RDAS ELEMENTS(DASDBUSY) SUMMARY REPLACE - OUTFILE(RDAS1 DATA A)END



Bar Chart of Ten Most Active DASD Devices

When the EVOBT EXEC executes this file, it creates the sequential data file RDAS2 DATA A. GDDM/ICU uses this datafile to produce a graphic chart similar to the one in Figure 71.


Figure 71 tracks the two elements (DEVADDR and DASDIOREQ) requested by the OBTAIN command file. Descriptions for these elements appear in “RDAS - Resource DASD Activity Report” on page 212.

The chart represents the 10 devices with the highest I/O request counts. Each bar is labelled with the address of the device it represents. In the sample chart, device 17D has the most I/O requests.

FIGURE 71. Sample Graph Tracking DEVADDR and DASDIOREQ

RDAS2 COMMAND A

SET FORMAT(COL) YESTERDAY STIME(16) ETIME(24) CMB OBTAIN RDAS ELEMENTS(DEVADDR,DASIOREQ) REPLACE - OUTFILE(RDAS2 DATA A) SIF(DASIOREQ(>10))CMS XEDIT RDAS2 DATA A (PROFILE RDASSORT)END



Pie Chart of Wait Reasons

When the EVOBT EXEC executes this file, it creates the sequential data file RBOT1 DATA A. GDDM/ICU uses this datafile to produce a graphic chart similar to the one in Figure 72.


Figure 72 contains all users found in a wait state during the specified interval. The 8 slices depict the percentage of those users found in each of 8 specific wait states. The 8 slices represent the 8 elements requested by the above command file. Descriptions for these elements appear in “RBOT - Resource Bottleneck Analysis Report” on page 207.

FIGURE 72. Sample Pie Chart Depicting the Percent of Users Found

RBOT1 COMMAND A

SET FORMAT(COL) YESTERDAY STIME(16) ETIME(24) CMB OBTAIN RBOT REPLACE OUTFILE(RBOT1 DATA A) - ELEMENTS(WAITCFSP,WAITCPU,WAITIDLP,WAITIDSP,WAITIOP, - WAITOTHP,WAITPAGP,WAITSIMP)END



Stacked Bar Chart of Wait Reasons

When the EVOBT EXEC executes this file, it creates the sequential data file RBOT2 DATA A. GDDM/ICU uses this datafile to produce a graphic chart similar to the one in Figure 73.


In Figure 73, each stacked bar spans one reporting interval. Each portion of a stack represents the percent of users found in one of the specific wait states requested by the OBTAIN command file. Descriptions for these elements appear in “RBOT - Resource Bottleneck Analysis Report” on page 207.

FIGURE 73. Sample Bar Graph Depicting the Percent of Users Found

RBOT2 COMMAND A

SET FORMAT(COL) YESTERDAY STIME(16) ETIME(24) CMB(1H) OBTAIN RBOT REPLACE OUTFILE(RBOT2 DATA A) - ELEMENTS(WAITCFSP,WAITCPU,WAITIDLP,WAITIDSP,WAITIOP, - WAITOTHP,WAITPAGP,WAITSIMP)END



Using GDDM/ICU to Generate Sample ChartsTo generate a sample chart, use the following:

® one of the 9 sample chart definition files

® the corresponding sample format file

® the data file created by the corresponding sample OBTAIN command file

The 9 sample chart definition files and corresponding format and OBTAIN command files are shipped on the EPILOG tape and are loaded automatically when EPILOG is installed. Follow these steps to display any one of the 9 sample charts available with EPILOG.

1. Run the EVOBT EXEC to execute the sample OBTAIN command file that corresponds to the sample chart you want to display.This step creates the EPILOG data file that will become the GDDM input data file. (Sample OBTAIN command filenames and their corresponding charts are presented on the preceding pages.)

2. Invoke the GDDM/ICU interface by entering the appropriate command for your installation.GDDM displays the INTERACTIVE CHART UTILITY - HOME PANEL screen.

3. Select option S to load one of the sample chart definitions.GDDM displays the SAVE AND LOAD CHART screen.

4. Respond as follows to the prompts on the SAVE AND LOAD CHART screen.At the What do you want to do? prompt, select option 1 to load one of the sample files.

At the Which part of chart? prompt, select option 1 to indicate that you want to load the sample format file.

At the Replace? prompt, leave the default value NO. If you have displayed a sample chart previously during this session, change this value to YES.

At the Format prompt, enter one of the sample chart format filenames. Valid chart format filenames and a brief description for each follow:

5. Press Enter.After you enter the above options, GDDM will display a message at the top of the screen confirming that the chart format file was loaded successfully.

6. Press PF12 to exit from this screen. GDDM displays the HOME PANEL screen.

RCPU1 Multi-line CPU utilization chart (includes CPU Busy, CP Busy, and Virtual Busy).

RCPU2 Multi-line CPU utilization chart (includes counts of users logged on).

RPAG1 Line chart of system-wide paging device load.

RHLS1 Line chart of the Resource Availability Index (RAI).

RHLS2 Scatter line chart of system-wide paging I/O rate vs. CPU utilization.

RDAS1 Bar chart of DASD device activity.

RDAS2 Bar chart of the ten most active DASD devices, by number of I/O requests.



7. Select option 2 to access the data-routing menu.GDDM displays the DATA ENTRY (ROUTING) menu. This controls the importing of the data file created by the OBTAIN command.

8. Select item 9, Data Import.The system displays the DATA IMPORT FILE SELECTION screen.

9. At the What do you want to do? prompt, select option 4 to load the sample data definition file.

10. Press Enter. GDDM displays the SAVE AND LOAD DATA DEFINITION screen.

11. Respond as follows to the indicated prompts:At the What do you want to do? prompt, select option 1 to load a data definition file.

At the Replace? prompt, leave the NO default if this is the first time you have displayed a chart. If you have displayed another sample chart during this GDDM session, change this value to YES.

At the Data Definition prompt, enter the name of the sample data format file. This filename must be the same name used above for the sample chart format file (for example: RCPU1 or RCPU2). (You can also display a pick list of available data definition files by selecting option.

12. Press Enter.GDDM displays a message at the top of the screen confirming that the data definition file was loaded successfully.

13. Press PF3/PF15 to return to the data-import screen.GDDM displays the DATA IMPORT FILE SELECTION screen.

14. Respond as follows to the indicated prompts:At the What do you want to do? prompt, select option 3 to import the data.

At the File identifier prompt, leave the correct file ID that has already been supplied.

At the Type of File prompt, leave the pre-set value of 1.

15. Press Enter.GDDM displays a message at the top of the screen confirming that the data has been imported to GDDM.

16. Press PF5/PF17 to display the chart at your terminal.

You can repeat these steps to display any of the 9 sample charts available with EPILOG.

Generating Graphs On a PC


Generating Graphs On a PCSpecific instructions for using the OBTAIN command are discussed above in “Extracting Data with EVOBT EXEC” on page 170. In this section, we elaborate only on those steps involved in getting data from the active EPILOG datastore to a PC where it can be used by a PC software product. The PC software product used in the explanations below is the graphics facility of Lotus® 1-2-3®. These are the three steps you must take in order to process EPILOG data on a PC.

1. Use OBTAIN to extract data from the EPILOG datastore.

2. Download the OBTAIN output file to a PC.

3. Generate a graph using a PC software product.

The first step may be accomplished with the sample OBTAIN command file in Figure 74 on page 164. This command file will extract EPILOG data properly formatted for use by a PC software package.

To accomplish the second step, use whatever utility is commonly used at your site to download EBCDIC flat files to a PC in ASCII format.

The third step requires using a PC and the appropriate graphing software to create your graphs. Some sample graphs are discussed in “Sample Graphs Generated on a PC” on page 165. These graphs were created on a PC using the data OBTAINed in step 1 and downloaded in step 2 (The graphics facility in Lotus 1-2-3 was used to create the sample graphs.)

Using OBTAIN to Extract DataThe sample EVOBT command file in Figure 74 is set up to extract the data needed to analyze activity in the following areas:® Paging DASD pool® Total DASD pool® CPU utilization® User loadWhen the sample command file is executed, it creates the two CMS flat files, RCPU DATA A and DASD DATA A.

FIGURE 74. Sample OBTAIN Command File for PC Processing

SET YDAY TIMEZONE(+8) CMB(1H) OBTAIN RCPU FORMAT(PC) OUTFILE(RCPU DATA A) REPLACE - ELEMENTS(CPBUSY VIRTBUSY AVGUSER ACTUSER) SET SIF(DASIOREQ(>0)) SIF(IOCOUNT(>0)) SUM OBTAIN RDAS RPAG - OUTFILE(DASD DATA A) REPLACE FORMAT(PC) - ELEMENTS(DEVIOSEC, IOPERSEC, EXTIOSEC, SERVTIME) END



The first SET command in the sample command file selects a date and time for the two OBTAIN commands that occur later in the file. YDAY is a relative date that specifies yesterday’s data no matter when you execute this command file. TIMEZONE resets the system internal TOD clock from Greenwich Mean Time (GMT). The time zone is incremented by 8 hours in order to obtain Pacific Standard Time (PST).

CMB(1H) sets the combine period to 1 hour for both OBTAIN commands. Combine summarizes data into larger time intervals. In this case, if you collect data in 15-minute intervals (the default), a combine of 1 hour takes four 15-minute records and summarizes them into one 1-hour record.

The first OBTAIN command extracts specified elements from the RCPU report and places them in the RCPU DATA A output file in a format ready to be downloaded and used by PC software. FORMAT(PC) formats EPILOG data in the output file so it can be downloaded and read directly into a PC software product. The REPLACE option allows OBTAIN to overlay the file specified in the OUTFILE keyword if one exists. The elements selected to be obtained from the RCPU report, CPBUSY, VIRTBUSY, AVGUSER, ACTUSER, are described in “Data Dictionary” on page 201.

The second SET command selects only those records with some DASD, paging and swapping activity. SUM summarizes the data from a particular subsystem on an interval-by-interval basis. For example, when running the DASD report without the SUM keyword, individual statistics for each device on the system are displayed, one line per device. When running the DASD report using the SUM keyword, statistics for the entire DASD subsystem for each reporting interval are displayed, one line per reporting interval.

The second OBTAIN command repeats the FORMAT keyword specified in the first OBTAIN command. The designation for OUTFILE has changed, and the elements to be selected have changed. The major difference between the two OBTAIN commands is that the first command specifies only one report name (RCPU), and the second specifies two report names (RDAS and RPAG).

The second example joins data from multiple reports into one file. There are some limitations in this join function that relate to report types. This issue is explained in greater detail in “OBTAIN Command Keywords” on page 172. Since there is no specification for the disposition of the OUTFILE on the second OBTAIN command, the default of APPEND is used. APPEND will locate the existing file specified in the OUTFILE keyword, and will add new records to the bottom of the file. If no file is found, APPEND will create a new file.

Use an editor such as XEDIT to create an OBTAIN command file to your specifications. When you have finished editing the command file, execute it using the EVOBT EXEC as described above in “Extracting Data with EVOBT EXEC” on page 170.

Downloading the OBTAIN Output FileAfter the command file has generated the output, download the output file(s) to a PC using whatever utility is available for this purpose at your site. Next, import the data into the software package you are using.

Sample Graphs Generated on a PCWhen the data is imported into Lotus 1-2-3, the text and numerics are placed into separate spreadsheet cells. You can use Lotus 1-2-3 and other PC products to manipulate the data as needed. The following sample graphs were generated by Lotus 1-2-3 using EPILOG data that was extracted by the SET and OBTAIN commands in the sample command file described above.



Figure 75 represents data that was extracted by the first sample OBTAIN command. The elements being displayed are CPBUSY (CPU used by CP) and VIRTBUSY (CPU used by virtual machines). When they are stacked, as they are in this bar graph, they represent the total CPU busy (CPUBUSY) for the entire system.

FIGURE 75. Sample Graph Tracking CPBUSY and VIRTBUSY



Figure 76 represents data that was extracted by the same sample OBTAIN command as the previous graph, but different elements are being displayed. This graphs displays a line trend of the count of users logged on (Avg Users) and the number of active users. The trend is examined over the period of one day. Active users are users found doing work during collection intervals.

FIGURE 76. Sample Graph Depicting Average Users and Active Users



Figure 77 displays data that was extracted by the second sample OBTAIN command. A separate line graph displays the average I/Os per second for each of the following: the entire DASD subsystem (DASD I/O), the paging subsystem (Paging I/O), and swapping subsystem (Swapping I/O).

Remember that the second sample OBTAIN command used the SUM keyword. This graph makes it easy to identify the subsystem that is generating the most I/Os per second.

FIGURE 77. Sample Graph Tracking DASD I/O, Paging I/O, and Swapping I/O



Figure 78 displays data extracted by the second sample OBTAIN command, but in this graph, service time (instead of I/O Rate) is displayed for the DASD, paging, and swapping subsystems. From this graph, you can detect a major service time delay on swapping devices. On the previous graph, the number of I/Os for swapping devices is low. These two graphs together strongly suggest that there is a swapping configuration problem.

FIGURE 78. Sample Graph of DASD, Paging, and Swapping of Service Time

Extracting Data with EVOBT EXEC


Extracting Data with EVOBT EXECThe EVOBT EXEC uses the OBTAIN command to select data from the active datastore for later use as input to other mainframe and microcomputer application packages. Only certain report output fields can be graphed. See “Data Dictionary” on page 201 to find which field names can be graphed for each report.

Running the EVOBT EXECDo not issue the OBTAIN command directly from CMS command mode. To issue the OBTAIN command, follow this two-step procedure:

1. Create a data extraction command file containing the OBTAIN command that specifies the data to be selected from the datastore and the name of the output file that will be created. The command file may also contain one or more SET, CMS, or CP commands, as needed.

2. Invoke the EVOBT EXEC to execute the contents of the command file created in step 1. Use the following syntax to invoke the EVOBT EXEC:

EVOBT fn [ft fm]

where:

Enter EVOBT ? to get on-line syntax information for the EVOBT EXEC.

Note: If, during installation, you used a user ID or minidisk address for the EPILOG datastore that is different from the one specified in the EVOBT EXEC, you must modify the EVOBT EXEC. The procedure to do this is detailed in OMEGAMON for VM, EPILOG for VM Installation and Customization Guide.

A list of sample OBTAIN command files and the titles of reports they generate appear in Table 34 on page 171.

fn Specifies the filename of the data extraction command file that contains the OBTAIN (and SET) command. This is the only required parameter.

ft Specifies the filetype of the command file. The default is COMMAND.

fm Specifies the filemode of the command file. The default is A.



OBTAIN Command SyntaxFigure 79 shows the syntax to use when entering the OBTAIN command in the EVOBT command file.

FIGURE 79. OBTAIN Command Syntax

Note: You can specify the DATEFORM and CLEAR keywords with the SET command. These keywords cannot be included on the OBTAIN command. You may also use the SET command to specify the keywords that appear in the previous figure, except for ELEMENTS and report-name. They must be specified on the OBTAIN command.

An alternative to including SET commands in the EVOBT command file is to include them in an OBSET GLOBAL file. They will execute before the commands in the command file.

Table 34. Sample OBTAIN Command Files

Sample Command File Report Name

RBOT1 Bottleneck Analysis Report (Combine All)

RBOT2 Bottleneck Analysis Report (Combine 1 Hour)

RCPU1 CPU Activity Data (% Busy Data)

RCPU2 CPU Activity Report (User Data)

RDAS1 DASD Activity Report (DASD Busy)

RDAS2 DASD Activity Report (I/O Data)

RHLS1 High Level Summary Report

RHLS2 High Level Summary Report

RPAG1 Paging Activity Report (% Busy Data)

OBTAIN {report-name, ...}OBT [date-range] [time-range] [BAND|RANGE] [COMBINE(nnc)] [REPORTIF(element(relation value units), ...)] [SELECTIF(element(relation value units), ...)] [SUMMARY] [SYSTEMID(cccccccc)] [ELEMENTS(field-name, ...)] [IPREFIX(prefix)] [OUTFILE(fn ft fm)] [FORMAT((INT|COL|PC)] {REPLACE|APPEND] [TIMEZONE(+/-nnnn)]



OBTAIN Command Keywords

report-name

You can specify one or multiple report names. If you enter more than one report name, the reports must belong to the same report type. Report-type groupings follow.

® Single-record-per-interval Reports

– RBOT

– RCPU

– REXP

– RFRE

– RHLS

– RICO

– RSCH

– RSTR

– RTRA

® Multiple-record-per-interval Reports

– RLPR

– WBOT

– WCPU

– WICO

– WSTO

– WSUM

– WTRA

® Device-address Report

– RDAS with at most, one of the following:

– RPAG

– RTDI

– RSPO

– RVDS

® Stand-alone Reports

– GRPD

– RCHP

– RNSS

– RSEE



– RSYS

date-range

The span of days for which data is to be extracted. The full set of date-range keywords is available as explained in “REPORT and SET - Generating Reports” on page 53. As with the REPORT command, the keywords fall into three categories:

® absolute start and end dates in the current DATEFORM format

® relative dates, such as SDATE(-7)

® generic dates, such as YESTERDAY or LASTMONTH

If no date-range is stated or SET, the full range of the attached database is assumed.

time range

The span of time during the day for which data is to be extracted. The full set of time-range keywords is available as explained in “REPORT and SET - Generating Reports” on page 53.

BAND|RANGE

Selects either the band or range interpretation of date and time-ranges. The distinction is only necessary when the date-range covers multiple days, and the time-range is less than 24 hours. If this occurs, BAND indicates only the time of day between the start and end times for each day separately. RANGE indicates all the time from the start time on the start date through to the end time on the end date. BAND is the default.

COMBINE(nnc)

Combines data from individual smaller time intervals into a larger time interval. The argument, nnc, specifies the larger time interval. The variable nn is a 1 or 2 digit number; c is a scale indicator. Valid scale indicators are C, D, H, and M, indicating calendar months, days, hours, and minutes, respectively. For example, CMB(1H) combines four 15-minute interval records into one 1-hour record. If no argument is specified, the reporting interval is used.

REPORTIF(element(relation value units), ...)

Data can be selected for extraction using this keyword in the same manner as explained in “REPORT and SET - Generating Reports” on page 53.

SELECTIF(element(relation value units), ...)

Data can be selected for extraction using this keyword in the same manner as explained in “REPORT and SET - Generating Reports” on page 53.

SUMMARY

Extracts only summary-level data from the datastore. This is the data that appears on the summary lines of detail reports.

When requesting multiple report names with the SUMMARY keyword, normal restrictions for report-type groupings are removed. The SUMMARY keyword changes all report types to the single-record-per-interval type. You can therefore request reports from any of the report-type groups mentioned above on an OBTAIN command that includes the SUMMARY keyword.



SYSTEMID(cccccccc)

Use this keyword to select only records from a particular processor. It is possible that a single database can contain data from several processors. If SYSTEMID is not specified, data is selected from all processors in the database that meet the selection criteria.

ELEMENTS(field-name, ...)

Identifies the field names to be selected from the specified report. Field names available for OBTAINing are itemized by report name in “Data Dictionary” on page 201.

The same field name is sometimes used in more than one report, and represents a different data element in each report. When requesting one of these field names, you must specify which report(s) you are referencing. For example, the field SERVTIME appears on two reports: RDASD and RPAGE. In the sample command below, the request is for SERVTIME from the reports RDAS and RPAGE. Notice that no report name is specified for the field name DASDBUSY, since this field appears only on the report RDAS.

OBTAIN RDAS RPAGE -

ELEM(RDAS(SERVTIME),DASDBUSY,RPAGE(SERVTIME))

The default field is DATETIME. To get all fields, you must specify ELEM(*).

IPREFIX(prefix)

Specifies the first two characters of the filenames to be used as input to the OBTAIN command. The default is EV, which indicates that input is coming from files in the active datastore.

prefix

Specifies the first two characters of the input file names. If not specified, EV is used, and input comes from files in the active datastore.

The prefix AC can be used to request that input come from condensed files generated by an ACCUM command that used the default OPREFIX value of AC. Other prefixes may be used if files were condensed and the default OPREFIX prefix of AC was overridden.

OUTFILE(fn ft fm)

This specifies the filename, filetype, and filemode of the CMS file that will receive the extracted data. The default output file identifier is EPILOG OBTAIN A.

FORMAT(INT|COL|PC)

Use this keyword to specify the format of the data that will be written to the OBTAIN output file. The output file is the file explicitly named with the OUTFILE keyword, or the default output file, EPILOG OBTAIN A. Three options are available for the FORMAT keyword: INT, COL, and PC. INT is the default value.

INT writes binary data formatted as described below in “Output Files” on page 175. Use the INT option if you will be writing your own programs to read the OBTAIN output file.

COL and PC write printable data arranged in columns. Use COL if the output file will be used as input to a mainframe graphics or statistics package. Use PC if the output file will be downloaded and used as input.



REPLACE|APPEND

Specifies whether OBTAINed data should overwrite (REPLACE) records in an existing OUTFILE with the same name, or add (APPEND) records to the end of the file. In both cases, the comment and attribute records are written to the file along with the observation records. REPLACE is the default.

TIMEZONE(+/-nnnn)

This keyword has the same effect here as it does when used with the REPORT command as documented in “REPORT and SET - Generating Reports” on page 53.

Output FilesEach invocation of EVOBT creates (or adds to) a sequential output file with variable length records. The format of the generated output file depends on the option used on the FORMAT keyword on the OBTAIN command. Each of the three options, INT, COL, and PC, creates output files with descriptive information and raw data. The descriptive information varies significantly among the three options; the raw data varies in displayed format only.

Use the INT option if you will be writing your own mainframe programs to read\ the OBTAIN output file.

Use COL if the output file will be used as input to a mainframe graphics or statistics package.

Use PC if the output file will be downloaded and used as input to a PC software package such as Lotus 1-2-3.

Output Files Generated by FORMAT(INT)

This output file contains three types of records: comment records, attribute records, and observation records. For each OBTAIN command issued with FORMAT(INT), there are two comment records, used mainly for documentation purposes. There is one attribute record that describes the fields being selected, and multiple observation records that contain the contents of the fields selected from the datastore.

1. The comment records have no fixed layout. The first comment record contains:– a date-time stamp for when the command was issued– a record-type indicator of *– a 1-byte reserved field– the text of the OBTAIN command as it exists in the command file

The second comment record contains:– the current settings, or default values for the BAND|RANGE and DATEFORM

keywords– the current setting of any other valid keywords that are set in the command file

2. The attribute record has a fixed layout. It contains:– a date-time stamp (8 bytes, packed decimal)

– a record-type indicator of A (1 byte)

– a reserved field (1 byte)

– the number of fields being OBTAINed, that is, the number of fields that will appear in each observation record (2 bytes, binary integer)



– for each element selected,

- the field name (8 bytes, character)

- the data type (list valid data types, for example, C, H)

- the field length in bytes (1 byte, binary integer)

- a reserved field (1 byte)

- the decimal point displacement, number of positions to move to the left for packed and integer fields (1 byte, binary integer)

- the field offset, location of field from beginning of observation record, in bytes (2 bytes, binary integer)

3. The observation records have a layout unique to the particular OBTAIN run. Each record contains:– a date-time stamp for the time the OBTAIN command was issued in the following

format: 0cyyddd. Where:

– a record-type indicator of the letter O (1 byte)– a reserved field (1 byte)– a date-time value for the start of the recording interval for the observation record (16

bytes)– a field value for each field name itemized in the attribute record

The contents of a typical OBTAIN output file generated with FORMAT(INT) are shown in Figure 80. The file contains the two comment records, one attribute record, and four observation records generated by the following command:

OBT RCPU YDAY STIME(10) ETIME(11) -

ELEMENTS(CPUBUSY,CPBUSY)

Note: The records displayed in the figure have been interpreted into readable format. If you were to list the contents of an OBTAIN output file generated with FORMAT(INT), non-readable, binary data would be displayed.

c Century (0=20th century, 1=21st century)

yy Year (for example, 96=1996)

ddd day of the year (for example, 005=January 5)



FIGURE 80. Output File for OBTAIN Using FORMAT(INT)

The second comment record contains the default values BAND and MMDDYY, since the user did not specify BAND|RANGE nor DATEFORM values in the command file. The start and end dates are for the day before the command was issued, since the user specified YDAY (yesterday) in the command file.

The date stamp in the first field of each record is given as a Julian Date (yyddd).

Note that since the default sampling interval is 15 minutes and the requested reporting interval is 1 hour (10:00 - 11:00), the number of observation records produced is 4.

Output Files Generated by FORMAT(COL)

This output file contains two record types: the attribute record and the observation record. For each OBTAIN command issued with FORMAT(COL), there is one attribute record describing the fields being selected, and multiple observation records containing the contents of the fields selected from the datastore.

1. The attribute record has a fixed layout. For each element, it contains:– an asterisk (*)

– the field name

– the offset (position of the field from the beginning of the record)

– the field length in bytes

– the data type: D(ecimal), H(exidecimal), C(haracter), or I(nteger)

2. The observation records have a layout unique to the particular OBTAIN run. Each record contains:– a 16-byte date-time value for the start of the recording interval for the observation

record

– a value for each field name itemized in the attribute record

0103246F 0132741F * OBT RCPU YDAY STIME(10) ETIME(11) -

0103246F 0132741F * ELEMENTS(CPUBUSY,CPBUSY) 0103246F 0132741F * BAND TIMEZONE(+08:00) SDATE(09/02/03) STIME(10:00)

EDATE(09/02/03) - 0103246F 0132741F * ETIME(11:00) DATEFORM(MMDDYY)

0103246F 0132741F A 0003 DATETIME C 16 00 10 CPUBUSY D 80 00 26 CPBUSY D 80 00 34

0103246F 0132741F O 09/02/0310:00:02 41CB68C79635E9B4 416436C88C54FAC9 0103246F 0132741F O 09/02/0310:15:02 41C91EF38DBE2A3F 415ACAD597E3C166

0103246F 0132741F O 09/02/0310:30:01 41C99F0FB38A94CE 415F0F3F086B67FA 0103246F 0132741F O 09/02/0310:45:01 41C9B069B5724B26 415DC5C5BF56E614



The contents of a typical OBTAIN output file for FORMAT(COL) are shown in Figure 82. The file contains the attribute record and the 24 observation records generated by the following command:

OBT RCPU YDAY CMB(1H) FORMAT(COL) OUTFILE(GRAPH EXTRACT A) -

ELEMENTS(CPUBUSY, CPBUSY, VIRTBUSY, AVGUSER, ACTUSER)

Note: The records displayed in the figure are in the same readable format as they would appear if you listed the file at a terminal or printer.

FIGURE 81. Output File for OBTAIN Using FORMAT(COL)

Note: Since the requested combine period was 1 hour, and the requested reporting interval is yesterday, the number of observation records produced is 24.

Output Files Generated by FORMAT(PC)

This output file contains two record types: the attribute record and the observation record. For each OBTAIN command issued with FORMAT(PC), there is one attribute record describing the fields being selected and multiple observation records containing the contents of the fields selected from the datastore.

1. The attribute record has a fixed layout. For each element, it contains the element name in double quotes.

2. The observation records have a layout unique to the particular OBTAIN run. Each record contains:– A date in double quotes and a time in double quotes, indicating the start of the

recording interval for the observation record (the date is in the format specified by DATEFORM).

*DATETIME 0 16C*CPUBUSY 16 10F*CPBUSY 26 10F*VIRTBUSY 36 10F *AVGUSER 46 10F*ACTUSER 56 10F10/17/0300:00:00 43.11 23.70 19.40 32.33 18.0910/17/0301:00:01 43.56 23.63 19.93 33.00 18.3710/17/0302:00:01 43.56 24.25 19.31 32.27 17.8810/17/0303:00:01 47.85 24.88 22.97 32.10 17.8010/17/0304:00:00 73.50 28.48 45.03 34.72 19.8310/17/0305:00:00 64.48 27.98 36.50 40.68 21.1710/17/0306:00:01 71.10 30.21 40.90 43.41 22.6110/17/0307:00:01 65.70 30.42 35.28 44.67 22.8510/17/0308:00:01 56.46 30.67 25.79 45.85 20.7810/17/0309:00:01 74.86 32.90 41.96 48.23 23.9010/17/0310:00:01 80.96 38.04 42.92 53.72 26.4010/17/0311:00:01 88.53 45.62 42.91 60.95 28.6510/17/0312:00:04 99.12 53.55 45.57 63.92 30.1110/17/0313:00:02 88.62 40.39 48.23 45.08 22.0310/17/0314:04:28 70.59 35.25 35.34 34.82 20.1610/17/0315:00:01 74.98 33.10 41.88 42.58 23.5710/17/0316:00:01 53.23 28.16 25.07 42.48 22.2310/17/0317:00:00 78.14 32.06 46.07 38.39 20.1510/17/0318:00:00 55.39 26.33 29.06 36.33 19.4810/17/0319:00:01 31.42 19.89 11.53 31.02 17.0510/17/0320:00:01 30.21 19.29 10.93 30.00 16.8210/17/0321:00:01 30.52 19.57 10.95 30.00 16.7810/17/0322:00:00 31.19 19.88 11.30 30.47 17.0010/17/0323:00:01 28.70 18.92 9.78 31.00 16.83



– A field value for each field name itemized in the attribute record. If the value is in character or hexadecimal format it will be surrounded by double quotes.

The contents of a typical OBTAIN output file for FORMAT(PC) are shown in Figure 82. The file contains the attribute record, and the 24 observation records generated by the following command:

OBT RCPU YDAY CMB(1H) FORMAT(PC) OUTFILE(PC EXTRACT A) -

ELEMENTS(CPUBUSY, CPBUSY, VIRTBUSY, AVGUSER, ACTUSER)

Note: The records displayed in the figure are in the same readable format as they would appear if you listed the file at a terminal or printer.

FIGURE 82. Output File for OBTAIN Using FORMAT(PC)

The date and time stamp for each record will always be surrounded by double quotes.

Note that since the requested combine period was 1 hour, and the requested reporting interval is yesterday, the number of observation records produced is 24.

Command File ExamplesThis section presents the contents of typical EVOBT command files. One command file contains only an OBTAIN command; one contains a SET command followed by an OBTAIN command.

When the following command file is executed by the EVOBT EXEC, OBTAIN extracts date-time (by default), device busy, device address, volume serial number, device type, and queue depth data for all DASD devices. One record is produced for each device, for each interval, starting with the first weekday that is at most seven days ago. If this command is run on a Saturday, the first records would be for the prior Monday starting at 9:00 AM.

OBT RDAS SDATE(-7) DAY(WEEKDAY) STIME(9) ETIME(12) -

ELEMENTS(DEVBUSY DEVADDR VOLSER DEVTYPE QDEPTH)

“DATE” “TIME” “CPUBUSY “ “CPBUSY “ “VIRTBUSY” “AVGUSER “ “ACTUSER ““10/17/03” “00:00:00” 43.11 23.70 19.40 32.33 18.09“10/17/03” “01:00:01” 43.56 23.63 19.93 33.00 18.37“10/17/03” “02:00:01” 43.56 24.25 19.31 32.27 17.88“10/17/03” “03:00:01” 47.85 24.88 22.97 32.10 17.80“10/17/03” “04:00:00” 73.50 28.48 45.03 34.72 19.83“10/17/03” “05:00:00” 64.48 27.98 36.50 40.68 21.17“10/17/03” “06:00:01” 71.10 30.21 40.90 43.41 22.61“10/17/03” “07:00:01” 65.70 30.42 35.28 44.67 22.85“10/17/03” “08:00:01” 56.46 30.67 25.79 45.85 20.78“10/17/03” “09:00:01” 74.86 32.90 41.96 48.23 23.90“10/17/03” “10:00:01” 80.96 38.04 42.92 53.72 26.40“10/17/03” “11:00:01” 88.53 45.62 42.91 60.95 28.65“10/17/03” “12:00:04” 99.12 53.55 45.57 63.92 30.11“10/17/03” “13:00:02” 88.62 40.39 48.23 45.08 22.03“10/17/03” “14:04:28” 70.59 35.25 35.34 34.82 20.16“10/17/03” “15:00:01” 74.98 33.10 41.88 42.58 23.57“10/17/03” “16:00:01” 53.23 28.16 25.07 42.48 22.23“10/17/03” “17:00:00” 78.14 32.06 46.07 38.39 20.15“10/17/03” “18:00:00” 55.39 26.33 29.06 36.33 19.48“10/17/03” “19:00:01” 31.42 19.89 11.53 31.02 17.05“10/17/03” “20:00:01” 30.21 19.29 10.93 30.00 16.82“10/17/03” “21:00:01” 30.52 19.57 10.95 30.00 16.78“10/17/03” “22:00:00” 31.19 19.88 11.30 30.47 17.00“10/17/03” “23:00:01” 28.70 18.92 9.78 31.00 16.83



The SET command in the following command file causes all dates in subsequent OBTAIN commands and output files to be read as and written in day, month, year format. The date range is weekdays starting at most seven days prior to the date this command is executed. The time range is 9:00 AM to noon.

The OBTAIN command overrides the previous SET SDATE date range with explicit dates. The previous SET DATEFORM makes the start and end dates on this command translate to October 9, 1990 and February 13, 1990, respectively.

The SET time range of 9:00 AM to noon causes the CMB(3H) on this command to generate one CPU record per day averaged over the 3-hour period. The first record will be for February 9, 2002 at 09:00. The actual output will be 09/02/02 09:00:00, because of the DATEFORM specified in the SET command.

FIGURE 83. Using the Set Command

SET DATEFORM(DDMMYY) SDATE(-7) DAY(WEEKDAY) - STIME(9) ETIME(12)OBT RCPU SDATE(9/2/02) EDATE(13/2/02) CMB(3H) - ELEMENTS(CPUBUSY, CPBUSY, VIRTBUSY, TVRATIO)

Maintaining the Datastore 181

Maintaining the Datastore

Chapter ContentsDatastore Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182The EVACCUM EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183The EVACCUM Command File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183The EVACCUM Output Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Running the EVACCUM EXEC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

The EVTDUMP EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Running the EVTDUMP EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

The EVTLOAD EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Creating an Automated Maintenance Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

6

Datastore Maintenance


Datastore MaintenanceDatastore maintenance is required when the active datastore approaches its full capacity. As a general rule, when the datastore reaches 90% of capacity, it is time to perform maintenance. There are two ways to obtain a percent-full reading for the active datastore:

® Read the % Datastore Full value on the copyright page of any EPILOG report.

® Issue the Collector QUERY DISK or QUERY EPILOG command.

Three EXEC utilities provide datastore maintenance functions. A brief description of each EXEC follows:

Two optional keywords that you can include on the Collector OPTIONS statement can be used in conjunction with one or more of the EXEC utilities to automate datastore maintenance at your installation. The Collector keywords are fully documented in the OMEGAMON and EPILOG for VM Installation and Customization Guide. Brief descriptions of the two keywords follow:

The next three sections in this chapter describe the three datastore maintenance EXEC utilities. The last section describes how to create an automated datastore maintenance procedure at your installation.

EVACCUM Condenses data in the active datastore and creates files on a separate minidisk that contain fewer records with longer recording intervals. See “The EVACCUM EXEC” on page 183 for details.

EVTDUMP Copies files from the active datastore (or condensed files from a separate minidisk) to tape or disk, and by default erases the datastore files. See “The EVTDUMP EXEC” on page 187 for details.

EVTLOAD Copies files from tape to another minidisk. See “The EVTLOAD EXEC” on page 191 for details.

DISKFull Specifies the percent-full threshold for the datastore. When this threshold is exceeded, the Collector invokes the command specified on the MAINTCOMMAND keyword.

MAINTCommand Specifies the command to be issued by the Collector when the datastore exceeds the percent-full threshold specified on the DISKFULL keyword.


The EVACCUM EXEC

The EVACCUM EXECEVACCUM allows you to keep more data online while minimizing the space required to do so. This is necessary when performing trend analyses that span long periods of time. The EVACCUM EXEC processes the ACCUM command that you enter in the EVACCUM command file. The ACCUM command generates condensed output files.

The input to ACCUM usually consists of files in the active datastore that you may or may not be ready to archive to tape using EVTDUMP. Input can also be output files created by a previous ACCUM run.

SyntaxThe syntax for issuing the EVACCUM EXEC includes the file identifier for the EVACCUM command file, which contains the full text of the ACCUM command that you specified. The syntax is illustrated below.

The EVACCUM Command File

Note: The EVACCUM command file must reside on a write-accessible minidisk before invoking the EVACCUM EXEC. Output files will be written to the minidisk where the command file is located.

The EVACCUM command file contains the ACCUM command with parameters that define the way data will be condensed in the output files. The parameters must include the COMBINE period. Optionally, you can specify a prefix for input filenames, a prefix for output file names, and the system for which data is being condensed.

The contents of a typical command file are shown below.

The resulting output files contain records with a COMBINE period of 1 hour. Input filenames have the default prefix of EV, which means they are being read from the active datastore.

fn The CMS filename of the EVACCUM command file where the text of the ACCUM command is located. The filename is required. There is no default value.

ft The CMS filetype of the EVACCUM command file. The filetype is not required. The default is ACCUMCTL.

fm The CMS filemode of the EVACCUM command file. The filemode is not required. The default is *.

SOURCE x Specifies the filemode of the source library. The default is * (the first accessed disk with a file that contains a filetype of STARTUP).

? This provides online syntax information for the EVACCUM EXEC.

EVACCUM {fn} [ft [fm]] (SOURCE x [?]

ACCUM {COMBINE(1h)}[IPREFIX(EV) OPREFIX(AC) SYSTEMID(IBM3090)]

The EVACCUM EXEC


Output filenames have the default prefix of AC. Only records with a system identifier of IBM3090 will be condensed.:

To add to the selection criteria available with the ACCUM command, use the CMS RENAME command to change filenames, filetypes and filemodes. This will prevent the renamed files from being condensed and written to disk since ACCUM searches for files with specific file IDs.

The EVACCUM Output FilesThis section describes in detail the output files generated when the EVACCUM EXEC executes the ACCUM command contained in the command file. Two types of output files are produced: the condensed data file and the log file.

Condensed Data Files

The ACCUM command generates a condensed data file for each input data file it processes. The filename of each condensed file is in the following format:

ACyymmdd

The filetype for each output file is the same as for the input file from which it was condensed (such as CHANACT or CPUACT).

The filemode for the output files is the same as the disk where the EVACCUM command file is located.

The following are examples of possible input file identifiers and their corresponding condensed output file identifiers.

COMBINE This parameter is required. Valid COMBINE values are 1H, 24H, and 1D.

IPREFIX This parameter is not required. If the IPREFIX specification is omitted, EV is used as the first two characters in the input filenames. This results in condensing the files in the active datastore.

OPREFIX This parameter is not required. If the OPREFIX specification is omitted, AC is used as the first two characters in the output filenames.

SYSTEMID This parameter is not required. If the SYSTEMID selection is omitted, all SYSTEMIDs are included in the condensed output files.

AC This portion of the filename can be changed by using the OUTFILE parameter in the command file. If you change the AC prefix, you will have to make a corresponding change to the IPREFIX default value on the REPORT and SET commands if you attempt to report on data contained in these files.

yymmdd This portion of the filename represents the date that the data was collected.

Input File in Datastore Output File in Datastore

: :

EV900301 CPUACT B AC900301 CPUACT C




: :


The EVACCUM EXEC

The condensed output files can be used as input to reports. When a REPORT command requests data from a time period that is no longer contained in the active datastore, EPILOG can report on condensed records residing on a different minidisk if the requested dates are found there. The report will necessarily be less detailed in the area using the condensed data.

The Log File

The ACCUM command generates a log file that contains the filename, filetype, and filemode of each detailed input file that was successfully condensed. This file can help you in creating a backup/delete procedure. The filename for this file is the same as that of the EVACCUM command file. The filetype is EXEC, and the filemode is the same as that of the condensed output files.

Running the EVACCUM EXECBelow are instructions for creating two condensed versions of the active datastore, one condensed on an hourly basis, and one on a daily basis. Two versions are given for instructional purposes only. You may choose to create only one condensed version of the active datastore.

1. Log onto any user ID.

2. Gain read/only access to the minidisk where the EPILOG datastore is located. A typical LINK-ACCESS command sequence is given below.

CP LINK VCOLLECT 191 194 RRACCESS 194 B

3. Gain read/write access to the minidisk where the condensed ACCUM output files will be located. Use different disks for different time periods. (We use C for hourly and D for daily.)

CP LINK VCOLLECT 291 291 WACCESS 291 C

CP LINK VCOLLECT 292 292 WACCESS 292 D

4. Create the EVACCUM command file(s) on the same minidisk(s) where the condensed output files will be located (C and D in this case). Once you create a command file, you should not change its contents, especially its combine period.

Create a command file named HOURLY ACCUMCTL C, and insert the following statement in the file:

ACCUM COMBINE(1H) OPREFIX(HH)

Create a command file named DAILY ACCUMCTL D, and insert the following statement in the file:

ACCUM COMBINE(1D) OPREFIX(DD)

5. Issue the EVACCUM EXECs.EXEC EVACCUM HOURLY ACCUMCTL C

EXEC EVACCUM DAILY ACCUMCTL D

The EVACCUM EXEC


FIGURE 84. EVACCUM Input and Output Files

Figure 84 is a graphic representation of the input and output files involved in the EVACCUM executions described above. In general, the disk files on the left represent input to the command file in the center, which generates the condensed output files on the right.

The top portion of the diagram represents the processing of the HOURLY command file; the bottom portion of the diagram represents the processing of the DAILY command file. Input to both files comes from the active EPILOG datastore.

Note the following points regarding Figure 84:

® The two-way arrows on the right side of the processing boxes indicate that the condensed output files can later be used as input to further EVACCUM processing. For instance, the HOURLY output files could be used as input to the DAILY command file.

® The output files generated by the two command files reside on separate disks (291 and 292). Candle recommends that you use different disks for data condensed into different time periods (hourly and daily, in this case).

® The output files generated by the HOURLY command file have filenames beginning with HH as specified with the OPREFIX keyword in the command file. Similarly, the output files generated by the DAILY command file have filenames beginning with DD.

® The EPILOG Reporter can report on data that was generated by the ACCUM command.


The EVTDUMP EXEC

The EVTDUMP EXECThe EVTDUMP EXEC copies the files in the active datastore or on the ACCUM minidisk to tape or disk, and by default, erases the copied files. Run EVTDUMP from a user ID other than the Collector to avoid having to stop the Collector during the dump/erase.

Note: If you would like to keep a condensed version of the active datastore on-line, run the EVACCUM EXEC before running EVTDUMP.

Syntax

parm This option can be any one of the following:

* results in dumping all files on the specified disk, except for those files created today. This is the default.

yymmdd results in dumping files that were created on this date, selected from all physical datastore disks. The filenames of the files on the datastore minidisk (or on the minidisk where condensed files are located) contain this date.

The wildcard character is supported on this option if used as the last character of the date specified. If you enter 0205*, EVTDUMP processes all of the files for May 2002. If you enter 02*, EVTDUMP processes all of the files for 2002. The % symbol is used as a place holder. If you enter 02%%01, EVTDUMP processes files created on the first of every month in 2002. If you specify 020501, the data for May 1, 2002 is processed.

<yymmdd results in processing all files created before this date. The wildcard character, *, is supported on this form of the date option, as a final character only. The place holder, %, is not.

<nnnD results in processing all files older than nnn days. Valid values for nnn are in the range 1 - 366. Neither the wildcard character, *, nor the place holder, %, are supported.

<nnM results in processing all files older than nn months. Valid values for nn are in the range 1 - 99. Neither the wildcard character, *, nor the place holder, %, are supported.

? provides on-line syntax information for the EVTDUMP EXEC.

EVTDUMP [parm][(TO fm|TAPn FROM fm IPREFIX xx COLLID xxxxxxxx OWNER cccccccc VOL1ID cccccc HDR1|NOHDR1 LABEL|NOLABEL ERASE|NOERASE DUMP|NODUMP LIST|NOLIST LOGOFF|NOLOGOFF CONS|NOCONS TEST)]

The EVTDUMP EXEC


TO fm|TAPn Specifies the filemode (fm) of the target minidisk, or unit (TAPn) of the target tape drive, to which files are to be dumped. The disk must be defined with read/write access and must be available when EVTDUMP is running. TAPn must conform to the conventions outlined by the CMS TAPE command. The default is TAP1.

FROM fm Specifies the filemode of the source minidisk that contains the files to be processed. The default is A.

IPREFIX xx Specifies the prefix of the source filenames in the datastore or on the minidisk. If omitted, the default prefix EV results in dumping files from the active datastore. You can change this prefix if you are dumping condensed files created by the EVACCUM EXEC.

COLLID xxxxxxxx Specifies the user ID of the Collector virtual machine. The default is VCOLLECT.

OWNER cccccccc The owner identifier (VOL1) of the output tape if a labeled tape is to be created. This option is only valid when the LABEL option is used. The default is OMEGAMON.

VOL1ID cccccc The volume identifier (VOL1) of the output tape if a labeled tape is to be created. This option is only valid when the LABEL option is used. The default is EPILOG.

LABEL|

NOLABEL

Specifies whether or not the output tape will have labels. This option is for tape output only.® If NOLABEL is specified and there is a label on the tape, the tape label

will be over-written. Output starts from the BOT (beginning of tape).® If NOLABEL is specified and there is no label on the tape, output starts

from the BOT (beginning of tape).® If LABEL is specified and there is a label on the tape, the tape is

positioned after the label. Output starts after the tape mark following the label(s).

® If LABEL is specified and there is no label on the tape:– The tape is positioned to the BOT (beginning of tape).– A VOL1 label is written using the options VOL1ID and OWNER.– A dummy HDR1 and a tape mark is written.– Output starts after the tape mark following the label(s).

The default is NOLABEL.

HDR1|NOHDR1 Specifies whether or not the dummy HDR1 record remains after the VOL1 or is destroyed. This option is only valid when the LABEL option is used, and there is no label on the tape, and this exec creates the label. The default is HDR1.

ERASE|NOERASE Specifies whether or not to erase the files from the datastore after they are dumped to tape or disk. The default is ERASE.

DUMP|NODUMP Specifies whether or not to copy the files from the datastore to tape or disk. Use the NODUMP keyword if you want to erase files in the datastore without saving them first. The default is DUMP.

LIST|NOLIST Specifies whether or not to display the names of the files being processed. LIST displays the filenames at the console. The default is NOLIST.


The EVTDUMP EXEC

The filenames of files being dumped follow this naming convention:

ccyymmdd

Running the EVTDUMP EXECTo manually run the EVTDUMP EXEC, follow these steps.

1. Log onto your user ID.

2. Be sure you have only READ access to the disk where the files to be dumped are located.

3. You do not need WRITE access because the Collector will erase the files (if the ERASE option is in effect.)

4. If dumping files to tape, mount a tape and attach it to your virtual machine.

5. Issue the EVTDUMP EXEC. The following command generates a typical run of an EVTDUMP EXEC that dumps all files from the active datastore for May 2002, and then erases the files.

EVTDUMP 0205*(ERASE

The EXEC displays the information shown in Figure 85.

LOGOFF|NOLOGOFF Specifies whether or not to issue a CP LOGOFF command after EVTDUMP finishes processing. LOGOFF is useful when EVTDUMP is being run from an AUTOLOGed user ID. The default is NOLOGOFF.

CONS|NOCONS Specifies whether or not to start the console and SPOOL it to the virtual reader queue. CONS is useful when EVTDUMP is running on a disconnected virtual machine, that is, an AUTOLOGed user ID. The default is CONS when EVTDUMP is running on a virtual machine that was automatically logged on and is running in disconnected mode. The default is NOCONS when EVTDUMP is running on a virtual machine that is logged on to a user ID

TEST This is the same as specifying NOERASE NODUMP LIST. It allows you test EVTDUMP without dumping or erasing any files. Use this keyword to display the selected files to be processed.

cc This prefix indicates the type of file being dumped, and gives some indication of its location. The default prefix EV indicates files are the original EPILOG files on the active datastore. The prefix AC, or any other prefix, indicates files are on a minidisk where condensed files created by the EVACCUM EXEC are located.

yymmdd Indicates the date on which the data was collected and stored.

The EVTDUMP EXEC


FIGURE 85. Execution of EVTDUMP EXEC

EPILOG for VM Version 610 - Data ARCHIVE Function Copyright 2003 !Candle Corporation EU011: EVTDUMPEU015: EVTDUMP options: TO=TAP1, FROM=A, IPREFIX=EV, COLLID=VCOLLECT, DUMP, ERASE, NOLIST, CONS, LOGOFF EU018: EVTDUMP statistics follow: 7 files have been processed. 63 (4096 byte) blocks. Approximately 12% of disk. VCOLLECT A-disk is now approximately 11% full. EPILOG for VM Version 610 - ARCHIVE Ended


The EVTLOAD EXEC

The EVTLOAD EXECThe EVTLOAD EXEC copies files from a tape (created by EVTDUMP) to a specified minidisk.

SyntaxUse the following syntax for the EVTLOAD EXEC.

The filename convention of records on the tape is:

ccyymmdd

yymmdd The date of the files you want to restore in one of the following forms:® Specify no date or a single asterisk (*), which causes all files on the tape to

be loaded, or® Specify a single date from which to load all the files on the tape.See the IPREFIX option for information on further limiting file selection. An asterisk (*) or an ampersand (&) cannot be used as a wild card or placeholder character within the date.

IPREFIX cc Specifies the first 2 characters of the EPILOG datastore filenames, created on yymmdd, that are to be loaded. An IPREFIX specification is ignored if a date specified as yymmdd is not specified. If yymmdd is specified without IPREFIX, the default is EV. The EV prefix specifies that you are loading files originating from the active datastore. You can change this prefix if you are loading condensed files created by EVACCUM.

TAPn Defines the source tape drive. TAPn must conform to the restrictions outlined in the CMS TAPE command. The default is TAP1.

DISKMODE c This specifies the filemode of the minidisk that will contain the files being loaded. The default is A.

? Provides online assistance for the EVTLOAD EXEC.

cc The filename prefix indicates the origin of the files. The default prefix EV indicates the files are from the original EPILOG datastore. The default prefix for condensed files (AC), or any prefix you specified on the ACCUM command, may also appear here.

yy Indicates the year.

mm Indicates the month.

dd Indicates the day.

EVTLOAD [yymmdd].inwidth on ‘EVTLOAD ‘[(IPREFIX cc TAPn DISKMODE c)][?]

The EVTLOAD EXEC


Running the EVTLOAD EXECYou may want to define permanent or temporary mini-disks on your virtual machine for loading data from tape. In either case, you must access the target load disk prior to running EVTLOAD.

To load previously-archived data, follow these steps.

1. Mount the data tape and attach to your virtual machine. If you are loading condensed files rather than files from the active datastore, be sure you have access to the disk where you want the condensed files to be located.

2. Issue the EVTLOAD EXEC. The following example loads all files on the tape for April 28, 2002 to the A-disk.EVTLOAD 020428

If at least one file exists on the A-disk with the yymmdd value you entered, or if you did not enter a value for yymmdd, the following message appears:

FIGURE 86. Execution of EVTLOAD EXEC

If you enter Y, the load process continues, and file on the datastore may be written over by files from the tape. If you enter N, the load process terminates.

When the load process completes, the EXEC displays the following message:

When running EPILOG reports (see the EVREPT EXEC described in “Generating a Customized Report” on page 51), all accessed mini-disks are searched for EPILOG data files. Reports will reflect all data files found on all accessed disks, as though they were one large file. If multiple files with the same name exist, the first one found in CMS disk-search order is used.

The date range specified may result in replacement of files onthe A-disk. Files found on the A-disk are:.inwidth on ‘the A’ EVyymmdd EVyymmdd ....inwidth off ‘the A’If you continue, these files are replaced by anylike-named files found on tape.Do you wish to continue? (Y/N) (“N” is the default)

EPILOG for VM Load Complete


Creating an Automated Maintenance Procedure

Creating an Automated Maintenance ProcedureOMEGAMON and EPILOG for VM provide two Collector keywords (DISKFULL and MAINTCOMMAND) to use with its three EXEC utilities (EVACCUM, EVTDUMP, and EVTLOAD) to allow you to create an automated datastore maintenance procedure. The sample procedure in this section illustrates one way you can create an automated datastore maintenance procedure at your installation.

For example, you can specify that when the space allocated to the datastore minidisk reaches 85% of its capacity, a user ID is autologged, and it automatically invokes the EVTDUMP EXEC. EVTDUMP then writes all data on the datastore minidisk that is more than 14 days old to tape drive TAP1. Finally, it erases the dumped files from the datastore minidisk. After EVTDUMP executes, the user ID on which it runs is logged off automatically. (While EVTDUMP was running, all its messages were SPOOLed to the autologged virtual machine’s reader queue.)

Here are the requirements for implementing the automated maintenance procedure described above. The process uses the DISKFULL and MAINTCOMMAND keywords in conjunction with the EVTDUMP EXEC.

1. Define the user ID that will be autologged by the Collector. The user ID must meet the following specifications:– It must have read access to the minidisk that contains the EVTDUMP EXEC and the

minidisk that contains the active datastore.

– Its PROFILE EXEC accesses the datastore minidisk that will be read later by EVTDUMP. In this example, the PROFILE EXEC contains the following statement to allow EVTDUMP to reference the datastore minidisk as filemode B ACCESS 199 B

2. Provide the collector virtual machine with the authorization to issue the CP AUTOLOG command. The Collector will need this privilege to autolog the user ID that performs the datastore maintenance function.

3. Insert two OPTIONS statement keywords in the Collector control file. The following OPTIONS keywords are required to initiate the automated procedure described in this example.OPTIONS

DISKFULL(85)

MAINTCOMMAND(“AUTOLOG userid password

EXEC EVTDUMP <14D (TO TAP1 FROM B CONS LOGOFF)”)

.

.

Note: An alternative to including the EVTDUMP EXEC on the MAINTCOMMAND keyword is to include it in the PROFILE EXEC of the user ID being autologged.

Creating an Automated Maintenance Procedure


Applying Maintenance ZAPs 195

Applying Maintenance ZAPs

Appendix A shows you how to apply maintenance ZAPs.

Chapter ContentsZAP Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Listing Applied Maintenance ZAPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Applying Maintenance to the Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Applying Maintenance to EPILOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

A

ZAP Types


ZAP TypesPeriodic maintenance of Candle products is as important as installing and using the products correctly. EPILOG uses the standard IBM ZAP program for all maintenance. There are two types of EPILOG ZAPs.

When ZAPs are shipped, they are numbered in this form:

FIGURE 87. ZAP Format

The following is a sample ZAP name:

OV600R02

The product ID code is OV, the version number is 600, the type is regular, and it is ZAP number 02.

Regular For general distribution.

Special To handle installation-specific environments or unique problems. These ZAPs are available to anyone who needs them, but they are not for general use and should not be generally applied. In fact, some may cause undesirable side effects at your installation.

ppvvvtnn

Candle product identification code

EPILOG version number (for example, 600)

Either an R for regular ZAP or an S for special ZAP

Sequential ZAP number


Listing Applied Maintenance ZAPs

Listing Applied Maintenance ZAPsEPILOG and the Collector use the IBM ZAP command for all maintenance.

For a list of ZAPs applied to EPILOG modules, issue the ZAP command in a Reporter command file. Figure 88 shows typical ZAP command output.

FIGURE 88. Typical Output of the EPILOG ZAP Command

For a list of ZAPs applied to the Collector, issue the following command:

CP SMSG vcollect Q ZAPS

Figure 89 shows typical QUERY ZAPs command output.

FIGURE 89. Typical Output of the Collector’s QUERY ZAPS Command

ZAPs applied: EV500R02 Version 1EV500R04 Version 1

EV500S01 Version 1

............... ................ ............... ................ ............... ................

10:02:00 CV0100 User * sent command "Q ZAPS"10:02:00 CV0570 Regular ZAP #1 Version 01 applied.10:02:00 CV0570 Regular ZAP #3 Version 02 applied.10:02:00 CV0570 Regular ZAP #4 Version 01 applied.10:02:00 CV0570 Regular ZAP #5 Version 01 applied.10:02:00 CV0570 Regular ZAP #7 Version 01 applied.10:02:00 CV0570 Regular ZAP #8 Version 01 applied.10:02:00 CV0002 "Q" command complete.

Applying Maintenance to the Collector


Applying Maintenance to the CollectorThe Collector is distributed in load-module format only. There is a separate CMS MODULE for each release of VM. ZAPs are applied to these MODULES by using the IBM ZAP command. See the IBM publication VM/SP Operator Commands for a description of the ZAP command.

Note: The CP nucleus does not have to be regenerated unless the user diagnose was changed.

To apply a ZAP, follow these steps:

1. Determine if the ZAP is applicable.

2. Apply the ZAPs to the appropriate MODULE. Note that the ZAP specifies whether it applies to all releases of VM or only to specific releases.

3. Reaccess the disk that contains the Collector module.

4. Reload the Collector module that contains the newly applied changes.Do not use the RESTART command to perform this function since it does not reload the Collector module.

You are now ready to test the changes and move to production. Figure 90 shows the procedure required to ZAP a Collector load module.

FIGURE 90. Applying a ZAP to the Collector

If you have any questions or problems, call Candle Customer Support.

ZAP MODULE Z440V <ZAP the module for VM release 4.4.0>NAME CVXP1 CVINI <name of module and CSECT to be ZAPped>VER 0000 FFFF <verify that x’FFFF’ appears at address x’0000’>REP 0000 FF00 <replace data at address x’0000’ with x’FF00’>END <end of ZAP entry>


Applying Maintenance to EPILOG

Applying Maintenance to EPILOGTo apply a ZAP, follow these steps:

1. Determine if the ZAP is applicable.

2. Apply the ZAPs to the EPILOG module. An example of applying a ZAP follows.

FIGURE 91. Applying a ZAP to Epilog

You are now ready to test the changes and move the updated EPILOG module to production.

There may be gaps in the ZAP numbers for two reasons:

® All ZAPs are numbered sequentially by release, and some will not apply to the module you are using.

® Some ZAPs may be in TEST status and are not generally available.

ZAP MODULE <apply maintenance to a module>NAME EPILOG evbase <name of module and CSECT to be ZAPped>VER 0000 FFFF <verify that x’FFFF’ appears at address x’0000’>REP 0000 FF00 <replace x’FF00’ at address x’0000’>END <end of ZAP entry>

Applying Maintenance to EPILOG


Data Dictionary 201

Data Dictionary

The data dictionary is designed to provide technical information when using the REPORT, SET, and OBTAIN commands. The tables in this appendix are arranged in alphabetical order by report short name.

If you need to sort, graph, or make selections when using the REPORT and SET commands, you must know which report fields can be used with the SORTBY, GRAPH, REPORTIF, and SELECTIF keywords. The tables on the following pages list the report field names for each report and indicate whether or not each field can be used with each of these keywords. If you need to extract data using the OBTAIN command, you will need to know the exact spelling of the field names. All field names appearing in these tables can be used with the OBTAIN command.

Chapter ContentsData Dictionary Column Headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Report Printing Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

GRPD - Group Definition Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206RBOT - Resource Bottleneck Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207RCHP - Resource Channel Path Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209RCPU - Resource CPU Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210RDAS - Resource DASD Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212REXP - Resource Expanded Storage Migration Report . . . . . . . . . . . . . . . . . . . . . . . 213RFRE - Resource Free Storage Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214RHLS - Resource High–Level Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215RICO - Resource IUCV/VMCF Communications Activity Report. . . . . . . . . . . . . . . . 219RLPR - Resource LPAR Utilization Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221RNSS - Resource Saved Segment/NSS Activity Report . . . . . . . . . . . . . . . . . . . . . . . 223RPAG - Resource Paging Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225RSCH - Resource Scheduler Storage Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226RSEE - Resource Seek Analysis Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228RSPO - Resource SPOOLing Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230RSTR - Resource Storage Management Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231RSYS - Resource System Information Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

B


RTDI - Resource Temporary Disk Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 237RTRA - Resource Transaction Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238RVDS - Resource VDISK Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239WBOT - Workload Bottleneck Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240WCPU - Workload CPU Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242WICO - Workload IUCV/VMCF Communications Activity Report . . . . . . . . . . . . . . . 243WSTO - Workload Paging/Storage Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244WSUM - Workload Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245WTRA - Workload Transaction Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Data Dictionary 203

Data Dictionary Column Headers

Data Dictionary Column HeadersThe following information describes the data in the dictionary tables that follow.

Column Header

The column header that identifies this output field on this report.

Field Name

The symbolic name by which EPILOG identifies this output field on the report. Use this name as an operand on the SORTBY, RIF, SIF, and GRAPH keywords and as an element name on the OBTAIN command.

Unit

The unit of measure for the data element.

Field Length

The length of the field in bytes.

ADDR Device address

BYT Bytes

CSEC Centiseconds (1/100th of a second)

DAY Days

DSEC Deciseconds (1/10th of a second)

FRMS Frames

HRS Hours

INT Integer

KBYT Kilobytes

MBYT Megabytes

MIN Minutes

MSEC Milliseconds

OTHR Other

PAGS Pages

PCT Percent

SEC Seconds

STCK Store clock (time-of-day format)

TICK Timer ticks (1/300 second)

USEC Microseconds

WEEK Weeks

Data Dictionary Column Headers


Data Type

The format in which the data element is stored.

Keyword SORT

Indicates whether you can use this field name as an operand on the SORTBY keyword.

Keyword GRAPH

Indicates whether you can use this field name as an operand on the GRAPH keyword.

Keyword RIF/SIF

Indicates whether you can use this field name as an operand on the REPORTIF and SELECTIF keywords.

Description

Shows additional descriptive information.

BITF Bit flags

CHAR Character

FLTD Double floating point

PDEC Packed decimal

SBIN Signed binary

UBIN Unsigned binary

Data Dictionary 205

Report Printing Environments

Report Printing EnvironmentsRefer to Table 35 if you are unable to print a particular report. Table 35 lists the report and the file type needed for EPILOG to collect data.

Table 35. Report Printing Environments

Report Name File Type

GRPD GRPD

RBOT SYSBOT

RCHP CHPACT

RCPU CPUACT

RDAS DVOLACT

REXP STRACT

RFRE STRACT

RHLS CPUACT

RICO SYSCOM

RLPR LPAR

RNSS RSSMGMT

RPAG DEXTACT

RSCH SCHACT

RSEE RSEEKS

RSPO DEXTACT

RSTR STRACT

RSYS SYSCONF

RTDI DEXTACT

RTRA CPUACT

RVDS ADDRSPAC

WBOT WRKBOT

WCPU WKLDACT

WICO WKLDACT

WSTO WKLDACT

WSUM WKLDACT

WTRA WRKTRN



GRPD - Group Definition Report

Table 36. GRPD - Group Definition Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF



Group Name GRPNAME 08 CHAR Y Name of group specified in the Collector control file.

Type Of Grouping

GRPTYPE INTG 12 CHAR Y Shows how a workload is grouped. Types of groups are: user ID, account code, distribution code, or bottleneck.

Group Entities RANGE1 08 CHAR The first designation for the user IDs, account codes, or distribution codes that make up the group.


Data Dictionary 207


RBOT - Resource Bottleneck Analysis Report

Table 37. RBOT - Resource Bottleneck Analysis Report


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF




Sample Count SYSSMPL INTG 04 UBIN Y Y The number of samplings recorded by the Collector during the reporting period.

% Using CPU USEDCPUP 08 FLTD Y Y Y The percentage of virtual machines using the CPU.

% CF Wait WAITCFSP 08 FLTD Y Y Y The percentage of virtual machines in the dispatch list found to be in a console function simulation wait state.

% CPU Wait WAITCPUP 08 FLTD Y Y Y The percentage of virtual machines in the dispatch list found to be in a CPU wait state.

% Idle WAITIDLP 08 FLTD Y Y Y The percentage of virtual machines in the dispatch list found to be in an idle wait state.

% Idle SVM Wait WAITIDSP 08 FLTD Y Y Y The percentage of virtual machines in the dispatch list found to be in a service virtual machine wait state.



% I/O Wait WAITIOP 08 FLTD Y Y Y The percentage of virtual machines found to be in an I/O wait state.

% Other WAITOTHP 08 FLTD Y Y Y The percentage of virtual machines in the dispatch list not found in any of the above wait states.

% Page Wait WAITPAGP 08 FLTD Y Y Y The percentage of virtual machines in a wait state found to be in a page wait state.

% Sim Wait WAITSIMP 08 FLTD Y Y Y The percentage of virtual machines in the dispatch list found to be in an instruction simulation wait state.

Table 37. RBOT - Resource Bottleneck Analysis Report (continued)

Data Dictionary 209


RCHP - Resource Channel Path Activity Report



Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

% CHP Busy CHPBUSYP 08 FLTD Y Y The percentage of time that this channel path was in use during the reporting interval.

Channel Path ID CHPID ADDR 02 SUBI Y The channel path identification number.






RCPU - Resource CPU Activity Report

Table 39. RCPU - Resource CPU Activity Report


Data Type

Keywords Description

SO

RT

GR

AP

H

RIF

/SIF

Active Users ACTUSER 08 FLTD Y Y Y Number of users who had any activity since the last sampling interval.

Logged On Avg AVGUSER 08 FLTD Y Y Y Average number of users logged on.

CP % CPBUSY 08 FLTD Y Y Y Percentage of CPU utilized by CP.

CPU % CPUBUSY 08 FLTD Y Y Y Total CPU utilization (CP and virtual combined). If you are running multiple processors, this value is the sum of CPU utilization for all processors and can be greater than 100%.

# CPUs CPUNUM 08 FLTD Y Y Number of active processors.


DATETIME STCK 08 CHAR Time of day at start of reporting interval.

Dialed Users DIALUSER 08 FLTD Y Y Y Number of users who are dialed to VM.

Users in Eligible ELIGUSER 08 FLTD Y Y Y Average number of users waiting in the eligible list.

LPAR Utilization Logical

LPARBUSY 08 FLTD Y Y Y Percentage of time this LPAR was busy based on the number of available logical processors.

Logged On Max MAXUSER INTG 08 FLTD Y Y Y Maximum number of users logged on during reporting interval.

Data Dictionary 211


LPAR Utilization Physical

PHYSBUSY 08 FLTD Y Percentage of time this LPAR was busy based on the number of physical processors in the system.

SYSID 08 CHAR Y Y Y System ID for entire report appears in upper right portion of report heading.

Total/Virt Ratio TVRATIO 08 FLTD Y Y Y Ratio of total CPU time to virtual CPU time.

Users in Queue USERQ 08 FLTD Y Y Y Average number of users waiting in queue to be dispatched.

Virtual % VIRTBUSY 08 FLTD Y Y Y Virtual CPU percent. Amount of CPU utilized by virtual machines in real problem state.

Table 39. RCPU - Resource CPU Activity Report (continued)



RDAS - Resource DASD Activity Report

Table 40. RDAS - Resource DASD Activity Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

Connect Time CONNTIME MSEC 08 FLTD Y Y Y Average time this device was in CONNECT state during the reporting interval.

Percent Busy DASDBUSY INTG 08 FLTD Y Y Y Percentage of time the device was found busy.

Queue Depth DASDQUE INTG 08 FLTD Y Y Y Average number of I/Os queued on the device.

Total I/O Requests

DASIOREQ INTG 08 FLTD Y Y Y Number of I/Os started on this device.


DATETIME STCK 08 CHAR Y Y Date and time when Collector started recording data for the device.

Device Address DEVADDR ADDR 02 SUBI Y Y Y Real address of device.

Device I/Os Per Second

DEVIOSEC INTG 08 FLTD Y Y Y I/Os per second to this device (I/O rate).

Device Type DEVTYPE INTG 04 CHAR Y Y Type of device (for example: 3380, 3350, or 3375).

Disconnect Time

DISCTIME MSEC 08 FLTD Y Y Y Average time this device was in DISCONNECT state during the reporting interval.

Pending Time PENDTIME MSEC 08 FLTD Y Y Y Average time this device was in PENDING state during the reporting interval.

Service Time (ms)

SERVTIME MSEC 08 FLTD Y Y Y Average service time for this device in milliseconds.


DASD Volser VOLSER INTG 06 CHAR Y Y DASD volume serial number.

Data Dictionary 213


REXP - Resource Expanded Storage Migration Report



Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF



Migrated Blocks Avg Age Change

EXPBKAGE INTG 08 FLTD Y Y Y The change in average age of all blocks migrated from expanded storage, in seconds.

Blocks Migrated EXPBKMIG INTG 08 FLTD Y Y Y The number of blocks migrated from expanded storage.

System Block Count

EXPMIGCP INTG 08 FLTD Y Y Y The number of blocks migrated from CP.

Dormant User Block Count

EXPMIGDM INTG 08 FLTD Y Y Y The number of blocks migrated from dormant users.

Active User Block Count

EXPMIGND INTG 08 FLTD Y Y Y The number of blocks migrated from active users.

Number of Migrations

EXPMIGS INTG 08 FLTD Y Y Y The number of invocations for expanded storage migration.

NSS/DCSS Block Count

EXPMIGSS INTG 08 FLTD Y Y Y The number of blocks migrated from all the saved systems combined.

Guest Blocks Allocated

EXPMIGVS INTG 08 FLTD Y Y Y Average number of blocks allocated to guests during the interval (for example: users, guests).

SYSID 08 CHAR System ID for entire report appears in upper right portionof report heading.



RFRE - Resource Free Storage Activity Report

Table 42. RFRE - Resource Free Storage Activity Report

Columm Header

Field Name

Unit Field Length

Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF



Free Frame Requests

FSTRFREQ INTG 08 FLTD Y Y Y The total number of free-storage extends during the reporting interval.

Free Frame Returns

FSTRFRRT INTG 08 FLTD Y Y Y The total number of free-storage extend releases during the interval.

Free Storage Requests

FSTRREQS INTG 08 FLTD Y Y Y The total number of free-storage requests during the reporting interval.

Free Storage Returns

FSTRRETS INTG 08 FLTD Y Y Y The total number of free-storage releases during the reporting interval.

Subpool List Count Regular

FSTRSBLK INTG 08 FLTD The number of frames in the regular free-storage subpool list during the reporting interval.

Subpool Calls Regular

FSTRSUBP INTG 08 FLTD Y Y Y The number of calls for V=R free storage that were handled by the V=R free-storage subpool list.

Subpool List Count V=R

FSVRSBLK INTG 08 FLTD The number of frames in the V=R free storage subpool list as set at system gen time.

% Real Storage

REALSPCT 08 FLTD Y Y Y The percent of real storage being used as free storage during the reporting interval.


V=R Free Size

VRFRESIZ INTG 08 FLTD The total number of frames of free storage reserved for the V=R guest at system gen time.

Data Dictionary 215


RHLS - Resource High–Level Summary Report

Table 43. RHLS - Resource High-Level Summary Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

Active Users ACTUSER 08 FLTD This statistic appears on the CPU Activity Report and represents the number of users who had any activity during the sampling interval.

Logged On Users

AVGUSER 08 FLTD This statistic appears on the CPU Activity Report and represents the average number of users logged on during the sampling period.

% CPU Busy CPUBUSY 08 FLTD This statistic appears on the CPU Activity Report and represents the percent of the CPU being utilized. CPU usage includes that used by CP and by virtual machines. If you are running multiple processors, this value is the sum of CPU utilization for all processors and can be greater than 100%.


DATETIME STCK 08 CHAR This statistic is available on all reports and represents the date and time when the Collector started recording data.

Page I/Os / Sec DEVIOSEC INTG 08 FLTD This number represents the system-wide I/O paging rate. Related statistics appear on the Paging Activity Report on a volume-by-volume basis.

% Logical Processor Busy

LPARBUSY 08 FLTD Percentage of time this LPAR was busy based on the number of available logical processors.




NTRVCNT INTG 08 FLTD Related statistics appear on the Transaction Activity Report. This number represents the total number of non-trivial transactions processed during the reporting interval.

Non-Trivial Transactions / Sec

NTRVRATE 08 FLTD Related statistics appear on the Transaction Activity Report. This number represents the average number of non-trivial transactions processed per second during the reporting interval.

% Paging Space In Use

PCTPAGE 08 FLTD Related statistics appear on the Paging Activity Report on a volume-by-volume basis. This number represents the average system-wide percent of paging space in use.

% SPOOL Space In Use

PCTSPOL 08 FLTD This statistic appears on the SPOOLing Activity Report and represents the percent of SPOOL space in use for the entire system.

% Temp Disk Space In Use

PCTTDSK 08 FLTD This statistic appears on the Temporary Disk Activity Report and represents the percent of temporary disk space in use for the entire system.

% Physical Processor Busy

PHYSBUSY 08 FLTD Percentage of time this LPAR was busy based on the number of physical processors in the system.

% Processor n Busy

PRC00 -PRC07

INTG 08 FLTD The percent busy for each processor, assuming a MP system (up to eight processors: PRC00 - PRC07).


Data Dictionary 217


Resource Availability Index

RAI 08 FLTD The Resource Availability Index is a statistic that summarizes how the resource met the demands placed on it during the reporting interval. The range is 0 - 1. 0 and 1 are limits, not possible values. 0 would mean the resource was never available; 1 would mean the resource was always available when needed.This RAI statistic is derived in the following way:1 - (((elig + q1)/(cpubusy/100))/user)Where:

The number displayed for RAI is useful as a comparative value for trend analysis. If the RAI value starts to drop over a period of time, you can view the individual components used to derive the RAI statistic. These components can be tracked by using the RHLS and RCPU reports.


elig the average number of users in the eligible list.

q1 the average number of users in queue 1.

user the average number of users that had activity during the sampling interval.



% of Real Storage = DPA

SYSDPAP 08 FLTD This statistic represents the percentage of real storage available to the Dynamic Paging Area.

% of Real Storage = System Free

SYSFREEP 08 FLTD This statistic appears on the Free Storage Activity Report and represents the number of V=R free storage pages plus the number of free pages that are in use.


Trivial Transactions / Sec

TRVRATE 08 FLTD Related statistics appear on the Transaction Activity Report. This number represents the total number of trivial transactions processed during the reporting interval.

Total/Virtual Ratio

TVRATIO 08 FLTD The Total/Virtual Ratio appears on the CPU Activity Report and represents the ratio of total CPU usage to Virtual CPU usage.

% Virtual Busy VIRTBUSY 08 FLTD This statistic appears on the CPU Activity Report and represents the percent of the CPU used by virtual machines in real problem states.

% VM I/O Wait WAITIOP 08 FLTD This statistic represents the percent of all virtual machines in an I/O wait state.

% VM Page Wait

WAITPAGP 08 FLTD This statistic represents the percent of all virtual machines in a page wait state.


Data Dictionary 219


RICO - Resource IUCV/VMCF Communications Activity Report

Table 44. RICO - Resource IUCV/VMCF Communications Activity Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

BLOCKIO %Err

BLKIOEP 08 FLTD Y Y Y The percent of error when using CP system service, BLOCKIO.

BLOCKIO Xfers

BLKIOXF INTG 08 FLTD Y Y Y Number of transfers between CP system service, DASD BLOCKIO, and other virtual machines.

CCS VM %Err

CCSEP 08 FLTD Y Y Y The percent of error when using CP system service, CCS

CCS VM Xfers

CCSXF INTG 08 FLTD Y Y Y Number of transfers between CP system service, CCS, and other virtual machines.


DATETIME STCK 08 CHAR The start date and time for this reporting interval.

MONITOR %Err

MONEP 08 FLTD Y Y Y The percent of error when using CP system service, MONITOR.

MONITOR Xfers

MONXF INTG 08 FLTD Y Y Y Number of transfers done for CP system service, MONITOR.

MSGALL %Err

MSGALLEP 08 FLTD Y Y Y The percent of error when using CP system service, MSGALL.

MSGALL Xfers

MSGALLXF INTG 08 FLTD Y Y Y Number of message transfers done for CP system service, MSGALL.

MSG %Err MSGEP 08 FLTD Y Y Y The percent of error when using CP system service, MSG.

MSG Xfers MSGXF INTG 08 FLTD Y Y Y Number of message transfers done for CP system service, MSG.



RPI %Err RPIEP 08 FLTD Y Y Y The percent of error when using CP system service, RPI.

RPI Xfers RPIXF INTG 08 FLTD Y Y Y Number of transfers done for CP system service, RPI.

SIGNAL %Err SIGNALEP 08 FLTD Y Y Y The percent of error when using CP system service, SIGNAL.

SIGNAL Xfers SIGNALXF INTG 08 FLTD Y Y Y Number of transfers between CP system service, SIGNAL, and other virtual machines.


IUCV VM %Err

VMIUCVEP 08 FLTD Y Y Y The percent of error when using IUCV between two virtual machines.

IUCV VM Xfers

VMIUCVXF INTG 08 FLTD Y Y Y Number of transfers done by IUCV between two virtual machines.

VMCF VM %Err

VMVMCFEP 08 FLTD Y Y Y The percent of error when using VMCF between two virtual machines.

VMCF VM Xfers

VMVMCFXF INTG 08 FLTD Y Y Y Number of transfers done by VMCF between two virtual machines.


Data Dictionary 221


RLPR - Resource LPAR Utilization Report

Table 45. RLPR - Resource LPAR Utilization Report


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

Logical CPU% LPARBUSY 08 FLTD Y Y Y Utilization of the system based on the number of logical processors available. Computed as: (Dispatch time / Elapsed time) * Number of LPs

Dispatch Time LPARDISP SECS 08 FLTD Y Y Y Total amount of time that all of the logical processors for this LPAR were busy during the reporting interval.

Number Processors LPARLPCT INTG 08 FLTD Y Y Y Number of logical processors assigned to this LPAR.

Name LPARNAME 08 CHAR Y Y Assigned name of the logical partition.

Number LPARNUM INTG 01 UBIN Y Y Assigned logical partition number.

LPAROVER CSEC 08 FLTD Y Y Y VM 1.2.0 or higher and LPAR management facility. Amount of logical CPU busy which was due to LP dispatching overhead.

Partition Overhead LPAROVHD PCT 08 FLTD Y Y Y VM 1.2.0 or higher and LPAR management facility. Percentage of overhead time across all logical processors.



Status LPARSTAT 08 CHAR Y Y Y Status of the logical partition during the reporting interval. Can be ACTIVE or INACTIVE. The partition that was used to collect the LPAR data will have an asterisk (*) appended (for example, “ACTIVE “).

Wait LPARWAIT 04 CHAR Y Y Y Status of the WAIT bit for the logical processors within this LPAR. If any LP has the WAIT bit ON, this field will contain “YES”.

Weight LPARWGHT INTG 08 FLTD Y Y Y Average weight of all logical processors defined for this LPAR. The weight values for dedicated processors will be 1000.

Physical CPU% PHYSBUSY 08 FLTD Y Y Y Utilization of the system based on the number of physical processors available. Computed as: (Dispatch time / Elapsed time) * Number of CPUs

Table 45. RLPR - Resource LPAR Utilization Report (continued)

Data Dictionary 223


RNSS - Resource Saved Segment/NSS Activity Report

Table 46. RNSS - Resource Saved Segment/NSS Activity Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF



Creation Time SNTCRTIM 08 STCK The date and time that the SPOOL file was created.

Segment Name SNTNAME 08 CHAR Y The name of the saved segment or NSS.

Users Non-Shared

SNTNUSRS INTG 08 FLTD Y Y Y The number of users who access the saved segment or NSS with a private copy.

Pages Saved SNTPAGCT INTG 08 FLTD Y Y Y The number of pages saved for this segment.

Pages Resident SNTRESPG INTG 08 FLTD The number of pages in memory for this saved system during this interval.

Page Faults SNTSHFLT INTG 08 FLTD Y Y Y The number of page faults generated in a shared saved segment and named saved system.

SPOOL ID SNTSPFID INTG 08 FLTD Y The ID number of the SPOOL file.

Pages Stolen SNTSTOLN INTG 08 FLTD Y Y Y The number of pages that were moved from real memory to external storage while being used, either by the demand scan, trim, or free-storage scan process.

Pages Defined SNTSTRCT INTG 08 FLTD Y Y Y The number of pages defined for this saved system.



Users Shared SNTSUSRS INTG 08 FLTD Y Y Y The number of users having shared access to the saved segment or NSS.


Table 46. RNSS - Resource Saved Segment/NSS Activity Report (continued)

Data Dictionary 225


RPAG - Resource Paging Activity Report

Table 47. RPAG - Resource Paging Activity Report


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF



Device Address DEVADDR ADDR 02 SUBI Y Y Real address of paging DASD.

Device Type DEVTYPE INTG 04 CHAR Y Y Type of DASD (for example: 3370 or 3380).

DASD Extent ENDCYL INTG 08 FLTD Y Y Y End extent allocated for paging on a device.

Extent % Full EXTFULL INTG 08 FLTD Y Y Y Percentage of page slots in use.

Paging Type PAGETYPE INTG 16 CHAR Y Y Type of paging.

Device Percent Busy

PCTBUSY INTG 08 FLTD Y Y Y The percentage of time DASD was found busy during the time frame.

Service Time SERVTIME MSEC 08 FLTD Y Y Y The average time it took to complete an I/O operation to a paging space.

Device Service Time

SERVTIME MSEC 08 FLTD Y Y Y The average time it took to complete an I/O operation.

DASD Extent STARTCYL INTG 08 FLTD Y Y Y Start extent allocated for paging on a device.


DASD Volser VOLSER INTG 06 CHAR Y Y Volume serial number of paging DASD.



RSCH - Resource Scheduler Storage Report

Table 48. RSCH - Resource Scheduler Storage Report


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

Avg Time AVGPGRD SECS 08 FLTD Y Y Y The average elapsed time in seconds that it takes to read one page.



E1 List Exp Indx EXPINDX1 INTG 08 FLTD Y Y Y The expansion index for short running users in the E1 queue.

E2 List Exp Indx EXPINDX2 INTG 08 FLTD Y Y Y The expansion index for medium-running users in the E2 queue.

E3 List Exp Indx EXPINDX3 INTG 08 FLTD Y Y Y The expansion index for long-running users in the E3 queue.

E1 List # Users EXPUSER1 08 FLTD Y Y Y The number of short running users in the eligible list for the E1 queue.

E2 List # Users EXPUSER2 08 FLTD Y Y Y The number of medium-running users in the eligible list for the E2 queue.

E3 List # Users EXPUSER3 08 FLTD Y Y Y The number of long-running users in the eligible list for the E3 queue.

System Pagein PAGERATE INTG 08 FLTD Y Y Y The number of pages per second being read in by the system.

Data Dictionary 227


Page Index PAGINDEX INTG 08 FLTD Y Y Y The system resource weight for paging. Used by the scheduler to decide how much of a bottleneck the paging resources are.

Stor Index STGINDEX INTG 08 FLTD Y Y Y The system resource weight for storage. Used by the scheduler to decide how much of a bottleneck the paging resources are.


Table 48. RSCH - Resource Scheduler Storage Report (continued)



RSEE - Resource Seek Analysis Report

Table 49. RSEE - Resource Seek Analysis Report


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

Avg. Move Per Seek AVGMOVE INTG 08 FLTD Y Y Y Average number of cylinders that were skipped for a seek into this minidisk.

Avg. Move Within Extent

AVGMVEXT INTG 08 FLTD Y Y Y Average number of cylinders that were skipped for a seek within this minidisk.



Real Address DEVADDR ADDR 02 SUBI Y Y The address of the real DASD device.

Device Type DEVTYPE INTG 04 CHAR Y Y The type of real DASD device.

DASD Extent ENDCYL INTG 08 FLTD Y Y Y The cylinder or block number on the real DASD device where the minidisk ends.

Extent Count NUMCYLS INTG 08 FLTD Y Y Y Difference between the start and end extents of this minidisk.

Total Seeks SEEKS 08 FLTD Y Y Total number of seeks to this minidisk.

Seeks In Extent SEEKSEXT INTG 08 FLTD Y Y Y The number of seeks made from one cylinder of the minidisk to another cylinder of the same minidisk.

DASD Extent STARTCYL INTG 08 FLTD Y Y Y The cylinder or block number on the real DASD device where the minidisk begins.

Data Dictionary 229



Virtual Address VCUU ADDR 02 UBIN Y Y The virtual address of this minidisk.

DASD Volser VOLSER INTG 06 CHAR Y Y The volume serial number for the real DASD device.

Userid WORKLOAD 08 CHAR Y Y The user ID of the user linked to this minidisk. If this area of the device is not allocated to a user, this field is set to SYSTEM.

Table 49. RSEE - Resource Seek Analysis Report (continued)



RSPO - Resource SPOOLing Activity Report

Table 50. RSPO - Resource SPOOLing Activity Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

Extent Count ALLOCCNT INTG 08 FLTD Y Y Y The number of cylinders or blocks allocated for the SPOOLing extent.

Available Slots AVAILSLT 08 FLTD Y Y Y The number of slots available at the time the sample was taken.



Device Address DEVADDR ADDR 02 SUBI Y Y Real address of the device where SPOOLing space is allocated.

Device Type DEVTYPE INTG 04 CHAR Y Y Device type for the real device.

DASD Extent ENDCYL INTG 08 FLTD Y Y Y The ending cylinder or block number for the SPOOLing extent.

Extent Percent Full

PERFULL 08 FLTD Y Y Y Percentage of space in use at the time the sample was taken.

DASD Extent STARTCYL INTG 08 FLTD Y Y Y The starting cylinder or block number for the SPOOLing extent.


Used Slots TOTUSLOT INTG 08 FLTD Y Y Y The number of used slots at the time the sample was taken.

DASD Volser VOLSER INTG 06 CHAR Y Y Volume serial number for the real device.

Data Dictionary 231


RSTR - Resource Storage Management Report

Table 51. RSTR - Resource Storage Management Report


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

Available List Frames

AVLFRAMS INTG 08 FLTD Y Y Y The number of frames currently on the available list. This number will be higher than the high threshold at IPL time.

Available List High Threshold

AVLHGHTH INTG 08 FLTD Y Y Y The high threshold for the available list replenishment subsystem.

Available List Low Threshold

AVLLOWTH INTG 08 FLTD Y Y Y The low threshold for the available list replenishment subsystem.

Frame Waits AVLWAIT INTG 08 FLTD Y Y Y The number of tasks that cannot be executed because they are waiting for a frame.

Page Faults/Sec Block

BLOKFLTS INTG 08 FLTD Y Y Y The average number of page faults per second for a block of pages during the reporting interval.



DPA Frames DPAFRAMS INTG 08 FLTD Y Y Y The number of frames allocated to the dynamic paging area.



Unsuccessful Demand Scans

DSCNFAIL INTG 08 FLTD Y Y Y The number of times the demand scan was invoked and could not replenish the available list to its threshold.

Extend Frames EXTFRAMS INTG 08 FLTD Y Y Y The number of frames used by free-storage management.

Extend Waits EXTWAIT INTG 08 FLTD Y Y Y The number of deferred pages waiting for a frame.

CP Pageins PGFAULTS INTG 08 FLTD Y Y Y The number of pages read in for CP.

Page Faults/Sec Single

SINGFLTS INTG 08 FLTD Y Y Y The average number of page faults per second for single-page reads during the reporting interval.


Table 51. RSTR - Resource Storage Management Report (continued)

Data Dictionary 233


RSYS - Resource System Information Report

Table 52. RSYS - Resource System Information Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

Abend Code ABNDCODE BYTE 08 CHAR CP abend code (only if previous IPL ended with an abnormal termination).

Actual Storage<2GB

AREALSTR BYTE 08 FLTD The real storage minus any offline (unusable) storage frames. Applies to storage below 2 GB.

Actual Storage AREALSTG BYTE 08 FLTD The real storage minus any offline (unusable) storage frames. Value is 0 for 32-bit images. Applies to all storage for 64-bit images.

Expanded Storage Size

CPEXPSTR INTG 08 FLTD The number of megabytes of expanded storage attached to this machine.

Size of Resident CP

CPSIZE INTG 08 FLTD The number of bytes occupied by the resident CP.

CP Trace Table CPTRACE INTG 08 FLTD The number of megabytes occupied by the CP trace table.

CPU Model CPUMODEL FLAG 02 UBIN Type of CPU being run (for example: 2064).



Time of IPL IPLTIME 08 STCK Date and time of most recent IPL.

Logical Processor CAPPING status

LPARCAPS FLAG 01 BITF CAPPING status for each LP. Each bit in this byte represents the CAPPING status of the corresponding LP (for example, if bit 3 is on, it indicates that LP 3 has CAPPING set to ON).



Dispatch Interval LPARINTV INTG 02 MSEC The dispatching interval for all LPARs. A data value of x’FFFF’ indicates dynamic.

Logical Processors

LPARLPCT INTG 02 UBIN Number of logical processors assigned to this LPAR.

LPAR Name LPARNAME 08 CHAR Name of this logical partition.

LPAR Number LPARNUM INTG 01 UBIN Number of this logical partition.

Physical Processors

LPARPHYS INTG 02 UBIN Number of CPUs in the physical partition.

Logical Processor WAIT status

LPARWAIT FLAG 01 BITF WAIT status for each LP. Each bit in this byte represents the WAIT status of the corresponding LP (for example, if bit 3 is on, it indicates that LP 3 has its WAIT status set to ON).












Data Dictionary 235








Non-Pageable Pages

NPAGECNT INTG 08 FLTD The number of pages of storage not available for paging.

Operating System

OPSYSREL FLAG 08 BITF Version and release of the host VM operating system.

Pageable Pages PAGECNT INTG 08 FLTD The number of pages of storage available for use by the paging subsystem.

Real Storage<2GB (genned)

REALSTR BYTE 08 FLTD The number of megabytes of storage genned at system gen time. Applies to storage below 2 GB.

Real Storage (genned)

AREALSTG BYTE 08 FLTD The number of megabytes of storage genned at system gen time. Value is 0 for 32-bit images. Applies to all storage for 64-bit images.

Service Level SERVLVL 08 CHAR Maintenance service level of the host VM operating system.





Time of Last Abend

TERMTIME 08 STCK Date and time of CP abend (only if previous IPL ended with an abnormal termination).

V=R Free Storage

VRFRESZ BYTE 08 FLTD The number of megabytes set aside for virtual machine free storage.

V=R Storage Area

VRSIZE BYTE 08 FLTD The number of megabytes set aside for virtual machines.


Data Dictionary 237


RTDI - Resource Temporary Disk Activity Report

Table 53. RTDI - Resource Temporary Disk Activity Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

Extent Count ALLOCCNT INTG 08 FLTD Y Y Y The total number of cylinders or blocks allocated for the temporary disk extent.



Device Address

DEVADDR ADDR 02 SUBI Y Y Real address of the device where the temporary disk is allocated.

Device Type DEVTYPE INTG 04 CHAR Y Y Y Device type of the real device.

DASD Extent ENDCYL INTG 08 FLTD Y Y Y The ending cylinder or block number for the temporary disk extent.

Largest Extent LAREXTAV INTG 08 FLTD The largest number of available cylinders or blocks that could be used to allocate a minidisk during the reporting period.

Extent Percent Full

PERFULL 08 FLTD Y Y Y Percent of space in use at the time of the Collector sampling. If more than one sampling was taken during the reporting interval, this is an average of the sampling percents.


DASD Extent STARTCYL INTG 08 FLTD The starting cylinder or block number for the temporary disk extent.

Total Extent Available

TOTEXTAV INTG 08 FLTD Y Y Y The total number of available cylinders or blocks.

DASD Volser VOLSER INTG 06 CHAR Y Y The volume serial number of the real device.



RTRA - Resource Transaction Activity Report

Table 54. RTRA - Resource Transaction Activity Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF






NTRVRATE 08 FLTD Y The average number of trivial transactions per second during the reporting interval.


NTRVRESP 08 FLTD Y Y Y The average number of seconds needed to complete one non-trivial transaction during the reporting interval.



TRVCNT INTG 08 FLTD Y Y Y The number of trivial transactions that took place during the reporting interval for uniprocessor virtual machines.


TRVRATE 08 FLTD Y Y Y The average number of trivial transactions per second during the reporting interval for uniprocessor virtual machines.


TRVRESP 08 FLTD Y Y Y The average number of seconds needed to complete one trivial transaction during the reporting interval for uniprocessor virtual machines.

Data Dictionary 239


RVDS - Resource VDISK Activity Report

Table 55. RVDS - Resource VDISK Activity Report

Columm Header

Field Name

Unit Field Length

Data Type

KeywordsDescription

SO

RT

GR

AP

H

RIF

/SIF

FBA-512 Blocks

BLOCKS INTG 08 FLTD Y Y Y Number of simulated 512 byte blocks allocated for this V-disk.

Virtual Address DEVADDR ADDR 02 SUBI Y Y The V-disk virtual device address.

Time ELAPSE SECS 08 FLTD Y Y Y Elapsed time during this reporting interval that the V-disk existed.

Links LINKS INTG 08 FLTD Y Y Maximum number of users linked to the V-disk.

PGRDs / Second

PGRDRATE

INTG 08 FLTD Y Y Y Average page read operations (primary plus expanded) per second for this V-disk.

Page Reads PGREADS INTG 08 FLTD Y Y Y Number of page read operations (primary plus expanded) performed for this V-disk.

Page Writes PGWRITES INTG 08 FLTD Y Y Y Number of page write operations (primary plus expanded) performed for this V-disk.

PGWRs / Second

PGWTRATE

INTG 08 FLTD Y Y Y Average page write operations (primary plus expanded) per second for this V-disk.

Resident Pages RESPAGES INTG 08 FLTD Y Y Y Average number of pages (primary plus expanded) resident during the reporting interval.

TDisk TDISK 04 CHAR Y Y Indicates whether this V-disk is a dynamically created temporary disk. The value can be YES or NO.

Creator / Owner

USERID 08 CHAR Y Y Userid of the virtual machine that created or owns the V-disk.

VIOs / Second VIORATE INTG 08 FLTD Y Y Y Average number of virtual I/O operations per second for this V-disk.



WBOT - Workload Bottleneck Analysis Report

Table 56. WBOT - Workload Bottleneck Analysis Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF




% CPU Busy USEDCPUP 08 FLTD Y Y Y The percentage of time this workload was using the CPU.

% CF Wait WAITCFSP 08 FLTD Y The percentage of time this workload was in a console function wait state.

% CPU Wait WAITCPUP 08 FLTD Y Y Y The percentage of time this workload was in a CPU wait state.

% Idle WAITIDLP 08 FLTD Y Y Y The percentage of time this workload was idle during the reporting interval.

% SVM Wait WAITIDSP 08 FLTD Y Y Y The percentage of time this workload was idle due to a service machine wait.

% Other WAITOTHP 08 FLTD Y Y Y The percentage of time this workload was in wait state other than those mentioned above.

% Page Wait WAITPAGP 08 FLTD Y Y Y The percentage of time this workload was found in a page wait state.

% Sim Wait WAITSIMP 08 FLTD Y Y Y The percentage of time this workload was in an instruction simulation wait state.

I/O Waits Dev (1)

WBODEV1 ADDR 02 SUBI The device address of the device with the highest I/O wait percent for this workload.

Data Dictionary 241


I/O Waits % (1)

WBODEV1P 08 FLTD Y Y Y The I/O wait percent of the device with the highest I/O wait percent for this workload.

I/O Waits Dev (2)

WBODEV2 ADDR 02 SUBI The device address of the device with the second highest I/O wait percent for this workload.

I/O Waits % (2)

WBODEV2P 08 FLTD Y Y Y The I/O wait percent of the device with the second highest I/O wait percent for this workload.

I/O Waits Dev (3)

WBODEV3 ADDR 02 SUBI The device address of the device with the third highest I/O wait percent for this workload.

I/O Waits % (3)

WBODEV3P 08 FLTD Y Y Y The I/O wait percent of the device with the third highest I/O wait percent for this workload.

I/O Waits Dev (4)

WBODEV4 ADDR 02 SUBI The device address of the device with the fourth highest I/O wait percent for this workload.

I/O Waits % (4)

WBODEV4P 08 FLTD Y Y Y The I/O wait percent of the device with the fourth highest I/O wait percent for this workload.

I/O Waits Dev (5)

WBODEV5 ADDR 02 SUBI The device address of the device with the fifth highest I/O wait percent for this workload.

I/O Waits % (5)

WBODEV5P 08 FLTD Y Y Y The I/O wait percent of the device with the fifth highest I/O wait percent for this workload.

VM Workload

WORKLOAD 08 CHAR Y Y One or more virtual machines grouped by user ID, account code, or distribution code.

Table 56. WBOT - Workload Bottleneck Analysis Report (continued)



WCPU - Workload CPU Report

Table 57. WCPU - Workload CPU Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF

CP Percent CPPCT 08 FLTD Y Y Y Percent of total CPU used by the system to manage this workload.

CP Seconds CPSECS SECS 08 FLTD Y Y Y Total CP seconds used by this workload (to nearest second).


CPU Seconds CPUSECS INTG 08 FLTD Y Y Y Total CPU seconds used by this workload (to nearest second).



Session Time SESSTIME SECS 08 FLTD Y Y Total time this workload was logged on (to nearest second).


Virtual Percent VIRTPCT 08 FLTD Y Y Y Percent of virtual CPU utilization for the workload specified.

Virtual Seconds VIRTSECS SECS 08 FLTD Y Y Y Total virtual CPU seconds used by this workload (to nearest second).

Vector Seconds WKLVECTO MSEC 8 FLTD Y Y Y The number of seconds used in the vector facility by this workload.

Vector Overhead

WKLVECTU MSEC 8 FLTD Y Y Y The number of seconds used to load and unload the vector facility for this workload.

VM Workload WORKLOAD

08 CHAR Y Y User or group of users specified by GROUP keyword.

Data Dictionary 243


WICO - Workload IUCV/VMCF Communications Activity Report

Table 58. WICO - Workload IUCV/VMCF Communications Activity Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF




IUCV Source Xfers

WKLISEVM INTG 08 FLTD Y Y Y The number of IUCV data transfers that were sent by this virtual machine during this reporting interval.

IUCV Target Xfers

WKLISTVM INTG 08 FLTD Y Y Y The number of IUCV data transfers that were received by this virtual machine during this reporting interval.

IUCV % Err WKLIUCVE 08 FLTD Y Y Y The percent of errors for IUCV for this virtual machine during this reporting interval.

VMCF % Err WKLVMCFE 08 FLTD Y Y Y The percent of errors for VMCF for this virtual machine during this reporting interval.

VMCF Source Xfers

WKLVSEVM 08 FLTD Y Y Y The number of VMCF data transfers sent by this virtual machine during this reporting interval.

VMCF Target Xfers

WKLVSTVM INTG 08 FLTD Y Y Y The number of VMCF data transfers received by this virtual machine during this reporting interval.




WSTO - Workload Paging/Storage Report

Table 59. WSTO - Workload Paging/Storage Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF




Page Rate/Sec PAGERATE 08 FLTD Y Y Y The rate of page-ins and page-outs for this workload (in pages/sec.).

Page Reads PAGREADS INTG 08 FLTD Y Number of page reads over the specified period of time.

Page Writes PAGWRTS INTG 08 FLTD Y Y Y Number of page writes over the specified period of time.

Resident Pages

RESPAGES 08 FLTD Y Y Y The current number of pages physically in main storage for this workload.

Storage Size in K

STORSIZE BYTE 08 FLTD Y Y Y Average storage size for this workload.

Exp Stor Attached

WKLXATT INTG 08 FLTD Y Y Y The number of megabytes of expanded storage attached to this workload.

Exp Stor Movement

WKLXMOV INTG 08 FLTD Y Y Y The number of expanded pages moved for this workload.

Exp Stor Paging

WKLXPAG INTG 08 FLTD Y Y Y The number of expanded storage blocks allocated to this workload by CP for paging.

VM Workload WORKLOAD 08 CHAR Y Y User or group of users specified by GROUP keyword.


WSS 08 FLTD Y Y Y A user’s projected working set size. This value is calculated each time a user drops from queue, and is based on the number of pages referenced during the last stay in queue.

Data Dictionary 245


WSUM - Workload Summary Report

Table 60. WSUM - Workload Summary Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF





Page I/O Count PAGIOCNT INTG 08 FLTD Y Y Y Total page transfers.

Session Time SESSTIME SECS 08 FLTD Y Y Total logon time for this workload (to nearest second).

SPOOL I/O Count

SPLIOCNT INTG FLTD Y Y Y Total I/O count for all unit record devices for this workload.

Total I/O Count TOTIOCNT INTG 08 FLTD Y Y Y Total number of I/O requests over the specified interval.

DASD I/O Count

WKLVDIO INTG 08 FLTD Y Y Y The number of virtual start I/Os issued to DASD devices by this workload during this reporting interval.

Other I/O Count

WKLVOIO INTG 08 FLTD Y Y Y The number of I/Os issued to other devices by this workload during this reporting interval.

Unit Record Count

WKLVUIO INTG 08 FLTD Y Y Y The number of virtual Start I/Os issued to unit record devices by this workload during this reporting interval.

VM Workload WORKLOAD 08 CHAR Y Y User or group of users specified with GROUP keyword.


WSS 08 FLTD Y Y Y Average working set size for this workload.



WTRA - Workload Transaction Activity ReportTable 61. WTRA - Workload Transaction Activity Report

Columm Header


Data Type

Keywords

Description

SO

RT

GR

AP

H

RIF

/SIF






NTRVRATE 08 FLTD Y Y Y The average number of trivial transactions per second during the reporting interval for this workload.


NTRVRESP 08 FLTD Y Y Y The average number of seconds needed to complete one non-trivial transaction during the reporting interval for this workload.



TRVCNT INTG 08 FLTD Y Y Y The number of trivial transactions that took place during the reporting interval for this workload.


TRVRATE 08 FLTD Y Y Y The average number of trivial transactions per second during the reporting interval for this workload.


TRVRESP 08 FLTD Y Y Y The average number of seconds needed to complete one trivial transaction during the reporting interval for this workload.


Index 247

Symbols* (asterisk, comment line) 53

Numerics20st century indicator 17621st century indicator 176

AACCTGROUP 61

in SET command 61ACCUM command

examples 185syntax 183

accumulation, data 24ADDRSPAC 205Adobe portable document format 13archiving 182automated maintenance procedure 193

BBAND

in OBTAIN command 173in REPORT command 56

bar chart of DASD device activity 158bar chart of ten most active DASD devices 159block

in PAGESEP command 67bottleneck analysis

report 80Bottleneck Analysis Report 80, 125, 207, 240

Ccandle system code 17Candle web site 12century indicator 176Channel Path Activity Report 82, 209character graphs from within EPILOG 145CHPACT 205CLEAR

in SET command 54CMS

communicating with CMS 68issuing from EPILOG 68

code, system 17collector

keywords required for reports 142

overview 23recording interval 23sampling interval 23validation interval 23

collector keywords needed for OMEGAMON displays 142

collector keywords needed for reports 142column headers, data dictionary 203COMBINE

in OBTAIN command 173in REPORT command

example 57in report layout 76with GRAPH keyword 146

command 24, 49command file examples 179command file, EVACCUM exec 183command file, EVREPT 49command keywords, OBTAIN 172command syntax, OBTAIN 171commands

ACCUM 183CP 68EVACCUM 183PRODUCTS 69REPORT 53reporter

in User Request Log 141ZAPS 69

commands, reporter 52comment lines 53communicating with CMS 68continuation character 52Conventions

reporter commands 52abbreviation 52long form 52short form 52

CP commandexample 68syntax 68

CPUActivity Report 83

CPU Activity Report 210CPU Report 128, 242CPUACT 205creating an automated maintenance procedure 193

Index


customized report 51

DDASD

Activity Report 85DASD Activity Report 85, 212DASDREP 50Data Accumulation Facility 24data dictionary 195, 201

column headers 203Data Extraction Facility 24data extraction using OBTAIN 164datastore 181, 193

customizing maintenance 193maintenance 181overview 23percent full 73

date rangein OBTAIN command 173

DATEFORMin SET command 55

Datenamein REPORT command

in SET command 55DAYOFWK

in REPORT commandin SET command 56

delimiters 52DEXTACT 205dictionary, data 195, 201DISKFULL 182displays, OMEGAMON (collector keywords

needed) 142DISTGROUP

in SET command 61downloading the OBTAIN output file 165DUPLICATE

in PAGESEP command 67DVOLACT 205

EELEMENTS

in OBTAIN command 174elig 95, 217END command

defined 69ENDDATE in REPORT command

in SET command 55ENDTIME in REPORT command

in SET command 56environments for report printing 205EPILOG maintenance 69EPILOG version 69

error messagesin user request log 140

EVACCUMcommand file 183examples 185output files 184syntax 183

EVACCUM EXEC 183EVOBT EXEC 170EVREPT EXEC 49

executing 51modifying 49

EVREPT EXEC command file 49EVREPT EXEC running 50EVTDUMP EXEC 187

syntax 187EVTLOAD EXEC 191

syntax 191examples

command file 179EXEC files

EVACCUM 183EVOBT 170EVTDUMP 187EVTLOAD 191

exiting from the reporter 69expanded storage

in problem-solving 35Expanded Storage Migration Report 87, 213extracting data 24

using OBTAIN 164with EVOBT EXEC 170

Ffacility, data accumulation 24facility, data extraction 24file types, report 205file, command (EVREPT) 49file, reporter

naming 49overview

samples 24flat file

extracting data for 170FOLDOFF

in PRTCNTL command 66FOLDON

in PRTCNTL command 66FORMAT

in OBTAIN command 174format, page 0 74formatting the separator page 66forms, short and long 52

Index 249

Free Storage Activity Report 89, 214

GGDDM/ICU

to generate sample charts 162using OBTAIN output files 152

generate sample charts using GDDM/ICU 162generating a customized report 51generating a sample report 50generating character graphs from within

EPILOG 145generating graphs on a PC 164generating graphs with GDDM/ICU 152generating reports 53generic report format for trend graphs 145generic report layout 75GRAPH

in REPORT command 145in SET command 59

graphs 170extracting data for 170mainframe 145

comparing 150generic layout 145using GDDM/ICU 152

PCusing OBTAIN output files 164

Group Definition Report 77, 206Group Report 77GRPD - Group Definition Report 77, 205, 206

example 77GRPDEFN 205GRPREP 50

Hheaders, column (data dictionary) 203High-Level Summary Report 91, 215

Iinterpreting the reports 71IPREFIX

in OBTAIN command 174in REPORT command 62in SET command 62

IUCV/VMCF Communications Activity Report 96, 130, 219, 243

Kkeywords 66

OBTAIN 172short forms 52title 74

LLASTMONTH


LASTYEARin REPORT command

in SET command 55layout, report 75line chart of paging device load 155line chart of resource availability index 156line, comment 53LINES

in PRTCNTL command 66long and short forms 52LPAR 205LPAR Activity Report 99LPAR Utilization Report 221

Mmaintaining the datastore 181maintenance

customizing 193datastore 181record of ZAPS applied 69

maintenance, EPILOG 69MAXSCALE 59


with GRAPH keyword 145MAXSCALE with GRAPH 145multi-line chart of CPU utilization 152multi-line chart of logged-on users 153

OOBSET GLOBAL 171OBTAIN command

defined 170EVOBT EXEC

examples 179keywords 172OBSET GLOBAL 171output files

for mainframe 175, 177for PC 178

running 170syntax 171

OMEGAMON displays, collector keywords needed 142

online help 49OUTFILE

in OBTAIN command 174output files generated by FORMAT(COL) 177


output files generated by FORMAT(INT) 175output files generated by FORMAT(PC) 178output files, EVACCUM 184overview 21

Ppage 0 format 74page, separator 66PAGEREP

DASDREP 50pages, preliminary 73PAGESEP - Formatting the Separator Page 66PAGESEP command

defined 66examples 67keywords 67syntax 67

pagingin problem-solving 35

Paging Activity Report 104Paging/Storage Report 132parameters 49, 170PC graphics

using OBTAIN output files 164PDF files, adding annotations 13pie chart of wait reasons 160preliminary pages 73print report problems 205printing

formatting output 66separator pages 66

printing problems 13problems, report printing 205problem-solving 25

expanded storage 35paging 35SPOOLing 42using RBO 26using RCPU 29using RDAS 44using REXP 37using RHLS 35using RSEE 32, 41using RTRA 30using WBOT 31, 40using WTRA

in problem-solving 30workload transaction analysis 30

procedure, automated maintenance 193PRODUCTS command

defined 69example 69

PRTCNTL 66PRTCNTL - Controlling Printer Output

controlling printer output 66PRTCNTL command

definedPRTCNTL 66

examples 66keywords 66syntax 66

PRTCNTL keywordsFOLDOFF 66FOLDON 66LINES 66

Qq1 95, 217

RRANGE

in OBTAIN command 173in REPORT command 56, 57

RBOT 26, 205RBOT - Resource Bottleneck Analysis Report 80,

207RBOT report

example 80in problem-solving 26

RBOT1 171RBOT2 171RCHP 205RCHP - Resource Channel Path Activity Report 82,

209RCHP report

example 82RCPU 27, 29, 205RCPU - Resource CPU Activity Report 83, 210RCPU report


RCPU1 171RCPU2 171RCPUREP

RCPUREP 50RDAS 44, 205RDAS - Resource DASD Activity Report 85, 212RDAS report


RDAS1 171RDAS2 171recording interval 23REPLACE

in OBTAIN command 175

Index 251

REPORT and SET - Generating Reports 53REPORT command

defined 53examples 63keywords 54syntax 53

report environments 205report file types 205report generation 53report interpretation 71REPORT keywords

BANDRANGE 56

Datename 55DAYOFWK 56ENDDATE 55ENDTIME 56GRAPH 59IPREFIX 62LASTMONTH 55LASTWEEK 55LASTYEAR 55report name 54REPORTIF

RIF 57SELECTIF

SIF 58SORTBY 62STARTDATE 55SUMMARY 63SYSTEMID 59THISMONTH 55THISWEEK 55THISYEAR 55time range

STARTTIME 56TIMEZONE 63TITLE 63TODAY 55USERGROUP 60YESTERDAY 55

report layout, generic 75report printing environments 205report printing problems 205report sample 50report, Bottleneck Analysis 80Report, Channel Path Activity 82Report, CPU Activity

CPU Activity Report 83report, customized

customizing 51how to print

how to use 51

Report, DASD Activity 85Report, Expanded Storage Migration 87Report, Free Storage Activity 89Report, Group Definition 77Report, High-Level Summary 91Report, IUCV/VMCF Communications Activity

Report 96Report, LPAR Activity 99Report, Paging Activity 104Report, Saved Segment/NSS Activity 102Report, Scheduler Storage 106Report, Seek Analysis 108Report, SPOOLing Activity 110Report, Storage Management 112Report, System Information 115Report, Temporary Disk Activity 119Report, Transaction Activity 121Report, VDISK Activity

VDISK Activity Report 123Report, Workload Bottleneck Analysis 125Report, Workload CPU 128Report, Workload IUCV/VMCF Communications

Activity 130Report, Workload Paging/Storage 132Report, Workload Summary 135Report, Workload Transaction Activity 137Reporter 24reporter

command file 24, 49samples 49

overview 24reporter command

in user request log 141syntax rules 52

reporter commands 52reporter exit 69reporter keywords

GRAPH 145MAXSCALE 145

REPORTIFin OBTAIN command 173in REPORT command

example 58in SET command 57

Reportsprinting samples 50

reportscollector keywords required 142generic layout 75graphs 145page 0 74preliminary pages 73resource


list of 79trend graphs 145user request log 140workload

list of 125Resource Bottleneck Analysis Report 80, 207Resource Channel Path Activity Report 82, 209Resource CPU Activity Report 210

CPU Activity Report 83Resource DASD Activity Report 85, 212Resource Expanded Storage Migration Report 87,

213Resource Free Storage Activity Report 89, 214Resource High-Level Summary Report 91, 215Resource IUCV/VMCF Communications Activity

Report 96, 219Resource LPAR Activity Report 99Resource LPAR Utilization Report 221Resource Paging Activity Report 104Resource Reports 79resource reports

See Reports 79Resource Saved Segment/NSS Activity Report 102,

223Resource Scheduler Storage Report 106, 226Resource Seek Analysis Report 108, 228Resource SPOOLing Activity Report 110, 230Resource Storage Management Report 112, 231Resource System Information Report 115, 233Resource Temporary Disk Activity Report 119, 237Resource Transaction Activity Report 121, 238Resource VDISK Activity Report 123, 239response time

See Workload Transaction Activity ReportREXP 37, 205REXP - Resource Expanded Storage Migration

Report 87, 213REXP report


RFRE 205RFRE - Resource Free Storage Activity Report 89,

214RFRE report 90RHLS 35, 205RHLS - Resource High-Level Summary Report 91,

215RHLS report 92

in problem-solving 35RHLS1 171RHLS2 171RICO 205RICO - Resource IUCV/VMCF Communications

Activity Report 96, 219RICO report

example 97RIF


RLPR 205RLPR - Resource LPAR Activity Report 99RLPR - Resource LPAR Utilization Report 221RLPR report sample 100RNSS 205RNSS - Resource Saved Segment/NSS Activity

Report 102, 223RNSS report

example 102RPAG 205RPAG - Resource Paging Activity Report 104, 225RPAG report

example 104RPAG1 171RSCH 205RSCH - Resource Scheduler Storage Report 106,

226RSCH report

example 106RSEE 41, 205RSEE - Resource Seek Analysis Report 108, 228RSEE report

example 109in problem-solving 32, 41

RSEEK 32RSEEKS 205RSPO 205RSPO - Resource SPOOLing Activity Report 110,

230RSSMGMT 205RSTR 205RSTR - Resource Storage Management Report 112,

231RSTR report

example 113RSYS 205

example 115RSYS - Resource System Information Report 115,

233RTDI 205RTDI - Resource Temporary Disk Activity

Report 119, 237RTDI report

example 119RTRA 26, 30, 205RTRA - Resource Transaction Activity Report 121,

238RTRA report

Index 253


running the EVACCUM EXEC 185running the EVOBT EXEC 170running the EVREPT EXEC 50running the EVTDUMP EXEC 189running the EVTLOAD EXEC 192RVDS 205RVDS - Resource VDISK Activity Report 123, 239

SSample files

GRPREP 50sample graphs generated on a PC 165Sample OBTAIN Command Files

RBOT1 171sample report 50sampling interval 23Saved Segment/NSS Activity Report 102, 223Saved Segments

NSS Activity Report 102SCAN

in SET command 60scatter-line chart of paging rate/CPU utilization 157SCHACT 205Scheduler Storage Report 106, 226Seek Analysis Report 108, 228SELECTIF

example 58, 59in OBTAIN command 173in REPORT command

in SET command 58separator page 66SET command 53

definedSET 53

examples 65keywords 54syntax 53

SET keywordsACCTGROUP 52, 61BAND

RANGE 56CLEAR 54DATEFORM 55Datename 55DAYOFWK 56DISTGROUP 52, 61ENDDATE 55ENDTIME 56GRAPH 59in REPORT command

in SET command 55

IPREFIX 62LASTMONTH 55LASTWEEK

LASTWEEK 55LASTYEAR 55MAXSCALE 59REPORTIF

RIF 57SCAN 60SORTBY 62STARTDATE 55SUMMARY 63SYSTEMID 59THISMONTH 55THISWEEK 55THISYEAR 55time range

STARTTIME 56TIMEZONE 63TITLE 63TODAY 55USERGROUP 52YESTERDAY 55

short and long forms 52shows the general form of the User Request

Log. 140SIF


Solving Data Center Problems 25Solving Paging and Storage Problems 35Solving Spooling Problems 42Solving Workload Transaction Problems 30SORTBY


SPOOLin problem-solving 42

SPOOLing Activity Report 110, 230stacked bar chart of wait reasons 161STARTDATE in REPORT command

in SET command 55STARTTIME


statistics packagesextracting data for 170

Storage Management Report 112, 231STRACT 205SUMMARY


in SET command 63


Summary Report 245Summary Report, Workload 135support of VM systems by Version 580 17Syntax 53, 68

blank spaces 52commas 52continuation character 52delimiters 52equal signs 52hyphen 52parentheses 52quotes 52single quotes 52

syntax 49syntax, EVACCUM exec 183syntax, EVTDUMP exec 187syntax, EVTLOAD 191syntax, OBTAIN 171SYSBOT 205SYSCOM 205SYSCONF 205system code 17System Information Report 115, 233system overview 21SYSTEMID


in SET command 59in report layout 76

systems supported by Version 580 17

TTemporary Disk Activity Report 119, 237the collector 23THISMONTH


THISWEEKin REPORT command

in SET command 55THISYEAR


Time rangein REPORT command

in SET command 56time range

in OBTAIN command 173TIMEZONE


TITLEin PAGESEP command 67


with GRAPH keyword 146TODAY


Transaction Activity Report 121, 137, 238trend graphs 145

generic layout 145

Uuser 95, 217user request log

defined 140general format 140naming 140

USERGROUPin REPORT command 60

using GDDM/ICU to generate sample charts 162using MAXSCALE with GRAPH 145using OBTAIN for 170using OBTAIN to extract data 164

Vvalidation interval 23VDISK Activity Report 123, 239VDISK sample report 123version of EPILOG 69VM systems supported by Version 580 17VMCF/IUCV Communications Activity Report 96,

130

WWBOT 31, 40, 205WBOT - Workload Bottleneck Analysis Report 125,

240WBOT report

example 125in problem-solving 31, 40

WCPU 205WCPU - Workload CPU Report 128, 242WCPU report

example 129WCPUREP

WCPU 50WICO 205WICO - Workload IUCV/VMCF Communications

Activity Report 130, 243WICO report

example 131WKLDACT 205Workload Bottleneck Analysis Report 125, 240

Index 255

Workload CPU Report 128, 242Workload IUCV/VMCF Communications Activity

Report 130, 243Workload Paging/Storage Report 132Workload Reports 125workload reports

See reports 125Workload Summary Report 135, 245Workload Transaction Activity Report 137workload transaction analysis

in problem-solving 30WRKBOT 205WRKTRN 205WSTO 205WSTO - Workload Paging/Storage Report 132WSTO report

example 133WSTRREP

WSTRREP 50WSUM 205WSUM - Workload Summary Report 135, 245

WSUM reportexample 136

WSUMREPWSUMREP 50

WTRA 30, 205WTRA - Workload Transaction Activity Report 137WTRA report

example 138

Yyear 2000

21st century indicator 176YESTERDAY


ZZAPS command

defined 69example 69


Documents

EPILOG for VM Product Manual, V610publib.boulder.ibm.com/tividd/td/ITOfV/GC32-9237... · Product Manual EPILOG™ for VM Version 610 for VM and z/VM GC32-9237-00 January 2004 Candle