OMEGAMON II for IMS User’s Guide, Vഀ攀爀猀椀漀渀...

User’s GuideOMEGAMON II® for IMS

Version 510

GC32-9270-00

March 2002

Candle Corporation201 North Douglas Street

El Segundo, California 90245

2 OMEGAMON II for IMS 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, eBA, eBA*ServiceMonitor, eBA*ServiceNetwork, eBusiness Institute, 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, Candle CIRCUIT, Candle eDelivery, 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, 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, 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 © March 2002, 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

Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Application Trace Facility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20New OMEGAMON II Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Documentation Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23User Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Navigating among OMEGAMON II’s User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . .26Enhanced Signon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Exiting OMEGAMON II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30The Hows and Whys of Managing IMS Performance. . . . . . . . . . . . . . . . . . . . . . . . . . .32Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Chapter 2. Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Learning About Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Navigating from Panel to Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Using the View and Options Pull-downs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Advanced Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Chapter 3. Navigating BetweenOMEGAMON II Sessions53

Using 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 . . . . . . . . . . . . . . . . . . . .64

Chapter 4. Monitoring System Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67The System Overview Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Contents


Investigating Tripped Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71Getting Help for a Tripped Exception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Accessing Bottleneck Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75Tracking IMS Transactions with the Application Trace Facility . . . . . . . . . . . . . . . . . . . .76Tracking IMS Transactions with the Transaction Reporting Facility . . . . . . . . . . . . . . . . .77

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

Chapter 6. Customizing YourOMEGAMON II Profiles83

Your Logon Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84Your User Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86

Chapter 7. Maintaining your OMEGAMON II Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . .103Accessing Profile Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104Using the Dynamic Profile Update Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

Chapter 8. Using the OMEGAMON II Menu Interface . . . . . . . . . . . . . . . . . . . . . . . . . . .107Beginning OMEGAMON II Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108Menu System Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109Ease-of-Use Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116Stopping OMEGAMON II’s Menu Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122

Chapter 9. Command Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Accessing the Command Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126Commands and Screen Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127Panel Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128Entering Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131Command Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134Screen Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138

Chapter 10. Screen Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Invoking Screen Spaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148Creating or Modifying Screen Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149Loading Screen Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151 Listing Screen Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152Renaming a Screen Space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153Deleting a Screen Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154Invoking Screen Spaces Automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155

Chapter 11. Advanced Commands and Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Rate and Difference Command Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158 Setting and Using Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

Contents 5

The Zooming Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161Secondary Console Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163

Chapter 12. Resolving a Response Time Problem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168Identifying Poor Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169Analyzing Response Times for a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170Determining Source of Degradation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171Identifying the Cause of Degradation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173Identifying DASD Problems with a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174Finding Cause of I/O Contention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177

Chapter 13. Managing Groups of IMS Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181Rules for Creating Resource Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182Selecting a PSB Group Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183 Creating a New PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187Copying a PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191Deleting a PSB from a PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195Stopping a PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196Starting a PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

Chapter 14. Analyzing Transaction Queuing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200Spotting a Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201Selecting Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202Identifying the Problem Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203Determining Transaction Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204Investigating the PSB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205Taking Action on the PSB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206Rechecking the Transaction Input Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207Checking the System Overview Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208Confirming the Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209Resolving the Problem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210

Chapter 15. Identifying a Looping BMP Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212Displaying CPU Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213Identifying Suspect BMP Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214Verifying the Situation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215Examining the Region in Question . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216Viewing Details for DL/I Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217Viewing Details for Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218Taking Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219


Chapter 16. Resolving a Message Queue I/O Bottleneck221

Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222Showing Details for Message Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223Showing Details for Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224Starting the Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226

Appendix A. Operating OMEGAMON IIfrom the Menu/Command Interface229

Logging On to the Menu/Command Interface Directly. . . . . . . . . . . . . . . . . . . . . . . . .230Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231Specifying a User Profile in ISPF, VTAM, or TSO Mode . . . . . . . . . . . . . . . . . . . . . . . .233Working with Exceptions in VTAM, ISPF, TSO, or Dedicated Mode . . . . . . . . . . . . . . .234

Appendix B. Exceptions Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247OMEGAMON II for IMS Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248

Appendix C. Fast Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273Using Fast Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274

Appendix D. Guide to Candle Customer Support 277

Base Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278Enhanced Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282Customer Support Contact Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Figures 7

FIGURE 1. Reconnection Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27FIGURE 2. Modify Default Logon Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27FIGURE 3. IMS Monitor Selection Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28FIGURE 4. Panel Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38FIGURE 5. Pull-down Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39FIGURE 6. Pop-up Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40FIGURE 7. Pushbuttons on Response Time Analysis Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45FIGURE 8. View Pull-down for Response Time Analysis Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . .46FIGURE 9. Options Pull-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

FIGURE 10. Transplex Navigation in CICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55FIGURE 11. System Overview Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68FIGURE 12. Regions Status Indicator - Critical Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71FIGURE 13. A Tripped Exception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72FIGURE 14. Regions Summary Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73FIGURE 15. Select IMS Command Entry Panel l . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82FIGURE 16. IMS Command Entry Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82FIGURE 17. Exception Groups Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91FIGURE 18. Profile Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95FIGURE 19. Create, Delete, and Save Profiles Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96FIGURE 20. List User Profiles Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97FIGURE 21. Describe a User Profile Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98FIGURE 22. Set Startup Configuration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99FIGURE 23. OMEGAMON Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110FIGURE 24. The INFO-line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111FIGURE 25. Monitor Menu with IMS STATUS Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112FIGURE 26. Monitor Menu with Transaction Plots Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113FIGURE 27. Exceptions Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114FIGURE 28. Systemwide Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115FIGURE 29. Systemwide Exceptions Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116FIGURE 30. General Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117FIGURE 31. Part of the OMEGAMON II Menu Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117FIGURE 32. Transactions Menu with All Transactions Option Displayed . . . . . . . . . . . . . . . . . . . . .119FIGURE 33. Detailed Information about a Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120FIGURE 34. Panel Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128FIGURE 35. INFO-line Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129FIGURE 36. VTAM User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130FIGURE 37. OMEGAMON II Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130FIGURE 38. Four Types of OMEGAMON II Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131FIGURE 39. OMEGAMON II Command Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132FIGURE 40. One-line Help Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134

Figures


FIGURE 41. Extended Help Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135FIGURE 42. Minor Command Help Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135FIGURE 43. INFO-Line Command Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136FIGURE 44. Commands that List OMEGAMON II Commands . . . . . . . . . . . . . . . . . . . . . . . . . . .137FIGURE 45. Using the DCL Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139FIGURE 46. Result of the DCL Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139FIGURE 47. PFK Definitions in Command Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141FIGURE 48. Session Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144FIGURE 49. Typical User-Created Screen Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150FIGURE 50. Screen Space List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152FIGURE 51. Response Times Status Indicator - Critical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169FIGURE 52. Response Time Analysis for CLASS 1 Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170FIGURE 53. Bottlenecks Analysis for CLASS 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171FIGURE 54. Database Conflicts Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173FIGURE 55. Database Summary Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174FIGURE 56. Device Statistics for Database Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175FIGURE 57. Details for Database Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176FIGURE 58. OMEGAMON Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177FIGURE 59. System Overview Panel - Select Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183FIGURE 60. PSB Operations Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184FIGURE 61. PSB Groups Available Pop-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185FIGURE 62. PSB Operations - Resources for PAYROLL Group . . . . . . . . . . . . . . . . . . . . . . . . . . .186FIGURE 63. Create Group Pop-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187FIGURE 64. Add Resources to Group Pop-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188FIGURE 65. List of PSBs Matching Data Filter Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189FIGURE 66. PSB Operations for PAYSTOP Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190FIGURE 67. Copy Group Pop-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191FIGURE 68. Create Group Confirmation Pop-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192FIGURE 69. Copy Resources Pop-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193FIGURE 70. PSB Operations for PAYSTOP Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194FIGURE 71. Delete Resources Pop-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195FIGURE 72. PSB Operations for PAYSTOP Group - Changed Status to Stop . . . . . . . . . . . . . . . .196FIGURE 73. PSB Operations for PAYSTOP Group - Status Schedulable . . . . . . . . . . . . . . . . . . . .197FIGURE 74. Transactions Status Light - Critical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201FIGURE 75. Transactions Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202FIGURE 76. Details for Transaction ADDINV Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203FIGURE 77. PSB Operations Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205FIGURE 78. PSB Operations Panel after Issuing an IMS Start Command . . . . . . . . . . . . . . . . . . .206FIGURE 79. Details for Transaction with High Input Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207FIGURE 80. CPU Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213FIGURE 81. Regions Summary Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215FIGURE 82. Details for Region BMPUT001 Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216FIGURE 83. Calls Details Panel with SAP Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217FIGURE 84. Region Locks Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218FIGURE 85. Region Operations Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219

Figures 9

FIGURE 86. Message Queue Buffers and Datasets Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223FIGURE 87. VTAM Nodes Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224FIGURE 88. Signed On LTERM Operations Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225FIGURE 89. Systemwide Exceptions Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234FIGURE 90. Set All Clear Message Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236FIGURE 91. History of All Tripped Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237FIGURE 92. Display of Pre-Defined IMS/MTO Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244

Preface 11

Preface

The OMEGAMON II for IMS User’s Guide lists and explains the various functions and components of OMEGAMON II for IMS (hereafter referred to as OMEGAMON II). This guide teaches you the basics of using OMEGAMON II to manage your realtime IMS environment.

P

About This Book


About This Book

Who should read this bookThis manual is intended 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

The user guide focuses on two topics:

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

n 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 response time analysis (RTA) or historical EPILOG components of OMEGAMON II. This guide does include limited information about the bottleneck analysis (DEXAN) component of OMEGAMON II. For information about these product components, refer to:

n OMEGAMON II for IMS Response Time Analysis (RTA) Reference Manual

n OMEGAMON II for IMS Bottleneck Analysis Reference Manual

n OMEGAMON II for IMS Historical Component (EPILOG) User’s Guide

Preface 13

About This Book

Following is a complete list of the documents for OMEGAMON II for IMS.

Table 1. OMEGAMON II for IMS Documentation Set

Document Number

Document Name Description

ET53-5586 End-to-End Response Time Feature (ETE) Reference Manual

Provides reference information about ETE commands, error messages, return codes, and sense codes.

IC51-6057 Installing Candle Products on MVS

Provides installation instructions and other installation considerations.

I251-5610 OMEGAMON II for IMS and OMEGAMON II for DBCTL Configuration and Customization Guide

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

I253-6332 OMEGAMON II for IMS Realtime Commands Reference Manual

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

I253-6333 OMEGAMON II for IMS Bottleneck Analysis Reference Manual

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

I253-6336 OMEGAMON II for IMS Historical Component (EPILOG) Reference Manual

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

I254-6334 OMEGAMON II for IMS User’s Guide

Teaches the basics of using OMEGAMON II for IMS to manage realtime IMS environments.

I254-6335 OMEGAMON II for IMS Historical Component (EPILOG) User’s Guide

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

I254-6337 OMEGAMON II for IMS Response Time Analysis (RTA) Reference Manual

Provides reference information and descriptions of the features of the response time analysis (RTA) component.

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

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

About This Book


Where to look for more informationFor more information related to this product and other related products, please see the

n technical documentation CD-ROM that came with your product

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 documentationTo order additional product manuals, contact your Candle Customer Support 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 communicating with the Candle Information Development department.

You can also send email to [email protected]. Please include "OMEGAMON II for IMS User’s Guide, Version 510" in the subject line.

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

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

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

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

W052-6238, W052-6239, W052-6240,W052-6356,W052-6357

Candle Products Messages Manual, Vol. 1 through 5

Provides reference summary information for all Candle product messages.

Table 1. OMEGAMON II for IMS Documentation Set

Document Number

Document Name Description

Preface 15

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 17


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 19

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20New OMEGAMON II Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Documentation Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

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 manual OMEGAMON II for IMS and OMEGAMON II for DBCTL Application Trace Facility, Version 510 . ATF’s online help has been upgraded to reflect these new features.

What’s New 21

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 23

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Navigating among OMEGAMON II’s User Interfaces . . . . . . . . . . . . . . . . 26Enhanced Signon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Signing Onto OMEGAMON II. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Exiting OMEGAMON II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30The Hows and Whys of Managing IMS Performance . . . . . . . . . . . . . . . . 32

Monitor Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Identify and Correct Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

1

User Interfaces


User Interfaces

IntroductionOMEGAMON II has the following user interfaces:

n CUA Interface

OMEGAMON II’s primary user interface, the CUA interface, 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 push buttons 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 interface.

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.

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

Introduction 25

User Interfaces

n Historical Information Interfaces

For historical information from OMEGAMON II’s historical component, 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 IMS 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 IIs user interfaces:

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

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

menu command Press PF12

command menu Press PF12

Introduction 27

Enhanced Signon

Enhanced Signon

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

Signing Onto OMEGAMON IITo sign onto OMEGAMON II:

1. At the Welcome panel, type your applid and press Enter.The next panel you see is the Candle logo panel.

2. Press Enter.The Signon panel displays.

3. Enter your USERID and PASSWORD. The Reconnection Confirmation panel displays, as shown in Figure 1.

FIGURE 1. Reconnection Confirmation

4. 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.The Modify Default Logon Parameters panel displays, as shown in Figure 2.

FIGURE 2. Modify Default Logon Parameters

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

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.

Enhanced Signon


5. 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 Figure 3.

FIGURE 3. IMS Monitor Selection Panel

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

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 ancel

Introduction 29

Exiting OMEGAMON II

Exiting OMEGAMON II

Steps to exit OMEGAMON II for IMS

You can exit OMEGAMON II from this interface:

By doing one of the following:

Note: If you logged onto 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, IMS region, 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 Response Time Analysis Component (RTA)

The response time analysis component monitors IMS transaction response time and End-to-End Response Time Feature.

IMS transaction response time is measured as the time it takes IMS to acknowledge an input message from the teleprocessing network and initiate a response. RTA measures queuing and service times within IMS for transactions waiting for resources, and summarizes its measurements into user-defined groups.

End-to-end response time is measured as the time from when a user presses Enter until a response appears on the screen. The information gathered by End-to-End Response Time Feature helps you determine whether a response problem is in the network or on the host system.

This guide includes information about accessing RTA information through the CUA interface, but not through the menu and command interfaces. For information about RTA menus and commands, see the OMEGAMON II for IMS Response Time Analysis (RTA) Reference Manual.

n Bottleneck Analysis (DEXAN) Component

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

Introduction 31

Components

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

n Historical Component (EPILOG)

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

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

n Companion Products

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

n SAP Support Component

If you use SAP, OMEGAMON II for IMS gives you the capability of identifying the internal SAP function being executed by an IMS transaction.

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 database transactions, programs, and so on, and to take action to make them available.

For example, you can request a view of only those resources 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 IMS transactions 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 the IMS transactions. The end user typically feels the effects of resource contention or unavailable resources and informs help desk personnel.

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

1. Monitoring your system’s actual performance.2. Identifying the cause when a workload or key system resource shows a

problem. 3. Correcting problems that arise.4. Using the data from your observations and your knowledge of data center

priorities to arrive at performance targets.5. Continuing the monitoring of 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 groups of transactions performing?

Introduction 33


2. How are my IMS resources performing?3. Are the problems that OMEGAMON II points up really problems for my

site? 4. 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 transactions and resources. They do 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 critera 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 83.

The OMEGAMON II for IMS Response Time Analysis (RTA) Reference Manual explains how to set response-time exception values for RTA.

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

For example, OMEGAMON II can tell you what may be causing poor performance for a particular group of transactions, and help you identify which resources or system components are busiest or unusually active when the response time for a particular group of transactions is delayed. You can then 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.

Modes of Operation


Modes of Operation

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

If you choose to log onto 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 “Logging On to the Menu/Command Interface Directly” on page 230.

35

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 37

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

Panel format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Pull-down menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Pop-up Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Color and highlighting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Moving the Cursor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Scrolling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Using Function Keys on Panels, Pop-ups, and Pull-downs. . . . . . . . . . 41

Navigating from Panel to Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Using the action bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43The Actions Pull-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43The GoTo pull-down. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Using pushbuttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Using the View and Options Pull-downs . . . . . . . . . . . . . . . . . . . . . . . . . . 46The View pull-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46The Options pull-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Panel-Level help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Help index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49About . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49User information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Check maintenance level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Help function keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Advanced Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Using action codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Short-cut techniques. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

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 43 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 43 explains more about actions.

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

2 -------------------------------------------------------------------------------(Response Time) <Response Time Components> <Bottlenecks> 3F1=Help F2=Keys F3=Exit F5=Refresh F6=Console F10=Action Bar

4

Getting Started 39


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 40) 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 further selections, provide alerts for possible error conditions, or display help

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 44 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 41 lists all of OMEGAMON II’s CUA interface function keys.

Actions GoTo Options Help -- +----------------------------------------+ -------------- 01/02/97 12:00:00 | 1. Show details for an item | IMS: I51A _____ + | 2. IMS Command Entry | Se | 3. End to End Response time |+-- | | -------------------------------+| | 4. Exit Omegamon II F3 | | Alerts ||-- | | -----------+-------------------|| | F1=Help F12=Cancel | ----- | _ Pools ----- || +----------------------------------------+ ----- | _ MessageQ ----- || _ CLASS 1 ----- | _ IMS Status ===== _ XRF ----- | || _ CLASS 2 ##### | _ Traces ===== _ ESS ----- | _ Regions ----- || _ CLASS 3 ----- | _ Bufr. Pools ##### _ | _ Logging ----- || _ CLASS 4 ----- |--------------------------------------| || _ CLASS 5 ----- | Operator Assist | _ Databases ----- || _ PSB 1 ----- |--------------------------------------| _ Fast Path ----- || _ PSB 2 ----- | _ Programs _ Trans. | || _ PSB 3 ----- | _ Regions _ Logging | _ Conflicts ----- || | _ Databases _ Network | _ Terminals ----- || | _ Conversatn. _ Users | |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd **=Fwd F10=Action Bar PA1=Switch PA2=OMEGAVIEW



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 appears 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. Fields that accept input are underlined or highlighted. Asterisks appear 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.

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.

Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 System Overview IMS: I51A _____ + Select a component with “S” to show details+------------------------------------------------------------------------------+| Response Times | Status | Alerts ||------------------+--------------------------------------+--------------------|| _ All ----- | _ Trans. ----- _ CPU ----- | _ Pools ----- || _ Other ----- | _ Virt. Stor. ----- _ I/O ----- | _ MessageQ ----- || _ CLASS 1 ----- | _ IMS Status ===== _ XRF ----- | |+------------------------------------------------------------------------------+| 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 **=Bkwd F8=Fwd F10=Action Bar PA1=Switch PA2=OMEGAVIEW

Getting Started 41


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 appears 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 used in the CUA interface, and PFn for function keys used in the menu and command interfaces. Each panel lists the available function keys and their assignments.

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.

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.



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 be displayed 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 be displayed 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 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 be displayed on the current panel.

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

Enter Refreshes the current panel display and validates entries.

Getting Started 43

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 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 allow you to perform any of the following tasks:

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 show details 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 Response Time panels and the Operator Assist panels. When a panel from the Operator Assist section displays, you can select an IMS command that is associated with the resource that is displayed on the panel, such as a region or a database.



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

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

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 an IMS command. See “Using the Action Bar” on page 82 for more information.

The GoTo pull-downThe GoTo pull-down helps you navigate to related data quickly. Sometimes the data that appears 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

Response Time Groups Show details, trends, components

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

Getting Started 45


FIGURE 7. Pushbuttons on Response Time Analysis 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 View Options Help ------------------------------------------------------------ 01/02/97 12:00:00 Response Time 1 Analysis for Group: CLASS 1 IMS: I51A _____ + Lines 1 to 4 of 4+-----------------------------------------------------------------------------+| | Interval 00:15 hrs | Interval 00:30 hrs | Interval 01:00 hrs || Item ID | Elapsed 00:06:16 | Elapsed 00:21:16 | Elapsed 00:51:16 ||--------------+--------------------+--------------------+--------------------|| CLASS1 aug | (79) 7.1s | (195) 6.9s | (269) 7.2s || T=ADDI* | ( 5) 6.3s | (269) 7.2s | (102) 2.3s || T=ABF* | ( 1) 3.4s | (102) 2.3s | ( 10) 1.4s || P=ABCPSB* | (73) 8.4s | (157) 9.7s | (157) 9.7s || | | | |+-----------------------------------------------------------------------------+ (Response Time) <Response Time Components> <Bottlenecks> F1=Help F2=Keys F3=Exit F5=Refresh F6=Console **=Bkwd **=Fwd F10=Action Bar F11=More 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 allows you to control your view of the data.

The following figure shows the choices available from the View pull-down on the Response Time Analysis for Group panel.

FIGURE 8. View Pull-down for Response Time Analysis Panel

View Control selections vary from panel to panel. Typically, you can show all data, or subsets of data. For example, in this scenario you might want to show only the Input Queue Time response time components. You can also filter the data in a number of ways. For example, 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.

Actions GoTo View Options Help ------------------+----------------------------------+------01/02/97 12:00:00 | 1. R1 Response Time 1 | IMS: I51A _____ + | 2. R0 Response Time 0 | s 0 to 0 of 0+------------------| 3. Input Queue Time |-----------------------+| | In| 4. Program Input Queue Time | | Interval 01:00 hrs || Item ID | E| 5. Processing Time | | Elapsed 00:51:16 ||--------------+---| 6. Output Queue Time |--+--------------------|| CLASS1 aug | | | | (269) 7.2s || T=ADDI* | | F1=Help F12=Cancel | | (102) 2.3s || T=ABF* | +----------------------------------+ | ( 10) 1.4s || P=ABCPSB* | (73) 8.4s | (157) 9.7s | (157) 9.7s || | | | |+-----------------------------------------------------------------------------+ (Response Time) <Response Time Components> <Bottlenecks> F1=Help F2=Keys F3=Exit F5=Refresh F6=Console **=Bkwd **=Fwd F10=Action Bar F11=More F15=System Overview PA1=Switch PA2=OMEGAVIEW

Getting Started 47


FIGURE 9. Options Pull-down

Actions GoTo Options Help ----------------- +-----------------------------------------+ 0/00 9:30:06 AM KI2P001 ¦ 1. Customize Exceptions... ¦ I61R ¦ 2. Set Controls... ¦ Select a componen ¦ 3. Set Preferences... ¦+----------------- ¦ ¦ ---------------+¦ Response Times ¦ 4. Issue OI Queries... ¦ Alerts ¦¦----------------- ¦ 5. Issue IMS Queries... ¦ ---------------¦¦ All ----- ¦ ¦ ools ----- ¦¦ Other ----- ¦ 6. Set IMS Options... ¦ essageQ ----- ¦¦ CLASS 1 ----- ¦ 7. Bottleneck Analysis Options... ¦ ¦¦ CLASS2 ----- ¦ ¦ egions ----- ¦¦ GROUP 03 ----- ¦ 8. Change Startup Profile... ¦ ogging ----- ¦¦ GROUP 04 ----- ¦ 9. List of Administrators ¦ ¦¦ GROUP 05 ----- ¦ 10. User Authorities... ¦ atabases ----- ¦¦ GROUP 06 ----- ¦ 11. Profile Maintenance... ¦ ast Path ===== ¦¦ GROUP 07 ----- ¦ ¦ ¦¦ GROUP 08 ----- ¦ 12. Application Trace Facility... ¦ onflicts ----- ¦¦ aaaaaaaaaaaaaaaaa¦aaaaa13. Online TRF Trace...aaaaaaaaaaaaa¦ aaaaaaaaaaaaaaa¦¦ ¦ ¦ erminals ===== ¦¦ More : + ¦ F1=Help F12=Cancel ¦ ¦+----------------- +-----------------------------------------+ ---------------+

F1=Help F2=Keys F3=Exit F5=Refresh F6=Console **=Bkwd F8=Fwd F10=Action Bar,F16=ATF Status

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

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.

The Set IMS Options selection lets you customize options related to your IMS commands BMP interface.

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 persons with administrator authority set levels of authority for other users.



The Profile Maintenance selection lets you copy, delete, export, import, or modify the description of a profile. To use this function, however, you must have administrator authority.

The Application Trace selection displays the Application Trace Control panel from which you can view Application Trace Facility parameters, and add, delete and modify ATF traces. For more information, see the manual OMEGAMON II for IMS and OMEGAMON II for DBCTL Application Trace Facility, Version 510.

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. For more information, see the manual OMEGAMON II for IMS and OMEGAMON II for DBCTL Transaction Reporting Facility, Version 510.

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

Getting Started 49

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. This help appears as a pop-up window when you press F1 anywhere on the panel. The panel-level help describes the entire panel and 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 Logmode Name, and current ACB Name.

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 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 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 made in any of the fields since you last pressed Enter.

Getting Started 51

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-cut techniquesWhen 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 wanted 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.

Advanced Functions


Navigating Between OMEGAMON II Sessions 53

Navigating BetweenOMEGAMON II Sessions

Chapter overviewIf you are logged on to your current session of OMEGAMON II for IMS through OMEGAVIEW, you can move to any other OMEGAMON II session defined to OMEGAVIEW, in several ways, 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

Introduction You 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 sample The 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.

FIGURE 10. Transplex Navigation in CICS

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 Details panel

a transaction is spending too much time in DL1

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

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.

____ Actions GoTo Index Options Help----------------------------------------------------------- 06/30/94 16:45:16KC2C02D Task Details Region: CICSPRODFastpath: =WTD Auto( 60)@-------------------------------------^--------------------------------------| Task number . . . . . 52___ + | Transaction ID . . . . : BURN || _ Facility ID . . . . : M552 | _ CICS transaction ID . : BURN || Facility type . . . : Term | Originating tran ID . : BURN || Task state . . . . . : RUNNING | _ First CICS program ID : BURNA100 || Task queue . . . . . : Executbl | _ Current CICS program ID: BURNA100 || Resource type . . . : RUNNING | || Resource name. . . . : RUNNING | Storage used above 16M : 17K || Userid . . . . . . . : CICSUSER | Storage used below 16M : 2K || _ EXEC CICS command . : x’100A’ | || Attach time. . . . . : 12:24:16 | Purgeable suspend . . : Yes || CPU time . . . . . . : 2.767s | Purgeable status . . : No purge || Task elasped time. . : 15.771 | Suspend timeout due. . : None || Time of suspend . . : 16:45:00 | Suspend type . . . . . : Suspend || Time in suspend . . : 0:00:15 | || | |#-------------------------------------~--------------------------------------`(Details) <Addresses> <Files> <Remote> <Statistics> <Storage> <Timings><Return to DB2> <GoTo Remote CICS> <Umbrella> <FEPI> <Task Terminal>



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.


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 following procedures 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 instruction. You can then use the following procedure to access the Task 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 Region Status panel, select Tasks and press Enter.

The Tasks 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. You can then use the following procedure to access the Task Details 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 Switching” on page 54. You can then use the following procedure to access the Task Remote Information panel and use Transplex navigation.

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

The Task Details panel displays.

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



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 from remote 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.

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.



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.


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

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



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.


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 Thread 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 TransferYou can use IMS Direct Transfer to move from the System Overview panel, from any primary panel in your current session of OMEGAMON II for IMS, or from some panels displaying pushbuttons in your current session of OMEGAMON II for IMS, 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. Use the Tab key to get 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” on page 58.

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

Status indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Exception/Status indicator mappings . . . . . . . . . . . . . . . . . . . . . . . . . 69

Investigating Tripped Exceptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Getting Help for a Tripped Exception . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Accessing Bottleneck Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Tracking IMS Transactions with the Application Trace Facility . . . . . . . . . . 76Tracking IMS Transactions with the Transaction Reporting Facility . . . . . . 77

4

The System Overview Panel



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

FIGURE 11. 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 resource groups, hardware resources, and critical system resources.

Status indicators are grouped into the following areas:

n Response Times

n Status

Actions GoTo Options Help ------------------------------------------------------------01/02/97 12:00:00 System Overview IMS: I51A ____ + Select a component with "S" to show details+-----------------------------------------------------------------------------+| Response Times | Status | Alerts ||------------------+--------------------------------------+-------------------|| _ All ----- | _ Trans. ----- _ CPU ----- | _ Pools ----- || _ Other ----- | _ Virt. Stor. ----- _ I/O ----- | _ MessageQ ----- || _ CLASS 1 ----- | _ IMS Status ===== _ XRF ----- | || _ CLASS 2 ----- | _ Traces ===== _ ESS ----- | _ Regions ##### || _ CLASS 3 ----- | _ Bufr. Pools ----- | _ Logging ----- || _ CLASS 4 ----- |--------------------------------------| || _ CLASS 5 ----- | Operator Assist | _ Databases ----- || _ PSB 1 ----- |--------------------------------------| _ Fast Path ----- || _ PSB 2 ----- | _ Programs _ Trans. | || _ PSB 3 ----- | _ Regions _ Logging | _ Conflicts ----- || | _ Databases _ Network | _ Terminals ----- || More : + | _ Conversatn. _ Users | |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd F8=Fwd F10=Action Bar PA1=Switch PA2=OMEGAVIEW



n Alerts

If your installation has defined more transaction groups than can fit in the Response Times area, a "More" indicator displays at the bottom of the list. You can use the F7 and F8 function keys to scroll up and down the list of groups.

Note: The Operator Assist section does not indicate status and is not dynamic. Operator Assist lets you select a panel that displays 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 mapping 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:

Bufr. Pools OHLO, VHLO

Conflicts XCNF

CPU CBHI, CBLO, CCHI, CCLO, CLHI, CLLO, CMHI, CMLO, CPUA, CRHI, CRLO, CSHI, CSLO



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

ESS ESNC, ESND, ESTH

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

I/O ACBH, DNRS, DRDY, IORC, LMGH, MFSH, NDIR, NDRE, QBKH, RDSH, SMGH, SPAH, TMFH, TNRS, TRDY

IMS Status COMW, CSVC, CVAH, CVHI, CVSH, DISP, ICFX, INAC, IRFC, IRGC, IRRC, IRRU, ITWH, MSGE, NACB, NILU, NPDL, NQRE, NSDC, NVAP, ONLC, ONLO, PSVC, RSRV, SAPW, SDSP, TCOI, TMSI, VROQ

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

MessageQ ALMD, AMSG, AQBD, ASMD

Pools ACEA, ACES, ACEW, ACEX, ACIO, ACIS, ACIW, ACIX, ACWA, ACWS, ACWW, ACWX, ADBW, ADMB, AEPC, AFRE, AHIO, AMFS, APIE, APSB, APSW, ARAU, ARCB, ASAP, AWKP, DMFF, FCIO, FCWA, FDBW, FDMB, FEPC, FHIO, FMFS, FPSB, FPSW, LDMB, LPSB, OSBL

Regions DSWP, IBHI, IBLO, ICHI, ICLO, ILHI, ILLO, IMHI, IMLO, IRHI, IRLO, IRQH, ISHI, ISLO, MDHI, MDLO, MIRT, MPCH, PIQH, RGNW, RGSH, RGSI, ROHI, ROLO, THHI, THHP, THLO, THLP

Terminals LPOQ, LTOQ, LVOQ, NLOQ, NPOQ, NVOQ, PROQ

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

Trans. NTIQ, TXIQ

Virt. Stor. IRCS, LALO, LMLO, LSLO, PIBC, PIBP, PICC, PICP, PIDC, PIDP, PILC, PILP, PIMC, PIRP, PISC, PISP, VMLO, VSLO, VTLO, WBHI, WBLO, WCHI, WCLO, WLHI, WLLO, WMHI, WMLO, WRHI, WRLO, WSHI, WSLO

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


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, “Customizing your exceptions” on page 89.

When an exception trips, a status indicator on the System Overview panel turns either yellow or red. Figure 12 on page 71 shows a Regions status indicator, which appears in red on your screen.

FIGURE 12. 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 panel that indicates which exception tripped. Figure 13 on page 72 shows a panel indicating a tripped RGNW exception.

Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 System Overview IMS: I51A ____ + Select a component with "S" to show details+-----------------------------------------------------------------------------+| Response Times | Status | Alerts ||------------------+--------------------------------------+-------------------|| _ All ----- | _ Trans. ----- _ CPU ----- | _ Pools ----- || _ Other ----- | _ Virt. Stor. ----- _ I/O ----- | _ MessageQ ----- || _ CLASS 1 ----- | _ IMS Status ===== _ XRF ----- | || _ CLASS 2 ----- | _ Traces ===== _ ESS ----- | _ Regions ##### || _ CLASS 3 ----- | _ Bufr. Pools ----- | _ Logging ----- || _ CLASS 4 ----- |--------------------------------------| || _ CLASS 5 ----- | Operator Assist | _ Databases ----- || _ PSB 1 ----- |--------------------------------------| _ Fast Path ----- || _ PSB 2 ----- | _ Programs _ Trans. | || _ PSB 3 ----- | _ Regions _ Logging | _ Conflicts ----- || | _ Databases _ Network | _ Terminals ----- || More : + | _ Conversatn. _ Users | |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd F8=Fwd F10=Action Bar PA1=Switch PA2=OMEGAVIEW



FIGURE 13. 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 Figure 14 on page 73. Depending on the exception that tripped, more details may be available for the items on this panel.

Actions GoTo Options Help ------------------------------------------------------------01/02/97 12:00:00 System Overview IMS: I51A ____ + Select a component with "S" to show details +----------------------------------------------------------------------------+ | Response Times | Status | Alerts | |-----------------+--------------------------------------+-------------------| |_ All ----- | _ Trans. ----- _ CPU ----- | _ Pools ----- | |_ Other ----- | _ Virt. Stor. ----- _ I/O ----- | _ MessageQ ----- | |_ CLASS 1 ----- | _ IMS Status ===== _ XRF ----- | | +----------------------------------------------------------------------------+ | 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 **=Bkwd F8=Fwd F10=Action Bar PA1=Switch PA2=OMEGAVIEW



FIGURE 14. Regions Summary Panel

The Regions Summary panel spans more than one screen with the addition of the Transaction Name column. To see the complete panel, you can scroll to the right by using F20. To scroll left, use F19.

3. To see details about an item on the information panel:Place the cursor next to the item and press Enter.

Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 Regions Summary IMS: I51A ____ + Lines 1 to 8 of 8 More: >+-----------------------------------------------------------------------+| Name | Type | Status | CPU Rate| Working|Locks | Transaction || | | | | Set |Held | ||------------+---------+--------+---------+--------+------+-------------+| IMS510AC | CONTROL |--n/a-- | ....... | 1432K | 0 | --n/a-- || IMS510AB | DBRC |--n/a-- | ....... | 192K | 0 | --n/a-- || IMS510AD | DLS |--n/a-- | ....... | 576K | 0 | --n/a-- || _ IMS510AI | IRLM |--n/a-- | ....... | 408K | 0 | --n/a-- || _ BMPID005 | BMP | Idle | ....... | 220K | 0 | --n/a-- || _ BMPUT001 | BMP |Ex-Drgn | ....... | 208K | 0 | --n/a-- || _ IFP51001 | FASTPATH| Idle | ....... | 220K | 0 | --n/a-- || _ IFP51002 | FASTPATH| Idle | ....... | 220K | 0 | --n/a-- |+-----------------------------------------------------------------------+ (Regions) <Virtual Storage> <CPU> F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd F10=Action Bar F15=System Overview F19=Left F20=Right PA1=Switch PA2=OMEGAVIEW

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, do the following:

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

Accessing Bottleneck Analysis

IntroductionYou can use the OMEGAMON II bottleneck analysis feature to investigate response time problems.

You can activate the Bottleneck Analysis collector by selecting Bottleneck Analysis Options from the Options pulldown menu on the System Overview panel. You access bottleneck analysis by selecting a transaction group from Response Times on the System Overview panel, specifying a specific response time from the View pull-down, and then selecting the <Bottlenecks> pushbutton.

Tracking IMS Transactions with the Application Trace Facility


Tracking IMS Transactions with the Application Trace Facility

IntroductionThe Application Trace Facility tracks and saves detail activity in IMS on a transaction basis. This includes information such as

n External subsystem activity, such as DB2 processing

n BMP scheduling and termination

n MPP scheduling and termination

n Regions

n DL/I DB calls

n IMS TM calls

n Message queue manager calls

For information on the functions of the Application Trace Facility (ATF), refer to the manual OMEGAMON II for IMS and OMEGAMON II for DBCTL Application Trace Facility, Version 510.

Accessing the Application Trace FacilityATF trace records can be added, deleted or modified from the CUA interface. ATF control is available under the Options pull-down.

1. Enter O on the action bar to use the Options pull-down menu.

2. Select Application Trace Facility from the list on the Options pull-down by typing the appropriate number or the underlined letter in the entry field. The Application Trace Control panel displays from which you can add, modify and delete traces.


Tracking IMS Transactions with the Transaction Reporting Facility


IntroductionThe Transaction Reporting Facility (TRF) captures performance and activity-related data for all IMS transactions, or for a specified subset. This includes information such as:

n CPU time

n Virtual storage use

n Response time

For more information on this facility, refer to the manual OMEGAMON II for IMS and OMEGAMON II for DBCTL Transaction Reporting Facility, Version 510.

Accessing the Transaction Reporting Facility

1. Enter G on the action bar to display the Goto pull-down.

2. Select Online TRF Trace... from the list on the Options pull-down by typing the appropriate number or the underlined letter in the entry field. The TRF Display Control panel displays from which you can add, modify and delete traces.

Issuing IMS Commands 79

Issuing IMS Commands

Chapter overviewOMEGAMON II provides a quick and easy way to monitor the performance of your IMS system. It allows you to 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 that 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 interfaceusing the:

n Operator assist feature

n System Console panel

n Action bar

This chapter explains how to use these techniques.

Chapter contentsUsing the Operator Assist Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Using the System Console Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Using the Action Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

5

Using the Operator Assist Feature


Using the Operator Assist FeatureThe 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 database PAYROLL1, 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 81

Using the System Console Panel

Using the System Console PanelYou 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 and press Enter.Responses from the system display in the window at the bottom of the panel.

Using the Action Bar


Using the Action BarYou 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 Figure 15 on page 82 displays.

FIGURE 15. Select IMS Command Entry Panel l

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 16. IMS Command Entry Pane

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 with the command recognition character. The OMEGAMON II CUA system does this for you automatically.

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

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

Customizing Your OMEGAMON II Profiles 83

Customizing YourOMEGAMON II Profiles

Chapter overviewYour profiles control the characteristics of your IMS 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Logon Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Your User Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Creating a User Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Customizing the CUA Component of Your User Profile. . . . . . . . . . . . 88Customizing the Menu/Command Interface Component of Your User Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

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 IMS

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

6

Your Logon Profile


Your Logon ProfileYour 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 onto 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.

Time/date display

On Displays the time and date on every panel.

Off Does not display the time and date.


Your Logon Profile

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

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

4. Customize the profile’s controls and exceptions to meet your needs as explained in ”Setting controls” on page 88 and ”Customizing your exceptions” on page 89.

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

The following sections describe how to customize your user profile:

n for the CUA interface.

n for the menu/command interface

Your User Profile


Customizing the CUA Component of Your User ProfileCustomizing the CUA component of your user profile includes:

This section explains how to set controls, exceptions, and IMS options.

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 IMS displays information.

Customizing exceptions

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

Changing IMS command options

Lets you customize options related to your IMS commands BMP interface.

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

Wait period for response to commands.

Enter the time period that you wantOMEGAMON 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 your displays or Off to suppress green status bars on your 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.

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 (=).

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 (”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 thresh, the corresponding light turns red. If all of them trip at their warning thresholds, the light turns yellow.

Procedure for customizing exceptions

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.

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 both 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 IMS 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 interface 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 interface.


Your User Profile

Note: You can customize the Candle default profile (/C) only for your current session.

2. From any panel, select Customize Exceptions from the Options pull-down.A list of all the IMS exception groups displays, as shown in Figure 17 on page 91.

FIGURE 17. 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 247. Otherwise, choose the group whose name describes the IMS 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.

Figure 3 on page 92 shows the Threads - High Exceptions Thresholds exception group.

Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 System Overview I51A + +-----------------------------------------------+ Select a component wi | Exception Groups Index |+--------------------- | | -----+| Response Times | | Lines 1 to 13 of 48 | ||------------------+-- | Move cursor to selection, then press Enter. | -----|| _ All ----- | | | ---- || _ Other ----- | | Exception Groups | ---- || _ CLASS 1 ----- | | | || _ CLASS2 ##### | | Buffer Pools - Low | ---- || _ GROUP 03 ----- | | CPU - High | ---- || _ GROUP 04 ----- |-- | CPU - Low | || _ GROUP 05 ----- | | Databases - Alerts | ---- || |-- | External Subsystem - Alerts | ---- || | | External Subsystem - High | || | | Fast Path - Alerts | ---- || | | Fast Path - High | ---- || | | Fast Path - Low | |+--------------------- | Fragmentation - Low | -----+ | 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 **=Bkwd **=Fwd F10=Action Bar PA1=Switch PA2=OMEGAVIEW

Your User Profile


Table 3. 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 on page 27.

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 on page 27.

6. If the exception you’re customizing is an alert, skip to step 7 on page 27.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 on page 26 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.

Changing IMS command options

You can change the IMS command options in your user profile as follows:

1. Specify the user profile you want to change when you log on.

2. Select Set IMS Options ... from the Options pull-down.

3. You can change the following IMS command options:

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

Submit Commands via BMP Interface

On This is the default. OMEGAMON II submits your commands through the BMP whenever possible. If it cannot use the BMP, OMEGAMON II attempts to submit your commands using the WTOR interface.

Off Turn this option OFF if you don’t want to submit any commands using the BMP.

Wait for IMS to Process Each Command

On Turn this option ON if you want to wait for each IMS command submitted using the BMP to process. If you submit multiple commands, or if you request an action that requires OMEGAMON II to submit multiple IMS commands, you’ll wait a maximum of 30 seconds for the last of these commands to process.

Note: After 30 seconds the system terminates the wait; the IMS command continues to process.

Off This is the default. You don’t wait for your IMS commands to process. IMS responses to your commands appear on the console and Operator Assist panels.

Automatically Attach BMP when needed

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

Your User Profile


Note: If the BMP stops working, IMS stops the associated PSB and transaction. The BMP cannot reATTACH until you:

1. Start the PSB.

2. Start the transaction.

3. Restart your BMP interface.For more detailed information on the BMP interface, see the Configuration and Customization Guide.

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. To access this menu, select the Profile option from the Main Menu.

OMEGAMON II displays the Profile Menu shown in Figure 18 on page 95.

On Turn this option ON if you want the BMP to attach automatically when you need it (for example, if the BMP has terminated itself due to having processed the number of commands specified on PROCLIM=).

Note: The BMP cannot attach automatically if the current CBMP ATTACH= value is either NO or SUSP.

Off This is the default. The BMP does not ATTACH automatically for you unless it was started with ATTACH=WAIT and you have Submit Commands via BMP interface set ON.

If the BMP is not currently ATTACHed, and you are submitting commands using the BMP interface only (Automatically Use WTOR if needed OFF), your IMS commands queue in memory until the BMP is reATTACHed.

Automatically Use WTOR if needed

On This is the default. OMEGAMON II uses the WTOR interface as a backup interface for submitting your IMS commands.

Off Turn this option OFF if you don’t want your commands submitted using the WTOR interface under any circumstances.

Note: You cannot submit some IMS commands using a BMP interface. For a list of these commands, see your IBM IMS Operator’s Reference. If you turn this option OFF, you won’t be able to issue any of these commands. And if the BMP is not ATTACHed and cannot ATTACH automatically, you won’t be able to issue any IMS commands.


Your User Profile

FIGURE 18. 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 19 on page 96 displays.

________________ KOIPOPT VTM OI-II /C I61D 08/18/99 12:00:00 B> 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 >> Changes you make from this menu become permanent when you save your profile.> Use PF22 to save the profile.

Your User Profile


FIGURE 19. 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 IMS 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 Figure 20 on page 97.

________________ KOIOPU VTM OI-II /C I61D 08/18/99 12:00:00 B> 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 ===============================================================================


Your User Profile

FIGURE 20. List User Profiles Screen

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 98 See “Configuring profiles” on page 98. 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.

________________ KOIOPUA VTM OI-II /C I61D 08/18/99 12:00:00 B> Help PF1 Back PF3 Up PF7 Down PF8 Save Profile PF22>===============================================================================> LIST USER PROFILES >PPRF LIST> RKOIPFSV DSN=TDIMS1.I2400SMP.R1.I51A.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


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 menuThe Describe a User Profile screen shown in Figure 21 on page 98 displays.

FIGURE 21. Describe a User Profile Screen

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

3. Save the description by pressing PF22.

Configuring profiles

OMEGAMON 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 18 on page 95, or type P.G on the INFO-line of any screen and press Enter. OMEGAMON II displays the menu shown in Figure 22 on page 99.

________________ KOIOPUB VTM OI-II /C I61D 08/18/99 12:00:00 B> 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

FIGURE 22. 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 bell

n Log

It 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)

n the first screen to display when OMEGAMON II is started

n The interval for the terminal bell

n whether zeros values display as zeros or blanks

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

________________ KOIOPTE VTM OI-II /C I61D 08/18/99 12:00:00 B > 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


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 22 on page 99) 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 cycles

n number of entries in the device name table

n prevention of loops caused by the PEEK command

n automatic updating delay cycle

n size of the REPORT file for logging screens

n 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 22 on page 99) 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

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

n characters on the left of the separator page


Your User Profile

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, ”Customizing your exceptions” on page 101.

Your User Profile


Maintaining your OMEGAMON II Profiles 103

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 “Maintaining your OMEGAMON II Profiles” on page 103.

Chapter contentsAccessing Profile Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Using the Dynamic Profile Update Facility . . . . . . . . . . . . . . . . . . . . . . . 105

Invoking externally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105User profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105MVS Modify command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Example command for exporting a profile . . . . . . . . . . . . . . . . . . . . 105Example command for importing a profile . . . . . . . . . . . . . . . . . . . . 106Messages produced by the Dynamic Profile Update Facility . . . . . . . 106

7

Accessing Profile Maintenance


Accessing Profile Maintenance

Steps

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.The system displays the Profile Maintenance menu. It shows you the current profile, a list of all the profiles, and the action codes.

3. 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 105

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

Using the OMEGAMON II Menu Interface 107

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

Starting OMEGAMON II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Accessing the menu interface from the CUA interface . . . . . . . . . . . . 108

Menu System Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Menu types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109The main menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109A menu for monitoring IMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111The plot IMS rates display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Exception analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Ease-of-Use Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Help screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Quick access method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117The zoom feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118OMEGAMON II menu PF key definitions . . . . . . . . . . . . . . . . . . . . . 121

Stopping OMEGAMON II’s Menu Interface . . . . . . . . . . . . . . . . . . . . . . 122

8

Beginning OMEGAMON II Operation


Beginning OMEGAMON II Operation

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

Starting OMEGAMON IIOMEGAMON II is installed on your system 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 230 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 interface:

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


Menu System Operation


IntroductionOMEGAMON II’s menu interface provides an easy way to access detailed information about IMS available from OMEGAMON commands. Each menu contains the following items:

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

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

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.

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.

Separator bars Lines with equal signs (=) in columns 2-5 are used to 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.



After you press Enter, you see the Main Menu shown in Figure 23 on page 110.

FIGURE 23. OMEGAMON Main Menu

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

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 as follows:

n Type MENU on the INFO-line, starting at the first underscore, as shown in Figure 24 on page 111 and press Enter.

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

__________________ZMENU VTM OI-II /C I61D 08/18/99 16:04:14 0B> 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 IMS Performance Monitor Main Menu _ E EXCEPTIONS ....... Current and potential system problems, latch conflicts_ R RESPONSE TIME .... Transaction response times (RTA users)_ B BOTTLENECKS ...... Resource contention (bottleneck analysis) (DEXAN users) _ M MONITOR .......... IMS status, graphs, and time controlled operations_ W WORKLOAD ......... PSBs, DMBs, transactions, regions, and classes_ L LINES ............ Terminals, nodes, and lines_ 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_ P PROFILE .......... Profile maintenance and session settings



FIGURE 24. The INFO-line

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 as follows:

n Move 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 25 on page 112.

MENU______________ VTM OI-II /C I61D 08/18/99 12:00:00 B



FIGURE 25. 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.

________________ KOIIMS VTM OI-II /C I61D 08/18/99 12:00:00 B B> 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 TRAN G-PLOT IMS> H-TCO STATUS I-TCO STARTUP J-TCO DELAYED K-TCO TIME OF DAY===============================================================================> IMS, Operating System, and Fast Path Status > IMS Status: ISYS IMS Version 6.1.0 Subsystem ID = ‘I61D’+ MVS/ESA -- SP6.0.7 IRLM Release 2.1+ IMS Restart date = 99.229 (Local) IMS Restart time = 10:08:53 (Local)+ IMS Restart date = 99.229 (UTC) IMS Restart time = 17:08:53 (UTC)+ Checkpoints taken = 26 Current Checkpoint id = 99230/170957+ MPPs active = 0 BMPs active = 0+ Applications scheduled = 116 Transactions queued = 0+ Msg Enqueue rate =.00/sec Msg Dequeue rate =.00/sec+ System Dsn OSAM I/O’s = 5740 DLS OSAM I/O count = 12741+ >>> Remote Site Recovery not installed <<<+ IMS Base LUname = N/A IMS Base Network Id = N/A+ APPC Status = DISABLED APPC Desired Status = DISABLED+ RACF Option = FULL Generic Resources LU = --N/A--+ LU62 Active Sync Convs = 0 LU62 Active Async Convs = 0 ==============================================================================> Operating System: MSYS System CPU usage = 65.25% System SIO rate = 533.33/sec+ IMS CPU usage = .00% IMS SIO rate = .00/sec+ Average IMS CPU = .00% IMS SIO average = .00/sec+ Number of active CPUs = 6 System ID = SP22++ --Virtual Storage--- ---------Working Set-----------+ Below 16m Above 16m Real Expanded Total WKST+ Control Region : 1912K 22356K 3352K N/A 3352K+ DBRC Region : 412K 10800K 272K N/A 272K+ DLS Region : 728K 10332K 460K N/A 460K+ IRLM Region : 512K 10520K 1752K N/A 1752K+ IMS Region : Region NOT active===============================================================================> Fast Path: FSYS >> OI422: Fast Path not installed in system <<===============================================================================> Checkpoint: CKPT Current Checkpoint id = 99230/170957+ Block Number = 1336+ ------------------------------------------------------------------------+ Latest DUMPQ/SNAPQ Checkpoint id = 99229/170853+ Block Number = 2===============================================================================> Online IMS change operations: OCHG Online change is not in progress+ Current online change id: 7 Current nucleus suffix: D+ Modify work area address: 00000000 Modstat work area address: 0000C9A8+ MODBLKSA is active ACBLIB is active FORMATA is active++ Date Time+ Previous MODIFY PREPARE 99109 17:33:32.+ Previous MODIFY COMMIT 99109 17:33:40.+ MODSTAT VOL=PPSMPO DSN=IMS.V6RC.MODSTAT===============================================================================



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.

You can scroll to the right to see the end of the lines in this panel.

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

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 TRAN, plots the transaction arrival rate, the dequeue rate, and the input queue length.

From the Monitor Menu, select the Plot TRAN 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. Figure 26 on page 113.

FIGURE 26. Monitor Menu with Transaction Plots Display

________________ KOITPLT VTM OI-II /C I61D 08/18/99 12:00:00 B> 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 TRAN G-PLOT IMS> H-TCO STATUS I-TCO STARTUP J-TCO DELAYED K-TCO TIME OF DAY===============================================================================> Transaction Plots > Transaction arrival rate, dequeue rate, and input queue size: PLOTX ARVL DEQU INQL++ ARVL MSG Enq rate/sec DEQU MSG Deq rate/sec INQL Input queue length+ 30 + 30 + 30 ++ | | |+ 22 =>---------------- 22 =>---------------- 22 =>----------------+ | | |+ 15 + 15 + 15 ++ | | |+ 7 =>---------------- 7 =>---------------- 7 =>----------------+ | | |+ + - + - + - + - + + - + - + - + - + + - + - + - + - ++ Past Now Past Now Past Now===============================================================================> Transactions processing more than nn per minute::rev refid=ejc1. ITX40 >>> No processing rates exceeded the threshold <<===============================================================================



This Transaction Plots display is useful for showing trends in transaction 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 230 for more information on OMEGAMON II modes of operation, and “Delaying automatic updating” on page 143 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 27 on page 114 appears.

FIGURE 27. Exceptions Menu

From this menu, you can select various exception displays. Figure 28 on page 115 shows part of the Systemwide Exceptions display (option B on the Exceptions Menu).

________________ KOIEXCP VTM OI-II /C I61D 08/18/99 12:00:00 B > 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 ===============================================================================



FIGURE 28. Systemwide Exceptions

This display alerts you to several types of exceptions: critical, operational, and status.

Selective dispatching is a critical exception that you can highlight by boxing the message. When the communications pool (the dynamic SAP pool) is 95% full, IMS automatically begins selective dispatching to reduce pool space demand. This creates a serious response time problem for all IMS users.

OMEGAMON II also warns you of situations that may become critical and that you need to watch for future corrections. For example, the Fixed FRE Pool utilization is high at 97.25%.

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 Figure 17 on page 91.

________________ KOISYS VTM OI-II /C I61D 08/18/99 12:00:00 B> 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 #+ ########################################################################+ PROQ Printer: DFSTCFI unable to receive output from queue+ PROQ Printer: PMAST61D unable to receive output from queue+ PROQ Printer: SMAST61D unable to receive output from queue+ FPSB PSB Pool: Largest free block = 2864 bytes+ DLTR DL/I Trace ON+ DSTR DISPATCHER Trace ON+ SCTR SCHEDULER Trace ON+ LKTR LOCK Trace ON+ OXLO OSAM Database: BA$HDLO0 DDName: BAHDLO01 I/O Rate = .00 (Low)+ OXLO OSAM Database: BA$HDLO0 DDName: BAHDLO01 I/O Rate = .00 (Low)+ OXLO OSAM Database: BB$HDLO0 DDName: BBHDLO01 I/O Rate = .00 (Low)+ OXLO OSAM Database: BC$HDLO0 DDName: BCHDLO01 I/O Rate = .00 (Low)+ OXLO OSAM Database: BD$HDMO0 DDName: BDHDMO01 I/O Rate = .00 (Low)+ OXLO OSAM Database: BE$HDMO0 DDName: BEHDMO01 I/O Rate = .00 (Low)+ OXLO OSAM Database: BF$HDMO0 DDName: BFHDMO01 I/O Rate = .00 (Low)+ OXLO OSAM Database: BG$HDHO0 DDName: BGHDHO01 I/O Rate = .00 (Low)+ OXLO OSAM Database: BH$HDHO0 DDName: BHHDHO01 I/O Rate = .00 (Low)+ OXLO OSAM Database: BI$HDHO0 DDName: BIHDHO01 I/O Rate = .00 (Low)+ VXLO 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 Figure 29 on page 116.

FIGURE 29. 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 Figure 29 on page 116 displays the General Help Menu shown in Figure 29 on page 116. You can also access this menu by pressing PF1 on the Main Menu.

________________ KOISYSH VTM OI-II /C I61D 08/18/99 12:00:00 B > 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. ===============================================================================



FIGURE 30. General Help Menu

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, Figure 31 on page 117 shows part of the OMEGAMON II menu hierarchy.

FIGURE 31. Part of the OMEGAMON II Menu Hierarchy

________________ KOIHLPVTM OI-II /C I61D 08/18/99 12:00:00 B > Back PF3 Main Menu PF4> Enter a selection letter on the top line.=============================================================================== > OMEGAMON for IMS General Help Menu _ A CUA................... OMEGAMON II for 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 ===============================================================================

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



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:

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



FIGURE 32. Transactions Menu with All Transactions Option Displayed

This screen lists basic information for several transactions.

2. To use the zoom feature to see detailed information, position the cursor under a transaction name (for example, ADDINV) and press PF11.OMEGAMON II displays the screen shown in Figure 33 on page 120 .

________________ KOITRAN VTM OI-II /C I61D 08/18/99 12:00:00 B> Help PF1 Back PF3 Up PF7 Down PF8 Zoom PF11 > To view a topic below, enter a selection letter on the top line. > *-ALL TRANS B-EXECUTING C-USTOPPED D-UNSCHEDULABLE> E-IN A CLASS F-QUEUE > n G-USER LIST===============================================================================> All Transactions > For the contents of the scheduler management block (SMB) associated with a > specific transaction (TRXA), or for more information about a scheduling class> (CLAS), program (PGMN), or route code (RCTE), place the cursor on the> appropriate item, and press PF11. #TRXA 271 TRXA ADDINV ADDPART BMX00000 BMX00010 BMX00020 BMX00030 BMX00040 BMX0050+ arv1 0 0 0 4 3 0 0 0 clad 1 1 1 1 1 1 1 1 stat Idle Idle Idle Active Active IdleIdle Idle attr .. .. MS .. .. MS .. .. MS .. .. MS .. .. MS .. .. MS .. .. MS .... MS pgmn DFSSAM04 DFSSAM04 BMP00000 BMP00010 BMP00020 BMP00030 BMP00040 BMP00050 ptyp Online Online BatchBatch Batch Batch Batch Batch prcs schc



FIGURE 33. Detailed Information about a Transaction

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

________________ KOITRX VTM OI-II /C I61D 08/18/99 12:00:00 B> Help PF1 Back PF3 Up PF7 Down PF8=============================================================================== > Dump of the Scheduler Management Block (SMB) for the Transaction DUMP Display IMS Control Blocks smb ADDINV 08ACB830+ 000 00000000 00000000 00000000 00000000 *................*+ 010 00000000 00810068 00040004 C1C4C4C9 *.....a......ADDI*+ 020 D5E54040 45484000 0700A701 FFFFFFFF *NV .. ...x.....*+ 030 00000002 FFFFFFFF 00000101 08ADFDA0 *................*+ 040 00000000 0000FFFF 0000FFFF 00000000 *................*+ 050 08ACB8B8 00000000 C4C6E2E2 C1D4F0F4 *........DFSSAM04*+ 060 40404040 40404040 00000000 00000000 * ........*+ 070 00000000 00000000 00000000 00000000 *................*+ 080 00000000 0B1055D8 *.......Q *=============================================================================



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

PF11, 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 interface System Overview panel.

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

4. Press PF3 to exit.

________________ KOIQST VTM OI-II /C I61D 08/18/99 12:00:00 B 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.================================================================================

123

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.

Command Basics 125

Command Basics

Chapter overviewThis chapter provides basic information about the format of theOMEGAMON 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Commands and Screen Spaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Panel Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

INFO-line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Panel display symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Entering Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Command types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Command Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Major, minor, and immediate command help . . . . . . . . . . . . . . . . . . 134INFO-line command help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Commands to list commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Screen Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Up/Down scrolling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Clearing the screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Deleting comment lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Inserting and deleting lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Using Program Function (PF) keys . . . . . . . . . . . . . . . . . . . . . . . . . . 140Displaying continuation lines of command output . . . . . . . . . . . . . . 142Delaying automatic updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Screen logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Activating the log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Checking the page limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Logging a single display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Logging part of a display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

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 127

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 has been saved in a file and given 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 147.

Panel Format


Panel Format

IntroductionThe following figure shows the OMEGAMON II panel format.

FIGURE 34. 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, it 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. It executes commands as it finds them, starting at the top of the panel and working down.

INFO-line Figure 35 on page 129 shows the components of the INFO-line.

______________ #01 VTM OI-II /C I61D 08/18/99 12:00:00 B <Main body of panel>

<Input area> <Display area>

Command Basics 129

Panel Format

FIGURE 35. INFO-line Format

The OMEGAMON II for IMS Realtime Reference Manual discusses the status symbols on the INFO-line in more detail. Note that the symbols for the logging status (LOG), the scrolling depth option (5), the automatic screen facility status (A), 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 thatOMEGAMON II displays with command output.

Comment lines (>)

To designate a comment line, enter a greater-than sign (>) in column 1. Any command entered 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 data at a time unless you request additional lines. “Displaying continuation

____________________ZMENU VTM LOG OI-II /C I51A 01/02/97 8:05:11 5 AB | | | | | | | | | | ||Input Area <---‘ | | | | | | | | | || | | | | | | | | | ||Screen Space Name <---‘ | | | | | | | | || | | | | | | | | || Mode of Operation <---‘ | | | | | | | || | | | | | | | || Logging Status <----‘ | | | | | | || | | | | | | || Product ID <------‘ | | | | | || | | | | | || User Profile Suffix <-‘ | | | | || | | | | || System ID <---‘ | | | || | | | || Screen Refresh Date <-----‘ | | || | | || Screen Refresh Time <-----‘ | || | || Scrolling Depth <---‘ || || Automatic Screen Facility <----‘ | | Screen Stacking and Bell Status <--‘

Panel Format


lines of command output” on page 142 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 Figure 36 on page 130.

FIGURE 36. 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 Figure 37 on page 130 .

FIGURE 37. OMEGAMON II Keywords

________________ KOIQST VTM OI-II /C I61D 08/18/99 12:00:00 B .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 OI-II /C I61D 08/18/99 12:00:00 B .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 131

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 Figure 38 on page 131 , you can see examples of the four types of commands used in OMEGAMON II along with some sample output.

FIGURE 38. 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 yourOMEGAMON II session (/STOP).

INFO-line commands are executed 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 must be entered 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 major command DISK produces a list of online disks. You can enter major commands on any line below the INFO-line.

/PRINT_ _ _ _ _ #01 VTM OI-II /C I61D 08/18/99 12:00:00 B 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. Commands can also be entered with labels or arguments, as shown in Figure 39 on page 132.

FIGURE 39. OMEGAMON II Command Format

Minor These commands display detailed information about the category that the major selects. In the example above, the minor command DADR 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 they are preceded 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)|+--> label field (col. 1)

Command Basics 133

Entering Commands

Extended arguments are entered in columns 8 through 72. In the example, the GDEV command has been entered with an argument of SYSDA, which is a generic device name in the system. This means that only devices in the SYSDA category are displayed. 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 output displayed. You can also use this field for special command modifiers, such as those that request online help text for commands.

In Figure 39 on page 132 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, .MJ command produces a list of major commands. It has been entered with an argument of DS, a group code that specifies that only disk major commands be listed.

Command Help


Command Help

Introduction OMEGAMON 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 Table 4: Command Help Symbols on page 134 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 Figure 40 on page 134.

FIGURE 40. 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 Figure 41 on page 135.

Table 4. Command Help Symbols

? Display an on-line help start 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 OI-II /C I61D 08/18/99 12:00:00 B>.WAT> Specifies a delay before executing the commands that follow. +

Command Basics 135

Command Help

FIGURE 41. 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, the same minor name is used 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 Figure 42 on page 135.

FIGURE 42. 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

________________ KOIQST VTM OI-II /C I61D 08/18/99 12:00:00 B>.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>> The commands shown above cause OMEGAMON to wait 2 seconds before> fetching screen space MYSCREEN.

________________ KOIQST VTM OI-II /C I61D 08/18/99 12:00:00 B>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


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 commands, you can type the major command name on the same line after the help request. For example, the entry

/dio DISK

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

INFO-line command helpYou can obtain INFO-line 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 one shown in Figure 43 on page 136.

FIGURE 43. INFO-Line Command Help

________________ KOIQST VTM OI-II /C I61D 08/18/99 12:00:00 B>.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> | space. It is only cancelled when you issue> | /DEF OFF. Use this option when you want to

Command Basics 137

Command Help

Commands to list commandsAnother form of help enables you to list allOMEGAMON 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 command preceded by an H in the label field (column 1), a one-line help for each command is displayed. The display in Figure 44 lists available OMEGAMON II commands:

FIGURE 44. 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 scrolling

n clearing the screen

n clearing comment text only

n inserting and deleting lines

n using program function keys

n displaying continued lines of command output

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

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 139

Screen Control

The clear screen command consists of two periods followed by two blanks. Enter ..bb 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.

Figure 45 on page 139 is an example of using /DCL to clear help text.

FIGURE 45. Using the DCL Command

On the next cycle, the panel shown in Figure 46 on page 139 appears.

FIGURE 46. Result of the DCL Command

/DCL_________________ VTM OI-II /C I61D 08/18/99 12:00:00 B >.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 OI-II /C I61D 08/18/99 12:00:00 B.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


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.

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 used in the menu system. 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

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 141

Screen Control

various types of analysis. Use the .PFK immediate command to list the settings.

Figure 47 on page 141 lists the default PF key definitions in the command interface.

FIGURE 47. 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.

.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+ 22=#22 /* CONTROLLING EXCEPTION ANALYSIS+ 23=#23 /* CONTROLLING EXCEPTION GROUPS+ 24=PFKDEF /* CMD/MENU MODE TOGGLE

.PFK19=/DEF ON /* Turns definition mode on

.PFK20=/DEF OFF /* Turns definition mode off

Screen Control


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:

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.

+.PFK21=/P /* PRINT CURRENT SCREEN

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

Command Basics 143

Screen Control

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 command 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 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 is not updated 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 so, place the cursor in the Home position, then move it back one space to the blank space in column 1 of the INFO-line. The words “Hold Mode” appear 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 Control


Screen logging

OMEGAMON 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 Figure 48 on page 144.

FIGURE 48. 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 appears 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 updatingOMEGAMON 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.

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.

_______________ KOIMENU VTM OI-II /C I61D 08/18/99 12:00:00 B 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 145

Screen Control

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 displayed by .SET 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 Control


Screen Spaces 147

Screen Spaces

Chapter overviewThrough its powerful screen space feature, OMEGAMON II can store, recall, and invoke a set of commands. Candle Corporation 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Creating or Modifying Screen Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Loading Screen Spaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Listing Screen Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Renaming a Screen Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Deleting a Screen Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Invoking Screen Spaces Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Conditional screen space fetching . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Delayed screen space fetching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Looping screen spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Testing .FGO routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Manipulating the log within screen spaces. . . . . . . . . . . . . . . . . . . . . 156

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 149

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.

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

– Figure 49 on page 150 shows a screen created for a screen space named SAMPLE. Notice the command explanations in the divider lines.



FIGURE 49. 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 159.

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 IMS Realtime Commands Referance 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 OI-II /C I61D 08/18/99 12:00:00 B. >================= DISPLAY GENERAL IMS INFORMATION ========================== > ISYS > >================= DISPLAY OVERVIEW MVS INFORMATION ========================== > MSYS > >================= DISPLAY EXCEPTIONAL CONDITIONS ========================== > LXIMS > >================= DISPLAY PROGRAM ISOLATION CONFLICTS ====================== > XPIQ >

Screen Spaces 151

Loading Screen Spaces

Loading Screen Spaces

IntroductionThe LSCR immediate command loads screen spaces from disk storage to main storage. By placing screen spaces in main storage with LSCR, you make them more available and more easily fetched. If a disk is not available, you can continue to invoke the screen spaces that you loaded into main storage with LSCR.

The format is:

LSCR cccccccc cccccccc . . . cccccccc

The variables are screen space names. Specify screen space names starting in column 8. You can load as many screens as can fit on the input line, up to the last eight columns. The following example instructs OMEGAMON II to load screen spaces ZZ1, ZZ2, and ZZ3 from disk to main storage.

LSCR ZZ1 ZZ2 ZZ3

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 pointed to by the RKOIPCSV and CANSOI ddnames. 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 IMS Realtime Commands Referance Manual for details.

Figure 50 on page 152 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 CANSOI concatenation.

FIGURE 50. Screen Space List

>SCRNB $ thru 99999999> In-storage screen facility 20 members 4232 bytes used> $ #01 #02 #03 DEBUG DEBUG01 DEBUG02 DEBUG03 ...> RKOIPCSV CANDLE. RKOIPCSV> #01 SAMPLE VSAM> CANSOI (DUP.) CANDLE. RKOIPCSV> CANSOI+01 CANDLE. CANSOI> #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 &PR.INIT00 PAM> SCREEN SCREENS SIT SLOT SLOTS STOP STOPC STOPI> SUBPOOLS TABLES TASK TASKS VIRTUAL VSAM

Screen Spaces 153

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 the screen space is to be found.

To rename the SAMPLE screen space to EXAMPLE in both main storage and RKOIPCSV, enter:

RENMB SAMPLE EXAMPLE

The following message appears:

>> Member “SAMPLE” Renamed to “EXAMPLE” Both In-Storage and in RKOIPCSV <<

The screen space SAMPLE no longer exists.

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 pointed to by the RKOIPCSV ddname, not from CANSOI, the read-only dataset. The DELT command accepts an argument specifying where the screen space is to be found.

If you want to delete the screen space SAMPLE from both main storage and RKOIPCSV, enter:

DELTB SAMPLE

The following message appears:

> >> Member “SAMPLE “ Deleted Both In-Storage and from RKOIPCSV <<

Screen Spaces 155

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 IMS Realtime Commands Referance 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. 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.



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 157

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 arguments

n variable substitution

n the zooming feature

n secondary dedicated terminals

If 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. . . . . . . . . . . . . . . . . . . . . . . 158Setting and Using Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159The Zooming Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Secondary Console Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

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 a rate argument is used 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. Their values are initialized by OMEGAMON II.

&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. /ZOOM 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 IMS 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 OI-II /C I61D 08/18/99 12:00:00 B> 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.

165

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 IMS system.

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

Resolving a Response Time Problem 167

Resolving a Response Time Problem

Chapter overviewThis chapter explains how to solve a database I/O conflict response time degradation problem.

Chapter contentsIdentifying Poor Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Analyzing Response Times for a Group . . . . . . . . . . . . . . . . . . . . . . . . . 170Determining Source of Degradation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Identifying the Cause of Degradation . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Identifying DASD Problems with a Database . . . . . . . . . . . . . . . . . . . . . 174Finding Cause of I/O Contention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

12

Scenario


Scenario

IntroductionResponse time degradation can be very frustrating for your customers and ultimately for your systems programmers. Generally you find out that a user is experiencing poor response time when you receive a call from a user. The problem requires quick diagnosis and resolution.


Identifying Poor Response Time

Identifying Poor Response Time

IntroductionYou are monitoring your system from the System Overview panel when you notice that the CLASS 1 response time status indicator is red. You also notice that the Conflicts status indicator is red. This may indicate that some database-related exception condition is causing poor response time for CLASS 1. You decide to find out more about the response time.

FIGURE 51. Response Times Status Indicator - Critical

Actions GoTo Options Help ------------------------------------------------------------01/02/97 12:00:00 System Overview IMS: I51A____ + Select a component with “S” to show details+-----------------------------------------------------------------------------+| Response Times | Status | Alerts ||------------------+--------------------------------------+-------------------|| _ All ----- | _ Trans. ----- _ CPU ----- | _ Pools ----- || _ Other ----- | _ Virt. Stor. ----- _ I/O ----- | _ MessageQ ----- || _ CLASS 1 ##### | _ IMS Status ===== _ XRF ----- | || _ CLASS 2 ----- | _ Traces ===== _ ESS ----- | _ Regions ----- || _ CLASS 3 ----- | _ Bufr. Pools ----- | _ Logging ----- || _ CLASS 4 ----- |--------------------------------------| || _ CLASS 5 ----- | Operator Assist | _ Databases ----- || _ PSB 1 ----- |--------------------------------------| _ Fast Path ----- || _ PSB 2 ----- | _ Programs _ Trans. | || _ PSB 3 ----- | _ Regions _ Logging | _ Conflicts ##### || | _ Databases _ Network | _ Terminals ----- || | _ Conversatn. _ Users | |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd F8=Fwd F10=Action Bar PA1=Switch PA2=OMEGAVIEW

Analyzing Response Times for a Group


Analyzing Response Times for a Group

IntroductionFirst you should request the Show details action for CLASS 1. To do this, position your cursor next to CLASS 1 and press Enter.

OMEGAMON II displays the Response Time Analysis panel for CLASS 1 ). This panel displays the average response times for the items that make up this group. OMEGAMON II reports the response time for the past 15- minute, 30- minute, and 1-hour intervals and highlights the values for tripped exceptions on this panel.

FIGURE 52. Response Time Analysis for CLASS 1 Panel

Notice in this figure that the response time of transactions that use PSBs beginning with ABCPSB has been poor.

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:00:00 Response Time 1 Analysis for Group: CLASS 1IMS: I51A____ + Lines 1 to 4 of 4+-----------------------------------------------------------------------------+| | Interval 00:15 hrs | Interval 00:30 hrs | Interval 01:00 hrs || Item ID | Elapsed 00:06:16 | Elapsed 00:21:16 | Elapsed 00:51:16 ||--------------+--------------------+--------------------+--------------------|| CLASS1 aug | (79) 7.1s | (195) 6.9s | (269) 7.2s || T=ADDI* | ( 5) 6.3s | (269) 7.2s | (102) 2.3s || T=ABF* | ( 1) 3.4s | (102) 2.3s | ( 10) 1.4s || P=ABCPSB* | (73) 8.4s | (157) 9.7s | (157) 9.7s || | | | |+-----------------------------------------------------------------------------+ (Response Time) <Response Time Components> <Bottlenecks> F1=Help F2=Keys F3=Exit F5=Refresh F6=Console **=Bkwd **=Fwd F10=Action Bar F11=More F15=System Overview PA1=Switch PA2=OMEGAVIEW


Determining Source of Degradation


IntroductionTo find out more about where this group of transactions is spending most of its time, you will need to determine which part of the system is delaying the processing of the transactions. Select the <Bottlenecks> pushbutton, to display bottleneck analysis information for the Class 1 group, as shown in the following figure.

FIGURE 53. Bottlenecks Analysis for CLASS 1

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

GoTo Options Help ------------------------------------------------------------01/02/97 12:00:00 Bottlenecks Analysis for Group : CLASS1 IMS: I51A____ + +-----------------------------------------------------------------------------+| Elapsed time . . . : 5 SEC Samples taken (short) . : 2 || Suppress states . . < 0 % Samples taken (long) . : 2 || Display Competing Transactions + Sampling interval . . . : 55 tenths-sec |+-----------------------------------------------------------------------------+ Lines 1 to 17 of 17 +-----------------------------------------------------------------------------+| Wait Reason | Short Term | Long Term ||-----------------------------------------------------------------------------|| Using CPU: | 9.8 |> | 8.8 |> || Using CPU in Appl | (2.4) |> | (2.5) |> || Using CPU in IMS | (7.3) |> | (6.3) |> || Scheduling Waits: | 17.0 |-> | 21.5 |----> || Wait for MPP | (3.9) |> | (8.5) |> || Wait for GU | (13.1) |-> | (12.9) |-> || IMS Activity: | 8.2 |> | 20.2 |----> || LGMSG I/O | (.4) |> | (1.1) |> || SYNC Point Wait | (1.8) |> | (2.1) |> || ISWITCHED to CTL | (5.7) |> | (16.8) |-> || Database I/O Waits | 46.7 |---------> | 39.1 |--------> || PAYROLL1 | (44.3) |--------> | (34.9) |-------> || UBTCLP0C | (.9) |> | (2.5) |> || MVS Waits: | 18.0 |-> | 10.1 |> || CPU Wait (MPP/BMP)| (8.2) |> | (5.5) |> || Program Fetch I/O | (3.4) |> | (.3) |> || Dep Priv Page | (6.3) |> | (2.6) |> || - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - || Avg. Trans Competing: 345 478 |+-----------------------------------------------------------------------------+ <Response Time> <Response Time Components> (Bottlenecks) F1=Help F2=Keys F3=Exit F5=Refresh F6=Console **=Bkwd **=Fwd F10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW



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 PSB 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%.

Note: All OMEGAMON II users monitoring the same IMS share the same sampling interval.

When you review the Wait Reason column, you notice that Database I/O Waits is the biggest contributor to degradation for this class.


Identifying the Cause of Degradation

Identifying the Cause of Degradation

IntroductionPress F15 to return to the System Overview panel. You see that the Conflicts indicator is still red. You want to determine if there are any conflicts that would cause database I/O waits and affect transactions that use PSBs starting with ABCPSB.

To Show details about Conflicts, position your cursor next to Conflicts and press Enter. OMEGAMON II displays the first of three Conflicts panels. You find that the region that uses ABCPSB1 is in UP/WAT status. You also notice on this panel that database PAYROLL1 is affected by the conflict.

FIGURE 54. Database Conflicts Panel

Note:

n To investigate database I/O wait problems, continue with the procedure in “Identifying DASD Problems with a Database” on page 174.

n You can navigate to the Region Details panel from here for more information.

Actions GoTo Options Help------------------------------------------------------------- 01/02/97 12:00:00 Database Conflicts IMS: I51A____ + Lines 1 to 2 of 2 +----------+-------+--------+---------+--------+--------+---------+--------+----+| Region |Subsys |PSBname |TX/RgID |LTerm ID|Status |DB/area |RBA/RBN |DCB |+----------+-------+--------+---------+--------+--------+---------+--------+----+| _IMSMP41A| IMSA | ABCPSB1| TXADDPRC|IEQSDBQ8| UP/WAT | PAYROLL1|001C99A0| 1 || _IMSMP41A| IMSA | ABCPSB1| TXADDPRC|IEQSDBQ8| UP/WAT | PAYROLL1|001C99A0| 1 |+----------+-------+--------+---------+--------+--------+---------+--------+----+ (Database Conflicts) <CI Conflicts> <Latch Conflicts> F1=Help F2=Keys F3=Exit F5=Refresh F6=Console **=Bkwd **=FwdF10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW

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 the PAYROLL1 database is experiencing an extremely high EXCP (I/O) rate.

FIGURE 55. Database Summary Panel

From the Database Summary panel, select the PAYROLL1 database. The Device Statistics for Database PAYROLL1 panel displays, as shown in Figure 56 on page 175.

Actions GoTo View Options Help ------------------------------------------------------------- 01/02/97 12:00:00 Database Summary IMS: I51A__+ 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 PA2=OMEGAVIEW



FIGURE 56. Device Statistics for Database Panel

This 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. Refer to “Finding Cause of I/O Contention” on page 177, to identify jobs or datasets which may be contributing to your DASD problems.

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 Figure 57 on page 176.

GoTo Options Help ------------------------------------------------------------- 01/02/97 12:00:00 Device Statistics for Database PAYROLL1 IMS: I51A____ + +-------------------------------------------------------------------------------+| DDName : PAYROLL1 Average EXCP Rate: .21/s || DSName : IMS.V6R1.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> F1=Help F2=Keys F3=Exit F5=Refresh F6=Console **=Bkwd **=Fwd F10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW



FIGURE 57. Details for Database 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 IMS: I51A____ + +-----------------------------------------------------------------------------+| DD Name: PAYROLL1 Dataset Name: IMS.V6R1.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 PA1=SwitchPA2=OMEGAVIEW


Finding Cause of I/O Contention


IntroductionUse OMEGAMON II’s menu interface to find out about the non-IMS dataset on the volume, that may be the cause of your I/O contention problems.

To access the menu system, open the GoTo pull-down, and select Cmd/Menu Interface (OMEGAMON). The Zoom to OMEGAMON pop-up displays. Make sure that OMEGAMON screen space is blank and press Enter. The Main Menu displays.

FIGURE 58. OMEGAMON Main Menu

From the Main Menu, select option C for Components. Then select option A for I/O. Position your cursor on volume IMS427 and press F11 for further details on the non-IMS volume. OMEGAMON IIissues the DPLTnn command. Look at the output to find out about the I/O activity of the volume.

To solve the contention problem, you may want to follow one of these recommendations:

1. Terminate the non-IMS job that is using the volume.2. When possible, move the non-IMS dataset to a different volume.

Press F15, to return to the CUA interface.

__________________ZMENU VTM OI-II /C I61A 03/11/99 9:59:27 0B> 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 IMS Performance Monitor Main Menu _ E EXCEPTIONS ....... Current and potential system problems, latch conflicts_ R RESPONSE TIME .... Transaction response times (RTA users)_ B BOTTLENECKS ...... Resource contention (bottleneck analysis) (DEXAN users) _ M MONITOR .......... IMS status, graphs, and time controlled operations_ W WORKLOAD ......... PSBs, DMBs, transactions, regions, and classes_ L LINES ............ Terminals, nodes, and lines_ 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_ P PROFILE .......... Profile maintenance and session settings

Managing Groups of IMS Resources 179

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Rules for Creating Resource Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Selecting a PSB Group Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Creating a New PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Copying a PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Deleting a PSB from a PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Stopping a PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Starting a PSB Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

13

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 group

n delete an existing resource group

n copy the contents of an existing group into a new or existing group

n add resources to a group

n 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 182, before continuing with the procedure “Selecting a PSB Group Name” on page 183.

Rules for Creating Resource Groups


Rules for Creating Resource Groups

RulesYou 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 and assigning the same resources. As soon as you copy a group give the new group another name.


Selecting a PSB Group Name


StepsBefore 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 and press Enter.

FIGURE 59. System Overview Panel - Select Programs

OMEGAMON II displays the PSB Operations panel, shown in Figure 60 on page 184.

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: I51A__+ Select a component with “S” to show details+-----------------------------------------------------------------------------+| Response Times | Status | Alerts ||------------------+--------------------------------------+-------------------|| _ All ----- | _ Trans. ----- _ CPU ----- | _ Pools ----- || _ Other ----- | _ Virt. Stor. ----- _ I/O ----- | _ MessageQ ----- || _ CLASS 1 ----- | _ IMS Status ===== _ XRF ----- | || _ CLASS 2 ----- | _ Traces ===== _ ESS ----- | _ Regions ##### || _ CLASS 3 ----- | _ Bufr. Pools ----- | _ Logging ----- || _ CLASS 4 ----- |--------------------------------------| || _ CLASS 5 ----- | Operator Assist | _ Databases ----- || _ PSB 1 ----- |--------------------------------------| _ Fast Path ----- || _ PSB 2 ----- | _ Programs _ Trans. | || _ PSB 3 ----- | _ Regions _ Logging | _ Conflicts ----- || | _ Databases _ Network | _ Terminals ----- || More : + | _ Conversatn. _ Users | |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd F8=Fwd F10=Action Bar PA1=Switch PA2=OMEGAVIEW



FIGURE 60. 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 Figure 61 on page 185.

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:00:10 PSB Operations IMS: I51A__+ 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 || TCHCK | Not-Scheduled | Batch |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd **=Fwd F10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW



FIGURE 61. 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 Figure 62 on page 186.

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:01:00 PSB Operations IMS: I51A__+ 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 |+---| |------------------------+ | 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



FIGURE 62. 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 187 or “Copying a PSB Group” on page 191.

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:01:00 PSB Operations IMS: I51A__+ VIEW: Pattern=PAY* L=Lock N=Unlock O=Stop R=Start Group Management: C=Copy Group_ PAYROLL + Lines 1 to 10 of 10+-----------------------------------------------------------------------------+| PSB | Status | Type ||--------------------------+-------------------------+------------------------|| _ 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 |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd **=Fwd F10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW


Creating a New PSB Group


StepsTo 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 63. 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 Figure 64 on page 188, 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:01:00 PSB Operations IMS: I51A__+VIEW: L=Lock N=Unlock O=Stop R=Start Group Management: C=Copy Group 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 |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd **=Fwd F10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW



FIGURE 64. 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 Figure 65 on page 189.

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:01:00 PSB Operations IMS: I51A__+ VIEW: L=Lock N=Unlock O=Stop R=Start Group Management: C=Copy Group 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 | | _ PAYVAC2 Scheduled Online | | _ PAYVAC3 Scheduled Online | | | F1=Help F | F1=Help F3=Exit F4=Prompt F7=Bkwd F8=Fwd F12=Cancel | F10=Action +-------------------------------------------------------------+



FIGURE 65. 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.The PAYSTOP group is now created with all of the specified PSBs, as shown in Figure 66 on page 190.

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:01:00 PSB Operations IMS: I51A__+ VIEW: 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 |+---------- | _ PAYVAC3 Scheduled Online | | _ PAYW41 Scheduled Online | | | F1=Help F | F1=Help F3=Exit F4=Prompt F7=Bkwd F8=Fwd F12=Cancel | F10=Action +-------------------------------------------------------------+



FIGURE 66. PSB Operations for PAYSTOP Group

To stop the PAYSTOP group, continue with the procedure “Deleting a PSB from a PSB Group” on page 195.

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.

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:01:00 PSB Operations IMS: I51A__+ VIEW: 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 |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd **=Fwd F10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW


Copying a PSB Group

Copying a PSB Group

StepsTo 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 67. 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 68 on page 192).

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:01:00 PSB Operations IMS: I51A__+ VIEW: L=Lock N=Unlock O=Stop R=Start Group Management: C=Copy Group D=Delete Group or Resourcec 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 |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd **=Fwd F10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW

Copying a PSB Group


FIGURE 68. 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 Figure 69 on page 193, 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

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:01:00 PSB Operations IMS: I51A__+ VIEW: 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. |F1=Help F2=Keys F3=Exit F4=P| 2. No, cancel create. |F10=Action Bar F15=System Ov| | | | | F1=Help F12=Cancel | +-------------------------------------------------+


Copying a PSB Group

FIGURE 69. Copy Resources Pop-up

5. 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 Figure 66 on page 190.

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:01:00 PSB Operations IMS: I51A__+ VIEW: 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 |F1=Help F2=Keys F3=Exit F| |F10=Action Bar F15=System| 3. Copy all resources from PAYROLL to PAYSTOP | | 4. Stop copy operation. | | | | F12=Cancel | +----------------------------------------------------+

Copying a PSB Group


FIGURE 70. 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 195.

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:01:00 PSB Operations IMS: I51A__+ VIEW: 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 | 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 |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd **=Fwd F10=Action Bar F15=System Overview F19=Left F20=Right PA1=Switch PA2=OMEGAVIEW


Deleting a PSB from a PSB Group

Deleting a PSB from a PSB Group

StepsTo 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 (Figure 70 on page 194).

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 71. 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:01:00 PSB Operations IMS: I51A__+ VIEW: 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 | Schedulable | Batch || _ PAYEMP1 | Scheduled | Online || _ PAYEMP2 | Scheduled | Online || _ PAYEMP3 | Scheduled | Online || d PAYVAC1 | Scheduled | Online || _ PAYVAC2 | Scheduled | Online || +-----------------------------------------------+ || | Delete Resources | || | Delete PAYVAC1 from group PAYSTOP? | |+-----------| |----------+ | 1 1. Yes, delete PAYVAC1 from PAYSTOP | | 2. No, do not delete PAYAC1 from PAYSTOP | | | | 3. Yes, delete All selected resources | | 4. Cancel delete operation | | | | F1=Help F12=Cancel | +-----------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console PA1=Switch PA2=OMEGAVIEW

Stopping a PSB Group


Stopping a PSB Group

StepsTo 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 the changed status for all of the PSBs in the PAYSTOP group.

FIGURE 72. 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 197 to start the PAYSTOP PSB group.

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:01:00 PSB Operations IMS: I51A__+ VIEW: 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 |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd **=Fwd F10=Action Bar F15=System Overview F19=Left F20=Right PA1=Switch PA2=OMEGAVIEW


Starting a PSB Group


StepsTo 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 73. PSB Operations for PAYSTOP Group - Status Schedulable

Actions GoTo View Options Help ------------------------------------------------------------ 01/02/97 12:01:00 PSB Operations IMS: I51A__+ VIEW: 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 **=Bkwd **=Fwd F10=Action Bar F15=System Overview F19=Left F20=Right PA1=Switch PA2=OMEGAVIEW

Analyzing Transaction Queuing 199

Analyzing Transaction Queuing

Chapter overviewThis chapter explains how you can use OMEGAMON II’s status lights to analyze a response time problem.

Chapter contentsScenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Spotting a Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Selecting Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Identifying the Problem Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Determining Transaction Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Investigating the PSB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205Taking Action on the PSB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Rechecking the Transaction Input Queue . . . . . . . . . . . . . . . . . . . . . . . . 207Checking the System Overview Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Confirming the Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Resolving the Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

14

Scenario


Scenario

IntroductionThere are times when measuring response time alone cannot alert you to a problem that is preventing a transaction from processing. Using OMEGAMON II’s status lights, that indicate when there is a problem in the system that can affect response time, you can solve a response time problem before the user even notices it.


Spotting a Status Indicator

Spotting a Status Indicator

IntroductionSuppose you are monitoring your system from the System Overview panel when you notice that the Transactions Status light turns red. At the same time, you notice that the Response Time indicators are still green.

FIGURE 74. Transactions Status Light - Critical

Actions GoTo Options Help ------------------------------------------------------------01/02/97 12:00:00 System Overview IMS: I51A ___ + Select a component with “S” to show details+-----------------------------------------------------------------------------+| Response Times | Status | Alerts ||------------------+--------------------------------------+-------------------|| _ All ----- | _ Trans. ##### _ CPU ----- | _ Pools ----- || _ Other ----- | _ Virt. Stor. ----- _ I/O ----- | _ MessageQ ----- || _ CLASS 1 ----- | _ IMS Status ===== _ XRF ----- | || _ CLASS 2 ----- | _ Traces ===== _ ESS ----- | _ Regions ----- || _ CLASS 3 ----- | _ Bufr. Pools ----- | _ Logging ----- || _ CLASS 4 ----- |--------------------------------------| || _ CLASS 5 ----- | Operator Assist | _ Databases ----- || _ PSB 1 ----- |--------------------------------------| _ Fast Path ----- || _ PSB 2 ----- | _ Programs _ Trans. | || _ PSB 3 ----- | _ Regions _ Logging | _ Conflicts ----- || | _ Databases _ Network | _ Terminals ----- || More : + | _ Conversatn. _ Users | |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd F8=Fwd F10=Action Bar PA1=Switch PA2=OMEGAVIEW

Selecting Transactions


Selecting Transactions

IntroductionTo Show details for Transactions, position your cursor next to Trans and press Enter.

OMEGAMON II displays a Transactions Tripped Exceptions pop-up with a list of all transactions that exceeded the transaction threshold. Press Enter to continue, and OMEGAMON II displays the Transactions panel. This panel shows status, class, and input queue length for each transaction defined in the IMS system.

FIGURE 75. Transactions Panel

Actions GoTo View Options Help ------------------------------------------------------------01/02/97 12:00:00 Transactions IMS: I51A ___ + VIEW=ALL +--------------+----------+----------+-----------+----------------------------+| Non-FP ENQ Rate. . : .00/sec Non-FP DEQ Rate. . : .00/sec || FP BALG ENQ Rate. . : .00/sec FP BALG DEQ Rate. . : .00/sec ||--------------+----------+----------+-----------+----------------------------|| Name | | Class | Length | 0........10.....20||--------------+----------+----------+-----------+----------------------------|| _ ADDINV | Queued | 1 | 23 | 1.2 |-> || _ ADDPART | Active | 1 | 1 | 3.1 |--> || _ BMX00000 | Idle | 1 | | | || _ BMX00010 | Idle | 1 | | | || _ BMX00020 | Idle | 1 | | | || _ BMX00030 | Idle | 1 | | | || _ BMX00040 | Idle | 1 | | | || _ BMX00050 | Idle | 1 | | | || _ BMX00060 | Idle | 1 | | | || _ CLOSE | Idle | Remote | | | || _ CNX00000 | Idle | 1 | | | || _ CNX00010 | Idle | 1 | | | || _ CNX00020 | Queued | 1 | 2 | .1 |> || _ CNX00030 | Idle | 1 | | | || _ CNX00040 | Idle | 1 | | | |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F5=Refresh F6=Console **=Bkwd F8=Fwd F10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW


Identifying the Problem Transaction

Identifying the Problem Transaction

IntroductionThe first thing you notice on the Transactions panel is that the enqueue rate is higher than the dequeue rate. In Figure 75 on page 202 you can also see that Transaction ADDINV has a high input queue length. To find out more about this transaction, request Show details by positioning the cursor next to transaction ADDINV and pressing Enter.

OMEGAMON II displays the Details for Transaction ADDINV panel.

FIGURE 76. Details for Transaction ADDINV Panel

GoTo Options Help ------------------------------------------------------------01/02/97 12:00:00 Details for Transaction : ADDINV IMS: I51A ___ + +-----------------------------------------------------------------------------+| | || | || Queue length . . : 23 | Processing limit . . : 65535 || | || Status . . . . . : Queued | Parallel Limit . . . : 65535 || | || Class . . . . . . : 1 | Normal priority . . : 7 || | || Program type . . : Online | Current priority . . : 7 || | || Program name . . : PADDINV | Limit Priority . . . : 10 || | || Serial . . . . . : No | Attributes . . . . . : MS || | || No. of regions scheduled 0 | || | || | |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F5=Refresh F6=Console F10=Action Bar F15=System Overview

Determining Transaction Details


Determining Transaction Details

IntroductionOn the Details for Transaction ADDINV panel, you notice that the status is Queued. From this you can conclude that the transaction itself is not the problem. On this same screen you note the related program name, PADDINV. (Typically the program name is the same as the PSB.)


Investigating the PSB

Investigating the PSB

IntroductionNow you decide to investigate the related PSB. To do this, open the GoTo pull-down and select Index. In the index, move the cursor next to Programs OP and press Enter. OMEGAMON II displays the PSB Operations panel, as shown in the following figure.

FIGURE 77. PSB Operations Panel

On the PSB Operations panel, open the View pull-down and select Pattern. Then enter PADDINV. OMEGAMON II will display only PADDINV. When you see PADDINV, you notice it is stopped.

Actions Goto View Options Help ------------------------------------------------------------01/02/97 12:00:00 PSB Operations IMS: I51A ___ + VIEW=ALL L=Lock N=Unlock O=Stop R=Start ________ + Lines 62 to 78 of 107 +-----------------------------------------------------------------------------+| PSB | Status | Type ||----------------------+---------------------------+--------------------------|| _ PABMP030 | PSB-Stop | Batch || _ PABMP040 | PSB-Stop | Batch || _ PADDINV | PSB-STOP | Online || _ PADDPART | Schedulable | Online || _ PBMSTX7R | Schedulable | Online || _ RBMSTX8A | Active | Online || _ RSTK0010 | PSB-Stop | Online || _ RSTK0020 | PSB-Stop | Online || _ RSTK0030 | Schedulable | Online || _ RMPGH120 | Schedulable | Online || _ RMPGH130 | Schedulable | Online || _ RMPGH140 | Schedulable | Online || _ RMPGH150 | Schedulable | Online || _ RPQLD149 | Schedulable | Online |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F5=Refresh F6=Console **=Bkwd F8=Fwd F10=Action Bar F15=System Overview

Taking Action on the PSB


Taking Action on the PSB

IntroductionTry to resolve the problem by starting the PSB. To do this, type an R next to the PADDINV and press Enter.

FIGURE 78. PSB Operations Panel after Issuing an IMS Start Command

Actions GoTo View Options Help ------------------------------------------------------------01/02/97 12:00:00 PSB Operations IMS: I51A ___ + VIEW=ALL L=Lock N=Unlock O=Stop R=Start ________ + Lines 62 to 78 of 107+-----------------------------------------------------------------------------+| PSB | Status | Type ||----------------------+---------------------------+--------------------------|| _ PABMP030 | PSB-Stop | Batch || _ PABMP040 | PSB-Stop | Batch || _ PADDINV | Schedulable | Online || _ PADDPART | Schedulable | Online || _ PBMSTX7R | Schedulable | Online || _ RBMSTX8A | Active | Online || _ RSTK0010 | PSB-Stop | Online || _ RSTK0020 | PSB-Stop | Online || _ RSTK0030 | Schedulable | Online || _ RMPGH120 | Schedulable | Online || _ RMPGH130 | Schedulable | Online || _ RMPGH140 | Schedulable | Online || _ RMPGH150 | Schedulable | Online || _ RPQLD149 | Schedulable | Online |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F5=Refresh F6=Console **=Bkwd F8=Fwd F10=Action Bar F15=System Overview


Rechecking the Transaction Input Queue

Rechecking the Transaction Input Queue

IntroductionPress F3 to return to the Details for Transaction ADDINV panel. Check the input queue. If the input queue is still very high for that transaction, the problem has not been corrected.

FIGURE 79. Details for Transaction with High Input Queue

Goto Options Help ------------------------------------------------------------01/02/97 12:00:00 Details for Transaction : ADDINV IMS: I51A ___ + +-----------------------------------------------------------------------------+| | || | || Queue length . . : 25 | Processing limit . . : 65535 || | || Status . . . . . : Queued | Parallel limit . . . : 65535 || | || Class . . . . . . : 1 | Normal priority . . : || | || Program type . . : Online | Current priority . . : 7 || Program name . . : PADDINV | || | Limit priority . . . : 10 || Serial . . . . . : No | || | Attributes . . . . . : .. .. MS || No. of regions scheduled: 0 | || | || | |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F5=Refresh F6=Console F10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW

Checking the System Overview Panel


Checking the System Overview Panel

IntroductionSince starting the PSB did not resolve your response time problem, press F15 to return to the System Overview panel and continue your investigation.

On the System Overview panel, you notice that the Pools Alert indicator is red. Request the Show details action for Pools, by moving the cursor next to Pools and pressing Enter. OMEGAMON II displays a pop-up that shows you that The PSBW POOL IS 100% USED.


Confirming the Problem

Confirming the Problem

IntroductionTo confirm the problem, press F6 to display the IMS console panel. On this panel the IMS console log displays. Look for the following message:

DFS9931 PSBW POOL TOO SMALL,

UNABLE TO SCHEDULE PSB PADDINV.

Resolving the Problem


Resolving the Problem

IntroductionA PSB workarea is required by each active PSB and is allocated from the PSBW pool when the PSB is scheduled. In this example, the incapacity to schedule for a specific PSB workpool is causing the slow response. Once you know that the PSB workpool is causing slow response, you may want to try one or more of the following recommendations to solve the problem:

1. Try to limit the number of dependent regions running concurrently, especially BMPs with a large number of PCBs.

2. Try to decrease the size of PSBs to reduce PSBW requirements. Use the IOASIZE, SSASIZE, and ISENFLD parameters in the PSBGEN to limit the storage a PSB requires

3. Increase the PSBW pool size by specifying a larger value for PSBW parameter on the IMS control region startup JCL.

Identifying a Looping BMP Region 211

Identifying a Looping BMP Region

Chapter overviewThis chapter explains how to use OMEGAMON II to determine if a BMP transaction is looping.

Chapter contentsScenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212Displaying CPU Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Identifying Suspect BMP Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Verifying the Situation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Examining the Region in Question . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Viewing Details for DL/I Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217Viewing Details for Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Taking Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

15

Scenario


Scenario

IntroductionIt is often difficult to determine if a BMP transaction is looping. Making this type of determination requires information that is hard to collect using standard IMS functions. As a result, you may often be forced to make that determination without enough data. Using the following operations, OMEGAMON II helps you obtain information to make this determination.


Displaying CPU Details

Displaying CPU Details

IntroductionSuppose you are monitoring your system from the System Overview panel when you notice that the CPU status indicator is red. First you request the Show details action for CPU. To do this, position your cursor next to CPU and press Enter.

OMEGAMON II displays the CPU panel, which lists the CPU rate of all the regions that are currently running.

FIGURE 80. CPU Panel

Actions GoTo Options Help ------------------------------------------------------------01/02/97 12:00:00 CPU IMS: I51A + Lines 1 to 11 of 11+-----------------------------------------------------------------------------+| | | Rates | | || Region | Type |-----------------| Total | Graph || | | TCB | SRB | |0.........0.24......0.48||-------------+----------+--------+--------+---------+------------------------|| IMS610AC | Control | .027 | .001 | .028 |--------------> || IMS610AB | DBRC | .002 | | .003 | || IMS610AD | DLS | | .003 | .004 | || _ IMS610AI | IRLM | | | | || _ BMPID005 | BMP | .026 | .001 | .027 |-------------> || _ BMPUT001 | BMP | .067 | .001 | .068 |---------------------->>|| _ IFP51001 | FASTPATH | .007 | | .007 | || _ IFP51002 | FASTPATH | .005 | | .006 | |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd **=Fwd F10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW

Identifying Suspect BMP Region


Identifying Suspect BMP Region

IntroductionOMEGAMON II uses reverse video to graphically display the CPU rate of the regions that are currently running. You find that the CPU rate of BMPUT001 is much higher than others, and you suspect that this BMP region is the culprit that triggered the red status light for CPU on the System Overview. However, it is too early to conclude that this region is looping.

To gather more information about this region, you open the GoTo pull-down and select Index. Then select the Regions panel from the index.


Verifying the Situation

Verifying the Situation

IntroductionOMEGAMON II displays the Regions Summary panel. From this panel, you can see the region type, current status, CPU rate, working set size, I/O rate, locks, and page-in rate of all the regions at a glance. Here you find that BMPUT001 is the only region that is not in n/a, Idle, or Wt-CPU status. This increases your suspicion that BMPUT001 might be in a transaction loop.

To find out more about this region, request Show details by moving the cursor to the input field next to BMPUT001 and pressing Enter.

FIGURE 81. Regions Summary Panel

The Regions Summary panel spans more than one screen. To see the complete panel, you can scroll to the right by using F20. To scroll left, use F19.

Actions GoTo Options Help ------------------------------------------------------------ 01/02/97 12:00:00 Regions Summary IMS: I51A + Lines 1 to 8 of 8 More: >+----------------------------------------------------------------------+| Name | Type | Status | CPU Rate| Working| Locks|Transaction || | | | | Set | Held | ||------------+---------+--------+---------+--------+------+------------+| IMS610AC | CONTROL |--n/a-- | ....... | 1432K | 0 | --n/a-- || IMS610AB | DBRC |--n/a-- | ....... | 192K | 0 | --n/a-- || IMS610AD | DLS |--n/a-- | ....... | 576K | 0 | --n/a-- || _ IMS610AI | IRLM |--n/a-- | ....... | 408K | 0 | --n/a-- || _ BMPID005 | BMP | Idle | ....... | 220K | 0 | --n/a-- || _ BMPUT001 | BMP |Ex-Drgn | ....... | 208K | 0 | --n/a-- || _ IFP51001 | FASTPATH| Idle | ....... | 220K | 0 | --n/a-- || _ IFP51002 | FASTPATH| Idle | ....... | 220K | 0 | --n/a-- |+----------------------------------------------------------------------+ (Regions) <Virtual Storage> <CPU> F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd **=Fwd F10=Action Bar F15=System Overview F19=Left F20=Right PA1=Switch PA2=OMEGAVIEW

Examining the Region in Question


Examining the Region in Question

IntroductionOMEGAMON II displays the Details for Region panel. This panel shows you information about the region, such as the PSB name, transaction name, transaction class, number of database calls, locks held, and elapsed time.

Note that the number of database calls is unusually small for a BMP region, compared to the region’s elapsed time. Since BMP transactions are normally dedicated to extensive processing of a database, you would consider this an unusual situation. You now have enough information to assume that this BMP region is probably looping.

FIGURE 82. Details for Region BMPUT001 Panel

Actions GoTo Options Help ---------------------------------------------------------- 12/19/98 15:13:35 BMPUT001 Details IMS: I51A ++------------------------------------+---------------------------------------+| Region Name . . . . . : BMPUT001 | Lock Structure BMP || Status . . . . . . . : --n/a-- | Name . . . . . . . . . : . . . RGN || I/O Rate . . . . . . : .0 | Size . . . . . . . . . : 0 6 || Region Utilization : .000 | T-- || Working Set . . . . . : 272K | Record List Entries (RLEs) SEC || BMPUT001 current | Used . . . . . . . . . : 0 || CSA usage . . . . : 604160 | In Lock Structure . . : 0 || | Percentage Used . . . : .00% || BMPUT001 Startup Options | SR1 || BMPUT001 Name . . . : BMPT | Total number of E-- || BMPUT001 ID . . . . : 1 | Real Contention Granted: 0 QLD || Maximum CSA . . . . : 3M | Real Contention Rate . : .00/s 05 || PC . . . . . . . . . : NO | Global False Contention: 0 :27 || Scope . . . . . . . : LOCAL | False Contention Rate : .00/s || | |+------------------------------------+---------------------------------------+ F1=Help F2=Keys F3=Exit F5=Refresh F6=Console F10=Action Bar F11=More F15=System Overview PA1=Switch PA2=OMEGAVIEW


Viewing Details for DL/I Calls

Viewing Details for DL/I Calls

IntroductionYou can look at additional information on current DL/I calls by selecting the Current DL/I Calls field on the Details for Region panel. The following is an example of the Calls Details panel.

FIGURE 83. Calls Details Panel with SAP Transaction

Note: You can navigate to the Region Locks Detail panel from this panel.

GoTo Options Help ---------------------------------------------------------- 01/02/97 12:00:00 Calls Details for IMS41MS2 IMS: I51A ++------------------------------------+----------------------------------------+| Total DL/I Calls. . . . : 7 | Delete Calls . . . . . . . . : 0 || Get Unique Calls. . . . : 1 | Replace Calls. . . . . . . . : 3 || Get Next Calls. . . . . : 0 | Message Number . . . . . . . : 9 || Get Next w/in Parent. . : 0 | Message Get Unique Calls . . : 7 || Get Hold Calls: | Message Get Next Calls . . . : 0 || Unique . . . . . . . . : 6 | Message Insert Calls . . . . : 6 || Next . . . . . . . . . : 0 | Message Purge Calls. . . . . : 0 || Next w/in Parent . . . : 0 | Message Calls Totals . . . . : 13 |+------------------------------------+----------------------------------------+| Most Recent DL/I Call || Function : GHU || PCB : IVPDB2 00 A .&r<A1111111...................... || IOA : GCAM.................................. UPD 1234.).. || ssa 01 + : a1111111(A1111111 =GCAM......) |+------------------------------------+----------------------------------------+(DL/I Calls) <Locks> F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console F15=System Overview PA1=Switch PA2=OMEGAVIEW

Viewing Details for Locks


Viewing Details for Locks

IntroductionYou can look at additional information on locks by selecting the Locks Held field on the Details for Region panel. The following is an example of the Region Locks details panel.

FIGURE 84. Region Locks Panel

Note: You can navigate to the DL/I Calls panel from this panel.

GoTo Options Help----------------------------------------------------------01/02/97 12:00:00 Region Locks Details for IMS61MS1 IMS: I51A + Lines 1 to 1 of 1 +-------------+----------+--------------+-----------+-----+ | Subsystem | Status | DB or Area | RBA/RBN | DCB | +-------------+----------+--------------+-----------+-----+ | I41A | UP/WAT | IVPDB2 | 00026814 | 1 | +-------------+----------+--------------+-----------+-----+<DL/I Calls> (Locks)F1=Help F2=Keys F3=Exit F5=Refresh F6=Console **=Bkwd **=FwdF15=System Overview PA1=Switch PA2=OMEGAVIEW


Taking Action

Taking Action

IntroductionIf this situation continues, your system throughput will be severely impacted. To alleviate the situation, you decide to stop this BMP region. You open the GoTo pull-down and select Index. Then, you select the Regions OP panel from the index.

OMEGAMON II displays the Region Operations panel.

FIGURE 85. Region Operations Panel

Notice the action mnemonics at the top of the panel under the panel name. The mnemonic for Stop is O. Move the cursor next to BMPUT001, type an (O), and then press Enter.

Confirm the termination by reading the messages that display at the bottom of the panel.

Actions GoTo View Options Help ------------------------------------------------------------01/02/97 12:00:00 Region Operations IMS: I51A + VIEW=ALL L=Lock N=Unlock O=Stop R=Start ________ + Lines 1 to 7 of 7+----------------------------------------------------------------------+| Region | Type | Status|Occupancy| Classes |Locks|Transaction||------------+--------+--------+---------+-----------+-----|-----------+| _ BMPID005 | BMP | Wt-CPU | --n/a-- | --n/a-- | 0 | --none-- || _ BMPUT001 | BMP | Ex-Drgn| --n/a-- | --n/a-- | 0 | --none-- || _ IFP31001 | FP IFP | Idle | IFP | --n/a-- | 0 | --none-- || _ IFP31002 | FP IFP | Wt-CPU| IFP | --n/a-- | 0 | --none-- || _ IMSMP31A | Message| Idle | 28% | 1, 2, 5, 3| 0 | --none-- || _ IMSMP31C | Message| Wt-CPU| 43% | 1 | 0 | --none-- || _ IMSMP31X | Message| Wt-CPU| 17% | 1 | 0 | --none-- |+----------------------------------------------------------+-----------+ F1=Help F2=Keys F3=Exit F4=Prompt F5=Refresh F6=Console **=Bkwd **=Fwd F10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW

Taking Action


Resolving a Message Queue I/O Bottleneck 221

Resolving a Message QueueI/O Bottleneck

Chapter overviewThis chapter explains how to use the Message Queue to investigate response time problems.

Chapter contentsScenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222Showing Details for Message Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223Showing Details for Terminals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224Starting the Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

16

Scenario


Scenario

IntroductionSuppose you are monitoring your system from the System Overview panel and you notice that several response time groups have status indicators that are red. You also notice that the MessageQ status indicator is red. You decide to investigate the Message Queue to see if that can solve your response time problems.


Showing Details for Message Queue

Showing Details for Message Queue

IntroductionTo find out more about the message queue, you request the Show details action for the Message Queue by positioning the cursor next to MessageQ and pressing Enter. OMEGAMON II displays the Message Queue Buffers and Datasets panel. You notice that the I/O rate on the message queue datasets is very high. Press F15 to return to the System Overview panel.

FIGURE 86. Message Queue Buffers and Datasets Panel

GoTo Options Help ------------------------------------------------------------01/02/97 12:00:00 Message Queue Buffers and Datasets IMS I51A + +-----------------------------------------------------------------------------+| Message Queue | Total | Short | Long | QBLKS | Free ||---------------------+----------+----------+----------+----------+-----------|| No. of Buffers | 209 | 40 | 125 | 44 | || Percentage | | 19.1% | 59.8% | 21.1% | |+-----------------------------------------------------------------------------++-----------------------------------------------------------------------------+| Dataset | % Used | Shutdown | I/O Rate ||-----------------+----------------------+-------------+----------------------|| Short | .31%, 839 of 263800| 98.32% | 17.94 per second || Long | 7.45%, 1416 of 19000| 84.12% | 23.39 per second || QBLKS | 5.36%, 1418 of 26400| 99.13% | 5.96 per second |+-----------------------------------------------------------------------------+ F1=Help F2=Keys F3=Exit F5=Refresh F6=Console F10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW

Showing Details for Terminals



IntroductionWhen you return to the System Overview panel, you notice that the Terminals status indicator is also red. You want to find out more about the terminals. You decide to display the LTERM Operations panel. With the LTERM Operations panel, you can find out more about the status of the Terminals and take some action if it is necessary.

To display the LTERM Operations panel, move the cursor next to Network in the Operator Assist section of the System Overview and press Enter. OMEGAMON II displays the VTAM Nodes panel.

FIGURE 87. VTAM Nodes Panel

Select the <LTERM OP> pushbutton, to display the Signed On LTERM Operations panel (Figure 88 on page 225).

Actions GoTo View Options Help ------------------------------------------------------------01/02/97 12:00:00 VTAM Nodes IMS I51A + VIEW: A=Activate E=Restart N=Idle Node O=Stop P=Open Dest R=Start T=Close Des ________ + Lines 1 to 11 OF 979+-----------------------------------------------------------------------------+| Node | Status | Type | Q. length|0..........14........29||----------------+--------------+----------+----------+-----------------------|| RTRM23 | ID | SLU2 | 0 | || RTRM21 | ID | SLU2 | 0 | || L610A88 | ID | SLU2 | 44 |--------------------->>|| SLAVE | ID | SLU2 | 0 | || L0046740 | ID | SLU2 | 0 | || L0046741 | ID | SLU2 | 0 | || L0046742 | ID | SLU2 | 0 | || L0046743 | ID | SLU2 | 0 | || L0047271 | ID | SLU2 | 0 | || L0047272 | ID | SLU2 | 0 | || L00A01 | ID | SLU2 | 0 | |+-----------------------------------------------------------------------------+ (VTAM Nodes OP) <LTERM OP> <Lines OP> <PTERM OP> F1=Help F2=Keys F3=Exit F5=Refresh F6=Console **=Bkwd **=Fwd F10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW



FIGURE 88. Signed On LTERM Operations Panel

You notice on this panel, LTERM AALVM200 has an exceptionally high output queue length. You also notice that the status of that LTERM is Stopped. You suspect from this that the output message queue buffers may be overutilized because the terminal is stopped.

Actions GoTo View Options Help ------------------------------------------------------------01/02/97 12:00:00 Signed On LTERM Operations IMS I51A + VIEW: Signed On O=Stop P=PStop R=Start U=Purge ________ + Lines 1 to 15 of 15+------------------------------------------------------------------------------+| LTERM | Status | Node |QLength |0.............165..........330||-------------+-----------+----------+----------+------------------------------|| _ AALVM100 | Started | AALVM100 | 0 | || _ AALVM200 | Stopped | AALVM200 | 89 |----------------->> || _ AALVM201 | Stopped | AALVM201 | 0 | || _ AALVM202 | Started | AALVM202 | 0 | || _ AALVM203 | Started | AALVM203 | 0 | || _ AALVM204 | Started | AALVM204 | 0 | || _ AALVM205 | Started | AALVM205 | 1 |> || _ AALVM206 | Started | AALVM206 | 0 | || _ AALVM207 | Started | AALVM207 | 0 | || _ AALVM208 | Started | AALVM208 | 0 | || _ AALVM209 | Started | AALVM209 | 0 | || _ AALVM210 | Started | AALVM210 | 0 | || _ AALVM211 | Started | AALVM211 | 3 |> || _ AALVM212 | Started | AALVM212 | 0 | || _ AALVM213 | Started | AALVM213 | 12 |--> |+------------------------------------------------------------------------------+ <VTAM Nodes OP> (LTERM OP) <Lines OP> <PTERM OP> F1=Help F2=Keys F3=Exit F5=Refresh F6=Console **=Bkwd F8=Fwd F10=Action Bar F15=System Overview PA1=Switch PA2=OMEGAVIEW

Starting the Terminal


Starting the Terminal

IntroductionPosition the cursor next to LTERM AALVM200, type an R, and press Enter. OMEGAMON II issues the command to start the LTERM.

227

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 IMS exceptions, and a table listing some Fast Path mnemonics.

Operating OMEGAMON II from the Menu/Command Interface 229

Operating OMEGAMON IIfrom the Menu/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 . . . . . . . . . . . . . . 230Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Specifying a User Profile in ISPF, VTAM, or TSO Mode . . . . . . . . . . . . . 233Working with Exceptions in VTAM, ISPF, TSO, or Dedicated Mode . . . . 234

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, theOMEGAMON 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 toOMEGAMON II. In TSO mode the OMEGAMON II screen does not refresh automatically. It refreshes when you press Enter or any program function key.

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.

Modes of Operation


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 appears on the INFO-line next to the product version number. This example shows that a profile named SW is in use.

________________ KOIMENU VTM OI-II SW I51A 01/02/97 9:20:19 OB

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 89. Systemwide Exceptions Display

Responding to exception messagesAn exception trips when the performance value it monitors exceeds the threshold you set 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.

________________ KOISYS VTM IO-II /C I61D 08/18/99 12:00:00 B> 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+ ICHI Control Region: I/O Rate = 4.44/second (High)===============================================================================



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. 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 (response time, limit situations)

so that an exception message is generated 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 IMS 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 appears whenever an exception condition occurs. When no exception conditions exist in your system, OMEGAMON II displays the message

No exceptions tripped this cycle

3. 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 90. 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 125 for more information on using command mode.

________________ KOICLER VTM IO-II /C I61D 08/18/99 12:00:00 B> 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 *** <== ‘ ===============================================================================



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 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 91 on page 237 a partial display of the History of All Tripped Exceptions panel.

FIGURE 91. 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 are displayed in alphabetical order.

________________ KOIHIST VTM IO-II /C I61D 08/18/99 12:00:00 B> 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 he> 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+ State=On+ Last 08/16 11:50:15 4 4



If you use the XSUM and XTRP commands to display this information, the following keywords are available:

For more information about XSUM or XTRP, or about TSF, see the OMEGAMON II for IMS 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 detail on individual command syntax and additional customization options, see the OMEGAMON II for IMS Realtime Commands Reference Manual.

You can customize exception analysis in the following ways:

n Group definition

n Exception group switches

n Exception control

n Invocation order

You can then save the settings you define in a user profile. Refer to “Creating and maintaining profiles” on page 95.

New group settings are not saved 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 147 or refer to the OMEGAMON II for IMS Realtime Commands Reference Manual.

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.

LIST=I Enter I to request that the exceptions are listed 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.



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.

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 IMS 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 IMS 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). Any



new definitions you create can be saved in a user profile for future sessions (see “Creating and maintaining profiles” on page 95).

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 the warnings for this exception to be enclosed 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 IO-II /C I61D 08/18/99 12:00:00 B> 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:

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



The following example shows a TERSE keyword display:

Reordering the display

You can display a list of the exceptions and the order in whichOMEGAMON 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:

________________ KOIODFBVTM IO-II /C I61D 08/18/99 12:00:00 B > 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. > ACEX Pool extension size > n. ================================================================================

XACB TERSE : DNRS Threshold=N/A Display=Red State=ON Bell=ON : TNRS Threshold=N/A Display=Blue State=TEST Bell=OFF : WSHI Threshold=2500 Display=Pink State=ON Bell=OFF : WSLO Threshold=300 Display=Blue State=NDSP Bell=OFF



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 atOMEGAMON II session initialization. For more information, see “Screen Spaces” on page 147, the OPTN command in the OMEGAMON II for IMS Realtime Commands Reference Manual, and the Configuration and Customization Guide.

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 Figure 92 on page 244 displays:

________________ KOIMENU VTM IO-II /C I61D 08/18/99 12:00:00 B 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 . . . . . . . . . . . . . . . . . .



FIGURE 92. Display of Pre-Defined IMS/MTO Messages

4. Follow the instructions on the panel to define or delete messages.

Defining message exception display 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

________________ KZIMSGD VTM IO-II /C I61D 08/18/99 12:00:00 B> Help PF1 Back PF3 Up PF7 Down PF8 Save Profile PF22>===============================================================================> 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. >MSGD ADD DFSnnn > To add an MVS message generated by an IMS region, remove the > before MSGD> below and enter the specific message number. >MSGD ADD ICEnnn > To delete an existing IMS/MTO message, remove the > before MSGD below, and> enter the specific DFS or MVS message number. >MSGD DELETE DFSnnn===============================================================================



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.

5. 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 95 for more information.

________________ KOIMENU VTM IO-II /C I61D 08/18/99 12:00:00 B 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: Group=IM Display=DEFAULT Log=OFF

Exceptions Table 247

Exceptions Table

Appendix overviewThis appendix lists the OMEGAMON II for IMS exceptions.

Appendix contentsOMEGAMON II for IMS Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

B

OMEGAMON II for IMS Exceptions



IntroductionThe following table lists all of the OMEGAMON II for IMS 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 5. OMEGAMON II for IMS 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

ACIO Displays when the communications I/O pool (CIOP) utilization is > nn%

Pools (CIO) Pools

ACIS Displays when IMS is in selective dispatching for the communications I/O pool (CIOP).


ACIW Displays when the pool extension IWAITs is > nn for the communications I/O pool (CIOP).

Pools (CIO) Pools

ACIX Displays when the pool extension size is > nn for the communications I/O pool (CIOP).

Pools (CIO) Pools

ACWA Displays when the communications work area pool (CWAP) utilization is > nn%.

Pools (CWA) Pools



ACWS Displays when IMS is in selective dispatching for the communications work area pool (CWAP).


ACWW Displays when the pool extension IWAITs is > nn for the communications work area pool (CWAP).

Pools (CWA) Pools

ACWX Displays when the pool extension size is > nn for the communications work area pool (CWAP).

Pools (CWA) 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

ADMB 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


Exception ID


Status Light



AFRE Displays when the fetch request element (FRE) pool utilization is > nn%.

Note: There is really no such thing as an FRE pool, but for convenience you can think of FRE that way.

Use the IMS FRE= parameter to specify the number of fixed FREs to allocate when IMS builds the message format block pool (MFP). If all of the fixed FREs are ever in use at the same time, the AFRE exception shows the pool as 100% utilized.

For more FREs, IMS must carve space out of the MFP buffer pool. These FREs are dynamic and are available as long as IMS is using them.

Note: The FREP command displays the number of dynamic FREs that IMS currently has allocated.

Pools (Other) Pools

AHIO Displays when the high I/O pool (HIOP) utilization is > nn%.

Pools (Other) Pools

ALMD Displays when the long message dataset utilization is > nn%.

Pools (Dataset Utilization)

MessageQ

AMFS Displays when the message format services (MFS) pool utilization is > nn%.

Pools (Other) Pools

AMSG Displays when the message queue buffer pool utilization is > nn%.

Displays when the message queue buffer pool utilization is > nn%.

MessageQ

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

AQBD Displays when the queue blocks dataset utilization is > nn%.


MessageQ


Exception ID


Status Light



ARAU Displays when the receive any pool utilization is > nn%.

Pools (CIO) Pools

ARCB Displays when the receives any buffers in use is > nn.

Pools (CIO) 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

ASMD Displays when the short message dataset utilization is > nn%.


MessageQ

AWKP Displays if the IMS general work pool utilization is > nn%.

Pools (Other) Pools

BLGH Displays when the balancing group input is > nn.

Fast Path (High)

Fast Path

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) CPU

CBLO Displays when BMP region CPU utilization is < nn%.

CPU (Low) CPU

CCHI Displays when control region CPU utilization is > nn%.

CPU (High) CPU

CCLO Displays when control region CPU utilization is < nn%.

CPU (Low) CPU

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


Exception ID


Status Light



CLHI Displays when IRLM region CPU utilization is > nn%.

CPU (High) CPU

CLLO Displays when IRLM region CPU utilization is < nn%.

CPU (Low) CPU

CMHI Displays when MPP region CPU utilization is > nn%.

CPU utilization is the percentage of the total CPU that the MPP region has used over the last OMEGAMON cycle. CPU itilization ranges from 0% to 100% for all online processors in the complex.

The default OMEGAMONcycle is five seconds.

CPU (High) CPU

CMLO Displays when MPP region CPU utilization is < nn%.

CPU utilization is the percentage of the total CPU that the MPP region has used over the last OMEGAMON cycle. CPU itilization ranges from 0% to 100% for all online processors in the complex.

The default OMEGAMON cycle is five seconds.

CPU (Low) CPU

COMW Displays when IMS has nn ITASKS waiting for pool space and IMS is in selective processing.

Pools (Other) IMS Status

CPUA Displays if the IMS CPU utilization is >= nn %.

CPU (Low) CPU

CRHI Displays if the DBRC region CPU utilization is > nn%.

CPU (High) CPU

CRLO Displays if the DBRC region CPU utilization is < nn%.

CPU (Low) CPU

CSHI Displays if the DLS region CPU utilization is > nn%.

CPU (High) CPU

CSLO Displays if the DLS region CPU utilization is < nn%.

CPU (Low) CPU

CSVC Displays when IMS control task is waiting in SVC code.

IMS Status (Alerts)

IMS Status


Exception ID


Status Light



CUOW Displays when one Fast Path region is in unit-of-work contention with another Fast Path region.

Fast Path (Alerts)

Fast Path

CVAH Displays when LU 6.2 total active asynchronous conversations equal or exceed thresholds.

IMS Status (Other)

IMS Status

CVHI Displays when LU 6.2 total active conversations equal or exceed thresholds.

IMS Status (Other)

IMS Status

CVSH Displays when LU 6.2 total active synchronous conversations equal or exceed thresholds.

IMS Status (Other)

IMS Status

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

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


Exception ID


Status Light



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 dataspace. Fast Path (Alerts)

Fast Path

DSTR Displays when dispatcher trace is on. Traces (Alerts) Traces

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

ESTH Displays when the number of active threads for an external DB2® subsystem is >nn.

External Subsystem (High)

DB2

FCIO Displays when the communications I/O pool’s (CIOP) largest free block is < nn bytes.

Fragmentation (Low)

Pools

FCWA Displays when the communications work area pool’s (CWAP) largest free block is < nn bytes.

Fragmentation (Low)

Pools

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


Exception ID


Status Light



FHIO Displays when the high I/O pool’s (HIOP) largest free block is < nn bytes.

Fragmentation (Low)

Pools

FMFS Displays when the message format services (MFS) pool’s largest free block is < nn bytes.

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

ICFX Displays if the I/CF is not connected to the monitored IMS. The exception only trips when you have defined an I/CF console is an I/CF Master Console for the monitored IMS ID.

IMS Status (Alerts)

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


Regions

ILHI Displays if the IRLM region I/O rate is > nn EXCPs per second over the lastOMEGAMON cycle.


Regions

ILLO Displays if the IRLM region I/O rate is < nn EXCPs per second over the last OMEGAMON cycle.


Regions


Exception ID


Status Light



IMHI Displays when the message processing region I/O rate is > nn EXCPs per second, during the last OMEGAMON cycle.



Regions

IMLO Displays when the message processing region I/O rate is < nn EXCPs per second, during the last OMEGAMON cycle.

The default OMEGAMONcycle is five seconds.


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)

Virt. Stor.

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, 5.2, and OS/390.

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


Exception ID


Status Light



IRRC Displays when the real contention rate is > 70 per second.


Resources (High)

IMS Status

IRRU Displays when IRLM RLE usage is > 70%.


Resources (High)

IMS Status

IRTP Displays when the IRLM pass-the-buck (PTB) trace is active.


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

ITWH Displays when the ITASKS waiting for dynamic SAPs are > nn.

Pools (Other) IMS Status

LALO Displays if the LSQA storage assurance is < nn K.

Virtual Storage (Low)

Virt. Stor.

LDMB Displays if the DMB pool blocks loaded <= 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

LMGH Displays when the long message dataset I/O rate is > nn per second.


I/O

LMLO Displays if the LSQA maximum free block size is < nn K.


Virt. Stor.

LPEX Displays if the the number of writes to WADS is > nn per second.

Logging (WADS High)

Logging

LPOQ Displays when all logical terminals, except video-type, have an output queue length > nn.

LTERMS Terminals


Exception ID


Status Light



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 <= nn%.

Pools (PSB) Pools

LSLO Displays if the LSQA total free storage is < nn K.


Virt. Stor.

LTOQ Displays when a video-type, logical terminal has an output queue length > nn.

LTERMS Terminals

LTWA Displays if the log tape write-ahead is not active.

Resources (Alerts)

Logging

LVOQ Displays when a video-type, virtual terminal has an output queue length > nn.

LTERMS Terminals

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 IMS Realtime Commands Reference Manual.

n/a n/a

MDHI Displays when the message dequeue rate is > nn per second.

Message Processing (High)

Regions

MDLO Displays when the message dequeue rate is < nn per second.

Message Processing (Low)

Regions

MFSH Displays when the MFS dataset I/O rate is > nn per second.


I/O


Exception ID


Status Light



MIRT Displays the number of message inserts that the specified region did to the message queue.

A sample MIRT message is MSG INSERT COUNT FOR REGION xxxxxxxx = nn, where xxxxxxxx is the transaction and nn is the count.

The count field displays the number of get calls the region did to the message queue. If the count field remains constant and the nn value increases, this may indicate that the application program is in a loop.


Regions

MPCH Displays when the MPP region database calls are > nn.


Regions

MSDI Displays when an MSDB has an invalid packed field.

IMS only resets the packed field when IMS restarts.

Fast Path (Alerts)

Fast Path

MSDO Displays when an MSDB has an overflowing field.

Note: IMS resets the overflowing field at the next synchronization point.

Fast Path (Alerts)

Fast Path

MSGE Displays when the ICNS command has not been issued.

IMS Status (Alerts)

IMS Status

NACB Displays when VTAM ACB is not open.

IMS Status (Alerts)

IMS Status

NDIR Displays when the systems programmer has not defined the $$IMSDIR table.

The NDIR analysis detects an undefined $$IMSDIR table and alerts you to the potential cause of any MFS overhead your system may be incurring.

Resources (Alerts)

I/O


Exception ID


Status Light



NDRE Displays when the $$IMSDIR table entry is not in the MFS format library.

OMEGAMON did not find a $$IMSDIR table entry in the MFS format library; you are using critical storage incorrectly.

Resources (Alerts)

I/O

NILU Displays when the IMSLU connection with APPC/MVS is not enabled. This exception trips only on START and FAILED.

IMS Status (Alerts)

IMS Status

NLOQ Displays when there are unavailable video-type, logical terminals with an output queue length > nn.

LTERMS Terminals

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

NPOQ Displays when there are unavailable non-video-type, logical terminals with an output queue length > nn.

LTERMS Terminals

NQRE Displays when a RECON dataset is enqueued by another job.

Resources (Alerts)

IMS Status

NSDC Displays when IMS does not perform START DC.

IMS Status (Alerts)

IMS Status

NTIQ Displays non-competing transactions with an input queue length > nn.

A non-competing transaction is a transaction that is unable to run for some reason other than the competition for IMS resources. Examples are a transaction where you stopped the transaction code or a transaction that requires the use of a stopped database.

Transactions Trans.


Exception ID


Status Light



NVAP Displays when there is no VTAM authorized path.

Running an IMS VTAM network without the VTAM authorized path option can have significant performance penalties.

IMS Status IMS Status

NVOQ Displays when there is an unavailable virtual video-type terminal with an output queue length > nn.

LTERMS Terminals

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

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.



Exception ID


Status Light



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)

Virt. Stor.

PIBP Displays if the BMP private area page-in rate is > nn per second during the last OMEGAMON cycle.


Virt. Stor.

PICC Displays if the common area page-in rate for the control region is > nn per second during the last OMEGAMON cycle.


Virt. Stor.

PICP Displays if the private area page-in rate for the control region is >nn per second during the last OMEGAMON cycle.


Virt. Stor.

PIDC Displays if the common area page-in rate for DBRC is > nn per second during the last OMEGAMON cycle.


Virt. Stor.

PIDP Displays if the private area page-in rate for DBRC is > nn per second during the last OMEGAMON cycle.


Virt. Stor.

PILC Displays if the common area page-in rate for IRLM is > nn per second during the last OMEGAMON cycle.


Virt. Stor.


Exception ID


Status Light



PILP Displays if the private area page-in rate for IRLM is > nn per second during the last OMEGAMON cycle.


Virt. Stor.

PIMC Displays when the message processing region common area page-in rate is > n per second during the last OMEGAMON cycle.


Virtual Storage (Page-In Rate)

Virt. Stor.

PIQH Displays if the number of PI enqueue locks held by the indicated thread is > nn.

Locks Regions

PIRP Displays when the message processing region private area page-in rate is > n per second during the last OMEGAMON cycle.



Virt. Stor.

PISC Displays if the common area page-in rate for the DLS region is > nn per second during the last OMEGAMON cycle.


Virt. Stor.

PISP Displays if the private area page-in rate for the DLS region is > nn per second during the last OMEGAMON cycle.


Virt. Stor.

PITR Displays when the program isolation trace facility is on.


PROQ Displays when the printer is unable to receive output.

Resources (Alerts)

Terminals

PSVC Displays when IMS physical logger task waiting in SVC code.

Resources (Alerts)

IMS Status

QBKH Displays when the queue blocks dataset I/O rate is > n per second.


I/O

RDSH Displays if the restart dataset I/O rate is > nn per second.


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


Exception ID


Status Light



RGSI Displays when the region sync point interval is > nn minutes.

The RGSI alerts the customer when current time minus time of the latest system checkpoint is greater than nn minutes and the region has insert and/or update activity.

Regions Regions

ROHI Displays when the message region occupancy is > nn%.

OMEGAMON calculates the occupancy factor by sampling each message region once every OMEGAMON cycle, to see if OMEGAMON has scheduled a transaction. Since this is a statistical method, the data is not significant until there is a relativley large number of samples. OMEGAMON bypasses this exception until it takes at least 120 samples.

Note: If OMEGAMON’s interval setting is five seconds, there is a ten minute delay for OMEGAMON to calculate occupancy.

OMEGAMON does not automatically treat WFI region occupancy as 100%, and only considers a WFI region occupied if the region is not in the waiting for input state.

For the occupany factor calculation, OMEGAMON only maintains samples less than 60 minutes old. Therefore, the region occupancy is an average over the preceding hour. As message regions stop and restart, OMEGAMON begins the calculation again.

A sample exception message is ROHI MPP ‘MESSAGE’: Region Occupancy = 93.84% (High).


Regions


Exception ID


Status Light



ROLO Displays when the message region occupancy is < nn%.

OMEGAMON calculates the occupancy factor by sampling each message region once every OMEGAMON cycle, to see if OMEGAMON has scheduled a transaction. Since this is a statistical method, the data is not significant until there is a relativley large number of samples. OMEGAMON bypasses this exception until it takes at least 120 samples.

Note: If OMEGAMON’s interval setting is five seconds, there is a ten minute delay for OMEGAMON to calculate occupancy.

OMEGAMON does not automatically treat WFI region occupancy as 100%, and only considers a WFI region occupied if the region is not in the waiting for input state.

For the occupany factor calculation, OMEGAMON only maintains samples less than 60 minutes old. Therefore, the region occupancy is an average over the preceding hour. As message regions stop and restart, OMEGAMON begins the calculation again.

A sample exception message is ROHI MPP ‘MESSAGE’: Region Occupancy = 6.72% (Low).

Message Processing (Low)

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

SAPW Displays when IMS puts an ITASK into the IWAIT state because no dynamic SAPs (save area prefix sets) are available.

The SAPW exception message may display with the SDSP (selective dispatching) message, since running out of dynamic SAPs is one reason why IMS actives selective dispatching.

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

SDSP Displays when selective dispatching is active.

IMS invokes selective dispatching, when there is a shortage of storage for some of the IMS internal resources. IMS must restrict the scheduling of new work until IMS relieves the shortage.

IMS Status (Alerts)

IMS Status

SMGH Displays when the short message dataset I/O rate is > nn per second.


I/O’

SPAH Displays when the SPA dataset I/O rate is > nn per second.


I/O


Exception ID


Status Light



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 IMS Realtime Commands Reference Manual.

n/a n/a

TCOI Displays when the Time Controlled Operations (TCO) is inactive.

IMS Status (Alerts)

IMS Status

TCOT Displays if the time controlled operations (TCO) trace is active.


THHI Displays if the number of active threads is > nn.

Threads (High) Regions

THHP Displays if the number of active threads is > nn% of all available threads.

Threads (High) Regions

THLO Displays if the number of active threads is < nn.

Threads (Low) Regions

THLP Displays if the number of active threads is < nn% of all available threads.

Threads (Low) Regions

TMFH Displays when the test MFS dataset I/O rate is > nn per second.

I/I Rates (Datasets)

I/O

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


Exception ID


Status Light



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 IMS Realtime Commands Reference Manual.

n/a n/a

TRDY Displays if a tape device drops ready. Resources (Alerts)

I/O

TXIQ Displays when there are competing transactions with an input queue length > nn.

he TXIQ analysis examines all competing transactions to identify those with an input message queue length <= the threshold n, which the user sets.

Note: A transaction might queue if a message region of the appropriate class is not currently available to run the transaction.

A non-competing transaction is a transaction that is unable to run for some reason other than the competition for IMS resources. Examples are a transaction where you stopped the transaction code or a transaction that requires the use of a stopped database.

Transactions Trans.

VCAS Displays when database VSAM control area splits are > 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 Bufr. Pools

VMEX Displays if the number of extents for the VSAM dataset is increasing.

VSAM (Alerts) Databases


Exception ID


Status Light



VMLO Displays when IMSCTL maximum private free block size is < nn K.


Virt. Stor.

VROQ Displays when logical terminal is unable to receive output.

IMS Status (Alerts)

IMS Status

VSLO Displays when IMSCTL total private free block size is < K.


Virt. Stor.

VTLO Displays when IMSCTL top free block size is < nn K.


Virt. Stor.

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)

Virt. Stor.

WBLO Displays when BMP working set size is < nn K.

Working Sets (Low)

Virt. Stor.

WCHI Displays when the control region working set size is > nn K.

Working Sets (High)

Virt. Stor.

WCLO Displays when the control region working set size is < nn K.

Working Sets (Low)

Virt. Stor.

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)

Virt. Stor.

WLLO Displays when IRLM working set size is < nn K.

Working Sets (Low)

Virt. Stor.


Exception ID


Status Light



WMHI Displays when the message processing region working set size is > nn K.

The working set size is the number of real pages the region currently has in memory. Under MVS/ESA, the working set size includes expanded storage.

Working Sets (High)

Virt. Stor.

WMLO Displays when the message processing region working set size is < nn K.

The working set size is the number of real pages the region currently has in memory. Under MVS/ESA, the working set size includes expanded storage.

Working Sets (Low)

Virt. Stor.

WRHI Displays when DBRC working set size is > nn K.

Working Sets (High)

Virt. Stor.

WRLO Displays when DBRC working set size is < nn K.

Working Sets (Low)

Virt. Stor.

WSHI Displays when DLS working set size is > nn K.

Working Sets (High)

Virt. Stor.

WSLO Displays when DLS working set size is < nn K.

Working Sets (Low)

Virt. Stor.

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


Exception ID


Status Light



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 273

Fast Paths

Appendix overviewThis appendix list the fast paths you can use to move directly to a panel.

Appendix contentsUsing Fast Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

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.

5. Enter the mnemonic string in the home entry field at the upper left of the panel and press Enter.You will see the panel you selected..

Mnemonic Go To

GB/G1 Buffer Pools

GD/G2 Databases

GO/G3 I/O

GM/G4 Message Queue

GS/G5 System Status

GC/G6 Zoom to underlyingOMEGAMON session

GI/G7 Index

Move to GOTO on the Action Bar and select 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

Fast Paths 275

Using Fast Paths

GI( Logging Buffers and Status

GI/ Logging Details

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

GIZ Transactions

GIM Terminals

GIQ Message Queue

GI@ Pools Description

GIE Conversations OP

GI2 Lines OP

GI4 LTERMS OP

GI6 PTERMS OP

GI8 Transactions OP

GI9 VTAM Nodes OP

GI) Fast Path Balancing Groups

Note: If RTA is active, then the following mnemonics are active:

GIA Response Time All

GI= Bottlenecks

Mnemonic Go To

Using Fast Paths


.

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

277

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278– 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282– Assigned Support Center Representative (ASCR)

– Maintenance Assessment Services (MAS)

– Multi-Services Manager (MSM)

Customer Support Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283– 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.

279


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 resolve your issue. All escalations or complaints received about support issues are logged and tracked to ensure responsiveness and closure.

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.

281


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


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

283

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 285

Symbols# in column 1 142$$IMSDIR table 259, 260&ZFRSTSS 159&ZXccccV 159&ZXcccV 159&ZXcccW 159+ at end of line 129+at end of line 142.CN immediate 163.D

argument 158immediate 140

.DCL immediate 139/DCL INFO-line 139

.DD immediateblock deletion, .DD 140

.DEF immediateHO 150OFF 150ON 150

.FGOimmediate 155, 156routine testing 156

.H argument 158

.I Immediate 140

.ILC immediate 136, 137

.LOG immediateON 144OUT 144POP 156PUSH 156

.LOGPOP 156

.LOGPUSH 156

.M argument 158

.MIN immediate 137

.MJC immediate 137

.MJI immediate 137

.MMA immediate 137

.PFK immediate 142

.PRT immediate 145

.R argument 158

.RC immediaterepeat lines 143

.S argument 158

.SGO immediate 155, 160

.VAR immediate 150, 159/ in column 1 134/BOTTOM INFO-line 138/D INFO-line 138/DCL INFO-line 139/DEF INFO-line

HOLD 150OFF 150ON 150

/DOWN INFO-line 138/LOG INFO-line

ON 144OUT 144

/P 145/PRINT INFO-line 145/REP INFO-line 149/SAVE INFO-line 149, 150/TOP INFO-line 138/U INFO-line 138/UP INFO-line 138/ZOOM INFO-line 161< in column 1> 142> in column 1 129, 149? in column 1 134’ in column 1 134

AA on INFO-line 129ABUF exception 248ACBH exception 248ACEA exception 248ACES exception 248ACEW exception 248ACEX exception 248ACIS exception 248ACIW exception 248ACIX exception 248action bar 38action bar function key area 39action bar keyword functions 43action bar panel body 38action bar pop-up windows 39action bar pull-down menus 39, 43action bar pushbutton area 39action bar, using 43action codes

Index


advanced functions action codes 51Actions pull-down 43actions pull-down menu 39ACWA exception 248ACWS exception 249ACWW exception 249ACWX exception 249ADBW exception 249ADHI exception 249ADLO exception 249ADMB exception 249Adobe portable document format 15ADSU exception 249advance functions 51advanced functions short-cut 51AFRE exception 250AHIO exception 250alerts, customizing 90all clear message, customizing 236ALMD exception 250AMFS exception 250AMSG exception 250APIE exception 250, 254Application Trace Facility (ATF) 76, 77APSB exception 250APSW exception 250AQBD exception 250ARAU exception 251ARCB exception 251argument 133

command 133extended 133

ASAP exception 251ASCR

assigned support center representative 282ASF 129ASHI exception 251ASLO exception 251ASMD exception 251assigned support center representative

ASCR 282assigning

INFO-line commands to 140screen spaces to 140

assigning screen spaces todefinitions of 141

attributes for exception messages 240automated screen facility (ASF) 129automatic screen facility (ASF) 155, 159, 235, 239

activating 99on INFO-line 129

automatic takeoverin progress 271

status 270automatic update 231

cycles 100suspending 150

availability manager not active 270AWKP exception 251

BB on INFO-line 129balancing group 251batch message processing

exceptions 262, 269beep, controlling 84bell

activating 99setting interval 99status on INFO-line 129

BLGH exception 251blue status indicator 69, 88BMP

exception 251, 255region I/O rate 255swapped out 254

bottleneck analysis component 30box XACB parameter 240BQHI exception 251BQLO exception 251buffer pool usage, HSSP

HSBH exception 255HSBL exception 255

CCANSOI 152CBHI exception 251CBLO exception 251CCHI exception 251CCLO exception 251characters for status indicators 69check maintenance level 50CILO exception 251CIO exception 248CIs number of free 266clear screen command (.. ) 138CLHO 252CLLO exception 252CMHI exception 252CMLO exception 252colon

in column 1 130color

of status indicators 69on panels 40

Index 287

options for exception message 240Color Settings menu 100command 99, 131, 132, 142

argument 133clear screen 138entry 44format 132help 133, 134, 135, 136, 137immediate, list 137INFO-line 129, 137input, multi-line 130limiting major command listings 137logging 144major, list 137minor, list

.EXM immediate 137mode 125name 133options 142parameters, entering 133

command interface 24accessing 126definition of 140panel format 128processing order 128screen control 138

commandsentering 125

commentcharacter 129character (>) 149deleting 139entering 129line 129, 149

commmand/menu interface operations 229common area page-in rate for

DBRC region 262DLS region 263IRLM region 262messages processing region 263

communicationsI/O pool (CIOP) 254work area pool (CWAP) 254

communications external subsystem poolexceptions 248

communications I/O pool (CIOP)pool extension IWAITs 248pool extension size 248selective dispatching 248utilization 248

communications work area pool (CWAP)pool extension IWAITs 249pool extension size 249

selective dispatching 249utilization 248

components 30components of OMEGAMON II

bottleneck analysis 31historical component 31realtime performance component

(OMEGAMON) 30response time analysis (RTA) 30

COMW exception 252conditional screen space 155configuring profiles 98console

control 163panel use 81secondary 163

context sensitivepull-down menu Help 49

continuation character 134142

# 142+ 142+ plus sign 129

control blue status bars displayed 88control green status bar character 89control green status bars displayed 88control interval refresh period 88control red status bar character 89control region 269

CPU utilization 251I/O rate 255working set size 269

control response wait period 88control yellow status bar character 89controls 47, 88count of items selected by a major command 142CPSER 159CPU 213

serial number 159CPUA exception 252creating profile 95CRHI exception 252CRLO exception 252CSHI exception 252CSLO exception 252CSR up/down scrolling 138CSVC exception 252CUA interface 26

options 84CUA interface,accessing 26cumulative= XACB parameter 241CUOW exception 253


CURS on INFO-line 149cursor

movement 40pointing feature 161saving position in screen spaces 149

customer supportbase maintenance plan 278contact information 283enhanced support services 282eSupport 279severity levels 279telephone support 278

customizingcontrols 88preferences 84

customizing exceptions 90customizing messages 236CVAH exception 253CVHI exception 253CVSH 253cycle XACB parameter 240

DDASD

device dropped ready 254data

entry database area unavailable 249database 254, 268

area I/O 251area splits 268DASD I/O 249dynamic backout error alert 253I/O 251I/O error exception 253management block 249management block (DMB) 249OSAM 262VSAM 269VSAM control 268work pool 249writecheck on 269

datasetrestart 263

dataset I/O ratelong message 257MFS 258queue blocks 263short message 266SPA 266test MFS 267

dataspaceDASD I/O 253I/O 251, 254

datedisplaying 84format 85, 99on INFO-line 129

datespacearea I/O 251

DBRC 252, 256, 262working set size 270

DBWE exception 253DCMN exception 253DDHI exception 253DDLO exception 253DEDB area

independent overflow exception 251dedicated mode 231defining messages 243definition mode 149, 150definitions of PF keys 121, 140delay processing 143delayed screen space fetching 156deleting

block 140comment lines 139lines 140menu/command component of user profile 97messages 243screen spaces 154

DELT immediate 154delta argument 158details, showing 39device

I/O error recovery 256name table entries 100number 160

difference argument 158DIR 159direct transfer 65director in cross system mode 159DISP exception 253dispatcher trace

status 254dispatching

priority 253display

continuation lines 142printing 144symbols 129XACB parameter 240

DL/Idetails 217no parallel 260trace table status 253

DLS 257, 263

Index 289

working set size 270DLTR exception 253DMB

pool blocks loaded 257DMB pool, fragmented 253DMBE exception 253DMER exception 253DMFF exception 253DNRS exception 253DRDY exception 254DSHI exception 254DSKB major 158DSL 252DSLO exception 254DSPI exception 254DSTR exception 254DSWP exception 254dynamic exceptions 258dynamic profile update facility 105dynamic save area prefix sets (SAPS) 266

EEAPC exception 249enqueue pool 251EPILOG

component of OMEGAMON II 30ESNC exception 254ESND exception 254ESTH exception 254eSupport

customer support 279exception 99, 241, 249, 251, 253, 254, 262, 269

abbreviated status display 241ABUF 248ACBH 248ACBLIB 248ACEA 248ACES 248ACEW 248ACEX 248ACIO 248ACIS 248ACIW 248ACIX 248ACWA 248ACWS 249ACWW 249ACWX 249ADBW 249ADHI 249ADLO 249ADMB 249

ADSU 249AEPC 249AFRE 250AHIO 250ALMD 250AMFS 250AMSG 250APIE 250, 254APSB 250APSW 250AQBD 250ARAU 251ARCB 251ASAP 251ASHI 251ASLO 251ASMD 251AWKP 251batch message processing 262, 269BLGH 251BMP 251, 255boxing 240BQHI 251BQLO 251CBHI 251CBLO 251CCHI 251CCLO 251, 252CILO 251CLHO 252CMHI 252CMLO 252color 240communication external subsystem pool 248COMW 252controlling an individual 239CPUA 252CRHI 252CRLO 252CSHI 252CSLO 252CSVC 252CUOW 253CVAH 253CVHI 253CVSH 253DBWE 253DCMN 253DDHI 253DDLO 253defining 239DISP 253


DLTR 253DMBE 253DMER 253DMFF 253DNRS 253DRDY 254DSHI 254DSLO 254DSPI 254DSTR 254DSWP 254ESNC 254ESND 254ESTH 254execution reordering 242FCIO 254FCWA 254FDBW 254FDMB 254FEPC 254FHIO 255FMFS 255forcing display 241FPSB 255FPSW 255FPTR 255frequency for checking 241HSBH 255HSBL 255IBHI 255IBLO 255ICFX 255ICHI 255ICLO 255ILHI 255ILLO 255IMHI 256IMLO 256IMS Status 253INAC 256investigating 235IORC 256IRCS 256IRFC 256IRGC 256IRHI 256IRIN 256IRLO 256IRQH 256IRRC 257IRRU 257IRTP 257

IRTR 257ISHI 257ISLO 257ITWH 257LALO 257LDMB 257limit checking 240limiting list by group 241listing 241LKTR 257LLBR 257LLCH 257LMGH 257LMLO 257logging facility (XLF) 144, 159, 235, 239LPEX 257LPOQ 257LPOR 258LPOW 258LPSB 258LSLO 258LTOQ 258LTWA 258LVOQ 258MDHI 258MDLO 258message 234MFSH 258MIRT 259Mnnn 258MPCH 259MSDI 259MSDO 259MSGE 259NACB 259NDIR 259NDRE 260NILU 260NLOQ 260NOFB 260NOOT 260NPDL 260NPOQ 260NQRE 260NSDC 260NTIQ 260NVAP 261NVOQ 261OBAU 261ODIE 261OHLO 261OLDS 258

Index 291

OLER 261OLNA 261OLST 261ONLC 261ONLO 261ORER 261ORIP 261ORST 261OSBL 261OSDN 262output reordering 242OXHI 262OXLO 262PBTR 262PIBC 262PIBP 262PICC 262PICP 262PIDC 262PIDP 262PILC 262PILP 263PIMC 263PIQH 263PIRP 263PISC 263PISP 263PITR 263private area 262, 263PROQ 263PSB 250PSVC 263QBKH 263RDSH 263RGNW 263RGSH 263RGSI 264ROHI 264ROLO 265RSRV 266SAPW 266SCTR 266SDLO 266SDSP 266SMGH 266SPAH 266stop checking 241TCOI 267TCOT 267terse output 241testing 235THHI 267

THHP 267THLO 267THLP 267threshold 235, 240TMFH 267TMSI 267Tnnn 267TNRS 267TPSB 268TRDY 268tripped 234, 237TXIQ 268variables 159VCAS 268VCIS 268VHLO 268VMEX 268VMLO 269VROQ 269VSLO 269VTLO 269VWRC 269VXHI 269VXLO 269WBHI 269WBLO 269WCHI 269WCLO 269WDNA 269WDNB 269WLHI 269WLLO 269WMHI 270WMLO 270WRHI 270WRLO 270WSHI 270WSLO 270XCNF 270XRAT 270XRAV 270XRIP 270XRIT 270XRNS 270XRPH 270XRSR 271XRTO 271

exception analysis 114, 239customizing 238defining IMS messages for 243groups 236history of tripped exceptions 237


immediate command 239LEXC immediate 242starting 236summary 237systemwide 114, 236XIMS 236

exception group 91exception mappings 69exceptions

batch message processing 262CIs number of free 266FP region contention 253output threads 260region in buffer wait 260region using Fast Path OBA 261systemwide 234

exiting OMEGAMON II 29EXNCYC = XACB parameter 241export profile 105extended

PCB pool 249, 254external

subsystem 254

FFast Path 253, 260, 261, 266

BQHI exception 251BQLO exception 251DEDB area I/O error 253trace on 255

FCIO exception 254FCWA exception 254FDBW exception 254FDMB exception 254features, advanced 157FEPC exception 254fetch request element

(FRE) pool utilization 250fetching screen spaces 155FGOLOOP keyword 156FHIO exception 255field

argument 133command name 133label 133parameter 133selecting 39

filtering data 46FMFS exception 255FORCE XACB keyword 241format

display area 128

INFO-line 128input area 128

FP region UOW contention 253FPSB exception 255FPSW exception 255FPTR exception 255free space

DMB pool, fragmented 253FREP command 250FREs

fixed dynamic 250FSB

pool 255function key area 39function keys 41, 140

displaying 85in the menu interface 121reinitializing after reset 118

function keys in help 50function keys in the CUA interface 41functions,advanced 51

GGDFN immediate 236, 238general help menu 116Go To pull-down 44graphical interface 24greater-than sign 129, 149green status bar character 89green status indicator 69

character 89displayed 88

GROUPXACB keyword 241XGSW keyword 239XSUM keyword 238

groupDMB, creating 182exception analysis 236PSB, creating 182switches 239XTRP keyword 238

groupsdefining 239switches 239

groups of IMS resources, managing 179

HH in column 1 137help 50, 134

about the current release 49added information 134

Index 293

extended 134function keys in 50glossary 49immediate commands 134index 49INFO-line commands 136major commands 134menu 116one-line 134panel level 49pull-down menu 49screens 116symbols 134user information 49

high I/O pool (HIOP) 255high I/O pool utilization 250highlignting on panels 40historical component 31

interfaces 25hold screen display 143HSBH exception 255HSBL exception 255

II/O

contention 177DELAY message 143prevention in progress 270toleration in progress 270

I/O error to database 253IBHI exception 255IBLO exception 255ICFX exception 255ICHI exception 255ICLO exception 255ICNS command 243, 259identifying DASD problems with a database 174ILHI exception 255ILLO exception 255IMHI exception 256IMLO exception 256immediate commands 132

help 134list 137

implicit action, controlling 85import profile 105IMS 243

command 82command entry 44, 82commands, issuing 79control task waiting 252CPU utilization 252

DC monitor active 253I/O error recovery alert 256inactive alert 256monitoring 32, 112physical logger task waiting 263plotting rates 113wait alert 262

IMS command entry 44IMS Direct Transfer 65IMS modes of operation 34IMSCTL 269IMSID 160INAC exception 256individual profile 83INFO-line 128

command 131commands 137components 129help commands 136system ID 129

initialization cycle 158input

area on INFO-line 129character(colon) 130

input queue length 260, 268inserting lines 140interval

refresh 88settings 100

invoking screen space 148IORC exception 256IRCS exception 256IRFC exception 256IRGC exception 256IRHI exception 256IRIN exception 256IRLM 252, 255, 256

CSA usage exception 256data sharing group connection 256false contention rate 256locks 256PTB trace 257real contention rate 257RH trace 257RLE usage 257working set size 269

IRLM resource conflict 270IRLO exception 256IRQH exception 256IRRC exception 257IRRU exception 257IRTP exception 257


IRTR exception 257ISAM/OSAM

database buffer pool locked 261ISHI exception 257ISLOexception 257ISPF

mode 231split-screen 231

issuing IMS Commands 79ITASK 266ITASKS waiting for dynamic SAPs 257ITASKS waiting for pool space 252ITWH exception 257IWAIT state 266

Jjobname on INFO-line 129

Kkeyword function 43keyword Go To 44

Llabel field 133LALO exception 257language 85LDMB exception 257less-than sign 142LEXC immediate 242lines,inserting and deleting 140LIST

XACB keyword 241XSUM keyword 238XTRP keyword 238

list messages 243list screen spaces 152LKTR exception 257LLBR exception 257LLCH exception 257LMGH exception 257LMLO exception 257load screen space

from &PROCSV to main storage 151lock trace alert 257locks details panel 218log

activating 99commands 144control 144screens 144

loggingoff menu interface 122

status on INFO-line 129logging facility (XLF)

activating 99setting parameters 241

logging on directly 229logon parameters 84logon profile 83, 84long message

dataset utilization 250long tape write-ahead alert 258looping region

how to identify 211looping screen spaces 156looping, preventing 100low

dataset going into miltiple extents 269top free block size in private 269total private free storage 269

low LSQAmaximmun free block size 257storage assurance 257

LPEX exception 257LPOQ exception 257LPOR exception 258LPOW exception 258LPSB exception 258LROWS parameters

up/down scrolling 138LSCR immediate 151LSLO exception 258LSQA 257

maximmun free block size 257storage assurance 257total free storage 258

LTOQ exception 258LTWA exception 258LVOQ exception 258

Mmain menu 109

accessing 110options 111

main storage 150, 153maintaining profiles 95, 103maintenance assessment service

MAS 282maintenance level, check 50major command 131, 142

continuing output 143help 134horizontal scrolling 142item count 142

Index 295

list 137repeating 143

management block (DMB)pool 254

managing IMS 32mapping exceptions to status indicators 69MAS

maintenance assessment service 282MAX up/down scrolling 138MDHI exception 258MDLO exception 258menu interface 24, 111

accessing 108ease-of-use features 116Help 116main menu 109operation 109program function keys 121quick access 117returning command interface 110starting 108stopping 122zooming to 108

menu options, selecting 111menu types 109menu/command interface operations 229menu/command interface, accessing 26message

boxing 240customizing 236exception 234exception analysis 243

message dequeue rate 258message format services

(MFS) pool utilization 250message format services (MFS) 255message inserts 259message processing region

common areapage-in rate 263

private areapage-in area 263

working set size 270message queue 259

buffer utilization 250message queue I/O

how to resolve bottlenecks,scenariosbottlenecked message queue 221

message region occupancy 264, 265messages

exception analysis 244modifiying 243trapping exceptions 243

MFS format library 260MFS overhead 259MFSH exception 258minor commands 132

.D argument 158

.H argument 158

.M argument 158

.R argument 158

.S argument 158difference output 158help 134list 137rate output 158repeating 143setting case 99

MIRT exception 259mnemonic action code 51, 84Mnnn exception 258MODE 159mode

dedicated 231ISPF 231tso 231VTAM 231

mode of operation 129, 230mode of operations 159modifying screen spaces 149monitoring

IMS 32system performance 68

moving the cursor 40MPCH exception 259MPP region utilization 252MSDB command 259MSDI exception 259MSDO exception 259MSGD command 258MSGE exception 259MSM

multi-services manager 282multiple output lines, viewing 130multi-services manager

MSM 282MVS Modify

for exporting profile 105for importing profile 106

NNACB exception 259national language 85navigation 40, 43, 118

accessing menu/command interface 26


NDIR exception 259NDRE exception 260NDSP setting for group switches 239NILU exception 260NLOQ exception 260no secondary RDS allocated 271NOFB exception 260NOOT exception 260NPDL exception 260NPOQ exception 260NQRE exception 260NSDC exception 260NTIQ exception 260number of

PSTs held on the standby system 270receive any buffers in use 251

NVAP exception 261NVOQ exception 261

OOBAU exception 261occupancy factor 264, 265ODIE exception 261OHLO exception 261OLDS

exceptions 258OLDS buffer waits 257OLER exception 261OLNA exception 261OLST exception 261OMEGAMON II 23

command interface 126logging screens 144menu interface 107operations 125starting 108user interface 23, 24

OMEGAMON II components 30, 31OMEGAMON main menu 177OMEGAVIEW 31OMEGAVIEW requirement 53ONLC exception 261ONLO exception 261operands 133operating modes, IMS 34operating OMEGAMON II

from the menu/command interface 229operating system level 159Operator Assist 183OPSYS 159options 76

keyword 46

main menu 111quick access to 117

Options pull-down 46trace 76

options, command 142OPTN immediate 144ORER exception 261ORIP exception 261ORST exception 261OSBL exception 261OSDN exception 262OUTP major command 144output

continuing 142displaying all 142next line output 142setting case 99skipping lines 142threads 260

output queue lengthlogical terminals (not video-type) 260logical terminals (video-type) 258, 260virtual terminals (video-type) 258, 261

overflowing field 259overview, OMEGAMON II 23, 24OXHI exception 262OXLO exception 262

Ppacked field 259PAGE up/down scrolling 138PAGELIMIT keyword

.SET immediate 144panel 40, 128

body 38color 40cursor movement 40display symbols 129format 38, 128help 49highlighting 40ID, displaying 84scrolling 41

panel appearance 38parameters

display 240exception box 240logon 84

PBS groupstarting 196

PBTR exception 262percentage, command output as 158

Index 297

performance monitoring 68PF keys 41, 140

assigning INFO-line commands to 141current assignments 142defining 140, 142menu interface 121PF22-PF99 141reinitializing after reset 118using

PF keys 140PFK immediate 140PI resource conflict 270PIBC exception 262PIBP exception 262PICC exception 262PICP exception 262PIDC exception 262PIDP exception 262PILC exception 262PILP exception 263PIMC exception 263PIQH exception 263PIRP exception 263PISC exception 263PISP exception 263PITR exception 263plus sign 142pool extension

IWAITs 249size 249

POP log argument 156pop-up windows 39pound sign 142preferences 47PREFIX 159PRINT INFO-line 145printer unable to receive output 263printing

output options 100screen 144, 145screen spaces 144

printing problems 15private area

exceptions 262, 263page-in rate 263

problem transactions 203product

code 159ID on INFO-line 129

profile 84, 88, 101color options 100configuring 98

control function options 100creating 95customizing 84customizing exceptions 89customizing threshold 89describing 98display options 99individual 238inprint options 100listing 96logon 84maintaining 95, 103saving 97suffix 160Timed Screen Facility entries 101types 83using 233

profile, user 97profiles

dynamic profile update facility 105program function(PF) keys 140program isolation 252

trace facility on 263PROQ exception 263PSB

definition 180exceptions 250investigating 205pool 258problem, confirming 209problem, resolving 210taking action on 206trace 262work pool 250, 255

PSB groupcopying 190creating new 187delete from 194stopping 195

PSTsnumber held on the standby system 270

PSVC exception 263pull-down action bar 39pull-down menu 39, 43

Go To 44keyword actions 43Options 46View 46

PUSH log argument 156pushbutton area 39pushbuttons 44


QQBKH exception 263question mark(?) in column 1 134queue

message 223transaction input 207

queue blocksdataser utillization 250

quick access to menu options 117

Rrate argument 158RDS

no secondary allocated 271RDSH exception 263receive any pool utilization 251RECON dataset 260red status bar character 89red status indicator 69refresh interval 88region 262

buffer wait 260common area page-in rate 262, 263Fast Path OBA 261I/O rate 256, 257I/O rate ,essage processing 256MPP database calls 259sync point interval 264utilization 252waiting time 263

region I/O ratemessage processing 256

Regions status light 71remote terminals 231rename screen space 153RENM immediate 153reorder exception output 242REPORT file 100RESET

XSUM keyword 238XTRP keyword 238

response time analysis component (RTA) 30response time problem,resolving

how to resolve 167response wait period 88restart dataset 263RGNW exception 263RGSH exception 263RGSI exception 264RKOIPCSV 152ROHI exception 264ROLO exception 265

RSR tracking systemVTAM connection 266

RSRV exception 266RTA component 30

SS on INFO-line 129SAPW exception 266save area

prefix exception 251SAVE PPRF option 97save screen space 150scenarios

looping BMP transaction 211managing groups of IMS resources 179poor response time 167resolving response time problem 167transaction queuing 199

schedule tracestatus 266

screenclearing 138control 138help 116inserting and deleting lines 140logging 145printing 144, 145stacking on INFO-line 129

screen in 150screen space 125

&ZFRSTSS 159/SAVE INFO-line 150assigning to PF keys 141branching between 155comment line 149conditional fetching 155creating 149, 150creating for zoom 161cursor position 149definition mode 149delay fetching 155deleting 154editing with text editor 149fetch (.FGO) 100, 155, 156first OMEGAMON II screen 99first screen name 159INFO-line commands in 149invoking 148, 155listing 152loading 151logging from 156looping 156

Index 299

LSCR immediate 151manipulating the log within 156modifying 149name on INFO-line 129names 150renaming 153RENM immediate 153saving 150separator line 149zooming 161

screen spaces 147printing 144

SCRN immediate 152scrolling 41

cursor controlled 138depth on INFO-line 129horizontal 142maximum number of lines 138page 138setting 99specific number of lines 138up/down window 138

SCTR exception 266SDLO exception 266SDSP exception 266searching for a string 41searching on the System Console panel 41secondary console control 163selective dispatching 248, 249, 266selective processing 252semicolon in column 1 134, 135separator line 149session switching 54Session switching procedure 54Sessions

switching 54Set Display options 99setting exceptions 90severity levels

customer support 279short message dataset

utilization 251short-cuts 51, 117signon 27SMGH exception 266SPAH exception 266START DC command 260STATE XGSW keyword 239status bar character

red status bar character 89status indicator mappings 69status indicators 68

character-based 69, 89colors 69controlling display 88monochrome 69spotting 201

steps for beginning users 43STOP=XACB keyword 241stopping

command processing 143menu interface 122OMEGAMON II 122screen updates 143

swap 231switches

setting 239switching sessions 54SYS=startup parameter 160system

ID 160ID on INFO-line 129performance monitoring 68

System Overview panel 71systemwide exceptions 114, 234, 236

TTCOI exception 267TCOT exception 267telephone support

customer support 278terminal

details 224start 226

terminal bellactivating 99setting interval 99

TERSE XACB keyword 241test .FGO routines 156test, exception 235THHI exception 267THHP exception 267THLO exception 267THLP exception 267thread details panel 60threads

high 267low 267

thresholdexceeding 90exceptions, customizing 90setting 235, 240value 159XACB parameters 240

time


displaying 84format 85on INFO-line 129

time controlled operations trace 267timed controlled operations (TCO) 267timed screen facility (TSF) 155, 159

activating 99defining entries 101

TMFH exception 267TMSI exception 267Tnnn exception 267TNRS exception 267TPSB exception 268trace 76tracking IMS transactions with ATF 76tracking IMS transactions with TRF 77transaction details 202, 204transaction input queue

rechecking 207transaction queuing problems

how to analyze 199Transaction Reporting Facility (TRF) 77transactions

competing 268non-competing 260

transferring among DBCTL and IMS sessions 65Translpex navigation

using with OII for CICS 57Transplex navigation

navigation, Transplex 55overview 55using with OII for DB2 60using with OII for IMS 63using with OMEGAMON II for DBCTL 64

Transport Manager subsystemVTAM connection 267

TRDY exception 268tripped exception 234, 237

help for 74last trip value 159worst trip value 159

TSO mode 231turquoise status indicator 69TXIQ exception 268type

immediate 131, 132INFO-line 131major 131minor 132

UUNIT=startup parameter 160

up/down scrolling 138user interfaces

command interface 24CUA interface 24graphical 24historical information 25menu interface 24OMEGAMON II 23

user profile 83deleting menu/command component 97suffix on INFO-line 129

USER= startup parameter 160user-defined profile 83

PPRF immediate 95

VVAR immediate 160variables

/ZOOM 159conditionally setting 160exception 159in screen spaces 150keywords for conditional setting 159OMEGAMON II-defined 159settings 159

VCAS exception 268VCIS exception 268version 400 27VHLO exception 268View

keyword 46View pull-down 46VMEX exception 268VMLO exception 269VROQ exception 269VSAM 269

dataset going into multiple extents 268VSAM control

interval splits 268VSLO exception 269VTAM mode 231VTLO exception 269VWRC exception 269VXHI exception 269VXLO exception 269

WWADS checkwrite requests 257wait period, command response 88WBHI exception 269WBLO exception 269WCHI exception 269

Index 301

WCLO exception 269WDNA exception 269WDNB exception 269WLHI exception 269WLLO exception 269WMHI exception 270WMLO exception 270work area for PEEK command 100work pool

ADBW exception 249AWKP exception 251FDBW 254FDBW exception 254PSBW exception 250

working set size 270WRHI exception 270WRLO exception 270WSHI exception 270WSLO exception 270

XXACB immediate 239, 240, 244XCNF exception 270XGRP immediate 239XGSW immediate 239XIMS

immediate 236XLF XACB parameter 241XRAT exception 270

XRAV exception 270XRF 270, 271

surveillance 270XRIP exception 270XRIT exception 270XRNS exception 270XRPH exception 270XRSR exception 271XRTO exception 271XSUM immediate 237, 239XTRP immediate 237, 239

Yyellow status bar character 89yellow status indicator 69

Zzeros, displaying 99zoom 161

cursor pointing 161prefix 161screens spaces for 161to detail panels 161, 235to detail screens 118to menu interface 108variables 159

zooming to menu/command interface 26

OMEGAMON II for IMS User’s Guide, Vഀ攀爀猀椀漀渀...

Documents

Transcript of OMEGAMON II for IMS User’s Guide, Vഀ攀爀猀椀漀渀...