OMEGAMON II for DBCTL User’s Guide ഀ嘀攀爀猀椀漀渀㔀publib.boulder.ibm.com/tividd/td/ITOMEGAIIfDBCTL/GC32-9260-00/e… · User’s Guide OMEGAMON II ® for DBCTL Version

User’s GuideOMEGAMON II® for DBCTL

Version 510

GC32-9260-00

March 2002

Candle Corporation201 North Douglas Street

El Segundo, California 90245

2 OMEGAMON II for DBCTL User’s Guide Version 510

Registered trademarks and service marks of Candle Corporation: AF/OPERATOR, AF/PERFORMER, AF/REMOTE, Availability Command Center, Candle, Candle Command Center, Candle Direct logo, Candle Electronic Customer Support, Candle logo, Candle Management Server, Candle Management Workstation, Candle Technologies, CL/CONFERENCE, CL/SUPERSESSION, CommandWatch, CT, CT/Data Server, CT/DS, DELTAMON, ETEWatch, IntelliWatch, IntelliWatch Pinnacle, MQSecure, MQView, OMEGACENTER, OMEGAMON, OMEGAMON/e, OMEGAMON II, OMEGAMON Monitoring Agent, OMEGAVIEW, OMEGAVIEW II, PQEdit, Solutions for Networked Applications, Solutions for Networked Businesses, and Transplex.Trademarks and service marks of Candle Corporation: Alert Adapter, Alert Adapter Plus, Alert Emitter, AMS, Amsys, AutoBridge, AUTOMATED FACILITIES, Availability Management Systems, Candle Alert, Candle Business Partner Logo, Candle Command Center/SentinelManager, Candle CommandPro, CandleLight, CandleNet, CandleNet 2000, CandleNet Command Center, CandleNet eBP, CandleNet eBP Access, CandleNet eBP Administrator, CandleNet eBP Broker Access, 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, CandleNet eBusiness Platform Administrator, CandleNet eBusiness Platform Connector, CandleNet eBusiness Platform Connectors, CandleNet eBusiness Platform Powered by Roma Technology, CandleNet eBusiness Platform Service Directory, CandleNet Portal, CCC, CCP, 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, DEXAN, e2e, eBA, eBA*ServiceMonitor, eBA ServiceNetwork, eBAA, eBAAuditor, eBAN, eBANetwork, eBAAPractice, eBP, eBusiness Assurance, eBusiness Assurance Network, eBusiness at the speed of light, eBusiness at the speed of light logo, eBusiness Exchange, eBusiness Institute, eBX, End-to-End, ENTERPRISE, Enterprise Candle Command Center, Enterprise Candle Management Workstation, Enterprise Reporter Plus, EPILOG, ER+, ERPNet, ESRA, ETEWatch Customizer, HostBridge, InterFlow, Candle InterFlow, Lava Console, MessageMate, Messaging Mastered, Millennium Management Blueprint, MMNA, MQADMIN, MQEdit, MQEXPERT, MQMON, NBX, NetGlue, NetGlue Extra, NetMirror, NetScheduler, OMA, OMC Gateway, OMC Status Manager, OMEGACENTER Bridge, OMEGACENTER Gateway, OMEGACENTER Status Manager, OMEGAMON Management Center, OMEGAMON DE, OMEGAMON XE, OSM, PC COMPANION, Performance Pac, PowerQ, PQConfiguration, PQScope, Response Time Network, Roma, 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, TMA2000, Tracer, Unified Directory Services, Volcano and ZCopy.Trademarks and registered trademarks of other companies: AIX, DB2, MQSeries and WebSphere are registered trademarks of International Business Machines Corporation. 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 are trademarks or registered trademarks of their respective companies.

Copyright © September 2001, 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 Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . 17Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Application Trace Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22New OMEGAMON II Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Documentation Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25User Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Navigating Among OMEGAMON II’s User Interfaces. . . . . . . . . . . . . 28Enhanced Signon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Exiting OMEGAMON II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32The Hows and Whys of Managing IMS Performance. . . . . . . . . . . . . 33Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Using OMEGAMON II’s Graphical CUA Interface

Chapter 2. Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Learning About Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Navigating from Panel to Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Using the View and Options Pull-downs . . . . . . . . . . . . . . . . . . . . . . 48Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Advanced Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Contents

Contents


Chapter 3. Navigating Between OMEGAMON II Sessions . . . . . . . . . . . . . 53Using Session Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Using Transplex Navigation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Using Transplex Navigation with OMEGAMON II for CICS. . . . . . . . 57Using Transplex Navigation with OMEGAMON II for DB2 . . . . . . . . 60Using Transplex Navigation with OMEGAMON II for IMS . . . . . . . . . 63Using Transplex Navigation with OMEGAMON II for DBCTL . . . . . . 64Using IMS Direct Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 4. Monitoring System Performance. . . . . . . . . . . . . . . . . . . . . . . . 67The System Overview Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Investigating Tripped Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Getting Help for a Tripped Exception . . . . . . . . . . . . . . . . . . . . . . . . 74Accessing Bottleneck Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Chapter 5. Issuing IMS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Using the Operator Assist Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Using the System Console Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Using the Action Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Chapter 6. Customizing Your OMEGAMON II Profiles . . . . . . . . . . . . . . . 81Your Logon Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Your User Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Chapter 7. Maintaining Your OMEGAMON II Profiles . . . . . . . . . . . . . . . . 97Accessing Profile Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Using the Dynamic Profile Update Facility. . . . . . . . . . . . . . . . . . . . . 99

Using OMEGAMON II’s Menu and Command Interfaces

Chapter 8. Using the OMEGAMON II Menu Interface . . . . . . . . . . . . . . . 103Beginning OMEGAMON II Operation . . . . . . . . . . . . . . . . . . . . . . . 104Ease-of-Use Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Stopping OMEGAMON II’s Menu Interface . . . . . . . . . . . . . . . . . . . 114

Contents 5

Contents

Chapter 9. Command Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Accessing the Command Interface. . . . . . . . . . . . . . . . . . . . . . . . . . 116Commands and Screen Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Panel Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Entering Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Command Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Screen Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Screen Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Chapter 10. Screen Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Invoking Screen Spaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Creating or Modifying Screen Spaces . . . . . . . . . . . . . . . . . . . . . . . 139Listing Screen Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Renaming a Screen Space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Deleting a Screen Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Invoking Screen Spaces Automatically . . . . . . . . . . . . . . . . . . . . . . 144

Chapter 11. Advanced Commands and Features . . . . . . . . . . . . . . . . . . . . 147Rate and Difference Command Arguments . . . . . . . . . . . . . . . . . . . 148Setting and Using Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149The Zooming Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Secondary Console Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Problem-Solving Scenarios

Chapter 12. Resolving a Response Time Problem . . . . . . . . . . . . . . . . . . . 157Background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Creating a PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Activating the Bottleneck Analysis Collector . . . . . . . . . . . . . . . . . . 163Displaying Bottleneck Summary Information for PSB Groups . . . . . 165Viewing Bottleneck Analysis Details for a Specific PSB Group. . . . . 167Identifying DASD Problems with a Database . . . . . . . . . . . . . . . . . . 169

Contents


Chapter 13. Analyzing Program Isolation Pool Use . . . . . . . . . . . . . . . . . . 173Background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Viewing PI Enqueue Pool Statistics . . . . . . . . . . . . . . . . . . . . . . . . . 176Restarting a PSB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Detecting a PI Enqueue Pool Lockout . . . . . . . . . . . . . . . . . . . . . . . 181

Chapter 14. Analyzing DBCTL Thread Activity . . . . . . . . . . . . . . . . . . . . . 183Background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Investigating the Tripped Exception. . . . . . . . . . . . . . . . . . . . . . . . . 186Viewing Details for a Specific Thread . . . . . . . . . . . . . . . . . . . . . . . 188Stopping a Thread . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190Viewing Details for PI or IRLM Locks . . . . . . . . . . . . . . . . . . . . . . . 192Viewing Details for DL/I Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Trapping Long-Running Threads . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Chapter 15. Managing Groups of IMS Resources. . . . . . . . . . . . . . . . . . . . 197Background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Rules for Creating Resource Groups . . . . . . . . . . . . . . . . . . . . . . . . 200Selecting a PSB Group Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Creating a New PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Copying a PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Deleting a PSB from a PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . 211Stopping a PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212Starting a PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Appendixes

Appendix A. Operating OMEGAMON II from the Menu/Command Interface . . . 217Logging On to the Menu/Command Interface Directly. . . . . . . . . . . 218Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Specifying a User Profile in ISPF, VTAM, or TSO Mode . . . . . . . . . 221Working with Exceptions in VTAM, ISPF, TSO, or Dedicated Mode 222

Contents 7

Contents

Appendix B. Exceptions Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233OMEGAMON II for DBCTL Exceptions. . . . . . . . . . . . . . . . . . . . . . 234

Appendix C. Fast Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249Using Fast Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Appendix D. Guide to Candle Customer Support . . . . . . . . . . . . . . . . . . . . 253Base Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254Enhanced Support Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258Customer Support Contact Information. . . . . . . . . . . . . . . . . . . . . . 260

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Contents


List of Figures 9

FIGURE 1. Reconnection Confirmation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29FIGURE 2. Modify Default Logon Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30FIGURE 3. IMS Monitor Selection Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30FIGURE 4. Panel Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40FIGURE 5. Pull-down Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41FIGURE 6. Pop-up Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42FIGURE 7. Pushbutton on Thread Details Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47FIGURE 8. View Pull-down for PSB Operations Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48FIGURE 9. System Overview Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

FIGURE 10. Regions Status Indicator - Critical Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71FIGURE 11. A Tripped Exception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72FIGURE 12. Regions Summary Panel (Primary) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73FIGURE 13. Select IMS Command Entry Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80FIGURE 14. IMS Command Entry Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80FIGURE 15. Exception Groups Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88FIGURE 16. Threads—High Exceptions Thresholds Pop-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89FIGURE 17. Profile Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91FIGURE 18. Create, Delete, and Save Profiles Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92FIGURE 19. List User Profiles Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92FIGURE 20. Describe a User Profile Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93FIGURE 21. Set Startup Configuration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94FIGURE 22. OMEGAMON Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105FIGURE 23. The INFO-line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106FIGURE 24. Monitor Menu with IMS STATUS Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107FIGURE 25. Monitor Menu with IMS CPU Use and I/O Plots Display . . . . . . . . . . . . . . . . . . . . . . .108FIGURE 26. Exceptions Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109FIGURE 27. Systemwide Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109FIGURE 28. Systemwide Exceptions Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110FIGURE 29. General Help Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110FIGURE 30. Part of the OMEGAMON II Menu Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111FIGURE 31. Regions Menu with All Regions Option Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . .112FIGURE 32. Detailed Information about a Region. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112FIGURE 33. Panel Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118FIGURE 34. INFO-line Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119FIGURE 35. VTAM User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120FIGURE 36. OMEGAMON II Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120FIGURE 37. Four Types of OMEGAMON II Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121FIGURE 38. OMEGAMON II Command Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122FIGURE 39. One-line Help Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124FIGURE 40. Extended Help Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125

List of Figures


FIGURE 41. Minor Command Help Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125FIGURE 42. INFO-Line Command Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126FIGURE 43. Commands that List OMEGAMON II Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . .127FIGURE 44. Using the DCL Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129FIGURE 45. Result of the DCL Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129FIGURE 46. .PFK Definitions in Command Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131FIGURE 47. Session Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134FIGURE 48. Typical User-Created Screen Space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140FIGURE 49. Screen Space List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141FIGURE 50. Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160FIGURE 51. List of PSB Groups - Before Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161FIGURE 52. Created PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161FIGURE 53. List of PSB Groups - After Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161FIGURE 54. Inactive Bottleneck Status Light. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163FIGURE 55. Bottleneck Analysis Options Pop-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164FIGURE 56. Bottlenecks Summary Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165FIGURE 57. Bottlenecks Summary Panel - High percentages . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166FIGURE 58. Bottleneck Analysis Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167FIGURE 59. Database Summary Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169FIGURE 60. Device Statistics Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170FIGURE 61. OSAM Database Details Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171FIGURE 62. System Overview Panel with a Tripped Exception. . . . . . . . . . . . . . . . . . . . . . . . . . . .175FIGURE 63. A Tripped APIE Exception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176FIGURE 64. First Pools Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177FIGURE 65. Second Pools Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177FIGURE 66. Details for PSBs Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179FIGURE 67. PSB Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180FIGURE 68. Database Access Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181FIGURE 69. Data Filters Pop-up - Enter a PSB Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182FIGURE 70. PSB Operations - Matches Specified Pattern Displays . . . . . . . . . . . . . . . . . . . . . . . . .182FIGURE 71. Tripped Exceptions Pop-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186FIGURE 72. Threads Summary Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187FIGURE 73. Thread Details Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188FIGURE 74. Region Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190FIGURE 75. Stop Options Pop-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191FIGURE 76. Thread Locks Details Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192FIGURE 77. Thread DL/I Calls Details Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193FIGURE 78. Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194FIGURE 79. TTIM Add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194FIGURE 80. TTIM List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195FIGURE 81. XIMS Immediate Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195FIGURE 82. TPSB Exception Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196FIGURE 83. System Overview Panel - Select Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201FIGURE 84. PSB Operations Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202FIGURE 85. PSB Groups Available Pop-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202

List of Figures 11

FIGURE 86. PSB Operations - Resources for PAYROLL Group . . . . . . . . . . . . . . . . . . . . . . . . . . .203FIGURE 87. Create Group Pop-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204FIGURE 88. Add Resources to Group Pop-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205FIGURE 89. List of PSBs Matching Data Filter Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206FIGURE 90. PSB Operations for PAYSTOP Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206FIGURE 91. Copy Group Pop-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208FIGURE 92. Create Group Confirmation Pop-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209FIGURE 93. Copy Resources Pop-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209FIGURE 94. PSB Operations for PAYSTOP Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210FIGURE 95. Delete Resources Pop-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211FIGURE 96. PSB Operations for PAYSTOP Group - Changed Status to Stop . . . . . . . . . . . . . . . . .212FIGURE 97. PSB Operations for PAYSTOP Group - Status Schedulable . . . . . . . . . . . . . . . . . . . .213FIGURE 98. Systemwide Exceptions Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222FIGURE 99. Set All Clear Message Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224

FIGURE 100. History of All Tripped Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225FIGURE 101. Display of Pre-Defined IMS/MTO Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231


Preface 13

Preface

IntroductionThe OMEGAMON II for DBCTL User’s Guide explains how OMEGAMON II for DBCTL monitors IMS systems. Several scenarios are presented and discussed to demonstrate how OMEGAMON II for DBCTL can improve system performance.

P

About this document


About this document

Who should use this guideThis manual is for:

n operators and data center personnel who are responsible for monitoring IMS

n systems programmers and performance analysts who are responsible for tuning IMS

n application programmers who wish to monitor their programs

n database administrators

n data center managers

This guide teaches you the basics of using OMEGAMON II® for DBCTL (hereafter referred to as OMEGAMON II) to manage your realtime IMS environment. It focuses on two topics:

OMEGAMON II’s graphical CUA™ interface, also known as the primary user interface. This interface lets you monitor IMS with ease and issue IMS commands without having to remember command names or syntax.

OMEGAMON II’s menu and command interfaces. These user interfaces provide in-depth performance information and tools through a comprehensive menu system and a set of powerful commands.

This guide also provides some common scenarios that demonstrate how to use OMEGAMON II to investigate, analyze, and solve system performance problems.

Documentation set informationThis guide does not include information about the historical (EPILOG) component of OMEGAMON II. This guide does include limited information about the bottleneck analysis (DEXAN) component of OMEGAMON II. For information about these product components, see the OMEGAMON II for DBCTL Bottleneck Analysis (DEXAN) Reference Manual and the OMEGAMON II for DBCTL Historical Component (EPILOG) User’s Guide.

The documentation listed in the following table is available for OMEGAMON II for DBCTL.Where to look for more information

Table 1. OMEGAMON II for DBCTL Documentation Set

Document Number Document Name Description

IC51-6057 Installing Candle Product on MVS

Provides installation instructions and other installation considerations.

Preface 15

About this document

For more information related to this product and other related products, please see the

n technical documentation CD-ROM that came with your product

ID53-6341 OMEGAMON II for DBCTL Realtime Commands Reference Manual

Describes in detail all of the features of the OMEGAMON II for DBCTL command interface.

ID53-6344 OMEGAMON II for DBCTL Bottleneck Analysis (DEXAN) Reference Manual

Provides reference information and descriptions of the features of the bottleneck analysis component.

ID53-6345 OMEGAMON II for DBCTL Historical Component (EPILOG) Reference Manual

Provides a comprehensive description of the features of the historical component (EPILOG).

ID53-6346 OMEGAMON II for DBCTL Historical Component (EPILOG) User’s Guide

Teaches you, step-by-step, how to operate the historical component (EPILOG) reporter after installation.

ID54-6340 OMEGAMON II for DBCTL User’s Guide

Teaches you, step-by-step, how to operate OMEGAMON II for DBCTL after installation.

I251-6317 OMEGAMON II for IMS/DBCTL Configuration and Customization Guide

Explains how to configure and customize OMEGAMON II and its user interfaces and components.

I299-6303 Application Trace Facility for OMEGAMON II for IMS and DBCTL

Provides user and reference information about the features of the Application Trace Facility (ATF) component.

I299-6338 Transaction Reporting Facility for OMEGAMON II for IMS and DBCTL

Provides user and reference information about the features of the Transaction Reporting Facility (TRF) component.

I299-6339 IMS Console Facility for OMEGAMON II for IMS and DBCTL

Provides a comprehensive description of the features of the IMS Console Facility (ICF) component.

W052-6238

W052-6239

W052-6240

Candle Product Messages Manual

Volumes 1, 2 and 3

Provides reference summary information for all Candle product messages.

Table 1. OMEGAMON II for DBCTL Documentation Set

Document Number Document Name Description

About this document


n technical documentation information available on the Candle Web site at www.candle.com

n online help provided with this and the other related products.

Ordering additional product documentationTo order additional product manuals, contact your Candle Support Services representative.

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 communication with Candle’s Information Development department. You can also send email to [email protected]. Please include the product name, version, and book title in the subject line.

Preface 17

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 forn Alln Current pagen 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:n 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.)

n 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.)

n 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.

n 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.

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.

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 19


SymbolsThe following symbols may appear in command syntax:

Table 2. 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.



What’s New 21

What’s New

Chapter overviewVersion 510 of OMEGAMON II for IMS and OMEGAMON II for DBCTL significantly enhanced the Application Trace Facility. This version also provides several new functions, which broaden the overall functionality of OMEGAMON II for IMS and OMEGAMON II for DBCTL.

Chapter contentsApplication Trace Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22New OMEGAMON II Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Documentation Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

W

Application Trace Facility


Application Trace FacilityApplication Trace Facility (ATF) is a monitoring agent in OMEGAMON II for IMS and OMEGAMON II for DBCTL. In Version 510, ATF was significantly enhanced so that:

n Multiple ATF OMEGAMON Classic address space sessions can monitor the same IMS

n The IMS Monitor can run concurrently with these ATF sessions

n All environments for IMS, IMS DB/DC, IMS DC and IMS DBCTL are supported

n A site has external control of its operations

n IMS Version 7 DC Monitor is supported

n Concurrent Online TRF display and ATF display functions are supported

In the previous Version 500, ATF had a DETAIL parameter that could be set to LOW or HIGH. In Version 510, this parameter was removed and the function was separated to display this information on separate sets of panels:

n What used to be DETAIL=LOW in ATF V500 is now the Online TRF Display

n What used to be DETAIL=HIGH in ATF V500 is now new ATF panels

The changes made to ATF in this release are explained in detail in the Application Trace Facility Manual for OMEGAMON II for IMS and DBCTL 510. ATF’s online help has been upgraded to reflect these new features.

What’s New 23

New OMEGAMON II Functions

New OMEGAMON II FunctionsSeveral new functions were added to OMEGAMON II for IMS and OMEGAMON II for DBCTL. These functions are:

n Expanded generic IMS command support

n Enhanced VSAM buffer pool statistics

n Enhanced fast path buffer pool statistics

n Enhanced fast path statistics

n Enhanced operator assistance for fast path areas

n Additional data and sorting on IMS Message region fields

Documentation Changes


Documentation Changes

Online documentationWith version 510, Candle Corporation has moved OMEGAMON II for IMS 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 II for IMS manuals. However, the manuals remain available online in the Adobe PDF version on CD-ROM and are also available on the Candle Corporation website at www. Candle.com.

The documentation CD being provided with this release has robust and easy-to-use search capabilities. You can search for information in multiple volumes, multiple versions, and across products. The CD also provides easy setup of search indexes with a single click of the mouse.

If you want to order printed copies of the documentation, please contact your Candle Support Services representative.

Introduction 25

Introduction

Chapter overviewThis chapter introduces you to OMEGAMON II, summarizing the user interfaces, components, and features of OMEGAMON II. It also explains approaches to tuning IMS.

Chapter contentsUser Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Navigating Among OMEGAMON II’s User Interfaces . . . . . . . . . . . . . . . . 28Enhanced Signon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Exiting OMEGAMON II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32The Hows and Whys of Managing IMS Performance . . . . . . . . . . . . . . . . 33Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

1

User Interfaces


User Interfaces

IntroductionOMEGAMON II has the following user interfaces:

n CUA Interface

OMEGAMON II’s primary user interface, the CUA, is a graphical interface that follows the guidelines of the IBM® SAA®/CUA (Systems Application Architecture®/ Common User Access™) model for consistent graphical user interfaces across products.

Features of the CUA interface include:

– Simplicity, ease-of-use and consistency with other products, allowing a new user to begin using the product immediately.

– Status light indicators alerting you to critical problems.

– Pull-down menus and pushbuttons that let you navigate easily throughout the product to access all the key IMS realtime status information.

– The operator assist feature makes it easy to use IMS commands without having to remember command names or syntax.

– Availability of help information for every display panel. Each help panel describes the information that you see on the display panel and also explains how to use this information to tune your IMS system.

– Ability to zoom to OMEGAMON II’s menu and command interfaces for more detailed information.

Part I of this guide focuses on the use of the CUA.

n Menu and Command Interfaces

For users requiring comprehensive details about the system, OMEGAMON II has two other user interfaces to the product’s realtime IMS information.

– The menu interface lets the user access realtime data via an easy-to-use menu system. Each menu option leads to a panel displaying appropriate OMEGAMON II commands and output.

– The command interface lets the user enter a set of extensive and very flexible commands in any order or combination covering almost every aspect of the IMS environment in real time.

Introduction 27

User Interfaces

Part II of this guide focuses on the use of the menu and command user interfaces.

n Historical Information Interfaces

For historical information from OMEGAMON II’s historical component (EPILOG), users request printed reports via a batch report generator, or make interactive queries through a series of TSO panels.

For information about these interfaces, see the OMEGAMON II for DBCTL Historical Component (EPILOG) User’s Guide.

Navigating Among OMEGAMON II’s User Interfaces


Navigating Among OMEGAMON II’s User Interfaces

IntroductionFollow these guidelines for navigating among OMEGAMON II’s user interfaces:

Note: This assumes you have logged on through the OMEGAMON II CUA interface.

From this interface:

You can access this interface:

By doing this:

CUA menu/command Select Cmd/Menu Interface (OMEGAMON) from the GoTo pull-down.

menu/command CUA (System Overview panel)

Press PA2.

menu command Press PF12.

command menu Press PF12.

Introduction 29

Enhanced Signon

Enhanced Signon

IntroductionWe have enhanced the OMEGAMON II signon with IMS monitor selection from a pop-up panel.

Signing on to OMEGAMON IITo sign on to OMEGAMON II:

1. At the Welcome panel, type your Applid and press Enter.

2. The next panel you see is the Candle logo panel. Press Enter.

3. The Signon panel appears. Enter your USERID and PASSWORD and press Enter.

4. The Reconnection Confirmation panel appears.

FIGURE 1. Reconnection Confirmation

To modify your logon parameters, select Modify Default Logon Parameters. Move your cursor to selection number 2 or type 2 in the input field. Press Enter.

5. The Modify Default Logon Parameters panel displays, as shown in the following figure.

Reconnection Confirmation Select one of the following, then press Enter. 1. Reconnect with Current Parameters 2. Modify Current Logon Parameters F12=Cancel

Enhanced Signon


FIGURE 2. Modify Default Logon Parameters

6. To change the Applid you are currently using, position your cursor on the Application ID field. Press F4 and a pop-up panel displays, as shown in the following figure.

FIGURE 3. IMS Monitor Selection Panel

7. This panel lists the Applids for the OMEGAMON II Realtime Performance Monitor for each IMS system. You can scroll through the list to locate the Applid you need. Press Enter and you return to the Modify Default Logon Parameters panel.

Modify Default Logon Parameters Change your logon parameters, or press ENTER to accept the default values Application ID . . . . . . . R11OIS11 + User Profile . . . . . . . . /C Logical Rows . . . . . . . . 999 99-9999 Refresh Interval . . . . . . 30 Seconds Note: User Profile must be a 2 character suffix where your OMEGAMON defaults will be saved. Enter F4=Prompt F12=Cancel

IMS Session Monitor Selection Lines 1 to 6 of 7 Move cursor to selection, then press Enter. IMS ID SESSION NAME APPL ID -------- ------------------------------ -------- I51A IMSFREDA DBDC SP11 R11OIS03 I51A IMSFREDA DB/DC SP11 R11OIS11 I51C IMSFREDA DBCTL SP22 R22OIS11 I51N IMSFREDA DBDC SP13 R13OIS03 I51N IMSFREDA DBDC SP13 R13OIS11 I51C IMSFREDA DBCTL SP12 R12OIS03 F1=Help **=Bkwd F8=Fwd F12=Cancel

Introduction 31

Exiting OMEGAMON II

Exiting OMEGAMON II

Steps

You can exit OMEGAMON II from this interface:

By doing one of the following:

Note: If you logged on to OMEGAMON II through OMEGAVIEW, exiting OMEGAMON II returns you to OMEGAVIEW.

CUA Press F3, and confirm.

menu/command n Press PF3, and confirm.n Enter X.X on the INFO-line.n Enter /STOP on the INFO-line.n Enter STOP on the INFO-line.

Components


Components

IntroductionSeveral components comprise the OMEGAMON II product package:

n Realtime Performance Component (OMEGAMON®)

The realtime performance component (OMEGAMON):

– Provides basic realtime data about the IMS environment.

– Provides automatic alerts when system problems occur or service levels are not being met, using exception analysis–one of the most unique features of OMEGAMON.

– Lets you request system, device, thread, IMS resource, and IMS/DB2® attach information.

– Lets you automatically log IMS messages and system data.

– Lets you enter powerful, authorized commands to manage IMS.

This guide provides information about this product component.

n Bottleneck Analysis Component (DEXAN)

The bottleneck analysis component (DEXAN) helps a system tuner perform bottleneck or degradation analysis, an analysis technique that focuses on workloads rather than resources. DEXAN breaks down IMS workloads into times spent in various executing states: CPU usage, database I/O waits, MVS waits, and IMS waits.

This guide includes information about accessing DEXAN bottleneck analysis information through the CUA, but not through the menu and command interfaces. For information about DEXAN menus and commands, see the OMEGAMON II for DBCTL Bottleneck Analysis (DEXAN) Reference Manual.

n Historical Component (EPILOG)

The historical component (EPILOG) provides historical information about the IMS environment. EPILOG collects, analyzes, and reports on resource information and bottlenecks for substantial periods of time, such as hours or days.

For information about EPILOG, see the OMEGAMON II for DBCTL Historical Component (EPILOG) User’s Guide.

n Companion Products

OMEGAMON II also works with Candle’s OMEGAVIEW® and the other OMEGAMON family of products, to give you comprehensive information–both from a high level status and low level detail perspective–about all aspects of your system.

Introduction 33

The Hows and Whys of Managing IMS Performance


IntroductionOMEGAMON II provides tools to enable you to manage your IMS system resources effectively, and to allow the help desk staff to identify and resolve problems, often before they affect the end user.

n Performance indicators alert you to impending problems and allow you to quickly navigate to detail panels.

n The Operator Assist function provides you with an easy way to display regions, databases, programs, and so on, and to take action to make them available.

For example, you can request a view of only those databases that are unavailable. Then, if you see a stopped database, you can move your cursor next to the database name and type the action code to start the database. OMEGAMON II creates the appropriate IMS command and passes it to IMS for execution.

Managing IMS performance includes balancing workloads and resources, and monitoring the effects of these balancing decisions. You monitor IMS to determine if databases, programs, and threads are processing at an acceptable rate. Even though IMS is a complex environment, something as simple as a stopped database can delay the completion of programs and database calls from CICS™ threads. The end user typically first feels the effects of resource contention or unavailable resources and informs the help desk personnel.

Managing your system is an iterative process consisting of the following steps that comprise a logical tuning approach:

1. Monitor your system’s actual performance.

2. Identify the cause when a workload or key system resource shows a problem.

3. Correct problems that arise.

4. Use the data from your observations and your knowledge of data center priorities to arrive at performance targets.

5. Continue monitoring your system.OMEGAMON II helps you carry out each of these steps.

Monitor performanceYour site might not have formal, written performance objectives, but almost all sites have informal objectives. OMEGAMON II can help you translate informal objectives into formal objectives, and can also help you see whether performance on your system is the way it should be. Once OMEGAMON II is up and running, you can start monitoring current IMS performance by asking yourself the following questions:



1. How are my IMS resources performing?

2. Are the problems that OMEGAMON II points up really problems for my site?

3. Is OMEGAMON II missing any problems for my site?OMEGAMON II’s graphical displays show you what is currently happening in your system and also alerts you to potential or definite problems for your resources. OMEGAMON II does this with status indicators, which are colored bars of light. For more information on status indicators see “Status indicators” on page 68.

OMEGAMON II uses a set of criteria called exceptions to determine whether to turn a status indicator yellow or red. Candle ships OMEGAMON II with a set of default exception values, but these defaults might not be right for you and your site. Adjusting the default exception values is easy; for more information on this, refer to “Customizing Your OMEGAMON II Profiles” on page 81.

Identify and correct problemsWhen one of the status indicators signals that a problem exists, OMEGAMON II can help you identify the cause of the problem.

For example, OMEGAMON II can tell you what may be causing poor performance for a particular program, and help you identify which resources or system components are busiest or unusually active when there is a response time delay for a particular program. You can use this information to correct the problem. If you need to issue an IMS command to correct the problem, you can navigate to panels where you can select IMS commands from a menu or issue IMS commands directly.

OMEGAMON II’s online help system also provides advice for resolving problems.

Introduction 35

Modes of Operation

Modes of Operation

IntroductionYou access OMEGAMON II’s primary CUA using VTAM®. From here, you can also zoom to the menu and command interfaces.

If you choose to log on to the menu and command interfaces directly, you can do so with several different modes of operation. These include dedicated, VTAM, TSO, and ISPF modes. For information about these modes, see “Modes of Operation” on page 219.

Modes of Operation


37

Part I: Using OMEGAMON II’s Graphical CUA Interface

Part I provides information about how to use OMEGAMON II with its primary user interface, the graphical CUA™ interface. In this section, references to OMEGAMON II signify the OMEGAMON II CUA interface, unless the text specifically indicates otherwise.


Getting Started 39

Getting Started

Chapter overviewThis chapter describes how to use OMEGAMON II’s CUA user interface and includes information about panel appearance, navigation methods, online help, and customization options.

Chapter contentsLearning About Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Navigating from Panel to Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Using the View and Options Pull-downs . . . . . . . . . . . . . . . . . . . . . . . . . . 48Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Advanced Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

2

Learning About Panels



IntroductionThe following sections illustrate the basic display elements of panels in the CUA interface.

Panel formatThe following figure shows the format of CUA interface panels.

FIGURE 4. Panel Format

Each panel consists of four areas:

1 Action bar. Every panel has an action bar on the top line. The action bar contains keyword choices that lead to pull-down menus when selected.

“Using the action bar” on page 45 explains how to use the action bar.

2 Panel body. OMEGAMON II displays its data here. The format of the data varies depending on its type. The panel body may contain status indicators, data lists, or graphic representations. The panel ID displays in the upper left corner of the panel body if the parameter to display the panel ID is turned ON. The IMS system ID displays in the upper right corner.

An input field (_) precedes some fields in the panel body, to indicate that you can select this field as an object. You can use the input field to select an action for that object. Positioning the cursor on the input field and pressing Enter is equivalent to selecting the Show details action for that object.

“Using the action bar” on page 45 explains more about actions.

____ Actions GoTo View Options Help 1-------------------------------------------------------------------------------

2

-------------------------------------------------------------------------------

<Threads Details> (Threads Summary) 3F1=Help F2=Keys F3=Exit F5=Refresh F6=Console F10=Action Bar 4

Getting Started 41


Pull-down menusWhen you select a keyword choice from the action bar, OMEGAMON II displays a pull-down menu. A pull-down menu provides a list of further selections that you can make. The figure below shows the pull-down menu that displays after you select Actions.

FIGURE 5. Pull-down Menu

Although part of the underlying panel is still visible, its selections and entry fields are unavailable. To cancel a pull-down menu, press F12.

Pop-up windowsPop-up windows (such as the one in Figure 6 on page 42) are small panels that are superimposed over the base panel. Pull-down menu choices that are followed by an ellipsis (...) result in pop-up windows. Pop-ups may prompt for

3 Pushbutton area. OMEGAMON II displays the pushbuttons that are applicable to the current panel here. Pushbuttons that are applicable to the current panel display between < >. The pushbutton displaying between ( ) indicates the current panel.

“Using pushbuttons” on page 46 explains more about pushbuttons.

4 Function key area. OMEGAMON II displays the function keys that are applicable to the current panel here. Function keys that are not applicable to the current panel information appear with asterisks instead of the function key number (for example, **=Bkwd rather than F7=Bkwd).

“Using function keys on panels, pop-ups, and pull-downs” on page 43 lists all of OMEGAMON II’s CUA interface function keys.

a___ Actions GoTo Options Help----+----------------------------------------+-------------- 01/02/97 12:00:00 | 1. Show details for an item | IMS: I51c____+ | 2. IMS Command Entry | | |+---| 3. Exit Omegamon II F3 |--------------------------------+| | | Alerts || | F1=Help F12=Cancel |--------------------------------++---+----------------------------------------+ ||_ Regions +++++ _ XRF ##### |_ Pools ----- _ Conflicts ----- || | ||_ IMS Status ----- _ ESS ===== |_ Threads ----- _ Databases ----- || | ||_ Bottleneck ----- _ Traces ##### |_ Logging ===== _ Fast Path ----- || | ||_ Buf. Pools ----- |_ Programs ===== || | ||_ I/O ----- |_ |+-----------------------------------------------------------------------------+| Operator Assist |+-----------------------------------------------------------------------------+|_ Databases _ Regions _ Programs _ Logging |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console F10=Action Bar



further selections, provide alerts for possible error conditions, or display help or security information. More than one pop-up window can be visible at a time, and the windows can overlap each other. To cancel a pop-up, press F12.

The following figure shows the pop-up that displays if you request the Show details action for Regions when an exception condition exists.

FIGURE 6. Pop-up Window

Color and highlightingText representing a selection item appears in white or blue on color terminals. White items are available for selection; blue items are not. Underlined or highlighted fields accept input. Asterisks display in those fields for which no data is currently available.

Moving the cursorThese keys move the cursor among selection fields on a panel:

Tab Moves the cursor from a selectable field to the next selectable field to the right.

Back Tab Moves the cursor from a selectable field to the next selectable field to the left.

Return Moves the cursor to the first selectable field on the next line.

___ Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 System Overview IMS: IMS: I51c____+ Select a component with “S” to show details +----------------------------------------------------------------------------+ | Status | Alerts | |-----------------------------------+----------------------------------------+ |_ Regions ##### _ XRF ----- | _ Pools ----- _ Conflicts ----- | | | |_ IMS Status ----- _ ESS ----- | _ Threads ----- _ Databases ----- | +----------------------------------------------------------------------------+ | Regions Tripped Exceptions | | | | | | Move cursor to selection, then press Enter. | | | | Exception Description | | | | RGNW Region waiting time is greater than 1 minute. | | | | | | | | | | | | F1=Help F12=Cancel | +----------------------------------------------------------------------------+

Getting Started 43


ScrollingMany panels include tables of data. You can scroll through this data either by using F8 (to scroll forward) and F7 (to scroll backward), or you can overtype the values shown in the Lines _1 to mm of nnn field.

Some panels have more columns than display on the current panel. You can scroll through this data using F20 (to scroll right) and F19 (to scroll left).

Some pop-up windows indicate scrolling with the word More, which displays near the upper right corner of the window. Next to the word is either a +, -, <, or >.

If + displays, press F8 to scroll forward to the next window. If - displays, press F7 to scroll backward to the previous window. If both + and - display, you can scroll in either direction.

If > displays, press F20 to scroll right to the next window. If < displays, press F19 to scroll left to the previous window. If both > and < display, you can scroll in either direction.

In the System Console display panel, you can scroll to the top or bottom of the console log by typing an M on the command line and pressing F7 for top or F8 for bottom. You can search for a string of characters in the console log by using variations of F ‘ccccc’on the command line, where ccccc is the character string. The following table describes these variations:

Using function keys on panels, pop-ups, and pull-downsMany of the tasks you perform in OMEGAMON II use function keys. These keys are the Fn or PFn keys, depending on your terminal. This manual uses the Fn designation for function keys in the CUA interface, and PFn for function keys in the menu and command interfaces. Each panel lists the available function keys and their assignments.

Home Moves the cursor to the action bar entry area from anywhere on the panel.

F10 When the cursor is in the panel body, F10 moves the cursor to the action bar. When the cursor is in the action bar, F10 moves the cursor to the first selectable field in the panel body, or to the input field where you were when you pressed F10 the first time.

Type on the command line . . . To search for the . . .

F ‘ccccc’ string following the current log position.

F ‘ccccc’ PREV string above the current log position.

F ‘ccccc’ NEXT string after the current log position.

F ‘ccccc’ LAST last string in the console log.



Not all function key selections are available for every panel. Only key selections relevant to the current panel display. For example, panels with data that continues over several panels have the backward and forward function keys (F7 and F8, respectively) available and display these at the bottom of the panel. Panels that contain just one panel’s worth of data do not display F7 and F8.

These are the function key assignments:

F1 Help. Displays a help window for the current panel.

F2 Keys. Toggles display of the function key assignments at the bottom of the panel. If the function key assignments currently display and you press F2, they disappear. If you press F2 again, the assignments reappear.

F3 Exit. Exits the current panel, saving all changes and additions made in any of the fields.

F4 Prompt. Displays a list of valid selections for an input field. If there are only two valid selections, F4 toggles between the two.

F5 Refresh. Clears the panel and updates it with new data.

F6 Console. Pressing this key takes you directly to the System Console panel.

F7 Backward. Scrolls backward if more lines exist than can display on the current panel. If you are on the first panel, two asterisks display instead of the function key name.

F8 Forward. Scrolls forward if more lines exist than can display on the current panel. If you are on the last panel, two asterisks display instead of the function key name.

F9 Retrieve. Retrieves the last command from the operator’s console.

F10 Action bar. Moves the cursor back and forth between the action bar at the top of the panel and the panel body.

F12 Cancel. Returns from a pop-up or pull-down to the current panel and erases all changes and additions you made in any of the fields since you last pressed Enter.

F15 System Overview. Returns to the System Overview panel from anywhere in the product.

F19 Left. Scrolls to the left if more columns exist that can display on the current panel.

F20 Right. Scrolls to the right if more columns exist that can display on the current panel.

Enter Refreshes the current panel display and validates entries.

Getting Started 45

Navigating from Panel to Panel


IntroductionOMEGAMON II offers several choices for navigating through panels. The basic style is point-and-shoot. Using point-and-shoot, you can easily move from a high-level status display to the lowest level of detail. All you need to do is move the cursor to the field of interest and press Enter. If you are a beginning or infrequent user, all you need to know is:

n Steps for beginning users.

n Press Enter for more details.

n Press F3 to return to a higher-level panel.

n Press F1 for help.

You can get a lot of information with point-and-shoot navigation. But OMEGAMON II has many powerful features that are just a few more keystrokes away. These include using pushbuttons, and the action bar and its Actions and GoTo pull-down menus.

Using the action barThe action bar is an area at the top of each panel that lists keyword choices. By typing the first letter of a keyword, or by placing the cursor to the left of a keyword and pressing Enter, you open pull-down menus, which let you perform any of the following tasks:

n keyword functions

n act upon selected objects (Actions)

n navigate to other panels (GoTo)

n display a subset of the information you are viewing (View)

n customize the user interface (Options)

n get help (Help)

The Actions pull-downWhen you move the cursor to a field and press Enter, you request the default action, Show details, for the object represented in that field. You would get the same result by entering s (for Show details) in the field, or by selecting the object with a slash (/), pressing Enter, and choosing Show details from the Actions pull-down.

But the Show details action is often only one of several actions available to you, especially for the Operator Assist panel. When a panel from the Operations section displays, you can select an IMS command that is associated with the resource that is displaying on the panel, such as a region or a database.



OMEGAMON II supports many different actions. Examples include the following:

The Actions pull-down lists the actions that are available for a panel.

Note: All Operator Assist panels display action code mnemonics at the top of the panel under the panel name.

An easy way to issue an IMS command is to go through the Actions pull-down. On the pull-down is the selection, IMS Command Entry. When you select IMS Command Entry and press Enter, the system displays a pop-up panel where you can issue the IMS command. See “Using the action bar” on page 45 for more information.

The GoTo pull-downThe GoTo pull-down helps you navigate to related data quickly. Sometimes the data that displays on the current panel indicates a possible problem with another resource. For example, you might be looking at the Database Operations panel and you want to see more information on the databases.

The GoTo pull-down contains the panels you would most often want to access. If you do not see the panel you want, select Index. The index lists all the CUA interface panels, and allows you to select the one you want.

You can also zoom to the menu and command interfaces by using the GoTo pull-down.

Using pushbuttonsOMEGAMON II provides pushbuttons as a way to navigate to panels that are closely related in subject and level of detail to the current panel. OMEGAMON II groups pushbuttons in a way that offers suggestions regarding where you might turn next for information related to the current panel.

Pushbuttons display in brackets < > or parentheses ( ) at the bottom of some panels, directly above the function key descriptions. You can only select those pushbuttons in brackets < >.

Objects Sample Actions

Databases Show details, start, stop, lock, unlock

Region Operations Show details, start, stop, abend, cancel

Getting Started 47


FIGURE 7. Pushbutton on Thread Details Panel

To use a pushbutton, place the cursor on the phrase or word in brackets < >, and press Enter. You can also use < x on the action bar, where x is the underscored character on the pushbutton.

Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 Thread Details for RCICS330 in Region 27 IMS: I51C +------------------------------------------------------------------------------+| RecoveryToken : A875132230213288 | Current: PSB . . . . . . : DFHSAM05 || Status . . . . . . . : Unavail | CICS Trans . . : WD80 || _ Number of DL/I Calls : 2 | Number or DB I/O . . . . : --None-- || _ Locks Held . . . . . : 4 | Elapsed Time for DB I/O : --None-- || Elapsed Wait Time for | Number of Waits for || Pool Space . . . . : --None-- | Test Enqueues . . . . : --None-- || Intent Conflict . : --None-- | Update Enqueues . . . : --None-- || Schedule Process . : .001513 | Exclusive Enqueues . . : --None-- || PI Locking . . . . : --None-- | DEDB Buffers . . . . . : --None-- ||------------------------------------------------------------------------------|| Current DL/I Call || Function : GHU || PCB : DI21PART01 A .. QPARTROOT........02CSR13G104KL || IOA : 02CSR13G104KL KR1J50KS || SSA 04 + : PARTROOT*----------------------------(PARTKEY =2CS |+------------------------------------------------------------------------------+ <GoTo CICS> F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console F10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW

Using the View and Options Pull-downs



IntroductionYou can use the View and Options pull-down menus to control the data that you are viewing and to customize your user interface.

The View pull-downMost panels include tables of data. The View pull-down lets you control your view of the data.

The following figure shows the choices available from the View pull-down on the PSB Operations panel. View Control selections vary from panel to panel.

FIGURE 8. View Pull-down for PSB Operations Panel

Typically, you can show all data, or only problem conditions. You can filter the data in a number of ways. For example, you might want to show only PSBs that are unusable. Or, you might want to show only PSB names that start with DFHS.

The View pull-down is not available on all panels.

The Options pull-downYou can use the Options pull-down to customize OMEGAMON II to meet your needs. The Options pull-down lets you customize exceptions, select default session controls, select interface preferences, set levels of authority for users, perform profile maintenance, and access the Application Trace Facility and Transaction Reporting Facility.

The Customize Exceptions selection lets you define acceptable and unacceptable system performance. For more detailed information about using this selection, see “Customizing your exceptions” on page 86.

v____ Actions GoTo View Options Help ------------------+---------------------+------------------- 01/02/97 12:00:00 | 1. All | ions IMS: I51C_____+ VIEW: Unusable | 2. Some | L=Lock N=Unlock | 3. Unusable | | | ________ + | F1=Help F12=Cancel | Lines 1 to 5 of 5+------------------| |------------------------------------+| PSB +---------------------+ | Type ||----------------------------------------------------+------------------------|| CAND001 | PSB-Stop | Batch || | | || | | || | | || | | |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh **=Bkwd F8=FwdF10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW

Getting Started 49


The Set Controls selection lets you define session defaults, including the use of status bars and the length of time OMEGAMON II will wait for a response to issued commands.

The Set Preferences selection lets you define whether the time displays, the date format, whether mnemonics display on panels, and more.

The Issue OI Queries selection lets you access additional information on switch settings and TRF defaults and status.

The Issue IMS Queries selection lets you access additional information on control region storage analysis, startup parameters and overrides, and lets you locate modules in virtual memory and extended buffer pools information.

The Bottleneck Analysis Options selection lets you start the bottleneck analysis collector, set collector options, and submit commands to control bottleneck analysis.

The Change Startup Profile selection lets you create or change a new startup profile.

The List of Administrators selection lets you see the list of users who have administrator authority.

The User Authorities selection lets you set a level of authority for each user if you are an administrator.

The Profile Maintenance selection lets you copy, delete, export, import or modify the description of a profile.

The Application Trace Facility selection displays the Application Trace Control panel from which you can view Application Trace Facility (ATF) parameters, and add, delete and modify ATF traces.

The Online TRF Trace selection displays the TRF Display Control panel from which you can view Transaction Reporting Facility (TRF) parameters, and add, delete and modify TRF traces.

When you customize your OMEGAMON II session using the Options pull-down, OMEGAMON II saves your settings in one of your profiles. For more information about your profiles, see “Customizing Your OMEGAMON II Profiles” on page 81.

Getting Help


Getting Help

IntroductionOMEGAMON II includes a comprehensive help system. This help system contains a range of information, including a glossary of terms, tuning considerations, and advice on solving problems. The help system connects all this information in a way that makes it easy to access only the information you need.

You can get help using either F1 or the Help pull-down. The system includes the following kinds of help:

n panel-level help

n help index

n glossary of topics and terms

n information about the current release

Panel-level helpEvery panel has its own help. Some pop-ups and pull-downs also have help. Help displays as a pop-up window when you press F1 anywhere on the panel. The panel-level help describes the entire panel, contains a guide to the actions you can take, and also describes the critical fields on the panel that may have the greatest effect on your system’s performance.

Help indexThe help index contains entries for every panel-level help. You can access the help index from the Help pull-down and from every help panel.

GlossaryThe glossary contains a list of topics and terms. The glossary items include definitions, tuning advice, and technical discussions.

AboutThis help panel displays the version number of the product. You can access this help from all CUA panels.

User informationThis panel displays the user ID, Terminal ID, System ID, VTAM Lterm Name and current ACB Name.

Getting Started 51

Getting Help

Check maintenance levelThis pop-up lets you enter the name of the panel for which you want the maintenance level. The next panel contains the number of the last PTF, if any.

Help function keysSome of the function keys have different assignments in help. As on other panels, the currently available function keys display at the bottom of help panels. The following list describes the function keys and their assignments in help.

F1 Help. Displays a help window.

F2 Ex Help. Extended Help.

F3 Exit. Exits the help system.

F5 Glossary. Displays a list of glossary topics and terms. You can select any topic or term and view definitions, tuning advice, or a technical discussion, depending on the topic or term.

F6 Search. Displays on the Glossary pop-up (F5) to permit searches of the glossary for all topics and terms containing the same word.

F7 Backward. Scrolls backward if more lines exist than can display on the current panel. If you are on the first panel, two asterisks display instead of the function key name.

F8 Forward. Scrolls forward if more lines exist than can display on the current panel. If you are on the last panel, two asterisks display instead of the function key name.

F9 Keys. Displays a list of function keys and their descriptions.

F11 Index. Displays the help index, which lists every help topic. You can select any topic for viewing by moving your cursor to the topic of interest and pressing Enter.

F12 Cancel. Cancels the current panel or window, and erases all changes and additions you have made in any of the fields since you last pressed Enter.

Advanced Functions


Advanced Functions

IntroductionAs you become more familiar with OMEGAMON II, you might want to execute functions more quickly. OMEGAMON II provides action codes, mnemonics, and short-cut techniques.

Using action codesEach object on a panel has an associated list of actions. To find out what these actions are, use the Actions pull-down.

OMEGAMON II associates a mnemonic action code with each action listed in the Actions pull-down. If you already know the action you want to take, you can use the action code to execute the action directly. The pull-down indicates the code, either by an underlined letter in the text of the action or by a letter in parentheses after the text.

For example, the mnemonic for Start is R. To execute the action directly, just enter the action code in the input field next to the resource you want to act on.

Note: All Operator Assist panels display the action code mnemonics at the top of the panel under the panel name.

Short-cutsWhen you are selecting from the action bar, you can enter up to four mnemonics at a time to choose a sequence of pull-down menus and submenus.

For example, if you want to view all the objects for a given panel, you could first enter v, View, then a, All. Or you could use the short-cut of entering va directly in the input area of the action bar.

Navigating Between OMEGAMON II Sessions 53

Navigating Between OMEGAMON IISessions

Chapter overviewThis chapter describes how if you are logged on to your current session of OMEGAMON II for DBCTL through OMEGAVIEW, you can move to any other OMEGAMON II session defined to OMEGAVIEW, without returning to OMEGAVIEW.

Chapter contentsUsing Session Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Using Transplex Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Using Transplex Navigation with OMEGAMON II for CICS . . . . . . . . . . . 57Using Transplex Navigation with OMEGAMON II for DB2 . . . . . . . . . . . . 60Using Transplex Navigation with OMEGAMON II for IMS . . . . . . . . . . . . 63Using Transplex Navigation with OMEGAMON II for DBCTL. . . . . . . . . . 64Using IMS Direct Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

3

Using Session Switching


Using Session Switching

IntroductionYou can switch directly among all your OMEGAMON® sessions defined to OMEGAVIEW® without having to return to OMEGAVIEW.

Session switching procedureUse the following procedure to switch sessions.

IF you’re switching to . . .THEN session switching takes you to . . .

a session for the first time during your current OMEGAVIEW session,

your destination session’s System Overview panel.

a session you’ve switched to before during your current OMEGAVIEW session,

the panel in your destination session where you left off previously.

Step Action

1 To switch sessions from any OMEGAMON panel or from the OMEGAVIEW main panel, press PA1. ( PA1 is the default key; you can change the default key by selecting Options from the OMEGAVIEW action bar, and then selecting Keys.)

To switch sessions from the OMEGAVIEW main panel action bar, select Switch and press Enter.

Result: OMEGAVIEW displays the Switch to Session pop-up menu.

2 From the Switch to Session pop-up menu, you can do one of the following:n Type the name of the session you want in the entry field at the top of the

session list and press Enter.n Move the cursor next to the session you want and press Enter.n Use the PF Find key (PF14) when you do not know the exact name of

the session. For example, if you know your session begins with ABC, press PF14 to get the Find Session pop-up. From the Find Session pop-up, type ABC in the Session Name entry field and press Enter.

OMEGAVIEW returns you to the Switch to Session pop-up menu; the session list will now begin with the session that precedes all of the ABC sessions. Select a session with the cursor and press Enter.

Result: OMEGAVIEW switches to the session you have chosen.


Using Transplex Navigation


IntroductionUse Transplex™ navigation to follow a specific transaction from a panel in one OMEGAMON to a panel in another OMEGAMON that contains information corresponding to that transaction. You can observe a processing transaction in CICS™, IMS, DBCTL, or DB2®. You invoke this feature with a context-sensitive pushbutton that provides the mechanism to navigate between OMEGAMON panels.

Transplex navigation screen sampleThe following screen sample shows how the DBCTL Transplex navigation pushbutton (<GoTo DBCTL>) looks on an OMEGAMON II for CICS panel. The subsystem name on the pushbutton changes depending on which product and panel you are navigating from, but the location of the pushbutton is the same for all of the OMEGAMONs.

Usage examplesThe following table shows examples of how you can use Transplex navigation to monitor transactions.

IF you are at... AND... USE Transplex navigation to go to...

an OMEGAMON II for CICS Task File Statistics panel

a transaction is spending too much time in DL1

the corresponding Thread Detail panel in OMEGAMON II for DBCTL for more information.

_____ Actions GoTo Index Options Help ----------------------------------------------------------- 01/02/97 15:30:59 Task Details Region: CICSPROD Fastpath: =WTD Auto(60) +----------------------------------------------------------------------------+ | Task number . . . . . 40 + | Transaction ID . . . .: WD80 | | Facility ID . . . . .: 0A50 | CICS transaction ID .: WD80 | | Facility type . . . .: Term | Originating tran ID .: WD80 | | Task state . . . . . : Suspend | First CICS program ID : WKDL8DIO | | Resource type . . . .: ICWAIT | Current CIC program ID: WKDL8DIO | | Resource name . . . .: 0A50 | | | Userid . . . . . . . : CICSUSER | Storage used above 16M: 704 | | | Storage used below 16M: 2K | | CPU time . . . . . . : 0.000s | | | Elapsed time . . . . : 8:25.124 | Purgeable suspend . .: Yes | | Time of suspend . . : 14:37:27 | Purge status . . . . .: No purge | | Time in suspend . . : 0:00:18 | Suspend timeout due .: None | | Task queue . . . . . : Executbl | Suspend type . . . . .: Suspend | | TQE flag . . . . . . : Active | | +----------------------------------------------------------------------------+ <Details> <Addresses> (Files) <Remote> <Statistics> <Storage> <Timings> <GoTo DBCTL>



an OMEGAMON II for IMS Region Detail panel

a transaction is spending too much time in DB2

the corresponding Thread Detail panel in OMEGAMON II for DB2 for more information.

an OMEGAMON II for DBCTL Thread Details panel

you want to look at the details about a task in the CICS region

the corresponding Task Details panel in OMEGAMON II for CICS for more information.

an OMEGAMON II for CICS Task Remote Information panel

you want to look at information about a remote CICS region

the corresponding Task Remote Information panel in your remote OMEGAMON II for CICS for more information.

IF you are at... AND... USE Transplex navigation to go to...


Using Transplex Navigation with OMEGAMON II for CICS


IntroductionTransplex navigation is available from the following panels:

n The Task Details panel. From this panel, use Transplex navigation to go either to the corresponding OMEGAMON II for DBCTL panel, or a corresponding OMEGAMON II for DB2 panel.

n The Task Remote Information panel. From this panel, use Transplex navigation to go to the corresponding remote OMEGAMON II for CICS panel.

The procedures below describe how to access and use Transplex navigation from these panels.

RequirementFor each target OMEGAMON that you navigate to, the OMEGAVIEW collector session for that OMEGAMON must be active. If an OMEGAMON collector session is not active, OMEGAVIEW displays a message with instructions to contact your System Administrator.

Navigating from the Task Details panel to DBCTLYou can use session switching to reach an OMEGAMON II for CICS session either from OMEGAVIEW or another OMEGAMON; refer to “Using Session Switching” on page 54 for instructions. You can then use the following procedure to access the Task File Statistics panel and use Transplex navigation.

Note: You invoke Transplex navigation with a pushbutton. If there is no transaction activity to monitor, this pushbutton does not display on the panel.

Step Action Result

1 From the Region Status panel, select Tasks and press Enter.

The Tasks panel displays.

2 From the Tasks panel, select a task and press Enter.

The Task Details panel displays.



Navigating from the Task Details panel to DB2You can use session switching to reach an OMEGAMON II for CICS session either from OMEGAVIEW or another OMEGAMON; refer to “Using Session Switching” on page 54 for instructions. You can then use the following procedure to access the Task File Statistics panel and use Transplex navigation.


Navigating from the Task Remote Information panel to remote CICSYou can use session switching to reach an OMEGAMON II for CICS session either from OMEGAVIEW or another OMEGAMON; refer to “Using Session

3 From the Task Details panel, press the GoTo DBCTL pushbutton at the bottom of the screen.

The OMEGAMON II for DBCTL target panel displays.

If you want to return to OMEGAMON II for CICS, press the Return to CICS pushbutton at the bottom of the screen.

Note: If the transaction you are monitoring is no longer active, an informational pop-up message displays.

Step Action Result



2 From the Tasks panel, select a task number and press Enter.


3 From the Task Details panel, press the GoTo DB2 pushbutton at the bottom of the screen.

The OMEGAMON II for DB2 target panel displays.

If you want to return to OMEGAMON II for CICS, press the Return to CICS pushbutton at the bottom of the screen.


Step Action Result



Switching” on page 54 for instructions. You can then use the following procedure to access the Task Remote Information panel and use Transplex navigation.


Step Action Result



2 From the Tasks panel, select a task number and press Enter.


3 From the Task Details panel, press the Remote pushbutton at the bottom of the screen.

The Task Remote Information panel displays.

4 From the Task Remote Information panel, press the GoTo Remote CICS pushbutton at the bottom of the screen.

The remote OMEGAMON II for CICS target panel displays.

If you want to return from the remote OMEGAMON II for CICS, press the Return to CICS pushbutton at the bottom of the screen.


Using Transplex Navigation with OMEGAMON II for DB2



IntroductionTransplex navigation is available from the OMEGAMON II for DB2 Thread Detail panel. From this panel, use Transplex navigation to go either to the corresponding OMEGAMON II for IMS panel, or to a corresponding OMEGAMON II for CICS panel.

The procedures below describe how to access and use Transplex navigation from this panel.


Navigating from the Thread Detail panel to IMSYou can use session switching to reach an OMEGAMON II for DB2 session either from OMEGAVIEW or another OMEGAMON; refer to “Using Session Switching” on page 54 for instructions. You can then use the following procedure to access the Thread Detail panel and use Transplex navigation.


Step Action Result

1 There are two methods you can use to access the Thread Detail panel. Both methods begin at the System Status panel; from this panel, you can select either a connection or a thread activity.n To select a connection, choose

IMS from the Connections group and press Enter. Continue to Step 2.

n To select a thread activity, skip to Step 4 for instructions.

The IMS Connections panel displays.

2 From the IMS Connections panel, select a connection and press Enter.

The IMS Thread Summary panel for that connection displays.



Navigating from the Thread Detail panel to CICSYou can use session switching to reach an OMEGAMON II for DB2 session either from OMEGAVIEW or another OMEGAMON; refer to “Using Session Switching” on page 54 for instructions. You can then use the following procedure to access the Thread Detail panel and use Transplex navigation.

3 From the IMS Thread Summary panel, select a PlanName and press Enter.

Note: Skip to Step 6.

The Thread Detail panel for that PlanName displays.

4 From the System Status panel, select Thread Activity from the Alerts group and press Enter.

The All Threads Connected to DB2 panel displays.

5 From the All Threads Connected to DB2 panel, select a thread and press Enter.

The Thread Detail panel for that thread displays.

6 From the Thread Detail panel, press the GoTo IMS pushbutton at the bottom of the screen.

The OMEGAMON II for IMS target panel displays.

If you want to return to OMEGAMON II for DB2, press the Return to DB2 pushbutton at the bottom of the screen.


Step Action Result




Step Action Result

1 There are two methods you can use to access the Thread Detail panel. Both methods begin at the System Status panel; from this panel, you can select either a connection or a thread activity.n To select a connection, choose

CICS from the Connections group and press Enter. Continue to Step 2.

n To select a thread activity, skip to Step 4 for instructions.

The CICS Connections panel displays.

2 From the CICS Connections panel, select a connection and press Enter.

The CICS Thread Summary panel for that connection displays.

3 From the CICS Thread Summary panel, select a plan name and press Enter.

Note: Skip to Step 6.

The Thread Detail panel for that PlanName displays.

4 From the System Status panel, select Thread Activity from the Alerts group and press Enter.

The All Threads Connected to CICS panel displays.

5 From the All Threads Connected to CICS panel, select a thread and press Enter.

The Thread Detail panel for that thread displays.

6 From the Thread Detail panel, press the GoTo CICS pushbutton at the bottom of the screen.

The OMEGAMON II for CICS target panel displays.

If you want to return to OMEGAMON II for DB2, press the Return to DB2 pushbutton at the bottom of the screen.



Using Transplex Navigation with OMEGAMON II for IMS

Using Transplex Navigation with OMEGAMON II for IMS

IntroductionTransplex navigation is available from the OMEGAMON II for IMS Details for Region panel. From this panel, use Transplex navigation to go to the corresponding OMEGAMON II for DB2 panel.


Navigating from the Details for Region panel to DB2You can use session switching to reach an OMEGAMON II for IMS session either from OMEGAVIEW or another OMEGAMON; refer to “Using Session Switching” on page 54 for instructions. You can then use the following procedure to access the Details for Region panel and use Transplex navigation.


Step Action Result

1 From the System Overview panel, select Regions from the Alerts group and press Enter.

The Regions Summary panel displays.

2 From the Regions Summary panel, select a region and press Enter.

The Details for Region panel displays.

3 From the Details for Region panel, press the GoTo DB2 pushbutton at the bottom of the screen.

The OMEGAMON II for DB2 target panel displays.

If you want to return to OMEGAMON II for IMS, press the Return to IMS pushbutton at the bottom of the screen.


Using Transplex Navigation with OMEGAMON II for DBCTL


Using Transplex Navigation with OMEGAMON II for DBCTL

IntroductionTransplex navigation is available from the OMEGAMON II for DBCTL Thread Details panel. From this panel, use Transplex navigation to go to the corresponding OMEGAMON II for CICS panel.


Navigating from the Thread Details panel to CICSYou can use session switching to reach an OMEGAMON II for DBCTL session either from OMEGAVIEW or another OMEGAMON; refer to “Using Session Switching” on page 54 for instructions. You can then use the following procedure to access the Thread Details panel and use Transplex navigation.

Note: You invoke Transplex navigation with a pushbutton. If there is no transaction activity to monitor, this pushbutton does not display on the panel..

Step Action Result

1 From the System Overview panel, select Threads and press Enter.

The Threads Summary panel displays.

2 From the Threads Summary panel, select a transaction and press Enter.

The Thread Details panel for that transaction displays.

3 From the Threads Details panel, press the GoTo CICS pushbutton at the bottom of the screen.

The OMEGAMON II for CICS target panel displays.

If you want to return to OMEGAMON II for DBCTL, press the Return to DBCTL pushbutton at the bottom of the screen.



Using IMS Direct Transfer


IntroductionYou can use IMS Direct Transfer to move from the System Overview panel, from any primary panel in your current session of OMEGAMON II for DBCTL, or from some panels displaying pushbuttons in your current session of OMEGAMON II for DBCTL, to the corresponding panel in any other OMEGAMON II for DBCTL or OMEGAMON II for IMS session.

A primary panel is any panel you can access directly from the System Overview panel, either by choosing an option, or pressing a function key. For example, the console panel is a primary panel, because you can access it from the System Overview panel by pressing a function key.

You can use IMS Direct Transfer as follows:

1. On the System Overview panel, primary panel, or panel with pushbuttons, tab to the system ID entry field underneath the date.

2. If you know the ID of the DBCTL or IMS system you want to monitor, type that ID in the entry field, and press Enter. The corresponding panel in the OMEGAMON II monitoring the system you specified displays.

3. If you do not know the ID of the DBCTL or IMS system you want to monitor, press F4 to display a list of the DBCTL and IMS systems currently defined to OMEGAVIEW.

4. Tab to the system you want to monitor and press Enter. If it is not active, ask your system administrator to start the CUA session associated with this system.

5. When the system ID you chose from the list displays in the entry field, press Enter to transfer to the OMEGAMON II monitoring that system. The corresponding panel in the OMEGAMON II monitoring the system you specified displays.

To choose a different system ID, return to step 3.



Monitoring System Performance 67

Monitoring System Performance

Chapter overviewThis chapter explains the OMEGAMON II approach to system-wide monitoring. It begins by describing the System Overview panel, which provides a realtime perspective of your system and lets you detect problems and navigate to different areas.

Chapter contentsThe System Overview Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Investigating Tripped Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Getting Help for a Tripped Exception . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Accessing Bottleneck Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

4

The System Overview Panel



IntroductionAfter you access OMEGAMON II, the System Overview panel displays.

FIGURE 9. System Overview Panel

This System Overview panel:

n uses status indicators to inform you of current system problems

n serves as a central navigation point to more detailed information

n lets you display panels where you can enter IMS commands for system components, such as a region or a database

Status indicatorsThe System Overview panel is comprised of several status indicators. Typically, these dynamic indicators inform you of the conditions of hardware resources and critical system resources.

Status indicators are grouped into the following areas:

n Status

n Alerts

Note: The Operator Assist section does not indicate status and is not dynamic. Operator Assist lets you select a panel that displays

___ Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 System Overview IMS: I51C_____+ Select a component with “S” to show details+-----------------------------------------------------------------------------+| Status | Alerts ||--------------------------------------+--------------------------------------|| _ Regions ##### _ XRF ----- | _ Pools ----- _ Conflicts ----- || | || _ IMS Status ----- _ ESS ----- | _ Threads ----- _ Databases ----- || | || _ Bottleneck ----- _ Traces ===== | _ Logging ----- _ Fast Path ----- || | || _ Buf. Pools ----- | _ Programs ----- || | || _ I/O ----- | ||-----------------------------------------------------------------------------|| Operator Assist ||-----------------------------------------------------------------------------|| _ Databases _ Regions _ Programs _ Logging |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console F10=Action Bar PA1=Switch PA2=OMEGAVIEW



individual components of your IMS system. You can then select IMS commands for those components.

Status indicators use color to supply system information. Each indicator can be one of five colors:

If your terminal does not support extended attributes or is not a color terminal, you will see status characters instead of colors. The default characters have the following meanings:

You can modify these characters using the Set Controls selection from the Options pull-down.

Exception/Status indicator mappingsThe following table lists the exceptions that map to each System Overview status indicator light.

Green Normal condition.

Yellow Warning condition.

Red Critical condition.

Turquoise Idle or disabled.

Blue Not applicable. Status is not associated with this component.

Hyphen (-) Normal condition.

Equal sign (=) Warning condition.

Pound sign (#) Critical condition.

Period (.) Idle or disabled.

Blank Not applicable. Status is not associated with this component.

This status indicator notifies you:

When these exceptions trip:

Buffer Pools OHLO, VHLO

Conflicts XCNF

Databases ABUF, DBWE, DMBE, OXHI, OXLO, VCAS, VCIS, VMEX, VWRC, VXHI, VXLO

ESS ESNC, ESND, ESTH

Fast Path ADHI, ADLO, ADSU, ASHI, ASLO, BQHI, BQLO, CILO, CUOW, DDHI, DDLO, DMER, DSHI, DSLO, DSPI, HSBH, HSBL, NOFB, NOOT, OBAU, SDLO

I/O ACBH, DNRS, DRDY, IORC, RDSH, TNRS, TRDY



IMS Status CSVC, DISP, INAC, IRFC, IRGC, IRRC, IRRU, IRIN, MSGE, NPDL, NQRE, ONLC, ONLO, PSVC, RSRV, TMSI, VROQ

Logging LLBR, LLCH, LPEX, LPOR, LPOW, LTWA, ODIE, OLER, OLNA, OLST, ORER, ORIP, ORST, OSDN, WDNA, WDNB

Pools ACEA, ACES, ACEW, ACEX, ADBW, ADMB, AEPC, APIE, APSB, APSW, ASAP, AWKP, DMFF, FDBW, FDMB, FEPC, FPSB, FPSW, LDMB, LPSB, OSBL

Programs TPSB

Regions CBHI, CBLO, CCHI, CCLO, CLHI, CLLO, CPUA, CRHI, CRLO, CSHI, CSLO, DSWP, IBHI, IBLO, ICHI, ICLO, ILHI, ILLO, IRCS, IRHI, IRLO, IRQH, ISHI, ISLO, LALO, LMLO, LSLO, PIBC, PIBP, PICC, PICP, PIDC, PIDP, PILC, PILP, PISC, PISP, PIQH, RGSI, RGSH, RGNW, VMLO, VSLO, VTLO, WBHI, WBLO, WCHI, WCLO, WLHI, WLLO, WRHI, WRLO, WSHI,WSLO

Threads Tnnn, THHI, THHP, THLO, THLP

Traces DCMN, DLTR, DSTR, FPTR, IRTP, IRTR, LKTR, PITR, PBTR, SCTR, TCOT

XRF XRAT, XRAV, XRIP, XRIT, XRNS, XRPH, XRSR, XRTO

This status indicator notifies you:

When these exceptions trip:


Investigating Tripped Exceptions


IntroductionAn exception trips when the performance value that the exception monitors exceeds the threshold you set. Tripped exceptions indicate warning or critical conditions. For information on setting thresholds, see “Customizing your exceptions” on page 86.

When an exception trips, a status indicator on the System Overview panel turns either yellow or red. The following figure shows a red Regions status indicator.

FIGURE 10. Regions Status Indicator - Critical Condition

To investigate the red or yellow status light on the System Overview panel:

1. Place the cursor next to the red or yellow status light for Regions and press Enter.

OMEGAMON II displays a pop-up that indicates which exception tripped. Figure 11 on page 72 shows the pop-up for a tripped RGNW exception.

___ Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 System Overview IMS: I51C_____+ Select a component with “S” to show details+-----------------------------------------------------------------------------+| Status | Alerts ||--------------------------------------+--------------------------------------|| _ Regions ##### _ XRF ----- | _ Pools ----- _ Conflicts ----- || | || _ IMS Status ----- _ ESS ----- | _ Threads ----- _ Databases ----- || | || _ Bottleneck ----- _ Traces ===== | _ Logging ----- _ Fast Path ----- || | || _ Buf. Pools ----- | _ Programs ----- || | || _ I/O ----- | ||-----------------------------------------------------------------------------|| Operator Assist ||-----------------------------------------------------------------------------|| _ Databases _ Regions _ Programs _ Logging |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console F10=Action Bar PA1=Switch PA2=OMEGAVIEW



FIGURE 11. A Tripped Exception

2. To see details related to the red or yellow status light, press Enter.

OMEGAMON II displays an information panel similar to the one in the following figure.

___ Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 System Overview IMS: I51C______+ Select a component with “S” to show details +----------------------------------------------------------------------------+ | Status | Alerts | |-----------------------------------+----------------------------------------+ |_ Regions ##### _ XRF ----- | _ Pools ----- _ Conflicts ----- | | | | |_ IMS Status ----- _ ESS ----- | _ Threads ----- _ Databases ----- | +----------------------------------------------------------------------------+ | Regions Tripped Exceptions | | | | | | Move cursor to selection, then press Enter. | | | | Exception Description | | | | RGNW Region waiting time is greater than 1 minute. | | | | | | | | | | | | F1=Help F12=Cancel | +----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console F10=Action Bar PA1=Switch PA2=OMEGAVIEW



FIGURE 12. Regions Summary Panel (Primary)

3. Place the cursor next to the item and press Enter.

____ Actions GoTo View Options Help__________________________________________________04/29/99 4:09:19 PM Regions Summary I51C Lines 1 to 4 of 4+----------------------------------------------------------------------+| Name | Type | CPU | I/O | Perform.| Dispatching || | | Rate | Rate| Group | Algor. Priority Queue |+----------------------------------------------------------------------+| IMS510CC | CONTROL | .000| .0| 520 | Fixed | (5D) 93| 0 || IMS510CB | DBRC | .000| .0| 520 | Fixed | (5D) 93| 0 || IMS510CD | DLS | .000| .0| 520 | Fixed | (5D) 93| 0 || IMS510CI | IRLM | .000| .0| 520 | Fixed | (5D) 93| 0 |+----------------------------------------------------------------------+ (Regions) <Virtual Storage> <CPU>F1=Help F2=Keys F3=Exit F5=Refresh F6=Console **=Bkwd **=FwdF10=Action Bar F15=System Overview

Getting Help for a Tripped Exception


Getting Help for a Tripped Exception

IntroductionYou can access help for individual tripped exceptions in the menu/command interface. For each tripped exception, this help gives you detailed information and recommended actions.

To get help for individual tripped exceptions:

1. Select Cmd/Menu Interface (OMEGAMON) from the GoTo pull-down.

2. Make sure the OMEGAMON screen space is blank, and press Enter.

3. Type E.B on the INFO-line and press Enter.

4. Place the cursor on the name of the tripped exception you want to investigate, and press PF11.


Accessing Bottleneck Analysis


IntroductionYou can use the OMEGAMON II bottleneck analysis feature to investigate response time problems. You can activate the collector, and view summary and detailed bottleneck analysis information for PSB groups.

You access bottleneck analysis by selecting the Bottleneck light on the System Overview panel. You can activate the bottleneck analysis collector by selecting Bottleneck Analysis Options from the Options pull-down menu on the System Overview panel.



Issuing IMS Commands 77

Issuing IMS Commands

Chapter overviewOMEGAMON II provides a quick and easy way to monitor the performance of your IMS system. You can quickly spot the delays in your system, identify who is affected by the delays, and determine the cause of the delays.

Once you have all this information, you may want to issue IMS commands to solve the problem as soon as possible without leaving OMEGAMON II. You can issue IMS commands from OMEGAMON II’s CUA using the:

n Operator assist feature

n Action bar

n System Console panel

This chapter explains how to use these techniques.

Chapter contentsUsing the Operator Assist Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Using the System Console Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Using the Action Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

5

Using the Operator Assist Feature


Using the Operator Assist Feature

IntroductionThe operator assist feature provides you with an easy way to enter IMS commands, even if you do not remember the names of the commands or the syntax. The Operator Assist section of the System Overview panel displays the system components for which you can select IMS commands. To issue an IMS command:

1. Select a system component from the Operator Assist section of the System Overview panel.

2. Select a specific item from one of the Operations panels.

3. Select an action from the Actions pull-down or select an action with an action code mnemonic. The action code mnemonics display at the top of the panel under the panel name.For example, to start the PAYROLL1 database, you would:

1. Position the cursor next to Databases in the Operator Assist section and press Enter.OMEGAMON II displays the Database Operations panel.

2. Position the cursor next to database PAYROLL1, type a slash (/), and press Enter.OMEGAMON II displays the Actions pull-down.

3. Position the cursor next to Start and press Enter.OMEGAMON II issues the IMS command to start database PAYROLL1.

Note: To use the short-cut technique in place of steps 2 and 3, position your cursor next to database PAYROLL1 and type the action code mnemonic R to start the database.

Issuing IMS Commands 79

Using the System Console Panel

Using the System Console Panel

IntroductionYou can use the System Console panel to enter free-form IMS commands on the command line. To enter IMS commands using the System Console panel:

1. Press F6 to display the System Console panel.

2. Position the cursor on the command line at the bottom of the System Console panel.

3. Type an IMS command, including the DBCTL recognition character, and press Enter.Responses from the system display in the window at the bottom of the panel.

Using the Action Bar


Using the Action Bar

IntroductionYou can issue any valid IMS command from any panel that has an Actions pull-down on the Action Bar.

Open the Actions pull-down menu. A panel similar to the panel in the following figure displays.

FIGURE 13. Select IMS Command Entry Panel

Note: The Actions pull-down menu will display the actions available for the panel where you open the Actions Pull-down.

Type a 2 or an I in the input field, or move the cursor to line 2. Press Enter.

OMEGAMON II displays the following pop-up panel.

FIGURE 14. IMS Command Entry Panel

Type the IMS command and press Enter.

Note: You can use up to 112 characters for the command. You do not need to enter the command recognition character. The OMEGAMON II CUA system does this automatically. The CUA system passes the command recognition character when a DBCTL system is active. Otherwise, the forward slash is added to the command.

_ 1. Show details for an item 2. IMS Command Entry 3. Exit Omegamon II F3 Enter F1=Help F12=Cancel

Enter IMS Commands Type the IMS command, then press Enter ____________________________________________________________ ____________________________________________________________ Enter F1=Help F12=Cancel

Customizing Your OMEGAMON II Profiles 81

Customizing Your OMEGAMON IIProfiles

Chapter overviewYour profiles control the characteristics of your OMEGAMON II for DBCTL session.

You have two types of OMEGAMON II profiles:

This chapter explains the elements of these two profiles and how to customize them.

Chapter contentsYour Logon Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Your User Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Logon Your logon profile contains all the information associated with your user ID:n the parameters you specify when you log onn your preferences about the way information displays on

panels and how you want to interact with OMEGAMON II for DBCTL

User User profiles contain information about how and when you want to receive information from OMEGAMON II. OMEGAMON II identifies each profile by a unique 2-character profile ID.

6

Your Logon Profile


Your Logon Profile

IntroductionYour logon profile contains all the information associated with your user ID:

n the parameters you specify when you log on (for example, the user profile you are using for your current session)

n your preferences (for example, whether or not the date and time display on each panel)

Only you have access to your logon profile, because only you have access to your user ID.

Logon parametersWhen you log on to OMEGAMON II, you specify the following information, which becomes part of your logon profile:

n your application ID

n your profile ID

n the number of logical rows

n the refresh interval

PreferencesYour preferences are a permanent part of your logon profile. You can customize your preferences as follows:

1. Select Set Preferences from the Options pull-down.The system displays the Preferences menu.

2. Tab to the preferences you want to set and make your changes.The following list describes each preference setting:

Mnemonics

On Displays the input area on the action bar for entering mnemonics.

Off Does not display the input area.

Beep

On Sounds the terminal alarm under certain error conditions.

Off Does not sound the alarm.

Panel ID

On Displays the panel ID on every panel.

Off Does not display the panel ID.


Your Logon Profile

3. When you finish customizing your preferences, press Enter.The system returns to your current panel.

Time/date display

On Displays the time and date on every panel.

Off Does not display the time and date.

Function key area

On Displays the function key area at the bottom of every panel.

Off Does not display the function key area.

Implicit action

On Enables implicit selection on full panels. This means that you can move the cursor to a field and press Enter to request the default action, Show details, for the object represented in that field.

Off Disables implicit selection. This means that after you move the cursor to a field, you must type s and press Enter to request the default action, Show details, for the object represented in that field.

National language

Specifies the language to display on panels.

Date Format Specifies how the date is to display. Choose one of the following formats:n mm/dd/yy (default)n dd.mm.yyn Month dd, yyyyn Day, Month dd, yyyyn dd/mm/yyn yy/mm/ddn yyyy.dddn yy.dddn ddd.yyn ddd.yyyyn dd Month yyyyn Day, dd Month yyyyn dd mmm yyyy

Time Specifies how the time is to display. You can specify the:n format hour (12 or 24)n separator character (default is :)n morning indicator (default is AM)n afternoon indicator (default is PM)

Your User Profile


Your User Profile

IntroductionYour user profile allows you to customize how and when you receive information in an OMEGAMON II session. Each user profile has a unique 2-character profile ID.

Creating a user profileYou can create a user profile based on the Candle default profile (/C) as follows:

1. Choose a profile ID for your user profile.

2. Log off by pressing F3 and confirming your choice.

3. Log back on, specifying the unique 2-character profile ID of the user profile you are creating.

Warning:

When naming the user profile that you create, make sure that the profile ID is available and not in use. To do this:

1. Select Cmd/Menu Interface (OMEGAMON) from the GoTo pull-down.

The Zoom to OMEGAMON pop-up displays.2. Make sure that OMEGAMON screen space is blank, and

press Enter.

The Main Menu displays.3. Type P.H.A on the INFO-line, and press Enter.

The List User Profiles screen displays.4. Scroll through the list using F7 and F8.

The last two characters of the profile names beginning OIUSER represent the profile IDs of all the available user profiles. You can log on with any of these profiles, your site default profile (/I), or the Candle default profile (/C).

However, if you want to create a new profile, make sure that the profile ID you want to use is not on this list. If you want to customize an existing profile, remember that you need to check with your system administrator before you customize any profile that you did not create.

5. When you have finished looking at the list, you can return to the CUA by pressing PA2.


Your User Profile

4. Customize the profile’s controls and exceptions to meet your needs, following the procedures “Setting Controls” on page 85 and “Customizing your exceptions” on page 86.The following sections describe how to customize your user profile:

n for the CUAn for the menu/command interface

Customizing the CUA component of your user profileCustomizing the CUA component of your user profile includes:

This section explains how to set controls and exceptions.

Setting Controls

This section tells you how to set controls for your user profile.

1. Select Set Controls from the Options pull-down.The system displays the Controls menu.

2. Use the tab key to move among the items on the Controls menu. Make your changes.The following list shows each item on the Controls menu and its purpose:

Setting controls Lets you define how and when OMEGAMON II for DBCTL displays information.

Customizing exceptions

Lets you customize the exceptions you want to use to monitor the system.

Interval refresh Enter the number of seconds for each interval refresh.

Wait period for response to commands

Enter the time period that you want OMEGAMON II to wait for a response to issued commands before displaying an error message.

Green status bars displayed

Enter On to display green status bars on displays or Off to suppress green status bars on displays.

Blue status bars displayed

Enter On to display blue status bars on displays or Off to suppress blue status bars on displays.

Use Characters in Status Bars

Enter On to display characters in status bars or Off to suppress characters in status bars.

Show PSBs with Status of Not-Fnd

Enter On to display PSBs with a status of Not-Fnd or Off to suppress PSBs with a status of Not-Fnd.

Show DMBs with Status of Not-Fnd

Enter On to display DMBs with a status of Not-Fnd or Off to suppress DMBs with a status of Not-Fnd.

Show RGNs with Status of Idle + Hot

Enter On to display RGNs with a status of Idle + Hot or Off to suppress RGNs with a status of Idle + Hot.

Your User Profile


3. When you finish setting your controls, press Enter.The system returns to your current panel.

Customizing your exceptions

You can use exceptions to specify

n which system activities you want to monitor

n at what points you want the system to notify you about potential problems associated with those activities’ performance

An exception is an unusual condition or situation which might affect system availability and/or performance.

Confirm IMS commands before processing

Enter On to display the confirmation pop-up before issuing an IMS command or Off to suppress the confirmation pop-up before issuing an IMS command.

Character for RED bar Enter a character that you want to display in place of the red bar on terminals that do not support extended attributes or color. Default is the pound sign (#).

Beep on critical exception

Enter On to hear a beep when an exception is at a critical level or enter Off to suppress the beep.

Automatically go to console

Enter On to automatically go to the console after entering an action against a resource on any Operator Assist panel and after entering an IMS command from the IMS Command Entry pull-down.

Enter Off to preserve the current navigation.

Character for YELLOW bar

Enter a character that you want to display in place of the yellow bar on terminals that do not support extended attributes or color. Default is the equal sign (=).

Automatically go to console

Enter On to automatically go to the console after entering an action against a resource on any Operator Assist panel and after entering an IMS command from the IMS Command Entry pull-down. Enter Off to preserve the current navigation.

Character for GREEN bar

Enter a character that you want to display in place of the green bar on terminals that do not support extended attributes or color. Default is the hyphen (-).

Character for IDLE bar Enter a character that you want to display in place of the turquoise idle bar on terminals that do not support extended attributes or color. Default is the period (.).


Your User Profile

There are two kinds of exceptions:

Each exception belongs to a group of related exceptions—an exception group. You can choose not to monitor any of the following:

n an entire exception group

n an individual exception

n either the warning or the critical component of an individual threshold

Each exception maps to a light on the System Overview panel (see “Exception/Status indicator mappings” on page 69). The help for each exception group explains which light or lights its exceptions map to.

If multiple thresholds that map to the same light trip, some at the warning threshold and some at the critical, the corresponding light turns red. If all of them trip at their warning thresholds, the light turns yellow.

You can customize the exceptions associated with your user profile as follows:

1. When you log on, specify the 2-character ID of the user profile you want to customize.Note: You can customize the Candle default profile (/C) only for your

current session.

Alerts Alerts represent incidents or conditions. If you are monitoring a given alert, a yellow light displays when the associated incident occurs, or when the associated condition exists.

Thresholds Thresholds represent levels of activity, and allow you to define acceptable and unacceptable performance. There are high and low thresholds to represent high and low activity levels. Both kinds of thresholds have warning and critical values.

If you are monitoring a threshold and you specified a warning value, a yellow light displays when the associated activity reaches or falls to that value (depending on the threshold type, high or low).

If you specified a critical value, a red light displays when the activity reaches or falls to that value.

Warning:

You must use the following procedure to customize exceptions.

The first time any user logs on to OMEGAMON II for DBCTL through the CUA with a given profile, OMEGAMON II builds an exceptions table using the profile’s existing exception values. These values can be either the original defaults, or values that were previously specified, either in the CUA or using commands.

Do not use the XACB command, or options A through E on the Profile Menu to customize a profile’s exceptions. OMEGAMON II writes over those values with the values in the exceptions table, the next time any user logs on with that profile through the CUA.

Your User Profile


2. From any panel, select Customize Exceptions from the Options pull-down.A list of all the OMEGAMON II for DBCTL exception groups displays, as shown in the following figure.

FIGURE 15. Exception Groups Index

3. If you know the name of the exception you want to customize, you can look up the name of its exception group in the “Exceptions Table” on page 233. Otherwise, choose the group whose name describes the DBCTL activity you want to monitor or stop monitoring. Scroll through the list of exception groups using F7 and F8, and select the group you want to customize.OMEGAMON II displays the appropriate exception group.

For example, the following figure shows the Threads - High Exceptions Thresholds exception group.

___ Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 System Overview IMS: 151C ___ + +-----------------------------------------------+ Select a component wi| Exception Groups Index |+---------------------| |-------+| Stat| Lines 1 to 13 of 39 | ||---------------------| Move cursor to selection, then press Enter. |-------|| _ Regions ##### | |----- || | Exception Groups | || _ IMS Status ----- | |----- || | Buffer Pools - Low | || | CPU - High | || _ Bottleneck ----- | CPU - Low |----- || | Databases - Alerts | || _ Buf. Pools ----- | External Subsystem - Alerts | || | External Subsystem - High || _ I/O ----- | Fast Path - Alerts ||---------------------| Fast Path - High |-------|| | Fast Path - Low | ||---------------------| Fragmentation - Low |-------|| _ Databases | I/O Rates - Datasets | |+---------------------| I/O Rates - Regions High |-------+ | I/O Rates - Regions Low | | | | F1=Help **=Bkwd F8=Fwd F12=Cancel | +-----------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console F10=Action Bar PA1=Switch PA2=OMEGAVIEW


Your User Profile

FIGURE 16. Threads—High Exceptions Thresholds Pop-up

4. If you want to monitor any of the exceptions in this exception group, type ON in Exceptions Group Monitor.If you do not want to monitor any of the exceptions in this exception group, type OFF in Exceptions Group Monitor, and skip to step 8.

Note: For more detailed information about this exception group, press F1.

5. Tab to the exception you want to customize. If you want to monitor this exception, type ON under Monitor.If you do not want to monitor this exception, type OFF under Monitor, and skip to step 7.

6. If the exception you’re customizing is an alert, skip to step 7.If the exception you’re customizing is a threshold, you can customize its warning and critical threshold values. When the activity this threshold monitors reaches the warning value, a yellow light displays. When it reaches the critical value, a red light displays.

If you don’t want to monitor this threshold at the warning level, you can type OFF under Warning. If you don’t want to monitor this threshold at the critical level, you can type OFF under Critical. You can turn both values OFF if you want. If you do this, the system turns the exception OFF.

If you want to specify both values, remember that if the threshold is a high threshold, you must specify a critical value that is higher than the warning value. If the threshold is a low threshold, you must specify a critical value that is lower than the warning value.

You can specify both values and press Enter, or you can specify one value, blank out the other, and press Enter to have the system calculate the other value for you, as follows:

IF you specify . . . THEN the system calculates . . .

a warning value (for example, 10) for a low threshold,

a critical value that is 80% of your warning value (in this case, 8).

a critical value (for example, 8) for a low threshold,

a warning value that is 125% of your critical value (in this case, 9).

+---------------------------------------------------------------------------+| Threads - High Exceptions Thresholds || || Name Description Warning Critical Monitor || || THHI Active threads >nn . . . . . . 0 1 On + On/Off || THHP Active threads >nn% of total . 72 80 On + On/Off || || Exceptions Group Monitor: On + On/Off || || Enter F1=Help F3=Exit F4=Prompt F12=Cancel |+---------------------------------------------------------------------------+

Your User Profile


7. Repeat steps 5 and 6 for any other exceptions in this group that you want to customize.

8. When you finish customizing this exception group, press F3 to return to the list of exception groups.

9. To return to your panel, press F12.

a warning value (for example, 80) for a high threshold,

a critical value that is 125% of your warning value (in this case, 96).

a critical value (for example, 96) for a high threshold,

a warning value that is 80% of your critical value (in this case, 76).

IF you specify . . . THEN the system calculates . . .


Your User Profile

Customizing the menu/command interface component of your user profile

The Profile Menu

Note: This section does not apply to CUA interface users.

You can create and maintain user profiles using the Profile Menu of the menu interface. To access this menu, select the Profile option from the Main Menu.

OMEGAMON II displays the Profile Menu shown in the following figure.

FIGURE 17. Profile Menu

The following sections describe how to use the Profile Menu to create, maintain, and use the menu/command interface component of a user profile.

Creating and maintaining profiles

Use the Create, Delete, and Save Profiles Menu to create and maintain the menu/command interface component of your user profile. To access this menu:

1. Select option H from the Profile Menu or type P.H on the INFO-line of any screen and press Enter.The menu shown in Figure 18 on page 92 displays.

________________ KOIPOPT VTM DBCTL /C I51C 01/02/97 12:00> Help PF1 Exit PF3 Save Profile PF22> Enter a selection letter on the top line.===============================================================================> Profile Menu> Exceptions_ A POOLS ............... Set pool utilization and fragmentation exceptions_ B DATABASE/FAST PATH... Set database, DASD logging, and fast path exceptions_ C IMS MISC . .......... Set miscellaneous IMS-related exceptions_ D OPERATING SYSTEM .... Set operating system-related exceptions_ E VSAM/STATIC ......... Set VSAM, trace, and other static exceptions_ F MESSAGES ............ Set exception messages> Configuration_ G CONFIGURE ........... Set default start-up configuration_ H SAVE/DELETE ......... Create, delete, save profiles> Quick-set Options_ I COLOR ............... Set color mode and colors_ J BACKGROUND .......... Set background processing (XLF, ASF, and TSF)_ K AUTO ON ............. Set automatic updating ON_ L AUTO OFF ............ Set automatic updating OFF_ M LOGGING ............. Log on, log off, log out, log options >

Your User Profile


FIGURE 18. Create, Delete, and Save Profiles Menu

You can select options from this menu to list all existing profiles, save or delete a profile, and specify a description for your profile. The OMEGAMON II menu system offers easy access to the commands for creating and maintaining profiles.

Note: Do not use options E, Save Install, and F, Delete Install. Only the person who is customizing OMEGAMON II for DBCTL for your site uses these options to work with your site profile.

2. Select option A, List Profiles, to display a list of all available profiles.The List User Profile screen appears as shown in the following figure.

FIGURE 19. List User Profiles Screen

________________ KOIOPU VTM DBCTL /C I51C 01/02/97 12:00> Help PF1 Back PF3 Save Profile PF22>===============================================================================> SAVE, DELETE, OR LIST PROFILES _ A LIST PROFILES ....... List user profiles_ B DESCRIBE PROFILE .... Describe user profile _ C SAVE USER............ Save new/altered user profile_ D DELETE USER.......... Delete user profile _ E SAVE INSTALL......... Save new/altered installation profile_ F DELETE INSTALL....... Delete installation profile===============================================================================

________________ KOIOPUA VTM DBCTL /C I51C 01/02/97 12:00> Help PF1 Back PF3 Up PF7 Down PF8 Save Profile PF22>===============================================================================> LIST USER PROFILES >PPRF LIST> RKOIPFSV DSN=TDIMS1.I2510SMP.R2.I51C.RKOIPFSV> ____________________________________________________> Profile ID Description Date Modified>> OIUSERAH USER PROFILE 06/17/93> OIUSERBS USER PROFILE 06/17/93> OIUSERCM USER PROFILE 02/26/93> OIUSERGG USER PROFILE 05/28/93> OIUSERMH USER PROFILE 07/15/93> OIUSERSK USER PROFILE 06/09/93> OIUSERXX USER PROFILE 08/16/93


Your User Profile

Saving Your profile

You can save your profile for subsequent sessions using the New/Altered User Profile screen. To access this screen:

1. Select the Save User option on the Create, Delete, and Save Profiles menu.

2. Specify a 2-character suffix that identifies your profile.When you save your profile, OMEGAMON II saves all current values for all user profile options referenced in “Configuring profiles” on page 94, as well as numerous exception analysis parameters.

Deleting the menu/command interface component of your user profile

You can delete the menu/command interface component of your user profile using the Delete User Profile screen. If you do this:

n The values in the menu/command interface component of your user profile revert to Candle defaults.

n You do not affect active sessions started with the user profile you’re working with.

To access the Delete User Profile screen:

1. Select the Delete User option on the Create, Delete, and Save Profiles menu.

2. Specify the 2-character suffix that you used when you created your profile.

Describing your profile

You can specify a single line description using the Describe a Profile screen. To access this screen:

1. Select the Describe Profile option on the Create, Delete, and Save Profiles menu.The Describe a User Profile screen shown in the following figure displays.

FIGURE 20. Describe a User Profile Screen

________________ KOIOPUB VTM DBCTL /C I51C 01/02/97 12:00> Help PF1 Back PF3 Save Profile PF22>===============================================================================> DESCRIBE A USER PROFILE > To add or change the description for this profile, type the description> between the single quotes that follow the colon on the last line. Press> ENTER to record the change. To save the description with this profile,> select SAVE USER on the PROFILE MAINTENANCE menu. PPRF COMMENT: ‘USER PROFILE ‘ ===============================================================================

Your User Profile


2. Type your description between the single quotes and press Enter.

3. Save the description by pressing PF22.

Configuring profilesOMEGAMON II saves the settings for all profile-definition commands in a profile each time you press PF22. You can change the setting of any user profile option at any time during a session. OMEGAMON II uses the changed setting during the current session only, unless you save the profile.

You configure profiles using the Set Startup Configuration menu. To access this menu, select option G, Configure, on the Profile Menu shown in Figure 17 on page 91, or type P.G on the INFO-line of any screen and press Enter. OMEGAMON II displays the menu shown in the following figure.

FIGURE 21. Set Startup Configuration Menu

The following sections describe the types of profile parameters you can customize.

Display options

Use the Set Display Options panel to change Display options. To access this screen, select A, Display, on the Set Startup Configuration menu or type P.G.A on the INFO-line of any screen and press Enter. This screen contains parameters to activate and deactivate various features in OMEGAMON II:

n Automatic screen facility (ASF)n Timed screen facility (TSF)n Exception logging facility (XLF)n Terminal belln LogIt also controls display characteristics for:

n the date (USA or EUROPEAN)n minor commands (UPPER or LOWER case)n all command output (UPPER or MIXED case)n scroll amount (PAGE or CSR)

________________ KOIOPTE VTM DBCTL /C I51C 01/02/97 12:00 > Help PF1 Back PF3 Save Profile PF22> Enter a selection letter on the top line.===============================================================================> Set Startup Configuration _ A DISPLAY ............... Display options_ B CONTROL ............... Control function options_ C ROUTING ............... Log sysout class, destination, and printer options_ D PLOT .................. IMS plot thresholds > Most changes you make from this menu path become permanent when you save your> profile. Press PF22 to save your profile.


Your User Profile

n the first screen to display when OMEGAMON II is startedn the interval for the terminal belln whether zeros values display as zeros or blanks

Note: OMEGAMON II does not save this setting in a profile.

Color options

You can set color, highlighting, and extended attribute options for each field on the OMEGAMON II display using the Color Settings menu.

To access this menu, select I, Color, on the Profile Menu or type P.I on the INFO-line of any screen and press Enter. Options A, B, and C allow you to turn on extended color, basic color, or monochrome display. Option D includes parameters to define the display attributes of each field on the display.

Control function options

Use the Set Control Function Options screen to set control function options.

To access this screen, select B, Control, on the Set Startup Configuration menu (Figure 21 on page 94) or type P.G.B on the INFO-line of any screen and press Enter. These options control the:

n screen space fetch feature (.FGO)n interval for OMEGAMON II cyclesn number of entries in the device name tablen prevention of loops caused by the PEEK commandn automatic updating delay cyclen size of the REPORT file for logging screensn size of the work area for the PEEK command

Print routing options

Use the Set Printer and Routing Options screen to control the output options for the REPORT or XLFLOG files.

To access this screen, select C, Routing, on the Set Startup Configuration menu (Figure 21 on page 94) or type P.G.C on the INFO-line of any screen and press Enter. The settings that OMEGAMON II saves in a profile are:

n the number of copies to print

n the ddname to override standard ddname

n the report destination

n the userid for the report

n whether lowercase is folded to uppercase

n the name of the form on which to print

n whether the output is placed in the hold queue and retrieved from TSO

Your User Profile


n separator pages and page headers that identify output from different OMEGAMON II sessions

n characters on the left of the separator page

n characters in the center of the separator page

n characters on the right of the separator page

n the number of lines per page on report

n the SYSOUT class of the report

Timed screen facility entries

The timed screen facility (TSF) lets you program OMEGAMON II events to take place automatically at intervals, such as certain times of the day or certain days of the week.

Use the Set Background Processing menu to specify the parameters that control TSF. To access this menu, select J, Background on the Profile Menu or type P.J on the INFO-line of any screen and press Enter.

Customizing your exceptions

For important, detailed information about how to customize the exception values associated with your user profile, see “Customizing your exceptions” on page 86.

Maintaining Your OMEGAMON II Profiles 97

Maintaining Your OMEGAMON II Profiles

Chapter overviewThis chapter tells you how to copy, delete, export, import, or modify the description of a profile. You must have administrative authority to perform these functions.

For details on types of profiles, see “Customizing Your OMEGAMON II Profiles” on page 81.

Chapter contentsAccessing Profile Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Using the Dynamic Profile Update Facility . . . . . . . . . . . . . . . . . . . . . . . . 99

7

Accessing Profile Maintenance


Accessing Profile Maintenance

IntroductionTo access profile maintenance:

1. On the System Overview panel, go to the Options pull-down and press Enter.

2. Select Profile Maintenance from the list on the Options pull-down by typing the appropriate number in the entry field.

3. The system displays the Profile Maintenance menu. It shows you the current profile, a list of all the profiles, and the action codes.

4. Type an action code in the entry field to the left of the profile you want.

Copy To copy a profile, type C next to the profile you want to copy and press Enter. The Copy Profile window appears.

Give the copy a new name and a description and press Enter.

Delete To delete a profile that is no longer needed, type D next to the profile you want to delete. The Delete Confirmation window appears.

Type the number to delete the profile and press Enter. You cannot delete the Candle default profile.

Modify To modify the description of a profile, type M next to the profile whose description you want to modify and press Enter. The Modify Profile Description window appears.

Type the new description and press Enter. You cannot modify the description of the Candle default profile.

Import To Import a profile that was previously exported, type I next to the profile you want to import and press Enter. The Import Profile window appears.

Type the dataset and member name and press Enter. The new name does not need to match the name of the one you are importing.

Export To Export a profile, type E next to the profile you want to export and press Enter. The Export Profile window appears.

Type the dataset and member name and press Enter. The destination export name does not need to match the one from which you are copying.

Maintaining Your OMEGAMON II Profiles 99

Using the Dynamic Profile Update Facility


Invoking externallyThe Dynamic Profile Update Facility lets you dynamically import and export individual OMEGAMON II user profiles to and from a partitioned dataset by using import and export dialogs that are invoked externally through MVS.

User profileA user profile contains the threshold and exception settings for a monitored IMS. It also contains the values specified in the Set Controls and Set IMS Options available from the Options pulldown. Each user profile is identified by a unique 2-character profile id for a given IMS. The profile id along with the IMS id of the monitored IMS make the profile unique.

MVS Modify commandWhen using the import and export dialogs:

n Invoke KI2EXP and KI2IMP using the MVS Modify command.

n Use KI2EXP to export a profile to a partitioned dataset and KI2IMP to import a profile from a partitioned dataset.

n When you export a profile, its data is written in a standard format to a partitioned dataset member.

n Allocate the partitioned dataset with an appropriate number of directory blocks and using the following values:

BLOCK = fixed

LRECL = 80

BLKSIZE = 8880

n After exporting a profile to a partitioned dataset member, do not modify the member. Unpredictable results may occur when you import the profile.

n Make sure CANSI2, the OMEGAMON II for DBCTL started task name, has write authority to the partitioned dataset.

n When you import a profile, the export process is reversed to create a profile based on the exported information.



Example command for exporting a profileThe MVS Modify command for exporting a profile is as follows:

/F CANSI2, NTD KI2EXP ‘PDSNAME MEMBER PROFILE IMSID IMSTYPE’

where:

n PDSNAME is the Target Partioned Dataset Name

n MEMBER is the Target Partitioned Dataset Member

n PROFILE is the 2-Character Source Profile ID

n IMSID is the Source Profile IMS ID

n IMSTYPE is the Source Profile IMS Type - IMS or DBCTL

Example command for importing a profileThe MVS Modify command for importing a profile is as follows:

/F CANSI2,NTD KI2IMP ‘PDSNAME MEMBER PROFILE IMSID IMSTYPE’

where:

n PDSNAME is the Source Partitioned Dataset Name

n MEMBER is the Source Partitioned Dataset Member

n PROFILE is the 2-Character Target Profile ID

n IMSID is the Target Profile IMS ID

n IMSTYPE is the Target Profile IMS Type - IMS or DBCTL

Messages produced by the Dynamic Profile Update FacilityIf you want to see the following messages indicating success or failure in the MVS Syslog, be sure that you have WTO(Y) specified in the KI2SYSIN Parameter Member in the RKANPAR Dataset. The messages are:

n KI2EXP00 - Profile Export Completed Successfully

n KI2EXPFF - Profile Export was Unsuccessful, see RKLVLOG for Messages

n KI2IMP00 - Profile Import Completed Successfully

n KI2IMPFF - Profile Import Was Unsuccessful, see the RKLVLOG for Messages

These messages appear in the RKLVLOG.

101

Part II: Using OMEGAMON II’s Menu and Command Interfaces

Part II provides information about OMEGAMON II’s menu and command interfaces. It includes chapters on basic and advanced features of these interfaces, and screen space creation and use.

In this section, references to OMEGAMON II signify the menu or command interface, unless the text specifically indicates otherwise.


Using the OMEGAMON II Menu Interface 103

Using the OMEGAMON II Menu Interface

Chapter overviewThis chapter introduces you to the basic features of OMEGAMON II’s menu interface. The most effective way to use the information in this chapter is to perform the instructions at a terminal while you read.

Note: Some details of screen displays and navigation on your system may be different from the descriptions provided in this guide depending on your site’s customization of OMEGAMON II.

Chapter contentsBeginning OMEGAMON II Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . 104Ease-of-Use Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Stopping OMEGAMON II’s Menu Interface . . . . . . . . . . . . . . . . . . . . . . 114

8

Beginning OMEGAMON II Operation



IntroductionThe following sections describe how to start OMEGAMON II and how to use OMEGAMON II menus.

Starting OMEGAMON IIInstallation of OMEGAMON II on your system is in one of the following operating modes:

n through OMEGAVIEW using VTAM

n directly through a dedicated console, VTAM, TSO, or ISPF

See “Logging On to the Menu/Command Interface Directly” on page 218 for a description of these modes.

Ask your system administrator how to log on to OMEGAMON II according to the operating mode and procedures in use at your site.

Accessing the Menu Interface from the CUA InterfaceTo access OMEGAMON II’s menu interface from the CUA:

1. Select option 6, Cmd/Menu Interface (OMEGAMON), from the GoTo pull-down.The Zoom to OMEGAMON pop-up displays.

2. Make sure that OMEGAMON screen space is blank, and press Enter.The Main Menu displays. For more information on using the Main Menu, see “The Main Menu” on page 105.

Menu system operationOMEGAMON II’s menu interface provides an easy way to access detailed information about DBCTL that is available from OMEGAMON commands. Each menu contains the following items:

INFO-line You use the top line of every screen to enter menu selections. For example, to see bottlenecks from the Main Menu, type B on the INFO-line and press Enter.

Comment lines Lines with a greater-than sign (>) in column 1 provide information on the function keys, menu selections, available actions, and information displayed on the screen.

Vertical menu options

Lines with an underscore (_) in column 1 identify menu choices. You can select these options by typing the associated letter on the INFO-line or by typing an S over the underscore and pressing Enter.



For more information on OMEGAMON commands, see “Command Basics” on page 115 and refer to the OMEGAMON II for DBCTL Realtime Commands Reference Manual.

For information on creating and saving your own OMEGAMON screens, see “Screen Spaces” on page 137.

Menu typesOMEGAMON II uses two kinds of menus: vertical and horizontal. The following pages explain both kinds of menus. A good example of a vertical menu is the Main Menu.

The Main MenuWhen you access OMEGAMON II’s menu interface, the Candle OMEGAMON copyright display appears on your screen. When you see this display, press Enter.

After you press Enter, you see the Main Menu shown in the following figure.

FIGURE 22. OMEGAMON Main Menu

Separator bars Lines with equal signs (=) in columns 2-5 separate sections of the screen.

Commands and their output

You enter OMEGAMON commands on any line in the menu/command interface except the INFO-line. OMEGAMON can display related commands and their output on the same screen, so you can analyze related items. For this reason, commands collect on the screen; they don’t immediately disappear. To see Help for the command output, press F1 or type a slash (/) next to the command and press Enter.

________________ KOIMENU VTM DBCTL /C I51C 01/02/97 12:00> Help/News PF1 Exit PF3 Keys PF5 Command Mode PF12>Return to CUA PA2 Colors PF18> Enter a selection letter on the top line.========================================================================> OMEGAMON for DBCTL Performance Monitor Main Menu _ E EXCEPTIONS ....... Current and potential system problems, latch conflicts_ R RESPONSE TIME .... Response time information (RTA users)_ B BOTTLENECKS .... Resource contention (bottleneck analysis) (DEXAN users) _ M MONITOR .......... IMS status, potential problems and graphs_ W WORKLOAD ......... PSBs, DMBs, and regions/threads_ A ALL POOLS ........ Communication, database, and program pools_ C COMPONENTS ....... I/O, logging, storage, and control blocks/modules _ F FAST PATH ........ IMS Fast Path information_ O OTHER SYSTEMS .... DB2 interface and XRF information _ T TOOLS ............ Operator tools



The Main Menu contains several performance monitoring and tuning options. The second line of the screen lists definitions of certain PF keys.

For example, you can display help by pressing PF1. For more information, see “Help screens” on page 110.

Note: You can enter OMEGAMON II’s command interface from the menu interface by pressing PF12 or PF24.

Accessing the Main Menu

If your site has modified the product’s menu system you might not automatically see the Main Menu when you start OMEGAMON II’s menu interface. However, you can display it from any OMEGAMON II screen by typing MENU on the INFO-line starting at the first underscore, as shown in the following figure, and press Enter.

FIGURE 23. The INFO-line

Note: If you are using OMEGAMON II’s command interface, you can access the Main Menu by pressing PF12.

For more information on the INFO-line, see “Panel Format” on page 118.

Selecting menu options

To select a menu option from the Main Menu, type the option letter on the INFO-line, starting at the first underscore, and press Enter.

You can also select an option by moving the cursor to the underscore at the left of the item you want to select, type S, and press Enter.

For example, to reach a menu that monitors IMS, type M on the INFO-line and press Enter.

A menu for monitoring IMSWhen you select Monitor from the Main Menu, you see a screen like the one in Figure 24 on page 107.

MENU______________ VTM DBCTL /C I51C 01/02/97 12:00



FIGURE 24. Monitor Menu with IMS STATUS Display

This is an example of a horizontal menu. It is a combination of a list of options at the top of the screen and the display of the selected option.

OMEGAMON II marks the name of the option currently selected with an asterisk in place of the option letter. For example, in the figure above, an asterisk replaces the letter A in front of the name IMS STATUS.

The screen title, IMS, Operating System, and Fast Path Status, describes the data that displays below the first row of equal signs.

________________ KOIDIMS VTM DBCTL /C I51C 01/02/97 12:00> Help PF1 Back PF3 Up PF7 Down PF8 > To view a topic below, enter a selection letter on the top line. > *-IMS STATUS B-POTENTIAL PROBLEMS C-STARTUP PARMS D-ACTIVE RESOURCES> E-PLOT PAGE F-PLOT IMS===============================================================================> IMS, Operating System, and Fast Path Status > IMS Status: ISYS IMS Version 6.1.0 Subsystem ID = ‘I51C’+ MVS/ESA -- SP6.0.7 IRLM Release 2.1+ IMS Restart date = 00.144 IMS Restart time = 15:46:00+ Checkpoints taken = 1 Current Checkpoint id = 00144/154600+ MPPs active = 0 BMPs active = 0+ Applications scheduled = 0 Transactions queued = 0+ Msg Enqueue rate =.00/sec Msg Dequeue rate =.00/sec+ System Dsn OSAM I/O’s = 304 DLS OSAM I/O count = 0+ >>> Remote Site Recovery not installed <<< ==============================================================================> Operating System: MSYS System CPU usage = 22.12% System SIO rate = 633.33/sec+ IMS CPU usage = .00% IMS SIO rate = .00/sec+ Average IMS CPU = .00% IMS SIO average = .00/sec+ Number of active CPUs = 3 System ID = SP22++ --Virtual Storage--- ----------Working Set-----------+ Below 16m Above 16m Real Expanded Total WKST+ Control Region : 1128K 10880K 2820K N/A 2820K+ DBRC Region : 332K 10028K 1408K N/A 1408K+ DLS Region : 748K 10544K 1720K N/A 1720K+ IRLM Region : 544K 10140K 1884K N/A 1884K+ TMS Region : Region NOT active ==============================================================================> Fast Path: FSYS IFPs (MD) active = 0 IFPs (UT) active = 0+ BALG Msgs processed = 0 BALG Msgs queued = 0+ BALG Msg Enq Rate = .00/sec BALG Msg Deq Rate = .00/sec =======================================================================> Checkpoint: CKPT Current Checkpoint id = 00144/154600+ Block Number = 2+ -----------------------------------------------------------------+ Latest DUMPQ/SNAPQ Checkpoint id = 00144/154600+ Block Number = 2 ======================================================================= > Online IMS change operations: OCHG Online change is not in progress



The Plot IMS Rates displayThe Monitor Menu presents you with several options for monitoring IMS, besides the IMS Status option which is displayed by default. For example, option F, Plot IMS, plots the IMS CPU use and I/O rate.

From the Monitor Menu, select the Plot IMS option by typing F on the INFO-line and pressing Enter. Data accumulates as you continue to press Enter, until OMEGAMON II has enough data to display. Then it displays a screen like the one in the following figure.

FIGURE 25. Monitor Menu with IMS CPU Use and I/O Plots Display

This IMS Plots display is useful for showing trends in CPU and I/O activity, when OMEGAMON II is automatically updating in either dedicated mode or VTAM automatic update mode.

See “Logging On to the Menu/Command Interface Directly” on page 218 for more information on OMEGAMON II modes of operation, and “Delaying automatic updating” on page 133 for more information on automatic updating.

Exception analysisException analysis helps you answer the question, ”Are there problems in the system, and if so, what are they?”.

OMEGAMON II displays a yellow or red light on the System Overview panel whenever an exception to normal system performance occurs (you can adjust the thresholds that define normal performance). This lets you respond to system problems quickly and intelligently.

To begin exception analysis from the Main Menu, select the Exceptions option by typing E on the INFO-line and pressing Enter. The menu shown in Figure 26 on page 109 appears.

________________ KZIIPLT VTM DBCTL /C I51C 01/02/97 12:00> Help PF1 Back PF3 Up PF7 Down PF8 > To view a topic below, enter a selection letter on the top line. > A-IMS STATUS B-POTENTIAL PROBLEMS C-STARTUP PARMS D-ACTIVE RESOURCES> E-PLOT PAGE *-PLOT IMS===============================================================================> IMS CPU Use and I/O Rate PLOTX CPUC IORT++ CPUC CPU Utilization IORT IMS I/Os per sec+ 100% + 240 ++ =>----------------+ 75% =>---------------- 180 +++ 50% + 120 ++ =>----------------+ 25% + 60 =>----------------+



FIGURE 26. Exceptions Menu

From this menu, you can select various exception displays. The following figure shows part of the Systemwide Exceptions display (option B on the Exceptions Menu).

FIGURE 27. Systemwide Exceptions

This display alerts you to several types of exceptions: critical, operational, and status. The display also shows you an operational exception labeled BQHI. The DLTR, DSTR, and LKTR exceptions tell you about the status of certain IMS features.

To see additional information and specific tuning recommendations for exceptions, place the cursor on the exception name and press PF11. For further information, see “Working with Exceptions in VTAM, ISPF, TSO, or Dedicated Mode” on page 222.

________________ KOIEXCP VTM DBCTL /C I51C 01/02/97 12:00 > Help PF1 Exit PF3> Enter a selection letter on the top line.===============================================================================> Exceptions Menu _ A MTO .......................... Master terminal operator (MTO) exceptions_ B SYSTEM........................ Systemwide exceptions_ C CONFLICTS .................... Enqueue and latch conflicts_ D HISTORY ...................... History of all tripped exceptions ===============================================================================

________________ KOISYS VTM DBCTL /C I51C 01/02/97 12:00> Help PF1 Back PF3 Up PF7 Down PF8 Zoom PF11>> For an explanation of an exception, place the cursor on the exception> name and press PF11.>===============================================================================> Systemwide Exceptions LXIMS OMEGAMON/IMS Exception Analysis+ DLTR DL/I Trace ON+ DSTR DISPATCHER Trace ON+ESNC ESS D41A defined in control region; not in any dependent regions+SCTR SCHEDULER Trace ON+ LKTR LOCK Trace ONVXLO VSAM Database: DI21PART DDName: DI21PART I/O Rate = .00 (Low)VXLO VSAM Database: DI21PART DDName: DI21PARO I/O Rate = .00 (Low)

Ease-of-Use Features



IntroductionOMEGAMON II provides context-sensitive help, quick-access menu and display selection, and a zoom feature for more effective navigation.

Help screensFor an explanation of any OMEGAMON II menu or screen, press PF1 for help. For example, if you press PF1 from the Systemwide Exceptions screen, you see a display like the one in the following figure.

FIGURE 28. Systemwide Exceptions Help

You can press PF1 from any help to display information about the OMEGAMON II general help facilities. For example, pressing PF1 from the help shown in the figure above displays the General Help Menu shown in the following figure. You can also access this menu by pressing PF1 on the Main Menu.

FIGURE 29. General Help Menu

________________ KOISYSH VTM DBCTL /C I51C 01/02/97 12:00 > General Help PF1 Back PF3 PF Keys PF5===============================================================================> SYSTEMWIDE EXCEPTIONS -- HELP > This panel displays exception messages for current systemwide problem> conditions. > When static exceptions are displayed on this screen, they only remain on the> screen for 5 OMEGAMON cycles. ===============================================================================

________________ KOIHLP VTM DBCTL /C I51C 01/02/97 12:00 > Back PF3 Main Menu PF4> Enter a selection letter on the top line.=============================================================================== > OMEGAMON for IMS General Help Menu _ A CUA .................. OMEGAMON II for DBCTL CUA front end_ B MENUS................. OMEGAMON’s menu system_ C EXCEPTIONS ........... Recommendations for handling exception conditions_ D OMEGAVIEW ............ How to access Omegaview display_ E ZOOMING .............. Navigation to more detail or related information_ F PF KEYS .............. PF keys in the menu system_ G COMMANDS ............. Command mode and command help_ H SUPPORT .............. Candle customer support information ===============================================================================



From the General Help Menu, press PF3 to return to the previous help. Press PF3 again to return to the screen from which you initially requested help. To return to the Main Menu, press PF4.

Quick access methodOMEGAMON II provides you with a quick method of selecting menu options.

From any screen, to go directly to a selection on the Main Menu, type the letter of that selection, followed by a period, on the INFO-line and press Enter. For example, the following figure shows part of the OMEGAMON II menu hierarchy.

FIGURE 30. Part of the OMEGAMON II Menu Hierarchy

To select the Main Menu option E, the Exception Information Menu, you don’t have to return to the Main Menu. Instead, from any screen, type E. (E followed by a period) on the INFO-line and press Enter.

You can also make multi-level selections. For example, from any screen, to select the Systemwide Exceptions screen, type E.B on the INFO-line and press Enter. This is like typing =n.m for quick access to an ISPF menu.

After selecting a menu with the quick access method, press PF3 to return to the previous screen.

Note: Avoid using screen space names to navigate in the menu system, because this may reset your PF keys. If your PF keys reset, you can reinitialize them by typing MENU on the INFO-line.

The Zoom featureWhen there is more information available about a task, resource, or exception than can appear on one screen, OMEGAMON II displays only the initial or critical data. However, you can easily see additional data. In the top right corner of the screen, you see Zoom PF11.

To zoom to another screen for additional information, position the cursor under the item about which you would like more information, then press PF11. For example:

MAIN MENU E. Exception Information A. ... B. Systemwide Exceptions ... W. Workload information A. ... B. ... C. IMS Regions/Threads A. All Regions



1. From any screen, choose the All Regions option by typing W.C.A on the INFO-line and pressing Enter.A screen like the one shown in Figure 31 on page 112 displays.

FIGURE 31. Regions Menu with All Regions Option Displayed

This screen lists basic information for several regions.

2. To use the zoom feature to see detailed information, position the cursor under a region name (for example, IMS310CC) and press PF11.OMEGAMON II displays the screen shown in the following figure.

FIGURE 32. Detailed Information about a Region

3. To return to the All Regions screen, press PF3.

________________ KOIDRGN VTM DBCTL /C I51C 01/02/97 12:00> Help PF1 Back PF3 Up PF7 Down PF8 Zoom PF11 > To view a topic below, enter a selection letter on the top line. > *-ALL REGIONS B-CONTROL C-DLI D-DBRC E-IRLM> F-BMP G-DEPENDENT REGIONS H-USER LIST I-DB2===============================================================================> All Regions > For more information about a region (RGNA), current reference database> (CDMB), or program specification block (PSB), place the cursor on the> appropriate item and press PF11. #RGNA 5 RGNA IMS310CC IMS310CB IMS310CD IMS310BI TCICS321 rgid --n/a-- --n/a-- --n/a-- --n/a-- 1 cdmb --n/a-- --n/a-- --n/a-- --n/a-- --n/a-- dbt .R ....... ....... ....... ....... ....... psbn --n/a-- --n/a-- --n/a-- --n/a-- --none-- stat --n/a-- --n/a-- --n/a-- --n/a-- Idle

________________ KOIPVSU VTM DBCTL /C I51C 01/02/97 12:00> Help PF1 Back PF3 Up PF7 Down PF8===============================================================================> Virtual Storage Usage > If ‘Security check failed’ and ‘Command not valid’ appear, a password is> required. Enter /PWD on the top line. At the prompt, enter the password. PEEK IMS310CC ASID=87 >> OB8112: Data Collection Initiated <<+ >> OB8111: Warning - WSIZ too small - Addr=A44008 Size=16368 Used=16304 amap+ ===== 2 Gig Line ====== <== 7FFFFFFF Highest 31-bit address+ | |+ |---------------------| <== 7FFFFFFF Top of Extended Private+ | /////////////////// |+ | /// System Area /// | >----------- 4K ELSQA/SWA unallocated+ | /////////////////// | 45K Fragmented free space+ |---------------------| <== 7F67F000 Current bottom of ELSQA/SWA+ | |+ | Available | >----------- 1,854M Avail. for ELSQA/SWA only+ | |+ |---------------------| <== 0B7FFFFF Extended User Area Limit+ | |



OMEGAMON II Menu PF key definitionsHere is a list of the Candle-supplied default PF key definitions you can use on OMEGAMON II menus.

You can display a list of available PF keys at any time by pressing PF5.

PF Key Description

PF1, PF13 Help

PF2, PF14 Not used

PF3, PF15 Return to previous screen

PF4, PF16 Return to Main Menu

PF5, PF17 List PF key settings

PF6 Print the screen

PF7, PF19 Scroll up

PF8, PF20 Scroll down

PF9, PF21 Not used

PF10 Not used

PF1,1 PF23 Zoom

PF12, PF24 Menu/Command mode switch

PF18 Set display colors

PF22 Save user profile

Stopping OMEGAMON II’s Menu Interface


Stopping OMEGAMON II’s Menu Interface

IntroductionIf you logged directly on to OMEGAMON II’s menu interface, log off as follows:

1. Press PF3.You see the following screen.

2. To confirm your choice and stop OMEGAMON, press PF3 again.You can bypass exit confirmation and stop OMEGAMON by entering X.X or /STOP on the INFO-line. In this case, OMEGAMON II displays an OMEGAMON Terminated message. Press Enter to return to the CUA System Overview panel.

3. Press PF3.OMEGAMON II displays the Exit Menu pull-down.

4. Press PF3 to exit.

________________ KOIQST VTM DBCTL /C I51C 01/02/97 12:00 Help PF1 Exit PF3>> Enter a selection on the top line================================================================================> EXIT CONFIRMATION _ M MENU ............. Return to menu system _ C COMMAND .......... Exit menu system to command mode OMEGAMON _ X EXIT ............. End this OMEGAMON session If you select command mode, you can return later to the menu system by usingthe command mode/menu mode toggle, PF12.

Command Basics 115

Command Basics

Chapter overviewThis chapter provides basic information about the format of the OMEGAMON II command interface panel and the syntax of OMEGAMON II commands. It also describes how to log screens and to control screen output in command mode.

Chapter contentsAccessing the Command Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Commands and Screen Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Panel Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Entering Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Command Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Screen Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Screen Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

9

Accessing the Command Interface


Accessing the Command Interface

IntroductionTo access the command interface from the menu interface, press PF12 or PF24. This same key toggles you back to the menu interface.

You can enter OMEGAMON II commands in both the menu interface and the command interface. However, the PF key settings are different in these two interfaces.

The PF keys in the menu interface support menu system navigation; in the command interface, they fetch analysis screens directly. For example, in the command interface, pressing PF3 takes you to a screen space named #03. Because the menu interface is easier to use, Candle recommends that new OMEGAMON users enter commands on the menu interface panels rather than switching to the command interface.

Command Basics 117

Commands and Screen Spaces

Commands and Screen Spaces

IntroductionThere are two ways to operate OMEGAMON II in the command interface: you can enter individual command names or you can execute screen spaces.

A screen space is a predefined set of commands that a user saves in a file and gives a name. When you type the screen space name on the INFO-line and press Enter, all the commands assigned to that screen space execute automatically in sequence. You can also assign a screen space name to a PF key, enabling you to execute the screen space with one keystroke.

Creating screen spaces is discussed in “Screen Spaces” on page 137.

Panel Format


Panel Format

IntroductionThe following figure shows the OMEGAMON II panel format.

FIGURE 33. Panel Format

Each line of the OMEGAMON II panel consists of an input area and a display area. You enter commands in the input area on the left side of the screen, and OMEGAMON II displays command output on the right side of the screen.

The input area of the top line, or the INFO-line, is where you enter menu options, INFO-line commands, or screen space names. The display area shows status information about your session. In the main body of the panel below the INFO-line, OMEGAMON II accepts the input of other types of commands and displays their output.

OMEGAMON II processes data on the INFO-line first. If an entry there begins with a slash (/), OMEGAMON II treats it as an INFO-line command. Otherwise, OMEGAMON II attempts to find and display a screen space by that name.

Next, OMEGAMON II processes the input area of the main body of the panel, executing commands as it finds them, starting at the top of the panel and working down.

______________ #01 VTM DBCTL /C I51C 01/02/97 12:00 <Main body of panel>

<Input area> <Display area>

Command Basics 119

Panel Format

INFO-lineThe following figure shows the components of the INFO-line.

FIGURE 34. INFO-line Format

The OMEGAMON II for DBCTL Realtime Commands Reference Manual discusses status symbols on the INFO-line in more detail. Note that the symbols for the logging status (LOG), the zero-value display option (0), and the bell status (B) appear on the INFO-line only when those features are in use. Otherwise, the field is blank.

If the zero-value display option is on, the system displays zero values as zeros. If the option is off, the system displays zero values as blanks.

Panel display symbolsThis section explains the panel symbols that OMEGAMON II displays with command output.

Comment lines (>)

To designate a comment line, enter a greater-than sign (>) in column 1. Any command that you enter on that line does not execute.

In addition to the comment symbols that you enter yourself, OMEGAMON II automatically comments out some commands after they execute to prevent re-execution on the next cycle. OMEGAMON II also comments out help text so that it remains on the screen until you clear it.

Continuation character (+)

OMEGAMON II displays a plus sign (+) at the end of a line of output to indicate when more output is available. You may see this continuation character after you issue certain major commands that select a long list of items (such as DISK, which displays all online disks). So that the display does not shift off the bottom of the screen, OMEGAMON II displays only one line of

____________________KOIMENU VTM LOG DBCTL /C I51C 01/02/97 12:00:00 0 B Input Area Screen Space Name Mode of Operation Logging Status Product ID User Profile Suffix System ID Screen Refresh Date Screen Refresh Time

Panel Format


data at a time unless you request additional lines. “Displaying continuation lines of command output” on page 132 explains how to request the additional lines.

Online help text also displays the continuation character when more help is available.

Commands that produce multiple display lines when they execute display the plus sign (+) in column 1. For example, the .VTM command displays multiple lines of information on VTAM users as shown in the following figure.

FIGURE 35. VTAM User Information

Commands that you enter below a command with multiple display lines may shift off the bottom of the screen. These commands reappear as soon as you scroll down through the output.

If you enter a new command on a continuation line, OMEGAMON II automatically moves the new command below the existing output lines.

Input character (:)

Some OMEGAMON II commands allow multi-line input for setting parameters. When you issue this type of command, OMEGAMON II responds with a table of keywords and their current settings. On each line of a multi-line input command, column 1 displays a colon (:) indicating that you can overtype the current setting to change the value, as shown in the following figure.

FIGURE 36. OMEGAMON II Keywords

________________ KOIQST VTM DBCTL /C I51C 01/02/97 12:00 .VTM Userid Terminal Mode Session Start Last Update+ R130A207 VTM 01/02/97 11:32:56 01/02/97 11:33:05+ RGI21100 VTM 01/02/97 11:28:40 01/02/97 12:14:22+ RGI21103 VTM 01/02/97 11:22:20 01/02/97 12:14:41

+ RGI21104 VTM 01/02/97 10:52:35 01/02/97 12:14:45

________________ KOIQST VTM DBCTL /C I51C 01/02/97 12:00 .SET: FGOLIMIT = 64 FGOLOOP = OFF: GDEVUCBS = 200 INTERVAL = 5.00: IODELAY = 5 LOOPCOUNT = 15000: LOOPTIME = 5.00 PAGELIMIT = 400: PEEKSIZE = 16384 STATUSMODE = OFF

: OCMDMASTER = ON

Command Basics 121

Entering Commands

Entering Commands

IntroductionTo operate OMEGAMON II in the command interface, you need to know the types of OMEGAMON II commands and the appropriate time and place to enter each type.

Command typesBeginning in column 1 of the following figure, you can see examples of the four types of commands that you can use in OMEGAMON II, along with some sample output.

FIGURE 37. Four Types of OMEGAMON II Commands

The four types of OMEGAMON II commands are:

INFO-line These commands perform control functions, such as printing a screen (/PRINT) and stopping your OMEGAMON II session (/STOP).

INFO-line commands execute first and disappear as soon as they execute. Therefore, you cannot save them in a screen space. INFO-line commands always begin with a slash (/) and you must enter them on the top line starting in column 2.

If you are running in an automatic update mode, placing the cursor in column 1 on this line pauses updating until you move the cursor.

Major These commands select general categories for display, such as system information, resource utilization, or storage utilization. In the example above, the DISK major command produces a list of online disks. You can enter major commands on any line below the INFO-line.

/PRINT_ _ _ _ _ #01 VTM DBCTL /C I51C 01/02/97 12:00 DISK VMXA04 VMXA05 VMSP50 VMHP02 OMONVM DOSTST DP215R DOSRES + dadr 1A0 1A1 1B0 1B1 2A7 2B0 4F1 4F2 .MIN DADR DALC DIO DIOQ DOPN DRES DSTA DTYP DUSR DVMP +

Entering Commands


Command formatThe following is another example of different OMEGAMON II commands and their output. Command fields are four characters long. You can enter commands with labels or arguments, as shown in the following figure.

FIGURE 38. OMEGAMON II Command Format

Minor These commands display detailed information about the category that the major selects. In the example above, the DADR minor command displays the unit addresses of the devices listed with DISK. You can enter minor commands on any line below the INFO-line, but they do not execute unless you precede them by an appropriate major command.

Immediate These commands serve various functions. Some are system monitoring commands, while others provide information about your session or about OMEGAMON II.

In the example above, .MIN produces a list of all the minors of DISK. Immediate commands can also provide screen and session controls, and often perform the same or similar functions as INFO-line commands of the same name. This enables you to include control commands as part of a screen space.

Enter immediate commands on any line below the INFO-line. You can enter immediate commands between a major command and one of its minors.

.MJ DS DISK DLST DSKB DSKC DSKE DSKG DSKM DSKN DSKP DSKQ DSKR DSKS + DISK VMXA04 VMXA05 VMSP50 VMHP02 OMONVM DOSTST DP215R DOSRES + dadr 1A0 1A1 1B0 1B1 2A7 2B0 4F1 4F2 2GDEV SYSDA MIS003 HSM001 WORKB1 PDB002 MIS002 MIS003 SYSB24 SYSD22 PROD02 + lccccnn________ extended argument or keyword field (cols. 8 through 72) argument field (cols. 6 and 7) command name (cols. 2 through 5)

Command Basics 123

Entering Commands

You can enter extended arguments in columns 8 through 72. In the example, the GDEV command has an argument of SYSDA, which is a generic device name in the system. This means that only devices in the SYSDA category display. Many commands also accept keywords and parameters that can extend to column 72. OMEGAMON II cannot extend a parameter string to a second line. You must re-enter the command (along with keywords) on succeeding lines.

label field Many commands accept a character in the label field that alters the type of display output. You can also use this field for special command modifiers, such as those that request online help text for commands.

In Figure 38 on page 122, the numeral 2 in the label field of the GDEV command restricts the display to only the second row of all available output.

command name This field contains the four-character command name. Although the command name field occupies columns 2 through 5, OMEGAMON II recognizes most commands that begin in column 1 and automatically shifts the command one space to the right.

argument field Many commands accept arguments that modify their function or specify output options. In the example, the .MJ command produces a list of major commands. This command has an argument of DS, a group code that specifies that OMEGAMON II list only disk major commands.

Command Help


Command Help

IntroductionOMEGAMON II provides online help for every command in the product. This section describes how to request help for different kinds of commands.

Major, minor, and immediate command helpTo request an explanation of a major, minor, or immediate command, enter one of the three symbols, listed in the following table, in column 1 before the command.

All commands offer a brief, one-line help. Many commands also have an extended help, which provides more information about the command or displays the command operands. A continuation character (+) to the right of the one-line help indicates that more (extended) help is available.

Examples of the three help symbols used with the .WAT command follow.

This entry for the .WAT immediate command

?.WAT

produces a one-line help as shown in the following figure.

FIGURE 39. One-line Help Display

OMEGAMON II comments out the help symbol when the help displays.

When you use a slash instead of a question mark,

/.WAT

an extended help displays as shown in the following figure.

Table 3. Command Help Symbols

? Displays a one-line help that stays on the screen until you clear it.

/ Displays an extended help that stays on the screen until you clear it.

You can clear the help text with the .DCL command discussed later in this guide.

; Displays an extended help that disappears from the screen on the next cycle.

________________ KOIQST VTM DBCTL /C I51C 01/02/97 12:00>.WAT

> Specifies a delay before executing the commands that follow. +

Command Basics 125

Command Help

FIGURE 40. Extended Help Display

The entry

;.WAT

produces the same output as /.WAT, except that plus signs display in column 1 below the one-line help. The plus signs are continuation symbols and indicate that the extended help text will disappear on the next cycle.

You can obtain help for a minor command by using the symbols previously described, without knowing the associated major command name. In some cases, however, OMEGAMON II uses the same minor name for multiple majors. If the function of the minor command is the same for all of its associated majors, OMEGAMON II displays a help panel like the following figure.

FIGURE 41. Minor Command Help Display

In cases where OMEGAMON II uses the same minor command name for multiple major commands, but the function and help text differ, OMEGAMON II lists the possibilities and instructs you to place your cursor under the desired major command name. When you press Enter, the appropriate help displays.

If you know that several major commands share the minor command, you can type the major command name on the same line after the help request. For example, the entry

/dio DISK

________________ KOIQST VTM DBCTL /C I51C 01/02/97 12:00>.WAT> Specifies a delay before executing the commands that follow. +>> Type of Command: Immediate>> Command Format: .WATnn>> 1 | 2 | Definition of operands> -----------------------------------------------------------------------> | .WAT | nn Specifies the length of | | the delay (seconds) before> | | the command(s) that follow are executed.>> EXAMPLE:>> .WAT02> .FGO MYSCREEN>

________________ KOIQST VTM DBCTL /C I51C 01/02/97 12:00>DIO> DIO is a minor command of the following major(s):> DEV DEVL DEVP DISK DSKB DSKC DSKE DSKG DSKM DSKN DSKP DSKQ> DSKR DSKS DSKU DSKV GDEV TAPE TPAL TPBS TPCU TPFR TPMT TPOF> TP16 TP38 TP62 TP7T TP80 2305 2314 3330 3340 3350 3375 3380> 3390> Help: > Displays the I/O count since IPL of the device(s). +

Command Help


produces the help text for the DIO minor specific to the DISK major.

INFO-line command helpYou can obtain INFO-line command help with the .ILC immediate command, rather than with a symbol in column 1. Enter the name of the INFO-line command (cccccc) after .ILC:

.ILC cccccc

You do not need the slash before the command. For example, to get help for the /DEF command, enter:

.ILC DEF

You see a help panel like the one shown in the following figure.

FIGURE 42. INFO-Line Command Help

________________ KOIQST VTM DBCTL /C I51C 01/02/97 12:00>.ILC /DEF> Sets definition mode. +>> Type of Command: INFO-line>> Command Format: /DEF cccc>> 1 | 2 Definition of operands:> ----------------------------------------------------------------------> | /DEF <cccc> ON Turns on definition mode. Definition mode> | suspends command execution (except for the> | commands which control screen editing> | functions) so that you can define a screen> | space without executing commands. Once you> | set definition mode with /DEF ON, it remains> | in effect until you issue /DEF OFF or the> | screen space is saved or replaced.> | OFF Restores normal command execution (cancels> | /DEF ON or /DEF HOLD).> | HOLD Same as ON argument, but definition mode> | remains in effect after you save a screen

Command Basics 127

Command Help

Commands to list commandsAnother form of help enables you to list all OMEGAMON II commands by type. You can also use some of these listing commands to show brief help for each command that displays.

If you issue the .MJ, .MJC, .MJI, or .MIN commands and precede them by an H in the label field (column 1), a one-line help for each command displays.

The display in the following figure lists available OMEGAMON II commands:

FIGURE 43. Commands that List OMEGAMON II Commands

You can limit the major command listing produced with .MJ, .MJC, or .MJI to a particular group of commands by typing the group code. Type .MJ for a list of the group codes.

>.MJ>..> Deletes lines(s). +>.AUP> Displays/resets the status of automatic update in VTAM mode. +>.BEL> Displays/sets bell (audible alarm) support. +>.CN> Opens, closes, swaps, or sets address of the secondary console. +>.D> Deletes lines(s). +>.DCL> Deletes its own line and all comment lines below it. +>.DD> Deletes a block of data from the screen. +>.DEF> Displays/resets the status of definition mode. +>.DIR> Executes a director/collector command.>.DSA> Sets authorization to list and/or zap non-sharable data-only spaces. +>.DSE> Displays the status of the stack. +

Screen Control


Screen Control

IntroductionThis section describes the following screen control functions:

n scrollingn clearing the screenn clearing comment text onlyn inserting and deleting linesn using program function keysn displaying continued lines of command outputn delaying automatic updating

Up/Down scrollingIn the menu interface, you use PF7 and PF8 for scrolling. However, in the command interface, OMEGAMON II assigns PF7 and PF8 to analysis screens, so PF19 and PF20 are the default scrolling keys (on terminals with 24 programmed function keys). They are set to /UP and /DOWN (alias /U and /D), and scroll one physical screen at a time. You can change the default scroll amount with the OPTN command.

You can also scroll by using the /UP and /DOWN INFO-line commands. Both /UP and /DOWN accept the following arguments:

As an alternative to /UP and /DOWN, you can use the INFO-line command /TOP to scroll to the top of the logical screen and /BOTTOM to scroll to the bottom of the logical screen.

You can also type any of the /UP and /DOWN arguments (such as nnn, MAX, or CSR) on the INFO-line before you press the PF key to change the scroll amount. If, for example, you type MAX on the INFO-line and then press PF20, OMEGAMON II scrolls forward the maximum number of lines.

Clearing the screenIf a Candle menu, screen space, or any commands display on your screen, and you want to clear the screen, use the clear screen immediate command. The clear screen command consists of two periods followed by two blanks.

nnn Scrolls nnn lines (nnn can be any number from 1–999).

PAGE Scrolls a physical screen at a time.

MAX Scrolls up or down the number of LROWS defined for your terminal. The short form of MAX is M.

CSR Scrolls according to the current location of the cursor. If the cursor is on the INFO-line, the scroll amount is one page.

Command Basics 129

Screen Control

Enter .. in the input area of any line below the INFO-line to clear the screen below it.

Deleting comment linesIf your screen is cluttered with lines of comment text, and you want to clear the comments but retain other command text, you can use the /DCL INFO-line command or the .DCL immediate command. /DCL clears all comment lines on the logical screen, while .DCL clears all comment lines below its entry line.

The following figure is an example of using /DCL to clear help text.

FIGURE 44. Using the DCL Command

On the next cycle, the panel shown in the following figure appears.

FIGURE 45. Result of the DCL Command

Inserting and deleting linesTo insert blank lines into a screen, use the following immediate command:

.I nn

The variable nn indicates the number of lines to insert. The default is 1. The nn argument must begin in column 6.

/DCL_________________ VTM DBCTL /C I51C 01/02/97 12:00 >.SPT > Sets pattern number n to the value cccccccc for generic selection. .SPT/1 >M* < DEVP/1 MVSA21 MP220A MP220D MVSD21 MVSE21 >dadr > Device unit address (cuu) >dio > Device I/O count (For rate use: ‘DIO.R’) >dres > Number of outstanding RESERVEs from this CPU for this device .DEFON >> OB0130: Definition mode ENABLED. << DEVP/1 dadr dalc dio

.DEFOF >> OB0130: Definition mode DISABLED. <<

____________________ VTM DBCTL /C I51C 01/02/97 12:00 .SPT/1 >M* < DEVP/1 MVSA21 MP220A MP220D MVSD21 MVSE21 .DEFON >> OB0130: Definition mode ENABLED. << DEVP/1 dadr dalc dio

.DEFOF >> OB0130: Definition mode DISABLED <<

Screen Control


OMEGAMON II inserts the new lines above the line where you type the insert command. Therefore, all other lines currently on the screen below the inserted line shift downward. When the command executes, the line you typed over with the insert command restores to its original data. For example, if you first display this screen:

and you enter .I on the second line, like this:

OMEGAMON II inserts one blank line below the first line, and restores all the original data on the second line like this:

To delete lines from a screen space, use the .D nn immediate command. This command works like .I nn. The default is 1.

You can also delete a block of data from the physical screen. To do this, enter .DD on the first and last lines of the block.

Using Program Function (PF) keysWhen you use OMEGAMON II’s command interface, the default PF key definitions differ from those that the menu system uses. In the command interface, some PF keys are preset to control commands such as scrolling and printing, and a number of them are set to Candle-defined screen spaces for various types of analysis. Use the .PFK immediate command to list the settings.

Figure 46 on page 131 lists the default PF key definitions in the command interface.

DISK VMXA04 VMXA05 VMSP50 VMHP02 OMONVM DOSTST DP215R DOSRES + dadr 1A0 1A1 1B0 1B1 2A7 2B0 4F1 4F2 dalc 8 16 6 12 24 16 32 8

DISK VMXA04 VMXA05 VMSP50 VMHP02 OMONVM DOSTST DP215R DOSRES + .I 1A0 1A1 1B0 1B1 2A7 2B0 4F1 4F2 dalc 8 16 6 12 24 16 32 8

DISK VMXA04 VMXA05 VMSP50 VMHP02 OMONVM DOSTST DP215R DOSRES + dadr 1A0 1A1 1B0 1B1 2A7 2B0 4F1 4F2 dalc 8 16 6 12 24 16 32 8

Command Basics 131

Screen Control

FIGURE 46. .PFK Definitions in Command Mode

You can define new PF key settings for your current session with the .PFK command. For example, you could assign the /DEF ON and /DEF OFF INFO-line commands to PF19 and PF20, respectively, to turn definition mode ON while you create a screen space, and OFF when you are finished. Define the keys and type comment text following a slash and asterisk (/*) as shown:

The PF keys that you define with .PFK are in effect only for the current OMEGAMON II session.

Installers can allow you to assign screen spaces or INFO-line commands to up to 99 PF keys with the .PFK immediate command. PF keys 1–24 are available via the physical keys if your terminal has them. You can access 99 logical PF keys by typing the PF key number on the INFO-line.

You can redefine several PF keys at once without having to re-enter the .PFK command.

1. Beginning in column 1, type:E.PFK

and press Enter. OMEGAMON II gives you an extended display of all current PF key assignments, and inserts .PFK before each key number as shown:

.PFK+ 01=#01 /* EXCEPTION ANALYSIS, GENERAL INFO+ 02=#02 /* ANALYZE ONE IMS REGION+ 03=#03 /* ANALYZE ALL DEPENDENT REGIONS+ 04=#04 /* PROGRAM SPECIFICATION BLOCKS+ 05=#05 /* DATABASE MANAGEMENT BLOCKS+ 06=#06 /* TRANSACTIONS+ 07=#07 /* LOGICAL TERMINALS+ 08=#08 /* SCHEDULING CLASSES+ 09=#09 /* DEVICE STATISTICS (DASD TAPE)+ 10=ZNOSEFI /* SELF EDUCATION FACILITY REPLACED+ 11=#11 /* NO ASSIGNMENT YET+ 12=ZSWITCH /* COMMAND MODE/MENU MODE TOGGLE+ 13=#13 /* IMS INITIALIZATION PARAMETERS+ 14=#14 /* IMS DATASETS STATISTICS+ 15=#15 /* REAL, VIRTUAL MEMORY UTILIZATION+ 16=#16 /* IMS POOL STATISTICS+ 17=#17 /* DATABASE BUFFER POOL STATISTICS+ 18=#18 /* DUMPING IMS CONTROL BLOCKS+ 19=/U /* SCROLL UP+ 20=/D /* SCROLL DOWN+ 21=/P /* PRINT THE CURRENT SCREEN

.PFK19=/DEF ON /* Turns definition mode on .PFK20=/DEF OFF /* Turns definition mode off

+.PFK21=/P /* PRINT CURRENT SCREEN

Screen Control


2. For each new assignment, blank out the plus sign (+) in front of .PFK and type the new assignment following the equal sign. When you press Enter, the assignments take effect for the duration of the session.

Displaying continuation lines of command outputSome major commands select a series of items. Often, the display output does not fit on one line. When this is the case, the major command displays only the first line of output, and a plus sign appears at the right of the line to indicate that more data is available.

If you want to see a count of the number of items that a major command will select, enter a pound sign (#) in column 1 before the command. The following example shows that there are 20 online disks for the DISK command to display:

#DISK 20

Continuing major command output

You can use a number of different continuation characters and commands to control the output display.

n Enter a less-than sign (<) in column 1 in front of a major command to generate all the output at once when it executes.

n After you issue a major command for the first time, you can put a number in column 1 to specify how many lines of the display to skip.

n You can repeat a major command to display only the next line of output.

Continuing major and minor command output

When a major command lists a series of items that continues for more than one line, any minor command you enter after the major applies only to the last line of output. Therefore, if you enter a minor command after the third line of major command output, that minor command only generates information about the third line of items listed by the major. Normally, the major and minor commands must be repeated once for each line of available output.

The .RC command is a shortcut to this process. .RC automatically repeats the major and the minor until all available lines of data are displayed. Enter the

<DISK VMXA04 VMXA05 VMSP50 VMHP02 OMONVM DOSTST DP215R DOSRES + CPM023 DBRCPROD DLSPROD IRLMPROD MPP01 MPP02

Command Basics 133

Screen Control

major command once, followed by the minor command(s), and then .RC below the minor(s). An example of the output is shown below.

Delaying automatic updatingThe delay and hold features temporarily defer updating when you are in dedicated mode or in VTAM mode with automatic updating in effect (see the .AUP command).

Delay feature

While OMEGAMON II is automatically updating, you can continue to enter commands. If OMEGAMON II detects a cursor movement since the last update, it defers processing to avoid executing half-entered input. The words “I/O Delay” appear on the INFO-line, and the screen does not update for the number of cycles specified with the IODELAY keyword of the .SET command.

Hold feature

If your screen display contains data that you want to study for longer than the normal automatic update interval, you can use the hold feature to temporarily freeze the screen image. To do this, home the cursor, then move it back one space to the blank space in column 1 of the INFO-line. The words “Hold Mode” display on the INFO-line, and the information on the screen does not change until you move the cursor away from row 1, column 1.

DISK VMXA04 VMXA05 VMSP50 VMHP02 OMONVM DOSTST DP215R DOSRES + dadr 1A0 1A1 1B0 1B1 2A7 2B0 4F1 4F2 dio 4157 4240 3975 4010 4422 272 1638 1147 DISK PPSMPE TSO024 QM0001 OMON25 MTBLI3 DB2002 PPSMPE TSO042 + dadr 148 149 14A 14B 14C 14D 14E 14F dio 6157 40885 3325 4115 277 1122 44322 48995 DISK CPM023 DBRCPROD DLSPROD IRLMPROD MPP01 MPP02 dadr 4F3 4F4 4F5 4F6 4F7 4F8 dio 3284 2140 3287 3967 298 275 .RC

Screen Logging


Screen Logging

IntroductionOMEGAMON II’s logging facility lets you print screen spaces, output appearing on the logical screen, or selected lines from the screen. When the log is on, a copy of every screen display is written to the log. The OUTP major command sets the characteristics of the REPORT file.

OMEGAMON II can log exception analysis screens automatically with the exception logging facility (XLF).

Activating the logTo turn on the log, enter the OPTN immediate command in the input area of the main body of the screen. Two columns of session options appear as shown in the following figure:

FIGURE 47. Session Options

The current status of the log (ON or OFF) displays after the LOG= entry. To initiate logging, type ON over the OFF entry. The word LOG displays on the INFO-line when the log is activated.

When the log is on, OMEGAMON II logs the screen output on each cycle. If you freeze the screen with the hold feature during automatic updating, OMEGAMON II logs only once until you move the cursor from row 1, column 1.

To force printing of the log, enter the /LOGOUT INFO-line command or the .LOGOUT immediate command. This command closes the current log file and dynamically reallocates it so that it is immediately reopened. If you have set new parameters for the log file, you must issue a LOGOUT command for the new parameters to take effect.

To turn off the log, re-enter the OPTN command and type LOG=OFF over the LOG=ON entry. The word LOG disappears from the INFO-line.

_______________ KOIMENU VTM DBCTL /C I51C 01/02/97 12:00 OPTN: ASF = OFF BELL = OFF: BELLINT = 60.00 DATEFORMAT = USA: FIRSTSCREEN = KOINITZZ LOG = OFF: MINORCASE = LOWER SCREENCASE = MIX: SCROLL = PAGE TSF = OFF: XLF = OFF ZEROES = OFF

Command Basics 135

Screen Logging

Checking the page limitThe OMEGAMON II profile in effect at your site contains a default limit on the number of pages that are printed before the log stops. The PAGELIMIT= keyword of the .SET immediate command controls the page limit.

Before the log begins to print, .SET displays the current default page limit. To change the limit for your session enter .SET and type a new value over the old one, after the PAGELIMIT= keyword.

During printing, the number that .SET displays decreases to reflect the number of pages left to print before the limit is reached. You can check the log’s progress by entering .SET while logging. When the page limit display reaches zero, the screen space clears and a message appears to inform you that the page limit was reached.

Press Enter to restore the screen display.

Logging a single displayTo print a single screen image without turning the log on, use the /PRINT (or /P) INFO-line command.

The PAGELIMIT= keyword does not affect the /P command. /P continues to work even when the counter is at zero.

Logging part of a displayTo print selected lines from a screen space, use the .PRT command.

In this example, OMEGAMON II logs one copy of the lines above the .PRT command, and then changes the command to a comment (>.PRT). To log these lines continually, add the H (Hold) argument to .PRT (.PRTH).

This prevents OMEGAMON II from changing the command to a comment.

DISK CPM023 DBRCPROD DLSPROD IRLMPROD MPP01 MPP02 dadr 4F3 4F4 4F5 4F6 4F7 4F8 >.PRT >> Screen Printed up to this line << dalc 8 16 6 12 24 16 32 8

Screen Logging


Screen Spaces 137

Screen Spaces

Chapter overviewThrough its powerful screen space feature, OMEGAMON II can store, recall, and invoke a set of commands. Candle ships OMEGAMON II with a number of predefined screen spaces, which Candle has designed to give you detailed information by category.

Chapter contentsInvoking Screen Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Creating or Modifying Screen Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Listing Screen Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Renaming a Screen Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Deleting a Screen Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Invoking Screen Spaces Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . 144

10

Invoking Screen Spaces


Invoking Screen Spaces

IntroductionYou can invoke a Candle-defined screen space by selecting a menu option, or by pressing certain PF keys, (if you are working in the command interface). You can also create custom screen spaces and recall them by typing the screen space name on the INFO-line, or by assigning the screen space name to a PF key.

When you invoke a screen space, its commands replace the commands currently on the screen. The commands then execute in the same way as they would if you entered them individually. You must set up screen spaces in advance of an OMEGAMON II session in order to use OMEGAMON II’s automatic screen facility, the timed screen facility, and the zooming feature.

Screen Spaces 139

Creating or Modifying Screen Spaces


IntroductionYou can create a screen space at any time on any screen by simply typing in a group of commands, assigning a name to them, and saving them. Note the following points about creating screen spaces.

n Include separator lines in screen spaces you create to make the screen more readable. OMEGAMON II automatically draws a separator line across the screen for you with the ==== immediate command. The format of this command is c====aa. The variable c allows you to specify the color, if you have extended color on your terminal. The variable aa allows you to specify the characters you want to use for the line.

n Use comment lines, wherever appropriate, to explain the commands. Begin all lines of comment text with a greater-than sign (>) in column 1.

n Use the definition mode (described later in this section) while you design the screen if you are including any commands that comment themselves out after execution. This prevents the comment character (>) from appearing in column 1 when you save the screen.

n You cannot include INFO-line commands as part of a screen space. Instead, use the equivalent immediate command.

OMEGAMON II does not save blank lines at the bottom of a screen space.

n Use the /REP or /SAVE commands if you want to save the cursor in a particular position on the screen. The default cursor position is the first position of the INFO-line.

To save the cursor in another position, type /REP or /SAVE on the INFO-line, move the cursor to the desired position, and then press Enter to execute the command. The cursor then appears in that position whenever OMEGAMON II invokes the screen.

n Use a standard text editor to create or alter screen spaces. When you use a text editor to view or edit a screen, keep the following points in mind:

– The INFO-line displays CURS=(n,m) if you place the cursor in any position except the default position. The variable n is the cursor row position, and m is the column position.

– You can add or change the cursor position in a saved screen by adding or changing CURS=(n,m).



The following figure shows a screen created for a screen space named SAMPLE. Notice the command explanations in the divider lines.

FIGURE 48. Typical User-Created Screen Space

OMEGAMON II accepts variable symbols as arguments for commands. The .VAR immediate command allows you to set variable symbols for use in designing screen spaces. You can define the variables at OMEGAMON II startup or at any other time during your session. For more information on using variables, see the discussion in “Setting and Using Variables” on page 149.

To create or modify a screen space, follow this procedure.

1. Use definition mode to inhibit updating and prevent OMEGAMON II from executing the commands you have entered.If you are creating a single screen space, enter the .DEFON immediate command or the /DEFON INFO-line command to place OMEGAMON II in definition mode.

If you are creating several screen spaces at once, use /DEF HOLD or .DEFHO to preserve definition mode until you issue a /DEFOFF or .DEFOFF command. Otherwise, saving the screen space automatically turns off definition mode.

2. Enter the desired commands on the screen.

3. Use the /SAVE INFO-line command to save the screen.To replace an existing screen space with a new screen space of the same name, use the /REP command. See the OMEGAMON II for DBCTL Realtime Commands Reference Manual for the format of /SAVE and /REP.

4. Use .DEFOFF or /DEFOFF to restore automatic updating if you turned on definition mode with the HOLD option in step 1.

_______________ SAMPLE VTM DBCTL /C I51C 01/02/97 12:00 >================= DISPLAY GENERAL IMS INFORMATION ========================== > ISYS > >================= DISPLAY OVERVIEW MVS INFORMATION ========================== > MSYS > >================= DISPLAY EXCEPTIONAL CONDITIONS ========================== > LXIMS > >================= DISPLAY PROGRAM ISOLATION CONFLICTS ====================== > XPIQ

>

Screen Spaces 141

Listing Screen Spaces

Listing Screen Spaces

IntroductionThe .SCRN immediate command, used without an argument, lists all screen spaces in main storage and in the disk datasets that the RKOIPCSV and RKOIPCSV ddnames point to. You can limit the list by using arguments to request a list of screens in main storage only, disk only, or both. You can also specify alphabetic limits for a range of member names, and use wildcard characters. See the OMEGAMON II for DBCTL Realtime Commands Reference Manual for details.

The following figure shows a typical default screen space listing. OMEGAMON II sorts the list by dataset, with in-storage screens first, followed by RKOIPCSV, then each dataset in the RKOIPCSV concatenation.

FIGURE 49. Screen Space List

>SCRNB $ thru 99999999> In-storage screen facility 20 members 4232 bytes used> $ #01 #02 #03 DEBUG DEBUG01 DEBUG02 DEBUG03 ...> RKOIPCSV TDIMS1.I2510SMP.R1.I51C.RKOIPCSV> #01 SAMPLE VSAM> RKOIPCSV (DUP.) TDIMS1.I2510SMP.R1.I51C.RKOIPCSV> RKOIPCSV +01 TDIMS1.I2510SMP.R1.I51C.RKOIPCSV> #01 #07 #08 #09 #10 #13 #14 #15> #16 #17 #18 #19 #20 #21 #22 #23> #24 BITMAP CPAM CSA DD DDACVOPS DDBASIC DDDEX> DDEXCEPT DDIO DDNAMES DDNEWS DDOMEGA DDOPER DDPFK DDSYS> DDSYSE DDSYSI DDTASK DEBUG DEBUG01 DEBUG02 DEBUG03 DEBUG04> DEXALL DEXAL2 DEXAL3 DEXAL4 DEXAL5 DEXAN DEXDFLT DEXDF2> DSA ENQUEUES EOD HELP HELP2 INTERVAL OIINIT00 PAM> SCREEN SCREENS SIT SLOT SLOTS STOP STOPC STOPI

Renaming a Screen Space


Renaming a Screen Space

IntroductionUse the RENM immediate command to rename a screen space. The RENM command accepts an argument specifying where to find the screen space.

To rename the SAMPLE screen space to EXAMPLE in both main storage and RKOIPCSV, enter:

RENMB SAMPLE EXAMPLE

The following message displays:

>> Member “SAMPLE” Renamed to “EXAMPLE” Both In-Storage and in RKOIPCSV <<

The screen space SAMPLE no longer exists.

Screen Spaces 143

Deleting a Screen Space

Deleting a Screen Space

IntroductionUse the DELT immediate command to delete screen spaces. OMEGAMON II deletes screen spaces only from main storage and the dataset that the RKOIPCSV ddname points to, not from RKOIPCSV, the read-only dataset. The DELT command accepts an argument specifying where to find the screen space.

If you want to delete the screen space SAMPLE from both main storage and RKOIPCSV, enter:

DELTB SAMPLE

The following message displays:

> >> Member “SAMPLE “ Deleted Both In-Storage and from RKOIPCSV <<

Invoking Screen Spaces Automatically



IntroductionOMEGAMON II offers the capability of chaining together a group of screen spaces, so that an entire series of screens can execute without operator intervention.

An .SGO or .FGO immediate command, entered in a predefined screen space, fetches the next screen automatically. The .FGO (fast go) and .SGO (screen go) commands perform identical functions, but .SGO displays the screens as they execute, whereas .FGO bypasses the OMEGAMON II cycle and the terminal display.

The screen space fetch feature is particularly useful when using OMEGAMON II’s Automatic Screen Facility (ASF) or Timed Screen Facility (TSF). ASF allows your system to react automatically to problem conditions that occur in the system. It can invoke predefined screen spaces containing commands that investigate the problem condition in detail and then log the output. TSF lets you schedule monitoring of tasks at regular intervals.

See the OMEGAMON II for DBCTL Realtime Commands Reference Manual for an explanation of how to set up ASF and TSF.

Conditional screen space fetchingThe .FGO and .SGO commands give you the flexibility of conditional screen space fetching. You can enter an argument, which may include relational operators, to fetch a screen space only if certain conditions are true. You can use relational operators to compare the CPU serial number, the mode of operation, the operating system level, the profile in use, the SMF ID, the OMEGAMON II console address, or any variable you have set with the .VAR command.

For example, to specify that you want to fetch screen space SAMPLE only if you are running in an ESA 3.1 environment, enter:

.SGO SAMPLE OPSYS=310

Delayed screen space fetchingThe .SGO command lets you delay the fetching of a screen space for a specified number of OMEGAMON II cycles. This allows you to accommodate commands that take more than one cycle to initialize (gather data). It also permits you to log several successive executions of a given screen space before moving on to the next screen space. A label in front of .SGO specifies the delay.

n.SGO screenname

The variable n can be a number representing a delay of 1–9 cycles or a letter from A–Z representing a delay of 10–35 cycles.

Screen Spaces 145


Looping screen spacesAn improper sequence of .FGO screens could cause a looping condition. To protect against this possibility, OMEGAMON II limits the number of consecutive fetches allowed (64 by default). After reaching this limit, .FGO acts like .SGO so that executing screen spaces display on each cycle. Once .FGO screen spaces cause a loop, you need to correct the condition and re-enable .FGO.

To re-enable .FGO, use the FGOLOOP keyword of the .SET command The FGOLOOP keyword is set to OFF until the limit of consecutive fetches is reached. At that point OMEGAMON II sets FGOLOOP to ON, indicating the probability of a loop. To reset .FGO, issue the .SET command and replace the ON argument with OFF.

Testing .FGO routinesBecause FGOLOOP=ON causes .FGO not to bypass the OMEGAMON II cycle and the terminal display, you may want to turn it on yourself to test your screen space fetch routines.

Manipulating the log within screen spacesTo log screen spaces selectively, the .LOG immediate command has PUSH and POP arguments. You can include these arguments in screen spaces to change the ON or OFF status of the log when you branch to other screen spaces, and then return the log to its original state after the screen routines complete.

For example, if you have a series of four screen spaces chained together with .FGO and you want to log only the last two, you can use .LOGPUSH and .LOGPOP in the following manner:

1. At the end of screen space 2, enter .LOGPUSH to have OMEGAMON II record the previous status of the log.

2. Enter OPTN LOG=ON to turn on the log at the beginning of screen space 3.

3. Enter .LOGPOP at the end of screen space 4.This causes the log to be restored to its original status when your branching routine is complete.

The .LOGPUSH and .LOGPOP functions are performed automatically when you log screen spaces using the Exception Logging Facility (XLF), the Automatic Screen Facility (ASF), or the Timed Screen Facility (TSF).



Advanced Commands and Features 147

Advanced Commands and Features

Chapter overviewThis chapter highlights some of OMEGAMON II’s operational features not covered in earlier chapters:

n rate and difference command argumentsn variable substitutionn the zooming featuren secondary dedicated terminalsIf you have operated OMEGAMON II through the menu system, you have already used zooming and variable substitution. This chapter shows you how you can also take advantage of these features in customizing your own sessions.

Chapter contentsRate and Difference Command Arguments. . . . . . . . . . . . . . . . . . . . . . . 148Setting and Using Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149The Zooming Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Secondary Console Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

11

Rate and Difference Command Arguments


Rate and Difference Command Arguments

IntroductionFor minor commands that normally display numeric values, you can use arguments to change the output to a rate or to a difference between OMEGAMON II intervals. You enter rate or difference arguments in columns 6 and 7 after the command. The rate and difference command arguments are:

The following figure illustrates the use of the .R argument.

The RGNA major command selects all regions for display, and the JPUI minor command displays the number of private area page-ins. When the .R argument is entered after the JPUI command, OMEGAMON II displays a rate of 4 page-ins per second for the region TDO310A.

OMEGAMON II requires data from two cycles to calculate a rate or a difference. On the first cycle (the initialization cycle), a row of eight periods (........) appears, indicating that the rate will appear on the next cycle. The rate and difference arguments are not effective in the following cases:

n If a major command selects different items from cycle to cycle. For example, the DSKB major command may select different busy disks at each screen update. When you use a rate argument with a minor of DSKB, the periods may appear after each update, indicating that OMEGAMON II is initializing each time.

n If a command displays a value that has been reset to zero by the system between OMEGAMON II intervals.

For commands that normally display time values (e.g., CPU time), any rate calculated represents a scaled percentage of utilization (expressed as a decimal value), where the real time of the interval equals 100%.

.S or .R Displays the output as a rate per second.

.M Displays the output as a rate per minute.

.H Displays the output as a rate per hour.

.D Displays the output as a difference between the two most recent values of the parameter (that is, between OMEGAMON II cycles).

RGNA BMPRGN01 BMPRGN02 BMPRGN03 BMPRGN04 BMPRGN05 BMPRGN06 BMPRGN07 jpui 921 134 258 179 69 1074 50 jpui.R .4


Setting and Using Variables


IntroductionThe .VAR immediate command lets you use variables in building OMEGAMON II screen spaces. With this capability, you can exploit the powers of various other OMEGAMON II features. For example:

n Build generic screen spaces that pick up values and analyze any number of like items, such as devices. OMEGAMON II’s zooming feature uses this capability.

n Set up conditional branches to other screen spaces (using .FGO) based on relationships of variable values.

n Pick up values in screen spaces designed for OMEGAMON II’s automating and logging features: XLF, ASF, and TSF.

OMEGAMON II lets you use variables in several ways.

n You can define your own variables with .VAR. For example:

.VAR SET &NXTSCRN MONITOR

.VAR SET &DEVICE 123

n You can use .VAR with relational operators to set a variable equal to a value under the condition specified. For example, you can specify that a variable be resolved only if a device address is greater than 150.

n You can use variables that are internally defined by OMEGAMON II at initialization. They are:

– &ZFRSTSS - first screen space name

– Zoom command variables (see /ZOOM)

– Exception variables (cccc is the exception name):

n You can use the following keywords for conditional setting of variables. OMEGAMON II initializes their values.

&ZXccccT Threshold value

&ZXccccV Last trip value

&ZXccccW Worst trip value

CPSER The CPU serial number.

DIR The ID assigned to the director in cross system mode.

MODE The mode of operation for OMEGAMON II.

OPSYS The operating system level.

PREFIX The OMEGAMON II product code.



For example, to pass values to screen spaces with .SGO, enter the following commands:

.VAR SET &NXTSCRN MONITOR

.VAR SET &DEVICE 123

This sets values for NXTSCRN and DEVICE. You can now use those variables in a screen space:

DEV &DEVICE

DIO

.SGO &NXTSCRN

OMEGAMON II interprets the screen space entries as if you had entered the following:

DEV 123

DIO

.SGO MONITOR

You can also set variables conditionally. In the following example, the variable SYSTEM is set to A if the variable SWITCH has previously been set to YES; SYSTEM is set to B if SWITCH has previously been set to NO; and SYSTEM is set to C if SWITCH has previously been set to MAYBE.

C.VAR SET &SYSTEM A &SWITCH=YES

C.VAR SET &SYSTEM B &SWITCH=NO

C.VAR SET &SYSTEM C &SWITCH=MAYBE

In the following example, the variable TOKEN is set to IMS only if the product prefix is OI:

C.VAR SET &TOKEN IMS PREFIX=OI

IMSID The system ID from the SYS= startup parameter.

UNIT The device number from the UNIT= startup parameter.

USER The profile suffix from the USER= startup parameter.

&var A variable. Allows you to set any comparison you want.


The Zooming Feature

The Zooming Feature

IntroductionCandle has designed the zooming feature to simplify the investigation of system conditions, by supplying a detailed level of information at the touch of the Zoom key. The /ZOOM command substitutes whatever value the cursor is on for a variable contained in a predefined screen space. Candle Corporation ships OMEGAMON II with the /ZOOM INFO-line command assigned to PF11.

You can use zooming to perform the same operation on a series of items. By using the cursor as a pointer and pressing the Zoom key, you can get a detailed analysis of any device, volume serial number, or address space.

OMEGAMON II’s menu system uses the zooming feature extensively. For example, when you are looking at a display of databases, you can place your cursor on a database name and press PF11. OMEGAMON II zooms to a panel that gives detailed information about that database.

In the menu system, when there are fields on a display that respond to the Zoom key, such as exception names or device names, Zoom PF11 is shown under the INFO-line as a navigation option.

You can use zooming in the command interface by setting up customized investigative screen spaces and zooming on command or exception names. For example, a systems programmer might want to set up a screen space to monitor an intermittent performance problem. The screen space can include commands that give specific information about the problem area, as well as a command to turn on the log. When the problem recurs, an operator can zoom to the screen space. OMEGAMON II executes the screen and logs the information for the programmer to examine later.

For a more thorough discussion of the zooming feature, see the /ZOOM INFO-line command in the OMEGAMON II for DBCTL Realtime Commands Reference Manual.

Note the following guidelines when setting up screen spaces for use with the /ZOOM command.

n The screen space name must start with a four-character prefix that begins with an alpha or national character (@ZOM is the default) and is followed by the command or exception name (@ZOMcccc).

n When creating your own zooming screen spaces, you can name them with your own prefix (aaaa) instead of @ZOM. To invoke a zooming screen space that has your aaaa prefix, do one of the following:

________________ KOISYS VTM DBCTL /C I51C 01/02/97 12:00> Help PF1 Back PF3 Up PF7 Down PF8 Zoom PF11================================================================================

The Zooming Feature


– Type /ZOOM aaaa on the INFO-line, move the cursor to the data, and press ENTER.

– Type aaaa on the INFO-line, move the cursor to the data, and press the Zoom key.

– Redefine the Zoom key, PF11, or assign another PF key to /ZOOM aaaa, move the cursor to the data, and press the Zoom key.


Secondary Console Control


IntroductionIf you run OMEGAMON II in dedicated mode, you can set up a secondary console for output display only. The secondary console is a repeater console; it echoes everything that appears on the primary console, but accepts no input of any kind.

To use a secondary console, first define the unit, and then open it up for OMEGAMON II output display. To define the console, enter the .CNxxx immediate command, where xxx is the hexadecimal address of the secondary console. Then, enter .CN OP to open the console for OMEGAMON II output display. The secondary console, like the dedicated console, must be a non-SNA local device.

To close a secondary console, enter the .CN CL command. You can also enter the .CN SW command to switch the primary and secondary console functions.



155

Part III: Problem-Solving Scenarios

Part III provides example scenarios to show you how you can use OMEGAMON II to resolve specific performance problems in your DBCTL system.

In the section, references to OMEGAMON II signify the OMEGAMON II CUA interface, unless the text specifically indicates otherwise.


Resolving a Response Time Problem 157

Resolving a Response Time Problem

Chapter overviewThis chapter explains how to use the bottleneck analysis technique to investigate a database I/O problem.

Chapter contentsBackground . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Creating a PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Activating the Bottleneck Analysis Collector . . . . . . . . . . . . . . . . . . . . . . 163Displaying Bottleneck Summary Information for PSB Groups. . . . . . . . . 165Viewing Bottleneck Analysis Details for a Specific PSB Group . . . . . . . . 167Identifying DASD Problems with a Database . . . . . . . . . . . . . . . . . . . . . 169

12

Background


Background

IntroductionBottleneck analysis (DEXAN) is a Candle-developed technique that focuses on the analysis of workloads rather than resources. Bottleneck analysis breaks the execution time of workloads into its component parts, allowing performance analysis on the areas most significant to IMS system performance.

The OMEGAMON II interface attaches the bottleneck analysis collector as an MVS subtask. The collector allocates the data areas and begins observing PSBs that IMS has scheduled in your system. At user-defined intervals, the collector samples the execution states of all scheduled PSBs and records the data it collects in virtual storage. Bottleneck analysis uses samples to calculate the percentage of time an average PSB spends in each of the execution state groups that the collector monitors.

An execution state is what a PSB (thread) is doing or why a thread is waiting. Typical execution states are “Using CPU in IMS”, “Waiting for CPU”, and “IRLM Conflict Wait”. Bottleneck analysis organizes execution states into four groups:

n CPU Usage

n Database I/O Waits

n MVS Waits

n IMS Waits

The virtual storage area that records the data the collector gathers consists of two parts: the short-term area and the long-term area, corresponding to the user-defined short and long-term sampling intervals. At these user-defined intervals, the collector “throws away” the data it has collected and starts fresh by zeroing the collector counters. This prevents bottleneck analysis from averaging data, that ceases to be of interest to a user of a realtime monitor, over a long period of time. The collector also clears the collector counters when you enter a new user-defined interval.

Note: All OMEGAMON II users monitoring the same IMS will share the same sampling interval.


Scenario

Scenario

IntroductionYour company provides an online credit checking service for retail outlets. For the past several days, you have received numerous complaints from customers that your credit checks are taking too long to complete. Your customers are threatening to take their business elsewhere unless you eliminate the delays.

This is a recurrent and increasingly frequent problem. The Chief Information Officer (CIO) asks the database analyst (DBA) to look into the problem. The DBA knows which PSBs execute the credit check application (PCRCHCK1, PCRCHCK2, PCRCHCK3) and suspects that the problem is IMS database I/O delays.

To confirm his suspicion, the DBA asks you, the senior systems programmer, to create a PSB group, adding the credit check application PSBs to this group, and then use bottleneck analysis to investigate the problem.

Creating a PSB Group



IntroductionCreating a PSB group includes:

n Navigating to the command/menu interfacen Using the SETG commands to create the groupn Adding PSBs to the group

To access or zoom to the OMEGAMON II command/menu interface from the System Overview panel:

1. Select Cmd/Menu Interface (OMEGAMON) from the GoTo pull-down.The Zoom to OMEGAMON pop-up displays.

2. To zoom to the menu interface, make sure that OMEGAMON screen space is blank, and press Enter.The Main Menu displays as shown in the following figure.

FIGURE 50. Main Menu

3. Type ..bb starting in column 2 under the INFO-line to clear the screen.

4. To create a PSB group and add PSBs PCRCHCK1, PCRCHCK2, and PCRCHCK3 to the group, type LSETG99 in column 2 under the INFO-line and press Enter.OMEGAMON II displays a list of all defined PSB groups, as shown in Figure 51 on page 161.

________________ KOIMENU VTM DBCTL /C I51C 01/02/97 12:00> Help/News PF1 Exit PF3 Keys PF5 Command Mode PF12 Colors PF>Return to CUA PA2> Enter a selection letter on the top line.========================================================================> OMEGAMON for DBCTL Performance Monitor Main Menu _ E EXCEPTIONS ....... Current and potential system problems, latch conflicts_ R RESPONSE TIME .... Response time information (RTA users)_ B BOTTLENECKS .... Resource contention (bottleneck analysis) (DEXAN users)_ M MONITOR .......... IMS status, graphs, and time controlled operations>_ W WORKLOAD ......... PSBs, DMBs, transmission, regions, and CUAs_ A ALL POOLS ........ Communication, database, and program tools_ C COMPONENTS ....... I/O, logging, storage, and control blocks/module _ F FAST PATH ........ IMS Fast Path information_ O OTHER SYSTEMS .... DB2 interface and XRF information _ T TOOLS ............ Operator tools_ P PROFILE .......... Profile maintenance and session settings



FIGURE 51. List of PSB Groups - Before Create

In this example groups #1 - #5 are existing PSB groups. You will need to use a new group number for the PSB group you are creating.

5. To create your new PSB group, typeCSETG6 PSB=PCRCHCK1,PCRCHCK2,PCRCHCK3

in column 2 under the INFO-line and press Enter.

OMEGAMON II displays a message telling you that OMEGAMON has created the PSB group and displays the names of all PSBs in the PSB group, as shown in the following figure.

FIGURE 52. Created PSB Group

6. To verify the addition of the PSB group, clear the screen, type LSETG99, and press Enter.OMEGAMON II displays a list of all defined PSB groups, as shown in the following figure. You will see your PSB group in the list.

FIGURE 53. List of PSB Groups - After Create

______________KOIMENU VTM DBCTL /C I51C 01/02/97 12:00======================================================================= LSETG99 + Group #1 (Name=CLASS 1 ) + Class=1 + Group #2 (Name=CLASS2 ) + Class=2 + Group #3 (Name=GROUP 03) + Class=3 + Group #4 (Name=GROUP 04) + Class=4 + Group #5 (Name=GROUP 05)

+ lass 5

______________KOIMENU VTM DBCTL /C I51C 01/02/97 12:00======================================================================= CSETG6 PSB=PCRCHCK1, PCRCHCK2, PCRCHCK3 + PSB=PCRCHCK1, PCRCHCK2, PCRCHCK3

______________KOIMENU VTM DBCTL /C I51C 01/02/97 12:00======================================================================= LSETG99 + Group #1 (Name=CLASS 1 ) + Class=1 + Group #2 (Name=CLASS2 ) + Class=2 + Group #3 (Name=GROUP 03) + Class=3 + Group #4 (Name=GROUP 04) + Class=4 + Group #5 (Name=GROUP 05) + Class=5 + Group #6 (Name=Group 06)

PSB=PCRCHCK1 PCRCHCK2 PCRCHCK3



7. Press PF15 to return to the System Overview panel.

Now that you have created a PSB group, continue with the procedure “Activating the Bottleneck Analysis Collector” on page 163 to use bottleneck analysis.


Activating the Bottleneck Analysis Collector


IntroductionBefore you can use your new PSB group, you must recycle the bottleneck analysis collector. Check the Bottleneck light on the System Overview panel.

FIGURE 54. Inactive Bottleneck Status Light

In this case, the Bottleneck light is turquoise indicating the collector is not active.

To activate the bottleneck analysis collector:

1. Select Bottleneck Analysis Options from the Options pull-down menu.OMEGAMON II displays a pop-up showing the current bottleneck analysis options, as shown in Figure 55 on page 164.

___ Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 System Overview IMS: 151C ___ + Select a component with “S” to show details+-----------------------------------------------------------------------------+| Status | Alerts ||--------------------------------------+--------------------------------------|| _ Regions ----- _ XRF ----- | _ Pools ----- _ Conflicts ----- || | || _ IMS Status ----- _ ESS ----- | _ Threads ----- _ Databases ----- || | || _ Bottleneck ..... _ Traces ===== | _ Logging ----- _ Fast Path ----- || | || _ Buf. Pools ----- | _ Programs ----- || | || _ I/O ----- | ||-----------------------------------------------------------------------------|| Operator Assist ||-----------------------------------------------------------------------------|| _ Databases _ Regions _ Programs _ Logging |+-----------------------------------------------------------------------------+



FIGURE 55. Bottleneck Analysis Options Pop-up

The Bottleneck Analysis Options panel shows that the collector is set to Off.

2. Place the cursor on the word “Off “next to Bottleneck Analysis Collector, type On, and press Enter.You can modify all other options on this panel. OMEGAMON II displays the information on this panel from the IDEG major and its associate minor commands.

3. Press F3 to return to the System Overview panel.

The Bottleneck light is now green, indicating that the collector is active.

Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 System Overview IMS: 151C ___ + +---------------------------------------------------------------+ Select a com | Bottleneck Analysis Options |+------------ | || | Enter Bottleneck Analysis collector options. ||------------ | To process changes, press ENTER. || _ Regions | To process changes and exit, press F3. || | || _ IMS Statu | _ Bottleneck Analysis Collector . . . . . . Off + On/Off || | _ Exclude BMPs . . . . . . . . . . . . . . . Off + On/Off || _ Bottlenec | _ Accumulate information by database name . On + On/Off || | _ Clear Long Term Interval every . . . . . . 30 minutes || _ Buf. Pool | _ Clear Short Term Interval every . . . . . 5 minutes || | _ Sampling interval . . . . . . . . . . . . 5 tenths-sec || _ I/O | _ Supress States . . . . . . . . . . . . . < 0 % ||------------ | || | Select a control option with a ‘/’ and press ENTER. ||------------ | || Databases | _ Suspend Sampling. |+------------ | _ Resume Sampling. | | _ Clear short and long term counters. | | | | Enter F1=Help F3=Exit F4=Prompt F12=Cancel | +---------------------------------------------------------------+


Displaying Bottleneck Summary Information for PSB Groups


IntroductionTo view a summary of your system’s execution states, place the cursor next to the Bottleneck status light on the System Overview panel, and press Enter.

OMEGAMON II displays a panel similar to the one in the following figure.

FIGURE 56. Bottlenecks Summary Panel

This panel displays a list of the PSB groups that are defined to OMEGAMON, plus the “All System” group, and provides a summary of bottleneck analysis information for each PSB group. The highest long and short-term percentages and the execution state group displays for each PSB group. OMEGAMON II displays the percentages and execution state groups from the PDEX command.

When your system is running smoothly, look at the summary information for all PSB groups with the I/O Waits execution state. Notice that the percentage values for highest long and short-term intervals are low when the system is running well.

You continue monitoring the system, checking the Bottlenecks Summary panel periodically. When you check the Bottlenecks Summary panel at 2:30 p.m., you notice that the highest short and long-term percentages for PSB group GROUP 06 are much higher, as shown in Figure 57 on page 166.

Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 Bottlenecks Summary IMS: 151C ___ + Lines 1 to 7 of 7+------------------------------------------------------------------------------+| Group | Highest | Execution | Highest | Execution || |Short Term % | State Group |Long Term % | State Group ||---------------+-------------+-----------------+------------+-----------------|| _ All System | 10.7 | I/O Waits | 12.4 | I/O Waits || _ CLASS 1 | 16.5 | I/O Waits | 18.7 | I/O Waits || _ CLASS2 | 15.2 | I/O Waits | 15.2 | I/O Waits || _ GROUP 03 | 17.4 | MVS Waits | 17.7 | I/O Waits || _ GROUP 04 | 29.3 | MVS Waits | 31.9 | MVS Waits || _ GROUP 05 | 17.1 | IMS Waits | 17.4 | IMS Waits || _ GROUP 06 | 23.2 | I/O Waits | 28.6 | IMS Waits |+------------------------------------------------------------------------------+ (Bottlenecks) <Programs> F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd **=Fwd



FIGURE 57. Bottlenecks Summary Panel - High percentages

To see detailed bottleneck analysis information for GROUP 06, follow the procedure in “Viewing Bottleneck Analysis Details for a Specific PSB Group” on page 167.

Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 Bottlenecks Summary IMS: 151C ___ + Lines 1 to 7 of 7+------------------------------------------------------------------------------+| Group | Highest | Execution | Highest | Execution || |Short Term % | State Group |Long Term % | State Group ||---------------+-------------+-----------------+------------+-----------------|| _ All System | 10.7 | I/O Waits | 12.4 | I/O Waits || _ CLASS 1 | 16.5 | I/O Waits | 18.7 | I/O Waits || _ CLASS2 | 15.2 | I/O Waits | 15.2 | I/O Waits || _ GROUP 03 | 39.4 | MVS Waits | 39.2 | MVS Waits || _ GROUP 04 | 29.3 | MVS Waits | 31.9 | IMS Waits || _ GROUP 05 | 17.1 | IMS Waits | 17.4 | IMS Waits || _ GROUP 06 | 72.6 | I/O Waits | 75.1 | MVS Waits |+------------------------------------------------------------------------------+


Viewing Bottleneck Analysis Details for a Specific PSB Group


IntroductionTo display detail bottleneck analysis information for PSB group GROUP 06, place the cursor in the input field next to group GROUP 06, type an S, and press Enter.

OMEGAMON II displays a panel with detailed bottleneck analysis information for that group, as shown in the following figure.

FIGURE 58. Bottleneck Analysis Panel

This panel displays the elapsed time since the collector last cleared the long-term counters, the number of samples taken for the short and long-term data, and the display and sampling intervals. The main body of the panel displays the percentage of time an average PSB in the group spent in each execution state, during both the short and long-term intervals. The execution states for each Wait Reason are the names of each database to which a thread did I/O.

OMEGAMON II displays information on this panel from the IDEG, PDEX, and other IDEG minor commands. The STIM and THRS minor commands provide the collector sampling interval and suppress states setting values. You can modify both of these values on this panel, to limit the scope of the display. Keep in mind that by so doing, you are modifying them for all users accessing this IMS. When you choose to suppress some execution states, the total percentages may not add up to 100%.

Notice the high percentages for the Database I/O Wait wait reason, and in particular for execution states DE3PART and AD7PART. You can see that there is likely a database I/O problem for databases.

GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 Bottlenecks Analysis for Group: GROUP 06 IMS: 151C ___ + +------------------------------------------------------------------------------+| Elapsed time . . . : 12 SEC Samples taken (short) . : 26 || Supress states . . < 0 % Samples taken (long) . : 26 || Sampling interval . . . : 5 tenths-sec |+------------------------------------------------------------------------------+ Lines 1 to 7 of 7+------------------------------------------------------------------------------+| Wait Reason | Short Term % | Long Term % || | % 0------- 50-------100 | % 0------- 50-------100 ||----------------------+---------------------------+---------------------------|| Database I/O Wait | 72.6 |---=========> | 75.1 |--==========> || DI21PART | 16.8 |> | 13.8 |> || DE3PART | 25.1 |--> | 28.0 |--> || AD7PART | 30.7 |---> | 33.3 |---> || IMS Activity | 23.2 |--> | 20.8 |--> || IRLM Conflict Wait | 2.8 |> | 3.2 |> || ISWITCHED to CTL | 20.4 |-> | 17.6 |-> |+------------------------------------------------------------------------------+



Reasons for a database I/O problem include problems with:

n DASD I/O response time

n database buffer pools

n database descriptions

Your investigation is now complete. Refer the bottleneck analysis information you have gathered on the GROUP 06 PSB group to the DBA for isolation and correction.

Note: To investigate DASD I/O problems, continue with the procedure in “Identifying DASD Problems with a Database” on page 169.


Identifying DASD Problems with a Database


IntroductionSuppose you are experiencing poor response time from your online transactions and bottleneck analysis shows a significant amount of database I/O wait time for each transaction. Database I/O wait time could be localized to a single database, or multiple databases may be showing a disproportionate amount of database I/O wait time.

Enhanced I/O analysis provides a way to help you identify non-IMS I/O problems which may be affecting your IMS. With the enhanced I/O analysis statistical information for databases, you can select the Databases light from the OMEGAMON II System Overview panel and see the EXCP rate for each database dataset. By modifying the view of the Database Summary panel, you can limit the view to a single database or even sort the view into a sequence which allows you to identify problem databases more quickly.

Suppose bottleneck analysis indicates that your online transactions are experiencing an exceptionally high database I/O wait for database PAYROLL1. From the Database Summary panel you can see that database PAYROLL1 is experiencing an extremely high EXCP (I/O) rate.

FIGURE 59. Database Summary Panel

From the Database Summary panel, select the PAYROLL1 database. The Device Statistics for Database PAYROLL1 panel displays, as shown in Figure 60 on page 170.

Actions GoTo View Options Help ------------------------------------------------------------- 01/02/97 12:00:00 Database Summary IMS. I51C Lines 1 to 12 of 19+-------------------------------------------------------------------------------+| DBD | DMB | DB Type/ | | EXCP RATE || Name | Status | Access Meth.|DD Name | 0..........50.........100||------------+----------------+-------------+--------+--------------------------|| BA$HDLO0 | /DBR ACTIVE | | | || BC$HDLO0 | /DBD ACTIVE | | | || _ BD$HDMO0 | DMB ACTIVE | HDAM/OSAM |BD$HDMD0| 121.73/s===============>>|| _ BE$HDMO0 | DMB ACTIVE | HIDAM/VSAM |BE$HDMD0| 71.25/s========> || _ BF$HDMO0 | DMB ACTIVE | DEDB |DFSIVD3A| || _ | DMB ACTIVE | DEDB |DVSIVD3B| || BH$HDHO0 | DMB NOT ALLOC | | | || _ BI$HDHO0 | DMB AVAILABLE | HSAM/OSAM |DDBHDH | 25.21/s || _ DBFSAMD1 | DMB ACTIVE | MSDB |DDSAM52 | || _ DBFSAMD2 | DMB AVAILABLE | MSDB |DDSAM53 | || _ DBFSAMD4 | DMB ACTIVE | INDEX/VSAM |DDSAM1 | .87/s || _ PAYROLL1 | DMB ACTIVE | HIDAM/OSAM |PAYROLL1| 127.33/s===============>>|| IVPDB1 | DYN ALLOC ERROR| | | F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd F8=Fwd F10=Action Bar F15=System Overview PA1=Switch P2=OMEGAVIEW



FIGURE 60. Device Statistics Panel

The Device Statistics panel shows the overall response time for the devices allocated for this specific database. The device statistics that display on this panel are not specific to the database, but to all MVS activity relative to the device, including IMS database activity. The device statistics allow you to determine if the DASD volume is having a system-wide performance problem. If so, you may need to work with your DASD administrator to modify the dataset placement on DASD or identify the offending dataset and possibly move it.

If the device statistics for your database do not indicate any specific volume response time problems, you may need to review your database dataset definition. Select the <Database Details> pushbutton, to view specific information which is pertinent to the database and the database dataset. The Details for Database panel displays, as shown in the following figure.

GoTo Options Help ------------------------------------------------------------- 01/02/97 12:00:00 Device Statistics for Database PAYROLL1 I51C +-------------------------------------------------------------------------------+| DDName : PAYROLL1 Average EXCP Rate: .21/s || DSName : IMS.V5R1.PAYROLL1 || Start Time: 14:44:00 Elapsed Time: 6:02 MN Interval Length: 14:59MN |+-------------------------------------------------------------------------------+ Lines 1 to 2 of 2+-------------------------------------------------------------------------------+| | | Volume |Volume|Volume|Volume|Volume| Volume | Vol | Total || Volser | Unit | Response | IOSQ | Pend | Conn | Disc | Queue | Pct | SSCH || | | Time | Time | Time | Time | Time | Length | Busy | Rate ||--------+------+----------+------+------+------+------+--------+------+--------|| PPSMP1 | 04E1 | 9.7 | .0| 1.7| 1.5| 6.3| .00| .0| .0|| PPSMP3 | 04E3 | 6.3 | .0| 2.2| 1.3| 2.8| .00| .0| .0|+-------------------------------------------------------------------------------+ (Device Statistics) <Database Details>



FIGURE 61. OSAM Database Details Panel

Looking at this panel, You may find that you have multiple VSAM extents and need to reorganize your database. You may also find that the control interval size is too small or the wrong buffer pool has been allocated to the dataset. Any of these could cause an increase in DASD I/O and have a detrimental effect on overall IMS performance.

GoTo Options Help ----------------------------------------------------------- 01/02/97 12:00:00 Details for Database : PAYROLL1 I51C +-----------------------------------------------------------------------------+| DD Name: PAYROLL1 Dataset Name: IMS.V5R1.PAYROLL1 |+-----------------------------------------------------------------------------+ +-------------------------------------+---------------------------------------+| Status . . . . . . : Available | Block Size . . . . . . . . : 4096 || | Logical Record Size . . . : 4089 || Type . . . . . . . : HIDAM | || | || Access Method . . . : OSAM |---------------------------------------+| | || Residency . . . . . : RESIDENT | Buffer Subpool . . . . . . : DEFAULT || | Active PSB Count . . . . . : 5 || Recoverability . . : NON-REC | Error Type . . . . . . . . : || | || DMB Address . . . . : 7245840 | DMB Size . . . . . . . . . : 244 |+-------------------------------------+---------------------------------------+ <Device Statistics> (Database Details) F1=Help F2=Keys F3=Exit F5=Refresh F6=Console F10=Action Bar



Analyzing Program Isolation Pool Use 173

Analyzing Program Isolation Pool Use

Chapter overviewThis chapter describes how to solve a typical PI enqueue pool exception.

Chapter contentsBackground . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Viewing PI Enqueue Pool Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Restarting a PSB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Detecting a PI Enqueue Pool Lockout . . . . . . . . . . . . . . . . . . . . . . . . . . 181

13

Background


Background

IntroductionA PCB (Program Communication Block) might require read-only, update, or exclusive access to a database. Because more than one PSB can access the same database, IMS must serialize the database (enqueued and dequeued) by some locking mechanism such as Program Isolation locking (PI-locking).

PI-locking requires a pool of storage, the PI enqueue pool, to keep track of its serialization. The CORE parameter of the IMSCTF macro specifies the size of the PI enqueue pool at IMS system generation time. Because IMS can extend the pool if more space is needed, the IMSCTF macro specifies an increment and a maximum allocation size. IMS initializes with one increment of space and adds more increments as required until the maximum allocation is reached.


Scenario

Scenario

IntroductionYou receive calls from CICS users that CICS transactions are very slow, are waiting, or are not working. When you check the IMS operator console, you see an IMS abend code of U775 indicating that PSBs have stopped. This, in turn, has caused CICS transactions to stop.

You suspect that the PI enqueue pool has filled up, so that PI-locking cannot serialize database access for CICS transactions.

When you check the System Overview panel, the Pools light is red as shown in the following figure, indicating a tripped exception.

FIGURE 62. System Overview Panel with a Tripped Exception

___ Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 System Overview IMS: 151C ___ + Select a component with “S” to show details+-----------------------------------------------------------------------------+| Status | Alerts ||--------------------------------------+--------------------------------------|.*****************| _ Regions ----- _ XRF ----- | _ Pools +++++ _ Conflicts ----- || | || _ IMS Status ----- _ ESS ----- | _ Threads ----- _ Databases ----- || | || _ Bottleneck ----- _ Traces ===== | _ Logging ----- _ Fast Path ----- || | || _ Buf. Pools ----- | _ Programs ----- || | || _ I/O ----- | ||-----------------------------------------------------------------------------|| Operator Assist ||-----------------------------------------------------------------------------|| _ Databases _ Regions _ Programs _ Logging |+-----------------------------------------------------------------------------+

Viewing PI Enqueue Pool Statistics



IntroductionTo investigate the red status light for Pools on the System Overview panel:

1. Place the cursor next to Pools and press Enter.OMEGAMON II displays a pop-up indicating the tripped exception as shown in the following figure.

FIGURE 63. A Tripped APIE Exception

This pop-up shows that the APIE exception has tripped, indicating that PI enqueue pool use has reached the percentage defined by the APIE threshold.

To see how the PI enqueue pool is being used:

2. Press Enter to see the Storage Pools panel.OMEGAMON II displays a panel similar to the one in Figure 64 on page 177.

___ Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 System Overview IMS: 151C ___ + Select a component with “S” to show details +----------------------------------------------------------------------------+ | Status | Alerts | |-----------------------------------+----------------------------------------+ |_ Regions ##### _ XRF ----- | _ Pools ----- _ Conflicts ----- | | | | |_ IMS Status ----- _ ESS ----- | _ Threads ----- _ Databases - | +----------------------------------------------------------------------------+ | Storage Pools Tripped Exceptions | | | | | | Move cursor to selection, then press Enter. | | | | Exception Description | | | | APIE The percentage of the PI enqueue is use is greater | | than the threshold. | | | | | | | | | | F1=Help F12=Cancel |



FIGURE 64. First Pools Panel

The Storage Pools display consists of two panels. The information you need is on the second panel.

3. Select the <Pools Description> pushbutton to display the second panel.OMEGAMON II displays a panel similar to the following figure.

FIGURE 65. Second Pools Panel

At the bottom of the second panel (under PIEP), you find the following information:

n current size of the PI enqueue pool in bytesn maximum size of the PI enqueue pool in bytesn number of bytes used in the PI enqueue pooln number of unused bytes in the PI enqueue pooln percentage of the maximum size that is currently being usedn increment by which the pool size increasesFrom this information, you can see that the PI enqueue pool is completely filled up.

GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 Storage Pools IMS: 151C ___ + +-----------------------------------------------------------------------------+| Pool | Size | Util | Free | High Water | Largest FB | Extensions ||-------+----------+--------+----------+------------+------------+------------|| WKAP | 49152 | .00% | 49152 | 312 | | || DBWP | 24576 | .00% | 24576 | 672 | 24576 | || PSBW | 24576 | .00% | 24576 | 2512 | 24576 | || EPCB | 12288 | .0 | 12288 | 0 | 12288 | || CESS | 4096 | .00% | 4096 | 240 | 4096 | 0 || SBUF | 10240 | .00 | | 0 | | || DMPL | 49152 | 1.30% | 48480 | 638 | 48480 | |+-----------------------------------------------------------------------------+

(Storage Pools) <Pools Description>F1=Help F2=Keys F3=Exit F5=Refresh F6=Console F10=Action Bar

GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 Storage Pools Description IMS: 151C ___ + +-----------------------------------------------------------------------------+| Pool | Description ||-------+---------------------------------------------------------------------|| SAP | Dynamic SAPs Allocated: 3 Dynamic SAPs in Use. : 1 || | Utilization . . . . . : 33.33% Privileged SAPs. . . : 6 ||-------+---------------------------------------------------------------------|| PIEP | >> OI427: IRLM is the Single Lock Manager << || | |+-----------------------------------------------------------------------------+ <Storage Pools> (Pools Description)



If the PI enqueue pool fills up, PSBs abend which causes CICS transactions to stop. The PI enqueue pool space problem can be resolved by:

n a change in the IMSCTF parameters to increase the maximum sizen a decrease in system activityOnce the PI enqueue pool space problem resolves, you can check the status of the PSBs and restart them, if necessary, so that CICS transactions can use them. For information on restarting PSBs, see the next section, “Restarting a PSB” on page 179.

Another reason the PI enqueue pool space may be full is that a PSB is in a loop in which it is acquiring, but never releasing, pool space. In this case, you can use Operator Assist to stop the PSB and free up the pool space.

However, if the PSB is not functioning due to a problem (such as looping) and not releasing acquired pool space, you might need to use the operator console to stop the thread running that PSB. See “Analyzing DBCTL Thread Activity” on page 183 for information on stopping a thread.


Restarting a PSB

Restarting a PSB

IntroductionOnce the PI enqueue pool space problem resolves, you can check the status of the PSBs and restart them, if necessary, so that CICS transactions can use them.

1. To see the status of PSBs, place the cursor next to Programs in the Operator Assist section of the System Overview panel and press Enter.OMEGAMON II displays a detail panel for the PSBs as shown in the following figure.

FIGURE 66. Details for PSBs Panel

If you have many PSBs running, you might want to view only the unusable PSBs to select the ones to restart.

2. Select Unusable from the View pull-down menu to see only the unusable PSBs.Note: You can also select a specific PSB or PSB group to view using the

View pull-down menu. Grouping PSBs makes it easier to restart several at once. See “Managing Groups of IMS Resources” on page 197 for instructions on creating PSB groups.

OMEGAMON II displays a panel listing PSBs with their status as shown in the following figure.

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:00:00 PSB Operations IMS: 151C ___ + L=Lock N=Unlock O=Stop R=Start ________ + Lines 1 to 5 of 5+-----------------------------------------------------------------------------+| PSB | Status | Type ||--------------------------+-------------------------+------------------------|| DBF#FPU0 | PSB-Stop | Online || ACCTNT010 | PSB-Stop | Batch || DFHSAM05 | PSB-Stop | Batch || DFHSAM14 | Schedulable | Batch || DFHSAM15 | Schedulable | Batch |+-----------------------------------------------------------------------------+F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd **=Fwd

Restarting a PSB


FIGURE 67. PSB Status

To see a list of the actions you can take on PSBs on this panel, type a slash (/) next to a stopped PSB or PSB group and press Enter. Or, type an A in the action bar entry field and press Enter.

3. To start a stopped PSB, type an R next to the stopped PSB (or PSB group) and press Enter.OMEGAMON II restarts the PSB or all the stopped PSBs in the group, which allows CICS transactions to restart.

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:00:00 PSB Operations IMS: 151C ___ + L=Lock N=Unlock O=Stop R=Start ________ + Lines 1 to 3 of 3+-----------------------------------------------------------------------------+| PSB | Status | Type ||--------------------------+-------------------------+------------------------|| DBF#FPU0 | PSB-Stop | Online || ACCTNT010 | PSB-Stop | Batch || DFHSAM05 | PSB-Stop | Batch |+-----------------------------------------------------------------------------+F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd **=FwdF10 A tion Bar F15 System Overview PA1 Swit h PA2 OMEGAVIEW


Detecting a PI Enqueue Pool Lockout


IntroductionAfter restarting all the stopped PSBs, you find that some CICS transactions are still stopped. You suspect that a PI enqueue pool lockout may be causing the problem. A PI enqueue pool lockout occurs when one thread needs to access part of a database that another thread has exclusively enqueued using PI-locking. To check for a PI enqueue pool lockout:

1. Place the cursor next to Conflicts on the System Overview panel and press Enter.OMEGAMON II displays the Database Conflicts panel as shown in the following figure.

FIGURE 68. Database Access Conflicts

On this panel, the PSB that owns the lock shows UP/OWN in the Status column and lists the name of the locked database area in the DB/area column. PSBs waiting for a database area have a Status of UP/WAT and list the name of the database area for which they are waiting.

To resolve the lockout problem, you can use Operator Assist to stop the PSB that owns the lock. To stop the PSB:

2. Press F3 to return to the System Overview panel.

3. Place the cursor next to Programs in the Operator Assist section of the System Overview panel.OMEGAMON II displays a detail panel for the PSBs.

4. Select Some from the View menu.OMEGAMON II displays a panel, as shown in Figure 69 on page 182, where you can enter the name of the PSB that you want to view.

GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 Database Conflicts IMS: 151C ___ + Lines 1 to 3 of 3+-----------------------------------------------------------------------------+| Subsys | Region | PSBname| TX/RgID | Lterm ID| Status| DB/area| RBA/RBN| DCB||--------+--------+--------+---------+---------+-------+--------+--------+----|| I31C |TCICS121|ACCNT010| 001 |--NONE-- | UP/OWN|ACCNTDBA|0000940C| 1 || I31C |TCICS121|UPDCUST1| 001 |--NONE-- | UP/WAT|ACCNTDBA|0000940C| 1 || I31C |TCICS132|UPDCUST1| 002 |--NONE-- | UP/WAT|ACCNTDBA|0000940C| 1 |+-----------------------------------------------------------------------------+F1=Help F2=Keys F3=Exit F5=Refresh F6=Console **=Bkwd **=FwdF10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW



FIGURE 69. Data Filters Pop-up - Enter a PSB Name

5. Enter the name of the PSB owning the lock in the Pattern field.Note: You can also enter a pattern (a partial name with asterisks as

wildcards) to view the PSBs whose names match the pattern.

OMEGAMON II displays a panel listing the PSB whose name matches the name you entered in the Pattern field as shown in the following figure.

FIGURE 70. PSB Operations - Matches Specified Pattern Displays

6. Type O next to the PSB owning the lock to stop that PSB.The PSB owning the lock stops, which releases the locked database area. The PSBs that were waiting for that database area can now continue processing.

v Actions GoTo View Options Help ----------------- +---------------------------------------------+ /97 12:02:10 | Data Filters | I51C____ + | | L=Lock N=Unlock | Type the correct values, then press Enter. | | | ________ + | Pattern . . . ACCTNT010 | f 2+----------------- | | -----------+| PSB | Status . . . ALL + | ||----------------- | | -----------|| ACCTNT0 | | h || DFHSAM0 | Enter F4=Prompt F12=Cancel | h |+------------------+---------------------------------------------+------------+F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd **=Fwd

F10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:00:00 PSB Operations IMS: 151C ___ + L=Lock N=Unlock O=Stop R=Start ________ + Lines 1 to 2 of 2+-----------------------------------------------------------------------------+| PSB | Status | Type ||--------------------------+-------------------------+------------------------|| ACCTNT010 | Schduled | Batch |+-----------------------------------------------------------------------------+ +------------------------------------------------------------------------------+

Analyzing DBCTL Thread Activity 183

Analyzing DBCTL Thread Activity

Chapter overviewThis chapter describes how to use this information to resolve a typical exception condition.

Chapter contentsBackground . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Investigating the Tripped Exception . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186Viewing Details for a Specific Thread . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Stopping a Thread . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190Viewing Details for PI or IRLM Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Viewing Details for DL/I Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Trapping Long-Running Threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

14

Background


Background

IntroductionIMS DBCTL is a database resource manager for CICS. CICS creates threads to DBCTL to access DBCTL databases. DBCTL represents a CICS thread with a Partition Specification Table (PST) control block. Because DBCTL has only 255 PSTs available for all CICS regions, the PSTs must be balanced among all CICS regions.

Two parameters, MAXTHRD and MINTHRD, are defined in the CICS system generation to control the number of threads that CICS can create for DBCTL database access. MINTHRD specifies the minimum number of threads that CICS must have allocated at all times. MAXTHRD specifies the thread allocation limit.

Having the number of available threads equal to MINTHRD reduces overhead when a CICS transaction needs to access the databases in a DBCTL system. If none of these threads is available, CICS dynamically creates a new thread for the transaction, as long as the number of threads is less than MAXTHRD. A MINTHRD value that is too small causes overhead, because threads must be created frequently. A MINTHRD value that is too large wastes resources.

When the number of active threads reaches a user-defined threshold, OMEGAMON II warns you with the THHI exception. When the number of active threads is less than a user-defined threshold, OMEGAMON II trips the THLO exception.

Using these exceptions, you can determine when you need to change the MINTHRD or MAXTHRD CICS parameters to accommodate thread activity. For example, if you set the exception threshold of THHI to a number that equals about 90% of the available threads, a THHI exception would indicate that you may soon need to increase MAXTHRD for one of the CICS regions so that PSTs will be available when they are needed.

Using OMEGAMON II, you can monitor the activity of all CICS threads. For each thread, you can see the transaction code, Program Specification Table (PST) number, recovery token, PSB name, and status. You can also see details for database locks and DL/I calls. To identify and trap long running threads, you can use the TTIM command to set CPU and elapsed time thresholds for a PSB that IMS schedules on behalf of a CICS thread. When the PSB exceeds the CPU or elapsed thresholds, OMEGAMON II trips the TPSB exception.


Scenario

Scenario

IntroductionWhen you arrive at work in the morning, the system seems to be running smoothly. As people begin using CICS for a variety of transactions, you start receiving calls that the transactions are running slowly. As the day goes on, response time becomes worse.

You check the System Overview panel and notice that the Threads status light is red, indicating a tripped exception.

Investigating the Tripped Exception



IntroductionTo investigate the threads status light on the System Overview panel:

1. Place the cursor next to the Threads status light and press Enter.OMEGAMON II displays a pop-up showing the tripped exception.

FIGURE 71. Tripped Exceptions Pop-up

The THHI exception has tripped because the number of active threads has reached the critical value you specified for this threshold. The THHI exception provides a warning before the number of active threads reaches the maximum defined with the CICS MAXTHRD parameter. If the number of active threads reaches MAXTHRD, CICS is unable to create more threads, and transactions begin waiting for threads to become available.

2. To see information about all threads, press Enter on the Threads Tripped Exceptions pop-up.OMEGAMON II displays a panel similar to the one in Figure 72 on page 187, listing all the threads used by all CICS regions.

___ Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 System Overview IMS: 151C ___ + Select a component with “S” to show details +----------------------------------------------------------------------------+ | Status | Alerts | |-----------------------------------+----------------------------------------| |_ Regions ##### _ XRF ----- | _ Pools ----- _ Conflicts ----- | | | | |_ IMS Status ----- _ ESS ----- | _ Threads ----- _ Databases ----- | +----------------------------------------------------------------------------+ | Threads Tripped Exceptions | | | | | | Move cursor to selection, then press Enter. | | | | Exception Description | | | | THHI The number of active threads is greater than the | | threshold. | | | | | | | | | | F1=Help F12=Cancel | +----------------------------------------------------------------------------+



FIGURE 72. Threads Summary Panel

From the Threads Summary panel, you can display detailed information about a particular thread. For example, you can see which CICS transaction a thread is running or whether the thread is holding any locks that might delay other threads.

Threads on this panel display the PST number in the Thread ID column. For example, in the above figure, thread RCICS330 has a PST number of 27.

Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 Threads Summary IMS: 151C ___ + Lines 1 to 2 of 2+-----------------------------------------------------------------------------+| Thread | Thread | CICS | PSB | Status | Database | Locks | CPU || Name | ID | Tran | Name | | Total I/O| Held | (TCB) ||------------+----------+------+--------+----------+----------+-------+-------|| _ RCICS330 | PST #27 | WD80 |DFHSAM05| Unavail | 54 | 4 | 2.45 || _ RCICS440 | PST #25 | TEST |IMSPSB2 | Idle | 18 | 0 | 2.35 |+-----------------------------------------------------------------------------+

Viewing Details for a Specific Thread



IntroductionTo see details about the active thread RCICS330, place the cursor next to the CCTL Name of the active thread with the PST Number of 27 and press Enter.

OMEGAMON II displays a detail panel for that thread as shown in the following figure.

FIGURE 73. Thread Details Panel

The Thread Details panel shows the thread’s CICS transaction code, PSB name, status, the number of DL/I calls, and indicates whether the thread is holding any locks which might delay other threads. If the thread is waiting, the panel sections entitled Elapsed Wait Time for and Number of Waits for indicate the reasons for waiting, the time spent waiting, and the number of waits. OMEGAMON II displays this information from the PNR major command and its minors, and from the THRD immediate command.

The Number of DL/I Calls and Locks Held fields are input fields on this panel. You can see details about DL/I calls by following the procedure in “Viewing Details for DL/I Calls” on page 193. You can see details about database locks by following the procedure in “Viewing Details for PI or IRLM Locks” on page 192.

The bottom section of the panel displays user parameter information for the current DL/I call. OMEGAMON II displays this information from the PNR major and .EXM immediate commands. The PNR major command provides access to minor commands used for thread analysis. The .EXM immediate command executes all the minor commands associated with the PNR major to provide extensive information about the thread.

Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 Thread Details for RCICS330 in Region 27 IMS: 151C ___ + +------------------------------------------------------------------------------+| RecoveryToken : A875132230213288 | Current: PSB . . . . . . : DFHSAM05 || Status . . . . . . . : Unavail | CICS Trans . . : WD80 || _ Number of DL/I Calls : 2 | Number or DB I/O . . . . : --None-- || _ Locks Held . . . . . : 4 | Elapsed Time for DB I/O : --None-- || Elapsed Wait Time for | Number of Waits for || Pool Space . . . . : --None-- | Test Enqueues . . . . : --None-- || Intent Conflict . : --None-- | Update Enqueues . . . : --None-- || Schedule Process . : .001513 | Exclusive Enqueues . . : --None-- || PI Locking . . . . : --None-- | DEDB Buffers . . . . . : --None-- ||------------------------------------------------------------------------------|| Current DL/I Call || Function : GHU || PCB : DI21PART01 A .. QPARTROOT........02CSR13G104KL || IOA : 02CSR13G104KL KR1J50KS || SSA 04 + : PARTROOT*----------------------------(PARTKEY =2CS |+------------------------------------------------------------------------------+ <GoTo CICS>



Look at the details for this thread under panel section Current DL/I Call. Notice that the CALL command indicates that this thread is executing the GHU (Get Hold Unique) function and that the PCB is DI21PART01. When you press F5 several times, the function and PCB do not change, but the CPU rate (indicated by the CPU command) increases. From this information, you suspect that the thread is looping.

You can stop the looping thread by following the procedure in “Stopping a Thread” on page 190.

Stopping a Thread


Stopping a Thread

IntroductionYou might want to stop a thread for one of the following reasons:

n A thread’s Status is Unavail on the Thread Details panel (see Figure 73 on page 188), which can cause CICS transactions to terminate improperly.

n A thread is looping.

To stop a thread:

1. Note the CCTL name of the unavailable thread.The CCTL name displays in the title of the Thread Details panel, as shown in Figure 73 on page 188.

2. Select Regions from the Operator Assist section of the System Overview panel, and press Enter.OMEGAMON II displays the Region Operations panel as shown in the following figure.

FIGURE 74. Region Operations

3. Type an O (O=Stop) next to the CCTL name of the thread, and press Enter.OMEGAMON II displays the Stop Options pop-up, as shown in Figure 75 on page 191.

____ Actions GoTo View Options Help__________________________________________________04/29/99 3:56:18 PM Region Operations I51CVIEW: Dependent O=Stop ________+ Lines 0 to 0 of 0+---------------------------------------------------------------------+| Region | Type |Status |Occupancy | Classes | Locks | Transaction |+---------------------------------------------------------------------+| | | | | | | |+---------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd **=Fwd


Stopping a Thread

FIGURE 75. Stop Options Pop-Up

4. In this case, select option 2, Abend, and press Enter.This command stops the unavailable thread. CICS can then dynamically recreate the thread when it is needed to process CICS transactions.

Actions GoTo View Options Help ----------+------------------------------------+------------ 01/02/97 12:00:00 | Stop Options | IMS: 151C ___ + | | O=Stop | Select a specific STOP command | | for the selected regions. | | | ________ | 1. Normal Stop | Lines 1 to 2 of 2+--------- | 2. Abend || Regio | 3. Cancel |---------------------+|--------- | 4. WFI Stop | Locks | Transaction || s RCICS3 | |---------------------+| _ RCICS4 | F1=Help F12=Cancel | | |+----------+------------------------------------+---------------------+F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd **=Fwd

F10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW

Viewing Details for PI or IRLM Locks


Viewing Details for PI or IRLM Locks

IntroductionTo see details about each of the database locks that thread RCICS330 is holding, type an S in the input field next to Locks Held on the Thread Details panel and press Enter.

OMEGAMON II displays a detail panel for thread locks as shown in the following figure.

FIGURE 76. Thread Locks Details Panel

The Thread Locks Details panel shows the

n name of the subsystem holding the lock

n intent and status of the PSB holding the lock or waiting for the resource

n database name or DEDB name

n relative byte address for PI locking or relative block number for IRLM locking (RBA/RBN)

The bottom section of the panel displays information about the PI enqueue pool utilization, including the percentage of the theoretical maximum pool size currently in use and other information relative to both current and maximum pool sizes.

If you want to display information about DL/I calls, place the cursor on the DL/I Calls pushbutton and press Enter, to go to the Thread DL/I Calls Details panel.

GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 Thread Locks Details for RCICS330 IMS: 151C ___ + Lines 1 to 1 of 1 +---------------------------------------------------------+ | Subsystem | Status | DB or Area | RBA/RBN | DCB | |-------------+----------+--------------+-----------+-----| | I41B | UP/Wat | DI21PART | AF2392E7 | 1 | +---------------------------------------------------------+


Viewing Details for DL/I Calls

Viewing Details for DL/I Calls

IntroductionTo see details about the DL/I calls that PSB DFHSAM05 has made, type an S in the input field next to Number of DL/I Calls on the Thread Details panel and press Enter.

OMEGAMON II displays a detail panel for DL/I calls as shown in the following figure.

FIGURE 77. Thread DL/I Calls Details Panel

The Thread DL/I Calls Details panel shows general information such as the CICS transaction name for the thread, the status of the thread, the number of database I/Os, and the number of DL/I database calls since the thread last scheduled the PSB.

This panel also displays more specific information about the database calls, including the number of:

n get hold calls (GH)n get unique calls (GU)n get next calls (GN)n get next within parent calls (GNP)n database insert, delete, and replace callsThe bottom section of the panel displays user parameter information for the current DL/I call.

If you want to display information about the database locks, place the cursor on the Locks pushbutton and press Enter, to go to the Thread Locks Details panel.

GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 Thread DL/I Calls Details for RCICS330 IMS: 151C ___ + +------------------------------------------------------------------------------+| CICS Transaction . . . : WD80 | Number of DL/I Calls . . . . : 2 || Status . . . . . . . . : Unavail | Number of DB I/O Executions : --None-- ||------------------------------------+-----------------------------------------|| Get Unique Calls . . . : 0 | Get Next Calls . . . . . . . : 0 || Get Hold Calls | Get Next within Parent Calls : 0 || Unique . . . . . . . : 0 | Insert Calls . . . . . . . . : 0 || Next . . . . . . . . : 0 | Delete Calls . . . . . . . . : 0 || Next within Parent . : 0 | Replace Calls . . . . . . . : 0 ||------------------------------------------------------------------------------|| Most Recent DL/I Call || Function : GHU || PCB : DI21PART01 A .. QPARTROOT........02CSR13G104KL || IOA : 02CSR13G104KL KR1J50KS || SSA 04 + : PARTROOT*----------------------------(PARTKEY =2CS |+------------------------------------------------------------------------------+

Trapping Long-Running Threads



IntroductionTo trap a long running PSB that IMS schedules on behalf of a CICS thread:

1. Note the PSB name of the thread you want to trap.The PSB name is DFHSAM05 for the thread shown on the panel in Figure 73 on page 188.

2. Select Cmd/Menu Interface (OMEGAMON) from the GoTo pull-down.The Zoom to OMEGAMON pop-up displays.

3. To zoom to the menu interface, make sure that OMEGAMON screen space is blank, and press Enter.The Main Menu appears as shown in the following figure.

FIGURE 78. Main Menu

To define time thresholds for a PSB use the TTIM immediate command.

4. Type ..bb starting in column 2 under the INFO-line to clear the screen.

5. Type TTIM ADD in column 2 under the INFO-line, specifying the CCTL name, PSB name and thresholds for CPU and/or elapsed times. Press Enter.OMEGAMON II displays a message telling you that it has added the PSB threshold, as shown in the following figure.

FIGURE 79. TTIM Add

________________ KOIMENU VTM DBCTL /C I51C 01/02/97 12:00> Help/News PF1 Exit PF3 Keys PF5 Command Mode PF12 Colors PF18> Return to CUA PA2> Enter a selection letter on the top line.========================================================================> OMEGAMON for DBCTL Performance Monitor Main Menu _ E EXCEPTIONS ....... Current and potential system problems, latch conflicts_ R RESPONSE TIMES ... Response time information (RTA users)_ B BOTTLENECKS ...... Resource contention (bottleneck analysis) (DEXAN users) _ M MONITOR .......... IMS status, graphs, and time controlled operations_ W WORKLOAD ......... PSBs, DMBs, transmission, regions and CUAs_ A ALL POOLS ........ Communication, database, and program tools_ C COMPONENTS ....... I/O, logging, storage, and control blocks/modules _ F FAST PATH ........ IMS Fast Path information_ O OTHER SYSTEMS .... DB2 interface and XRF information _ T TOOLS ............ Operator tools

______________KOI#01D VTM DBCTL /C I51C 01/02/97 12:00 OB======================================================================= TTIM ADD RCICS330 PSB=DFHSAM05 CPU=1 ELAPSED=10

+ PSB THRESHOLD HAS BEEN ADDED



6. To verify that the PSB threshold is added, type ..bb starting in column 2 under the INFO-line to clear the screen, type TTIM, and press Enter.OMEGAMON II displays a list of all defined thresholds for all CCTLs, as shown in the following figure. You will see your PSB threshold in the list.

FIGURE 80. TTIM List

To trap long running threads, the TTIM immediate command compares each active thread with each TTIM threshold to see if a PSB has exceeded the CPU or elapsed threshold. If a PSB exceeds either of the time thresholds, the TPSB exception trips.

Note: Exception Analysis and the Transaction Reporting Facility (TRF) must be active for the TPSB exception to provide data. If you start OMEGAMON after IMS schedules a PSB, the TTIM command does not check the PSB against the TTIM thresholds.

7. To show all tripped exceptions, type LXIMS, starting in column 1 under the INFO-line and press Enter.OMEGAMON II starts Exception Analysis and displays a list of tripped exceptions, as shown in the folowing figure.

FIGURE 81. XIMS Immediate Command

8. Locate the TPSB exception in the list.

9. Move the cursor to column 2 beside the TPSB exception and press F11.OMEGAMON II displays the help for the TPSB exception, as shown in Figure 82 on page 196.

______________KOI#01D VTM DBCTL /C I51C 01/02/97 12:00 OB======================================================================= TTIM+ RCICS410 PSB=DFHSAM05 CPU=0001 ELAPSED=0010+ RCICS410 PSB=DFHSAM25 CPU=0001 ELAPSED=0001+ RCICS310 PSB=DFSIVP4 CPU=0001 ELAPSED=0010+ RCICS310 PSB=C* CPU=0001 ELAPSED=0002+ RCICS310 PSB=B* CPU=0001 ELAPSED=0001+ RCICS310 PSB=*05 CPU=0001 ELAPSED=0001

______________KOIMENU VTM DBCTL /C I51C 01/02/97 12:00 OB > Help/News PF1 Exit PF3 Keys PF5 Command Mode PF12 Colors PF18LXIMS OMEGAMON/IMS Exception Analysis+ TPSB CCTL RCICS310 PSB DFHSAM05 threshold exceeded:+ RgID DFSIVP4 ELAPSED time = 1473.0+ RgID DFSIVP4 CPU time = .5+ PISP DLS Region: Private Area Page-in Rate = .00/second (High)+ PILC IRLM Region: Common Area Page-in Rate = .00/second (High)

+ PILP IRLM Region: Private Area Page-in Rate = .00/second (High)



FIGURE 82. TPSB Exception Help

10. Follow the procedure in “Viewing Details for a Specific Thread” on page 188, to check the status of the PSB thread.

______________KOITPSB VTM DBCTL /C I51C 01/02/97 12:00 OB> Back PF3 Up PF7 Down PF8=======================================================================> TPSB -- A PSB has exceeded an execution time threshold > Explanation: > This exception message displays when one or more of the PSBs that> the TTIM command defines with an execution time threshold exceeds> a specified CPU or ELAPSED time threshold.>> There are many reasons a PSB may use more CPU or ELAPSED> time than expected. Among them are:>> - A database that the PSB requires is stopped> - The PSB is waiting for a lock on a database or area to be freed> - The PSB is waiting for DMB, PSB, or PSB Work Area pool space>> Recommendations: > Issue the THRD immediate command to check the status of the PSB> that IMS has scheduled in the CCTL thread for which the exception> tripped. Note that this exception does not trip for threads that> were scheduled before OMEGAMON began executing.

Managing Groups of IMS Resources 197

Managing Groups of IMS Resources

Chapter overviewThis chapter explains how to use the Operator Assist group management facility to manage a group of PSBs.

Chapter contentsBackground . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Rules for Creating Resource Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Selecting a PSB Group Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Creating a New PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Copying a PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Deleting a PSB from a PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211Stopping a PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212Starting a PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

15

Background


Background

IntroductionIMS uses a data structure called a program specification block (PSB) to define an application program’s view of its IMS databases. Each PSB is composed of one or more program communication blocks (PCBs), a data structure IMS uses to define an application’s view of an individual IMS database.

Each PCB explicitly relates to an individual database by pointing to its definition data structure, the database description (DBD). Many PCBs in a single application program can all point to a single DBD.

You can use PSBs to define an application’s access to the database by excluding data the program either does not need or should not be able to read because of security reasons.

OMEGAMON II’s Operator Assist group management facility lets you group related IMS resources of the same type, including PSBs, databases, regions, and threads, and associate a name with the group. You can then issue commands against the group name, instead of issuing commands against each individual resource in the group.

You can use the group management facility to:

n create a new resource groupn delete an existing resource groupn copy the contents of an existing group into a new or existing groupn add resources to a groupn delete resources from a group


Scenario

Scenario

IntroductionYour company uses an online payroll application involving several different PSBs. These PSBs let the Payroll department iteratively enter new employees, rate-of-pay changes, and vacation usage.

Once each week, the Payroll department must stop the payroll application PSBs to run the batch payroll calculation application. This batch application calculates the employee’s pay and prints payroll checks.

Currently, stopping the payroll application involves stopping 8 PSBs, one at a time. To expedite stopping the PSBs, you decide to use OMEGAMON II’s Operator Assist facility to create a PSB group and add all of the payroll application PSBs to this group. You can then issue a single command to stop the PSB group, instead of having to stop each PSB individually. After running the batch payroll calculation application, you can then issue a single command to start the same PSB group.

You may want to review the “Rules for Creating Resource Groups” on page 200, before continuing with the procedure “Selecting a PSB Group Name” on page 201.

Rules for Creating Resource Groups


Rules for Creating Resource Groups

IntroductionYou must follow these rules when creating resource groups:

n You can associate a single group name with 1–999 IMS resources of the same type using OMEGAMON II tools.

n You can copy all PSBs in a group into a new or existing group, if you are the creator of the new or existing group.

n A group name provides you with a way to issue an Operator Assist command, like Start or Stop, on a set of IMS resources of the same type. IMS resources include PSBs, DMBs, regions, and threads.

n To operate on an individual PSB, specify a command mnemonic (from the mnemonics list at the top of the panel) in the input field to the left of the PSB name.

n To operate on a group of PSBs, create a group and specify the command mnemonic in the input field to the left of the group name.

n You can delete individual PSBs from a group or delete an entire group only if you log on with the same user ID that created the group.

If you use a group that you did not create, OMEGAMON II does not display the menu selections that let you delete resources or groups.

n Every group you create will correspond only to the current ID that IMS is monitoring. The same PSB group can exist on different IMS ID monitors, but make sure the PSB group has a different name on each system.

n A group exists only in the IMS system where you create it. You can create a new PSB group by copying an existing group from another IMS system and assigning the same resources. As soon as you copy a group give the new group another name.


Selecting a PSB Group Name


IntroductionBefore creating a new PSB group, you should check to see what group names already exist.

1. Select Programs from the Operator Assist section of the System Overview panel (Figure 83 on page 201) and press Enter.

FIGURE 83. System Overview Panel - Select Programs

OMEGAMON II displays the PSB Operations panel, shown in Figure 84 on page 202.

Note: Your PSB Operations panel may display a list of PSBs at this point, depending on whether other users have previously been working with PSB groups. Continue with this procedure as it is written: the displayed PSBs have no effect on what you are doing.

___ Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 System Overview IMS: 151C ___ + Select a component with “S” to show details+-----------------------------------------------------------------------------+| Status | Alerts || -------------------------------------+--------------------------------------|| _ Regions ----- _ XRF ----- | _ Pools ----- _ Conflicts ----- || | || _ IMS Status ----- _ ESS ----- | _ Threads ----- _ Databases ----- || | || _ Bottleneck ----- _ Traces ===== | _ Logging ----- _ Fast Path ----- || | || _ Buf. Pools ----- | _ Programs ----- || | || _ I/O ----- | _ ||-----------------------------------------------------------------------------|| Operator Assist ||-----------------------------------------------------------------------------|| _ Databases _ Regions s Programs _ Logging |+-----------------------------------------------------------------------------+



FIGURE 84. PSB Operations Panel

2. Position your cursor in the input field at the top of your panel under the action mnemonics, and press F4.OMEGAMON II displays a list of all defined groups, as shown in the following figure.

FIGURE 85. PSB Groups Available Pop-up

Notice that there is a PSB group called PAYROLL. You suspect that PAYROLL may contain some or all of the PSBs you need.

3. To confirm your suspicion, move the cursor to the PAYROLL group and press Enter.OMEGAMON II displays a list of the resources associated with the PAYROLL group, as shown in the following figure.

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:00:00 PSB Operations IMS: 151C ___ + VIEW: ALL L=Lock N=Unlock O=Stop R=Start ________ + Lines 1 to 12 of 12+-----------------------------------------------------------------------------+| PSB | Status | Type ||--------------------------+-------------------------+------------------------|| DFSIVPC | Schedulable | Batch || PAYCALC | Schedulable | Batch || PAYEMP1 | Scheduled | Online || PAYEMP2 | Scheduled | Online || PAYEMP3 | Scheduled | Online || PAYVAC1 | Scheduled | Online || PAYVAC2 | Scheduled | Online || PAYVAC3 | Scheduled | Online || PAYW41 | Scheduled | Online || PAYW42 | Scheduled | Online || PAYW43 | Scheduled | Online |

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:00:00 PSB Operations IMS: 151C ___ + VIEW: ALL L=Lock N=Unlock O=Stop R=Start ________ + Lines 1 to 10 of 10+---+------------------------------------------------+------------------------+| | Groups Available for Selection | Type || | |------------------------|| | | Batch || | Move cursor to selection, then press Enter. | Online || | | Online || | Group Owner Resources | Online || | | Online || | GGBDBS TDMX54 7 | Online || | MEHVDBS TDMX54 5 | Online || | PAYROLL TDMX12 10 | Online || | SH83550 TDMX02 6 | Online || | | Online |



FIGURE 86. PSB Operations - Resources for PAYROLL Group

You confirm your suspicion, since all of the payroll application PSBs are part of the PAYROLL PSB group. You can create a new group from scratch or you can copy the PAYROLL group to create a new group. In either case, we will call this new group PAYSTOP.

Now that you have selected a name for your PSB group, continue with the procedure “Creating a New PSB Group” on page 204 or “Copying a PSB Group” on page 208.

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:00:00l PSB Operations IMS: 151C ___ + L=Lock N=Unlock O=Stop R=Start Group Management: C=Copy Group_ PAYROLL + Lines 1 to 10 of 10+-----------------------------------------------------------------------------+| PSB | Status | Type ||--------------------------+-------------------------+------------------------|| _ PAYCALC | Scheduable | Batch || _ PAYEMP1 | Scheduled | Online || _ PAYEMP2 | Scheduled | Online || _ PAYEMP3 | Scheduled | Online || _ PAYVAC1 | Scheduled | Online || _ PAYVAC2 | Scheduled | Online || _ PAYVAC3 | Scheduled | Online || _ PAYW41 | Scheduled | Online || _ PAYW42 | Scheduled | Online || _ PAYW43 | Scheduled | Online |

Creating a New PSB Group



IntroductionTo create a new PSB group from scratch:

1. Position your cursor in the input field at the top of your panel under the action mnemonics, type PAYSTOP, and press Enter.OMEGAMON II displays the Create Group pop-up, as shown in the following figure.

FIGURE 87. Create Group Pop-up

2. Choose option 1, Yes, create group, to create the new group PAYSTOP.OMEGAMON II displays the Add Resources to Group panel, as shown in the following figure, where you can limit the selection of displayed PSB resources and also select specific PSB resources for the new PAYSTOP group.

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:00:00 PSB Operations IMS: 151C ___ + L=Lock N=Unlock O=Stop R=Start PAYSTOP + Lines 1 to 10 of 10+-----------+-------------------------------------------------+---------------+| | Create Group PAYSTOP | ype || | | --------------|| _ | Group PAYSTOP does not exist. | atch || _ | Create group PAYSTOP on your IMS system I31C? | nline || _ | | nline || _ | 1. Yes, create group. | nline || _ | 2. No, cancel create. | nline || _ | | nline || _ | F1=Help F12=Cancel | nline || _ +-------------------------------------------------+ nline || _ PAYW42 | Scheduled | Online || _ PAYW43 | Scheduled | Online |



FIGURE 88. Add Resources to Group Pop-up

3. For this scenario, group all PSBs that begin with the characters PAY by typing PAY in the Pattern... field. Use the default value ALL for the Status field and press Enter.Note: You can display a list of the valid status values, by pressing F4 when

the cursor is in the Status field.

The Add Resources to Group panel now displays only those resources that begin with PAY, as shown in the following figure.

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:00:00 PSB Operations IMS: 151C ___ + L=Lock N=Unlock O=Stop R=Start PAYSTOP + Lines 1 to 10 of 10+-----------+-------------------------------------------------+-----------+---+| | Add Resources to Group: PAYSTOP | || | |---|| _ | Press Enter to change View. Press F3 to add resources. | || _ | | || _ | View Resources: | || _ | Pattern . . . : | || _ | Status . . . : ALL | || _ | | || _ | Select all resources that meet view options. | || _ | | || _ | Lines 7 to 14 of 19 | || _ | Select resources with a ‘/’ | |+---------- | | --+ | PSB Status Type | | _ DFHSAM05 Schedulable Batch | | _ DFSIVPC Schedulable Batch | | _ PAYEMP1 Scheduled Online | | _ PAYEMP2 Scheduled Online | | _ PAYEMP3 Scheduled Online | | _ PAYVAC1 Scheduled Online |



FIGURE 89. List of PSBs Matching Data Filter Pattern

Looking at this list of PSBs, you notice the PSB with the name PAYVAC1. PAYVAC1 is a vacation days used query program that must stay active, so you do not want to include this in the PAYSTOP group. Also, the PSB named PAYCALC is the batch payroll calculation application that needs to run after you stop the PAYSTOP group, so you do not want to include this in the PAYSTOP group.

4. Type a slash (/) next to all resources in the list, except for PAYVAC1 and PAYCALC, and press F3 to add the resources to the PAYSTOP group.OMEGAMON II now creates the PAYSTOP group with all of the specified PSBs, as shown in the following figure.

FIGURE 90. PSB Operations for PAYSTOP Group

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:00:00 PSB Operations IMS: 151C ___ + L=Lock N=Unlock O=Stop R=Start PAYSTOP + Lines 1 to 10 of 10+-----------+-------------------------------------------------+-----------+---+| | Add Resources to Group: PAYSTOP | || | |---|| _ | Press Enter to change View. Press F3 to add resources. | || _ | | || _ | View Resources: | || _ | Pattern . . . : PAY | || _ | Status . . . : ALL | || _ | | || _ | Select all resources that meet view options. | || _ | | || _ | Lines 1 to 8 of 10 | || _ | Select resources with a ‘/’ | |+---------- | | --+ | PSB Status Type | | _ PAYCALC Schedulable Batch | | _ PAYEMP1 Scheduled Online | | _ PAYEMP2 Scheduled Online | | _ PAYEMP3 Scheduled Online | | _ PAYVAC1 Scheduled Online | | PAYVAC2 Scheduled Online |

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:00:00 PSB Operations IMS: 151C ___ + L=Lock N=Unlock O=Stop R=Start Group Management: C=Copy Group D=Delete Group or Resource_ PAYSTOP + Lines 1 to 10 of 10+-----------------------------------------------------------------------------+| PSB | Status | Type ||--------------------------+-------------------------+------------------------|| ________ + | | || _ PAYEMP1 | Scheduled | Online || _ PAYEMP2 | Scheduled | Online || _ PAYEMP3 | Scheduled | Online || _ PAYVAC2 | Scheduled | Online || _ PAYVAC3 | Scheduled | Online || _ PAYW41 | Scheduled | Online || _ PAYW42 | Scheduled | Online || _ PAYW43 | Scheduled | Online |



To stop the PAYSTOP group, continue with the procedure “Deleting a PSB from a PSB Group” on page 211.

Note: If you want to add more resources to your group, move your cursor to the input field at the top of the list under the PSB column heading, type the resource name, and press Enter.

Copying a PSB Group


Copying a PSB Group

IntroductionTo copy the existing PSB group PAYROLL and create a new group:

1. Position your cursor on the input field at the top of the PSB Operations panel next to PAYROLL.

2. Type a C. beside the group name and press Enter. (You can also open the Action pull-down and select Copy Group).OMEGAMON II displays the Copy Group pop-up, as shown in the following figure.

FIGURE 91. Copy Group Pop-up

3. Type PAYSTOP in the Copy PAYROLL into input field and press Enter.OMEGAMON II creates the new PAYSTOP group, copies all of the PSBs from the PAYROLL group into the new group, and displays the Create Group pop-up, where you can confirm the group creation (Figure 92 on page 209).

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:00:00 PSB Operations IMS: 151C ___ + L=Lock N=Unlock O=Stop R=Start Group Management: C=Copy Groupc PAYROLL + Lines 1 to 10 of 10+--- +-------------------------------------------------+----------------------+| | Copy Group PAYROLL | Type || | |----------------------|| | Type the name of the group where the selected | Batch || | group is to be copied and press ENTER. | Online || | | Online || | Copy PAYROLL into . . . : ________ | Online || | | Online || | Enter F1=Help F12=Cancel | Online || +-------------------------------------------------| Online || _ PAYW41 | Scheduled | Online || _ PAYW42 | Scheduled | Online || _ PAYW43 | Scheduled | Online |+-----------------------------------------------------------------------------+


Copying a PSB Group

FIGURE 92. Create Group Confirmation Pop-up

4. Choose option 1, Yes, create group, to confirm the group creation.OMEGAMON II displays the Copy Resources pop-up, as shown in the following figure, where you can:

n choose whether or not to copy a specific PSB into the new PSB group you are creating

n copy all PSBs from the existing group to the new group

n stop the copy operation

FIGURE 93. Copy Resources Pop-up

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:00:00 PSB Operations IMS: 151C ___ + L=Lock N=Unlock O=Stop R=Start Group Management: C=Copy Groupc PAYROLL + Lines 1 to 10 of 10+--- +-------------------------------------------------+----------------------+| | Copy Group PAYROLL | Type || | |----------------------|| | Type the name of the group where the selected | Batch || | group is to be copied and press ENTER. | Online || | | Online || | Copy PAYROLL into . . . : ________ | Online || | +-------------------------------------------------+| | Enter F1=Help F12 | Create Group PAYSTOP || +--------------------- | || _ PAYW41 | Group PAYSTOP does not exist. || _ PAYW42 | Create group PAYSTOP on your IMS system I31C? || _ PAYW43 | |+-------------------------- | 1 1. Yes, create group. | | 2. No, cancel create. | | | | | | F1=Help F12=Cancel | +-------------------------------------------------+

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:00:00 PSB Operations IMS: 151C ___ + L=Lock N=Unlock O=Stop R=Start Group Management: C=Copy Groupc PAYROLL + Lines 1 to 10 of 10+--- +-------------------------------------------------+----------------------+| | Copy Group PAYROLL | Type || | |----------------------|| | Type the name of the group where the selected | Batch || | group is to be copied and press ENTER. | Online || | | Online || | Copy PAYROLL into . . . : ________ | Online || | +----------------------------------------------------+| | Enter F1=Help | Copy Resources || +-------------------| || _ PAYW41 | Copy PAYROLL into group PAYSTOP? || _ PAYW42 | || _ PAYW43 | 3 1. Yes, copy PAYCALC into PAYSTOP |+------------------------| 2. No, do not copy PAYCALC to PAYSTOP | | | | 3. Copy all resources from PAYROLL to PAYSTOP | | 4. Stop copy operation. | | | | F12=Cancel |

Copying a PSB Group


In this case, choose option 3, to copy all resources from PAYROLL to PAYSTOP.

The PAYSTOP group is now created with all of the PSBs from the PAYROLL group, as shown in the following figure.

FIGURE 94. PSB Operations for PAYSTOP Group

Looking at this list of PSBs, you notice the PSB with the name PAYVAC1. PAYVAC1 is a vacation days used query program that must stay active, so you will need to delete this PSB from the PAYSTOP group. Also, the PSB named PAYCALC is the batch payroll calculation application that needs to run after you stop the PAYSTOP group. You must also delete this PSB from the PAYSTOP group.

To delete a PSB from the PAYSTOP group, continue with the procedure “Deleting a PSB from a PSB Group” on page 211.

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:00:00 PSB Operations IMS: 151C ___ + L=Lock N=Unlock O=Stop R=Start Group Management: C=Copy Group D=Delete Group or Resource_ PAYSTOP + Lines 1 to 11 of 11+-----------------------------------------------------------------------------+| PSB | Status | Type ||--------------------------+-------------------------+------------------------|| ________ + | | || _ PAYCALC | Scheduable | Batch || _ PAYEMP1 | Scheduled | Online || _ PAYEMP2 | Scheduled | Online || _ PAYEMP3 | Scheduled | Online || _ PAYVAC1 | Scheduled | Online || _ PAYVAC2 | Scheduled | Online || _ PAYVAC3 | Scheduled | Online || _ PAYW41 | Scheduled | Online || _ PAYW42 | Scheduled | Online || _ PAYW43 | Scheduled | Online |+-----------------------------------------------------------------------------+


Deleting a PSB from a PSB Group

Deleting a PSB from a PSB Group

IntroductionTo delete PAYVAC1 from the PAYSTOP PSB group:

1. Move the cursor to the input field next to PAYVAC1 on the PSB Operations panel for PSB group PAYSTOP (see Figure 90 on page 206).

2. Type a D in the input field and press Enter.OMEGAMON II displays the Delete Resources pop-up, as shown in the following figure, where you can confirm the PSB deletion.

FIGURE 95. Delete Resources Pop-up

3. Choose option 1 to delete PAYVAC1 from the PAYSTOP group.

4. Repeat this procedure to delete PAYCALC.

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:00:00 PSB Operations IMS: 151C ___ + L=Lock N=Unlock O=Stop R=Start Group Management: C=Copy Group D=Delete Group or Resource_ PAYSTOP + Lines 1 to 10 of 10+-----------------------------------------------------------------------------+| PSB | Status | Type ||--------------------------+-------------------------+------------------------|| _ PAYCALC | Scheduable | Batch || _ PAYEMP1 | Scheduled | Online || _ PAYEMP2 | Scheduled | Online || _ PAYEMP3 | Scheduled | Online || d PAYVAC1 | Scheduled | Online || _ PAYVAC2 | Scheduled | Online || +-----------------------------------------------+ Online || | Delete Resources | Online || | | Online || | Delete PAYVAC1 from group PAYSTOP? | Online |+---------- | | ----------------+ F1=Help F2 | 1 1. Yes, delete PAYVAC1 from PAYSTOP |F7=Bkwd F10=Action | 2. No, do not delete PAYVAC1 from PAYSTOP | | | | 3. Yes, delete All selected resources | | 4. Cancel delete operation | | | | F1=Help F12=Cancel |

Stopping a PSB Group


Stopping a PSB Group

IntroductionTo stop the PAYSTOP PSB group:

1. Position your cursor on the input field at the top of the PSB Operations panel next to PAYSTOP.

2. Type O in the input field and press Enter.OMEGAMON II stops all of the PSBs associated with PSB group PAYSTOP. The following figure shows all of the PSBs in the PAYSTOP group.

FIGURE 96. PSB Operations for PAYSTOP Group - Changed Status to Stop

You can now run the batch payroll calculation application. When this application completes, continue with “Starting a PSB Group” on page 213 to start the PAYSTOP PSB group.

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:00:00 PSB Operations IMS: 151C ___ + L=Lock N=Unlock O=Stop R=Start Group Management: C=Copy Group D=Delete Group or Resource_ PAYSTOP + Lines 1 to 8 of 8+-----------------------------------------------------------------------------+| PSB | Status | Type ||--------------------------+-------------------------+------------------------|| _ PAYEMP1 | PSB-Stop | Online || _ PAYEMP2 | PSB-Stop | Online || _ PAYEMP3 | PSB-Stop | Online || _ PAYVAC2 | PSB-Stop | Online || _ PAYVAC3 | PSB-Stop | Online || _ PAYW41 | PSB-Stop | Online || _ PAYW42 | PSB-Stop | Online || _ PAYW43 | PSB-Stop | Online |+-----------------------------------------------------------------------------+


Starting a PSB Group


IntroductionTo start the PAYSTOP PSB group:

1. Position your cursor on the input field at the top of the PSB Operations panel next to PAYSTOP.

2. Type R in the input field and press Enter.OMEGAMON II starts all of the PSBs associated with PSB group PAYSTOP, and changes the status from PSB-Stop to Schedulable, as shown in the following figure.

FIGURE 97. PSB Operations for PAYSTOP Group - Status Schedulable

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:00:00 PSB Operations IMS: 151C ___ + L=Lock N=Unlock O=Stop R=Start Group Management: C=Copy Group D=Delete Group or Resource_ PAYSTOP + Lines 1 to 8 of 8+-----------------------------------------------------------------------------+| PSB | Status | Type ||--------------------------+-------------------------+------------------------|| _ PAYEMP1 | Schedulable | Online || _ PAYEMP2 | Schedulable | Online || _ PAYEMP3 | Schedulable | Online || _ PAYVAC2 | Schedulable | Online || _ PAYVAC3 | Schedulable | Online || _ PAYW41 | Schedulable | Online || _ PAYW42 | Schedulable | Online || _ PAYW43 | Schedulable | Online |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console F7=Bkwd **=Fwd



215

Part IV: Appendixes

Part IV provides additional information on using OMEGAMON II. It includes a section on using the menu/command interfaces to operate OMEGAMON II, a table listing all OMEGAMON II for DBCTL exceptions, and a table listing some Fast Path mnemonics.


Operating OMEGAMON II from the Menu/Command Interface 217

Operating OMEGAMON II from theMenu/Command Interface

Appendix overviewYou can log on to the menu/command interface directly in VTAM, ISPF, TSO, and Dedicated modes. From the menu/command interface you can:

n start exception analysis

n view exception analysis summary information

n respond to exception messages

n control and customize exceptions

n perform message exception analysis

Appendix contentsLogging On to the Menu/Command Interface Directly . . . . . . . . . . . . . . 218Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Specifying a User Profile in ISPF, VTAM, or TSO Mode . . . . . . . . . . . . . 221Working with Exceptions in VTAM, ISPF, TSO, or Dedicated Mode . . . . 222

A

Logging On to the Menu/Command Interface Directly


Logging On to the Menu/Command Interface Directly

IntroductionIf you choose to log on to OMEGAMON II’s menu/command interface directly, you can do so in several different modes of operation. These include VTAM, ISPF, TSO, and dedicated modes. Each of these modes and their advantages are described below.

For information about how to install and start OMEGAMON II in each mode, see the Configuration and Customization Guide.


Modes of Operation

Modes of Operation

VTAM modeIn VTAM mode, OMEGAMON II is connected directly to VTAM terminals, without the intervention of an intermediate online application such as TSO. VTAM mode allows up to 99 persons to operate OMEGAMON II, each from an individual terminal, without requiring access to TSO.

In VTAM mode you can set OMEGAMON II so that the screen refreshes automatically as in dedicated mode, but also responds immediately when you press Enter or any other program function key, as in TSO mode. This mode also assures the availability of OMEGAMON II if TSO is experiencing problems or is inoperable.

ISPF modeIn ISPF mode, users communicate with OMEGAMON II through TSO by means of ISPF.

In this mode, the OMEGAMON II screen does not refresh automatically. It refreshes when you press Enter or any other program function key.

OMEGAMON II can run in ISPF split screen mode; this mode lets you swap back and forth between multiple OMEGAMON II sessions or between OMEGAMON II and another ISPF application.

TSO modeIn TSO mode, OMEGAMON II communicates with the TSO address space via VTM1, a Candle-supplied VTAM application. TSO mode allows up to 99 persons to operate OMEGAMON II, each from an individual terminal. Because TSO use is widespread, this mode can provide many users with convenient access to OMEGAMON II.

In TSO mode the OMEGAMON II screen does not refresh automatically. It refreshes when you press Enter or any program function key.

Modes of Operation


Dedicated modeIn dedicated mode, OMEGAMON II is connected to one or optionally two dedicated consoles, each of which is a local non-SNA device.

Dedicated mode offers the highest OMEGAMON II availability, because it is least affected by system problems such as a VTAM outage. This is because in dedicated mode OMEGAMON II uses no telecommunications access methods; it communicates with the terminal via EXCP. By operating this way, OMEGAMON II can report hardware and software problems, even if VTAM is unavailable or the MTO console is disabled.

In dedicated mode, OMEGAMON II refreshes the screen automatically every five seconds without operator intervention. The default five-second interval can be changed to suit your reporting requirements. See the Configuration and Customization Guide for more information on customizing this interval.


Specifying a User Profile in ISPF, VTAM, or TSO Mode

Specifying a User Profile in ISPF, VTAM, or TSO Mode

IntroductionBy default, your OMEGAMON II session is started with the profile specified on the USER= parameter in your startup JCL or CLIST. To override the default, enter the 2-character suffix you assigned to your profile as follows:

n In ISPF mode, on the USER SUFFIX option of the ISPF logon menu.

n In VTAM mode, on the USER= startup parameter.

The following format is used for starting OMEGAMON II and specifying the USER parameter:

LOGON APPLID(applid) DATA(USER=’cc’)

n In TSO mode, on the USER parameter in the CLIST.

The current session’s profile suffix displays on the INFO-line next to the product version number. This example shows that a profile named SW is in use.

________________ KOIMENU VTM DBCTL SW 151C 01/02/97 12:00:00

Working with Exceptions in VTAM, ISPF, TSO, or Dedicated Mode



IntroductionOMEGAMON II exception analysis is a key factor in the logical tuning approach. It helps you answer the question, “What are the problems in the system?”.

Exceeding exception thresholdsException analysis alerts you to system problems, by producing messages on your terminal whenever exceptions to normal system performance occur. Your site defines normal system performance in the form of exception thresholds. Exception analysis compares IMS operating statistics to your current profile’s exception values and automatically warns you when threshold limits are exceeded or when unexpected problem conditions occur. The following figure is an example of an exception analysis display:

FIGURE 98. Systemwide Exceptions Display

Responding to exception messagesAn exception trips when the performance value it monitors exceeds the threshold you set or, in the case of alerts, when a particular condition or incident occurs. Tripped exceptions indicate warning or critical conditions. When an exception trips, you decide whether to change the exception threshold, gather more information to help you interpret the exception message, or take immediate action.

Setting exception thresholds

Candle ships OMEGAMON II with a default set of threshold values that you can use immediately. However, you can also set new threshold values to conform to your installation performance standards. Because exception conditions vary in each site, you need to customize OMEGAMON II to define which exceptions should execute and what their thresholds should be.

________________ KOISYS VTM DBCTL /C I51C 01/02/97 12:00> Help PF1 Back PF3 Up PF7 Down PF8 Zoom PF11>> For an explanation of an exception, place the cursor on the exception> name and press PF11.>===============================================================================> Systemwide Exceptions LXIMS OMEGAMON/IMS Exception Analysis+ DISP ########################################################################+ # OMEGAMON/IMS’s dispatching priority is lower than IMS’s #+ ########################################################################+ BQHI Fast Path available buffers for new PST use = 40 (High)+ DLTR DL/I Trace ON+ DSTR DISPATCHER Trace ON+ LKTR LOCK Trace ON



Determining your exception thresholds is a continuing process. You need to establish system parameters for:

n environment (CPU, I/O, working set size)n storage utilization (storage availability, violations)n task activity (DLI activity, limit situations)so that an exception analysis generates an exception message only when a value indicates that a condition has reached a critical level and action is needed. If you set exception criteria improperly, operators might spend too much time reacting to exceptions that do not represent real problems.

When deciding on appropriate thresholds for your site, you might want to check some current system values to determine what a normal value is for your system, and then set the threshold appropriately. You can test an exception through the selections on the Profile Menu (Option P on the Main Menu). These panels are discussed later in this chapter.

Investigating an exception

You can use the following features to help you investigate exception conditions.

n The zooming feature allows you to investigate an exception condition with the touch of a key. You can place your cursor on an exception and press PF11 to zoom to a Help panel containing recommended actions for the exception. You can also place your cursor on fields in a display such as volume serial numbers, device names, and address space names and press PF11 to zoom to greater detail.

n The Automatic Screen Facility (ASF) automatically reacts when an exception trips by invoking user-specified screen spaces and logging the command output, all without operator intervention.

n The Exception Logging Facility (XLF) automatically turns on the log to capture detailed information about performance exceptions when they occur. You can use this feature to ensure documentation and subsequent correction of intermittent performance problems. See the OMEGAMON II for DBCTL Realtime Commands Reference Manual for a detailed explanation of ASF and XLF.

n OMEGAMON II supplies a number of display panels that analyze various areas, such as IMS regions, device statistics, and memory utilization. These display panels are accessed through a set of menus.

Starting exception analysisThis section explains how to initiate exception analysis for all exceptions or for a limited group of exceptions.



All exceptions

To start exception analysis:

1. Select option E from the Main Menu.

2. From the Exceptions Menu, select option A to start group exception analysis or option B to display systemwide exceptions.When exception analysis is running, a warning message displays whenever an exception condition occurs. When no exception conditions exist in your system, OMEGAMON II displays the message

No exceptions tripped this cycle

You can customize this message on the Set All Clear Message panel. Type P.F.A on the INFO-line and press Enter.

OMEGAMON II displays the Set All Clear Message panel shown in the following figure.

FIGURE 99. Set All Clear Message Screen

Exceptions by group

OMEGAMON II organizes exceptions into logically related types, allowing you to execute, display, and customize them as a group. To display exception groups, you can select an option on the Exceptions Menu. For example, the Master Terminal Operator Exceptions panel displays the exceptions related to IMS internals, and those related to DASD logging (DL group).

You can see a list of the existing exception groups at your site. From command mode (press PF12 to toggle to command mode from menu mode), type GDFN with no arguments. OMEGAMON II also allows you to define your own exception groups with GDFN. See “Command Basics” on page 115 for more information on using command mode.

Exception analysis summary commandsYou can display exception analysis summary information in command mode (using the XSUM and XTRP commands) or in menu mode (using the History of All Tripped Exceptions panel). You can use this information to help you

________________ KOICLER VTM DBCTL /C I51C 01/02/97 12:00> Help PF1 Back PF3 Up PF7 Down PF8 Save Profile PF22===============================================================================> Set All Clear Message > The display below shows the current message that appears when exception> analysis detects no components above their exception threshold. To change> the message, type a new one of up to 60 characters enclosed in quotes after> XTXT. To make the change permanent, be sure to save the profile. XTXT+ ‘==> *** NO EXCEPTIONS TRIPPED ON THIS CYCLE *** <== ‘ ===============================================================================



set appropriate threshold values. For example, if an exception is tripped often, the threshold value might be set too low. Once you have fine tuned the threshold value for each exception, you can use this information to accurately monitor your IMS system for performance problem areas.

The summary display shows whether the exceptions are on or off, the threshold settings, the ASF parameters, and trip times and values. To display the History of All Tripped Exceptions type E.D on the INFO-line of any panel and press Enter.

Figure 100 on page 225 is a partial display of the History of All Tripped Exceptions panel.

FIGURE 100. History of All Tripped Exceptions

The Total Trips column shows the number of times the exception tripped since the OMEGAMON II session started.

The exceptions display in alphabetical order.

If you use the XSUM and XTRP commands to display this information, the following keywords are available:

GROUP=cc You can limit the tripped exceptions displayed to a specified exception group. Enter any 2-character code for a Candle-supplied exception group or a user-defined group.

________________ KOIHIST VTM DBCTL /C I51C 01/02/97 12:00> Help PF1 Back PF3 Up PF7 Down PF8 Zoom PF11>> To have the Exception History update, remove the > preceding the XIMS> command. The XIMS command must be executed to drive exception analysis.> Exception analysis must be performed to create a history of tripped> exceptions. For an explanation of an exception, place the cursor on the> exception name and press PF11.>===============================================================================> History of All Tripped Exceptions >XIMS XTRP LIST=A+----------+----------+-----------+--------------+-----------+----------------++ BQHI Threshold Trip Value Time Occurred Total Trips Trips Since Reset+ State=On 20+ Last 40 08/16 11:50:15 4 4+ Worst 40 08/16 11:50:15+ Group=FA Limit=0 Persist=0 Auto=Off Log=Off+----------+----------+-----------+--------------+-----------+----------------++ DISP Threshold Trip Value Time Occurred Total Trips Trips Since Reset



For more information about XSUM or XTRP, or about TSF, see the OMEGAMON II for DBCTL Realtime Commands Reference Manual.

Controlling and customizing exception analysisAlthough customizing exception analysis is generally part of the installation process, OMEGAMON II allows individual users to customize their sessions and to save these settings in individual profiles for later recall. This section provides an overview of the profile feature. For details on individual command syntax and additional customization options, see the OMEGAMON II for DBCTL Realtime Commands Reference Manual.

You can customize exception analysis in the following ways:

n Group definitionn Exception group switchesn Exception controln Invocation orderYou can then save the settings you define in a user profile. Refer to “Creating and maintaining profiles” on page 91.

You cannot save new group settings in the user profile. If you want to reuse those settings in future sessions, save them in a screen space and invoke the screen space at the start of your session. For more information on screen spaces, see “Screen Spaces” on page 137 or refer to the OMEGAMON II for DBCTL Realtime Commands Reference Manual.

Defining group exceptions

You can define your own exception groups by using the GDFN command in command mode. You might want to supplement or change the default groupings to organize exceptions in groups that are specifically related to your application. You could also group highly critical exceptions that have a potentially severe impact on the system.

LIST=I Enter I to request that the exceptions list in order of invocation.

RESET Enter RESET to reset the last and worst trip values to zero. This is useful when you change the default thresholds to ones that meet your installation performance standards. It can also be helpful when you want statistics on a specific job, or if you want to track exception activity for a given period of time in addition to cumulative activity.

Note: The XTRP command generates the summary display. The XSUM command displays all exceptions that are set, whether they have tripped or not. You can include the XSUM or XTRP RESET command in a TSF screen space for automatic resetting at periodic intervals. Resetting either XSUM or XTRP resets the counters for both commands.



Some advantages of defining exception groups are:

n Related or critical exception messages appear when you invoke exception analysis by group. They are more visible, because they are shown at the top of the display.

n A summary of the last and worst occurrences of exception warnings by group displays on the History of all Tripped Exceptions panel.

n You can set group switches using the XGSW command to determine the invocation state of the group as a whole. To display the existing groups, switch to command mode and enter XGSW. You can also define new groups or delete old ones in menu mode. See the OMEGAMON II for DBCTL Realtime Commands Reference Manual for more information on the XGSW command.

Setting group switches

You can control the state of all exceptions within a specified group by using the XGSW command. For example, you can turn all exceptions in a group on or off at once, force a sample warning message for each exception in a group for testing purposes, or suppress the display of messages for a group even though the exception switch is on (the latter option is useful for XLF and ASF).

The group switch overrides individual exception settings (unless you define a null state for the group).

You can list the existing groups or change them. To change the status of a group, add the keywords on the XGSW panel.

Here is an example of XGSW with keywords:

XGSW GROUP=IM STATE=NDSP

The above entry specifies that the IM group of exceptions is on and can be logged, but will not display on the terminal.

See the OMEGAMON II for DBCTL Realtime Commands Reference Manual for more information on XGSW keywords.

Controlling individual exceptions

OMEGAMON II provides a set of panels from which you can view the current characteristics of an exception or change the characteristics of an exception. On these panels you can dynamically change the settings of each keyword in the display by typing over the displayed value and pressing Enter. You can access these panels from the Profile Menu (option P on the Main Menu). You can save any new definitions you create in a user profile for future sessions (refer to “Creating and maintaining profiles” on page 91).

Some of the options on this panel allow you to call attention to an exception message. For example, you can cause the terminal bell to ring, control the color in which a warning displays, and assign display attributes that highlight the message. The following figure is an example of the Set Communications



External Subsystem Pool Exceptions panel showing the current characteristics for the ACEA exception (option P.A.A).

This panel allows you to specify five types of parameters for each exception.

Display Specifies display characteristics for the exception, such as the 2-character group name identifying the type of exception, whether the exception is ON or OFF, and whether to activate an audible alarm when the exception trips.

Box Specifies whether you want to enclose the warnings for this exception in a box. If not, specify NOBOX. Otherwise, you can specify the box character for the box, the box color or intensity, and attributes such as blinking, reverse video, and underlining.

Threshold Sets the exception threshold, usually numeric. You can also set display color and attributes for the exception message if you have not requested a boxed message.

________________ KOIODFB VTM DBCTL /C I51C 01/02/97 12:00> Help PF1 Back PF3 Up PF7 Down PF8 Save Profile PF22===============================================================================> Set Communications External Subsystem Pool Exceptions > To display the threshold of an exception, remove the > preceding XACB,> and type the exception name following LIST=. > To change the setting for an exception, type over the current setting> and press ENTER. To make your changes permanent, you must SAVE your> OMEGAMON profile. >XACB LIST=cccc > The CESS exceptions are: > ACEA Utilization > n%.> ACES IMS in selective dispatching for CESS pool.> ACEW Pool extension IWAITs > n.> ACEX Pool extension size > n.===============================================================================



The following keywords can be used with the XACB command shown on the previous panel:

The following example shows a TERSE keyword display:

Cycle Limits OMEGAMON II’s exception checking, which avoids using CPU time to test high overhead exceptions.

The EXNCYC keyword sets the frequency for checking exceptions. For example, you can choose to have OMEGAMON II check for a particular exception condition only every 5 or 10 cycles. See the .NXE immediate command in the OMEGAMON II for DBCTL Realtime Commands Reference Manual. for information about controlling the frequency of display.

The STOP keyword stops the checking of exceptions after they have tripped the specified number of times. It also displays how many times an exception has tripped since STOP= was reset.

The CUMULATIVE keyword is informational, indicating how many times an exception has tripped during the session.

XLF For a description of the XLF parameters, see the exception logging facility in the OMEGAMON II for DBCTL Realtime Commands Reference Manual.

LIST= Allows you to list the exceptions to display or modify.

GROUP= Allows you to limit the list of exceptions to those in the specified exception group.

FORCE Displays the exception’s current value as a sample exception message.

TERSE Displays an abbreviated, single-line status for each defined exception, showing the threshold value, display color, exception state, and the state of the bell.

________________ KOIODFB VTM DBCTL /C I51C 01/02/97 12:00 > Help PF1 Back PF3 Up PF7 Down PF8 Save Profile PF22 ================================================================================ > Set Communications External Subsystem Pool Exceptions > To display the threshold of an exception, remove the > preceding XACB, > and type the exception name following LIST=. > To change the setting for an exception, type over the current setting > and press ENTER. To make your changes permanent, you must SAVE your > OMEGAMON profile. XACB LIST=ACEA TERSE : ACEA Threshold=60 Display=DEFAULT State=ON Bell=OFF > The CESS exceptions are: > ACEA Utilization > n%. > ACES IMS in selective dispatching for CESS pool. > ACEW Pool extension IWAITs > n.



Reordering the display

You can display a list of the exceptions and the order in which OMEGAMON II executes and displays them by using the LEXC command (press PF12 for command mode).

The following example shows a partial display of the exceptions in the OMEGAMON II default order:

To dynamically change the order of the exceptions, type over an exception name or its number. You can save the new definition in your user profile.

Exception analysis for IMS messagesOMEGAMON II contains a facility that enables you to trap your IMS messages as exceptions. This facility is called message exception analysis.

Message exception analysis is activated from any OMEGAMON II terminal with the ICNS command. To ensure that message exception analysis is activated, your OMEGAMON II installer might want to define the ICNS command in an initialization panel invoked at OMEGAMON II session initialization.

For more information, see “Screen Spaces” on page 137, the OPTN command in the OMEGAMON II for DBCTL Realtime Commands Reference Manual, and the Configuration and Customization Guide.

________________ KOIMENU VTM DBCTL /C I51C 01/02/97 12:00 LEXC: INAC = 1 TCOI = 2 TCOT = 3 DISP = 4 DNRS = 5 TNRS = 6: DRDY = 7 TRDY = 8 IORC = 9 SPAH = 10 QBKH = 11 SMGH = 12: LMGH = 13 RDSH = 14 MFSH = 15 TMFH = 16 ACBH = 17 OSBL = 18: SAPW = 19 ITWH = 20 COMW = 21 SDSP = 22 CROL = 23 ARSP = 24 . . . . . . . . . . . .

. . . . . .



Listing, defining, and deleting messages with menus

Candle ships OMEGAMON II with a group of predefined IMS messages. To view or modify this list through the menu system, follow these steps.

1. From the Main Menu, select option P, Profile.The Profile Menu displays.

2. Select option F, Messages, from the Profile Menu.You see the Set Exception Messages Menu.

3. Select option B, Messages.The panel in the following figure displays:

FIGURE 101. Display of Pre-Defined IMS/MTO Messages

4. Follow the instructions on the panel to define or delete messages.

________________ KZIMSGD VTM DBCTL /C I51C 01/02/97 12:00> Help PF1 Back PF3 Up PF7 Down PF8 Save Profile PF22>===============================================================================> The MSGE exception must be ON for exception message processing to occur.> If you want to change the settings, type over the display below.> To make the changes permanent you must save you profile (PF22). XACB LIST=MSGE TERSE: MSGE Threshold=N/A Display=TURQUOISE State=ON Bell=OFF > SPECIFY EXCEPTION MESSAGES > This is a list of all currently defined IMS/MTO messages (such as DFSnnn or> ICEnnn) that display under Exception Analysis. MSGD+ M001 DFS144 OPTION = BUFSHOW+ M002 DFS236 OPTION = BUFSHOW+ M003 DFS243 OPTION = BUFFER . . . . . . . . . . . . + M024 DFS2179 OPTION = BUFSHOW+ M025 DFS2473 OPTION = BUFSHOW+ M026 DFS2474 OPTION = BUFSHOW > To add an IMS message, remove the > before MSGD below, and enter the specific> DFS message number. ________________ KZIMSGD VTM DBCTL /C I51C 01/02/97 12:00>MSGD ADD DFSnnn > To add an MVS message generated by an IMS region, remove the > before MSGD> below and enter the specific message number.



Defining message exception dsplay characteristics

To define the display characteristics of each message exception, complete the following steps:

1. Define the messages for message exception analysis on the Specify IMS/MTO Messages for Display panel (option P.F.B).

2. Press PF12 to enter command mode.

3. Enter the XACB command with the message exception name that you want to display.For example:

XACB LIST=M001

You see a display similar to the following.

4. Type over the setting for the display characteristic that you want to change.For example, for an audible signal when this exception trips, type ON after the BELL= parameter.

If you want to retain your changes after the current OMEGAMON II session, be sure to save them in a user profile. See “Creating and maintaining profiles” on page 91 for more information.

________________ KOIMENU VTM DBCTL /C I51C 01/02/97 12:00 XACB: INAC+ DISPLAY Parameters: THRESHOLD Parameters: XLF Parameters:: State=ON Threshold=N/A Auto=OFF: Group=IM Display=CLR1 Log=OFF: Bell=OFF Attribute=REVERSE Limit=0 (0): BOX Parameters: CYCLE Parameters: Repeat=NO: Boxchar=’#’ ExNcyc=0 Persist=0: Boxclr=TURQUOISE Stop=0 (0) SS=: Boxattr=REVERSE Cumulative=0: TCOI+ DISPLAY Parameters: THRESHOLD Parameters: XLF Parameters:: State=ON Threshold=N/A Auto=OFF: Group=IM Display=CLR1 Log=OFF: Bell=OFF Attribute=NONE Limit=0 (0): BOX Parameters: CYCLE Parameters: Repeat=NO: Boxchar=NO BOX ExNcyc=0 Persist=0: Boxclr=NONE Stop=0 (0) SS=: Boxattr=NONE Cumulative=0: TCOT+ DISPLAY Parameters: THRESHOLD Parameters: XLF Parameters:: State=ON Threshold=N/A Auto=OFF

Exceptions Table 233

Exceptions Table

Appendix overviewThis appendix lists the OMEGAMON II for DBCTL exceptions.

Appendix contentsOMEGAMON II for DBCTL Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . 234

B

OMEGAMON II for DBCTL Exceptions



IntroductionThe following table lists all of the OMEGAMON II for DBCTL exceptions in alphabetical order, along with a short description of what activity each exception monitors, the name of the exception group, and the status light the exception maps to for each exception.

Table 4. OMEGAMON II for DBCTL Exceptions

Exception ID

Description Exception Group

Status Light

ABUF Displays when sequential buffering storage utilization is > nn%.

Pools (Other) Databases

ACBH Displays when ACBLIB dataset I/O rate is > nn per second.

I/O Rates (Datasets)

I/O

ACEA Displays when utilization is > nn% for the communication external subsystem pool.

Pools (CES) Pools

ACES Displays when IMS is in selective dispatching for the communication external subsystem pool.

Pools (Alerts) Pools

ACEW Displays when pool extension IWAITs are > nn for communication external subsystem pool.

Pools (CES) Pools

ACEX Displays when pool extension size is > nn for communication external subsystem pool.

Pools (CES) Pools

ADBW Displays when database work pool utilization is > nn%.

Pools (Other) Pools

ADHI Displays when area DASD I/O per second is > nn.

The value of nn is the average DASD read + write rate for a DEDB area within a dataspace.

Fast Path (High)

Fast Path

ADLO Displays when area DASD I/O per second is < nn.

The value of nn is the average DASD read + write rate for a DEDB area within a dataspace.

Fast Path (Low)

Fast Path

ADME Displays when database management block (DMB) pool utilization is > nn%.

Pools (DMB) Pools



ADSU Displays if the data entry database (DEDB) area is unavailable.

Fast Path (Alerts)

Fast Path

AEPC Displays if the extended PCB pool utilization is > nn% for IMS systems that were generated with Fast Path.

Pools (Other) Pools

APIE Displays if the program isolation (PI) pool utilization is > nn%.

Pools (Other) Pools

APSB Displays if the active program specification block (PSB) pool utilization is > nn%.

Pools (PSB) Pools

APSW Displays if the PSB work pool (PSBW) utilization is > nn%.

Pools (PSB) Pools

ASAP Displays if the save area prefix (SAP) pool utilization is > nn%.

Pools (Other) Pools

ASHI Displays when area dataspace I/O per second is > nn.

The value of nn is the average dataspace read + write rate for a DEDB area within a dataspace.

Fast Path (High)

Fast Path

ASLO Displays when area dataspace I/O per second is < nn.

The value of nn is the average dataspace read + write rate for a DEDB area within a dataspace.

Fast Path (Low)

Fast Path

AWKP Displays if the IMS general work pool utilization is > nn%.

Pools (Other) Pools

BQHI Displays if the number of Fast Path available buffers for new PST use is > nn.

Fast Path (High)

Fast Path

BQLO Displays if the Fast Path available buffers for new PST use are < nn.

Fast Path (Low)

Fast Path

CBHI Displays when BMP region CPU utilization is > nn%.

CPU (High) Regions

CBLO Displays when BMP region CPU utilization is < nn%.

CPU (Low) Regions

CCHI Displays when control region CPU utilization is > nn%.

CPU (High) Regions

CCLO Displays when control region CPU utilization is < nn%.

CPU (Low) Regions


Exception ID


Status Light



CILO Displays when the number of free control intervals in independent overflow for a DEDB area is < nn.

This means that you may need to reorganize the database.

Fast Path (Low)

Fast Path

CLHI Displays when IRLM region CPU utilization is > nn%.

CPU (High) Regions

CLLO Displays when IRLM region CPU utilization is < nn%.

CPU (Low) Regions

CPUA Displays if the IMS CPU utilization is <= nn%.

CPU (Low) Regions

CRHI Displays if the DBRC region CPU utilization is > nn%.

CPU (High) Regions

CRLO Displays if the DBRC region CPU utilization is < nn%.

CPU (Low) Regions

CSHI Displays if the DLS region CPU utilization is > nn%.

CPU (High) Regions

CSLO Displays if the DLS region CPU utilization is < nn%.

CPU (Low) Regions

CSVC Displays when IMS control task is waiting in SVC code.

IMS Status (Alerts)

IMS Status

CUOW Displays when one Fast Path region is in unit-of-work contention with another Fast Path region.

Fast Path (Alerts)

Fast Path

DBWE Displays when an I/O error against a database has occurred.

Databases (Alerts)

Databases

DCMN Displays when IMS DC monitor is active.

Traces (Alerts) Traces

DDHI Displays when the dataspace DASD I/O per second is > nn.

The value of nn is the average dataspace read + write rate for a dataspace.

Fast Path (High)

Fast Path

DDLO Displays when the dataspace DASD I/O per second is < nn.

The value of nn is the average dataspace read + write rate for a dataspace.

Fast Path (Low)

Fast Path


Exception ID


Status Light



DISP Displays when the dispatching priority of OMEGAMON is <= the dispatching priority of IMS.

IMS Status (Alerts)

IMS Status

DLTR Displays when the DL/I trace table is on.


DMBE Displays the names of the databases that have dynamic backout errors.

Databases (Alerts)

Databases

DMER Displays when a Fast Path DEDB area has an I/O error.

Fast Path (Alerts)

Fast Path

DMFF Displays when free space in DMB pool is fragmented.


DNRS Displays if an I/O issued to a DASD device allocated to the IMS control region took longer than one OMEGAMON cycle to complete.

Resources (Alerts)

I/O

DRDY Displays when DASD device drops ready.

Resources (Alerts)

I/O

DSHI Displays when the dataspace I/O per second is > nn.

The value of nn is the average dataspace read + write rate.

Fast Path (High)

Fast Path

DSLO Displays when the dataspace I/O per second is < nn.

The value of nn is the average dataspace read + write rate.

Fast Path (Low)

Fast Path

DSPI No areas are loaded in the dataspace.

Fast Path (Alerts)

Fast path

DSTR Displays when dispatcher trace is on.


DSWP Displays when a dependent region is swapped out.

Resources (Alerts)

Regions

ESNC Displays when an external subsystem is defined to the control region, but not to any dependent region.

External Subsystem (Alerts)

DB2

ESND Displays when an external subsystem is defined to a dependent region, but not to the control region.

External Subsystem (Alerts)

DB2


Exception ID


Status Light



ESTH Displays when the number of active threads for an external DB2® subsystem is > nn.

External Subsystem (High)

DB2

FDBW Displays if the database work pool largest free block is < nn bytes.

Fragmentation (Low)

Pools

FDMB Displays if the database management block (DMB) pool largest free block is < nn bytes.

Fragmentation (Low)

Pools

FEPC Displays if the extended PCB pool largest free block is < nn bytes in IMS systems generated with Fast Path.

Fragmentation (Low)

Pools

FPSB Displays if the PSB pool’s largest free block is < nn bytes.

Fragmentation (Low)

Pools

FPSW Displays if the PSBW largest free block is < nn bytes.

Fragmentation (Low)

Pools

FPTR Displays if there is a Fast Path region, there is activity in the FP region, and the Fast Path trace is on.


HSBH Displays if the HSSP private area buffer pool usage is > nn%.

Fast Path (High)

Fast Path

HSBL Displays if the HSSP private area buffer pool usage is < nn%.

Fast Path (Low)

Fast Path

IBHI Displays if the BMP region I/O rate is > nn EXCPs per second over the last OMEGAMON cycle.

I/O Rates (Regions High)

Regions

IBLO Displays if the BMP region I/O rate is < nn EXCPs per second over the last OMEGAMON cycle.

I/O Rates (Regions Low)

Regions

ICHI Displays if the control region I/O rate is > nn EXCPs per second over the last OMEGAMON cycle.


Regions

ICLO Displays if the control region I/O rate is < nn EXCPs per second over the last OMEGAMON cycle.


Regions

ILHI Displays if the IRLM region I/O rate is > nn EXCPs per second over the last OMEGAMON cycle.


Regions


Exception ID


Status Light



ILLO Displays if the IRLM region I/O rate is < nn EXCPs per second over the last OMEGAMON cycle.


Regions

INAC Displays when IMS is inactive. IMS Status (Alerts)

IMS Status

IORC Displays if a device allocated to IMS is in I/O error recovery.

Resources (Alerts)

I/O

IRCS Displays if IRLM’s CSA usage is > nn% of MAXCSA.

Resources (High)

Regions

IRFC Displays when the false contention rate is > 70 per second.

Note: This only applies to IRLM version 2.1 and above.

Resources (High)

IMS Status

IRGC Displays when IRLM is not connected to a data sharing group.

Note: This only applies to MVS version 5.1 and above.

Resources (Alerts)

IMS Status

IRHI Displays if the DBRC region I/O rate is > nn EXCPs per second during the last OMEGAMON cycle.


Regions

IRIN Displays when the required IRLM is not available for IMS.

Note: This applies only to IRLM version 2.1 and above.

Resources (Alerts)

IMS Status

IRLO Displays if the DBRC region I/O rate is < nn EXCPs per second during the last OMEGAMON cycle.


Regions

IRQH Displays when the number of IRLM locks by region exceeds the threshold.


Regions

IRRC Displays when the real contention rate is > 70 per second.


Resources (High)

IMS Status

Displays when IRLM RLE usage is > 70%.


Resources (High)

IMS Status

IRTP Displays when the IRLM pass-the-buck (PTB) trace is active.



Exception ID


Status Light



IRTR Displays when the IRLM resource handler (RH) trace is active.


ISHI Displays if the DLS region I/O rate is > nn EXCPs per second during the last OMEGAMON cycle.


Regions

ISLO Displays if the DLS region I/O rate is < nn EXCPs per second during the last OMEGAMON cycle.


Regions

LALO Displays if the LSQA storage assurance is < nn K.

Virtual Storage (Low)

Regions

LDMB Displays if the DMB pool blocks loaded is >= nn%.

Pools (DMB) Pools

LKTR Displays if the lock trace is on. Traces (Alerts) Traces

LLBR Displays if the OLDS buffer waits per second are > nn.

Logging (OLDS)

Logging

LLCH Displays if the WADS checkwrite requests per second are > nn.

Logging (WADS High)

Logging

LMLO Displays if the LSQA maximum free block size is < nn K.


Regions

LPEX Displays if the the number of writes to WADS is > nn per second.

Logging (WADS High)

Logging

LPOR Displays if the OLDS reads (dynamic backout) are > nn per second.

Logging (OLDS)

Logging

LPOW Displays if the OLDS writes are > nn per second.

Logging (OLDS)

Logging

LPSB Displays if the PSB pool blocks loaded is >= nn%.

Pools (PSB) Pools

LSLO Displays if the LSQA total free storage is < nn K.


Regions

LTWA Displays if the log tape write-ahead is not active.

Resources (Alerts)

Logging


Exception ID


Status Light



Mnnn These are dynamic exceptions you create using the MSGD command. They display when they detect special IMS message numbers on the log.

Note: You can see these exceptions only in the menu/command interface.

For more information, See the MSGD command in the OMEGAMON II for DBCTL Realtime Commands Reference Manual.

n/a IMS Status

MSGE Displays when the ICNS command has not been issued.

IMS Status (Alerts)

IMS Status

NOFB Displays when a region is in buffer wait due to a lack of Fast Path buffers.

Fast Path (Alerts)

Fast Path

NOOT Displays when all output threads are in use and there are buffers queuing up for OTHRs.

Fast Path (Alerts)

Fast Path

NPDL Displays when there is no parallel DL/I.

IMS Status (Alerts)

IMS Status

NQRE Displays when a RECON dataset is enqueued by another job.

Resources (Alerts)

IMS Status

OBAU Displays when a region is currently using the Fast Path overflow buffer allocation.

Fast Path (Alerts)

Fast Path

ODIE Displays when less than three OLDS are still active.

Logging (Alerts)

Logging

OHLO Displays when the ISAM/OSAM hit ratio is <nn%.

Buffer Pools Buf. Pools

OLER Displays when OLDS nn has encountered a write I/O error.

Logging (Alerts)

Logging

OLNA Displays when OLDS auto archiving is not active.

Logging (Alerts)

Logging

OLST Displays when OLDS nn is stopped.

Logging (Alerts)

Logging

ONLC Displays when an online change is in progress.

IMS Status (Alerts)

IMS Status


Exception ID


Status Light



ONLO Displays when an online change has occurred.

IMS Status (Alerts)

IMS Status

ORER Displays when the number of OLDS with I/O errors is > nn.

Logging (OLDS)

Logging

ORIP Displays when the number of OLDS inactive is > nn.

Logging (OLDS)

Logging

ORST Displays when the number of OLDS that have been stopped is > nn.

Logging (OLDS)

Logging

OSBL If there are any ISAM/OSAM database buffer pools locked due to a write error, OSBL displays the number that are locked.


OSDN Displays when:There is only one OLDS available.The rest of the OLDS have been stopped or have write errors.IMS is terminating because the last available OLDS is damaged.

Logging (Alerts)

Logging

OXHI Displays when the OSAM database dataset EXCP rate is > the user-specified limit.

Note: This applies to all OSAM databases.

Databases (Alerts)

Databases

OXLO Displays when the OSAM database dataset EXCP rate is < the user-specified limit.

Note: This applies to all OSAM databases.

Databases (Alerts)

Databases

PBTR Displays when PSB trace facility is on.


PIBC Displays if the BMP common area page-in rate is > nn per second during the last OMEGAMON cycle.

Virtual Storage (Page-In Rates)

Regions

PIBP Displays if the BMP private area page-in rate is > nn per second during the last OMEGAMON cycle.


Regions

PICC Displays if the common area page-in rate for the control region is > nn per second during the last OMEGAMON cycle.


Regions


Exception ID


Status Light



PICP Displays if the private area page-in rate for the control region is > nn per second during the last OMEGAMON cycle.


Regions

PIDC Displays if the common area page-in rate for DBRC is > nn per second during the last OMEGAMON cycle.


Regions

PIDP Displays if the private area page-in rate for DBRC is > nn per second during the last OMEGAMON cycle.


Regions

PILC Displays if the common area page-in rate for IRLM is > nn per second during the last OMEGAMON cycle.


Regions

PILP Displays if the private area page-in rate for IRLM is > nn per second during the last OMEGAMON cycle.


Regions

PIQH Displays if the number of PI enqueue locks held by the indicated thread is > nn.

Locks Regions

PISC Displays if the common area page-in rate for the DLS region is > nn per second during the last OMEGAMON cycle.


Regions

PISP Displays if the private area page-in rate for the DLS region is > nn per second during the last OMEGAMON cycle.


Regions

PITR Displays when the program isolation trace facility is on.


PSVC Displays when IMS physical logger task waiting in SVC code.

Resources (Alerts)

IMS Status

RDSH Displays if the restart dataset I/O rate is > nn per second.

I/O Rates (Datasets)

I/O

RGNW Displays when region waiting time is > nn minutes.

Regions Regions

RGSH Displays when checkpoints taken for an IMS BMP are > nn.

Regions Regions

RGSI Displays when the region sync point interval is > nn minutes.

Regions Regions


Exception ID


Status Light



RSRV Displays when there is no VTAM connection to the RSR Tracking System.

The VTAM connection between the ACTIVE IMS and the TRACKING IMS is not available. This is only available from the ACTIVE IMS.

Note: Because the TRACKING IMS can function for multiple ACTIVE IMS systems, we cannot identify an IMS that is not connected but should be.

IMS Status (Alerts)

IMS Status

SCTR Displays if the scheduler trace is active.


SDLO Displays when the number of free CIs in the sequential dependent part of the DEDB area is < nn%.

Fast Path (Low)

Fast Path

Tnnn This is a dynamic exception that you create using the THIN command. This exception displays when it detects that a CCTL has exceeded its percentage of threads in use threshold.

For more information, see the THIN command in the OMEGAMON II for DBCTL Realtime Commands Reference Manual.

n/a Threads

TCOT Displays if the time controlled operations (TCO) trace is active.


THHI Displays if the number of active threads is > nn.

Threads (High) Threads

THHP Displays if the number of active threads is > nn% of all available threads.

Threads (High) Threads

THLO Displays if the number of active threads is < nn.

Threads (Low) Threads

THLP Displays if the number of active threads is < nn% of all available threads.

Threads (Low) Threads


Exception ID


Status Light



TMSI Displays when the Transport Manager Subsystem (TMS) is not active.

Note: This will also cause a break in the VTAM connection.

Without TMS, you cannot re-establish the VTAM connection from the ACTIVE IMS to the TRACKING IMS.

IMS Status (Alerts)

IMS Status

TNRS Displays if a tape device is not responding to an I/O request.

Resources (Alerts)

I/O

TPSB This is a dynamic exception that you create using the TTIM command. This exception displays when it detects that a PSB has exceeded a time threshold.

Note: You can see this exception only in the command/menu interface.

For more information, see the TTIM command in the OMEGAMON II for DBCTL Realtime Commands Reference Manual.

n/a Programs

TRDY Displays if a tape device drops ready.

Resources (Alerts)

I/O

VCAS Displays when database VSAM control area splits are > nn per minute.

VSAM Databases

VCIS Displays when database VSAM control interval splits are > nn per minute.

VSAM Databases

VHLO Displays when the VSAM hit ratio is <nn%.

Buffer Pools Buf.Pools

VMEX Displays if the number of extents for the VSAM dataset is increasing.

VSAM (Alerts) Databases

VMLO Displays when IMSCTL maximum private free block size is < nn K.


Regions

VROQ Displays when logical terminal is unable to receive output.

IMS Status (Alerts)

IMS Status


Exception ID


Status Light



VSLO Displays when IMSCTL total private free block size is < nn K.


Regions

VTLO Displays when IMSCTL top free block size is < nn K.


Regions

VWRC Displays if the VSAM writecheck is ON for a database.

VSAM (Alerts) Databases

VXHI Displays when the VSAM database dataset EXCP rate is > the user-specified limit.

Note: This applies to all VSAM databases.

Databases (Alerts)

Databases

VXLO Displays when the VSAM database dataset EXCP rate is < the user-specified limit.

Note: This applies to all VSAM databases.

Databases (Alerts)

Databases

WBHI Displays when BMP working set size is > nn K.

Working Sets (High)

Regions

WBLO Displays when BMP working set size is < nn K.

Working Sets (Low)

Regions

WCHI Displays when the control region working set size is > nn K.

Working Sets (High)

Regions

WCLO Displays when the control region working set size is < nn K.

Working Sets (Low)

Regions

WDNA Displays when the write-ahead datasets (WADS) are inactive.

Logging (Alerts)

Logging

WDNB Displays when the number of spare WADS remaining is < nn.

Logging (WADS Low)

Logging

WLHI Displays when IRLM working set size is > nn K.

Working Sets (High)

Regions

WLLO Displays when IRLM working set size is < nn K.

Working Sets (Low)

Regions

WRHI Displays when DBRC working set size is > nn K.

Working Sets (High)

Regions

WRLO Displays when DBRC working set size is < nn K.

Working Sets (Low)

Regions


Exception ID


Status Light



WSHI Displays when DLS working set size is > nn K.

Working Sets (High)

Regions

WSLO Displays when DLS working set size is < nn K.

Working Sets (Low)

Regions

XCNF Displays when a Program Isolation (PI) or IMS/VS Resource Lock Manager (IRLM) resource conflict exists.

Locks (Alerts) Conflicts

XRAT Displays when XRF automatic takeover is not active.

XRF (Alerts) XRF

XRAV Displays when XRF availability manager is not active.

XRF (Alerts) XRF

XRIP Displays when I/O prevention is in progress on the active IMS system.

XRF (Alerts) XRF

XRIT Displays when I/O toleration is in progress on the standby IMS system.

XRF (Alerts) XRF

XRNS Displays when XRF surveillance is not active.

XRF (Alerts) XRF

XRPH Displays when the number of PSTs held on the standby system is > nn.

XRF XRF

XRSR Displays when no secondary RDS is allocated.

XRF (Alerts) XRF

XRTO Displays when an XRF takeover is in progress.

XRF (Alerts) XRF


Exception ID


Status Light



Fast Paths 249

Fast Paths

IntroductionThis appendix lists the fast paths you can use to move directly to a panel.

Appendix ContentsUsing Fast Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

C

Using Fast Paths


Using Fast Paths

IntroductionFast path is a way to move directly to a panel instead of navigating through a series of panels to reach the one you want.

1. Tab over to Options on the Action Bar and press Enter.

2. Key in 2 (Set Preferences) and press Enter.

3. Set mnemonics to ON and press Enter. Exit from this panel.

4. Now you can use a Fast path from any panel that has an Action Bar.Enter the mnemonic string in the home entry field at the upper left of the panel and press Enter.

5. You will see the panel you selected.

Mnemonic Go To

GB/G1 Buffer Pools

GD/G2 Databases

GO/G3 I/O

GS/G4 System Status

GC/G5 Zoom to underlying OMEGAMON session

GI/G6 Index

The following mnemonics are in the Index

GIT Traces

GIB DB2

GII I/O

GIX XRF

GIO OSAM Pools

GIV VSAM Pools

GID Databases

GIP Storage Pools

GIL Logging

GIN Conflicts

GIF FastPath Status

GI% Device Statistics

GI( Logging Buffers and Status

GI/ Logging Details

Fast Paths 251

Using Fast Paths

GI# Conflicts CI

GI* Conflicts Latch

GIC CPU

GIS Virtual Storage

GIR Regions

GI1 Databases OP

GI3 Logging OP WADS

GI+ Logging OP OLDS

GI5 Programs OP

GI7 Regions OP

GI@ Pools Description

From the Options pull-down, select Issue IMS Queries.

Under IMS Startup Parameters and Overrides you will see a new item: Expandable Storage Pool Upper Limits.

Use any one of the following mnemonics for this item; each one takes you to the same popup.

OISE OIS5 OI1E O5SE

O5S5 O51E O515

Mnemonic Go To

Using Fast Paths


Guide to Candle Customer Support 253

Guide to CandleCustomer Support

IntroductionCandle Corporation is committed to producing top-quality software products and services. To assist you with making effective use of our products in your business environment, Candle is also committed to providing easy-to-use, responsive customer support.

Precision, speed, availability, predictability—these terms describe our products and Customer Support services.

Included in this Guide to Candle Customer Support is information about the following:

Base Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254– Telephone Support

– eSupport

– Description of Severity Levels

– Service-level objectives

– Recording and monitoring calls for quality purposes

– Customer Support Escalations

– Above and Beyond

Enhanced Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258– Assigned Support Center Representative (ASCR)

– Maintenance Assessment Services (MAS)

– Multi-Services Manager (MSM)

Customer Support Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . 260– Link to Worldwide Support Telephone and E-mail information

D

Base Maintenance Plan



OverviewCandle offers a comprehensive Base Maintenance Plan to ensure that you realize the greatest value possible from your Candle software investments. We have more than 200 technicians providing support worldwide, committed to being responsive and to providing expedient resolutions to support requests. Technicians are available worldwide at all times during the local business day. In the event of an after-hours or weekend emergency, our computerized call management and forwarding system will ensure that a technician responds to Severity One situations within one hour. For customers outside of North America, after-hours and weekend support is provided in English language only by Candle Customer Support technicians located in the United States.

Telephone supportCandle provides consistently reliable levels of service—thanks to our worldwide support network of dedicated experts trained for specific products and operating systems. You will always work with a professional who truly understands your problem.

We use an online interactive problem management system to log and track all customer-reported support requests. We give your support request immediate attention by routing the issue to the appropriate technical resource, regardless of geographic location.

Level 0 Support is where your call to Candle Customer Support is first handled. Your support request is recorded in our problem management system, then transferred to the appropriate Level 1 support team. We provide Level 0 manual interaction with our customers because we support more than 170 products. We feel our customers would prefer personal interaction to a complex VRU or IVR selection menu.

Level 1 Support is the service provided for initial support requests. Our Level 1 team offers problem determination assistance, problem analysis, problem resolutions, installation assistance, and preventative and corrective service information. They also provide product usage assistance.

Level 2 Support is engaged if Level 1 cannot provide a resolution to your problem. Our Level 2 technicians are equipped to analyze and reproduce errors or to determine that an error is not reproducible. Problems that cannot be resolved by Level 2 are escalated to Candle’s Level 3 R&D support team.

Level 3 Support is engaged if a problem is identified in Candle product code. At Level 3, efforts are made to provide error correction, circumvention or notification that a correction or circumvention is not available. Level 3 support provides available maintenance modifications



and maintenance delivery to correct appropriate documentation or product code errors.

eSupportIn order to facilitate the support process, Candle also provides eSupport, an electronic full-service information and customer support facility, using the World Wide Web at www.candle.com/support/. eSupport allows you to open a new service request and update existing service requests, as well as update information in your customer profile. New and updated service requests are queued to a support technician for immediate action. And we can respond to your request electronically or by telephone—it is your choice.

eSupport also contains a continually expanding knowledge base that customers can tap into at any time for self-service access to product and maintenance information.

The Candle Web Site and eSupport can be accessed 24 hours a day, 7 days a week by using your authorized Candle user ID and password.

Description of Candle severity levelsResponses to customer-reported product issues and usage questions are prioritized within Candle according to Severity Code assignment. Customers set their own Severity Levels when contacting a support center. This ensures that we respond according to your individual business requirements.

Severity 1 Crisis

A crisis affects your ability to conduct business, and no procedural workaround exists. The system or application may be down.

Severity 2High

A high-impact problem indicates significant business effect to you. The program is usable but severely limited.

Severity 3Moderate

A moderate-impact problem involves partial, non-critical functionality loss or a reasonable workaround to the problem. A “fix” may be provided in a future release.

Severity 4Low

A low-impact problem is a “how-to” or an advisory question.

Severity 5Enhancement Request

This is a request for software or documentation enhancement. Our business units review all requests for possible incorporation into a future release of the product.

http://www.candle.com/support/



Candle has established the following service-level objectives:

Recording and Monitoring Calls for Quality PurposesCandle is committed to customer satisfaction. To ensure that our customers receive high levels of service, quality and professionalism, we’ll monitor and possibly record incoming and outgoing Customer Support calls. The information gleaned from these calls will help us serve you better. If you prefer that your telephone call with Candle Customer Support in North America not be monitored or recorded, please advise the representative when you call us at (800) 328-1811 or (310) 535-3636.

Customer Support EscalationsCandle Customer Support is committed to achieving high satisfaction ratings from our customers. However, we realize that you may occasionally have support issues that need to be escalated to Candle management. In those instances, we offer the following simple escalation procedure:

If you experience dissatisfaction with Candle Customer Support at any time, please escalate your concern by calling the Candle support location closest to you. Ask to speak to a Customer Support manager. During standard business hours, a Customer Support manager will be available to talk with you or will return your call. If you elect to hold for a manager, you will be connected with someone as soon as possible. If you wish a return call, please tell the Candle representative coordinating your call when you will be available. After contacting you, the Customer Support manager will develop an action plan to

Call Status Severity 1 Goal

Severity 2 Goal

Severity 3 Goal

Severity 4 Goal

Severity 5Goal

First Call Time to Answer

90% within one minute

Level 1 Response

(Normal Business Hours)

90% within 5 minutes

90% within one hour

Level 2 Response

(Normal Business Hours)

Warm Transfer

90% within two hours

90% within eight hours

Scheduled follow-up (status update)

Hourly or as agreed

Daily or as agreed

Weekly or as agreed Notification is made when an enhancement is incorporated into a generally available product.

Notification is made when a fix is incorporated into a generally available product.

The above information is for guideline purposes only. Candle does not guarantee or warrant the above service levels. This information is valid as of October 1999 and is subject to change without prior notice.



resolve your issue. All escalations or complaints received about support issues are logged and tracked to ensure responsiveness and closure.

Above and BeyondWhat differentiates Candle’s support services from our competitors? We go the extra mile by offering the following as part of our Base Maintenance Plan:

n Unlimited multi-language defect, installation and operations support

n eSupport using the World Wide Web

n Regularly scheduled product updates and maintenance provided at no additional charge

n Over 200 specialized technicians providing expert support for your Candle products

Enhanced Support Services



OverviewOur Base Maintenance Plan provides a high level of software support in a packaged offering. However, in addition to this plan, we have additional fee-based support services to meet unique customer needs.

The following are some examples of our added-value support services:

n Assigned Support Center Representative Services (ASCR)

– An assigned focal point for managing support escalation needs

– Proactive notification of available software fixes

– Proactive notification of product version updates

– Weekly conference calls with your ASCR to review active problem records

– Monthly performance reviews of Candle Customer Support service levels

– Optional on-site visits (extra charges may apply)

n Maintenance Assessment Service (MAS)

– On-site assessment services

– Advice about product maintenance and implementation

– Training your staff to develop efficient and focused procedures to reduce overall cost of ownership of your Candle software products

– Analysis of your Candle product environment: versions, updates, code correction history, incident history and product configurations

– Reviews to ensure that purchased Candle products and solutions are used effectively

n Multi-Services Manager (MSM)

Multi-Services Manager provides highly valued services to customers requiring on-site full time expertise to complement their technical resources.

– Dedicated on-site Candle resource (6 months or one year) at your site to help ensure maximum use and effectiveness of your Candle products

– Liaison for all Candle product support activities, coordination and assistance with implementation of all product updates and maintenance releases

– Works with your staff to understand business needs and systems requirements



– Possesses technical and systems management skills to enhance your staff’s knowledge and expertise

– Other projects as defined in Statement of Work for MSM services

Customer Support Contact Information


Customer Support Contact Information

Link to Worldwide Support Telephone and E-mail informationTo contact Customer Support, the current list of telephone numbers and e-mail addresses can be found on the Candle Web site, www.candle.com/support/.

Select Support Contacts from the list on the left of the page.

http://www.candle.com/support/

Index 261

Symbols# in column 1 132&ZXcccV 149&ZXcccW 149) in column 1 124, 125+ at end of line 119, 132.CN immediate 153.D

immediate 130.DCL immediate 129.DD immediate 130.DEF immediate

HO 140OFF 140ON 140

.EXM immediate 127, 188

.FGOimmediate 144, 145routine testing 145

.I immediate 129

.ILC immediate 126, 127

.LOG immediateON 134OUT 134POP 145PUSH 145

.LOGPOP 145

.LOGPUSH 145

.MIN immediate 127

.MJ immediate 127

.MJC immediate 127

.MJI immediate 127

.MMA immediate 127

.PFK immediate 130, 132

.PRT immediate 135

.RC immediate 132

.SCRN immediate 141

.SET immediate 135

.SGO immediate 144, 150

.VAR immediate 140, 150/ in column 1 124/BOTTOM INFO-line 128/C profile 84/D INFO-line 128/DCL INFO-line 129/DEF INFO-line

HOLD 140OFF 140ON 140

/DOWN INFO-line 128/I profile 84/LOG INFO-line

ON 134OUT 134

/P 135/PRINT INFO-line 135/REP INFO-line 139/SAVE INFO-line 139, 140/STOP INFO-line 114/TOP INFO-line 128/U INFO-line 128/UP INFO-line 128/ZOOM INFO-line 151> in column 1 119, 139? in column 1 124

AA on INFO-line 119ABUF exception 234ACBH exception 234accessing

command interface 28, 116CUA interface 28menu interface 28, 103

ACEA exception 234ACES exception 234ACEW exception 234ACEX exception 234action bar

GoTo 46Help 50keyword functions 45Options 48pop-up windows 41pull-down menus 45

action bar 40using 45View 48

action codes 52Actions pull-down 45ADBW exception 234ADHI exception 234

Index


ADLO exception 234ADMB exception 234Adobe portable document format 17ADSU exception 235advanced functions 52

action codes 52short-cut 52

AEPC exception 235alerts, customizing 87all clear message, customizing 224analysis

exception 223APIE exception 235APSB exception 235APSW exception 235argument 123

command 123extended 123

ASAP exception 235ASCR

assigned support center representative 258ASHI exception 235ASLO exception 235assigned support center representative

ASCR 258attributes for exception messages 228automatic screen facility (ASF) 144, 223, 227

activating 94on INFO-line 119

automatic update 219cycles 95suspending 140

availability manager not active 247AWKP exception 235

BB on INFO-line 119batch message processing

exceptions 242, 246beep on critical exception character 86beep, controlling 82bell

activating 94setting interval 95status on INFO-line 119

block deletion, .DD 130blue status indicator 69, 85BMP

exceptions 235, 238region I/O rate 238swapped out 237

bottleneck analysis 158, 167

summary 165bottleneck analysis component (DEXAN) 32Bottleneck Analysis panel 167bottlenecks summary panel 165Box XACB parameter 228BQHI exception 235BQLO exception 235buffer pool usage, HSSP

HSBH exception 238HSBL exception 238

CCandle-supplied profile 84CBHI exception 235CBLO exception 235CCHI exception 235CCLO exception 235characters for status indicators 69CICS and DBCTL 184CILO exception 236CIs, number of free 244clear screen command (.. ) 128CLHI exception 236CLLO exception 236collector

bottleneck analysis 163colon 120color

of status indicators 69on panels 42options for exception message 228

Color Settings menu 95command

accessing menu 28, 46argument 123clear screen 128entry 46format 122help 124, 125, 126, 127immediate, list 127INFO-line 119, 127input, multi-line 120interface 26, 153limiting major command listing 127logging 134major, list 127minor, list 127name 123options 132output

continuing 132setting case 94

Index 263

parameters, entering 123type

immediate 121, 122INFO-line 121major 121minor 122

command interface 26accessing 28, 116panel format 118processing order 118screen control 128

command/menu interface 217accessing 160

commentcharacter (>) 119, 139deleting 129entering 119line 119, 139

common area page-in rate forDBRC region 243DLS region 243IRLM region 243

communications external subsystem poolexceptions 234

components of OMEGAMON IIbottleneck analysis component (DEXAN) 32historical component (EPILOG) 32

configuring profiles 94conflicts, database access 181console

control 153panel use 79secondary 153

continuation character 124# 132+ 119, 132

control regionCPU utilization 235I/O rate 238low

dataset going into multiple extents 245top free block size in private 246total private free storage 246

working set size 246controls 49, 85

beep on critical exception status bar character 86blue status bars displayed 85green status bar character 86green status bars displayed 85interval refresh period 85red status bar character 86response wait period 85yellow status bar character 86

correcting problems 34count of items selected by a major command 132CPSER 149CPU

serial number 149CPUA exception 236creating profiles 91CRHI exception 236CRLO exception 236CSHI exception 236CSLO exception 236CSR up/down scrolling 128CSVC exception 236CUA interface

accessing 28navigating 28navigation 45options 82panel appearance 40

highlighting 42panel body 40pop-up window 41pull-down menu 41pushbutton area 41scrolling 43

Cumulative= XACB parameter 229CUOW exception 236CURS on INFO-line 139cursor

movement 42pointing feature 151saving position in screen spaces 139

customer supportbase maintenance plan 254contact information 260enhanced support services 258eSupport 255severity levels 255telephone support 254

customizing exceptions 87customizing messages 224Cycle XACB parameter 229

DDASD

device dropped ready 237data

entry database area unavailable 235data sharing group connection 239database

dynamic backout error alert 237I/O error exception 236


management block (DMB) 234pool 238

OSAM 242VSAM 246VSAM control

area splits 245interval splits 245

work pool 234FDBW exception 238

database access 174Database Conflicts panel 181database lock 192database locks

IRLM 192PI 192viewing details 192

datasetrestart 243

dataspaceareas 237DASD I/O 234, 236I/O 235, 237

datedisplaying 83format 83, 94on INFO-line 119

DBRCregion

common area page-in rate 243I/O rate 239utilization 236

working set size 246DBWE exception 236DCMN exception 236DDHI exception 236DDLO exception 236DEDB area

independent overflow exception 236dedicated mode 220definition mode 139, 140definition of PF keys 113delay processing 133deleting

block 130comment lines 129lines 129menu/command component of user profile 93screen spaces 143

DELT immediate 143Describe a User Profile screen 93details, showing 40device

I/O error recovery 239

name table entries 95number 150

DEXAN component 32DIR 149direct transfer 65director in cross system mode 149DISP exception 237dispatcher trace

status 237dispatching

priority 237display

continuation lines 132printing 134symbols 119XACB parameter 228

DL/I calls 193details panel 193

DL/I trace tablestatus 237

DL/I, no parallel 241DLS

regioncommon area page-in rate 243I/O rate 240utilization 236

working set size 247DLTR exception 237DMB

pool blocks loaded 240DMB pool, fragmented 237DMBE exception 237DMER exception 237DMFF exception 237DNRS exception 237DRDY exception 237DSHI exception 237DSLO exception 237DSPI exception 237DSTR exception 237DSWP exception 237dynamic exceptions 241dynamic profile update facility 99

EEPILOG

component of OMEGAMON II 32historical component 32interfaces 27

ESNC exception 237ESND exception 237ESTH exception 238eSupport

Index 265

customer support 255exceeding threshold 87, 222exception

abbreviated status display 229ABUF 234ACBH 234ACBLIB 234ACEA 234ACES 234ACEW 234ACEX 234ADBW 234ADHI 234ADLO 234ADMB 234ADSU 235AEPC 235analysis 223APIE 235APSB 235APSW 235ASAP 235ASHI 235ASLO 235AWKP 235batch message processing 242, 246BMP 235, 238boxing 228BQHI 235BQLO 235CBHI 235CBLO 235CCHI 235CCLO 235CILO 236CLHI 236CLLO 236color 228communication external subsystem pool 234controlling an individual 227CPUA 236CRHI 236CRLO 236CSHI 236CSLO 236CSVC 236CUOW 236database

management block 234OSAM 242VSAM 246work pool 234

dataspacearea I/O 235DASD I/O 234, 236I/O 237

DBWE 236DCMN 236DDHI 236DDLO 236DISP 237DLTR 237DMBE 237DMER 237DMFF 237DNRS 237DRDY 237DSHI 237DSLO 237DSPI 237DSTR 237DSWP 237ESNC 237ESND 237ESTH 238execution reordering 230FDBW 238FDMB 238FEPC 238forcing display 229FPSB 238FPSW 238FPTR 238frequency for checking 229HSBH 238HSBL 238IBHI 238IBLO 238ICHI 238ICLO 238ILHI 238ILLO 239INAC 239investigating 176, 223IORC 239IRCS 239IRHI 239IRIN 239IRLM 239IRLO 239IRQH 239IRTP 239IRTR 240ISHI 240


ISLO 240LALO 240LDMB 240limit checking 229limiting list by group 229listing 229LKTR 240LLBR 240LLCH 240LMLO 240logging facility (XLF) 134, 223, 227

activating 94setting parameters 229

LPEX 240LPOR 240LPOW 240LPSB 240LSLO 240LTWA 240message 222Mnnn 241MSGE 241NOFB 241NOOT 241NPDL 241NQRE 241OBAU 241ODIE 241OHLO 241OLDS 240OLER 241OLNA 241OLST 241ONLC 241ONLO 242ORER 242ORIP 242ORST 242OSBL 242OSDN 242output reordering 230OXHI 242OXLO 242PBTR 242PIBC 242PIBP 242PICC 242PICP 243PIDC 243PIDP 243PILC 243PILP 243

PIQH 243PISC 243PISP 243PITR 243private area 243PSB 235PSVC 243RDSH 243RGNW 243RGSH 243RGSI 243RSRV 244SCTR 244SDLO 244stop checking 229systemwide 222TCOT 244terse output 229testing 222THHI 184, 244THHP 244THLO 184, 244THLP 244threshold 222, 228TMSI 245Tnnn 244TNRS 245TPSB 245TRDY 245tripped 74, 186, 222, 224VCAS 245VCIS 245VHLO 245VMEX 245VMLO 245VROQ 245VSLO 246VTLO 246VWRC 246VXHI 246VXLO 246WBHI 246WBLO 246WCHI 246WCLO 246WDNA 246WDNB 246WLHI 246WLLO 246WRHI 246WRLO 246WSHI 247

Index 267

WSLO 247XCNF 247XRAT 247XRAV 247XRIP 247XRIT 247XRNS 247XRPH 247XRSR 247XRTO 247

exception analysis 108, 222customizing 226defining IMS messages for 230groups 224

defining 226switches 227

history of tripped exceptions 225immediate command 227LEXC immediate 230starting 224summary 224systemwide 109, 224XIMS 224

exception group 88Exception mappings 69exceptions, customizing 87exiting OMEGAMON II 31EXNCYC= XACB parameter 229export profile 99extended

PCB pool 235, 238external

subsystem 237, 238

Ffalse contention rate 239Fast Path

BQHI exception 235BQLO exception 235DEDB area I/O error 237exceptions

CIs, number of free 244FP region UOW contention 236output threads 241region in buffer wait 241region using Fast Path OBA 241

trace on 238Fast Paths 250FDBW exception 238FDMB exception 238features, advanced 147FEPC exception 238

fetching screen spaces 144FGOLOOP keyword 145field

argument 123command name 123label 123parameter 123selecting 40

filtering data 48FORCE XACB keyword 229FP region UOW contention 236FPSB exception 238FPSW exception 238FPTR exception 238free space

DMB pool, fragmented 237function key area 41function keys 52

command interface 130displaying 83in help 51in the CUA interface 43in the menu interface 113reinitializing after reset 111using 43

functionsadvanced 52

GGDFN immediate 224, 226general help menu 110GoTo pull-down 46graphical interface 26greater-than sign 119, 139green status indicator 69

character 86displayed 85

GROUPXACB keyword 229XGSW keyword 227XSUM keyword 225XTRP keyword 225

groupDMB, creating 200exception analysis 224PSB, creating 200switches 227

groups of IMS resources, managing 198

HH in column 1 127Help


about the current release 50, 51context sensitive 50glossary 50index 50menu 110panel level 50pull-down menu 50screens 110

help 124added information 124extended 124function keys in 51immediate commands 124INFO-line commands 126major commands 124minor commands 124one-line 124symbols 124

highlighting on panels 42historical component

EPILOG 32interfaces 27

History of All Tripped Exceptions display 225hold screen display 133HSBH exception 238HSBL exception 238

II/O

contention 169DELAY message 133error to database 236prevention in progress 247toleration in progress 247

IBHI exception 238IBLO exception 238ICHI exception 238ICLO exception 238ICNS command 230, 241identifying problems 34ILHI exception 238ILLO exception 239immediate commands 122

help 124list 127

implicit action, controlling 83import profile 99IMS 80

command entry 46, 80Command Entry Panel 80commands, issuing 77control task waiting 236

CPU utilization 236DC monitor active 236I/O error recovery alert 239inactive alert 239messages

modifying 231trapping as exceptions 230

monitoring 107physical logger task waiting 243plotting rates 108wait alert 242

IMS command entry 46IMS Direct Transfer 65IMSID 150in column 1 124INAC exception 239individual profile 81INFO-line 119

commands 121, 127components 119help commands 126system ID 119

inputarea on INFO-line 119character (colon) 120

inserting lines 129interface

command 26, 116CUA 26, 40menu 26

intervalrefresh 85setting 95

invoking screen space 138IORC exception 239IRCS exception 239IRFC exception 239IRGC exception 239IRHI exception 239IRIN exception 239IRLM 239

control regionI/O rate 238, 239

CSA usage exception 239locks 239PTB trace 239region

common area page-in rate 243utilization 236

RH trace 240working set size 246

IRLM lock 192IRLM resource conflict 247

Index 269

IRLO exception 239IRQH exception 239IRRC exception 239IRRU exception 239IRTP exception 239IRTR exception 240ISAM/OSAM

database buffer pool locked 242ISHI exception 240ISLO exception 240ISPF

mode 219split-screen 219

Jjobname on INFO-line 119

Llabel field 123LALO exception 240language 83LDMB exception 240LEXC immediate 230lines, inserting and deleting 129LIST

XACB keyword 229XSUM keyword 226XTRP keyword 226

List User Profiles display 92listing screen spaces 141LKTR exception 240LLBR exception 240LLCH exception 240LMLO exception 240lock

IRLM 192lock trace alert 240log

activating 94commands 134control 135screens 134

log tape write-ahead alert 240logging

off menu interface 114status on INFO-line 119

logon parameters 82logon profile 82long-running thread, trapping 194looping, preventing 95low IMSCTL 246low LSQA 240

maximum free block size 240storage assurance 240

LPEX exception 240LPOR exception 240LPOW exception 240LPSB exception 240LROWS parameters 128LSLO exception 240LSQA

maximum free block size 240storage assurance 240total free storage 240

LTWA exception 240

Mmain storage 140, 142maintaining profiles 91, 98maintenance assessment service

MAS 258major command 121

continuing output 132help 124horizontal scrolling 132item count 132list 127output

next line 132skipping lines 132

repeating 132managing IMS 33mapping exceptions to status indicators 69MAS

maintenance assessment service 258MAX up/down scrolling 128MAXTHRD parameter 184menu interface 26, 103

ease-of-use features 110hel 110program function keys 113quick access 111returning from command interface 106stopping 114

menu options, selecting 106menu/command interface

accessing 160menu/command interface operations 217menu/command interface, accessing 28message

boxing 228customizing 224defining 231deleting 231


exception 222exception analysis 230, 232listing 231

MessagesDynamic Profile Update Facility 100

minor commands 122help 124list 127repeating 132setting case 94

MINTHRD parameter 184mnemonic action code 52, 82Mnnn exception 241MODE 149mode of operation 35, 119, 149, 218monitoring

IMS 33system performance 68

moving the cursor 42MSGD command 241MSGE exception 241MSM

multi-services manager 258multiple output lines, viewing 120multi-services manager

MSM 258MVS Modify

for exporting profile 100for importing profile 100

Nnational language 83navigation 28, 42, 45, 111

action bar 45Actions pull-down 45GoTo pull-down 46short-cut 52

navigation, Transplex 55NDSP setting for group switches 227no secondary RDS allocated 247NOFB exception 241NOOT exception 241NPDL exception 241NQRE exception 241number

PSTs held on the standby system 247

OOBAU exception 241ODIE exception 241OHLO exception 241OLDS

exceptions 240OLDS buffer waits 240OLER exception 241OLNA exception 241OLST exception 241OMEGAMON II

command interface 116exiting 31logging screens 134overview 26stopping 114user interfaces 26

OMEGAMON realtime component 32OMEGAVIEW 32omponents of OMEGAMON II

realtime performance component (OMEGAMON) 32

ONLC exception 241ONLO exception 242operands

argument 123operating OMEGAMON II

from the menu/command interface 217operating system level 149operation modes 35Operator Assist 78, 179, 181, 201

regions 190OPSYS 149Options

command 132pull-down menu 48

optionsquick access to menu 111

Options pull-down 48OPTN immediate 134ORER exception 242ORIP exception 242ORST exception 242OSBL exception 242OSDN exception 242OUTP major command 134output

threads 241overview

OMEGAMON II 26OXHI exception 242OXLO exception 242

PPAGE up/down scrolling 128PAGELIMIT keyword 135panel

body 40

Index 271

color 42cursor movement 42format 40, 118

display area 118INFO-line 119input area 118

help 50highlighting 42ID, displaying 82scrolling 43

panel appearancecolor 42highlighting 42pop-up window 41scrolling 43

panel display symbols 119parameters

display 228exception box 228logon 82

PBTR exception 242performance monitoring 33, 68PF keys 43, 130

assigningscreen spaces to

INFO-line commands to 130assigning INFO-line commands to 131assigning screen spaces to 131current assignments 131defining 130, 131definitions 113menu interface 113PF22-PF99 131reinitializing after reset 111using 130

PIresource conflict 247

PI enqueue poolcurrent size 177increment for increasing size 177lockout 181maximum size 177percentage of maximum space used 177size 177space, available 177space, used 177

PI enqueue pool statistics 176PI enqueue pool, allocation 174PI lock 192PIBC exception 242PIBP exception 242PICC exception 242

PICP exception 243PIDC exception 243PIDP exception 243PILC exception 243PI-locking 174PILP exception 243PIQH exception 243PISC exception 243PISP exception 243PITR exception 243Plot IMS Rates display 108plus sign 119, 132PNR major 188POP log argument 145pop-up window 41pound sign 132PPRF immediate 91preferences 49, 82PREFIX 149PRINT INFO-line 135printing

output options 95screen 134, 135screen spaces 134

printing problems 17private area

exception 243exceptions 243

problems, correcting 34product

code 149ID on INFO-line 119version on INFO-line 119

profile 82color options 95configuring 94control function options 95creating 91customizing 82, 84

controls 85exceptions 86preferences 82thresholds 86

describing 93display options 94individual 226listing 92logon 82maintaining 91, 98print options 95profile ID 84saving 93


suffix 150Timed Screen Facility entries 96types 81using 221

Profile menu 91profile, user

deleting menu/command component 93profiles

dynamic profile update facility 99program function (PF) keys 130program isolation

enqueue pool 235trace facility on 243

Program Isolation locking 174program isolation pool use 174Program Specification Block 174PSB 174

definition 198exceptions 235pool 238, 240trace 242work pool 235, 238

PSB group 201bottleneck analysis 167bottleneck analysis summary 165copying 208creating 160, 204, 209deleting from 211name 188selecting name 201starting 213stopping 212

PSBsdetails 181looping 178nonfunctional 178restarting 179, 180status 179stopping 178unusable, viewing 179viewing 181

PST number 188PSTs

number held on the standby system 247PSTs, number available 184PSVC exception 243pull-down menus 45

action bar 41Actions 45GoTo 46Help 50Options 48View 48

PUSH log argument 145pushbutton area 41Pushbuttons 46pushbuttons 46

Qquestion mark (?) in column 1 124quick access to menu options 111

RRDS

no secondary allocated 247RDSH exception 243real contention rate 239realtime performance component

(OMEGAMON) 32RECON dataset 241Reconnection Confirmation panel 29red status bar character 86red status indicator 69refresh interval 85region

buffer wait 241Fast Path OBA 241sync point interval 243waiting time 243

Regions status light 71Regions Summary panel 73remote terminals 219rename screen space 142RENM immediate 142reorder exception output 230repeat lines 132REPORT file 95RESET

XSUM keyword 226XTRP keyword 226

response time problem, resolving 158response wait period 85restart dataset 243RGNW exception 243RGSH exception 243RGSI exception 243RKOIPCSV 141RLE usage 239RSR tracking system

VTAM connection 244RSRV exception 244

SS on INFO-line 119save area

Index 273

prefix exception 235SAVE PPRF option 93save screen space 140Save, Delete, or List Profiles menu 92scenarios

analyzing DBCTL thread activity 184analyzing program isolation pool use 174managing groups of IMS resources 198resolving response time problem 158

scheduler tracestatus 244

screenclearing 128control 128help 110inserting and deleting lines 129logging 135printing 134, 135stacking on INFO-line 119

screen space 137/SAVE INFO-line 140assigning to PF keys 131branching between 144comment line 139conditional fetching 144creating 139, 140creating for zoom 151cursor position 139definition mode 139delayed fetching 144deleting 143editing with text editor 139fetch (.FGO) 95, 144, 145first OMEGAMON II screen 95INFO-line commands in 139invoking 138, 144listing 141logging from 145looping 145manipulating the log within 145modifying 139name on INFO-line 119names 140printing 134renaming 142RENM immediate 142saving 140separator line 139variables in 140zooming 151

scrolling 43cursor controlled 128

depth on INFO-line 119horizontal 132maximum number of lines 128page 128setting 94specific number of lines 128up/down 128

SCTR exception 244SDLO exception 244searching on the System Console panel 43secondary console control 153semicolon ( 124, 125separator line 139session switching 54Sessions

switching 54Set All Clear Message panel 224Set Communications External Subsystem Pool

Exceptions panel 228Set Control Function Options screen 95Set Display Options screen 94Set Startup Configuration menu 94setting exceptions 87severity levels

customer support 255short-cuts 52, 111show details 45signon 29Some 120STATE XGSW keyword 227status indicator mappings 69status indicators 34, 68

character-based 69, 86colors 69controlling display 85monochrome 69

STOP immediate 191STOP= XACB keyword 229stopped

CICS transactions 175PSBs 175

stoppingcommand processing 133menu interface 114OMEGAMON II 114screen updates 133thread 190

Storage Pools panel 176swap 219switching Sessions 54switching sessions 54SYS= startup parameter 150system


ID 150ID on INFO-line 119performance monitoring 68

System Console panel 43searching for a string 43

System Overview panel 68, 71, 78systemwide exceptions 109, 222, 224

TTCOT exception 244telephone support

customer support 254terminal bell

activating 94setting interval 95

TERSE XACB keyword 229test, exceptions 222testing .FGO routines 145THHI exception 244THHP exception 244THLO exception 244THLP exception 244thread

allocation, limiting 184analysis 188analyzing DBCTL thread activity 184CICS transaction number 188details

panel 188DL/I calls 193examining 188listing 194long-running 194PSB name 188PST number 188restarting 190status 188stopping 190trapping 194unavailable 190

Thread Details panel 188thread DL/I calls

details 193thread locks

details 192threads

high 244low 244

Threads Summary panel 186threshold 34

customizing 86exceeding 87, 222

setting 222, 228value 149XACB parameters 228

timedisplaying 83format 83on INFO-line 119

time controlled operations trace 244timed screen facility (TSF) 144

activating 94defining entries 96

TMSI exception 245Tnnn exception 244TNRS exception 245TPSB exception 245transfer

direct 65transferring among DBCTL and IMS sessions 65Transplex navigation 55

overview 55using with OMEGAMON II for CICS 57using with OMEGAMON II for DB2 60using with OMEGAMON II for DBCTL 64using with OMEGAMON II for IMS 63

Transport Manager subsystemVTAM connection 245

TRDY exception 245tripped exception 222, 224

help for 74last trip value 149worst trip value 149

TSO mode 219TTIM immediate 194tuning approach 33turquoise status indicator 69

UUNIT= startup parameter 150up/down scrolling 128user interfaces

command interface 26CUA 26graphical 26historical information (EPILOG) interfaces 27menu interface 26overview 26

user profiledeleting menu/command component 93facility 82suffix on INFO-line 119

USER= startup parameter 150user-defined profile 81, 91

Index 275

using the OMEGAMON II menu interface 103

Vvariables

conditionally setting 150in screen spaces 140keywords for conditional setting 149

VCAS exception 245VCIS exception 245VHLO exception 245View

pull-down menu 48View pull-down 48VMEX exception 245VMLO exception 245VROQ exception 245VSAM

databasewritecheck on 246

dataset going into multiple extents 245VSLO exception 246VTAM mode 219VTLO exception 246VWRC exception 246VXHI exception 246VXLO exception 246

WWADS checkwrite requests 240wait period, command response 85WBHI exception 246WBLO exception 246WCHI exception 246WCLO exception 246WDNA exception 246WDNB exception 246window 128WLHI exception 246WLLO exception 246work area size for PEEK command 95work pool

ADBW exception 234AWKP exception 235FDBW 238PSBW exception 235

WRHI exception 246WRLO exception 246WSHI exception 247WSLO exception 247

XXACB immediate 227, 228, 232

XCNF exception 247XGRP immediate 227XGSW immediate 227XIMS immediate 224XLF XACB parameter 229XRAT exception 247XRAV exception 247XRF

automatic takeoverin progress 247status 247

surveillance 247XRIP exception 247XRIT exception 247XRNS exception 247XRPH exception 247XRSR exception 247XRTO exception 247XSUM immediate 224, 227XTRP immediate 224, 227

Yyellow status bar character 86yellow status indicator 69

Zzeros, displaying 95zoom 151

cursor pointing 151prefix 151screens spaces for 151to detail panels 151, 223to detail screens 111

zooming to menu/command interface 28


Documents

OMEGAMON II for DBCTL User’s Guide ഀ嘀攀爀猀椀漀渀 㔀publib.boulder.ibm.com/tividd/td/ITOMEGAIIfDBCTL/GC32-9260-00/e… · User’s Guide OMEGAMON II ® for DBCTL Version

OMEGAMON II for DBCTL User’s Guide ഀ嘀攀爀猀椀漀渀㔀publib.boulder.ibm.com/tividd/td/ITOMEGAIIfDBCTL/GC32-9260-00/e… · User’s Guide OMEGAMON II ® for DBCTL Version