OMEGAMON II for CICS Reference Manual, Volume 2,...

Reference ManualOMEGAMON II® for CICS

Volume 2

Version 520

GC32-9247-00

October 2001

Candle Corporation201 North Douglas Street

El Segundo, California 90245-9796

2 OMEGAMON II for CICS Reference Manual, Volume 2, Version 520

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*ServiceMonitor, eBA*ServiceNetwork, ETEWatch, IntelliWatch, IntelliWatch Pinnacle, MQSecure, MQView, OMEGACENTER, OMEGAMON, OMEGAMON/e, OMEGAMON II, OMEGAMON Monitoring Agent, OMEGAVIEW, OMEGAVIEW II, PQEdit, Solutions for Networked Applications, Solutions for Networked Businesses, and Transplex.Trademarks and service marks of Candle Corporation: Alert Adapter, Alert Adapter Plus, Alert Emitter, AMS, Amsys, AutoBridge, AUTOMATED FACILITIES, Availability Management Systems, Candle Alert, Candle Business Partner Logo, Candle Command Center/SentinelManager, Candle CommandPro, CandleLight, CandleNet, CandleNet 2000, CandleNet Command Center, CandleNet eBP, CandleNet eBP Access, CandleNet eBP Administrator, CandleNet eBP Broker Access, CandleNet eBP Configuration, CandleNet eBP Connector, CandleNet eBP File Transfer, CandleNet eBP Host Connect, CandleNet eBP Object Access, CandleNet eBP Object Browser, CandleNet eBP Secure Access, CandleNet eBP Service Directory, CandleNet eBP Universal Connector, CandleNet eBP Workflow Access, CandleNet eBusiness Assurance, CandleNet eBusiness Exchange, CandleNet eBusiness Platform, CandleNet eBusiness Platform Administrator, CandleNet eBusiness Platform Connector, CandleNet eBusiness Platform Connectors, CandleNet eBusiness Platform Powered by Roma Technology, CandleNet eBusiness Platform Service Directory, CandleNet Portal, CCC, CCP, CEBA, CECS, CICAT, CL/ENGINE, CL/GATEWAY, CL/TECHNOLOGY, CMS, CMW, Command & Control, Connect-Notes, Connect-Two, CSA ANALYZER, CT/ALS, CT/Application Logic Services, CT/DCS, CT/Distributed Computing Services, CT/Engine, CT/Implementation Services, CT/IX, CT/Workbench, CT/Workstation Server, CT/WS, !DB Logo, !DB/DASD, !DB/EXPLAIN, !DB/MIGRATOR, !DB/QUICKCHANGE, !DB/QUICKCOMPARE, !DB/SMU, !DB/Tools, !DB/WORKBENCH, Design Network, DEXAN, e2e, eBA, 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 © October 2001, Candle Corporation, a California corporation. All rights reserved. International rights secured.

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

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

Contents 3

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23New Features and Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Chapter 1. Introduction to the Menu System Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Signing Onto the Menu System Interface Directly . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30OMEGAMON II Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Chapter 2. Using the Menu System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Menu System Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36Menu System Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37INFO-line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39Menu System Function Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40Menu System Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41Menu System Zooming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42Fast Pathing in the Menu System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Menu System Help Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Menu System Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Chapter 3. Overview Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Displaying CICS Regions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Performance Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Chapter 4. Response Time Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53CICS Transaction Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Response Time Data Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Network Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Response Time Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Response Time Data Collection Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Chapter 5. Exception Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Displaying Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66Global CPU Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69CICS Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

Contents


Customizing Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83VSAM Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Chapter 6. Task Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89Task Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90Task Detail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91Categorizing Task Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102Killing a Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105Transaction Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109Resource Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111Starting and Stopping Resource Limiting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

Chapter 7. Task History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117Historical Task Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118Historical Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119Historical Detail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121File Level Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124Historical Task Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129Controlling Online Historical Viewing Collector (ONDV) . . . . . . . . . . . . . . . . . . . . . . .131

Chapter 8. Bottleneck Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135How Bottleneck Analysis Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136Bottleneck Analysis Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137Wait Reasons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140Operational Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145Enqueues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149

Chapter 9. Impact Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153How Impact Analysis Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154Starting and Stopping Impact Analysis Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . .155Impact Analysis Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156Workload Impact Profile (IPRO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161Adjusting Collection and Display Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163

Chapter 10. Storage Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167CICS Storage Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169CICS Storage Analysis Displays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171MVS Storage Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188MVS Storage Management Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189Storage Display and Alteration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195

Chapter 11. File Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197Accessing the Files Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198File Allocation and Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199VSAM Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207

Contents 5

Chapter 12. Database Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Accessing the Databases Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216DB2 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217DLI Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219

Chapter 13. CICS System Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229Accessing the CICS Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231Automatic Initiate Descriptors (AIDs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233AID Kill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235Common System Area (CSA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236Destination Control Table (DCT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238DLI Data Management Block Directory (DDIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242DLI Program Specification Block Directory (PDIR) . . . . . . . . . . . . . . . . . . . . . . . . . . .244CICS Dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246CICS Exits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247Extended Recovery Facility (XRF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249File Control Table (FCT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250Interval Control Elements (ICEs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255ICE Kill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257Journal Control Table (JCT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258Processing Program Table (PPT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261System Initialization Table (SIT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264Terminal Control Table Prefix (TCTFX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266Temporary Storage Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267Temporary Storage Queues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269Terminal Control Table (TCT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271CICS Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276Program Control Table (PCT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278Transient Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281CICS Shutdown Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284

Chapter 14. MVS Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285CPU and Paging Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286Program Status Word (PSW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291TCB Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292MVS Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293

Chapter 15. DASD Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295DASD Response Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296Devices Exceeding a Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298DASD Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299Device Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300

Chapter 16. Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303Accessing Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .304


Issuing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305Obtaining Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308Viewing and Modifying Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316

Chapter 17. Group Definition and Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325Background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .326Stopping and Starting the Response Time Data Collector . . . . . . . . . . . . . . . . . . . . . .327Group Definition Limits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .328Element Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329Default Group Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .330Group Definition Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .331

Appendix A. Menu System Fastpath Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341Using the Fastpath Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .342

Appendix B. Guide to Candle Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359Base Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .360Enhanced Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .364Customer Support Contact Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

List of Figures

FIGURE 1. Signing onto OMEGAMON II through ISPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30FIGURE 2. Menu System Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36FIGURE 3. Tasks Panel Showing Horizontal Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37FIGURE 4. Profile Panel Showing Vertical Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38FIGURE 5. INFO-line Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39FIGURE 6. Typical Help Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44FIGURE 7. OMEGAMON II General Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45FIGURE 8. Summary of CICS Regions Panel (W.). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48FIGURE 9. Performance Overview Panel (V.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

FIGURE 10. Transaction Response Times by Intervals Panel (R.G) . . . . . . . . . . . . . . . . . . . . . . . . . .57FIGURE 11. Groups with Response Time Activity in Last 10 Minutes Panel (R.) . . . . . . . . . . . . . . . .58FIGURE 12. Graph of Response Time Problems Panel (R.F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60FIGURE 13. End-to-end Response Times for LUs Panel (R.K) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61FIGURE 14. Average Transaction Response Times Panel (R.J) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62FIGURE 15. Current Exceptions Panel (E.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66FIGURE 16. Summary of Exceptions this Session Panel (E.B). . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67FIGURE 17. Exception Recommendation Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . .68FIGURE 18. Global Resource Limit Panel (P.A.K) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69FIGURE 19. Database Exception Settings Panel (P.A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83FIGURE 20. VSAM Exception Settings Panel (P.A.I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88FIGURE 21. All Tasks in System Panel (T.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90FIGURE 22. Task Detail Panel - Task Detail Information Section (T.F.P). . . . . . . . . . . . . . . . . . . . . . .92FIGURE 23. Task Detail Panel - Remote Information Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94FIGURE 24. Task Detail Panel - Current Storage Usage Section (CICS/MVS) . . . . . . . . . . . . . . . . . .95FIGURE 25. Task Detail Panel - Current Storage Usage Section (CICS/ESA). . . . . . . . . . . . . . . . . . .96FIGURE 26. Task Detail Panel - Storage Statistics Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97FIGURE 27. Task Detail Panel - Time Statistics Section (CICS/ESA) . . . . . . . . . . . . . . . . . . . . . . . . .98FIGURE 28. Task Detail Panel - General Statistics Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98FIGURE 29. Task Detail Panel - File Control Statistics Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99FIGURE 30. Task Detail Panel - DLI Statistics Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99FIGURE 31. Task Detail Panel - ADABAS Statistics Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100FIGURE 32. Task Detail Panel - Umbrella Data Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100FIGURE 33. Task Detail Panel - Unit-of-Work Information Section . . . . . . . . . . . . . . . . . . . . . . . . .100FIGURE 34. Horizontal Menu Showing Task Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102FIGURE 35. Tasks in a Class Panel (T.F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103FIGURE 36. Kill Tasks Panel (T.G) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105FIGURE 37. Kill Task Detail Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106FIGURE 38. Transaction Rate Panel (T.H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109FIGURE 39. Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114FIGURE 40. Control Options Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

List of Figures 7

FIGURE 41. Historical Transaction Overview Panel (H.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119FIGURE 42. (Part 1) Historical Transaction Detail Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . .121FIGURE 43. (Part 2) Historical Transaction Detail Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . .122FIGURE 44. (Part 3) Historical Transaction Detail Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . .123FIGURE 45. Historical File Summary for Selected Task (Accessed by Zoom). . . . . . . . . . . . . . . . . .124FIGURE 46. DLI Statistics (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125FIGURE 47. ADABAS Statistics (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125FIGURE 48. DATACOM Statistics (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126FIGURE 49. IDMS Statistics (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126FIGURE 50. USREVNT1 Statistics (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127FIGURE 51. SUPRA Statistics (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127FIGURE 52. Detail File Request Statistics Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . .128FIGURE 53. Set Criteria for Selecting Historical Records Panel (H.B) . . . . . . . . . . . . . . . . . . . . . . .129FIGURE 54. Historical Collector Status Panel (O.H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131FIGURE 55. Control Database Collectors Panel (O.P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133FIGURE 56. Bottlenecks Panel (B.B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137FIGURE 57. Bottleneck Graph Panel (B.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138FIGURE 58. Wait Reason Detail Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139FIGURE 59. Bottleneck Analysis Control Panel (O.I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146FIGURE 60. Control Bottleneck Analysis Wait Reason Buckets Panel (O.J) . . . . . . . . . . . . . . . . . . .147FIGURE 61. Enqueues with Tasks Waiting Panel (B.H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149FIGURE 62. Enqueues with Tasks Waiting Panel Using RES=* (B.H) . . . . . . . . . . . . . . . . . . . . . . .151FIGURE 63. Enqueue Resource Detail Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . .152FIGURE 64. Workload Impact Analysis Panel (B.E). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156FIGURE 65. Display Body Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157FIGURE 66. Workload Impact Analysis Detail Panel (B.G) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159FIGURE 67. Workload Impact Analysis Profile Panel (B.F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161FIGURE 68. Workload Impact Analysis Settings Panel (O.N) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163FIGURE 69. Plot Percentage Message Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165FIGURE 70. Storage Summary Panel (S.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172FIGURE 71. Storage Violations Panel (S.B). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175FIGURE 72. Task Storage Panel (S.C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176FIGURE 73. Dynamic Storage Area Panel for CICS/ESA Version 4.1 (S.D) . . . . . . . . . . . . . . . . . . .177FIGURE 74. Dynamic Storage Area Panel for CICS/ESA (S.D) . . . . . . . . . . . . . . . . . . . . . . . . . . . .179FIGURE 75. Dynamic Storage Area Panel for CICS/MVS (S.D). . . . . . . . . . . . . . . . . . . . . . . . . . . .180FIGURE 76. Storage Allocated in the DSA Panel for CICS/ESA (S.F) . . . . . . . . . . . . . . . . . . . . . . .181FIGURE 77. Storage Allocated in the DSA Panel for CICS/MVS (S.F) . . . . . . . . . . . . . . . . . . . . . . .182FIGURE 78. Storage Usage for All Subpool Groups Panel for CICS/ESA (S.H) . . . . . . . . . . . . . . . .184FIGURE 79. Storage Usage for a Loader Subpool Group (Accessed by Zoom) . . . . . . . . . . . . . . . .185FIGURE 80. Storage Usage for a Task Subpool Group (Accessed by Zoom) . . . . . . . . . . . . . . . . . .186FIGURE 81. Storage Compressions for CICS/MVS Panel (S.J) . . . . . . . . . . . . . . . . . . . . . . . . . . . .187FIGURE 82. CICS Region MVS Subpools Panel (M.F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190FIGURE 83. CICS Region Storage Panel (S.I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192FIGURE 84. All Datasets Allocated to CICS Panel (F.H). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199FIGURE 85. Select Datasets Panel (F.L) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201


FIGURE 86. File Detail Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202FIGURE 87. VSAM Summary Panel (F.E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207FIGURE 88. VSAM File Detail Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209FIGURE 89. LSR Pool Summary Panel (F.F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210FIGURE 90. LSR Pool Detail Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212FIGURE 91. Files Using Specific LSR Pool (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . .213FIGURE 92. String and Buffer Waits Panel (F.I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214FIGURE 93. CICS/DB2 Interface Panel (D.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217FIGURE 94. DB2 Transaction Detail Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . .218FIGURE 95. DLI Summary Panel (D.B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219FIGURE 96. DLI General Information Panel (D.C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221FIGURE 97. DLI Databases Panel (D.D) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222FIGURE 98. DLI Database Detail Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223FIGURE 99. DLI Subpool Statistics Panel (D.E). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224

FIGURE 100. CICS/DLI Interface ECBs Panel (D.F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225FIGURE 101. CICS/DLI Interface Addresses Panel (D.G) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226FIGURE 102. CICS/DBCTL Interface Panel (D.H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227FIGURE 103. CICS Options Menu Panel (C.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231FIGURE 104. Automatic Initiate Descriptors (AIDs) Panel (C.A) . . . . . . . . . . . . . . . . . . . . . . . . . . . .233FIGURE 105. AID Detail Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234FIGURE 106. Common System Area (CSA) Panel (C.C). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236FIGURE 107. Destination Control Table Attributes Panel (C.D) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238FIGURE 108. DCT Summary Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239FIGURE 109. Extrapartition DCT Entry Panel (Accessed by Zoom). . . . . . . . . . . . . . . . . . . . . . . . . .240FIGURE 110. Indirect Intrapartition DCT Entry Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . .241FIGURE 111. DLI DMB Directory Attributes Panel (C.F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242FIGURE 112. DDIR Summary Panel (Accessed by Zoom). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243FIGURE 113. DLI PSB Directory Attributes Panel (C.G) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244FIGURE 114. PDIR Summary Display (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245FIGURE 115. Dump Component Panel (C.H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246FIGURE 116. Exits Panel (C.I). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247FIGURE 117. Extended Recovery Facility Status Panel (C.J) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249FIGURE 118. File Control Table Attributes Panel (C.K) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250FIGURE 119. FCT Summary Panel (Accessed by Zoom). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251FIGURE 120. FCT Entry Panel for VSAM File (Accessed by Zoom). . . . . . . . . . . . . . . . . . . . . . . . . .252FIGURE 121. FCT Entry Panel for BDAM File (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . .253FIGURE 122. FCT Entry - Remote Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253FIGURE 123. FCT Entry - Data Table Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254FIGURE 124. Interval Control Elements (ICEs) Panel (C.L). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255FIGURE 125. ICE Detail Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256FIGURE 126. Journal Control Table Attributes Panel (C.N) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258FIGURE 127. JCT Summary Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259FIGURE 128. JCT Entry Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260FIGURE 129. Processing Program Table Attributes Panel (C.Q). . . . . . . . . . . . . . . . . . . . . . . . . . . . .261FIGURE 130. PPT Summary Panel (Accessed by Zoom). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .262

List of Figures 9

FIGURE 131. PPT Entry Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263FIGURE 132. System Initialization Table (SIT) Panel (C.R) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265FIGURE 133. Terminal Control Table Prefix Panel (C.S) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266FIGURE 134. Temporary Storage Panel (C.T) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267FIGURE 135. Temporary Storage Queues Panel (C.U) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269FIGURE 136. Terminal Control Table Attributes Panel (C.V) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271FIGURE 137. TCT Summary Panel (Accessed by Zoom). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272FIGURE 138. TCT 3270 Entry Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273FIGURE 139. TCT BSAM Entry (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274FIGURE 140. TCT Console Entry (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274FIGURE 141. TCT Connection Entry (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274FIGURE 142. TCT SYS/IRC Entry (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275FIGURE 143. TCT Remote Entry (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275FIGURE 144. CICS Trace Overview Panel for CICS/ESA (C.W) . . . . . . . . . . . . . . . . . . . . . . . . . . . .276FIGURE 145. CICS Trace Overview Panel for CICS/MVS (C.W) . . . . . . . . . . . . . . . . . . . . . . . . . . . .277FIGURE 146. Program Control Table Attributes Panel (C.X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278FIGURE 147. PCT Summary Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279FIGURE 148. PCT Entry Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280FIGURE 149. Transient Data Panel (C.Y) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282FIGURE 150. CICS Shutdown Purge Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284FIGURE 151. CICS System Analysis Panel (M.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286FIGURE 152. System Summary Panel (M.B). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288FIGURE 153. PSW and Registers Panel (M.C). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291FIGURE 154. CICS TCB Structure Panel (M.D). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292FIGURE 155. MVS Loaded Modules in the CICS Address Space Panel (M.E) . . . . . . . . . . . . . . . . . .293FIGURE 156. CICS DASD Statistics Panel (I.A). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296FIGURE 157. DASD Exceeding Thresholds Panel (I.B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298FIGURE 158. DASD Allocation, User, and Number of Open DCBs Panel (I.C) . . . . . . . . . . . . . . . . .299FIGURE 159. Examining a Specific Device (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . . . . .300FIGURE 160. DASD Detail Panel (I.D) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301FIGURE 161. DASD Plot Panel (I.E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .302FIGURE 162. Utilities Menu Panel (U.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .304FIGURE 163. Operating System Console Panel (U.A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305FIGURE 164. Display or Change CICS Master Terminal Settings Panel (U.L) . . . . . . . . . . . . . . . . . .306FIGURE 165. Issue Common Interface Command Panel (U.M). . . . . . . . . . . . . . . . . . . . . . . . . . . . .307FIGURE 166. CICS Snapshot Panel (U.N) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308FIGURE 167. OMEGAMON II Diagnostics Introductary Panel (U.O). . . . . . . . . . . . . . . . . . . . . . . . .309FIGURE 168. OMEGAMON II Diagnostics Banner Page Panel (U.O then Enter) . . . . . . . . . . . . . . . .310FIGURE 169. Verify OMEGAMON II Components Panel - Part 1 (U.P). . . . . . . . . . . . . . . . . . . . . . .312FIGURE 170. Verify OMEGAMON II Components Panel - Part 2 (U.P). . . . . . . . . . . . . . . . . . . . . . .313FIGURE 171. Verify OMEGAMON II Components Panel - Part 3 (U.P). . . . . . . . . . . . . . . . . . . . . . .314FIGURE 172. Current OMEGAMON II Maintenance Panel (U.Q) . . . . . . . . . . . . . . . . . . . . . . . . . . .315FIGURE 173. Display OMEGAMON II or Common Area Storage Panel (U.B) . . . . . . . . . . . . . . . . .316FIGURE 174. Scan OMEGAMON II or Common Area Storage Panel (U.C) . . . . . . . . . . . . . . . . . . .317FIGURE 175. Modify OMEGAMON II or Common Area Storage Panel (U.D). . . . . . . . . . . . . . . . . .317


FIGURE 176. Display CICS Storage Panel (U.E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318FIGURE 177. Sample MDEF Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .319FIGURE 178. Scan CICS Storage Panel (U.F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .319FIGURE 179. Modify CICS Storage Panel (U.G) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320FIGURE 180. Display Dataspace Storage Panel (U.H). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .321FIGURE 181. Scan Dataspace Storage Panel (U.I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .321FIGURE 182. Modify Dataspace Storage Panel (U.J) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .322FIGURE 183. List Dataspaces Panel (U.K). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323FIGURE 184. Group Summary Panel (G.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .331FIGURE 185. Group Detail Information Panel (Accessed by Zoom) . . . . . . . . . . . . . . . . . . . . . . . . .332FIGURE 186. Create Group Panel (G.B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .332FIGURE 187. Add Elements to Group Panel (G.C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334FIGURE 188. Update Group Panel (G.D) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .335FIGURE 189. Update Elements in Group Panel (G.E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .336FIGURE 190. Delete Elements from a Group Panel (G.F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .337FIGURE 191. Clear a Group Panel (G.G) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .338FIGURE 192. List Groups Panel (G.H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .339

List of Figures 11


List of Tables

Table 1. OMEGAMON II for CICS Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Table 2. Symbols in Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Table 3. Page Locations for Control Options Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Table 4. Task Detail Display Zoom Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101Table 5. Task Resources and Limit Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112

List of Tables 13


Preface 15

Preface

OMEGAMON II is a comprehensive software performance monitor that assists in troubleshooting problems and tuning your IBM Customer Information Control System (CICS). Providing a real-time window into CICS activity, OMEGAMON II automatically detects and warns of problems that affect CICS availability and performance, identifying any degradation associated with resources internal to CICS or external to CICS in the MVS environment.

Although OMEGAMON II runs in a separate address space from CICS, it has some facilities that run within the CICS address space.

OMEGAMON II can monitor multiple CICS systems running at different release levels. Refer to the OMEGAMON II for CICS Configuration and Customization Guide for all releases of IBM software that OMEGAMON II currently supports.

This document refers to version 2 of CICS as CICS/MVS, and Versions 3 and greater as CICS/ESA.

Preface Contents

About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Who should read this book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Documentation set information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Where to look for more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Ordering additional documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18We would like to hear from you . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Printing this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Printing problems? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Contacting Adobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Panels and figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Revision bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Variables and literals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

P

About This Book


About This Book

Who should read this bookThis document provides comprehensive information on the features of OMEGAMON II for CICS Version 520 (hereafter referred to as OMEGAMON II). The manual should be read by those who need to understand how or use OMEGAMON II’s CUA interface and menu system interface to access the data you n need to analyze CICS performance problems, create profiles, define groups for monitoring purposes, and use all of OMEGAMON II’s features.

n Volume 1 provides the information about the CUA interface.

n Volume 2 provides the information about the menu system interface.

Documentation set informationThe documentation listed below is available for OMEGAMON II for CICS.

Table 1. OMEGAMON II for CICS Documentation

Document Number Document Name Description

C251-6363 OMEGAMON II for CICS Configuration and Customization Guide

Explains how to configure and customize OMEGAMON II after it is installed.

C254-6312 OMEGAMON II for CICS User’s Guide

Provides a task-oriented guide to using OMEGAMON II. Explains basic features and navigation methods.

C253-6313 OMEGAMON II for CICS Reference Manual - Volume 1

Provides comprehensive reference information about the features of OMEGAMON II and explains how to access OMEGAMON II data in the CUA interface.

C253-6314 OMEGAMON II for CICS Reference Manual - Volume 2

Provides comprehensive reference information about the features of OMEGAMON II and explains how to access OMEGAMON II data in the menu system interface.

C299-6316 OMEGAMON II for CICS Historical Reporting Manual

Describes how to use the SMF records created by OMEGAMON II to produce historical reports.

WO52-6238

WO52-6239

WO52-6240

Messages Manual - Volume 1 OMEGAMON II/OMEGAVIEW



Provides reference summary of all OMEGAMON II and OMEGAVIEW messages.

C257-6315 OMEGAMON II for CICS Problem Determination Manual

Describes how to diagnose and solve problems that you may encounter with OMEGAMON II, get the best possible problem-solving help from Candle Customer Support, and prevent or reduce the recurrence of problems.

Preface 17

About This Book

C299-6370 OMEGAMON II for CICS Quick Reference Card

Pocket-sized document that explains how to use the CUA interface and lists all of the fast paths.

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

Describes ETE and its commands, and lists its error messages, return codes, and sense codes.

Table 1. OMEGAMON II for CICS Documentation

Document Number Document Name Description

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 CICS Reference Manual, Volume 2, Version 520" in the subject line.

Preface 19

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 All

n Current page

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

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.

Preface 21


{ } 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.

Table 2. Symbols in Command Syntax

Symbol Usage



What’s New 23

What’s New

IntroductionThis section details the new features and enhancements incorporated into OMEGAMON II for CICS Version 520.

HighlightsOMEGAMON II for CICS Version 520 includes the following new features and enhancements:

n Allows printing a SNAPSHOT of a CICS region.

n Added the Exchange Logname Status exception.

n Added Transaction Server 1.3 Task Monitoring Data and Statistics

n Enhanced RLIM Interval Settings

n Added User Defined Event Monitoring

n Enhanced ADABAS statistics reporting

n Added support for ADABAS 7.1

The following features are no longer supported by OMEGAMON II for CICS Version 520:

n Support for CICS/ESA Version 3.x.x

n Documentation for BookManager no longer supported

W

New Features and Enhancements



Print SNAPSHOT of CICS RegionThe SNAP facility is composed of a sequence of pre-defined OMEGAMON II screens which contain every OMEGAMON Classic command you can use to report on the state and content of your CICS region.

This facility is now accessible in the C2/CUA interface to OMEGAMON II for CICS product. A new item was added to the Options/Controls pulldown which upon selection will route the output to the JES print queue under the common interface (Menu System) Job JCL.

Exchange Logname Status ExceptionExchange Logname status is a new OMEGAMON II for CICS exception added to the list of existing ones under the MRO/ISC. Once enabled the MRO/ISC light will alert users when the Exchange Log Name or XLN is ’Notdone’ between two, APPC type connected, CICS systems.

Online Global FacilityThe Online Global Facility is introduced to eliminate the requirement for re-assembly and linking of the product global data area module(s). Using the C2/CUA interface, this facility will enable users to SAVE the currently running global module to the library defined by the RKC2GLBL DD statement.

Using the Candle Installation/Configuration Assistance Tool (CICAT), users can edit and verify any of the existing global data area modules. Note that utilities are provided to migrate the previous versions of the global data area to the new format in V520. Refer to the OMEGAMON II for CICS Configuration and Customization Guide for more information.

What’s New 25


Transaction Server 1.3 Task Monitoring Data and StatisticsThe OMEGAMON II for CICS product has been enhanced to support the new performance monitoring data and statistics introduced in Transaction Server release 1.3. Non-3270 statistics such as WEB Send and Receive request counts are now displayable in active transactions as well as the Online History (ONDV) component.

The Task Time Analysis screens have been enhanced to include the newly introduced performance monitoring data such as JVM elapsed and suspend times, IMS(DBCTL) wait time, DB2 wait times, Socket I/O wait time, Global ENQ delay, among others. In addition, the Task Timings panels have been redesigned to display a categorical view of Timings attributed to a transaction or task.

Resource Limiting (RLIM) Interval SettingsThe Resource Limiting feature of OMEGAMON II for CICS product has been enhanced to introduce a set of user defined intervals. This enhancement will allow users to activate the previously defined rules based on a user modifiable interval. The new RLIM interval may be set in three different ways:

n By TIME.

n By the number of EXEC CICS calls made by a task.

n By the number of Database calls made by a task.

User Defined Event MonitoringThe User Defined Event Monitoring (USREVNT1) describes a way for application programmers to clock and count the number of requests being made to an in-house database, program or procedure. Similar to other Third Party Products such as ADABAS, DATACOM, IDMS and SUPRA, this facility may be enabled from the Options pulldown in the C2/CUA interface under the CICS File/Database collection option.



ADABAS Statistics ReportingADABAS statistics in the OMEGAMON II for CICS product have been traditionally based on DB ID and File number. With the specification of a new operand in the product’s global data area module, users may request OMEGAMON to collect statistics based on DB ID, File number, and Command Code.

Support for ADABAS V7.1The new release of ADABAS V7.1 supports DB IDs greater than 255. The relevant OMEGAMON II for CICS product panels were enhanced to display a 5-digit database ID.

Online DocumentationWith version 520, Candle Corporation has moved OMEGAMON II for CICS 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 CICS 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 to the Menu System Interface 27

Introduction to theMenu System Interface

Chapter OverviewThe realtime monitor includes two user interfaces: the CUA and menu system interface. This section provides information about the menu system interface. Refer to Part 1 of this manual and the OMEGAMON II for CICS User’s Guide for information on using the CUA interface of OMEGAMON II.

Chapter ContentsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Signing Onto the Menu System Interface Directly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

VTAM mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30ISPF mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30TSO mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Dedicated mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

OMEGAMON II Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Bottleneck analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32CICS system analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Exception analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Response time analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Storage analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Task analysis (realtime and historical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33File/database analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Impact analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33MVS analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

1

Overview


OverviewMost chapters begin with an overview of an OMEGAMON II feature and describe how to use it to improve CICS performance. Sample display panels show typical OMEGAMON II data available through the menu system. Following the sample panels are definitions of significant fields with information about their importance in tuning CICS.

You will find these OMEGAMON II features as the subject of chapters in this part of the reference manual:

n bottleneck analysisn CICS system analysisn exception analysisn file analysisn database analysisn impact analysisn DASD performancen MVS analysisn response time analysisn storage analysisn realtime task analysisn historical task analysisn user profile facilityn group definition and activation

Refer to “OMEGAMON II Features” on page 32 for a detailed description of each of these features.

Information on the Control Options, a feature which lets you do such things as

n view the current status and start or stop the response time monitor, ONDV collection, bottleneck analysis, and impact analysis

n set response time monitor intervals

n control bottleneck analysis wait reasons

does not appear in a separate chapter but is incorporated in the pertinent chapters that cover a particular feature. The following table shows the pages where you can find information on the control options within the chapters.


Overview

Table 3. Page Locations for Control Options Information

Control Options Pages

RTA On, RTA Off, RTA Status, RTA Intervals, RTA Scale/Window

page 55 and page 63

ONDV On, ONDV Off, ONDV Status, Database Collectors

page 131–page 132, page 133

Bottleneck Control page 146

Bottleneck Wait Reasons page 137–page 138, page 147

INTR Control See the OMEGAMON II for CICS Historical Reporting Guide.

Impact Analysis On page 156

Impact Analysis Off page 156

Impact Analysis Settings page 163

CICS Shutdown Option page 284

Resource Limiting On, Resource Limiting Off, Resource Limiting Status

page 114

Signing Onto the Menu System Interface Directly


Signing Onto the Menu System Interface DirectlyOMEGAMON II can operate in standalone mode or under Candle’s OMEGAVIEW product. You can log onto the OMEGAMON II Menu System directly or through the CUA interface. Refer to Part 1 of this manual and the OMEGAMON II for CICS User’s Guide for information on using the CUA interface of OMEGAMON II. You can log on directly to the Menu System in four ways.

VTAM modeTo start an OMEGAMON II session under VTAM, issue the following command on a VTAM terminal:

LOGON APPLID(aaaaaaaa) DATA(‘CICS=cccccccc’)

ISPF modeIn ISPF mode, you sign onto OMEGAMON II from TSO/ISPF.

To start an OMEGAMON II session, choose one of the following methods:

n If you installed a selection for OMEGAMON II on your site’s ISPF Primary Options Menu or ISPF panel, select OMEGAMON II on the menu to invoke KOCLIST.

n If OMEGAMON II is not a selection on your site’s ISPF Primary Options Menu, invoke the following CLIST for TSO/E: %KOCLIST.

When you log on in ISPF mode, OMEGAMON II recognizes that you invoked KOCLIST in ISPF mode.

OMEGAMON II displays this ISPF panel.

FIGURE 1. Signing onto OMEGAMON II through ISPF

aaaaaaaa The VTAM APPLID specified to KOCVTMnn when OMEGAMON II was started.

cccccccc The CICS jobname to be monitored (optional if the default is specified in the KOCVTMnn member of rhilev.RKANPAR).

--------------------------- OCSPF - INVOCATION MENU -------------------------- OPTION ===> _ 1 ASSIGN KEYS - ASSIGN SPLIT-SWAP PFK 2 LOGON KOCVTAM - START OMCICS VTAM SESSION X EXIT - EXIT THIS SCREEN FOR OPTION 2, SPECIFY: USER SUFFIX ===> /C LROWS ===> 99 FIRST SCREEN ===> OBVTAM APPL ===> OBVTAMA CICS JOBNAME ===> PRODCICS


Signing Onto the Menu System Interface Directly

Select option 1 if you want to assign function keys. The default keys are F2 for the ISPF split function and F9 for the ISPF swap function.

Select option 2 to log on and provide appropriate values for the requested fields.

When your logon is successful, the first screen you see is the OMEGAMON II copyright screen. Press Enter to continue. OMEGAMON II is now running in ISPF mode. Split screen mode is allowed.

TSO modeTo start an OMEGAMON II session under TSO, invoke one of the following CLISTs:

Replace cccccccc with the CICS region you want to monitor, and add additional parameters as required.

When you log on in TSO mode, OMEGAMON II recognizes that you invoked KOCLIST in TSO mode.

The first screen you see is the OMEGAMON II copyright screen. Press Enter to continue. OMEGAMON II is now running in TSO mode.

Dedicated modeYou start an OMEGAMON II dedicated session on a locally attached terminal. This mode uses EXCP to ensure availability even if TSO or VTAM is not responding.

Verify that the terminal you use is not an MVS console or is not allocated to any other job or started task (including VTAM). A dedicated OMEGAMON II session requires the use of a locally-attached, non-SNA terminal.

Start a dedicated session.

n Prepare a member in rhilev.RKANPAR that contains an appropriate START command. Use the shipped sample member in the data library as a model. Refer to the OMEGAMON II for CICS Configuration and Customization Guide for more information on installing in dedicated mode.

n Enter the MVS MODIFY command shown below.

F KOCCI,EXEC cccccccc

The MVS console log indicates that the dedicated session has started. The first screen you see on the dedicated terminal is the OMEGAMON II copyright screen. The session automatically refreshes itself every few seconds.

cccccccc The name of the member in rhilev.RKANPAR that contains a START command.

%KOCLIST CICS(cccccccc) (,added parameters as required) * for TSO/E - OR - %KOCLISTN CICS(cccccccc) (,added parameters as required) * for non-TSO/E

OMEGAMON II Features


OMEGAMON II FeaturesThe following features of OMEGAMON II provide information to help you improve CICS performance.

Bottleneck analysisA CICS task waits many times during normal processing. OMEGAMON II’s bottleneck analysis feature monitors and categorizes the resources for which CICS tasks are waiting. Typical waits might include I/O events, VSAM buffer and string waits, enqueue waits, and short-on-storage conditions.

As applications grow and change, so does the use of resources in the CICS system. By highlighting resources which contribute most to response time, OMEGAMON II helps you focus your tuning efforts where they will do the most good.

CICS system analysisA CICS system at a typical installation is constantly undergoing change. OMEGAMON II’s CICS system analysis features display control blocks, parameter settings, and status bars that are internal and external to your CICS system. You can inquire on such items as:

n AID/ICE activityn transient data usagen temporary storage usagen CICS table entriesn CICS control blocks

The CICS system analysis displays enable you to monitor the various control areas and tables and take immediate action to improve system performance.

Exception analysisAs tasks on a CICS system compete with each other for resources, problems may occur with the availability of these resources or the performance of the tasks.

OMEGAMON II’s exception analysis feature continually monitors CICS systems for such problems. When a user-specified threshold is met or exceeded, OMEGAMON II alerts you to the problem and enables you to respond to it before availability or performance is degraded.

Response time analysisOMEGAMON II’s response time analysis feature provides displays of CICS internal response time for transactions, terminals, and programs, as well as end-to-end response time for VTAM Logical Units (LUs). OMEGAMON II compares response time against user-specified performance standards for any of these resources or groups of resources.



Storage analysisOMEGAMON II’s storage analysis feature enables you to monitor storage usage in both CICS and MVS and shows you the effects of any adjustments you make. The storage analysis displays are specifically tailored to CICS/MVS and CICS/ESA.

Task analysis (realtime and historical)OMEGAMON II’s task analysis feature monitors currently running CICS tasks and provides an instantaneous display of system activity. As tasks complete, OMEGAMON II saves pertinent resource usage data for online viewing and batch reporting.

OMEGAMON II also includes an historical collection feature that captures CICS system and task-related performance data and then writes it to SMF for batch reporting. The reports you can create include information about response time, task volume, resource usage, your CICS environment, and usage by user ID or terminal.

File/database analysisOMEGAMON II’s file analysis feature reports on file activity within CICS. You can examine:

n files defined to CICS, STEPLIB, JES, DFHRPL, IMS, and journalsn VSAM filesn local shared resource poolsn VSAM string and buffer waitsn DB2 connection statusn DL/I database activity and status informationn third-party database activity

Impact analysisOMEGAMON II’s impact analysis feature identifies other workloads running on MVS that are impacting CICS by competing with it for MVS resources. These workloads can be batch jobs, started tasks, TSO users, or even other CICS regions. The displays not only identify the main sources of impact, but also show how CICS is being affected so you can take immediate action to address those areas that will result in the most significant improvement.

MVS analysisSince MVS factors can influence CICS availability and response time, OMEGAMON II’s MVS analysis feature provides information on such areas as DASD, CPU, paging, and Task Control Block (TCB) structure.



Using the Menu System 35

Using the Menu System

Chapter OverviewThe menu system is OMEGAMON II’s classic interface that provides access to the complete set of OMEGAMON II functions.

Chapter ContentsMenu System Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36Menu System Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37INFO-line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39Menu System Function Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40Menu System Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41Menu System Zooming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42Fast Pathing in the Menu System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Menu System Help Panels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Menu System Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

2

Menu System Main Menu


Menu System Main MenuThe menu system provides a set of menus and menu-driven displays to help you analyze and solve CICS system performance problems. When you enter the menu system, the OMEGAMON II for CICS Performance Monitor System menu, or main menu appears.

FIGURE 2. Menu System Main Menu

Options on the main menu are arranged to reflect the logical order that you may follow when analyzing system problems.

________________ ZMENU VTM $CICSTOR V&OLD./I SYSA 02/03/99 16:57:36> PF1 Help/News/Index PF3 Exit PF18 Color===============================================================================> Enter a selection letter on the top line.> OMEGAMON II for CICS PERFORMANCE MONITOR SYSTEM > W REGIONS ............ List CICS regions, switch monitoring> V OVERVIEW ........... Performance overview> R RESPONSE TIME ...... CICS and end-to-end response time monitoring> E EXCEPTIONS ......... Current system problems and problems this session> T TASKS .............. Task analysis> H HISTORY ............ Historical transaction viewing and selection> B BOTTLENECKS ........ Resource contention (bottlenecks, impacts, enqueues)> S STORAGE ............ Storage summary, violations, DSA, EDSA, PAM, subpools> F FILES .............. CICS datasets, VSAM, LSR, string and buffer waits> D DATABASES .......... DB2 and DLI> C CICS ............... CICS tables and control blocks> M MVS ................ Operating System control blocks for CICS> I I/O ................ DASD performance > U UTILITIES .......... Utility functions and displays> O CONTROL ............ Control options (response time, history, contention)> G GROUPS ............. Group definitions> P PROFILE ............ Profile options and maintenance===============================================================================


Menu System Navigation

Menu System NavigationFrom any menu system panel, you can navigate using PF keys or by entering the letter of an option at the top left (the home position) of the panel.

Most menu system performance displays include horizontal menus. These panels list menu options across the top of the panel and display OMEGAMON II output for the selected option below, in the body of the panel. The figure below shows an example of a panel with horizontal menu options A through H. This is the All Tasks option (A) which is the initial option on the Tasks path (T).

FIGURE 3. Tasks Panel Showing Horizontal Menu

The Control, Utilities, and Profile options on the main menu, however, use vertical menus (menus that list options vertically).

________________ ZTKALL VTM $CICSTOR V&OLD./I SYSA 02/03/99 13:55:51> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-All B-Master C-Waiting D-Over MAXR E-Running F-Other G-Kill H-Rate===============================================================================> ALL TASKS IN SYSTEM TASK+ Number of tasks selected: 28 Skipped: 0+ Tran Task Task Facility Resource Resource CPU+ ID Number State Type=ID Type Name Time+ -------- -------- -------- -------- -------- -------- --------+ CDLI 28444 Suspend Trm=0071 IRLINK DB2EF23 0.004+ EXC1 28443 Suspend Trm=0296 KCCOMPAT TERMINAL 0.000+ EXC1 28440 Suspend Trm=0229 KCCOMPAT TERMINAL 0.000+ CDME 28425 Suspend Trm=0332 IRLINK DB2EF17 0.002+ EXC1 28339 Suspend Trm=0269 KCCOMPAT TERMINAL 0.000+ EXC1 27909 Suspend Trm=0457 KCCOMPAT TERMINAL 0.000+ EXC1 25732 Suspend Trm=0070 KCCOMPAT TERMINAL 0.000+ CSNC 19 Suspend Task IRC CSNCWORK n/a+ CSSY 5 Suspend Task ICMIDNTE DFHAPTIM n/a+ CSTP 2 LastDisp Task TCP_NORM DFHZDSP n/a+ TIdomain None Suspend TIdomain TIEXPIRY DS_NUDGE n/a+ SMdomain None Suspend SMdomain SMSYSTEM (none) n/a+ CSSY 16 Suspend Task JCTERMN SUBTASK n/a+ CSSY 34 Suspend Task KCCOMPAT SINGLE 0.001===============================================================================

Menu System Navigation


FIGURE 4. Profile Panel Showing Vertical Menu

________________ ZPROF VTM $CICSTOR V&OLD./I SYSA 02/03/99 11:15:23> PF1 Help PF3 Exit PF10 Save Profile===============================================================================> Enter a selection letter on the top line.>> PROFILE OPTIONS AND MAINTENANCE > Profile Maintenance> A EXCEPTIONS ....... Set exception analysis thresholds> B CONFIGURE ........ Set default startup configuration> C SAVE/DELETE ...... Save, delete, list profiles > Session Controls> D COLOR ............ Set colors, color mode, intensities> E BACKGROUND ....... Set XLF, ASF, and TSF> F AUTO ON .......... Turn automatic updating on (VTAM mode only)> G AUTO OFF.......... Turn automatic updating off (VTAM mode only)> H LOGGING .......... Log/XLFLOG output options, log on, log off, log print > Altered settings become permanent when you save your profile. To do this,> press PF10/22 from any screen. ===============================================================================


INFO-line

INFO-lineYou enter the selection letter of menu options in the input area of the INFO-line which is the top line of a panel. The following figure shows the INFO-line, which provides status information about your session.

FIGURE 5. INFO-line Format

Note that the symbols for the logging status (LOG), automatic screen facility status (A), and bell status (B) appear on the INFO-line only when those features are in use. Otherwise, the field is blank.

____________________ZMENU VTM LOG APPLID V&OLD./C SYSA 02/03/99 12:21:40 AB | | | | | | | | | | ||Input Area <---‘ | | | | | | | | | || | | | | | | | | | || Screen Name <-‘ | | | | | | | | || | | | | | | | | || Mode of Operation <---‘ | | | | | | | || | | | | | | | || Logging Status <---‘ | | | | | | || | | | | | | || OMEGAMON II applid <---‘ | | | | | || | | | | | || Product Version <---‘ | | | | || | | | | || Profile Suffix <-‘ | | | || | | | || System ID <---‘ | | || | | || Date <---‘ | || | || Time <---‘ || || || || Automatic Screen Facility <-------‘| | Bell Status <--------‘

Menu System Function Keys


Menu System Function KeysThe function keys are standard throughout the menu system as follows:

PF1(PF13) Displays current panel help from a menu or display panel. Displays General Help from any help panel.

PF2(PF14) Undefined.

PF3(PF15) Returns to the previous panel.

PF4(PF16) Reinitializes menu system variables and returns to the main menu.


PF6 Prints current display on the screen log.

PF7(PF19) Scrolls backward.

PF8(PF20) Scrolls forward.


PF10(PF22) Saves currently defined user or installation profile.

PF11(PF23) Zooms to more detail about item displayed at current cursor position.


PF18 Goes to color settings panel (PF3 returns to current panel).

PA2(default) Returns to CUA Interface.


Menu System Colors

Menu System ColorsOMEGAMON II is designed for an extended color terminal. Colors show you which fields are zoomable and highlight the status of key fields:

Colors may be different for the text description of a field and the actual field value. If the text is turquoise and the field is yellow, then the value shown is considered abnormal, but may not be cursor selected with the zoom key. If the text is white, however, then the field may be cursor-selected.

Turquoise text Comment line or non zoomable text.

White text or field Zoomable field.

Blue Number of items selected or skipped.

Turquoise field Normal field value.

Green reverse video Normal status.

Yellow reverse video Warning status.

Red reverse video Critical status.

Turquoise reverse video Idle (no activity).

Menu System Zooming


Menu System ZoomingWhen a large amount of information is available (about tasks or files, for example), menu system panels show only the initial or critical data. To get more information, move the cursor to the item you want more data about and press PF11. This zooms you to another panel where more detail is available.

Zooming is available when PF11 Zoom displays in the PF key line at the top right of the panel. On extended color terminals, zoomable fields are highlighted in white.

To return to the original panel, press PF3.


Fast Pathing in the Menu System

Fast Pathing in the Menu SystemFast pathing provides a quick way to navigate to panels throughout the menu system. At the INFO-line, type the selection letter of each menu and submenu option separated by a period. For example, to go directly to the Transaction Rate panel from any panel, enter T.H (Tasks, Rate) on the INFO-line. Entering T.F.D. (Tasks, Other, DLI) takes you directly to the Tasks Using DLI panel.

From any panel, to go directly to the initial panel of a main menu option, enter the letter of the main menu option followed by a period. For example, to reach the initial panel of the Exceptions option, enter E. on the INFO-line.

Do not enter panel names (such as ZEXCPS) directly; this deactivates menu system variables.

Menu System Help Panels


Menu System Help PanelsOMEGAMON II provides help panels that give you an explanation of the current panel when you press PF1. Help is available when PF1 Help appears on the PF key line at the top of the panel. For example, if you are in an Exceptions panel and you want help, press PF1 to see the following panel.

FIGURE 6. Typical Help Panel

To display the General Help menu, press PF1 again from any help panel.

________________ ZEXCPSH VTM $CICSTOR V&OLD./I SYSA 02/03/99 16:10:28> PF1 Help PF3 Back PF4 Main Menu ========================================================================> CURRENT EXCEPTIONS -- HELP > This display shows the current exceptional conditions in your CICS system.> OMEGAMON is constantly verifying dozens of CICS conditions that may indicate> a potential or real performance slowdown. When such a condition is> recognized, OMEGAMON alerts you by displaying an exception (or warning)> message. > Each exception that OMEGAMON recognizes has a unique name. The exception> name begins in column 3 of the display, to the left of the exception message. > To invoke a recommendation screen that provides an explanation of the> exception and recommendation(s) for responding to it, place the cursor> anywhere on the line displaying the exception and press PF11 to zoom. > Because each installation is different, examine and evaluate the default> thresholds that are provided by Candle. To display and/or change the> thresholds, select the PROFILE option on the main menu.========================================================================


Menu System Help Panels

FIGURE 7. OMEGAMON II General Help Menu

The Index option (A) provides an index of CICS and performance topics. From the Index you can select a topic and navigate directly to its display panel. The Index Usage option (D) tells you how to use the Index.

The News option (B) tells you the highlights of the current release.

The remaining options provide general information about how to use the menu system.

Below the options, there is a list of support center telephone numbers for various locations, if you need assistance.

________________ ZHELPM VTM $CICSTOR V&OLD./I SYSA 02/03/99 17:00:11> PF3 Back PF4 Main Menu > Enter a selection letter on the top line.===============================================================================> GENERAL HELP MENU > A INDEX ................ Alphabetical index of CICS and performance topics> B NEWS ................. What’s new in this release> C MENUS ................ How to use the menu facility> D INDEX USAGE .......... How to use the alphabetical index to get fast paths> E ZOOMING .............. How to get more detail> F EXCEPTIONS ........... Recommendations for resolving exception conditions> G COLORS ............... What do the display colors mean?> H MULTIPLE REGIONS ..... An overview of multiple regions> I PF KEYS .............. PF key settings listing> J COMMANDS ............. How to get help for commands > For more information or to report problems, contact Candle Support: > North America......... (800)328-1811> London ............... (44)(71)734 8292 Paris ........(33)(1)4092-02900> Munich ............... (49)(89)545 540 Sydney .......(61)(2)369-1070===============================================================================

Menu System Displays


Menu System DisplaysBy default, OMEGAMON commands convert a numeric value to xxxK and then to xxxM as the value increases. A field value is not converted if it contains a decimal point or if the field length is less than 4. A value that overflows the field length is displayed as a row of asterisks (******).

Overview Panels 47

Overview Panels

Chapter OverviewOMEGAMON II provides two overviews of CICS information: CICS Regions Summary and Performance Overview. The first panel summarizes activity on all active CICS regions, and if you are using OMEGAMON II in the Menu System, enables you to switch regions that you want to monitor. The second panel provides a snapshot of key CICS performance indicators, alerting you to problems in CICS that require further analysis.

To access this information, select main menu options REGIONS (W) and Overview (V).

Chapter Contents

Displaying CICS Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Performance Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

3

Displaying CICS Regions


Displaying CICS RegionsTo display all the active CICS regions running on the same Central Electronic Complex (CEC) as the current CICS region being monitored, select the REGIONS option (W) on the main menu or enter fast path (W.) from any panel. The region summary appears as in the following figure.

FIGURE 8. Summary of CICS Regions Panel (W.)

This panel only lists regions swapped in. For each active CICS jobname, the panel provides the start date and time, the CICS release, the VTAM application ID, and the total CPU time since region startup. You can use this information to determine which regions are currently available and whether any regions are using excessive CPU time.

If you are using OMEGAMON II in the Menu System mode, this panel also indicates whether you may switch monitoring to another region. The ability to switch monitoring is not supported if:

n the new region is not a supported level of CICS

n you are operating with OMEGAVIEW

See the OMEGAVIEW documentation for additional information.

n the new CICS is not using the same XMIT suffix as OMEGAMON II

See the OMEGAMON II for CICS Configuration and Customization Guide for additional information.

n the global module load for the new region failed

n you have zoomed into the Menu System from the CUA interface

On extended color terminals, colors differentiate the switch status:

n Current region is highlighted in yellow.

n Switchable regions are highlighted in white.

n Non-Switchable regions are turquoise.

________________ ZPLEX VTM $CICSTOR V520/I SYSA 02/04/99 13:09:14> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down ===============================================================================> SUMMARY OF CICS REGIONS ON SAME CEC and SWITCH MONITORING CICS+ CICS Start Start CICS CICS Total Switch+ Jobname Time Date Release Applid CPU Time Allowed+ -------- -------- -------- -------- -------- -------- --------+ TCICS410 10:12:09 02/03/99 4.1 CICS411 194.57 Yes+ $CICSTOR 21:22:31 02/03/99 3.3 $CICSTOR 616.96 Current+ DCICSTOR 21:27:14 02/03/99 3.1.1 DCICSTOR 107.40 No+ DCICSCAN 21:27:58 02/03/99 3.1.1 CICSDB2 222.00 No+ $CICSCAN 21:23:26 02/03/99 2.1.1 $DB2CICS 3750.64 No===============================================================================

Overview Panels 49

Displaying CICS Regions

You can switch monitoring to another region without having to log off the current OMEGAMON II session and log onto a new session. Simply place the cursor on the line describing the region and press PF11 (the zoom key). You will then see the copyright screen for the new session. If the new region is secured, you will also see an entry validation screen with a logon prompt.

Use the REGIONS option at any time to return to monitoring the current region or to proceed to monitor another region.

Performance Overview


Performance OverviewThe Performance Overview panel is a comprehensive display of current CICS system status.

FIGURE 9. Performance Overview Panel (V.)

________________ ZOVER VTM TDOCS15 V520/C SYSG 02/03/99 10:40:01> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ===============================================================================> PERFORMANCE OVERVIEW> For more detail, place the cursor on your choice and press PF11. LEXSY OMEGAMON II for CICS/ESA Exception Analysis+ WSHI Working Set Size = 5332K *HIGH*+ DSIZ Total number of pages in CICS DSA = 256 * LOW*+ MAXP 82% of MAX tasks reached *HIGH*+ STRU File: DEG has 100% of strings in use, tasks waiting = 2 *HIGH*>------------------------------------------------------------------------------ PDEX++ Resource Resource+ Type Name Short Term Information Long Term Information+ -------- -------- ---------------------- ----------------------+ % 0_______ 50_______100 % 0_______ 50_______100+ DISPATCH QR_TCB 2 |> . . . .| 2 |> . . . .|+ EKCWAIT SINGLE 6 |> . . . .| 6 |> . . . .|+ FCIOWAIT *TOTAL* 1 |> . . . .| 1 |> . . . .|+ DEG ( 1) |> . . . .| ( 1) |> . . . .|+ FCPSWAIT *TOTAL* 7 |> . . . .| 7 |> . . . .|+ DEG ( 7) |> . . . .| ( 7) |> . . . .|+ KCCOMPAT CICS 1 |> . . . .| 1 |> . . . .|+ KC_ENQ *TOTAL* 81 |------=======>>> .| 81 |------=======>>> .|+ ...}AITE ( 1) |> . . . .| ( 1) |> . . . .|+ ENQWAIT (81) |------=======>>> .| (81) |------=======>>> .|+ RUNNING RUNNING 1 |> . . . .| 1 |> . . . .|++ Samples . . : 1053 Samples . . : 1053+ Elapsed . . : 6:20 MN Elapsed . . : 6:20 MN+ Interval . : 10:00 MN Interval . : 30:00 MN>------------------------------------------------------------------------------ TASK WAITING+ Number of tasks selected: 28 Skipped: 0+ Tran Task Task Facility Resource Resource CPU+ ID Number State Type=ID Type Name Time+ -------- -------- -------- -------- -------- -------- --------+ DEGV 60 Dispatbl Task DISPATCH QR_TCB 0.895+ CECI 57 Suspend Trm=M489 ZCIOWAIT DFHZARQ1 0.006+ OEN2 44 Suspend Task KC_ENQ ENQWAIT 0.000+ OEN2 43 Suspend Task KC_ENQ ENQWAIT 0.000+ OEN2 42 LastDisp Task EKCWAIT SINGLE 0.001>------------------------------------------------------------------------------ ENQ+ Number of tasks selected: 13 Skipped: 0+ Tran Task Enqueue Owning Owning Owning Owning+ ID Number Resource Tran ID Task No. Res Type Res Name+ -------- -------- -------- -------- -------- -------- --------+ OEN2 43 ENQWAIT OEN2 42 EKCWAIT SINGLE+ OEN2 44 ENQWAIT OEN2 42 EKCWAIT SINGLE

Overview Panels 51


Press Enter to refresh the panel for the latest information. This panel summarizes several of the most important OMEGAMON II features: exception, bottleneck, task, and enqueue analysis.

The overview display is divided into four sections and provides information on the following:

For an explanation of an exception condition and recommendations for resolving it, place the cursor on the exception line and press PF11. To obtain more information about a wait-reason, waiting task, or enqueue resource, move the cursor to the line describing the item and press PF11.

Exception Analysis OMEGAMON II automatically tests dozens of conditions against predefined thresholds and reports any potential problems by displaying a warning message with an exception name. For additional information on the exception analysis feature, see “Exception Analysis” on page 65.

Bottleneck Analysis OMEGAMON II monitors CICS activity and reports on any condition causing CICS to wait. The wait reasons listed here are internal to CICS. Contention caused by other workloads running on this processor are detected by impact analysis and can be accessed by selecting the Bottlenecks option (B) on the main menu. For more information on OMEGAMON II’s bottleneck analysis feature, see “Bottleneck Analysis” on page 135.

Task Analysis A list of all tasks in a wait condition displays automatically. The transaction ID and task number are included as well as the name and type of resource causing the wait. For a list of associated wait reasons, select All Tasks (A) on the Tasks menu or enter T. to fast path, and then press PF1 for Help. For more information on OMEGAMON II’s task analysis feature, see “Task Analysis” on page 89.

Enqueue Analysis Any task holding a resource causing another task to wait is detected and displayed by Enqueue Analysis. The task name and number as well as the name of the resource being waited for is listed. For additional information on the enqueue analysis feature, see “Enqueues” on page 149.



Response Time Analysis 53

Response Time Analysis

Chapter OverviewOMEGAMON II collects, analyzes, and displays CICS response time for predefined groups of transactions, terminals, and programs. It also collects end-to-end response time data for LU groups, if the End-to-End™ (ETE) feature is active.

To collect and analyze response time data, you must define one or more response time groups and their thresholds. You may change one or more groups and their thresholds for the duration of an ongoing OMEGAMON II session or permanently. See “Group Definition and Activation” on page 325 for information on changing response time groups for the duration of a session, and the OMEGAMON II for CICS Configuration and Customization Guide for information on changing them permanently.

When you define response time thresholds, you can raise alert conditions when the response time exceeds those thresholds. These alerts can be communicated to OMEGAVIEW or the exception analysis component of OMEGAMON II. (See “Exception Analysis” on page 65, as well as the OMEGAVIEW User’s Guide for more information.)

Chapter ContentsCICS Transaction Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Response Time Data Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Network Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Response Time Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Fixed time period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Moving time period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58User-defined time intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Response Time Data Collection Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63Time intervals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63Time scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63Time window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

4

CICS Transaction Response Time


CICS Transaction Response TimeThe response time for a transaction is the elapsed time for a transaction or conversation. In CICS/MVS versions, OMEGAMON II uses the CICS Global User Exit facility to determine transaction response time and resource usage. This operates independently of the CICS Monitoring facility to allow you to collect this data with minimal overhead. Each conversation is considered as a separate transaction. The transaction start time occurs when CICS first dispatches the task. The transaction end time occurs when CICS detaches the task. Therefore the delay in waiting for a task to be attached due to a CMXT condition would not appear as part of the response time.

In CICS/ESA, OMEGAMON II uses CICS Monitoring to determine transaction response time. The CONV=YES parameter in the CICS monitor control table (MCT) determines whether records are written for each conversation. For conversational transactions, CICS Monitoring includes the terminal input wait time as part of the conversation’s elapsed time. If you do not want this time included, you can direct OMEGAMON II to remove terminal input/output wait time from its elapsed time. See the CONVTIME operand on the global data area parameter in OMEGAMON II for CICS Configuration and Customization Guide for more information.

In an MRO/ISC environment performing function shipping or distributed program link, each request handled by a mirror transaction may be treated as a separate transaction, depending on the request and, for MRO, the MROLRM SIT parameter setting. Consult the IBM CICS documentation for details of mirror transaction processing.


Response Time Data Status

Response Time Data StatusYou can view the current data collection status of the response time monitor by selecting the RTA Status option (C) on the Control path or entering fast path O.C from any panel. This status display includes the status, start date/time, and current scale and window display options for the response time monitor.

Network Response Time


Network Response TimeThe network response time of VTAM LUs, or end-to-end response time, is the elapsed time between the user’s pressing a key (ENTER, PF1 through PF24, PA1, PA2, PA3 or CLEAR) and receiving a response at the terminal.

In order to capture this data, Candle’s End-to-End Response Time feature (ETE) must be installed at your facility. See the OMEGAMON II for CICS Configuration and Customization Guide for information on installing ETE. ETE places itself inside one of the VTAM SNA layers to measure network response time. In this location, ETE can time all SNA traffic that flows through VTAM. The measured time begins when a request flows through VTAM toward the application; it ends when VTAM receives the definite response from the terminal controller. For detailed information on the capabilities of this feature, see the End-to-End Response Time Feature (ETE) Reference Manual.


Response Time Periods

Response Time PeriodsThere are three ways to view response time data: by fixed time periods, by moving time periods, and by user-defined time periods.

Fixed time periodA fixed time period display shows the average transaction response time and transaction count for specific time periods within the last 24 hours. The time periods are defined in the global data area (see the OMEGAMON II for CICS Configuration and Customization Guide for more information). Statistics appear for a single element, a group of elements, or for all monitored elements.

To display fixed period response time, select the CICS Today option (G) on the Response Time path or enter fast path R.G from any panel. The panel in the following figure displays, showing average response times by daily time slot for each transaction monitored (defined in a transaction group).

FIGURE 10. Transaction Response Times by Intervals Panel (R.G)

On this panel, time periods that start and end later in the day than the current time and that contain transaction counts and response times, represent transactions that ran yesterday.

________________ ZRCICT VTM $CICSTOR V520/I SYSA 02/03/99 10:43:11> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-Overview B-Transactions C-Terminals D-Programs E-VTAM LUs> F-Graphical G-CICS Today H-ETE Today I-Groups Today J-Averages> K-ETE All LUs L-ETE Current M-ETE Exceeded===============================================================================> TRANSACTION RESPONSE TIMES BY INTERVALS> To see later time slots, enter 1 to 9, A, or B preceding CSLT. CSLT | ID | 00:00-08:00 | 08:00-08:15 | 08:15-08:30 | 08:30-08:45 |> | | | | | | time |CD | 0.329 | 0.377 | 0.471 | 0.415 |+ |CDCE | 0.663 | 1.050 | 1.022 | 0.753 |+ |CDDS | 0.227 | 0.330 | 0.398 | 0.262 |+ |CDLI | 1.165 | 1.100 | 1.616 | 1.748 |+ |CDMM | 0.506 | 1.290 | 1.398 | 0.815 |+ |CDNE | 0.902 | | | |+ |CDPA | 0.968 | 0.696 | 1.159 | 1.352 |+ |AVERAGES| 0.304 | 0.361 | 0.518 | 0.427 |> | | | | | | cnt |CD | 192 | 25 | 29 | 25 |+ |CDCE | 4 | 3 | 6 | 6 |+ |CDDS | 150 | 21 | 25 | 25 |+ |CDLI | 300 | 37 | 38 | 48 |+ |CDMM | 20 | 1 | 6 | 7 |+ |CDNE | 2 | | | |+ |CDPA | 24 | 11 | 7 | 6 |+ |TOTALS | 692 | 98 | 111 | 117 |



To display additional time slots, place a number from 1 through 9, or A, or B, in front of CSLT. For example, 1 displays the second group of 4 time slots and A displays the eleventh group of 4 time slots. Specify blank or 0 to display the first 4 time slots.

To display fixed-time periods for a particular group, select the Groups Today option (I) on the Response Time path or enter fast path R.I from any panel. You will then view a display similar to the one shown in the previous figure except that all elements will belong to the group specified.

Moving time periodMoving time periods show the response time within the last ten minutes for ID groups and elements. The data can be displayed numerically or graphically.

Numeric response times

To display an overview of numeric response times as shown in the following figure, select the Overview option (A) on the Response Time path or enter fast path R. from any panel.

FIGURE 11. Groups with Response Time Activity in Last 10 Minutes Panel (R.)

This panel displays the response times for each minute of the last 10 minutes for any ID group that experienced activity during the last 10 minutes. Whenever the response time exceeds the group or element threshold, it appears in reverse video on color graphics terminals as follows:

Turquoise No activity.

Green Below threshold.

Yellow Threshold exceeded.

Red Twice the threshold has been exceeded.

________________ ZRESP VTM $CICSTOR V520/I SYSA 02/03/99 10:41:02> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Overview B-Transactions C-Terminals D-Programs E-VTAM LUs> F-Graphical G-CICS Today H-ETE Today I-Groups Today J-Averages> K-ETE All LUs L-ETE Current M-ETE Exceeded===============================================================================> GROUPS WITH RESPONSE TIME ACTIVITY IN THE LAST 10 MINUTES RESP GROUP+ Number of groups selected: 3 Skipped: 0+ Group Group Curr -1 -2 -3 -4 -5 -6 -7 -8 -9+ Number Type min min min min min min min min min min+ -------- -------- ---- ---- ---- ---- ---- ---- ---- ---- ---- ----+ 01 Tran 1.8 .6 1.1 1.7 .7 .8 1.1 1.1 3.3+ 13 Tran .1 .2 .2 .6 .2 .2 .2 .3 .3 .9+ 25 Tran 1.8 .2 1.1 1.4+ 27 Prog 1.4 .3 1.6 1.5===============================================================================



If a group is composed of LUs, three lines of information are displayed:

You can zoom on a group number for detailed response time information for all elements within that group.

Response time path options B through E. display the last 10 minutes’ response times for the following types of response time:

To display a graphic representation of moving time period response time data as shown in the following figure, select the Graphical option (F) on the Response Time path or enter fast path R.F from any panel.

LU-ETE End-to-end response time, consisting of host plus network response times.

LU-Net Network response time, the amount of elapsed time attributed to sending data between terminal and host.

LU-Host Host response time, the amount of elapsed time as viewed within CICS.

Option B CICS response times for transaction groups.

Option C CICS response times for terminal groups.

Option D CICS response times for program groups.

Option E ETE response times for VTAM LU groups.

Graphical



FIGURE 12. Graph of Response Time Problems Panel (R.F)

This screen shows a moving time slot analysis of response time for elements experiencing response time problems. The vertical scale on the left side represents response time in tenths of a second. The time window at the bottom represents the length of time, in minutes, for which response times are displayed.

The horizontal dashed line for each element represents its threshold setting. The element ID name and the most recent response time for that element are shown at the top of each graph.

Elements appear only if their response time within a defined time window exceeds their response time threshold. A time window starts at the current minute and extends back up to 10 minutes.

In this example, each line on the scale represents 2 seconds. The plus sign (+) highlights elements with response times exceeding the top end of the scale.

When graphing VTAM LUs, the response time for each element is differentiated between the host component (s) and the network component (n) of end-to-end response time.

To display end-to-end response times for monitored VTAM LUs as shown in the following figure, select the VTAM LUs option (K) on the Response Time path or enter fast path R.K from any panel.

End-to-End moving time periods

________________ ZRPLOT VTM TDOCS01 V520/C SYSG 02/03/99 17:01:26> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-Overview B-Transactions C-Terminals D-Programs E-VTAM LUs> F-Graphical G-CICS Today H-ETE Today I-Groups Today J-Averages> K-ETE All LUs L-ETE Current M-ETE Exceeded===============================================================================> GRAPH OF RESPONSE TIME PROBLEMS RSP | PAY1 | KLOC | HOWA | | | |+ | 1.275 | 0.301 | 1.666 | | | |+ |==========+==========+==========+==========+==========+==========++ 2.0|------++--|------++--| + | | | |+ 1.8| ++ | ++ | +*| | | |+ s 1.6| ++ | ++ | +*| | | |+ e 1.4| ++* | ++ | +*| | | |+ c 1.2| ++**| ++ |--------+-| | | |+ o 1.0| ++**| ++ | * +*| | | |+ n .8| ++**| ++* | * +*| | | |+ d .6| ++**| * ++* | * * +*| | | |+ s .4| ++**| * ++**| * ** +*| | | |+ .2| ++**| * ++**| * ** +*| | | |+ +----------+----------+----------+----------+----------+----------++ Tran Tran+ min -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0===============================================================================



FIGURE 13. End-to-end Response Times for LUs Panel (R.K)

This panel shows the end-to-end response times for all VTAM LUs within their defined groups. The fields displayed are:

The panel shows all the ID groups that are associated with LUs. Under the response history, you can see the status for the last 16 intervals. The default interval is one minute. Refer to “Response Time Data Collection Settings” on page 63 for information on changing the time interval.

You can limit this display to LUs in a particular group, those that have activity in the current sample, or those that exceeded the threshold in the current sample. Refer to the help screen using PF1 for more information.

Group/LU Groups and LUs being monitored. You must define LUs in LU group(s) prior to starting the response time monitor.

Response History Status for the current interval and the last 16 intervals. Red bars indicate exceeded thresholds and green dots indicate normal conditions. Refer to “Response Time Data Collection Settings” on page 63 for setting thresholds.

Current Samples Number of samples in the current interval.

Host Response Average host response time in the current interval. This field is red if the host threshold was exceeded during the current interval.

Network Response Average network response in the current interval. This field is red if the network threshold was exceeded during the current interval.

Total Response Average total response in the current interval. This field is red if the total threshold was exceeded during the current interval.

________________ ZRETE VTM TDOCS01 V520/C SYSG 02/03/99 17:02:37> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-Overview B-Transactions C-Terminals D-Programs E-VTAM LUs> F-Graphical G-CICS Today H-ETE Today I-Groups Today J-Averages> K-ETE All LUs L-ETE Current M-ETE Exceeded===============================================================================> ETE RESPONSE TIMES FOR ALL DEFINED LOGICAL UNITS> To display a group summary, enter SUMMARY after ETE. To display LUs for one> group, enter GROUP=nn after ETE. ETE+ Group / Response History Current Host Network Total+ LU 16:00 mn <-- 0 mn Samples Response Response Response+ -------- ----------------- -------- -------- -------- --------+ Group 30 R-D LUS+ CLNT3150 .|...|.||........ 45 0.045 1.020 1.065+ CLNT3151 .....||...|||...| 9 0.670 3.100 3.770+ CLNT3152 ..|....|...|..... 0 0.000 0.000 0.000+ CLNT3153 .........|....... 0 0.000 0.000 0.000+ CLNT3154 ..........|..|||| 10 0.040 2.230 2.270+ Summary 64 0.755 6.350 7.105



To display all VTAM LUs that have end-to-end response times, select the ETE Current option (L) on the Response Time path or enter fast path R.L from any panel. To display all VTAM LUs that have exceeded their thresholds, select the ETE Exceeded option (M) on the Response Time path (fast path R.M).

User-defined time intervalsYou can display the average response time over three overlapping time intervals. These intervals reflect short, medium, and long-term response times. Each interval is expressed in minutes where the medium-term interval is a multiple of the short-term interval and the long-term interval is a multiple of the medium-term interval. Refer to “Time intervals” on page 63 for information on changing the interval length.

You invoke the time intervals display as shown in the following figure, by selecting the Averages option (J) on the Response Time path or entering fast path R.J from any panel.

FIGURE 14. Average Transaction Response Times Panel (R.J)

This panel shows for each interval, the interval length in minutes in parentheses followed by the elapsed time for the interval. The average response time and the number of occurrences for each element ID are shown for all elements having some activity.

Elements can be selected by group number, and you can choose to display only group averages by modifying the time and cnt statements below CRSP. Refer to the help screen using PF1 for more information.

________________ ZRAVER VTM $CICSTOR V520/I SYSA 02/03/99 10:46:35> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-Overview B-Transactions C-Terminals D-Programs E-VTAM LUs> F-Graphical G-CICS Today H-ETE Today I-Groups Today J-Averages> K-ETE All LUs L-ETE Current M-ETE Exceeded===============================================================================> AVERAGE TRANSACTION RESPONSE TIMES> To view averages for just the group specified, enter any group number> directly after ATIME and ACNT. CRSP | ID | (00:15) 00:08:48 | (00:30) 00:23:48 | (01:00) 00:23:48 |> | | | | |Atime |AVERAGES| 0.470 | 0.526 | 0.526 |Acnt |TOTALS | 498 | 1153 | 1153 |===============================================================================


Response Time Data Collection Settings

Response Time Data Collection SettingsThe following settings can be changed from an OMEGAMON II session.

n time intervalsn time scale for moving time periods (Time Scale)n thresholdsn period in moving time period for determining exceeded threshold (Time Window)In order to change any settings, you must first stop collecting response time data. This is necessary to clear any accumulated data. Select the Control option (O) on the main menu and then select the RTA Off option (B) or enter fast path O.B from any panel to deactivate response time analysis. After changing the settings, restart data collection by selecting the RTA On option (A) on the Control path or entering fast path O.A from any panel.

The settings that affect the collection and display of response time data are defined in the global data area. See the OMEGAMON II for CICS Configuration and Customization Guide for information on the global data area.

You can modify a subset of these settings from an OMEGAMON II session. The changes remain in effect for all sessions monitoring that CICS region until you change them or stop OMEGAMON II.

Time intervalsYou can set the time intervals for the short, medium and long-term response time periods as well as the time interval on the end-to-end response time graph by selecting the RTA Intervals option (D) on the Control path or entering fast path O.D from any panel.

Time scaleThe time scale affects the graphical moving time period display. There are 10 points on the vertical axis for this display. The scale represents the time interval in tenths of a second for each point. The allowable range is .1 seconds to 9.9 seconds. Set the time scale by selecting the RTA Scale/Window option (E) on the Control path or entering fast path O.E from any panel. Note that the time scale must be identical for all elements that OMEGAMON II monitors.

ThresholdsID groups and elements within a group have associated response time thresholds. Any occurrences of the threshold being exceeded can be highlighted on the displays. Additionally, an alert can be communicated to exception analysis or OMEGAVIEW.

For LU elements and groups, you can set three thresholds corresponding to the host, network, and total ETE response time.

See “Group Definition and Activation” on page 325 for more information on setting thresholds.

Response Time Data Collection Settings


Time windowThe time window affects the graphical moving time period display. Only those elements that exceed their threshold during the time window are displayed. The window must be identical for all elements that OMEGAMON II monitors.

You specify the window as a number from 1 through 10. For example, if you specify 3, elements are displayed only if their response time exceeds their threshold during the last three minutes. By specifying a value of 10, you include an element if it exceeds its threshold any time during the last 10 minutes.

Select the RTA Scale/Window option (E) on the Control path or enter fast path O.E. to set the time window.

Exception Analysis 65

Exception Analysis

Chapter OverviewOMEGAMON II continually monitors CICS for conditions that may affect resource availability and system performance. When a condition falls outside the range of a predetermined threshold, OMEGAMON II generates an exception and alerts you by displaying a warning. If you need help remedying the problem noted by the exception, you can access an OMEGAMON II recommendation screen that suggests the appropriate actions to take.

Although OMEGAMON II exceptions are shipped with default settings, you can customize them by individually adjusting thresholds, changing display characteristics, and disabling specific exceptions. Changes such as these can be saved, and either shared across sessions, or retained in a separate profile for specific users.

Exceptions can generate color-coded alerts for OMEGAVIEW and the Region Status panel of OMEGAMON II. Refer to the OMEGAVIEW User’s Guide and the OMEGAMON II for CICS User’s Guide for more information.

Two other OMEGAMON II features, the exception logging facility (XLF) and the automatic screen facility (ASF), provide automatic handling of exceptions. Refer to the OMEGAMON II for CICS Configuration and Customization Guide and “Background Facilities (ASF, TSF, XLF)” in Volume 1 of this manual for more information.

Chapter Contents

Displaying Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Current exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66OMEGAMON II session exceptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67Exception recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Global CPU Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69CICS Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70Customizing Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

DISPLAY parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84THRESHOLD parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85XLF parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85Box parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86CYCLE parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

VSAM Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

5

Displaying Exceptions


Displaying ExceptionsYou can display exception information for two types of exceptions:

n those that are presently occurring

n those that took place during your OMEGAMON II session

You can customize each exception message for characteristics such as color, highlighting, whether it generates an audible alarm, and others. See “Customizing Exceptions” on page 83 for details.

Current exceptionsFor current exceptions, select the Exceptions option (E) on the main menu or enter fast path E. from any panel. An example of the exception messages displayed appears below.

FIGURE 15. Current Exceptions Panel (E.)

Each exception is identified by a unique 4-character name beginning in column 3 of the display. For a list of all possible exceptions, see “CICS Exceptions” on page 70.

The above display shows four exceptions:

If no current exceptions were triggered, OMEGAMON II displays a message to that effect.

XTOD A boxed message warns that the CICS time of day clock is not being updated. This indicates that a task may have gone into a loop and that the CICS task dispatcher is not getting control.

AMXT The system is at active max tasks.

CPHI The CPU rate of the CICS address space is unusually high.

VCIS The “PAYMSTR” VSAM file has undergone a period of high activity; it had 10 CI splits during the last 2 minutes.

________________ ZRETEC VTM TDOCS10 V520LF SYSG 02/03/99 15:24:50 > PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Current Exceptions B-Exceptions this Session===============================================================================> CURRENT EXCEPTIONS> For a recommendation, place the cursor on the exception line and press PF11. LEXSY OMEGAMON II/CICS Exception Analysis+ XTOD ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + CICS Time Of Day not being updated - CSACTODB = 15:24:49.41 ++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ AMXT System at ACTIVE max tasks+ ACTIVE max tasks exceeded: AMAXT = 10, active =10+ CPHI CPU rate = 89.00% *HIGH*+ VCIS VSAM exceptions (VCIS) for the last 2 minutes+ File ‘PAYMSTR’ (DATA) had 10 CI splits *HIGH*



OMEGAMON II session exceptionsFor exceptions that occurred during your OMEGAMON II session, select the Exceptions this Session option (B) on the Exceptions path or enter fast path E.B from any panel. An example of this display appears in the following figure.

FIGURE 16. Summary of Exceptions this Session Panel (E.B)

This screen provides a summary of all exceptions that occurred during this OMEGAMON II session, displaying their worst value and their most recent value. The fields that compose the Exceptions Summary screen are:

Name Four-character identifier for the exception. See “CICS Exceptions” on page 70 for a list of all possible exceptions.

Last Value Value at the time the last exception occurred.

Last Occurrence Date and time of the last occurrence.

Worst Value Value of the worst occurrence during your session.

Worst Occurrence Date and time of the worst occurrence.

________________ ZEXTRP VTM CICSP01 V520./I SYSA 02/03/99 15:53 28 > PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Current Exceptions B-Exceptions this Session ================================================================================= > SUMMARY OF EXCEPTIONS THIS SESSION > For a recommendation, place the cursor on the exception name and press PF11. TXTRP + Name Last Value Last Occurence Worst Value Worst Occurence + CPHI 77.33% 08/15 15:53:07 99.31% 08/15 4:12:07 + ESIZ 384 08/15 15:53:07 384 08/15 5:53:07 + GRSP 08/15 15:53:07 08/15 5:53:07 + OSCH 1556K 08/15 15:53:07 1556K 08/15 5:53:07 + RMTH 0% 08/15 15:53:07 0% 08/15 5:53:07 + STRU 100% 08/15 15:52:24 100% 08/15 5:52:24 + WSHI 2940K 08/15 15:53:07 3240K 08/15 5:33:41 =================================================================================



Exception recommendationsException recommendations are panels that provide advice or the causes and possible resolutions for exception conditions. Each recommendation provides an explanation of the exception condition and suggests ways to diagnose and/or resolve the problem causing the exception. In addition it enables you to modify the threshold settings for the exception without having to navigate to another panel.

To access an exception recommendation display, place the cursor on the line containing the 4-character exception name and press PF11. The following figure shows an example of a recommendation screen for the exception VCAS, VSAM CA splits.

FIGURE 17. Exception Recommendation Panel (Accessed by Zoom)

_______________ ZXVCAS VTM CICSP1 V520./I SYSA 02/03/99 15:56:58 > PF3 Back PF4 Main Menu PF7 Up PF8 Down ============================================================================= > VCAS -- CA SPLITS HAVE EXCEEDED 1 SINCE LAST VSAM CYCLE > Explanation: > This message displays the number of times a file has incurred a Control > Area split (CA Split) since OMEGAMON II last updated its counters which is > 9. > Recommendation: > 1) Reorganize the file as soon as possible. > 2) If splits continue to occur at a frequent rate, consider redefining the > FREESPACE options to reduce split activity. > Background information: > The VSAM command will display the total number of CA splits incurred since > the file was last reorganized. > Settings: > To change VCAS threshold settings, enter the new values over the current > settings below. To make changes permanent, save your OMEGAMON II profile. =================================================================================


Global CPU Threshold

Global CPU ThresholdException analysis detects when CICS transactions exceed a specified CPU time threshold. Unlike other exception thresholds, this one is defined globally for all sessions monitoring a CICS region. To display or change the global resource limit CPU threshold as shown in the following figure, select the MAXR option (K) on the Exception Settings path (under the Profile menu) or enter fast path P.A.K from any panel.

FIGURE 18. Global Resource Limit Panel (P.A.K)

The CPU threshold is specified in seconds. A value of 0 deactivates CPU exception reporting.

CPU exception reporting is in effect for all transactions in your system, except for program names beginning with DFH. Measurement reporting takes effect for all transactions or conversations that start after MAXR is activated.

The threshold you set is in effect for the duration of your session. I is not saved when you save your profile. To permanently change the threshold, see the chapter on the Global Data Area in the OMEGAMON II for CICS Configuration and Customization Guide.

________________ ZXSET11 VTM $CICSTOR V520./I SYSA 02/03/99 16:17: 5> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF10 Save > A-Database B-I/O C-Task D-Terminal E-OMEGAMON II F-MVS> G-Storage H-TD/TS I-VSAM J-CICS K-MAXR L-All Clear===============================================================================> GLOBAL RESOURCE LIMIT > To change the global resource CPU time limit, enter a value (0 - 3276> seconds) over the current one. 0 deactivates global CPU monitoring.> For more information about the MAXR exception, place the cursor on the> line with MAXR statement anywhere beyond column 5 and press PF11. MAXR: CPU = > This setting is in effect for the duration of this session. It is not saved> when you save your profile. You can define a MAXR value to be used in> subsequent sessions, by reassembling the global module. > To specify whether or not this exception of exceeding the specified response> threshold should display, enter ON or OFF, after STATE=. XACB LIST=MAXR: MAXR+ DISPLAY Parameters: THRESHOLD Parameters: XLF Parameters:: State=ON Threshold=N/A Auto=OFF: Group=KC Display=CLR1 Log=OFF: Bell=ON 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=============================================================================

CICS Exceptions


CICS ExceptionsFollowing is an alphabetical list of OMEGAMON II exceptions:

AIDs The number of AIDs (Automatic Initiate Descriptors) is high.

An AID is created in CICS when a task issues a request for the use of a terminal. The terminal can be a physical terminal or a system.

AMXP Percent of AMAXTASKS that are currently active.

The limit tested by AMXP analysis is the maximum number of active tasks set by the AMAXTASKS option of the master terminal transaction or by the AMXT parameter of the SIT.

The analysis checks the number of active tasks in the system against the AMAXTASKS value, and displays a message when the percentage is greater than the threshold you specify.

Note: This exception is not valid in CICS Version 4.

AMXT Tasks at or over AMAXTASKS.

AMXT analysis checks the current number of active tasks against the AMAXTASKS number. Whenever CICS is at AMAXTASKS, if there is not an ongoing stall situation, any new transactions being entered are started but suspended. At this time, CICS users can notice a delay in the CICS response time. The limit imposed by AMAXTASKS is meant to prevent stall situations where too many tasks strain the use of CICS resources.

In a heavily loaded system, more tasks may be in the dispatcher active chain than specified by AMXT. When this occurs, those tasks on the active chain beyond the AMXT point are not considered for dispatch, even if they are ready to run.


CMXP Class max task threshold exceeded.

Like AMXP, CMXP analysis computes the percentage of active tasks in a class against the limit specified in the SIT, through RDO, or through the master terminal transaction, and compares that percentage with the CMXP threshold specified.

CMXT The system is at class max task.

The number of tasks that belong to a transaction class is equal to the limit for that transaction class. There may also be tasks waiting to b attached. If this message appears consistently, it means that tasks defined in a class are not initiated because Class Max Tasks (CMXT= in SIT) has been reached. CMXT limits the number of concurrent tasks within a defined transaction class.

CPHI CPU utilization is high.

This CPU utilization is the fraction of the total CPU used by the address space over the last OMEGAMON II cycle.

CPLO CPU utilization is low (< n%).

This CPU utilization is the fraction of the total CPU used by the address space over the last OMEGAMON II cycle.


CICS Exceptions

DBMN DLI DB monitor is active.

The DB Monitor has high overhead and can potentially impact both DLI and CICS performance.

DBON Monitored CICS region is not attached to DB2.

DBUP CICS is attached to DB2 during shutdown processing.

If DB2 is not detached before or during shutdown, CICS hangs and shutdown processing stops.

DB21 Current RCT entries with insufficient threads.

When the percentage of threads currently in use exceeds the threshold percentage, OMEGAMON II generates a message. If the thread use count exceeds the number of dedicated threads, OMEGAMON II displays a count of the waiting tasks. Only the first RCT entry in a group entry will appear. The thread pool is treated as RCT entry ID POOL.

If you specified TWAIT=POOL in the RCT entry, the RCT entry may be using pool threads. In this case, the message will be tasks overflowed to pool = n. The RCT entry is ignored if it has no dedicated threads.

DB22 Percentage of RCT entries with significant thread waits since CICS started.

DB22 produces a message when the number of waits and rollovers compared to the number of requests for threads exceeds the percentage threshold you set for any RCT entry. Only the first RCT entry in a group entry will be displayed. The thread pool is treated as RCT entry ID POOL.

If you specified TWAIT=POOL in the RCT entry, it may be rolling over to use pool threads. In this case, the message will read overflowed to pool. An RCT entry is ignored if it has no dedicated threads.

DB2A Percentage of abending DB2 transactions.

The percentage of transactions that abend while holding a DB2 thread.

DB2M Maximum active threads per RCT entry is high.

The maximum active threads limit for an RCT entry is defined in the DSNCRCT table. It is not detrimental to achieve a high percentage of use of the maximum active thread limit. However, when the ratio frequently nears 100%, you should revise the thread assignment for this transaction in the DSNCRCT. Choose the DATABASE path to view the current thread limits for the RCt entry.

DB2T Percentage of DB2 threads in use per RCT entry is high.

If this situation occurs frequently, it indicates that the number of maximum active threads defined (THRDA in the DSNCRCT) is not adequate for the volume of the DB2 activity.

DB2W Percentage of waits per DB2 RCT entry is high.

The percentage of DB2 tasks having to wait for a thread to become available is greater than expected. The level of DB2 requests for the tasks with this RCT entry is greater than the current number of maximum active threads. If this situation occurs frequently, it indicates that the number of maximum active threads defined (THRDA in the DSNCRCT) is not adequate for the current volume of this RCT entry.

CICS Exceptions


DLCL The CICS Database Control facility for IMS (DBCTL) is inactive.

Use the CICS transaction CDBC to initiate the connection.

DLDB Number of DMBs that stopped or failed initialization > nn.

DLPB Number of unavailable local PSBs > nn.

DLTH DLI threads in use > nn. If 100% utilization is reached, DLTH analysis displays how many tasks are waiting for threads to become available.

DMBP DMB pool utilization > nn.

This storage pool is acquired from the CICS dynamic storage area and should be specified large enough to accommodate all DMBs used in CICS, including shared databases. If the pool is not large enough, an operating system close/open of databases may become necessary to service new database requests.

DNRS DASD devices not responding.

The performance of a telecommunications system such as CICS is highly dependent on the timely completion of I/O requests. DNRS analysis produces a message if an I/O issued to any DASD device allocated to CICS takes longer than one OMEGAMON II cycle to complete. Suppose, for example, that CICS issues an I/O against device CICS02, which is currently RESERVEd by another CPU. If DNRS analysis sees this same I/O waiting for the device two OMEGAMON II cycles in a row, it produces a warning message.

When the I/O finally completes, the message is removed. Note that a RESERVE can only be stated as a possible reason for the delay; it could also be head-of-string contention, since MVS I/O architecture makes it impossible to distinguish between the two. However, if a delay lasts long enough for DNRS to report, it is likely to be shared DASD contention.

DNRS also detects a problem if CICS tries to issue an I/O to a device that has dropped ready. Note that DRDY exception analysis would also produce a message in this case.

Please note that a problem cannot be spotted unless the I/O takes longer than one OMEGAMON II cycle.

DPRO OMEGAMON II dispatching priority is lower than CICS.

DRDY DASD devices are dropped ready.

DRDY analysis produces a warning message if any DASD device allocated to CICS enters the dropped ready state. If any I/O was in progress on this device at the time of failure, the DNRS exception shows the cylinder address.


CICS Exceptions

DSAV Number of pages available before SOS for any DSA below the 16M line.

CICS can have more than one DSA depending on the release. The names of the DSAs that are part of the exception message are as follows:

DSA For CICS releases 2.1.2 through 3.2.1, the area below the 16M boundary.

CICS DSA For CICS release 3.3, the area below the 16M boundary for CICSKEY storage.

USER DSA For CICS release 3.3, the area below the 16M boundary for USERKEY storage.

EDSA For CICS release 3.2.1, the area above the 16M boundary.

CICS EDSAFor CICS release 3.3, the area above the 16M boundary for CICSKEY storage.

USER EDSAFor CICS release 3.3, the area above the 16M boundary for USERKEY storage.

READ ONLY EDSAFor CICS release 3.3, the area above the 16M boundary used to load reentrant programs.

DSAV produces a warning when the number of pages available in the dynamic storage area is less than the specified threshold.

If the amount of available storage is insufficient to satisfy a GETMAIN request, CICS can go short-on-storage. This will seriously impact currently active transactions until enough storage is freed, either voluntarily by CICS transactions or by CICS purging transactions.

Set the DSAV threshold so that it is only tripped when the number of available pages before SOS is critically small. Change the region size parameter for the CICS address space, or limit the maximum number of tasks that can execute concurrently. If your CICS system is under hardware restraints, assigning a unique class to transactions that require an unusually high number of pages may be a good choice to minimize the possibility of CICS going short-on-storage.

If the GETMAIN that tripped this exception also caused an SOS condition the available page count is negative, displaying the amount of storage cushion used.


CICS Exceptions


DSHI Utilization is high for any DSA below the 16M line.

DSHI analysis produces a message when the utilization percentage of the DSA or DSALIMIT is greater than the user specified threshold.

In versions prior to CICS Version 4, DSHI computes utilization on the number of pages available plus the size of the storage cushion. High utilization is likely to become a CICS short-on-storage condition, especially if the storage cushion has already been broken into because of previous short-on-storage situations.

In CICS/ESA Version 4, DSHI computes utilization on the amount of storage either unallocated, or in extents which have no pages allocated. High utilization indicates that a DSA may be unable to extend, therefore leading to a CICS short-on-storage condition.

The measures described for the DSAV section also apply to situations where the DSHI exception is tripped.

For information on the various types of DSAs, see the DSAV exception.

DSIZ Total size analysis for the DSA below the 16M line.

DSIZ verifies that the total size of the DSA is within the user-specified threshold.


DSLO Utilization is low for any DSA or the DSALIMIT below the 16M line.

DSLO analysis produces a message when the utilization percentage of the DSA or DSALIMIT is less than the user-specified threshold.

In versions prior to CICS/ESA Version 4, DSLO computes the storage utilization percentage for each DSA on the number of pages available plus the size of the storage cushion. The DSLO exception is useful for monitoring over-allocation of storage. In CICS/ESA Version 4, DSLO computes utilization on the amount of storage either unallocated, or in extents which have no pages allocated.

For information on the various types of DSAs which this exception applies to, see the DSAV exception.

DSTO Storage available for DSAs to extend is low.

DSTO produces a message when the amount of storage available for CICS to extend a DSA below the line is less than the user-specified threshold. Set the DSTO threshold so that is only tripped when the available storage before SOS is critically small. Change the DSALIMIT parameter for the CICS address space to increase the storage available to CICS.

Note: The DSTO exception applies only to CICS/ESA Version 4 systems.

DUMP CICS is requesting a system dump.


CICS Exceptions

DXAB Bottleneck analysis abended.

The Bottleneck Analysis task monitors CICS tasks at a predefined interval of time. If during a task scan bottleneck analysis encounters an unusual situation, it may abend and, depending on the circumstances, stop its analysis.

When this message appears, select the Utilities option (U) on the main enu and then the Debug option (O) or enter fast path U.O from any panel. Follow the instructions that appear on the screen. You may then restart the bottleneck analysis collector by selecting the Control option (O) on the main menu and then the Bottleneck Ctl option (I) or by entering fast path O.I from any panel. For help in determining the cause of the abend, contact Candle Support Services.

ENQC The number of enqueue conflicts (number of tasks that are waiting or enqueues) is high. Task wait time, due to enqueues, may be responsible for slow response time and can affect CICS availability. By noting the frequency and number of waiting tasks to an enqueued resource, you may identify bottlenecks in your system. For example, specifying recovery that is not necessary increases task waits from enqueues on recoverable resources and system log I/O.

ENQP PI enqueue pool utilization > nn.

The maximum amount of storage that can be used is set by the ENQPL parameter of the SIT. PI enqueue pool storage is GETMAINed out of OSCOR, and a transaction that cannot be serviced because of an OSCOR shortage, or because the ENQPL maximum has been reached, is abended with a U775.

For IMS 1.3 and above, if IRLM is active (DLIRLM=YES specified in the SIT) this exception is bypassed. The IRLM address space contains the program isolation enqueue pool.

ENQW The number of tasks waiting for a particular enqueue is high.

Task wait time, due to enqueues, may be responsible for slow response time and can affect CICS availability. By noting the frequency and number of waiting tasks to an enqueued resource, you may identify bottlenecks in your system. For example, specifying recovery that is not necessary increases task waits due to enqueues on recoverable resources and system log I/O.

ESAV Number of pages available before SOS for any DSA above the 16M line.

See the DSAV exception for further information.

ESHI Utilization is high for any EDSA or EDSALIMIT.

See the DSHI exception for further information.

ESIZ Total size analysis for any DSA above the 16M line.

See the DSIZ exception for further information.


ESLO Utilization is low for any EDSA of the EDSALIMIT.

See the DSLO exception for further information.

CICS Exceptions


ESOS CICS short-on-storage message for any DSA above the 16M line.

See the XSOS exception for further information.

ESTO Storage available for EDSA’s to extend is low.

See the DSTO exception for further information.

GRSP Response time for any element within a group exceeds its threshold.

Elements can be transactions, programs, terminals, or VTAM LUs. For information on defining elements in groups and specifying their thresholds, see “Group Definition and Activation” on page 325.

ICES The number of ICEs (Interval Control Elements) in CICS is high.

An ICE is created in CICS when a task issues a timer dependent request to create a new task or resume its own execution.

INAB Interval Record collector subtask abended.

When the message appears, select the Utilities option (U) on the main menu and then the Debug option (O) or enter fast path U.O from any panel. Follow the instructions that appear on the panel. You may then restart the Interval Record collector by selecting the INTR option (K) on the Control path or entering fast path O.K from any panel. For help in determining the cause of the abend, contact Candle Support Services.

INAB Interval Recorder stopped SMF error.

For help in determining the reason that INTR stopped, add DEBUG to the INTR command (start from option O.K). Look for the message:

INTR ERROR RETURN FROM SMFWTM MACRO, CODE=rrrrrrrr

where rrrrrrrr is the SMFWTM return code as detailed above.

IOHI CICS I/O rate is high.

IOHI analysis produces a warning when the I/O rate for the CICS address space is greater than the user-specified threshold of n EXCPs per second. This I/O rate is calculated as the number of EXCPs issued by the region over the last OMEGAMON II cycle (default = 10 seconds in automatic update mode) divided by the length of the cycle.

JCJS Journals are waiting for a valid WTOR response.

This exception trips when a WTOR response is needed and none has been issued by the operator, or when a response has been issued but it is not what CICS is expecting.

LSQA Largest contiguous LSQA area is smaller than the threshold specified in nKs of storage.


CICS Exceptions

MAXP Percentage of MXT exceeded threshold.

The MXT parameter of the SIT allows you to specify the maximum number of tasks that can be initiated in CICS. Use MXT instead of AMXT for systems which are predominantly pseudo-conversational.

Task initiation requests from a terminal are queued in VTAM and use little or no CICS resources, while AMXT tasks are queued within CICS. The IBM CICS Performance Guide explains the use of this parameter in more detail and gives guidelines to determine what its setting should be.

MAXP analysis computes the percentage of initiated tasks against the MXT limit and compares the percentage with the threshold specified for MAXP.

MAXR Tasks over the threshold for CPU consumption.

The MAXR exception displays all tasks currently over the global resource threshold for CPU consumption.

MAXT Number of executing tasks is at or over the MXT limit.

Whenever CICS goes into a max task situation, the terminal control program does not attach new tasks resulting from transactions entered at a terminal. However, the task control program does not stop honoring attach requests from tasks already running. This may cause the number of initiated tasks to exceed the limit specified in the SIT with the MXT= parameter, or the limit set with the MAXTASKS option of the master terminal transaction. When this is detected by MAXT analysis, OMEGAMON II displays a message.

NDMP More than nn transaction dumps generated.

OSCH Contiguous OSCOR area is high.

OSCH analysis produces a warning message when the largest contiguous OSCOR area is larger than the size in Ks specified as the threshold. This exception can help you tune the amount of OSCOR that needs to be allocated when CICS starts up.

OSCL Contiguous OSCOR area is low.

OSCL analysis computes the largest contiguous OSCOR area and produces a message when the size of the area is less than the threshold. Once the largest contiguous OSCOR area is smaller than the threshold, restrict all dynamic file open/close activities to an absolute minimum, since that is the major cause for OSCOR fragmentation. Eventually, depending on how small the largest area is, it may be impossible to open or close any files, causing loss of functions in your CICS system.

CICS Exceptions


PAGE Page-in rate per second is high.

The CICS private and common area page-in statistics are sampled, during each OMEGAMON II cycle, and a rate of page-ins per second computed. PAGE analysis compares the rate against the PAGE threshold and produces a message if the threshold is exceeded.

A page-in can cause the CICS job to wait for the page fault to resolve. Any delay during this process, regardless of the cause, degrades response time for all CICS tasks.

I/O contention on the paging string or volume, excessive paging activity by any job in the system, or simply a shortage of real memory affects the paging subsystem and may cause severe degradation.

PAGE analysis, together with device not-ready/dropped-ready analyses, can provide a timely evaluation of the cause of excessive paging or slow page fault resolution.

PCRT Program compression rate per minute. This exception is valid only for CICS/MVS.

PSBP PSB utilization > nn.

The PSB (Program Specification Block) storage pool is acquired from the CICS dynamic storage area. It should be specified large enough to accommodate all PSBs used in CICS, including shared databases. If the pool is not large enough, operating system close/open of databases may become necessary to service new database requests.

RMTH MRO/ISC links in use > nn%.

RMTT Waits for MRO/ISC links > nn.

SDMP More than nn system dumps generated.

SRHm Active strings for CICS LSR pool m > nn%.

The value of m may be 1–8.

SRLM The buffer lookaside ratio for an LSR pool m < nn%

VSAM read requests that are satisfied without initiating I/O because the CI was already resident in the buffer pool are considered successful lookasides.

SRTm String waits for CICS LSR pool m > nn.

The value of m may be 1–8.

STIO Percentage of I/Os waiting for strings exceeds threshold.

STIO computes the percentage of I/O requests issued for a file that are waiting for strings to be available.

STRU Percentage of strings in use per file is high.

STRU issues a message when the string utilization for a VSAM file exceeds the user-specified threshold.


CICS Exceptions

STRW Total number of string waits per file is high.

When all strings for a file are in use, new requests against it are queued until a string is released. String waits by many concurrent tasks may eventually lead to new tasks being forced to wait on the active max task limit. Some string waits for a file may be inevitable, but they should be monitored so as not to cause extreme situations in CICS.

STRW produces a message when the number of string waits for a file exceeds the user-specified threshold.

STRX Current number of string waits per file is high.

This value reflects the number of tasks that are now waiting for a string.

SVSY Storage violations total > nn.

Storage violations can become the cause of many problems in CICS, including errors in management modules a long time after the storage violation is detected. The first tool in eliminating them is complete application testing. Once a transaction enters the production environment, debugging after the fact (and probably after the transaction that incurred the violation is long gone from the system) is a difficult task.

Because of the potential damage to system availability, dependability, and data integrity, storage violations must be eliminated as quickly as possible from a production system. Their impact is also felt in response time because of the necessity to enter storage recovery and, in some cases, the time it takes to produce a storage violation dump.

SVSY produces a message when the number of terminal and/or transaction storage violations exceeds the threshold.

The first line of the display is identical to the output from the SVTK exception, and the second line is identical to output from the SVTR exception.

SVSY trips if the total count from either the PCT or TCT storage violation counter exceeds the SVSY exception threshold.

Note that CICS increments both the PCT and TCT storage counters for a single violation when appropriate, so the total number of violations may be less than the sum of the two figures. Once a storage violation has been detected, CICS integrity is suspect.

Note: Once a storage violation has occurred, SVSY causes both the PCT and the TCT to be scanned, which increases overhead. Use SVSY with caution. You may use the Storage Exception Settings panel (fast path P.A.G) to reset exception thresholds if you have frequent storage violations.

SVTK Storage violations per transaction > nn.

SVTK displays a message when the number of storage violations caused by any one transaction exceeds the user-specified threshold.

Important: Once a storage violation has occurred, SVTK causes the PCT to be scanned, which increases overhead. Use SVTK with caution. You may use the Storage Exception Settings panel (fast path P.A.G) to reset exception thresholds if you have frequent storage violations.

CICS Exceptions


SVTR Storage violations per terminal > nn..

SVTR displays a message when the number of storage violations associated with any one terminal exceeds the user-specified threshold.

Note: Once a storage violation has occurred, SVTR causes the TCT to be scanned which increases overhead. Use SVTR with caution. You may use the Storage Exception Settings panel (fast path P.A.G) to reset exception thresholds if you have frequent storage violations.

TDBU Percentage of transient data buffers in use >nn%.

TDBW Number of current transient data buffer waits >nn.

This exception indicates that the number of transient data buffer waits exceeds the threshold.

TDCI Percentage of transient data CIs in use > nn%.

This exception indicates that the percentage of transient data CIs in use exceeds the threshold.

TDHI Transient data queue over trigger level.

TDHI checks the length of each intrapartition destination and compares it with its trigger level (if the level is nonzero). If the number of records in the queue exceeds the trigger level by more records than specified in the TDHI threshold, a message is produced.

TDQU Transient data queue records > nn.

TDQU checks the queue level on each intrapartition destination against the TDQU threshold and displays a message when the number of records in the queue is greater than the threshold.

TDSH Active strings for transient data > nn%.

TDST Total string waits for transient data > nn.

TNRS Tape device not responding to I/O request.

TNRS analysis produces a warning message if an I/O issued to any tape device allocated to the CICS address space takes longer than one OMEGAMON II cycle to complete. Suppose, for example, that a CICS log tape I/O was issued against device 631 and another tape drive on that string is in the middle of a long burst of chained I/O. If TNRS sees the same I/O waiting for the device two OMEGAMON II cycles in a row, it produces a warning message. When the I/O finally completes, the message is removed.

TNRS also detects a problem if CICS tries to issue an I/O to a device that has dropped ready. Note that TPDR exception analysis also produces a message in this case.

TPDR Tape device dropped ready.

TPDR analysis produces a warning message if any tape device allocated to the CICS address space enters the dropped ready state. Note that if any I/O is in progress on this device at the time of failure, the TNRS exception probably produces an additional warning naming the current user.


CICS Exceptions

TRLO The total transaction rate is low.

A low transaction rate may be a symptom of a short-on- storage condition, bottleneck, or other CICS problem.

The transaction rate is calculated per second or per minute depending on the UNIT specified on the RATE command.

Verify whether CICS task limit settings have been set too low: max tasks, active max tasks, and class max tasks.

TSBU Temporary storage buffers in use >nn%.

TSBW Temporary storage buffer waits >nn.

TSPU Auxiliary temporary storage percent utilization > nn%.

If auxiliary storage is exhausted, severe degradation of CICS performance occurs. This exception may indicate that the temporary storage dataset is closed to being filled.

TSPU computes the percentage of control intervals used in the temporary storage dataset and displays a message when the percentage exceeds the user-specified threshold.

TSSH Active strings for temporary storage > nn%.

TSST Total string waits for temporary storage > nn.

VCAS CA splits are high.

VSAM split/extent analysis checks the VSAM files allocated to the CICS task every nn minutes, as defined by the XVSC command. If a file has incurred control area splits over the threshold specified in VCAS, a message is displayed.

VCIS CI splits are high.

Control interval splits are monitored by VCIS analysis, on every cycle, as defined by the XVSC command.

VINX Index component splits/extents.

Index split/extent analysis is monitored by VINX analysis, on every cycle, as defined by the XVSC command.

VINX checks for any occurrence of CA splits, CI splits, or new extents incurred by an index object. When one of these is detected, VINX analysis displays a message.

VMEX Extensions per file.

Extent analysis is monitored by VMEX, on every cycle, as defined by the XVSC command.

VMEX produces a message when a new extension is detected for a VSAM file, also showing the current total number of extents.

VTMA VTAM ACB not open message.

CICS Exceptions


WSHI Working set size > nK.

WSHI analysis produces a warning when the working set size for the CICS address space is greater than the user-specified threshold of nK (where 1K = 1024 bytes). The working set size is defined as the number of central storage pages the region currently has in memory.

WSLO Working set size < nK.

WSLO analysis produces a warning when the working set size for the CICS address space is less than the specified threshold of nK. Working set size is the number of real pages the region currently has in memory.

XRFA Alternate XRF system is not active.

XSOS CICS short-on-storage message for any DSA below the 16M line.

The short-on-storage situation in CICS degrades your CICS response time. Tasks may be abended due to the stall interval having elapsed.

Avoid the short-on-storage situation by monitoring DSA utilization and using CICS limit parameters.

For information on the various types of DSAs, see the DSAV exception.

XTOD CICS Time of Day (T.O.D.) clock is not updated.

When a task goes into a loop and the CICS task dispatcher does not get control, the CICS time of day clock field in the common system area is not updated by task control.

XTOD verifies that the CSA time of day field changes every OMEGAMON II cycle; if not, a message is displayed.

Note that when monitoring a CICS that is not heavily used, the XTOD message can appear as a result of the user causing OMEGAMON II to cycle more than once during the CICS exit interval (ICV).


Customizing Exceptions

Customizing ExceptionsThe exception parameters you can customize appear in the following sections.

When you change any of these settings, they remain in effect for the duration of your session. If you save them in your profile, they will be available for subsequent sessions that use the same profile. For more information on user-defined profiles, see OMEGAMON II for CICS Configuration and Customization Guide.

To customize an exception, select the Exceptions option (A) on the Profile menu (main menu option P) or enter fast path P.A from any panel. Then, follow the instructions on the panel to display the current settings for the exception you want. In the following figure, the settings for the DBON exception are displayed.

FIGURE 19. Database Exception Settings Panel (P.A)

To change an option, enter a new value over the displayed value. If you want to change another exception, enter the 4-character exception name after XACB LIST=.

You can select another exception category from the options on the horizontal menu. Each option lists all the exception names and their descriptions belonging to that category.

________________ ZXSET1 VTM TDOCS01 V520./C SYSG 02/03/99 11:17:03> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF10 Save > A-Database B-I/O C-Task D-Terminal E-OMEGAMON II F-MVS> G-Storage H-TD/TS I-VSAM J-CICS K-MAXR L-All Clear=================================================================================> DATABASE EXCEPTIONS > To display an exception threshold, remove the > preceding XACB and enter> the exception name after LIST=. To change a setting, enter over the current> value. To make your changes permanent, you must save your OMEGAMON profile.> For more information about a particular exception, place the cursor under> the required exception name and press PF11. XACB LIST=DBON: DBON+ DISPLAY Parameters: THRESHOLD Parameters: XLF Parameters:: State=OFF Threshold=N/A Auto=OFF: Group=DB Display=CLR2 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=================================================================================



DISPLAY parametersThese parameters include monitoring or ignoring an exception, and setting characteristics of the alert.

State One of the following:

NDSP Suppresses the display of exceptions. OMEGAMON II treats the exception as ON, but the exception does not appear. Instead, it can be logged to the XLFLOG, or can trigger an automatic screen space sequence when it occurs.

ON Invokes this exception during the current OMEGAMON II session.

OFF Does not invoke this exception during the current OMEGAMON II session.

TEST Forces a sample warning message, even if the exceptional condition is not presently occurring, for purposes of training or demonstration. (When TEST state forces a message to display, a T appears in column 2 of the exception display line.

Group 2-character exception group identifier. OMEGAMON II is shipped with exception groups predefined.

Bell Whether the audible alarm on the terminal sounds when this exception occurs. The bell must be activated by selecting the Display Options option (A) on the Configure path or entering fast path P.B from any panel.



THRESHOLD parametersThese parameters include setting threshold values for applicable exceptions, and modifying characteristics such as color and highlighting.

XLF parametersThese parameters deal with exception logging.

They enable you to perform operations such as stop issuing an exception message after the nth occurrence, or issue a series of predefined screen spaces. See Appendix B for more information.

Threshold Exception threshold. For exceptions that are either ON or OFF and do not have a numeric threshold, this entry is blank.

Display Sets the exception display color or intensity. Can be set to the variables Clr1 through Clr7. The values are associated with the colors listed below and follow the same order. Optionally, this value can be HI or LO on 4-color or noncolor terminals and one of the following on terminals that support the extended data stream.

RE RedBL BlueYE YellowPI PinkGR GreenTU TurquoiseWH WhiteNONE Hardware default colors

Note: The presentation of the intensity or color level on your terminal is determined by the type of terminal and the settings of the .SCC keywords.

Attribute Sets an additional highlight attribute for the box surrounding the exception message.

BLINK Turns on blinking for the exception.RVRS Displays the exception message in reverse video.UNDR Underscores the exception message.NONE Uses the default extended highlight attributes.

These attributes take effect only in modes other than ISPF on terminals that support the extended data stream.



Box parametersBox parameters define the characteristics of the exception box that encapsulates the exception message. You might want to use the box for exception messages that require immediate attention.

There might be several exception messages generated on one screen. By using a box around a particular exception, you can draw attention to it.

If you do not set color and highlighting attributes for the box, OMEGAMON II uses those that you set for the exception.

BOXCHAR Box character which makes up the box, enclosed in single quotes. The default is a plus sign (+). Do not use a single quote as a box character, since it is the delimiter.

Enter NOBOX without quotes to turn off boxing for an exception. If Boxchar=NOBOX, then the BOXCLR and BOXATTR parameters have no effect.

BOXCLR Color or intensity of the exception box. The Boxclr= keyword settings follow the same format as the threshold parameter, Display=.

BOXATTR Additional highlight attribute for the box on seven-color terminals modes other than ISPF.

BLINK Turns on blinking for the exception.

RVRS Displays the exception message in reverse video.

UNDR Underscores the exception message.

NONE Specifies the hardware default attributes.

If you set Boxchar=NOBOX, then the Boxclr and Boxattr parameters have no effect.



CYCLE parametersThese parameters indicate how often an exception is checked and how often it is allowed to be triggered.

EXNCYC Sets the frequency for checking the exception at every n OMEGAMON II cycles. If this parameter is set to 0 or 1, it will be tested every OMEGAMON II cycle. If it is set to a higher number, it will only be tested each time that number of cycles elapses. The default setting for EXNCYC is 0.

This parameter is provided so that you can tailor high overhead exceptions for your own environment. You can avoid using CPU time to test them every cycle. For example, if you have many devices in the class being examined by an exception (such as DASD or tape), you may want to set this parameter for corresponding exceptions in the hardware group.

When an exception that is not tested every cycle trips, the exception message appears on the screen as usual. In the following cycles during which it is not scheduled for testing, the exception message redisplays on the screen below the primary exception analysis display.

STOP=n (m) Sets a limit on the number of times an exception is allowed to trip. After the exception trips n times, the exception will not be tested or displayed during the current OMEGAMON II session, unless the user resets this parameter. The m value, which is informational only, indicates the number of times the exception has already tripped since the user last reset the Stop parameter. The default value for Stop is 0, which means that there is no limit to how many times the exception can be tested and displayed.

CUMULATIVE Indicates how many times the exception has tripped during the current OMEGAMON II session. You may not alter this value.

VSAM Analysis


VSAM AnalysisDetecting CI/CA splits and newly created extents for VSAM datasets could result in high overhead if done during every cycle. Therefore OMEGAMON II maintains a separate interval time to determine the number of minutes between updates for these exceptions. To display the current interval or to change the interval, select the VSAM option (I) on the Exception Settings path or enter fast path P.A.I from any panel. An example of the VSAM Exceptions settings panel is shown in the following figure.

FIGURE 20. VSAM Exception Settings Panel (P.A.I)

At the bottom of this panel, the XVSC statement displays the currently defined number of minutes between split and extent analysis. To change this interval, enter a number from 0–1440 immediately following XVSC (0 requests that the interval be every cycle).

Any changes to XVSC are in effect for the duration of your session. They are not saved when you save your profile.

________________ ZXSET9 VTM $CICSTOR V520./I SYSA 02/03/99 16:16: 0> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF 0 Save > A-Database B-I/O C-Task D-Terminal E-OMEGAMON II F-MVS> G-Storage H-TD/TS I-VSAM J-CICS K-MAXR L-All Clear==================================================================================> VSAM EXCEPTIONS > To display an exception threshold, remove the > preceding XACB and enter> the exception name after LIST=. To change a setting, enter over the current> value. To make your changes permanent, you must save your OMEGAMON II profile.> For more information about a particular exception, place the cursor under> the required exception name and press PF11. >XACB LIST=cccc > VSAM exception names:> SRH1 LSR pool 1 strings in use > nn% VCAS CA splits > n-last VSAM cycle> SRT1 LSR pool 1 string waits > nn VCIS CI splits > n-last VSAM cycle> STIO Rate of string waits per I/O > nn VINX VSAM index splits and extents> STRU Percentage of strings in use > nn VMEX Extentions > n-last VSAM cycle*> STRW Number of string waits exceeds nn > Set the interval between VSAM analysis cycles for split and extent> exceptions below: XVSC >> VSAM split/extent analysis will be performed every 5 minutes <===============================================================================

Task Analysis 89

Task Analysis

Chapter OverviewTask analysis provides realtime analysis of currently running tasks. OMEGAMON II monitors all running CICS transactions and provides an instantaneous display of task activity. As transactions complete, OMEGAMON II optionally saves pertinent resource usage data for online viewing.

Chapter ContentsTask Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90Task Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

Task Detail Information section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92Remote Information section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94Current Storage Usage section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95Storage Statistics section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97Time Statistics section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98General Statistics section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98File Control Statistics section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99Database Statistics section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99Unit-of-Work Information section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100Additional task detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Categorizing Task Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102Other task selections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Killing a Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105Transaction Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109Resource Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111Default RLIM testing frequency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112Setting RLIM testing intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112Enabling resource limiting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112Defining resource limiting thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113If a transaction reaches its resource limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

Starting and Stopping Resource Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

6

Task Summary


Task SummaryYou can access the complete range of task analysis features through the Tasks path. Several task options display summary information on tasks that fit a selected category (such as waiting tasks or tasks exceeding MAXR, the global CPU time limit threshold). Some of the task options provide detailed information on a single task that fits the selected category (such as the currently running task). In addition, the Tasks path includes an option to terminate unwanted tasks and an option to view short- and long-term transaction rates.

Start on the Tasks path by selecting the Tasks option (T) on the Main Menu, or entering fast path T. from any panel. The initial display as shown in the following figure summarizes all tasks in the system.

FIGURE 21. All Tasks in System Panel (T.)

This panel and any other summary tasks panel in the Tasks path show the transaction ID, task number, status, facility type, wait resource type, wait resource name, and CPU time used for the tasks that fit the selected category.

By analyzing the wait resource type and name you can determine what state each task is in and what might be delaying further task execution. For more information on wait reasons in CICS/MVS, see “Wait Reasons” on page 140. For CICS/ESA wait reasons, see IBM’s CICS Problem Determination Guide and for additional CICS/ESA wait reasons provided by OMEGAMON II, press PF1 for Help from the All Tasks panel.

________________ ZTKALL VTM $CICSTOR V520./I SYSA 02/03/99 13:55:51> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-All B-Master C-Waiting D-Over MAXR E-Running F-Other G-Kill H-Rate=================================================================================> ALL TASKS IN SYSTEM TASK+ Number of tasks selected: 28 Skipped: 0+ Tran Task Task Facility Resource Resource CPU+ ID Number State Type=ID Type Name Time+ -------- -------- -------- -------- -------- -------- ---------+ CDLI 28444 Suspend Trm=0071 IRLINK DB2EF23 0.004+ EXC1 28443 Suspend Trm=0296 KCCOMPAT TERMINAL 0.000+ EXC1 28440 Suspend Trm=0229 KCCOMPAT TERMINAL 0.000+ EXC1 28438 Suspend Trm=0407 KCCOMPAT TERMINAL 0.000+ CDME 28425 Suspend Trm=0332 IRLINK DB2EF17 0.002+ EXC1 28339 Suspend Trm=0269 KCCOMPAT TERMINAL 0.000+ EXC1 27909 Suspend Trm=0457 KCCOMPAT TERMINAL 0.000+ EXC1 25732 Suspend Trm=0070 KCCOMPAT TERMINAL 0.000+ CSNC 19 Suspend Task IRC CSNCWORK n/a+ CSSY 5 Suspend Task ICMIDNTE DFHAPTIM n/a+ CSTP 2 LastDisp Task TCP_NORM DFHZDSP n/a+ TIdomain None Suspend TIdomain TIEXPIRY DS_NUDGE n/a+ SMdomain None Suspend SMdomain SMSYSTEM (none) n/a+ CSSY 16 Suspend Task JCTERMN SUBTASK n/a+ CSSY 34 Suspend Task KCCOMPAT SINGLE 0.001================================================================================

Task Analysis 91

Task Detail

Task DetailTo see detailed information on an individual task, place the cursor on the line for that task and press Enter from any task summary display. OMEGAMON II collects the detailed task statistics using exit facilities in CICS and, for CICS/ESA, the CICS Monitoring facility.

The task detail display consists of titled sections which may comprise several panels. You can scroll through them using PF8 (Forward) and PF7 (Backward). Although one section on the task detail panel immediately follows another, each section is discussed here separately.

Note: You have the option of displaying only particular sections by including the DETAIL keyword in the TASK statement.

For example,

TASK NUMBER=00028459 DETAIL=(section)

When issuing the command, replace section with one or more of the following: ADabas, DAtacom, DB2, DLI, File, General, Idms, Remote, STATistics, STOrage, SUpra, Time, UMbrella UOw, USrevnt1, Zoom, or ALl.

It is necessary to specify only as many characters as needed to uniquely identify the keyword or required section. The minimum letters for each selection are capitalized in the preceding list.

Task Detail


Task Detail Information sectionThe first section, Task Detail Information appears as shown in Figure 22 on page 92.

FIGURE 22. Task Detail Panel - Task Detail Information Section (T.F.P)

Note: This panel is from a CICS/ESA Version 3 system. Other versions will vary from the above.

The Task Detail Information section includes:

Transaction ID Transaction identifier for the task.

Task number Specific task number which identifies the task.

Resource type Type of resource that the task is waiting on. For CICS/MVS systems, see “Wait Reasons” on page 140 for a list of all possible resource types. For CICS/ESA, see the CICS Problem Determination Guide.

Resource name Certain resource types show the name of the resource the task is waiting to access. For example, for a file wait the resource is the file name and for an enqueue wait the resource is the enqueue name.

Userid Eight character user’s signon ID.

Task state Current state of this task such as: running, suspended, or resumed.

________________ ZZTASK VTM $CICSTOR V520./I SYSA 02/03/99 13:56:55> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom =================================================================================> TASK DETAIL INFORMATION TASK NUMBER 00028459++ Task Detail Information+ Transaction ID . . . . : EXC1 Task number . . . . . . : 28459+ Resource type . . . . . : KCCOMPAT Resource name . . . . . : TERMINAL+ Userid . . . . . . . . : STMK07 Task state . . . . . . : Suspend+ Task purgeable . . . . : Yes Originated by . . . . . : EXC1+ Purge status . . . . . : No purge Task queue . . . . . . : Executbl+ Time of suspend . . . . : 13:56:01 Suspend timeout due . . : 14:16:09+ Time in suspend . . . . : 0:00:54 Suspend type . . . . . : Suspend+ Attaching domain . . . : AP TCB affinity . . . . . : QR+ Dispatching priority . : 1:11:09 TQE flag . . . . . . . : Active+ Facility ID (local) . . : 0290 Facility type (local) . : Term+ Real transaction ID . . : EXC1 Umbrella transaction ID : None+ Program ID - first . . : DFHCRP Umbrella program . . . : None+ Program ID - current . : DFHCRP+ Suspend area address . : 05693810+ DTA address . . . . . . : 05ABC1B8+ TQE address . . . . . . : 05344C30+ System TCA address . . : 00528A30+ User TCA address . . . : 00528BE8+ TMA address . . . . . . : 05462840+

Task Analysis 93

Task Detail

Task purgeable Whether the task is purgeable due to suspend timeout. Possible values for CICS/MVS are: St, Te, Stall, Term, or No. Possible values for CICS/ESA are Yes or No.

Originated by Originating transaction ID for this task.

Purge status Current purge status: No purge or Pending.

Task queue Which queue the task belongs to such as: Executable, Dispatchable, or Resumed (CICS/ESA).

Time of suspend Point in time when the task was suspended.

Suspend timeout due Point in time when the task will exceed the suspend timeout threshold.

Time in suspend Amount of time the task has been suspended.

Suspend type Suspended or Nonexecutable.

Attaching domain Domain that attached this task (CICS/ESA).

TCB affinity Which CICS TCB will handle the task: resource-owning, concurrent, quasi-reentrant (CICS/ESA), or FEPI.

Dispatching priority PCT dispatching priority in CICS/MVS; TCB aging time in CICS/ESA.

TQE flag Value of the TQE flag for this task or No TQE (CICS Version 3).

Facility ID Terminal ID or destination ID.

Facility type Type of facility identified above: term or dest.

Real transaction ID Transaction ID by which CICS knows this task.

Umbrella transaction ID Transaction ID assigned by Umbrella Services.

Umbrella program Program name assigned by Umbrella Services.

Suspend area address Location of the task’s suspend area (CICS/ESA).

DTA address Location of the task’s Dispatcher Task Area (DTA) (CICS/ESA).

XMXNC address Location of the task’s Transaction Manager transaction control block (CICS Version 4).

TQE address Location of the task’s Task Queue Element (TQE) (CICS Version 3).

System TCA address Location of the task’s system Task Control Area (TCA).

User TCA address Location of the task’s user TCA.

TMA address Location of the task’s Transaction Monitoring Area (TMA) used by CICS Monitoring to store performance data.

OC task area address Location of the task’s Monitor Work Area.

Task Detail


Remote Information sectionThe Remote Information section of the task detail panel appears as shown in this figure only if the task is part of a function shipping or transaction routing request.

FIGURE 23. Task Detail Panel - Remote Information Section

This section includes:

Session ID Remote session ID.

System ID System ID of remote system.

Transaction ID CICS transaction ID of remote task.

Facility ID Remote file ID, TS queue, or TD queue. This field may also contain the value of ‘Sync Pt’, which indicates that the session is in Sync Pt communication.

Facility type Remote type of facility identified above. Possible values include:n TrnRout (Transaction Route)n FC (File Control)n TD (Transient Data)n IC (Interval Control)n TS (Temporary Storage)n JC (Journal Control)n DLI (DL/I Request)n Funcshp (Function Ship Request)n DTP (Distributed Transaction Processing)

Session side Side (Frontend or Backend) of the conversation on which the task resides.

Session I/O Mode of the task. Can be RECEIVE (waiting for session to respond) or SEND (initiating the next request).

++ Remote Information+ System ID . . . . . . .: F19 Session ID . . . . . . : DB2E+ Transaction ID . . . . : EXC1 Facility ID . . . . . . : ‘Sync Pt’+ Facility type . . . . . : TrnRout Session I/O . . . . . . : SEND+ Session side . . . . . .: Backend+

Task Analysis 95

Task Detail

Current Storage Usage sectionThe Current Storage Usage section of the task detail panel includes statistics collected by the Storage Manager Domain for CICS/ESA and statistics based on an examination of all storage chained to the task’s TCA for CICS/MVS. For CICS/MVS, this section appears as shown in this figure.

FIGURE 24. Task Detail Panel - Current Storage Usage Section (CICS/MVS)

For CICS/MVS, this panel shows:

User storage Amount of storage allocated from the task subpool in the DSA.

User storage elems Number of storage elements allocated from the task subpool in the DSA.

Terminal storage Amount of storage allocated from the teleprocessing subpool in the DSA.

Terminal storage elems Number of storage elements allocated from the teleprocessing subpool in the DSA.

> 16M storage Amount of user storage allocated above the line.

> 16M storage elems Number of storage elements allocated above the line.

++ Current Storage Usage+ User storage. . . . . . : 23K User storage elems. . . : 21+ Terminal storage. . . . : 360 Terminal storage elems. : 1+ >16M storage. . . . . . : 0 >16M storage elems. . . : 0+

Task Detail


For CICS/ESA, current storage usage appears as shown in the following figure.

FIGURE 25. Task Detail Panel - Current Storage Usage Section (CICS/ESA)

For CICS/ESA, this panel shows:

Storage elements < 16M Number of storage elements obtained below the line.

Storage elements > 16M Number of storage elements obtained above the line.

Storage used < 16M Amount of storage actually used below the line.

Storage used > 16M Amount of storage actually used above the line.

Storage allocated < 16M Amount of storage allocated below the line.

Storage allocated > 16M Amount of storage allocated above the line.

++ Current Storage Usage+ Storage elements <16M . : 3 Storage elements >16M . : 1+ Storage used <16M . . . : 2K Storage used >16M . . . : 592+ Storage allocated <16M. : 4K Storage allocated >16M. : 4K+

Task Analysis 97

Task Detail

Storage Statistics sectionThe Storage Statistics section of the task detail panel includes statistics from the CICS Monitoring Facility for CICS/ESA and from OMEGAMON II’s collection facility for CICS/MVS as shown in the this figure.

FIGURE 26. Task Detail Panel - Storage Statistics Section

This section includes:

Occupancy measures the area under the curve of task storage in use against elapsed time. The unit of measure is byte-unit where byte is storage byte and unit is 1024 microseconds. For example, a task occupying 256 bytes for 125 milliseconds (122 units) incurs 31232 byte-units.

Getmains < 16M Number of storage getmains from below the line.

Getmains > 16M Number of storage getmains from above the line.

HWM < 16M Highest amount of storage from below the line.

HWM > 16M Highest amount of storage from above the line.

Occupancy < 16M Measure of storage used over time for storage below the line (CICS/ESA only).

Occupancy > 16M Measure of storage used over time for storage above the line (CICS/ESA only).

HWM of pgm storage < 16M Highest amount of program storage from below the line.

HWM of total pgm storage Highest amount of program storage from above or below the line.

Terminal storage Amount of storage allocated to TIOAs.

++ Storage Statistics+ Getmains <16M . . . . . : 4 Getmains >16M . . . . . : 0+ HWM <16M. . . . . . . . : 6K HWM >16M. . . . . . . . : 592+ Occupancy <16M. . . . . : 42K Occupancy >16M. . . . . : 0K+ HWM of total pgm storage: 3K 3K+ HWM of pgm storage <16M : 51K 3k+ HWM of pgm storage >16M : 78K HWM pgm storage cdsa . .: 0+ HWM pgm storage ecdsa . : 0 HWM pgm storage rdsa . .: 51K+ HWM pgm storage erdsa . : 78K HWM pgm storage sdsa . .: 0+ HWM pgm storage esdsa . : 0

Task Detail


Time Statistics sectionThe Time Statistics section of the task detail panel shows only the CPU time and Overall elapsed time for CICS/MVS. For CICS/ESA, this section shows CPU time, elapsed time, dispatch time, and various wait times as collected by the CICS Monitoring Facility. For CICS/ESA, this section appears as shown in this figure.

FIGURE 27. Task Detail Panel - Time Statistics Section (CICS/ESA)

General Statistics sectionThe General Statistics section of the task detail panel includes the number of TD gets, puts, and purges; TS gets and puts (to auxiliary and main); program control loads, links, and transfers of control; interval control starts; journal control writes; synchpoint requests; input and output messages and characters for primary and secondary terminals; and Basic Mapping Support (BMS) input, output, map, and total requests as shown in this figure. Fields marked with * apply only to CICS/ESA.

FIGURE 28. Task Detail Panel - General Statistics Section

++ Time Statistics+ CPU time . . . . . . . : 0.000 Overall elapsed time . : 8:30.788+ Total wait time . . . . : n/a Re-dispatch wait time . : 0.000+ Exception wait time . . : 0.000 TS VSAM I/O wait time . : 0.000+ TD VSAM I/O wait time . : 0.000 File I/O wait time . . : 0.000+ JC I/O wait time . . . : 0.000 TC I/O wait time . . . : n/a+ MRO wait time . . . . . : 0.000 1st dispatch delay time : 0.000+ Transaction class delay : 0.000 Max tasks delay . . . . : 0.000+ ENQ delay . . . . . . . : 0.000 LU61 wait time . . . . : 0.000+ LU62 wait time . . . . : 0.000 FEPI wait time . . . . : 0.000+ RMI elapsed time . . . : 0.000 RMI suspend time . . . : 0.000

++ General Statistics+ Primary term input msgs : 1 Primary term output msgs: 0+ Primary term input chars: 34 Prmary term output chars: 0+ Sec term input msgs . . : 0 Sec term output msgs. . : 0+ Sec term input chars. . : 0 Sec term output chars . : 0+ Sec lu62 input msgs . . : 0 Sec lu62 output msgs. . : 0+ Sec lu62 input chars. . : 0 Sec lu62 output chars . : 0+ * TD gets . . . . . . . . : 0 * TD puts . . . . . . . . : 0+ * TD purges . . . . . . . : 0 * TS gets . . . . . . . . : 0+ * TS puts to aux. . . . . : 0 * TS puts to main . . . . : 0+ * PC links. . . . . . . . : 0 * PC loads. . . . . . . . : 0+ * PC xctls. . . . . . . . : 0 * JC writes . . . . . . . : 0+ * IC starts . . . . . . . : 0 * Synchpoint requests . . : 0+ * BMS requests. . . . . . : 0 * BMS map requests. . . . : 0+ * BMS in requests . . . . : 0 * BMS out requests. . . . : 0+

Task Analysis 99

Task Detail

File Control Statistics sectionThe File Control Statistics section of the task detail panel appears as shown in this figure.

FIGURE 29. Task Detail Panel - File Control Statistics Section

This section includes the total number of requests made by the task for each filename.

Database Statistics sectionStatistics for DLI and third-party database products are collected for a task if you enabled the collection facility (see “Controlling file level statistics” on page 133). Fields for DLI Statistics correspond to the different types of DLI calls that a task can issue. For third-party databases, this section shows the total number or requests. There is a separate section for each database product.

DLI statistics appear as shown in this figure.

FIGURE 30. Task Detail Panel - DLI Statistics Section

This panel shows the number of requests for each type of DLI call and the amount of elapsed time taken to satisfy the requests.

An ADABAS section which shows total requests and elapsed time appears as shown in this figure. Similar statistics also appear for DB2, DATACOM, SUPRA, IDMS, and USREVNT1.

++ File Control Statistics+ Browses . . . . . . . . : 1 Gets. . . . . . . . . . : 4+ Adds. . . . . . . . . . : 0 Puts. . . . . . . . . . : 0+ Deletes . . . . . . . . : 0 Total requests. . . . . : 5+ Total VSAM calls. . . . : 4+

++ DL/I Statistics+ PSB schedule. . . . . . : 1 PSB schedule time . . . : 0.657+ PSB terminate . . . . . : 0 PDB terminate time. . . : 0.000+ Get Unique. . . . . . . : 0 Get Unique time . . . . : 0.000+ Get Next. . . . . . . . : 0 Get Next time . . . . . : 0.000+ Get Next in Parent. . . : 0 Get Next in Parent time : 0.000+ Get Hold Unique . . . . : 2 Get Hold Unique time. . : 0.948+ Get Hold Next . . . . . : 1 Get Hold Next time. . . : 0.000+ Get Hold Next in Parent : 0 GHN in Parent time. . . : 0.000+ Insert. . . . . . . . . : 0 Insert time . . . . . . : 0.000+ Delete. . . . . . . . . : 0 Delete time . . . . . . : 0.000+ Replace . . . . . . . . : 0 Replace time. . . . . . : 0.000+ Total requests. . . . . : 4 Elapsed time. . . . . . : 1.605

Task Detail


FIGURE 31. Task Detail Panel - ADABAS Statistics Section

The following figure shows the Umbrella user data work area. This work area is available for use by an application for reading and storing information. It is displayed in this panel in both character and hexadecimal formats. For more information on using Umbrella services, see the OMEGAMON II for CICS Configuration and Customization Guide.

FIGURE 32. Task Detail Panel - Umbrella Data Section

Unit-of-Work Information sectionThe Unit-of-Work Information section of the task detail panel appears as shown in this figure.

FIGURE 33. Task Detail Panel - Unit-of-Work Information Section

The unit of work section includes:

For MRO or ISC, unit-of-work ID combined with netname uniquely identifies a task, because UOWID is unique only to the originating CICS.

Netname Fully qualified name by which the originating system is known to the VTAM network. For CICS/ESA, the Netname is the LU of the originating terminal. For CICS/MVS, the Netname is the LU of the originating CICS region. If non-VTAM, it is networkid.generic_applid. If a DLI batch session, it is jobname.stepname.procname from the originator.

CICS token Name by which the unit-of-work is known within the originating system. Uses an STCK-derived token when locally attached or the unit-of-work ID (UOWID) that is part of the ISC/IRC attach-header.

++ Adabas Statistics+ Total requests . . . . : 5 Elapsed time. . . . . . : 0.430

++ Umbrella Data+ User work area (char) . : 12345678901234567890123456789012+ User work area (hex) . : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF+ 12345678901234567890123456789012

++ Unit-of-work Information+ Netname . . . . . . . . : ISCAC001.L0046953+ CICS token info (char). : ...G....+ CICS token info (hex) . : A5EC6300+ 02F73701

Task Analysis 101

Task Detail

Additional task detailFrom any task detail display, you can zoom to further displays linked to selected fields. Zoomable fields, when applicable, are highlighted in white. Zoomable task detail display fields and their destinations are listed in the following table:

Note: Additional zooming may be available from these zoom destinations.

There are also displays on the File, Database, Bottleneck, and Overview paths in the menu system that list tasks from which you can zoom to task detail in the same manner as above.

Table 4. Task Detail Display Zoom Destinations

Zoomable Field Destination

Facility ID (local) TCT entry

Read transaction ID PCT entry

Program ID - first PPT entry

Program ID - current PPT entry

Suspend area address Hex dump of suspend area

DTA address Hex dump of DTA

XMXNC address Hex dump of XMXNC

TQE address Hex dump of TQE

System TCA address Hex dump of system TCA

User TCA address Hex dump of user TCA

TMA address Hex dump of TMA

Categorizing Task Information


Categorizing Task InformationYou can obtain a summary or single task detail display for tasks that fit a specified category by selecting the various options on the menu that appears at the top of each task display. Summary task displays are similar except that the tasks included are limited by the category chosen. Task detail displays are similar except that they only include the sections that are applicable to the task. There are several task selection options that only apply to CICS/ESA.

Across the top of the All Tasks display and the displays for the other options listed is a menu of options that provides various categories of tasks.

FIGURE 34. Horizontal Menu Showing Task Categories

The available selections on this menu are as follows:

Other task selectionsIf you select the Other option (F) on the Tasks path or enter fast path T.F from any panel, you can access additional task categories which are listed in a menu across the top of each display. When you select Other, the initial panel lists tasks in Transaction Class 0 as shown in the following figure.

All All tasks in the CICS region.

Master Tasks in the application manager’s master queue. These are the tasks in the application domain. This display applies only to CICS Version 3 and above.

Waiting All waiting tasks.

Over MAXR Tasks that have exceeded the MAXR threshold. MAXR is a global CPU time limit which you set using the MAXR option on the Exception Settings menu in the Profile path (fastpath P.A.K).

Running Task detail for the currently executing task.

Other Additional task categories from which you can choose. See “Other task selections” on page 102.

Kill Summary of all tasks from which you can isolate a task for termination. See “Killing a Task” on page 105.

Rate Short-term and long-term transaction rates that exceed a specified threshold. See “Transaction Rate” on page 109.

________________ ZTKALL VTM $CICSTOR V520./I SYSA 02/03/99 13:55:51> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-All B-Master C-Waiting D-Over MAXR E-Running F-Other G-Kill H-Rate===============================================================================

Task Analysis 103


FIGURE 35. Tasks in a Class Panel (T.F)

The options available on the menu listed across the top of this panel provide additional categories of tasks which you may choose. Some options provide summaries and others provide detail of a single task. Some options apply to both CICS/MVS and CICS/ESA while others apply only to CICS/ESA.

The additional task categories include the following:

Class Tasks within the transaction class you specify. Transactions in Class 0 display by default.

CMAX Tasks in the application domain’s class max held chain. This display applies only to CICS/ESA.

CO Tasks in the concurrent TCB dispatchable queue. These are tasks that are ready to dispatch but are waiting for the concurrent TCB to become available. This display applies only to CICS/ESA.

DLI Tasks using DLI. To limit the display to tasks using DBCTL, you can replace DLI after the TASK statement with DBCTL.

DTA Detail for the task with the Dispatcher Task Area (DTA) address you specify. This display applies only to CICS/ESA.

Exec Tasks in the displatch domain’s executable queue. This display applies only to CICS/ESA.

FID Tasks with the initiating facility ID (terminal or destination ID) that you specify.

FTYPE Tasks with the initiating facility type (task, terminal-attached, or destination-attached) that you specify.

Handpost Tasks in the dispatcher domain’s handpostable queue. This display applies only to CICS/ESA.

________________ ZTKSEL VTM $CICSTOR V520./I SYSA 02/03/99 12:50:52> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Class B-CMAX C-CO D-DLI E-DTA F-Exec G-FID> H-FTYPE I-Handpost J-Journal K-Last L-MAXT M-New N-Non-Journ> O-Non-exec P-Task No. Q-QR R-Resume S-RO T-SOS U-Taskreq> V-Terminal W-Token X-TQE Y-Tran Z-User ZZ-Utran===============================================================================> TASKS IN A CLASS> Enter any transaction class number after CLASS. TASK CLASS 0+ Number of tasks selected: 19 Skipped: 0+ Tran Task Task Facility Resource Resource CPU+ ID Number State Type=ID Type Name Time+ -------- -------- -------- -------- -------- -------- --------+ EXC1 22255 Suspend Trm=0196 KCCOMPAT TERMINAL 0.000+ EXC1 22203 Suspend Trm=0160 KCCOMPAT TERMINAL 0.000+ EXC1 22188 Suspend Trm=0225 KCCOMPAT TERMINAL 0.000================================================================================



Pressing PF3 from any of these options returns you to the All Tasks display and the initial tasks menu.

Journal Journal tasks. These are system tasks that write, open, or close journals.

Last Detail for the task last dispatched. This display applies only to CICS/ESA.

MAXT Tasks in the application manager’s maxtask queue. These are tasks in the application domain that are held because of a MAXTASK condition in CICS. This display applies only to CICS/ESA.

New Tasks in the dispatcher domain’s new queue. These are held tasks that have never been dispatched because the maximum number of active tasks was reached. This display applies only to CICS Version 3 and above.

Non-Journ All tasks in CICS except the CICS system journal tasks.

Non-exec Tasks in the dispatcher domain’s non-executable queue. These are held tasks that have exceeded the MAXTASK limit. This display applies only to CICS Version 3 and above.

Task No. Detail for the task number that you specify.

QR Tasks in the quasi-reentrant dispatchable queue. These are tasks that are ready to dispatch but are waiting for the quasi-reentrant (QR) TCB (the main CICS TCB which is used for all applications) to become available. This display applies only to CICS/ESA.

Resume Tasks in the dispatcher domain’s resume queue. This display applies only to CICS Version 3.

RO Tasks in the resource-owning dispatchable queue. These are tasks that are ready to dispatch but are waiting for the resource-owning (RO) TCB to become available. This display applies to CICS/ESA only.

SOS Tasks that are waiting because of a short-on-storage (SOS) condition in CICS.

Taskreq Tasks started by the special key that you specify, which may be a PA key, PF key, light pen, magnetic card reader, or operator card.

Terminal Task(s) at the specific or generic terminal ID that you specify.

Token Detail for the task with the MRO token ID that you specify.

TQE Detail for the task with the Task Queue Element (TQE) address that you specify. This only applies to CICS Version 3.

Tran Task(s) with the specific or generic transaction ID that you specify.

User Task(s) with the specific or generic user ID that you specify.

Utran Tasks with the umbrella transaction ID that you specify. An umbrella transaction ID is a single transaction used by a fourth generation language for all generated tasks.

Task Analysis 105

Killing a Task

Killing a TaskYou might want to purge a task when, for example, a task is looping, consuming excessive resources, holding locks that are preventing other tasks from running, or causing a short-on-storage condition.

From OMEGAMON II, you can remove a task from CICS either by issuing a CEMT PURGE request to CICS via the operating system console, or by using the OMEGAMON II kill mechanism.

OMEGAMON II must be initialized in the CICS region before the task that you want to kill is started.

You should carefully consider the risks of losing data integrity or terminating CICS when you choose to purge a task. To prevent unauthorized use, OMEGAMON II is shipped with these facilities secured by default (see the OMEGAMON II for CICS Configuration and Customization Guide).

To purge a task, first select the Kill option (G) on the Tasks path or enter fast path T.G from any panel. The Kill Tasks panel appears as shown in the following figure.

FIGURE 36. Kill Tasks Panel (T.G)

The Kill Tasks panel displays a summary of all tasks in the system. Scroll through the summary to find the task you want to purge. To select a task for termination, place the cursor

________________ ZTKILL VTM TDOCS01 V520./C SYSA 02/03/99 13:20:29> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-All B-Master C-Waiting D-Over MAXR E-Running F-Other G-Kill H-Rate=================================================================================> KILL TASKS> WARNING: KILL may cause an abend or a corruption of CICS.> To select a task for possible kill, place the cursor on your choice and press> PF11. To cancel the kill, enter another selection letter or press PF3. KILL+ Number of tasks selected: 13 Skipped: 0+ Tran Task Task Facility Resource Resource CPU+ ID Number State Type=ID Type Name Time+ -------- -------- -------- -------- -------- -------- --------+ CSNC 24 Suspend Task IRC CSNCWORK 0.076+ CSSY 23 Suspend Task JCJOURDS DFHJ05A 0.000+ CSSY 22 Suspend Task JCJOURDS DFHJ04A 0.000+ CSSY 21 Suspend Task JCJOURDS DFHJ03A 0.000+ CSSY 20 Suspend Task JCJOURDS DFHJ02A 0.000+ CSSY 19 Suspend Task JCJOURDS DFHJ01A 0.001+ CSSY 8 Suspend Task JCJASUS JABSUTOK 0.109+ CSSY 7 LastDisp Task ICWAIT (none) 1.875+ CSSY 6 Suspend Task ICEXPIRY DFHAPTIX 1.148+ CSSY 5 Suspend Task ICMIDNTE DFHAPTIM 0.000+ CSTP 2 Suspend Task TCP_NORM DFHZDSP 1.970+ CSSY 18 Suspend Task JCTERMN SUBTASK 0.003+ CSSY 28 Suspend Task KCCOMPAT SINGLE 0.001===============================================================================

Killing a Task


on the line describing the task and press PF11. A kill confirmation panel appears as shown in the following figure.

FIGURE 37. Kill Task Detail Panel (Accessed by Zoom)

The Kill Task Detail panel warns of any conditions that should be considered prior to confirming the kill request. For example, in the previous figure, you are warned that this is a CICS system task. Attempting to purge this task carries a far greater chance of terminating CICS.

________________ ZZKILL VTM TDOCS01 V520./C SYSA 02/03/99 13:24:15> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down =================================================================================> KILL TASK DETAIL> WARNING: KILL may cause an abend or corruption of CICS.>> Before attempting to use the OMEGAMON KILL mechanism, use the CEMT> transaction to purge the task: type the action character (-) in> column 1 before the following OCMD command and press enter. OCMD F CSNCWORK,CEMT SET TASK(24) PURGE No Act > To request OMEGAMON II to terminate the task, type YES and press enter.> To cancel the kill and return press PF3.> (To request an unconditional KILL of the task, type FORCE after the> command. This should only be done after attempting to KILL the task> normally). KILL NUMBER 00000024++ ========================================================================: ___ <----- Enter ‘YES’ to terminate this task+ ========================================================================++ ************************************************************************+ *> <*+ *> Caution: KILL is a last resort and may abend CICS. The CEMT <*+ *> PURGE and/or FORCE options should be tried first. <*+ *> <*+ *> This task is a CICS system task. <*+ *> <*+ ************************************************************************++ Transaction ID . . . . : CSNC Task number . . . . . . : 24+ Resource type . . . . . : IRC Resource name . . . . . : CSNCWORK+ Userid . . . . . . . . : SYS1 Task state . . . . . . : Suspend+ Purgeable suspend . . . : No Originated by . . . . . : CSNC+ Purge status . . . . . : No purge Task queue . . . . . . : Executbl+ Time of suspend . . . . : 10:27:46 Suspend timeout due . . : None+ Time in suspend . . . . : 2:56:30 Suspend type . . . . . : Suspend+ Attaching domain . . . : AP TCB affinity . . . . . : QR+ Dispatching priority . : 4:20:41 TQE flag . . . . . . . : Active

Task Analysis 107

Killing a Task

Depending on your release of CICS and what state the task is in, OMEGAMON II issues an OCKC, S0C6, or EIKI abend when a task is killed. OMEGAMON II issues these abends under the conditions listed in the following table.

Before trying the Kill option, first try using CEMT. To do so, enter a hyphen (-) preceding the OCMD statement on this panel. This issues a CEMT PURGE of the selected task for you. Keep pressing Enter until you see a message stating whether or not the purge took place.

Because of the changes in task management and the introduction of the dispatcher domain, the kill mechanism works very differently for CICS/ESA than it does for CICS/MVS. In CICS/ESA, we recommend that you initialize OMEGAMON II in the monitored CICS region (via PLTPI program KOCOME00 or transaction OMEG INIT) for the full range of kill features to be available.

To confirm an OMEGAMON II kill of the selected task, enter YES in the entry field below the KILL statement. When the kill has been requested, you will see a message below the KILL statement telling you what method will be used to perform the kill or explaining why it was unsuccessful. For more information about the message, see the Messages Manual.

If other methods do not work, you can enter FORCE after the KILL statement to bypass certain integrity checks. For example,

KILL NUMBER=12345 FORCE

You still must enter YES to confirm the kill. The FORCE option enables you to purge tasks in a dispatcher wait. When you issue a FORCE purge in CICS/ESA, look for messages on the operating system console to say whether the kill was successful (use fast path U.A).

If you prefer to cancel the kill and return to the summary panel, press PF3. By default, only the General and Remote Task detail sections are displayed through the Kill command.

Note: You have the option of displaying only those sections that are of interest to you by including the DETAIL keyword in the KILL statement.

For example,

KILL NUMBER=00028459 DETAIL=(section)

Abend CICS Version Task Condition

OCKC CICS/MVS Suspended tasks; KCP not waiting

S0C6 CICS/MVS Task currently running or KCP waiting on VSAM I/O

EIKI CICS/ESA Tasks waiting, but not in VSAM I/O

S0C6 CICS/ESA Currently running task (QR, RO, CO TCB only; the FEPI TCB, ZS, is not checked)

— CICS/ESA When a task is waiting on file I/O, OMEGAMON II issues a force purge

Killing a Task


When issuing the command, replace section with one or more of the following: ADABas, DATAcom, DB2, DLI, FILE, GENEral, IDMS, REMOte, STATistics, STORage, SUPRa, TIME, UMBRella, UOW, UE1, ZOOM, or ALL.

It is necessary to specify only as many characters as needed to uniquely identify the keyword or required section. The minimum letters for each selection are capitalized in the preceding list.

See “Task Detail” on page 91 for a description of the displayed detail sections.

Task Analysis 109

Transaction Rate

Transaction RateThe transaction rate is a good indication of CICS system throughput. OMEGAMON II calculates the transaction rate at a short-term interval (one minute) and at a long-term interval (user-specified) for individual transactions as well as all transactions.

To display transaction rate, select the Rate option (H) on the Tasks path or enter fast path T.H from any panel. The Transaction Rate panel appears as shown in the following figure.

FIGURE 38. Transaction Rate Panel (T.H)

This panel shows the number of transactions per minute for each transaction that has exceeded the specified transaction rate threshold. Short-term and long-term rates are displayed.

The overall total, shown at the bottom of the panel, represents the total number of transactions attached by CICS during the interval and is not equivalent to the sum of the rates of the individual transaction IDs listed.

You may see high transaction rates with a low total transaction rate because no new transactions are attached, but those already attached are being dispatched by CICS. A high total transaction rate, however, with a low transaction rate may indicate a problem, in that

________________ ZTKRATE VTM $CICSTOR V520./I SYSA 02/03/99 14:00:15> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-All B-Master C-Waiting D-Over MAXR E-Running F-Other G-Kill H-Rate=================================================================================> TRANSACTION RATE> To change transaction rate settings, enter new values over the current ones. RATE THRESHOLD=1,LONGTERM=1,SCALE=400,UNIT=minute++ Tran Trans/ Trans/+ ID Minute -------Short-Term------ Minute --------Long-Term------+ ----- ------ 0----133----266-----400 ------ 0----133----266-----400+ CATD 1.6 |> . . . . . . . . . .| 1.6 |> . . . . . . . . . .|+ CDLI 4.0 |> . . . . . . . . . .| 4.0 |> . . . . . . . . . .|+ CRSR 5.6 |> . . . . . . . . . .| 5.6 |> . . . . . . . . . .|+ CSNE 2.2 |> . . . . . . . . . .| 2.2 |> . . . . . . . . . .|+ EXC1 12.8 |> . . . . . . . . . .| 12.8 |> . . . . . . . . . .|+ MI 1.2 |> . . . . . . . . . .| 1.2 |> . . . . . . . . . .|+ MIMI 1.6 |> . . . . . . . . . .| 1.6 |> . . . . . . . . . .|+ MSA2 9.1 |> . . . . . . . . . .| 9.1 |> . . . . . . . . . .|+ XCIM 1.2 |> . . . . . . . . . .| 1.2 |> . . . . . . . . . .|+ TOTAL 44.6 |--> . . . . . . . . .| 44.6 |--> . . . . . . . . .|===============================================================================

Transaction Rate


CICS is attaching new transactions that are not being dispatched. The RATE statement includes several options that you can modify to alter the display:

To clear the transaction rates displayed and pick up any new transactions that have been added to the system, enter RESET after the RATE statement.

RATE RESET

THRESHOLD Specifies a threshold transaction rate. The panel displays only those transactions whose dispatch rates exceed the threshold.

LONGTERM Sets the time interval for the long-term portion of the display. The short-term interval is fixed at one minute.

SCALE Sets the scale for the graphic portion of the display.

UNIT Sets the transaction rate to either transactions per minute or transactions per second. If the transaction rate in minutes overflows (the field displays as a series of asterisks), consider specifying the UNIT as second instead of minute.

Task Analysis 111

Resource Limiting

Resource Limiting

DescriptionResource limiting allows you to predetermine the amount of CICS resources that a task may use. Any task that reaches a usage threshold will be abended by OMEGAMON II. The CICS resources that OMEGAMON II can monitor, on a task basis are:

n CPU timen elapsed timen number of file and database requestsn current amount of CICS task storage in use

For each resource in the global data area, you set a threshold and identify the tasks that must comply with the threshold. You can specify tasks using wildcard characters. All tasks, except those specified in an exclude list, are subject to a resource limit. If a task has more than one limit for a resource, the lowest limit is used.

Once resource limiting has been enabled, OMEGAMON II tests transactions to determine whether the threshold criteria have been met. OMEGAMON II’s testing can either be performed following each CICS EXEC call or database request, or can be set to perform testing after a specified number of calls or period of time.

OMEGAMON II determines whether a threshold has been reached when a CICS transaction issues EXEC level commands. Transactions with EXEC CICS calls are tested based upon the resource usage of all prior CICS requests, while exclusively MACRO level CICS transactions are not tested and are not subject to resource limiting. Database requests are tested at the time any number of them are received.

A separate threshold is available for each type of file and database request. Currently these requests are:

n EXEC level file controln EXEC and CALL DL/I requestsn DB2 requestsn third-party database (IDMS, ADABAS, DATACOM, USREVNT1, and SUPRA) requests

OMEGAMON II purges any transactions performing function shipping in the CICS application owning region (AOR) that exceed the threshold.

For storage usage, there is one threshold for task storage used in the DSA (<16M) and one threshold for all task storage used in the DSA and EDSA (<16M & >16M), respectively. OMEGAMON II compares the amount of task storage currently in use with the amount requested to determine whether a limit has been reached.

Resource Limiting


Default RLIM testing frequencyThe point at which OMEGAMON II performs resource limiting testing depends on both the resource, and whether or not you have specified RLIM interval settings.

The following table displays each resource and the frequency of its limit testing. The subsequent section discusses how to set RLIM testing intervals that can be used in place of these defaults.

Setting RLIM testing intervalsResource limiting testing intervals may be set to change the frequency of threshold testing from previously defined resource limits or rules. The benefit of this feature is that, properly set, it can reduce the amount of CPU usage attributed to RLIM processing.

There are two general types of RLIM testing intervals:

n Time-based interval settings allow you to specify the period of time that must pass between threshold tests. This interval is specified in seconds, and may be set for any number up to a period of one week (614800 seconds).

n Command-instance interval settings allow you to specify the number of CICS EXEC or database calls that must be made between threshold tests. Any number of EXEC or database calls may be specified.

Once RLIM has been activated, a non-zero setting for any of the interval types will cause that interval to be applied to all transactions. Also, any previous settings are ignored if a new setting is specified. Setting all interval types to 0 will result in the defaults being used.

Enabling resource limitingWhen you initialize OMEGAMON II in the CICS region, you automatically enable resource limiting based on parameters that you supplied in the global data area (REOURCE_LIMITINGnn) module.

Table 5. Task Resources and Limit Testing

Resource Tested . . .

CPU time At every EXEC CICS call.

Elapsed time At every EXEC CICS call.

File Control request At every EXEC CICS file control request.

DL/I request At every EXEC CICS call. It is not tested during EXEC DLI or CALLDLI requests, therefore, OMEGAMON II does not abend a task until the next EXEC CICS request.

DB2 request At every EXEC DB2 call.

Database request At every database request.

Storage At every GETMAIN request. A conditional GETMAIN that causes a task to reach or exceed its limit is abended even if the GETMAIN request fails due to a lack of storage.

Task Analysis 113

Resource Limiting

Defining resource limiting thresholdsYou define the limits for resources in your global data area (RESOURCE_LIMITINGnn) module and specify the limits in the RESOURCE_LIMITING parameter. See the OMEGAMON II for CICS Configuration and Customization Guide for information on these two parameters.

If a transaction reaches its resource limitIf OMEGAMON II finds a CICS transaction that has reached its resource limit, that transaction will be abended or a warning message will be issued. The abend code depends on the resource limit that was reached, while the warning message depends upon the LIMIT parameter that was set in the Resource Limiting component of the global data area. For a list of the resource limiting codes, see the appendix listing the codes in the Messages Manual.

Starting and Stopping Resource Limiting


Starting and Stopping Resource LimitingOMEGAMON II performs resource limiting when it initializes its data collection component in the CICS region. The program KOCOME00 normally does this during PLTPI. You can also perform the OMEG INIT or OMEG SHUT transaction from CICS to start or stop the data collection component.

While the data collection component is running, you can start and stop resource limiting from the Control path of the Menu System.

1. Enter O on the Info-line of the main menu to display the Control Options menu.

FIGURE 39. Main Menu

The Control Options menu displays.

2. From the Control Options menu, enter R, S, or T to start, stop, or display the current status of resource limiting.

O_______________ ZMENU VTM $CICSTOR V520./I SYSA 02/05/99 16:57:36> PF1 Help/News/Index PF3 Exit PF18 Color TOR=================================================================================> Enter a selection letter on the top line.> OMEGAMON FOR CICS/ESA PERFORMANCE MONITOR SYSTEM > W REGIONS ............ List CICS regions, switch monitoring> V OVERVIEW ........... Performance overview> R RESPONSE TIME ...... CICS and end-to-end response time monitoring> E EXCEPTIONS ......... Current system problems and problems this session> T TASKS .............. Task analysis> H HISTORY ............ Historical transaction viewing and selection> B BOTTLENECKS ........ Resource contention (bottlenecks, impacts, enqueues)> S STORAGE ............ Storage summary, violations, DSA, EDSA, PAM, subpools> F FILES .............. CICS datasets, VSAM, LSR, string and buffer waits> D DATABASES .......... DB2 and DLI> C CICS ............... CICS tables and control blocks> M MVS ................ Operating System control blocks for CICS> I I/O ................ DASD performance > U UTILITIES .......... Utility functions and displays> O CONTROL ............ Control options (response time, history, contention)> G GROUPS ............. Group definitions> P PROFILE ............ Profile options and maintenance===============================================================================

Task Analysis 115


FIGURE 40. Control Options Menu

If you stop resource limiting using option S (Resource Limiting Off), you must then select R (Resource Limiting On) to start it later. Performing the OMEG SHUT transaction followed by the OMEG INIT transaction does not automatically restart resource limiting in this case.

________________ ZCNTL VTM $CICSTOR V520./I SYSA 02/05/99 16:57:36> PF1 Help/News/Index PF3 Exit PF18 Color TOR=================================================================================> Enter a selection letter on the top line.> CONTROL OPTIONS > A RTA ON ................... Start response time monitor> B RTA OFF .................. Stop response time monitor> C RTA STATUS ............... Response time monitor status> D RTA INTERVALS ............ Set response time monitor intervals> E RTA SCALE/WINDOW ......... Set response time monitor scale and window> F ONDV ON .................. Start online historical data viewing collector> G ONDV OFF ................. Stop online historical data viewing collector> H ONDV STATUS .............. Online historical data viewing collector status> I BOTTLENECK CONTROL ....... Control bottleneck analysis> J BOTTLENECK WAIT REASONS... Control bottleneck analysis wait reasons> K INTR CONTROL ............. Control interval record collection> L IMPACT ANALYSIS ON ....... Start workload impact analysis> M IMPACT ANALYSIS OFF ...... Stop workload impact analysis> N IMPACT ANALYSIS SETTINGS . Workload impact analysis settings> O IMPACT ANALYSIS GROUPS ... Define workload impact analysis groups> P DATABASE COLLECTORS ...... Control database collectors> Q CICS SHUTDOWN OPTION ..... CICS shutdown purge option> R RESOURCE LIMITING ON ..... Start resource limiting> S RESOURCE LIMITING OFF..... Stop resource limiting> T RESOURCE LIMITING STATUS.. Resource limiting status================================================================================



Task History 117

Task History

Chapter OverviewThe task history feature provides analyses of tasks that have completed. Online historical data viewing (ONDV) enables you to select transactions with specified transaction and terminal IDs for viewing from the historical datastore. You can filter the historical display to include tasks that ran in a specified time period, exceeded certain thresholds, or terminated with certain abend codes.

OMEGAMON II can also record task analysis data for completed tasks to SMF, producing batch reports for offline analysis. To allocate the historical dataset through CICAT™, select option 5, Allocate historical dataset(s), on the Customization menu. Refer to the OMEGAMON II for CICS Configuration and Customization Guide to see an example of this panel.

Chapter ContentsHistorical Task Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118Historical Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119Historical Detail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121File Level Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124Historical Task Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129Controlling Online Historical Viewing Collector (ONDV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131

Historical collector status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131Starting and stopping the historical collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132Controlling file level statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133

7

Historical Task Analysis


Historical Task AnalysisOMEGAMON II collects performance related statistics at the end of each conversation or task and saves them for later viewing.

Task History 119

Historical Summary

Historical SummaryTo access task-related historical data, select the History option (H) on the main menu. The initial display on this path is the Historical Transaction Overview, which is a summary of all tasks on the current log file as shown in the following figure.

FIGURE 41. Historical Transaction Overview Panel (H.)

________________ ZONDV VTM $CICSTOR V520/I SYSA 02/03/99 14:00:37> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-History Record View B-History Record Selection===============================================================================> HISTORICAL TRANSACTION OVERVIEW ONDV NEXT+ Transaction Overview starting at 02/03/99+ Start Tran Task Term Type CPU Resp Storage File Term Abend+ Time ID Number ID Time Time HWM Reqs I/O Code+ -------- ---- ------ ---- ---- ----- ------- ------- ----- ---- -----+ 13:47:08 MSA2 28054 0165 TRM .1 2.8 99152 64 1114+ 13:47:09 MIMI 28055 0066 TRM .0 1.3 1792 0 16+ 13:47:12 EXC1 28027 0461 TRM .0 0.0 1792 0 470+ 13:47:14 CRSR 28060 E1 TRM .0 0.0 800 0 0+ 13:47:13 CDLI 28059 0270 TRM .0 0.6 1792 0 16+ 13:47:14 XCIM 28061 0270 ATI .0 0.0 1792 0 0+ 13:47:14 CRSR 28062 E1 TRM .0 0.0 800 0 0+ 13:47:16 EXC1 28027 0461 TRM .0 0.3 1792 0 823+ 13:47:16 MSA2 28065 0255 TRM .0 0.1 43136 36 969+ 13:47:18 CSPQ 28067 n/a ATI .0 0.2 944 0 0+ 13:47:18 EXC1 28027 0461 TRM .0 0.2 1792 0 617+ 13:47:18 EXC1 28063 0270 ATI .0 0.1 1792 0 855+ 13:47:19 EXC1 28027 0461 TRM .0 0.1 1792 0 812+ 13:47:21 EXC1 28027 0461 TRM .0 0.0 1792 0 711+ 13:47:21 EXC1 28063 0270 ATI .0 0.1 1792 0 883

Historical Summary


On the historical overview display, you can see:

Tran ID CICS transaction ID or the umbrella transaction ID if supplied.

Task Number Number sequentially assigned by CICS to uniquely identify the task. An S following the task number indicates that CMF created a syncpoint performance record for the task; an F indicates a long-running transaction.

Type How the transaction was started:

ATI Automatic task initiation.DCT Trigger level from a DCT entry.IC Interval control request.SYS System internal task (CICS/MVS only).TRM Terminal request.

CPU Time Number of CPU seconds the task used.

Resp Time Task response time in seconds.

Storage HWM Highwater mark for all user storage above and below the 16M line.

File Reqs Total count of all file control, DB2, DLI, and third-party database requests.

Term I/O Character count of all input and output messages.

Abend Code Transaction abend code if applicable.

Task History 121

Historical Detail

Historical DetailTo view detailed historical data on a specific task, place the cursor on the transaction and press PF11. An example of a detailed historical task display is shown in the following figure.

FIGURE 42. (Part 1) Historical Transaction Detail Panel (Accessed by Zoom)

________________ ZZONDV VTM $CICSTOR V520/I SYSA 02/03/99 14:01:04> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down ===============================================================================> HISTORICAL TRANSACTION DETAIL ONDV 09 ++ Task Detail Information++ General Information+ Transaction ID . . . . : CDLI Task number . . . . . . : 28059+ Userid . . . . . . . . : CSDB04 Luname . . . . . . . . : R310H00+ Facility ID (local) . . : 0270 Facility type (local) . : Term+ Real transaction ID . . : CDLI Umbrella transaction ID : None+ Program ID - first . . : DFHCRP Umbrella program . . . : None++ Time Statistics+ CPU time . . . . . . . : 0.000 Overall elapsed time . : 0:29:58+ * Total wait time . . . . : 0.151 Re-dispatch wait time . : 0.050+ * Exception wait time . . : 0.000 TS VSAM I/O wait time . : 0.000+ * TD VSAM I/O wait time . : 0.000 File I/O wait time . . : 0.000+ * JC I/O wait time . . . : 0.000 TC I/O wait time . . . : 0.000+ * MRO wait time . . . . . : 0.000 1st dispatch delay time : 1.435+ * Transaction class delay : 0.000 Max tasks delay . . . . : 0.000+ * ENQ delay . . . . . . . : 0.000 LU61 wait time . . . . : 0.000+ * LU62 wait time . . . . : 0.000 FEPI wait time . . . . : 0.000+ * RMI elapsed time . . . : 0.000 RMI suspend time . . . : 0.000++ General Statistics+ Primary term input msgs : 1 Primary term output msgs: 0+ Primary term input chars: 34 Prmary term output chars: 0+ Sec term input msgs . . : 0 Sec term output msgs. . : 0+ Sec term input chars. . : 0 Sec term output chars . : 0+ Sec lu62 input msgs . . : 0 Sec lu62 output msgs. . : 0+ Sec lu62 input chars. . : 0 Sec lu62 output chars . : 0+ * TD gets . . . . . . . . : 0 * TD puts . . . . . . . . : 0+ * TD purges . . . . . . . : 0 * TS gets . . . . . . . . : 0+ * TS puts to aux. . . . . : 0 * TS puts to main . . . . : 0+ * PC links. . . . . . . . : 0 * PC loads. . . . . . . . : 0+ * PC xctls. . . . . . . . : 0 * JC writes . . . . . . . : 0+ * IC starts . . . . . . . : 0 * Synchpoint requests . . : 0+ * BMS requests. . . . . . : 0 * BMS map requests. . . . : 0+ * BMS in requests . . . . : 0 * BMS out requests. . . . : 0+

Historical Detail



+ Storage Statistics+ Getmains <16M . . . . . : 4 Getmains >16M . . . . . : 1+ HWM <16M . . . . . . . : 1K HWM >16M . . . . . . . : 592+ Occupancy <16M . . . . : 609K Occupancy >16M . . . . : 302K+ HWM of total pgm storage: 728+ HWM of pgm storage <16M : 0 3K+ HWM of pgm storage >16M : 728 HWM pgm storage cdsa . .: 0+ HWM pgm storage ecdsa . : 0 HWM pgm storage rdsa . .: 51K+ HWM pgm storage erdsa . : 728 HWM pgm storage sdsa . .: 0+ HWM pgm storage esdsa . : 0++ File Control Statistics+ Browses . . . . . . . . : 0 Gets . . . . . . . . . : 0+ Adds . . . . . . . . . : 0 Puts . . . . . . . . . : 0+ Deletes . . . . . . . . : 0 Total requests . . . . : 0+ Total VSAM calls . . . : 0++ DL/1 Statistics+ PSB schedule . . . . . : 1 PSB schedule time . . . : 0.724+ PSB terminate . . . . . : 0 PSB terminate time . . : 0+ Get Unique . . . . . . : 2 Get Unique time . . . . : 1.927+ Get Next . . . . . . . : 8 Get Next time . . . . . : 0.069+ Get Next in Parent . . : 0 Get Next in Parent time : 0+ Get Hold Unique . . . . : 0 Get Hold Unique time . : 0+ Get Hold Next . . . . . : 0 Get Hold Next time . . : 0+ Get Hold Next in Parent : 0 GHN in Parent time . . : 0+ Insert . . . . . . . . : 0 Insert time . . . . . . : 0+ Delete . . . . . . . . : 0 Delete time . . . . . . : 0+ Replace . . . . . . . . : 0 Replace time . . . . . : 0++ DB2 Statistics+ Open cursors . . . . . : 1 Open cursors time . . . : .100+ Close cursors . . . . . : 0 Close cursors time . . : 0+ Fetches . . . . . . . . : 0 Fetches time . . . . . : 0+ Selects . . . . . . . . : 5 Selects time . . . . . : .990+ Inserts . . . . . . . . : 0 Inserts time . . . . . : 0+ Updates . . . . . . . . : 0 Updates time . . . . . : 0+ Deletes . . . . . . . . : 0 Deletes time . . . . . : 0+ Prepares . . . . . . . : 0 Prepares time . . . . . : 0+ Describes . . . . . . . : 0 Describes time . . . . : 0+ Executes . . . . . . . : 0 Executes time . . . . . : 0+ Exec immediates . . . . : 0 Exec immediates time . : 0+ Misc calls . . . . . . : 0 Misc calls time . . . . : 0+

Task History 123

Historical Detail


This panel displays detailed statistics for the transaction history record you have selected. The fields on this panel are the same as on the task detail panels in the Tasks path. (See “Task Detail” on page 91 for descriptions of the task detail fields.) You may need to scroll forward (PF8) to see applicable file and database request statistics for the task. Zooming is available when the field is highlighted in white. Fields marked with an asterisk (*) apply only to CICS/ESA. The asterisks are notational; they are not part of the panel’s contents.

+ Adabas Statistics+ Total requests . . . . : 1 Elapsed time . . . . . : .050++ IDMS Statistics+ Total requests . . . . : 1 Elapsed time . . . . . : .050++ DATACOM Statistics+ Total requests . . . . : 1 Elapsed time . . . . . : .050++ SUPRA Statistics+ Total requests . . . . : 1 Elapsed time . . . . . : .050++ USREVNT1 Statistics+ ADD requests. . . . : 1 ADD time. . . . . . : 7.930+ DELETE requests. . . . : 1 DELETE time. . . . . . : 1.047+ BROWSE requests. . . . : 1 BROWSE time . . . . . : 0.000+ UPDATE requests. . . . : 1 UPDATE time . . . . . : 2.096+ READ requests. . . . : 1 READ time . . . . . : 2.097+ WRITE requests. . . . : 1 WRITE time . . . . . : 3.145+ OPEN requests. . . . : 1 OPEN time . . . . . : 19.997+ CLOSE requests. . . . : 1 CLOSE time . . . . . : 3.124+ DELAY requests. . . . : 1 DELAY time . . . . . : 1.049+ Total requests . . . . : 9 Elapsed time . . . . . : 40.485+ Average time . . . . . : 4.498++ Umbrella Data+ User work area (char) . : 12345678901234567890123456789012+ User work area (hex) . : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF+ 12345678901234567890123456789012++ Unit-Of-Work Information+ Netname . . . . . . . . : USCACO01.R103C02+ CICS token info (char) : 1$..*....+ CICS token info (hex) . : F53E5B200+ 1BECC680B

File Level Statistics


File Level StatisticsFields on the task detail display such as File Control Statistics, DL/I Statistics, and third-party database statistics are zoomable if there was any activity. You can view file level statistics by zooming on these titles, which are highlighted in white. Then, from the file or database statistics panel, you can zoom again on an individual file or database for counts of each type of request or call to it.

To obtain File Control statistics for each file on the Historical Transaction Detail panel, scroll forward to the File Control Statistics title, position the cursor on the title, and press PF11. An example of File Control statistics appears in Figure 45 on page 124.

FIGURE 45. Historical File Summary for Selected Task (Accessed by Zoom)

This panel shows counts and elapsed times for each type of file operation as well as a summary of file operations per file name. Elapsed time is the wall-clock difference between the time that the file control request was received by the CICS EXEC interface and the time CICS returns control to the application. This value includes all CICS management module execution times and wait times involved in servicing the request.

See “Controlling file level statistics” on page 133 and the “Global Data Area” chapter in the OMEGAMON II for CICS Customization Guide for more information on defining file level collection options.

Note: VSAM file-level statistics are collected by OMEGAMON only when a file request invokes the EXEC interface program, DFHEIP. Detailed statistics will not be collected for a file, therefore, for any transaction that does not access the file through an EXEC CICS call. For example, detailed statistics for file DFHCSD are not available for transaction CEDA.

________________ ZZONDVD VTM $CICSTOR V520/I SYSA 02/03/99 14:33:13> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down ===============================================================================> HISTORICAL FILE SUMMARY FOR SELECTED TASK ONDV 12 FILE SUMMARY+ Transaction Detail for MSA2 task number =29757++ File Control Statistics+ Read . . . . . . . . . : 4 Read time . . . . . . . : 0.884+ Write . . . . . . . . . : 10 Write time . . . . . . : 3.354+ Update . . . . . . . . : 26 Update time . . . . . . : 0.485+ Delete . . . . . . . . : 2 Delete time . . . . . . : 0.024+ Browse . . . . . . . . : 2 Browse time . . . . . . : 0.006+ Misc requests . . . . . : 2 Misc requests time . . : 0.227++ File Requests Elapsed+ ID Time+ -------- -------- --------+ LKTWAD 3 0.046+ LKPDSEC 12 0.136+ APFM930 2 0.002+ CCFM920 4 0.044===============================================================================

Task History 125


If you zoom on DLI Statistics from the Historical Transaction Detail display (“(Part 1) Historical Transaction Detail Panel (Accessed by Zoom)” on page 121), a panel appears as shown in Figure 46 on page 125.

FIGURE 46. DLI Statistics (Accessed by Zoom)

If you zoom on ADABAS Statistics from the Historical Transaction Detail display, a panel appears as shown in the following figure.

FIGURE 47. ADABAS Statistics (Accessed by Zoom)

++ DL/I Statistics+ PSB schedule. . . . . . : 1 PSB schedule time . . . : 2.912+ PSB terminate . . . . . : 1 PDB terminate time. . . : 0.076+ Get Unique. . . . . . . : 0 Get Unique time . . . . : 0.000+ Get Next. . . . . . . . : 0 Get Next time . . . . . : 0.000+ Get Next in Parent. . . : 0 Get Next in Parent time : 0.000+ Get Hold Unique . . . . : 2 Get Hold Unique time. . : 6.361+ Get Hold Next . . . . . : 8 Get Hold Next time. . . : 0.168+ Get Hold Next in Parent : 0 GHN in Parent time. . . : 0.000+ Insert. . . . . . . . . : 0 Insert time . . . . . . : 0.000+ Delete. . . . . . . . . : 0 Delete time . . . . . . : 0.000+ Replace . . . . . . . . : 0 Replace time. . . . . . : 0.000++ DBD/PSB Requests Elapsed+ Name Time+ -------- -------- --------+ PC2COINQ 1 2.912+ BE2LORDR 9 5.408+ BE2PCUST 1 1.141+

++ ADABAS Statistics+ Open user . . . . . . . : 0 Open user time. . . . . : 0.000+ Process ISN . . . . . . : 0 Process ISN time. . . . : 0.000+ Search. . . . . . . . . : 0 Search time . . . . . . : 0.000+ File operation. . . . . : 7 File operation time . . : 37.224+ Checkpnt/backout. . . . : 0 Checkpnt/backout time . : 0.000+ Misc request. . . . . . : 4 Misc request time . . . : 21.440+ End trans . . . . . . . : 0 End trans time. . . . . : 0.000+ Close user. . . . . . . : 0 Close user time . . . . : 0.000++ Database Requests Elapsed+ Time+ -------- -------- --------+ 004-007 8 40.506+ 004-006 1 6.240+ 004-005 1 6.642+ 004-004 1 5.245+



If you zoom on DATACOM Statistics from the Historical Transaction Detail display, a panel appears as shown in Figure 48 on page 126.

FIGURE 48. DATACOM Statistics (Accessed by Zoom)

If you zoom on IDMS Statistics from the Historical Transaction Detail display, a panel appears as shown in the following figure.

FIGURE 49. IDMS Statistics (Accessed by Zoom)

If you zoom on USREVNT1 Statistics from the Historical Transaction Detail display, a panel appears as shown in

++ DATACOM Statistics+ Add . . . . . . . . . . : 0 Add time. . . . . . . . : 0.000+ Backout . . . . . . . . : 0 Backout time. . . . . . : 0.000+ Count . . . . . . . . . : 0 Count time. . . . . . . : 0.000+ Delete. . . . . . . . . : 0 Delete time . . . . . . : 0.000+ Get next. . . . . . . . : 0 Get next time . . . . . : 0.000+ Locate generic. . . . . : 0 Locate generic time . . : 0.000+ Locate specific . . . . : 1 Locate specific time. . : 2.132+ Log operation . . . . . : 0 Log operation time. . . : 0.000+ Read. . . . . . . . . . : 12 Read time . . . . . . . : 4.557+ Release . . . . . . . . : 0 Release time. . . . . . : 0.000+ Select. . . . . . . . . : 0 Select time . . . . . . : 0.000+ Select set. . . . . . . : 0 Select set time . . . . : 0.000+ System/Other. . . . . . : 0 System/Other time . . . : 0.000+ Update. . . . . . . . . : 4 Update time . . . . . . : 1.200++ Database Requests Elapsed+ Time+ -------- -------- --------+ POH001 16 7.989+

++ IDMS Statistics+ Bind RU . . . . . . . . : 1 Bind RU time. . . . . . : 0.226+ Record operation. . . . : 6 Record operation time . : 12.210+ Area operation. . . . . : 0 Area operation time . . : 0.000+ Set operation . . . . . : 0 Set operation time. . . : 0.000+ Commit/Rollback . . . . : 0 Commit/Rollback time. . : 0.000+ Accept statistics . . . : 0 Accept statistics time. : 0.000+ Accept/Curr. key. . . . : 0 Accept/Curr. key time . : 0.000+ LRF . . . . . . . . . . : 0 LRF time. . . . . . . . : 0.000+ Proc/Logic. . . . . . . : 0 Proc/Logic time . . . . : 0.000+ Finish RU . . . . . . . : 1 Finish RU time. . . . . : 0.145++ Database Requests Elapsed+ Time+ -------- -------- --------+ MASTY01 6 12.210+

Task History 127


FIGURE 50. USREVNT1 Statistics (Accessed by Zoom)

If you zoom on SUPRA Statistics from the Historical Transaction Detail display, a panel appears as shown in Figure 51 on page 127.

FIGURE 51. SUPRA Statistics (Accessed by Zoom)

The elapsed time for an operation represents the time that the task issued the request until the time the request completed and CICS redispatched the task.

You can zoom on an individual file to see detailed statistics by individual type of call or request for a file (or database) by positioning the cursor on the line containing the file name and pressing PF11. The panel shown in the following figure appears.

++ USREVNMT1 Statistics+ ADD requests. . . . : 1 ADD time. . . . . . : 7.930+ DELETE requests. . . . : 1 DELETE time. . . . . . : 1.047+ BROWSE requests. . . . : 1 BROWSE time . . . . . : 0.000+ UPDATE requests. . . . : 1 UPDATE time . . . . . : 2.096+ READ requests. . . . : 1 READ time . . . . . : 2.097+ WRITE requests. . . . : 1 WRITE time . . . . . : 3.145+ OPEN requests. . . . : 1 OPEN time . . . . . : 19.997+ CLOSE requests. . . . : 1 CLOSE time . . . . . : 3.124+ DELAY requests. . . . : 1 DELAY time . . . . . : 1.049+++ USREVNT1 Requests Elapsed Average+ Resources Time Time+ --------- -------- ------- -------+ FILE1 5 19.303 3.860+ DBASE2 3 14.073 4.691+ RES3 2 3.828 7.657+

++ SUPRA Statistics+ Add . . . . . . . . . . : 0 Add time. . . . . . . . : 0.000+ Close . . . . . . . . . : 0 Close time . . . . . . : 0.000+ Delete . . . . . . . . : 0 Delete time . . . . . . : 0.000+ Find . . . . . . . . . : 0 Find time . . . . . . . : 0.000+ Open . . . . . . . . . : 0 Open time . . . . . . . : 0.000+ Read . . . . . . . . . : 0 Read time . . . . . . . : 0.000+ Release . . . . . . . . : 1 Release time . . . . . : 2.132+ Signoff . . . . . . . . : 0 Signoff time . . . . . : 0.000+ Signon . . . . . . . . : 0 Signon time . . . . . . : 0.000+ System/Other . . . . . : 12 System/Other time . . . : 4.557+ Write . . . . . . . . . : 0 Write time . . . . . . : 0.000++ Database Requests Elapsed+ Time+ -------- -------- --------+ MAINFILE 16 7.989+



FIGURE 52. Detail File Request Statistics Panel (Accessed by Zoom)

This panel shows statistics for each type of request, call, or command which accessed the file or database you selected.

File control statistics by filename are accumulated for EXEC level requests only. For function shipped requests, statistics are collected in the Application Owning Region (AOR) under the application transaction and in the File Owning Region (FOR) under the mirror transaction.

DL/I statistics are accumulated for both EXEC level and CALL level DLI to local, remote, and DBCTL databases. Local and remote database statistics display by DBD name. DBCTL databases display PSB name. For function shipped requests, statistics are collected in the AOR.

_____________ ZZONDVD VTM TDOCS01 V520/C SYSG 02/03/99 12:58:18> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down ===============================================================================> HISTORICAL FILE DETAIL FOR SELECTED TASK ONDV 06 DLI DETAIL BE2LORDR+ Transaction Detail for TINQ task number = 903++ DL/1 Statistics+ DBD Name . . . . . . . : BE2LORDR+ Get Unique . . . . . . : 0 Get Unique time . . . . : 0.000+ Get Next . . . . . . . : 0 Get Next time . . . . . : 0.000+ Get Next in Parent . . : 0 Get Next in Parent time : 0.000+ Get Hold Unique . . . . : 1 Get Hold Unique time . : 7.223+ Get Hold Next . . . . . : 8 Get Hold Next time . . : 0.370+ Get Hold Next in Parent : 0 GHN in Parent time . . : 0.000+ Insert . . . . . . . . : 0 Insert time . . . . . . : 0.000+ Delete . . . . . . . . : 0 Delete time . . . . . . : 0.000+ Replace . . . . . . . . : 0 Replace time . . . . . : 0.000===============================================================================

Task History 129

Historical Task Selection

Historical Task SelectionYou can limit the task history records displayed by specifying selection criteria. To specify selection criteria, select the History Record Selection option (B) on the History path or enter fast path H.B from any panel. The display to define the criteria is shown in the following figure.

FIGURE 53. Set Criteria for Selecting Historical Records Panel (H.B)

This panel shows the current settings for historical record selection. To change a setting, replace it with the new value. To erase a value, enter blanks.

Any changes to selection criteria take effect only for your OMEGAMON II session. They remain in effect until changed again or until you terminate your session.

________________ ZONDT VTM $CICSTOR V520/I SYSA 02/03/99 14:06:11> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-History Record View B-History Record Selection===============================================================================> SET CRITERIA FOR SELECTING HISTORICAL TRANSACTION RECORDS> To change selection criteria, enter over the current ones displayed below. ONDV SELECT+ Time values in seconds :: RESPONSE= .0 CPU= .0 DISPATCH= .0 SUSPEND= .0++ Date in MM/DD/YY and time in HH:MM:SS :: START-DATE=00/00/00 START-TIME=00:00:00 END-DATE=00/00/00 END-TIME=00:00:00++ Counts in integers :: STORAGE= 0 FILE= 0 DLI= 0 DB2= 0: ADABAS = 0 DATACOM= 0 IDMS= 0 SUPRA= 0++ To select only abended tasks; enter YES, NO or a specific abend code :: ABENDS=NO++ Maximum number of records to scan :: SCAN= 0++ Include only those transactions matching the following criteria :: INC-TRANS=’ ‘: INC-GROUPS=’ ‘: INC-TERMID=’ ‘: INC-USERID=’ ‘++ Exclude those transactions matching the following criteria :: EXC-TRANS=’ ‘: EXC-GROUPS=’ ‘: EXC-TERMID=’ ‘: EXC-USERID=’ ‘ + Reverse the display to show the newest transactions at the top (YES or NO) :: REVERSE=NO===============================================================================

Historical Task Selection


Time values can range from .1 to 999.9 seconds. Start and end dates select transactions based on their start and end date/time. A start date without a start time defaults to 12 midnight on that date. An end date without an end time defaults to 11:59 pm on that date. Entering a time without a date is ignored.

You can enter dates in European date format, if that format was specified in your user or installation profile. See the OMEGAMON II for CICS Configuration and Customization Guide for more information.

If you enter YES in the ABENDS field, any transactions that abended are selected. If you enter a specific abend, such as ASRA, any transactions that abended with that code are selected. If you enter NO, abend codes are not used in record selection.

The SCAN field limits the number of records OMEGAMON II retrieves to satisfy a request. Use this option to prevent excess response time when a selection criteria could possibly cause a very large number of records to be examined for inclusion.

For a record to be selected it must meet all the criteria specified by the above fields: time, date, counts, abends, and records.

In addition, inclusion and exclusion criteria are interpreted as follows:

n First records are selected only if they meet any inclusion criteria.n If no inclusion criteria are specified, then all records are selected.n Then, each record is excluded if it matches any of the exclusion criteria.

Enter items for inclusion or exclusion separated by a comma or space. If these items cannot fit on a single line, specify them as an OMEGAMON II group. See the “Group Definition and Activation” on page 325 for more information.

You can use the asterisk (*) as a wildcard character. All input text is converted to upper case.

The following examples illustrate how the selection criteria works.

INC-TRANS=’TX* SERT N*’

INC-TERMID=’N2* V2*’

This example selects transaction SERT, or those transactions beginning with either TX or N, or those transactions whose terminal ID begins with either N2 or V2.

INC-GROUPS=’1 2’

EXC-TRANS=’CEMT’

This example assumes group 1 is a transaction group defined as C* and group 2 is a terminal group defined as NT*. The example selects only those transactions with a terminal ID beginning with NT or a transaction ID beginning with C, but it excludes transaction ID CEMT.

The Reverse option only appears if your on-line historical data is saved in a VSAM dataset only (that is, you specified DATA_STORE_TYPE=FILEONLY in the ONLINE_VIEWER parameter of the global data area.) Refer to the OMEGAMON II for CICS Configuration and Customization Guide for more information.

Task History 131

Controlling Online Historical Viewing Collector (ONDV)

Controlling Online Historical Viewing Collector (ONDV)In order to view task-related historical data online, the online historical data viewing collector (ONDV) must be active. Also, you can dynamically select for which file or database products you want to collect statistics. There are four options on the Control menu (main menu option O) to activate, deactivate, and view the status of ONDV, and to control file statistics.

Historical collector statusTo display the current status of ONDV, select the ONDV Status, option (H) on the Control menu or enter fast path O.H from any menu system panel. The status appears as shown in the following figure.

FIGURE 54. Historical Collector Status Panel (O.H)

________________ ZCHSTAT VTM TDOCS01 V520/C SYSA 02/03/99 12:02:48> PF1 Help PF3 Back PF4 Main Menu > A-RTA On B-RTA Off C-RTA Status D-RTA Intervals E-RTA Scaling> F-ONDV On G-ONDV Off H-ONDV Status I-Bottleneck Ctl J-Wait Reasons> K-INTR Ctl L-IANL On M-IANL Off N-IANL Settings O-IANL Groups> P-Collection Q-Shutdown R-RLIM On S-RLIM Off T-RLIM Status===============================================================================> ONLINE HISTORICAL TRANSACTION VIEWING COLLECTOR STATUS ONDV STATUS+ ONDV Control Information+ Status . . . . . . . . : Active Data store wraparound . : 0+ Start time . . . . . . : 10:57:30 Start date . . . . . . : 02/03/99+ Data store type . . . . : File Display requests . . . : 0+ Data store size . . . . : 956K Xmem posts . . . . . . : 0+ Data store size (recs) : 921 Cycle time (seconds) . : 2+ Records received . . . : 15++ Function Elapsed CPU Paging+ Time Time+ -------- -------- -------- --------+ Initial 0.001 0.001 0+ Collect 0.277 0.079 0+ Display 0.000 0.000 0+ Wait 1:05:16 n/a n/a ===============================================================================



The control information fields displayed on this panel are:

The lower portion of the ONDV Status panel shows by function (collector component) the CPU usage, response time, and paging rate.

Starting and stopping the historical collectorYou can easily activate or deactivate ONDV by selecting the ONDV On option (F) or the ONDV Off option (G) on the Control Options path (main menu option O). Or you can enter fast paths O.F and O.G from any panel to start and stop ONDV.

Status Collector status which may be Active, Quiesce, Initial, Abended, Inactive, or Reply.

A status of Reply indicates that the allocated data store is incompatible with the collector version started. The collector will remain suspended until you enter a response to message OCO417 from the console.

Data store wraparound Number of wraparounds that occurred in the data store.

Start date/time Date and time that the collector was started.

Data store type DSPACE Dataspace only (MVS/ESA)

FILE Dataspace backed up by linear VSAM dataset (MVS/ESA)

FILEONLY Linear VSAM dataset only

FILEOCMP Linear VSAM dataset only with compression

Display requests Number of requests from the ONDV display.

Data store size Size of the data store in K bytes.

Xmem posts Number of times the collector was asked to retrieve data from CICS excluding the instances when the collector normally retrieves data in the default 2 second interval. If this exceeds 2 or 3, the buffers in CICS are becoming depleted because of a high transaction rate. If the data is not collected frequently enough from CICS, it can be lost. In this case, check the CICS SYSLOG messages signaling this event. To increase the number of buffers in CICS, reassemble the global module.

Index wraparound (if FILEONLY parameter has been set in the Global Data Area) Number of times the index area of the VSAM datastore has “wrapped” or been overlayed.

VSAM Dataset (if FILEONLY parameter has been set in the Global Data Area) Name of the VSAM dataset being used by ONDV as the repository for historical data.

Data store size (recs) Maximum number of records in the data store.

Cycle time Interval in seconds that the collector polls CICS to retrieve records.

Records received Number of records retrieved from CICS.

Task History 133


Controlling file level statisticsYou can dynamically control the collection of access statistics for VSAM, DLI, and third-party database products. For these products, you can decide whether you want only statistics by task or you also want to collect statistics by file or database. For DB2, only task statistics may be collected. For VSAM, task statistics are always collected if CICS Monitoring is active, but you may decide whether you want file statistics. Select the Collection Control option (P) on the Control Options path (main menu option O) or enter fast path O.P from any panel to access the Database Collection Control panel as shown in the following figure.

FIGURE 55. Control Database Collectors Panel (O.P)

This panel controls the collection of file statistics for online historical displays (ONDV) and SMF records. One line displays for each product specified in the global module. You can turn on or turn off monitoring for each product by overtyping the current value with ON or OFF.

You may collect task statistics without collecting file statistics. If you turn off task statistics, file statistics automatically turn off. If you want to turn on file statistics, you must also turn on task statistics.

File statistics for DB2 are not collected, but you may decide whether you want DB2 task statistics.

Task statistics for VSAM are collected as long as CICS Monitoring is active. Therefore, the task-level field for VSAM is only informational.

The columns Write to ONDV and Write to SMF refer only to file level statistics. Task level statistics are always written as long as task level monitoring is ON.

________________ ZCCOLL VTM TDOCS01 V520/C SYSG 02/03/99 12:45:55> PF1 Help PF3 Back PF4 Main Menu > A-RTA On B-RTA Off C-RTA Status D-RTA Intervals E-RTA Scaling> F-ONDV On G-ONDV Off H-ONDV Status I-Bottleneck Ctl J-Wait Reasons> K-INTR Ctl L-IANL On M-IANL Off N-IANL Settings O-IANL Groups> P-Collection Q-Shutdown R-RLIM On S-RLIM Off T-RLIM Status===============================================================================> CONTROL DATABASE COLLECTORS > To change status of a collector, enter ON or OFF over the current values> displayed below: COLL+ Product Task-lvl File-lvl Write to Write to+ Name Monitor Monitor ONDV SMF+ -------- -------- -------- -------- --------: VSAM ON ON ON ON: DB2 ON N/A N/A N/A: DLI ON ON ON ON: IDMS OFF OFF OFF OFF: ADABAS OFF OFF OFF OFF: SUPRA OFF OFF OFF OFF: DATACOM OFF OFF OFF OFF: USREVNT1 ON ON ON OFF===============================================================================



Bottleneck Analysis 135

Bottleneck Analysis

Chapter OverviewA significant part of CICS transaction response time consists of waiting for resources to become available or events to complete. In order to minimize response time, you must identify which resources are responsible for these waits. Bottleneck analysis is a diagnostic tool that analyzes and categorizes the resources responsible. By identifying those resources with the longest waits, bottleneck analysis allows you to direct your tuning efforts to areas with the most critical need.

Chapter Contents

How Bottleneck Analysis Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136

Data sampling and collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136Excluding tasks from analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136Customization procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136

Bottleneck Analysis Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137Main bottleneck analysis display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137Bottleneck analysis graphical summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138Bottleneck analysis group summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138Bottleneck analysis detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139

Wait Reasons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140Nondispatchable conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140Remote processing waits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144Dispatchable conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144

Operational Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145Bottleneck analysis control display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146

Enqueues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149Main enqueue display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149Displaying enqueue resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150Enqueue detail display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152

8

How Bottleneck Analysis Works


How Bottleneck Analysis WorksOMEGAMON II’s bottleneck analysis feature samples CICS task data at a specified interval, conducts statistical analyses of the accumulated data, and displays pertinent wait condition information. You can view the information numerically, graphically, and at several levels of granularity.

Data sampling and collectionOMEGAMON II samples CICS data at a default interval of 2 seconds to determine the current state of all the tasks. This interval is known as the cycle time or sampling interval. In order for the sample to be representative, it should contain at least 30 observations. Smaller samples may not be statistically significant and should not be used.

For each wait reason, OMEGAMON II collects the sampling data into short- and long-term intervals. The default settings are 10 minutes for the short-term interval and 30 minutes for the long-term interval. As a short-term interval expires, it is refreshed. As a long-term interval expires, data samples collected during the latest short-term interval are rolled into it.

Excluding tasks from analysisInternal CICS tasks are excluded to ensure that the results reflect the state of CICS applications. These internal tasks have the following transaction IDs:

n CSSY n CSJC n CVST n CSSX n CSGX n CSNC n DSNC You can also exclude additional tasks as well as wait reasons from bottleneck analysis. To exclude tasks, refer to the bottleneck analysis parameter described in the OMEGAMON II for CICS Configuration and Customization Guide. To exclude wait reasons, refer to the wait reason parameter described in the same manual. You can also exclude wait reasons in the menu system by selecting the Wait Reasons option (J) on the Control Options path or entering fastpath O.J from any panel.

Customization proceduresYou can permanently change a number of bottleneck analysis parameters, so that they are in effect each time you start OMEGAMON II. These include the sampling interval, the short- and long-term interval, the resource types that are displayed, wait reasons, and transactions to exclude from analysis. Refer to “Customizing the Global Data Area” in the OMEGAMON II for CICS Configuration and Customization Guide.

If you want to temporarily change the above settings, refer to “Operational Considerations” on page 145. In this case, the changes take effect when they are made and remain in effect until OMEGAMON II is recycled.


Bottleneck Analysis Displays

Bottleneck Analysis DisplaysThis section describes the principal bottleneck analysis displays and their features, and explains how to use them.

Main bottleneck analysis displayTo access bottleneck analysis, select the Bottlenecks option (B) on the Bottlenecks path or enter fastpath B.B from any panel. The Bottlenecks panel appears as shown in the following figure.

FIGURE 56. Bottlenecks Panel (B.B)

This panel shows CICS wait conditions that are degrading the CICS workload. Note that wait reasons are different for CICS/ESA and CICS/MVS. Although every CICS wait reason is detected, only those specified with On appear. Select option J (Wait Reasons) on the Control Options menu to specify On or Off for each wait reason (fastpath O.J).

If *OVRFLW* is displayed, insufficient variable buckets have been defined. Consider increasing the variable bucket limit using the VARIABLE_BUCKETS parameter of the DEX command (see “Bottleneck analysis control display” on page 146) on the BOTTLENECK_OPTIONS parameter in the global data area.

________________ ZBPDEX VTM TDOCS01 V520/C SYSG 02/03/99 9:57:25> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Bottleneck Graph B-Bottlenecks C-Group Graph D-Group Bottlenecks> E-Impact Analysis F-Impact Profile G-Impact Detail H-Enqueues===============================================================================> BOTTLENECKS PDEX++ Resource Resource+ Type Name Short Term Information Long Term Information+ -------- -------- ---------------------- ----------------------+ % 0_______ 50_______100 % 0_______ 50_______100+ DISPATCH QR_TCB 13 |-> . . . .| 13 |-> . . . .|+ FCBFWAIT *TOTAL* 11 |-> . . . .| 11 |-> . . . .|+ DEG (11) |-> . . . .| (11) |-> . . . .|+ FCIOWAIT *TOTAL* 13 |-> . . . .| 13 |-> . . . .|+ DEG (13) |-> . . . .| (13) |-> . . . .|+ FCPSWAIT *TOTAL* 26 |----> . . .| 26 |----> . . .|+ DEG (17) |--> . . . .| (17) |--> . . . .|+ KCCOMPAT SINGLE 14 |-> . . . .| 14 |-> . . . .|+ RUNNING RUNNING 14 |-> . . . .| 14 |-> . . . .|++ Samples . . : 178 Samples . . : 178+ Elapsed . . : 7:44 MN Elapsed . . : 17:45 MN+ Interval . : 10:00 MN Interval . : 30:00 MN===============================================================================



Bottleneck analysis graphical summaryThe same information can be displayed graphically by selecting the Bottleneck Graph option (A) on the Bottlenecks path or entering fastpath B.A as shown in the following figure.

FIGURE 57. Bottleneck Graph Panel (B.)

This panel displays the long-term wait reasons in order of descending percentage. If the number of samples is not sufficient, OMEGAMON II displays a message.

For terminals with extended color, the display appears in the colors set for levels 5, 6 and 7. The graph appears in level 5 color, the wait condition labels in level 7 color, and the lines pointing from the wait condition labels to the graph in level 6 color.

Bottleneck analysis group summaryBy selecting the Group Bottlenecks option (D) on the Bottlenecks path or entering fastpath B.D, you can display the wait reasons for only those transactions belonging to a particular transaction, program or terminal group. Bottleneck analysis does not support VTAM LU groups. See “Group Definition and Activation” on page 325 for more information on creating and maintaining groups.

________________ ZBDEXG VTM CICSP01 V520/I SYSA 02/03/99 16:11:13> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Bottleneck Graph B-Bottlenecks C-Group Graph D-Group Bottlenecks> E-Impact Analysis F-Impact Profile G-Impact Detail H-Enqueues================================================================================> BOTTLENECK GRAPH IPRO PDEX+ The largest impactor to CICSP01 is KC: Suspend by CICS+ |||||||||||||||||||||||||||||||||||||||||||||||+ |||||||||||||||||||||||| ------------------------+ ||||||||||||||||||||||||<---------------------- 48%-| KC: Suspend by CICS |+ |||||||||||||||||||||||| ------------------------+ |||||||||||||||||||||||||||||||||||||||||||||||+ ||||||||||||||||||||||||||||||||| -----------------------+ |||||||||||||||||||||||||||||||||<------------- 29%-| FC: DASD I/O |+ ||||||||||||||||||||||||||||||||| -----------------------+ |||||||||||||||||||||||||||||||||||||||||||||||+ || ||||||||||||||||||||||||||||| ------------------------+ || CICSP01 |||||||||||||||||||||||||||||<------ 13%-| DS: Task dispatched |+ || ||||||||||||||||||||||||||||| ------------------------+ |||||||||||||||||||||||||||||||||||||||||||||||================================================================================



Bottleneck analysis detailFor more detail about a wait reason listed on the Bottlenecks panel (fastpath B.B), place the cursor on the line containing the resource type and press PF11. The following figure shows the Wait Reason Detail display produced.

FIGURE 58. Wait Reason Detail Panel (Accessed by Zoom)

This panel shows you details describing the wait as well as which of your defined groups are affected by a particular wait as follows:

ID for BLST Four character code that refers to the wait reason. You can suppress a wait reason from appearing on a display by using this code. See “Operational Considerations” on page 145 for more information.

CICS issuing module Name of the CICS module that issues this wait, or MULTIPLE, if more than one CICS module can issue this wait.

Resource type and name Described in “Wait Reasons” on page 140.

Dispatcher call In CICS/ESA when you issue a wait request, the dispatcher performs a specific type of wait. For example, WAITOLDC maps onto the DFHKC wait type. See IBM’s CICS Problem Determination Guide for further information.

Task type In CICS/ESA this indicates the category of tasks (User, System, or Both) that can be in this type of wait. See IBM’s CICS Problem Determination Guide for more information.

________________ ZZWAIT VTM TDOCS01 V520/C SYSG 02/03/99 9:58:42> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down ===============================================================================> WAIT REASON DETAIL PDEX FCPS 04F5C848+ Wait Reason Detail Display+ ID for BLST . . . . . . : FCPS CICS issuing module . . : DFHFCVR+ Resource type . . . . . : FCPSWAIT Resource name . . . . . : ********+ Dispatcher call . . . . : WAITOLDC Task type . . . . . . . : User+ Wait reason description : FC: Private string++ Short Term Groups 01-06: 0% 0% 0% 25% 0% 0%+ ( 30%) Groups 07-12: 0% 0% 0% 0% 0% 25%+ Groups 13-18: 0% 0% 0% 0% 0% 0%+ Groups 19-24: 0% 0% 0% 0% 0% 0%+ Groups 25-30: 0% 0% 25% 25% 0% 0%++ Long Term Groups 01-06: 0% 0% 0% 25% 0% 0%+ ( 30%) Groups 07-12: 0% 0% 0% 0% 0% 25%+ Groups 13-18: 0% 0% 0% 0% 0% 0%+ Groups 19-24: 0% 0% 0% 0% 0% 0%+ Groups 25-30: 0% 0% 25% 25% 0% 0%===============================================================================

Wait Reasons


Wait ReasonsEach wait reason consists of a resource type and name. It is version specific. For CICS/MVS, OMEGAMON II analyzes the system environment for each task to determine the wait reason. For CICS/ESA, OMEGAMON II uses the wait reasons supplied by CICS in the task’s DTA.

Wait reasons for CICS/MVS appear in the following table. For CICS/ESA, refer to IBM’s CICS/ESA Problem Determination Guide for a complete description.

Nondispatchable conditions

DB2-thrd DB2 thread wait.

Percentage of degradation caused by tasks waiting for a DB2 thread.

DB2-Wait DB2 wait.

Percentage of degradation caused by tasks waiting for completion of a DB2 request.

Dump-ctl DUMP control.

Percentage of total degradation caused by tasks waiting for a dump control request to complete.

ENQ-Susp ENQ wait.

Percentage of degradation caused by each task waiting for resources via DFHKC TYPE=ENQ. This is followed by a list of individual ENQ names and the percentage of degradation caused by tasks waiting for each ENQ. If the ENQ name exceeds 8 characters, only the first 8 characters are displayed.

File-I/O I/O event wait.

Percentage of degradation caused by tasks waiting for FILE I/O to complete. This is followed by a list showing the percentage degradation caused by tasks waiting by FILE ID. The file I/O wait percentages are broken down by VSAM, BDAM, and individual database products. If you use a third- party database, this wait reason will appear with the file name you specified when the database transaction becomes nondispatchable.

File-st File state change.

CICS task is waiting for a file to be opened or dynamically allocated.

Intv-ctl Interval control.

Percentage of degradation caused by tasks waiting for completion of requests issued through DFHIC services

Jrnl-Ctl Journal control.

Percentage of degradation caused by tasks waiting for a journal control request to complete. This is followed by a list indicating the journal ID and the percentage of degradation caused by tasks waiting.


Wait Reasons

LSR-Buff LSR buffer wait.

Percentage of degradation caused by tasks waiting for completion of a VSAM file control request that had to wait for an available buffer within the LSR pool. If this figure is large, it indicates that the LSR pool is too small and forced writes of modified buffers are being made in order to read in more data.

LSR-strn LSR string wait.

Percentage of degradation caused by tasks waiting for completion of a VSAM file control request that had to wait for an available string to the LSR pool.

Map-Load Map load wait.

Percentage of total degradation caused by tasks waiting for a BMS map to be loaded.

Pgrm-Ctl PC load wait.

Percentage of degradation caused by tasks waiting for nonresident programs to be loaded.

Note: In an MRO environment, the terminal-owning region shows two very fast transactions with PC LOAD as the major degradation. The transaction processing region reflects normal processing. This is due to the CICS implementation of MRO in using the terminal control program (DFHTCP) to write to the CICS mirror in the destination region.n this appears as one short transactionn there is no activity while the destination region does its processingn there is another short transaction as the terminal control program does

the readn then, the output goes back to the terminal

RSLC-xxx External RSLC.

CICS task is waiting for approval from an external security manager, such as RACF, to access a resource protected by the resource security level checking specification.

SC-Susp Storage control suspended.

Percentage of degradation caused by tasks that were suspended by the storage control program due to a shortage of storage.

Start JES JES interface.

CICS task is waiting for the completion of a JES function requested by the CICS interface with JES.

STRING Get string wait.

Percentage of degradation caused by tasks waiting for completion of a VSAM file control request that had to wait for an available string.

CICS waits for a read-only string, if it is a read-only request and no strings are available.

Wait Reasons


STRNOG String wait.

Percentage of degradation caused by tasks waiting for completion of a VSAM file control request that had to wait for an available string that is not read-only (STRNOG).

TC-BMS Terminal control (BMS).

Percentage of degradation caused by tasks waiting for terminal input using the services of basic mapping support.

TC-I/O Terminal control.

Percentage of degradation caused by tasks waiting for terminal input. These are generally conversational transactions.

Tmp-Stor Temporary storage wait.

Percentage of total degradation caused by tasks waiting for a temporary storage operation to complete. The wait is due to the actual I/O required for the operation, not a suspend due to a shortage of resources.

Transdat Transient data wait.

Percentage of total degradation caused by tasks waiting for a transient data request to complete.

TS-Susp Temporary storage suspended.

Total percentage of degradation caused by tasks suspended by the temporary storage program due to a shortage of temporary storage.

Wait-LST List of ECBs.

Percentage of degradation caused by tasks that issued a DFHKC TYPE=WAIT,DCI=LIST request. This shows a wait for the completion of more than one event.

Wt-Amaxt AMAXT(total) wait.

Percentage of degradation caused by tasks that have become nondispatchable due to an active max task condition.

Wt-CICS CICS event wait.

Percentage of degradation caused by tasks waiting for a CICS system event. This is displayed when a DFHKC TYPE=WAIT,DCI=CICS request is issued. This request is issued by many of the CICS management modules, and is intended as a means of serializing certain resources.

Wt-Cmaxt CMAXT(class) wait.

Percentage of degradation caused by tasks that became nondispatchable due to a class active max task condition.

Wt-DataI Data interchange.

Percentage of degradation caused by tasks waiting for completion of a data interchange request.

Wt-DLI DLI wait.

Percentage of degradation caused by tasks waiting for completion of a DLI request. This is followed by a list indicating the percentage of degradation for all of the DLI wait reasons.


Wait Reasons

Wt-Other Undetermined wait.

Percentage of degradation caused by tasks that are nondispatchable for reasons that cannot be determined.

Most Wt-Other wait reasons are given for suspended user tasks that are running under CEDF. In this case, the CEDF transaction takes control and suspends the user task each time the user task issues an EXEC CICS command. CEDF resumes the suspended user task when the user continues the command.

Wt-Page Anticipatory page.

Percentage of degradation caused by tasks waiting due to anticipatory paging.

Wt-Pflt Page fault wait.

Percentage of degradation caused by tasks waiting due to a CICS page fault.

Wt-Sbtsk Wait on a subtask.

Percentage of degradation caused by tasks waiting for the completion of an MVS subtask. This event does not include waits resulting from VSAM, external security, or JES spool requests.

Wt-Sin Single event wait.

Percentage of degradation caused by tasks that issued a DFHKC TYPE=WAIT,DCI=SINGLE request. This shows a wait for the completion of a single event.

Wt-SRB SRB mode process.

Percentage of degradation caused by tasks waiting for the completion of services that were scheduled by CICS to operate in SRB mode. An example of a service performed in SRB mode is the VTAM high performance option.

Xclusive CI exclusive control.

Percentage of degradation caused by tasks waiting for completion of a VSAM file control request that had to wait for the control interval (CI) to be free. CICS attempts to ENQ on the key field of a record (if exclusive control is specified in the FCT, which is the default) and then pass the request to VSAM. If another task is updating a different record in the same CI, the task waits.

Wait Reasons


Remote processing waitsThe following wait reasons can be displayed in either MRO or ISC environments:

Dispatchable conditions

ISC-Sess Session Wait.

MRO-Sess Session Wait.

MRO-Fnsh Function Ship.

ISC-Fnsh Function Ship.

MRO-Mirr Mirror Wait.

ISC-Mirr Mirror Wait.

MRO-TrRT Transaction Route.

ISC-TrRT Transaction Route.

MRO-DTP Distributed Transaction Processing.

ISC-DTP Distributed Transaction Processing.

MRO-RTC Remote TC-I/O.

ISC-RTC Remote TC-I/O.

>ACTIVE< Executing.

A task was executing when the sample was taken.

Wt-Dspch Dispatching wait.

Percentage of total degradation caused by tasks currently dispatchable, but waiting for the CPU.


Operational Considerations

Operational ConsiderationsYou can define parameters that affect the collection and display of bottleneck analysis data either in the global data area or from an OMEGAMON II session. Changes to the global data area are effective for all CICS regions monitored after the global data area is changed. Changes from an OMEGAMON II session are effective only for the duration that OMEGAMON II is monitoring that CICS region.

For more information on the global data area, see the OMEGAMON II for CICS Configuration and Customization Guide.

You can make the following changes from an OMEGAMON II session:

n starting and stopping bottleneck analysis collection

n clearing the short- and long-term statistics

n changing the cycle timer that determines how often OMEGAMON II samples the CICS tasks

n changing the threshold to determine which wait reasons are displayed

n changing the display indicators to determine which wait reasons are displayed

n changing the short- and long-term collection intervals



Bottleneck analysis control displayTo display the bottleneck analysis control panel as shown in the following figure, select the Bottleneck Control option (I) on the Control Options menu or enter fastpath O.I from any panel.

FIGURE 59. Bottleneck Analysis Control Panel (O.I)

To start or stop collection, enter Start or Stop in place of SET next to DEX on the panel.

To change the cycle timer, short-term interval, long-term interval, or display threshold, enter the new values over the current ones, following SET.

n The cycle time is expressed in seconds with a range from 0.1–9.9.

n The short-term interval is expressed in minutes with a range from 0–999. A value of zero clears the bucket on every timer cycle.

n The long-term interval is expressed in minutes with a range from the short-term interval to 999. A value of 0 prevents the bucket from being cleared. A value of CLEAR for either interval clears the buckets.

n The threshold is expressed as a percent from 1–99.

n The variable bucket count is the number of variable buckets that bottleneck analysis has allocated.

n The variable bucket limit is the maximum number of variable buckets that bottleneck analysis can allocate. The value may range from 0–32767. If bottleneck analysis runs out of variable buckets, overflow buckets are used. These overflow buckets do not distinguish among different resource names, and display as *OVRFLW* by PDEX.

________________ ZCDSET VTM TDOCS22 V520./I SYSG 08/16/99 15:51:36> PF1 Help PF3 Back PF4 Main Menu > A-RTA On B-RTA Off C-RTA Status D-RTA Intervals E-RTA Scaling> F-ONDV On G-ONDV Off H-ONDV Status I-Bottleneck Ctl J-Wait Reasons> K-INTR Ctl L-IANL On M-IANL Off N-IANL Settings O-IANL Groups> P-Collection Q-Shutdown R-RLIM On S-RLIM Off T-RLIM Status===============================================================================> BOTTLENECK ANALYSIS CONTROL > Current bottleneck analysis status displays below. To start or stop the> collector, enter START or STOP in place of SET. To modify cycle timer,> short-term interval, long-term interval, or display threshold, enter the new> values over the current ones following SET. DEX SET CYCLE=2.0 SHORT=10 LONG=999 THRESH=10 VBS=1000+ Bottleneck Analysis Control Information+ Status . . . . . . . . : Active+ Start time . . . . . . : 15:29:06 Start date . . . . . . : 08/16/99+ Short term interval . . : 10 MN Long term interval . . : 999 MN+ Cycle timer . . . . . . : 2.0 SEC Display threshold . . . : 10%+ Variable bucket count . : 0 Variable bucket limit . : 1000+ Short term elapsed time : 22 SEC Long term elapsed time : 22 SEC+ Short term cycles . . . : 12 Long term cycles . . . : 12===============================================================================



n If you change the short- or long-term interval, the accumulators will be cleared.

To view and change the display indicators for the wait reasons, select the Wait Reasons option (J) on the Control Options menu or enter fastpath O.J from any panel. A partial display of wait reasons for a CICS/ESA system is shown in the following figure.

FIGURE 60. Control Bottleneck Analysis Wait Reason Buckets Panel (O.J)

________________ ZCDLST VTM $CICSTOR V520/I SYSA 02/03/99 12:57:59> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-RTA On B-RTA Off C-RTA Status D-RTA Intervals E-RTA Scaling> F-ONDV On G-ONDV Off H-ONDV Status I-Bottleneck Ctl J-Wait Reasons> K-INTR Ctl L-IANL On M-IANL Off N-IANL Settings O-IANL Groups> P-Collection Q-Shutdown R-RLIM On S-RLIM Off T-RLIM Status===============================================================================> CONTROL BOTTLENECK ANALYSIS WAIT REASON BUCKETS BLST+ BLST On/ Resource Resource Issuing Wait Reason+ ID Off Type Name Module Description+ ---- --- -------- -------- -------- ------------------------: SY1W ON (none) (none) DFHDUIO DU: Dump dataset I/O: SY2W ON (none) (none) DFHTISR TI: Timer service rq: DLCN ON (none) DLCNTRL DFHDBCT DBCTL: Work element: DLCO ON (none) DLCONECT DFHDBCON DBCTL: Connection: DMUT ON (none) DMWTQUEU DFHDMWQ DM: Work queue: LMQU ON (none) LMQUEUE DFHLMLM LM: Lock request: TCAL ON ALLOCATE (varies) DFHALP TC: Session allocate: TDAB ON any_MBCB (varies) DFHTDSUB TD: I/O Buffers: TDAR ON any_MRCB (varies) DFHTDSUB TD: VSAM String: DLIN ON AP_INIT CSADLECB DFHSII1 AP: DLI Restart: TCEC ON AP_INIT ECBTCP DFHAPSIP AP: TCP Synchronize: DMEC ON AP_INIT SIPDMTEC DFHAPSIP AP: DM Synchronize: TCVC ON AP_INIT TCTVCECB DFHSII1 AP: TC Restart: CSAS ON AP_QUIES CSASSI2 DFHSTP AP: Stage 2 quiesce: SHEC ON AP_QUIES SHUTECB DFHSTP AP: Domain quiesce: STPD ON AP_TERM STP_DONE DFHAPDM AP: STP Complete: CCST ON CCSTWAIT VSMSTRNG DFHCCCC CC: VSAM string: CCV1 ON CCVSAMWT ASYNRESP DFHCCCC CC: Asynch request: CCV2 ON CCVSAMWT EXCLOGER DFHCCCC CC: Exception logger: DBCT ON DBCTL DLSUSPND DFHDBSPX DBCTL: Suspend: DBXE ON DBDXEOT (none) DFHDXSTM DBCTL: XRF uncond: DBXI ON DBDXINT (none) DFHXSTM DBCTL: XRF interval: TCCO ON DISPATCH CO_TCB UNKNOWN DS: Concurrent TCB: TCQR ON DISPATCH QR_TCB UNKNOWN DS: Quasi-reent TCB: TCRO ON DISPATCH RO_TCB UNKNOWN DS: Resource own TCB: DLIW ON DLI (varies) DFHDLR DLI: Initialization: DLSU ON DLSUSPND DBCTL DFHDBSPX DBCTL: DLI Request: DSHA ON DS_HELD AMXT UNKNOWN DS: AMXT Bound: DSHM ON DS_HELD MXT UNKNOWN DS: MXT Bound: FCBF ON FCBFWAIT (varies) DFHFCVR FC: VSAM Buffer



You can control whether bottleneck analysis displays statistics for a particular wait reason by entering On or Off in the On/Off column next to the Resource Type. This option affects the display characteristics, not the actual collection of data.

For more information on resource types in CICS/MVS, see “Wait Reasons” on page 140. For CICS/ESA, see the IBM CICS/ESA Problem Determination Guide for a complete description.

Ten buckets are reserved for Third Party Product Support (TPPS) products. These buckets have BLST IDs ZTP0 through ZTP9. The first third party product that incurs a wait in a specific CICS region gets ZTP0; the next third party product to incur a wait gets ZTP1, and so on.


Enqueues

EnqueuesAn enqueue is a request to the CICS enqueue service, allowing you to serialize access to a resource or address. This technique is useful when, for example, you need to prevent concurrent database or file updates or maintain single threads in parts of a reentrant program’s execution.

OMEGAMON II’s enqueue display allows you to determine the type and number of enqueues waiting in the system, and their impact on CICS system performance.

Main enqueue displayTo access information on enqueues as shown in the following figure, select the Enqueues option (H) on the Bottlenecks path or enter fastpath B.H from any panel.

FIGURE 61. Enqueues with Tasks Waiting Panel (B.H)

This screen lists all tasks currently waiting on an enqueue held by another task. You can use it to quickly determine whether one or more tasks are causing degradation due to enqueue wait. If a task is listed multiple times in the Owning task columns, then that task may be causing enqueue degradation.

________________ ZBENQU VTM TDOCS15 V520/C SYSG 02/03/99 10:49:58> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Bottleneck Graph B-Bottlenecks C-Group Graph D-Group Bottlenecks> E-Impact Analysis F-Impact Profile G-Impact Detail H-Enqueues===============================================================================> ENQUEUES WITH TASKS WAITING> To display all enqueue resources, enter RESOURCE=* after ENQ. For a summary> of enqueues matching a resource, enter RESOURCE=cccccccc after ENQ. For> enqueue detail, place the cursor on your choice and press PF11. ENQ+ Number of tasks selected: 4 Skipped: 0+ Tran Task Enqueue Owning Owning Owning Owning+ ID Number Resource Tran ID Task No. Res Type Res Name+ -------- -------- -------- -------- -------- -------- --------+ OEN2 47 ENQWAIT OEN2 55 EKCWAIT SINGLE+ OEN2 48 ENQWAIT OEN2 55 EKCWAIT SINGLE+ OEN2 49 ENQWAIT OEN2 55 EKCWAIT SINGLE+ OEN2 50 ENQWAIT OEN2 55 EKCWAIT SINGLE===============================================================================

Enqueues


In the above figure, the fields are defined as follows:

You can often use the owning resource type and name data as a debugging step to determine if the enqueue problem is a symptom of some other bottleneck in your system.

Displaying enqueue resourcesThe top portion of the display shown in Figure 61 on page 149 contains instructions for displaying enqueues. When you use the ENQ statement with the RES parameter, you get a list of names or addresses for which an enqueue has been issued. You can use the display to either identify enqueues that have many tasks waiting or to obtain more specific information on an enqueue.

If you want to display all enqueues in the system, enter RES=* after the ENQ statement. You get a display resembling that shown in Figure 62 on page 151. Note that the Resource Length field is the number of characters in the resource name. A plus sign (+) in the Enqueue Resource column indicates that the resource name is composed of more than 8 characters.

If you want to display subgroups of enqueues, you can use the asterisk as a wildcard character. For example,

RES=AB*

displays all enqueued resources beginning with the string AB.

Tran ID Transaction ID of the task waiting for the enqueue.

Task Number Number of the task waiting for the enqueue.

Enqueue Resource First 8 characters of the enqueue name or address.

Owning Tran ID Transaction ID of the task currently holding the enqueue.

Owning Task Number Number of the task holding the enqueue.

Owning Resource Type Type of resource that the owning task is currently waiting for.

Owning Resource Name Resource that the owning task is waiting for.


Enqueues

FIGURE 62. Enqueues with Tasks Waiting Panel Using RES=* (B.H)

________________ ZBENQU VTM TDOCS15 V520/C SYSG 02/03/99 10:52:13> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Bottleneck Graph B-Bottlenecks C-Group Graph D-Group Bottlenecks> E-Impact Analysis F-Impact Profile G-Impact Detail H-Enqueues===============================================================================> ENQUEUES WITH TASKS WAITING> To display all enqueue resources, enter RESOURCE=* after ENQ. For a summary> of enqueues matching a resource, enter RESOURCE=cccccccc after ENQ. For> enqueue detail, place the cursor on your choice and press PF11. ENQ RES=*+ Number of enqueues selected: 4 Skipped: 0+ Enqueue Resource Owning Owning Owning Owning Waiting+ Resource Length Tran ID Task No. Res Type Res Name Tasks+ -------- -------- -------- -------- -------- -------- --------+ ENQWAIT 7 OEN2 49 EKCWAIT SINGLE 1+ ENQWAI + 9 OEN2 49 EKCWAIT SINGLE 0+ 80148561 n/a OEN2 49 EKCWAIT SINGLE 0+ 80148568 n/a OEN2 49 EKCWAIT SINGLE 0===============================================================================

Enqueues


Enqueue detail displayTo obtain detailed information on an enqueue resource, move your cursor to the resource you want and press PF11. The panel shown in the following figure appears.

FIGURE 63. Enqueue Resource Detail Panel (Accessed by Zoom)

You can select any task on the display and use the zoom key (PF11) to obtain more information on a task. For example, you may want to zoom on the owning task to uncover more information on a problem source. For more information on the task detail display see “Task Detail” on page 91.

You can also zoom on the QEA Address, the control block that describes the enqueue. In this case, a dump of that control block displays.

________________ ZZENQ VTM TDOCS15 V520/C SYSG 02/03/99 10:42:19> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ===============================================================================> ENQUEUE RESOURCE DETAIL ENQ QEA=050A8030++ QEA address . . . . . . : 050A8030 Waiting tasks . . . . . : 11+ Resource type . . . . . : Variable Resource length . . . . : 7+ Enqueue resource (char) : ENQWAIT++ Tran Task Task Resource Resource+ ID Number Status Type Name+ -------- -------- -------- -------- --------+ OEN2 44 Owning EKCWAIT SINGLE+ OEN2 45 Waiting KC_ENQ ENQWAIT+ OEN2 46 Waiting KC_ENQ ENQWAIT+ OEN2 51 Waiting KC_ENQ ENQWAIT+ OEN2 52 Waiting KC_ENQ ENQWAIT+ OEN2 53 Waiting KC_ENQ ENQWAIT+ OEN2 54 Waiting KC_ENQ ENQWAIT+ OEN2 55 Waiting KC_ENQ ENQWAIT+ OEN2 47 Waiting KC_ENQ ENQWAIT+ OEN2 48 Waiting KC_ENQ ENQWAIT+ OEN2 49 Waiting KC_ENQ ENQWAIT+ OEN2 50 Waiting KC_ENQ ENQWAIT===============================================================================

Impact Analysis 153

Impact Analysis

Chapter OverviewImpact analysis extends the diagnostic capabilities of bottleneck analysis. It identifies workloads that run on MVS and compete with CICS for MVS resources. These workloads can be batch jobs, started tasks, TSO users, other CICS regions, or the CICS region itself. Whereas bottleneck analysis locates the sources of performance degradation within a CICS region, impact analysis assesses the effect of MVS or other address spaces on a CICS region.

OMEGAMON II’s impact analysis displays identify the main sources of impact and describe their effects on CICS. This allows you to take prompt action to reduce competing workloads and improve CICS performance.

Chapter Contents

How Impact Analysis Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154

Starting and Stopping Impact Analysis Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155Impact Analysis Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156

Display parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156Productivity analysis and interval description area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157Display body . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157Impact detail display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

Workload Impact Profile (IPRO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161Adjusting Collection and Display Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163

Controlling the sampling interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163Impact analysis time-out facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164

9

How Impact Analysis Works


How Impact Analysis WorksImpact analysis monitors selected CICS regions at periodic intervals and determines which of the following three execution states categorize each observation.

After activating the impact analysis collector, allow accumulation of enough intervals (at least 30), so that the data displayed is statistically valid.

Productive CICS is performing useful work, such as using CPU or performing I/O.

Unproductive CICS is ready but unable to perform work. If CICS must wait for an MVS resource that another address space is using, that address space is said to be contending with CICS. Impact analysis shows it as affecting CICS performance. When CICS is unproductive, impact analysis identifies the specific address spaces that are using the resources for which CICS is waiting. Examples of unproductive states are CPU dispatching waits and time spent queued for I/O. This option displays as Contention.

Other CICS is not performing work due to normal reasons. OMEGAMON II disregards these states, since they do not indicate performance degradation. This option is not shown in impact analysis displays. Waiting for work and STIMER are examples of idle states.

Impact Analysis 155

Starting and Stopping Impact Analysis Collection

Starting and Stopping Impact Analysis CollectionTo use the impact analysis displays, you must turn the feature on. Options Impact Analysis On (L) and Impact Analysis Off (M) on the Control Options menu start and stop impact analysis collection (fast paths O.L and O.M).

Impact Analysis Displays


Impact Analysis DisplaysYou access impact analysis from the main menu through the Bottlenecks path (main menu option B). Options E, F, and G on the Bottlenecks menu allow you to invoke the three types of impact analysis displays: Overview, Summary, and Detail (fast paths B.E, B.F, and B.G).

All impact analysis displays follow the same basic format. The following figure shows a sample Summary display. Descriptions of its main parts follow.

FIGURE 64. Workload Impact Analysis Panel (B.E)

Display parametersThe first row of the impact analysis screen is the input options area (beneath the menu options and panel title).

IANL CICSA IAST=.9 IATH=5 IACS=1 IACL=5

Immediately following the IANL statement is the name of the region being analyzed. On the right are the collection and display parameters in effect. In this example, the parameters are set as follows:

n Sampling interval (IAST) is .9 seconds.n Plot threshold (IATH) is 5%.n Short-term interval (IACS) is 1 minute.n Long-term interval (IACL) is equal to 5 short-term intervals.

“Adjusting Collection and Display Parameters” on page 163 explains these parameters and their default settings.

________________ ZBIANL VTM $CICSTOR V520/I SYSA> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-Bottleneck Graph B-Bottlenecks C-Group Graph D-Group Bottlenecks> E-Impact Analysis F-Impact Profile G-Impact Detail H-Enqueues===============================================================================> WORKLOAD IMPACT ANALYSISIANL CICSA IAST=.9 IATH=5 IACS=1 IACL=5 Productive/Contention/Other | 10.8% 83.7% 5.5% | | 38.7% 52.5% 8.8% | Contending Address Spaces |Short (3:24M,88) | |Long (13:24M,361) | ----------------------------+-1-2-3-4-5-6-7-8-9-+ +-1-2-3-4-5-6-7-8-9-+ *Total Contention* *83.7*|------======>>>>> |*52.2*|------====> | *Self-Contention* 10.2|-> . . . . . . . . | 7.9|-> . . . . . . . . | RELOADDB (J1208) PG3 37.5|-----=>. . . . . . | 0.0| . . . . . . . . . | TESTCICS (S1366) PG5 13.3|-->. . . . . . . . | 11.0|-> . . . . . . . . | USER01 (T0934) PG2 0.0| . . . . . . . . . | 15.3|-->. . . . . . . . | System 22.7|---->. . . . . . . | 18.3|---> . . . . . . . |

Impact Analysis 157


Productivity analysis and interval description areaThe following two rows of the display show productivity analysis data, collection elapsed times, and the number of samples collected.

Productive/Contention/Other | 10.8% 83.7% 5.5% | | 38.7% 52.5% 8.8% |

| Short (3:24M,88) | |Long (13:24M,361) |

Productive/Contention/Other information is a tripartite breakdown of how CICS spends its time. In the example above, 10.8 percent is productive time, 83.7 percent is in contention with MVS or CICS resources, and 5.5 percent falls in neither of those categories.

The short-term interval contains information collected over the past 3 minutes and 24 seconds, during which there were 88 observations. The long-term interval spans 13 minutes and 24 seconds, during which 361 observations were made.

Display bodyThe display body, as in the following figure, shows the various sources of contention, and the degree to which they are impacting CICS, for both short- and long-term collection intervals.

Contending Address Spaces lists jobs that compete with CICS for resources. The short-term statistics refer to time elapsed since the short-term buckets have cleared and to the number of samples taken during that interval. The long-term statistics summarize the last n intervals.

FIGURE 65. Display Body Example

Contention data

At the right of each impact source is the percent of non-idle time that CICS was waiting for one or more resources being used by the contender.

The graphs highlight the percent contention data:

n If contention is less than 30 percent, the body of the arrow is composed of hyphens only (--->).

n If contention is greater than 30 percent, the portion of the graph between thirty and sixty percent is composed of equal signs (---===>).

n If contention is greater than 60 percent, the portion of the graph between 60 and 100 percent is represented by greater-than signs (>>>).

----------------------------+-1-2-3-4-5-6-7-8-9-+ +-1-2-3-4-5-6-7-8-9-+*Total Contention* *83.7*|------======>>>>> | *52.5*|------====> |*Self-Contention* 10.2|-> . . . . . . . . | 7.9|-> . . . . . . . . |RELOADDB (J1208) PG3 37.5|-----=>. . . . . . | 0.0| . . . . . . . . . |TESTCICS (S1366) PG5 13.3|-->. . . . . . . . | 11.0|-> . . . . . . . . |USER01 (T0934) PG2 0.0| . . . . . . . . . | 15.3|-->. . . . . . . . |System 22.7|---->. . . . . . . | 18.3|---> . . . . . . . |



Total contention

The first line of the display body shows total contention, which may not be equal to the sum of the contention from all impact sources shown below it. This is because only the main impact sources are shown on the default display. In this case, only those that account for 5 percent or more of the non-idle time are included.

Self-contention

The second line of the display body always shows self-contention, if it exists. In this example, OMEGAMON II is analyzing a single CICS region (CICSA). Self-contention in single-region analysis indicates that tasks within the region are in competition for MVS resources.

Impact sources

The next three lines show three impact sources: a batch job (RELOADDB), a started task (TESTCICS), and a TSO user (USER01). Next to each name, the display shows the JES job number of the impact source and the performance group in which it is executing. Note that the job numbers each begin with a letter denoting the type of job:

If the job number field contains SBSYS, it means that the contender is a subsystem.

In the example, RELOADDB is clearly the largest short-term impact source, accounting for 37.5 percent of non-idle time. However, the long-term display shows USER01 to be the major impact source over a longer period of time, even though it is not currently impacting CICS at all.

System contention

The last line of the display shows system contention. This is usually contention that is detected, but is not attributable to any particular address space.

J Batch job.

S Started task.

T TSO user.

Impact Analysis 159


Impact detail displayDetail displays show the specific I/O devices and enqueue types in contention. To request a detail display, select the Impact Detail option (G) on the Bottlenecks path or enter fast path B.G from any panel. The following figure shows an example of a detail display.

FIGURE 66. Workload Impact Analysis Detail Panel (B.G)

RELOADDB is impacting CICSA in three ways:

n I/O contention on one or more devicesn CPU contentionn holding one or more enqueues

DIANL CICSA IAST=2.2 IATH=0 IACS=10 IACL=20+ Productive/Contention/Other | 10.8% 83.7% 5.5% | | 38.7% 52.5% 8.8% |+ Contending Address Spaces |Short (3:24M,88) | |Long (13:24M,361) |+ ----------------------------+-1-2-3-4-5-6-7-8-9-+ +-1-2-3-4-5-6-7-8-9-++ *Total Contention* *83.7*|------======>>>>> | *52.5*|------====> |+ *Self-Contention* 10.2|-> . . . . . . . . | 7.9|-> . . . . . . . . |+ Contending I/O (10.2)| | (7.9)| |+ PAGP1 on 520 <10.2>|-> . . . . . . . . | <7.9>|-> . . . . . . . . |+ RELOADDB (J1208) PG3 37.5|-----=>. . . . . . | 0.0| . . . . . . . . . |+ Contending I/O (22.3)| | (0.0)| |+ MVSPK1 on 3A4 <15.2>|-->. . . . . . . . | <0.0>| . . . . . . . . . |+ PAGPK1 on 520 <7.1>|>. . . . . . . . . | <0.0>| . . . . . . . . . |+ Using CPU (10.2)|-> . . . . . . . . | (0.0)| . . . . . . . . . |+ Holding Enqueue (5.0)| | (0.0)| |+ SYSDSN <5.0>|>. . . . . . . . . | <0.0>| . . . . . . . . . |+ TESTCICS (S1366) PG5 13.3|-->. . . . . . . . | 11.0|-> . . . . . . . . |+ Contending I/O (12.7)| | (9.8)| |+ CICS03 on 320 <12.7>|-->. . . . . . . . | <9.8>|-> . . . . . . . . |+ Holding Enqueue (0.4)| | (1.0)| |+ SYSVSAM <0.4>| . . . . . . . . . | <1.0>| . . . . . . . . . |+ Using CPU (0.2)| . . . . . . . . . | (0.2)| . . . . . . . . . |+ USER01 (T0934) PG2 0.0| . . . . . . . . . | 15.3|-->. . . . . . . . |+ Contending I/O (0.0)| | (10.1)| |+ PROD10 on 200 <0.0>| . . . . . . . . . | <10.1>|-> . . . . . . . . |+ Using CPU (0.0)| . . . . . . . . . | (5.2)|>. . . . . . . . . |+ System 22.7|---->. . . . . . . | 18.3|---> . . . . . . . |+ SRM MPL Delay (17.8)|---> . . . . . . . | (7.9)|-> . . . . . . . . |+ Contending I/O (2.7)| | (8.4)| |+ PAGPK1 on 520 <2.7>|>. . . . . . . . . | <8.4>|-> . . . . . . . . |+ Using CPU (1.4)| . . . . . . . . . | (1.1)| . . . . . . . . . |+ Holding Enqueue (0.8)| | (0.9)| |+ SYSVTOC <0.8>| . . . . . . . . . | <0.9>| . . . . . . . . . |



These are the ways in which an address space can impact CICS performance:

Contending I/O CICS is queued for an I/O device and the address space is causing the device to be unavailable. (The detail display shows the specific devices under contention. This display is described in “Impact detail display”.)

Using CPU CICS is waiting to be dispatched on the CPU while the address space is using it.

Using Real Storage When CICS is waiting for page-in, impact analysis identifies each address space that is using real storage and weights the contention, based upon how much real storage each address space is using.

Holding Enqueue The address space is holding an enqueue on a resource while CICS is waiting for it. (The detail display shows the major enqueue name(s) being held. “Impact detail display” shows this display.)

Mount Pending CICS is waiting for a DASD or tape mount. This is considered system contention and is not attributed to competing address spaces.

SRM Delay There are four categories of SRM delay:n enqueue exchange swaps (ENQ)n exchange swaps (EXC)n out and ready (MPL)n unilateral swaps (UNI)Since production CICS systems are usually nonswappable, contention due to SRM delay is generally seen for test systems only.

Holding CML Lock CICS is waiting for its local lock while the impact source is holding it as a Cross-Memory Local (CML) lock.

MVS uses locks to serialize access to resources. Each address space needs control over its local lock to get dispatched in the CPU. Another address space can, however, take control of that local lock by obtaining the CML lock.

When this type of contention appears, it indicates that the impacting address space has obtained the CML lock and has gained control over the CICS region’s local lock. CICS must wait until the CML lock is released before it can regain control over its local lock.

Impact Analysis 161

Workload Impact Profile (IPRO)

Workload Impact Profile (IPRO)The Impact Profile option (F) on the Bottlenecks path (fast path B.F) displays a workload impact profile (IPRO). Note that IPRO cannot be used to initiate monitoring; you must first start monitoring the job or group.

The workload impact profile is another form of overview display in impact analysis. It shows a graphic illustration of current contention on your system. The following figure shows a typical display.

FIGURE 67. Workload Impact Analysis Profile Panel (B.F)

The percentage of impact on this CICS region is represented by the amount of indentation. Contenders are listed in order of decreasing severity, except for self-contention, which is always first, and system contention, which is always last. In this example, job RELOADDB is having the greatest impact on CICS.

The profile displays only the long-term wait condition figures available with impact analysis (IANL), instead of the short-term ones, to ensure a statistically significant value.

For terminals with extended color in effect, the Workload Impact Profile appears in the colors set for Levels 5, 6, and 7. The graph itself appears in the Level 5 color, the impact source labels are in the Level 7 color, and the lines pointing from the impact source labels to the graph are in the Level 6 color. For information about turning on extended color and setting the color for each level, see the OMEGAMON II for CICS Configuration and Customization Guide.

IPRO IANL CICSA+ The largest impactor to CICSA is RELOADDB+ |||||||||||||||||||||||||||||||||||||||||||||||+ |||||||||||||||||||||||||||||||||||||||| +----------------------++ ||||||||||||||||||||||||||||||||||||||||<-------10%-| *Self-Contention* |+ |||||||||||||||||||||||||||||||||||||||| +----------------------++ |||||||||||||||||||||||||||||||||||||||||||||||+ ||||||||||||||||||||||||||||| +----------------------++ |||||||||||||||||||||||||||||<------------------38%-| RELOADDB (J1208) |+ ||||||||||||||||||||||||||||| +----------------------++ |||||||||||||||||||||||||||||||||||||||||||||||+ |||||||||||||||||||||||||||||||||||||| +----------------------++ ||||||||||||||||||||||||||||||||||||||<---------13%-| TESTCICS (S1366) |+ |||||||||||||||||||||||||||||||||||||| +----------------------++ |||||||||||||||||||||||||||||||||||||||||||||||+ ||||||||||||||||||||||||||||||||||||||||||| +----------------------++ |||||||||||||||||||||||||||||||||||||||||||<-----5%-| USER01 (T0934) |+ ||||||||||||||||||||||||||||||||||||||||||| +----------------------++ |||||||||||||||||||||||||||||||||||||||||||||||+ || |||||||||||||||||||||||| +----------------------++ || CICSA ||||||||||||||||||||||||<------------23%-| System |+ || |||||||||||||||||||||||| +----------------------++ |||||||||||||||||||||||||||||||||||||||||||||||

Workload Impact Profile (IPRO)


As with all impact analysis displays, you should be aware that the workload impact profile becomes most useful when a CICS region is experiencing response time problems. When response time is acceptable, the profile provides a picture of normal contention, and no tuning is required. If response time worsens due to contention from other MVS address spaces, the workload impact profile may also change, indicating a possible cause of the response time problem.

Impact Analysis 163

Adjusting Collection and Display Parameters

Adjusting Collection and Display ParametersThe impact analysis feature uses preset defaults for use with a wide variety of configurations. However, as you gain experience using it, you may want to customize the displays to better suit the unique requirements of your installation.

Controlling the sampling intervalYou can set the sampling interval for impact analysis collection by selecting the Impact Analysis Settings option (N) on the Control Options path (main menu option O) or by entering O.N to fast path to the Workload Impact Analysis Settings panel, shown in the following figure.

FIGURE 68. Workload Impact Analysis Settings Panel (O.N)

Scroll to the IAST statement to display or reset the sampling interval to specify how often the impact analysis collector checks the status (execution state) of CICS regions. By default, CICS regions are checked every .9 seconds, or just slightly more than 66 times per minute. (This interval length is set to an irregular value to avoid accidental synchronization with other system events.)

________________ ZCIASET VTM $CICSTOR V520/I SYSA 02/03/99 13:54:22> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-RTA On B-RTA Off C-RTA Status D-RTA Intervals E-RTA Scaling> F-ONDV On G-ONDV Off H-ONDV Status I-Bottleneck Ctl J-Wait Reasons> K-INTR Ctl L-IANL On M-IANL Off N-IANL Settings O-IANL Groups> P-Collection Q-Shutdown R-RLIM On S-RLIM Off T-RLIM Status===============================================================================> WORKLOAD IMPACT ANALYSIS SETTINGS > IMPORTANT: To limit impact analysis resource utilization, there is an> automatic timeout interval. This interval indicates how long the impact> analysis collector remains active after an impact analysis request. If the> interval elapses, the collector terminates itself, freeing data areas. The> next impact analysis request reactivates the collector. > Set the impact analysis automatic time-out interval by typing the number of> minutes (0 - 99) to elapse before timeout immediately after IATO. (0> specifies no time-out). IATO+ << IA0217 IA collection task times out after 5 minutes >> > A larger sampling interval will also reduce overhead. To set a new sampling> interval, remove the > preceding IAST and enter the value of the time> interval (in tenths of a second) following IAST.>IAST+ << IA0205 The data collector sample time = .9 seconds << > To set a new severity threshold (value below which resource contention data> will not appear), enter the percentage (0-99) after IATH. If you enter 0,> all contenders appear on impact analysis displays.



Smaller sampling intervals provide more data and improve accuracy, but do so at the expense of CPU utilization. Conversely, setting larger intervals reduces the CPU requirements of impact analysis, but can reduce the accuracy of the data.

Impact analysis time-out facilityWhile the impact analysis collector is active, it is consuming resources. Since it is possible to start impact analysis collection and then move on to other kinds of analysis without turning the collector off, the impact analysis time-out facility automatically terminates the collector after a period of time. This time period is equal to the short-term collection interval multiplied by the number of short-term intervals in the long-term interval. For example, if the short-term interval is 1 minute and the long-term interval is 5 short-term intervals (the defaults), impact analysis times out after 5 minutes. You can set the long-term interval by scrolling to the IACL statement. The format is:

IACLn

For example, if you set IACL to 1, there will be no difference between the short- and long-term intervals in the impact analysis display. If you set IACL to 3, the long-term part of the impact analysis display will include the current short-term interval, plus the two previous short-term intervals.

You can set the short-term interval by scrolling to the IACS statement. The format is:

IACSnn

You may use the IACS statement at any time during a session. OMEGAMON II automatically clears the buckets as soon as you use this option.

You can set the number of groups that will be monitored for the impact analysis display by scrolling to the IANC statement. The format is:

IANCnn

b or 0 Displays the current long-term bucket clearing interval.

1–5 Sets the long-term bucket clearing interval at 1–5 short-term intervals. The default is 5.

b or 0 Displays the current short-term bucket clearing interval, and clears the short-term bucket immediately. OMEGAMON II does not clear the bucket again until the IACL statement is re-entered with a numeric operand.

1–99 Sets the short-term bucket clearing interval at 1–99 minutes. The default is 1 minute.

b or 0 Displays the current maximum number of CICS regions or groups monitored by impact analysis.

1–5 Sets the maximum number of CICS regions or groups to 1–5. The default is a maximum of 5 CICS regions or groups.

Impact Analysis 165


If you wish to monitor fewer than five regions or groups, you must reduce the maximum with the IANC statement before you begin the session (that is, before you use IANL the first time). Upon execution, IANC issues a message informing you of the new maximum number.

You cannot change the maximum number of regions while the collector is running; you must either do so before you start the collector, or you must stop the collector, change the number of regions, and then restart collection.

You can set the severity threshold for the impact analysis display by scrolling to the IATH statement. The format is:

IATHnn

You can enter the IATH statement at any time during a session.

For example, to limit impact analysis displays to impact sources that account for 10% or more of the non-idle time, enter the following:

IATH10

The resulting message shows you the new threshold value.

FIGURE 69. Plot Percentage Message Example

Notice that the operand is expressed as a percentage and that the statement is not commented out (preceded by >) after qxecution.

b Displays the current value.

0 Displays all impact sources.

1–99 Causes impact analysis to display impact sources that account for the indicated percentage or more of non-idle time of the CICS region or group. By default, impact sources that account for 5% or more of the total non-idle time of the CICS region or group are shown in the display.

IATH >> IA2006 Plot percentage threshold is 10% <<



Storage Analysis 167

Storage Analysis

Chapter OverviewVirtual storage availability is necessary for CICS systems to function properly. When virtual storage usage goes above critical levels, serious degradation of CICS performance may occur. In some cases, the resulting problems can be so severe as to require restarting CICS.

There are two levels of storage to monitor in your CICS system.

n CICS manages storage for its internal components and applications. It has its own storage management component for that purpose.

n The operating system manages the remaining storage. This includes, for example, allocating and freeing storage as files are opened and closed.

CICS/ESA versions manage storage differently from CICS/MVS versions. CICS/ESA uses domain architecture to manage more than one Dynamic Storage Area (DSA), with up to 255 domain subpools in each DSA. CICS/ESA Version 3.2.1 uses two DSAs: one for managing storage below 16M, the other for storage above 16M. CICS/ESA Version 3.3 manages five DSAs, which can be used to implement subsystem storage protection. CICS/ESA Version 4.1 manages eight DSAs, which can be used to implement subsystem storage protection and transaction isolation.

OMEGAMON II enables you to monitor storage utilization and assess the effects of any adjustments you might make for both CICS and the operating system. The first part of the chapter addresses CICS storage management, and the second part, the operating system (in those sections referred to as MVS). Both parts describe the OMEGAMON II displays, specifically tailored to CICS/MVS and CICS/ESA versions, in detail, and advise you on their use.

Chapter Contents

CICS Storage Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169

CICS main storage areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169CICS private area storage (OSCOR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169CICS subpool groupings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169CICS/ESA subsystem storage protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170

CICS Storage Analysis Displays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171Storage Summary panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171Storage violations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174

10


Storage usage by task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176DSA/EDSA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177Page allocation map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181Storage subpools (CICS/ESA only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183Program compressions (CICS/MVS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186

MVS Storage Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188MVS Storage Management Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189

MVS subpools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189Region Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192

Storage Display and Alteration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195


CICS Storage Management

CICS Storage ManagementCICS applications frequently make requests for storage. If the operating system were to handle these requests, other CICS applications would be delayed until the request was completed. Further, unconditional requests to the operating system for storage that cannot be serviced cause the CICS system to abend. To avoid these types of situations, CICS manages storage for its applications.

CICS main storage areasCICS maintains and manages storage by allocating one or more dynamic storage areas at initialization. CICS/MVS issues an MVS conditional GETMAIN for all below-the-line storage and proceeds with initialization. At the appropriate point in the initialization process, CICS attempts an MVS conditional GETMAIN for the amount of storage specified in the OSCOR SIT parameter. If this request cannot be satisfied in full (and under most circumstances it will not be satisfied), CICS issues an MVS FREEMAIN for the amount of storage specified in the OSCOR SIT parameter. Above the line storage for CICS/MVS is essentially managed by MVS with CICS providing services for allocation and deallocation.

In CICS/ESA Version 3, storage is allocated by requesting a fixed amount using SIT parameters for each individual DSA.

In CICS/ESA Version 4, individual DSA size is not fixed. CICS/ESA Version 4 manages dynamic storage as two pools, one above the 16M boundary, and one below. The maximum size of these pools is limited by the values specified on the DSALIM and EDSALIM SIT parameters respectively.

CICS/ESA Version 4 allocates initial extents for the 4 DSAs below the 16M line and the 4 above from within the appropriate pools. Individual DSA size varies according to demand as CICS allocates new extents for or removes extents from DSA.

CICS private area storage (OSCOR)This area is used for requests for operating system storage subpools 0 through 127, 250 and 252. It includes any unallocated area below the top of the region plus the IEALIMIT extension. It does not include any storage in the LSQA.

One of OSCOR’s major uses is in dynamically opening and closing files. If your CICS systems performs these operations, you should monitor OSCOR usage to ensure that sufficient storage is available.

Although CICS/ESA dropped the OSCOR SIT parameter in favor of defining the DSA size directly, OSCOR is still used to describe storage managed below the line by the operating system. OSCOR in CICS/ESA is what remains after DSA has been allocated.

CICS subpool groupingsFor efficient management and allocation of storage, CICS allocates storage out of subpools. In CICS/MVS, there are six subpools: control, program, RPC, shared, task, and TP. CICS/ESA extended subpools to allow up to 255 domain subpools in a single DSA. These subpools have eight character IDs that are defined by the component that owns the subpool.

CICS Storage Management


CICS/ESA subsystem storage protectionIn CICS/ESA version 3.3, CICS introduced subsystem storage protection that protects CICS storage from being overwritten by applications. It performs this function by dividing storage into three key types:

CICS manages storage for each of the keys with five DSAs, one above the line for each of the keys, and a user and CICS key DSA below the line. For further information, see the CICS Version 3.3 Release Guide.

You can monitor each of the DSAs by specifying the KEY= parameter after the STOR statement, or by zooming on a particular DSA in the storage summary screen (fast path S.). For displays of subpool groups or tasks, the key value can be used as a filter to display only those subpool groups or tasks that use the specified protection key.

READ ONLY Used to load reentrant programs and cannot be modified (provided reentrant storage protection has been selected in the SIT via the RENTPGM keyword).

USER User-key storage, which is used for applications and is not protected.

CICS CICS-key storage, which is used for CICS and cannot be overwritten by applications running in user-key (provided subsystem storage protection has been selected in the SIT via STGPROT and the hardware supports system storage protection).


CICS Storage Analysis Displays

CICS Storage Analysis DisplaysOMEGAMON II presents the following types of analysis for CICS storage management. Access the Storage path by selecting the Storage option (S) on the main menu.

Storage Summary panelThe Storage Summary panel, shown in the following figure for a CICS/ESA Version 4.1 system, provides an overview of storage utilization. The following list summarizes the storage for different versions of CICS.

Move the cursor to a DSA Summary or EDSA Summary title line and press PF11 to display a detailed breakdown of that DSA.

CICS/MVS 1 DSA

CICS/ESA Version 3.1.1 1 DSA and 1 EDSA

CICS/ESA Version 3.2.1 1 DSA and 1 EDSA

CICS/ESA Version 3.3 summarizes all 5 DSAs,n CDSA n UDSA n ECDSAn EUDSAn ERDSA

CICS/ESA Version 4.1 summarizes all 8 DSAs,n CDSA n UDSA n SDSA n RDSA n ECDSAn EUDSAn ESDSAn ERDSA



FIGURE 70. Storage Summary Panel (S.)

________________ ZSTOR VTM TDOCS01 V520./C SYSG 02/03/93 13:57:56> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Summary B-Violations C-Task Storage D-DSA E-EDSA> F-PAM DSA G-PAM EDSA H-Subpool Groups I-Region Storage J-Compressions===============================================================================> STORAGE SUMMARY STOR+ Storage Information+ DSA limit . . . . . . . : 5120K EDSA limit . . . . . . : 10240K+ DSA storage allocated . : 1280K EDSA storage allocated : 6144K+ DSA storage in use . . : 1024K EDSA storage in use . . : 5120K+ DSA area currently SOS : No EDSA are currently SOS : No+ Total storage violations: 0 Storage recovery option : No+ Storage protection . . : No Transaction isolation . : No+ Total storage notifies : 0 Statistics last reset . : 0:00:01+ Current free OSCOR . . : 1597K Largest free OSCOR . . : 1516K++ CICS Key DSA Summary+ DSA size . . . . . . . : 512K Cushion size . . . . . : 64K+ Current free space . . : 204K Largest free area . . . : 192K+ Extents allocated . . . : 2 Extents in use . . . . : 2+ Current tasks suspended : 0 Total tasks suspended . : 0+ Currently SOS . . . . . : No Total times SOS . . . . : 0++ User Key DSA Summary+ DSA size . . . . . . . : 256K Cushion size . . . . . : 64K+ Current free space . . : 256K Largest free area . . . : 256K+ Extents allocated . . . : 1 Extents in use . . . . : 0+ Current tasks suspended : 0 Total tasks suspended . : 0+ Currently SOS . . . . . : No Total times SOS . . . . : 0++ Shared DSA Summary+ DSA size . . . . . . . : 256K Cushion size . . . . . : 64K+ Current free space . . : 252K Largest free area . . . : 256K+ Extents allocated . . . : 1 Extents in use . . . . : 1+ Current tasks suspended : 0 Total tasks suspended . : 0+ Currently SOS . . . . . : No Total times SOS . . . . : 0++ Read Only DSA Summary+ DSA size . . . . . . . : 256K Cushion size . . . . . : 64K+ Current free space . . : 72K Largest free area . . . : 72K+ Extents allocated . . . : 1 Extents in use . . . . : 1+===============================================================================



This panel shows the following fields:

DSA limit (CICS/ESA Version 4.1 only) The total amount of storage the DSA’s below the 16Meg line are allowed to allocate. This value is specified in the SIT or can be overridden via the CEMT transaction.

EDSA limit (CICS/ESA Version 4.1 only) The total amount of storage the DSA’s above the 16Meg line are allowed to allocate. This value is specified in the SIT or can be overridden via the CEMT transaction.

DSA storage allocated

(CICS/ESA Version 4.1 only) The current total storage allocated by the DSA’s below the 16Meg line.

EDSA storage allocated

(CICS/ESA Version 4.1 only) The current total storage allocated by the DSA’s above the 16Meg line.

DSA storage in use (CICS/ESA Version 4.1 only) The current storage allocated by DSA extents below the 16Meg line which have at least one page in use.

EDSA storage in use (CICS/ESA Version 4.1 only) The current storage allocated by DSA extents above the 16Meg line which have at least one page in use.

DSA area currently SOS

(CICS/ESA Version 4.1 only) Whether any of the DSA’s below the 16Meg line are currently short on storage.

EDSA area currently SOS

(CICS/ESA Version 4.1 only) Whether any of the DSA’s above the 16Meg line are currently short on storage.

Total storage violations

Count of storage violations detected by CICS. Each violation constitutes an instance of a CICS application writing into storage that it doesn’t own. While CICS can usually recover from these errors, the recovery process is time consuming and degrades application response time. To find out which transactions encountered storage violations, select the Violations option (B) on the Storage path (fast path S.B). Note that the count for this field is reset every time CICS resets the system statistics for CICS/ESA.

Storage recovery option

Whether CICS will attempt to recover from storage violations. This option is set in the CICS System Initialization Table (SIT).

Storage protection (CICS/ESA Version 4.1 only) Whether CICS will attempt to protect CICS internal storage against corruption from user applications.

Transaction isolation (CICS/ESA Version 3.3 and above) Whether CICS will attempt to protect user storage against corruption from other CICS user tasks.

Total storage notifies (CICS/ESA only) How many times the Storage Manager domain has notified other domains that the DSA is approaching a short-on-storage (SOS) condition. The closer CICS approaches SOS, the more frequently this count increases.

Statistics last reset Time of day when CICS storage statistics were last reset.

OSCOR requested (CICS/MVS only) The total amount of OSCOR storage requested for this startup.



Storage violationsA storage violation occurs when a transaction overwrites storage owned by another program. When CICS detects a storage violation, it performs a recovery process that may affect the response times of other CICS applications. If CICS cannot recover, it terminates. Therefore, in order to maintain acceptable CICS system performance, it is important to determine the sources of storage violations.

CICS attributes a storage violation to a transaction if the damaged storage is transaction-related, or to a terminal, if the damaged storage is terminal-related. If transaction A overwrites storage owned by transaction B, CICS associates a storage violation with transaction B. As a result, determining the problem source is not always straightforward. CICS contains a diagnostic facility that analyzes all CICS storage chains during every storage request, in order to promptly detect violations. See the CICS Problem Determination Guide for more information.

To display storage violations as shown in the following figure, select the Violations option (B) on the Storage menu or enter fast path S.B from any panel.

Current free OSCOR Total amount of storage available in the CICS private area to handle MVS getmain requests. Since this amount consists of the sum total of available fragments, a getmain request for storage less than this amount may not succeed.

Largest free OSCOR Size of the largest contiguous area available in the CICS private area to handle MVS getmain requests.

DSA size For CICS/ESA, this amount is specified in the SIT. For CICS/MVS, this size is the amount left over after CICS allocates storage for resident programs, tables, and OSCOR.

Cushion size Amount of storage in the DSA that is set aside to satisfy a storage request when the DSA is almost completely utilized. If CICS uses storage from the cushion, it indicates an SOS condition.

Current free space Amount of currently unused storage in the DSA.

Largest free area Largest amount of currently unused contiguous storage in the DSA.

Extents allocated (CICS/ESA Version 4.1 only) The number of extents currently allocated in this DSA.

Extents in use (CICS/ESA Version 4.1 only) The number of extents in this DSA which have at least one page in allocated.

Current tasks suspended

Current number of tasks suspended due to insufficient storage.

Total tasks suspended

Total number of tasks suspended due to insufficient storage since last statistics reset or startup.

Currently SOS Whether CICS is short-on-storage.

Total times SOS Number of times CICS went short-on-storage.



FIGURE 71. Storage Violations Panel (S.B)

This panel displays all recorded storage violations as a result of scanning the PCT and the TCT. The storage violation count kept by CICS/ESA storage management, shown on the Storage Summary display (Figure 70 on page 172), is reset during every statistics interval. The PCT and TCT storage violation statistics are also reset every statistics interval for CICS/ESA.

________________ ZSTVIOL VTM CICSP01 V520./I SYSA 02/03/93 16:16:07 > PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Summary B-Violations C-Task Storage D-DSA E-EDSA > F-PAM DSA G-PAM EDSA H-Subpool Groups I-Region Storage J-Compressions ================================================================================ > STORAGE VIOLATIONS STOR VIOLATIONS + + Tran PCTE Storage + ID Address Viols + -------- -------- -------- + WREK 001419C4 4 + + Terminal TCTTE Storage + ID Address Viols + -------- -------- -------- + M045 0012C1F0 1 + + Storage violation statistics last reset at : 15:00:00 ================================================================================



Storage usage by taskSelect the Task Storage option (C) on the Storage path (fast path S.C) to see the Storage Usage by Task display for CICS/ESA as shown in the following figure.

FIGURE 72. Task Storage Panel (S.C)

This panel displays an entry for each task in the system with a Task Control Area (TCA). It shows you how much storage is used by each task. You can use this display to determine which tasks are using excessive storage when storage problems are occurring. For detailed information about a specific task, place the cursor on the line describing the task and press PF11.

For CICS/ESA Version 3.3 and above, the display shows storage allocated in any of the protection keys. To filter the display by a particular storage key for CICS Version 3.3, enter the following after the STOR TASK statement:

KEY=(USER|READ|CICS)

To filter the display by a particular storage key for CICS Version 4.1, enter the following after the STOR TASK statement:

KEY=(USER|READ|CICS|SHRD)

________________ ZSTRTSK VTM TDOCS01 V520./C SYSG 02/03/93 13:58:56> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Summary B-Violations C-Task Storage D-DSA E-EDSA> F-PAM DSA G-PAM EDSA H-Subpool Groups I-Region Storage J-Compressions===============================================================================> TASK STORAGE > For CICS V3.3, enter KEY=nnnn after STOR TASK to show task storage usage in> one of the three keys: CICS, USER or READONLY. The default is all keys. STOR TASK+ Tran Task Current DSA DSA EDSA EDSA+ ID Number Elements Used Alloc Used Alloc+ -------- -------- -------- -------- -------- -------- --------+ CSTP 2 1 1K 4K 0 0+ CSSY 4 1 1K 4K 0 0+ CSSY 5 1 1K 4K 0 0+ CSSY 6 1 1K 4K 0 0+ CSSY 7 1 1K 4K 0 0+ CSSY 17 2 1K 4K 0 0+ CSSY 18 3 3K 4K 0 0+ CSSY 19 3 5K 12K 0 0+ CSSY 20 3 6K 12K 0 0+ CSSY 21 3 9K 16K 0 0+ CSSY 22 3 9K 16K 0 0+ CSNC 23 2 2K 4K 0 0+ CSSY 29 1 1K 4K 0 0++ Total n/a 25 48K 92K 0 0===============================================================================



DSA/EDSASelect the DSA option (D) on the Storage path to see the Dynamic Storage Area display for CICS/ESA, as shown in the following figure. For CICS/MVS, see Figure 75 on page 180. Note that some fields are common to both releases.

FIGURE 73. Dynamic Storage Area Panel for CICS/ESA Version 4.1 (S.D)

________________ ZDSA VTM TDOCS01 V520./C SYSG 02/03/93 13:59:32> PF1 Help PF3 Back PF4 Main Menu > A-Summary B-Violations C-Task Storage D-DSA E-EDSA> F-PAM DSA G-PAM EDSA H-Subpool Groups I-Region Storage J-Compressions===============================================================================> DYNAMIC STORAGE AREA > For CICS V3.3, enter KEY=CICS after STOR DSA to show the CDSA or KEY=USER> to show the UDSA. UDSA is the default. STOR DSA+ DSA Information+ DSA size . . . . . . . : 512K Cushion size . . . . . : 64K+ Current tasks suspended : 0 Currently SOS . . . . . : No+ Current free space . . : 232K Largest free area . . . : 176K+ % DSA allocated . . . . : 55% Page size . . . . . . . : 4K+ Extents allocated . . . : 2 Extents in use . . . . : 2++ DSA Statistics+ Getmain requests . . . : 4714 Freemain requests . . . : 3516+ Total tasks suspended . : 0 HWM tasks suspended . . : 0+ Times cushion released : 0 Total times SOS . . . . : 0+ LWM free space . . . . : 0 HWM free space . . . . : 0+ Add subpool requests . : 125 Delete subpool requests : 58+ Purged while suspended : 0 Getmain failures . . . : 0+ Total time SOS . . . . : 00:00:00 Statistics last reset . : 12:32:41+ Storage violations . . : 00:00:00 Time last went SOS . . : 12:32:41++ DSA Allocations+ Address of PAM . . . . : 08400230+ Size of extent . . . . : 256K % allocated . . . . . . : 94%+ Start address . . . . . : 00040000 End address . . . . . . :0007FFFF++ Address of PAM . . . . : 08497D98+ Size of extent . . . . : 256K % allocated . . . . . . : 16%+ Start address . . . . . : 00100000 End address . . . . . . : 0013FFFF===============================================================================



DSA size Size of the DSA. For CICS/MVS, this size is the amount remaining after CICS allocates storage for resident programs, tables, and OSCOR. For CICS/ESA, this size is specified in the SIT.

Cushion size Amount of storage set aside in the DSA and EDSA that if needed signals that CICS is going SOS. The amount is specified in the SIT.

Current tasks suspended

Number of tasks currently suspended due to a lack of storage in the DSA or EDSA.

Currently SOS Whether CICS is short-on-storage.

Current free space Amount of free space, including cushion size, in the DSA or EDSA.

Largest Free Area Largest contiguous area in the DSA or EDSA.

% DSA allocated For CICS/ESA only: The percentage of the DSA currently in use.

Page size Either 2K or 4K depending on the size specified in the SIT for CICS/MVS. For CICS/ESA the page size is always 4K.

Extents allocated (CICS/ESA Version 4.1 only) The number of extents currently allocated to this DSA.

Extents in use (CICS/ESA Version 4.1 only) The number of extents in this DSA that have at least one page allocated.

Getmain requests Count of getmain requests.

Freemain requests Count of freemain requests.

Total tasks suspended

Total number of tasks suspended due to short-on-storage.

HWM tasks suspended

Highwater mark of tasks suspended during one occurrence of a short-on-storage.

Times cushion released

Number of times CICS had to satisfy a getmain request from the storage cushion.

Total times SOS Number of times CICS went short-on-storage.

LWM free space For CICS/ESA only: The smallest amount of free space ever available.

HWM free space For CICS/ESA only: The largest amount of free space ever available.

Add subpool requests

Count of requests to add a subpool. This request is usually done only by CICS internal functions.

Delete subpool requests

Count of requests to delete a subpool. This request is usually done only by CICS internal functions.

Purged while suspended

Number of tasks that CICS purged while short-on-storage.

Getmain failures Number of getmain requests that could not be satisfied due to an SOS.

Total time SOS Amount of time CICS was SOS.

Time last went SOS The time that CICS was last short on storage in this DSA.



FIGURE 74. Dynamic Storage Area Panel for CICS/ESA (S.D)

Figure 75 on page 180 shows the DSA display for a CICS/MVS system.

Storage violations Amount of time CICS was SOS.

Statistics Last Reset Time of day when CICS storage statistics were reset.

Address of PAM Address of the Page Allocation Map that maps out the DSA and EDSA.

Size of extent The size of this extent within the DSA.

% DSA allocated The percentage of the DSA currently in use.

Start address Starting address of the DSA or EDSA.

End address Ending address of the DSA or EDSA.

________________ ZDSA VTM TDOCS01 V520./C SYSG 02/03/93 13:59:32> PF1 Help PF3 Back PF4 Main Menu > A-Summary B-Violations C-Task Storage D-DSA E-EDSA> F-PAM DSA G-PAM EDSA H-Subpool Groups I-Region Storage J-Compressions===============================================================================> DYNAMIC STORAGE AREA > For CICS V3.3, enter KEY=CICS after the STOR command to show the CDSA> or KEY=USER to show the UDSA. UDSA is the default. STOR DSA+ DSA Information+ DSA size . . . . . . . : 3456K Cushion size . . . . . : 16K+ Page size . . . . . . . : 4K Address of PAM . . . . : 04FC26E8+ Start address . . . . . : 0004C000 End address . . . . . . : 003ABFFF+ Current tasks suspended : 0 Currently SOS . . . . . : No+ Current free space . . : 1964K Largest free area . . . : 1944K+ % DSA allocated . . . . : 43% LWM free space . . . . : 1920K++ DSA Statistics+ Getmain requests . . . : 4714 Freemain requests . . . : 3516+ Total tasks suspended . : 0 HWM tasks suspended . . : 0+ Times cushion released : 0 Total times SOS . . . . : 0+ Add subpool requests . : 125 Delete subpool requests : 58+ Purged while suspended : 0 Getmain failures . . . : 0+ Total time SOS . . . . : 00:00:00 Statistics last reset . : 12:32:41===============================================================================



FIGURE 75. Dynamic Storage Area Panel for CICS/MVS (S.D)

The following DSA display fields apply only to CICS/MVS.

For CICS/MVS, the bottom part of the display shows the amount of storage allocated to each of the six subpools. For CICS/ESA, storage subpools are shown on a different display. (See Figure 78 on page 184.)

Global Storage > 16M Shared storage allocated above the line, in bytes.

Task Storage > 16M Total above-the-line storage allocated to individual tasks, in bytes.

Total Getmains > 16M Total number of storage allocations above the line.

________________ ZDSA VTM $CICSCAN V520./I SYSA 02/03/93 13:48:12> PF1 Help PF3 Back PF4 Main Menu > A-Summary B-Violations C-Task Storage D-DSA E-EDSA> F-PAM DSA G-PAM EDSA H-Subpool Groups I-Region Storage J-Compressions===============================================================================> DYNAMIC STORAGE AREA STOR DSA+ DSA Information+ DSA size . . . . . . . : 5688K Cushion size . . . . . : 120K+ Page size . . . . . . . : 4K Address of PAM . . . . : 0001D030+ Start address . . . . . : 0001E000 End address . . . . . . : 005ABFFF+ Current tasks suspended : 0 Currently SOS . . . . . : No+ Current free space . . : 2936K Largest free area . . . : 2688K+ Getmain requests . . . : 3423880 Freemain requests . . . : 3405170+ Total tasks suspended . : 0 HWM tasks suspended . . : 0+ Times cushion released : 0 Total times SOS . . . . : 0+ Global storage >16M . . : 17065K Task storage >16M . . . : 630K+ Total getmains >16M . . : 446728++ Storage Pages % DSA+ Subpool Alloc Alloc+ -------- -------- --------+ Control 6 0%+ Program 150 11%+ RPL 1 0%+ Shared 226 16%+ Task 280 20%+ TP 26 2%++ Total 689 48%===============================================================================



Page allocation mapA Page Allocation Map (PAM) indicates, for each page of storage in the DSA, whether the page is allocated and, if so, to which storage subpool. Select the PAM DSA option (F) on the Storage path or enter fast path S.F, to see the PAM for CICS/ESA, as shown in the following figure.

FIGURE 76. Storage Allocated in the DSA Panel for CICS/ESA (S.F)

Each letter shown in the display represents a group to which the storage belongs. This grouping is an OMEGAMON II convention. It allows you to view up to 255 types of storage subpools, based on their intended use. The key legend used in the map is defined below.

________________ ZPAM VTM TDOCS01 V520./C SYSG 02/03/93 13:59:53> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Summary B-Violations C-Task Storage D-DSA E-EDSA> F-PAM DSA G-PAM EDSA H-Subpool Groups I-Region Storage J-Compressions===============================================================================> STORAGE ALLOCATED IN THE DYNAMIC STORAGE AREA > For CICS V3.3 only, type KEY=nnnn after the command to show the PAM for> the CDSA (KEY=CICS) or UDSA (KEY=USER). Default is UDSA > For page storage, place the cursor on the page position and press PF11. STOR PAMDSA Key : A-AP D-TD F-File L-Loader M-Monitor O-Other S-TS T-Task Z-Terminal++ Address+ 0004C000 LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL+ 0008C000 LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL+ 000CC000 LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL+ 0010C000 LLLAAAAADLLLOZOFLLLLLLLLLLLLZZZZZZZZZZZZZZZZZZZZLLLLOOOOOOLLLLOL+ 0014C000 LLLLLLSSSOFFFLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL+ 0018C000 LLLLZOZZZZZZZZOOFLLLLOSLLLLLLL..................................+ 001CC000 to 0038BFFF not allocated+ 0038C000 ....TTTTTTTTT....TTTTT.TTTTTTTTT++ Total pages . . . . . . : 864 Free pages . . . . . . : 491===============================================================================



Note that lines are not displayed if they are not allocated.

The PAM for CICS/MVS is shown in the following figure.

FIGURE 77. Storage Allocated in the DSA Panel for CICS/MVS (S.F)

A Application domain.

D Transient Data storage.

F File storage.

L Loader storage (programs).

M Monitoring storage.

O Other.

S Temporary storage.

T Task storage.

Z Terminal storage.

________________ ZPAM VTM $CICSCAN V520./I SYSA 02/03/93 13:47:38> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Summary B-Violations C-Task Storage D-DSA E-EDSA> F-PAM DSA G-PAM EDSA H-Subpool Groups I-Region Storage J-Compressions===============================================================================> STORAGE ALLOCATED IN THE DYNAMIC STORAGE AREA> For page storage, place the cursor on the page position and press PF11. STOR PAMDSA Key : C-Control D-Programs for deletion P-Program R-RPL+ S-Shared T-Task X-Resident programs Z-TP++ Address+ 0001E000 CRZZSTTTTTTSSSTSTSSSSSSSSSSSTTSSSSSSCSSSSSSSSSSSSSSSSSSTTTTTTSSS+ 0005E000 TTSSCSSSSSSSSSSSSSSSSTSSSSSSSSZTSSSSSSSSSCSSSSSSSSSSSSSSSSSSSSTS+ 0009E000 SSCSSSSSSSSSTSSTSTSTSSSSSSTSSSZSSSSSSS.SS.SSSSTSZSSSSSSSSSSSSSSZ+ 000DE000 ZSSSSSTSSSSSSSSSSSCSSSSSSSSSSSSZSSZSSSSTSSSSSTZTSTSSSZSSTTTTZSSS+ 0011E000 SZTSZZSSSSSSTZTSSSSZSST.TZZZTTZZSSSTTTTT.S.TTTTSZTTTT..TTTTSSS.T+ 0015E000 TTT.ZSTTTTTTTT..ZZZTTTTTTTTTTTT.STTTTTTTTTTTTTT...TTTT.STTTTTTTT+ 0019E000 TTTTTTTTTTTT.TTTTTTTTTTTTTTTTTT..STTTTTT...TTTTTTTTTTTTTTSTTTTTT+ 001DE000 TTTTTTTTTTTTTTTTTTTTTTTTTTTTTT..TTTTTTTTTTTTTTTT........TTTTTT.T+ 0021E000 TTTTTTTTTTTTT..TTTTTTTTTTTTTTTTT....TTTTTTTT..TTTTTTTTTTT.TTTTTT+ 0025E000 TTTTTTTTTT.TTTTTTTTTT..T........................................+ 0029E000 to 004DDFFF not allocated+ 004DE000 ........................................................PPPPPPPP+ 0051E000 PPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP+ 0055E000 PPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPXXXXXXXXXXXXXXXXXXXXXXXDPPPPP+ 0059E000 PPPPPPPPPPPPPP++ Total pages . . . . . . : 1422 Free pages . . . . . . : 687===============================================================================



For CICS/MVS, the PAM shows the following types of subpools.

Storage subpools (CICS/ESA only)CICS manages its storage using subpools, which are areas of storage dedicated to common uses. CICS/ESA allows up to 255 subpools per DSA. In order to aid viewing of so many different types of subpools, OMEGAMON II categorizes these subpools into one of nine groups.

To access the Storage Subpool Group display as shown in the following figure, select the Subpool Groups option (H) on the Storage path or enter fast path S.H from any panel.

Control Contains CICS control blocks such as the DCA, AIDs, and ICEs.

Programs for deletion Program storage that will be deleted when the programs are no longer in use. See “Program compressions (CICS/MVS only)” on page 186 for the conditions when CICS will flag programs for deletion.

Program Program storage of dynamically loaded programs.

RPL Storage used by VTAM.

Shared Storage not associated with a specific task which must be explicitly freed. An example is main temporary storage.

Task Storage associated with a particular task. This storage is freed when the task terminates.

Resident Programs Programs that have been originally loaded as resident outside of the DSA but are now loaded into the DSA due to a master terminal NEWCOPY request.

TP Storage associated with terminal I/O.



FIGURE 78. Storage Usage for All Subpool Groups Panel for CICS/ESA (S.H)

Storage in the task subpool group is allocated to satisfy getmain requests for storage by CICS applications. CICS domains and components use the other subpool groups to satisfy their storage requests.

A getmain results in one element being created in the DSA or EDSA for a particular subpool. The corresponding freemain releases that storage element. Therefore, the number of elements in the DSA and EDSA show the number of outstanding getmains for each subpool group.

You can zoom on a subpool group by moving the cursor to the line containing the group and pressing PF11. A detail display of the LOADER subpool group is shown in the following figure.

________________ ZSTRGRP VTM TDOCS01 V520./C SYSG 02/03/93 10:10:02> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Summary B-Violations C-Task Storage D-DSA E-EDSA> F-PAM DSA G-PAM EDSA H-Subpool Groups I-Region Storage J-Compressions===============================================================================> STORAGE USAGE FOR ALL SUBPOOL GROUPS > For CICS V3.3 only, type KEY=nnnn after the command to show the storage> usage for one of the three storage protect keys, CICS, USER or READONLY.> The default is to combine the storage usage for all keys. STOR GROUP=ALL+ Subpool DSA DSA DSA EDSA EDSA EDSA+ Group Elements Used Alloc Elements Used Alloc+ -------- -------- -------- -------- -------- -------- --------+ AP 20 9K 20K 28 69K 72K+ File 43 2K 20K 74 18K 36K+ Loader 174 1337K 1356K 1131 976K 1744K+ Monitor 0 0 0 35 77K 84K+ Task 25 48K 92K 0 0 0+ TD 1 288 4K 14 10K 16K+ Terminal 391 74K 124K 4 256 4K+ TS 9 10K 20K 1 12K 12K+ Other 603 43K 56K 26 36K 80K++ Total 1266 1526K 1692K 1313 1201K 2048K===============================================================================



FIGURE 79. Storage Usage for a Loader Subpool Group (Accessed by Zoom)

A detail display of a task subpool group is shown in the following figure.

________________ ZZGRP VTM $CICSTOR V520./I SYSA 02/03/93 16:53:29> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down ===============================================================================> STORAGE USAGE FOR A SUBPOOL GROUP STOR GROUP=LOADER+ Subpool Subpool Getmain Freemain Current Storage Storage+ Name Location Requests Requests Elements Used Alloc+ -------- -------- -------- -------- -------- -------- --------+ LD_APES EDSA 196 188 231 0 36K+ LD_CNTRL EDSA 0 0 1636 345K 356K+ LD_CNUC DSA 16 16 96 878K 900K+ LD_CSECT EDSA 226 218 332 0 64K+ LD_ECNUC EDSA 0 0 32 335K 360K+ LD_EPGMS EDSA 0 0 33 386K 404K+ LD_ERESA EDSA 0 0 4 96K 196K+ LD_PGMS DSA 180 172 55 1189K 1280K+ LD_RESA DSA 0 0 10 305K 328K++ Total n/a 618 594 2429 3536K 3924K++ Getmain and freemain requests last reset at : 15:00:00===============================================================================



FIGURE 80. Storage Usage for a Task Subpool Group (Accessed by Zoom)

Program compressions (CICS/MVS only)When a getmain request is issued that would cause CICS to allocate storage from the storage cushion, CICS attempts program compression to reclaim storage no longer in use. If program compression fails, a short-on-storage (SOS) condition occurs.

In order to avoid fragmentation, CICS allocates storage in the program subpool from the high end of DSA, and allocates storage for other subpools in the low end. When program compression frees up unneeded program storage, some program storage might be left in the middle of two free areas of the DSA.

Since CICS will not allocate any nonprogram storage past the point of the lowest addressed program, this can have the effect of blocking off free storage for many storage requests. Therefore as part of program compression, CICS will also mark program storage at the lowest addressed part of DSA as deletable. When the program is no longer needed, it will be deleted.

Select the Compressions option (J) on the Storage path for program compressions in CICS/MVS (fast path S.J). The program compression rate over the last 5 minutes is shown in the following figure.

________________ ZZGRP VTM TDOCS01 V520./C SYSG 02/03/93 14:02:27> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down ===============================================================================> STORAGE USAGE FOR A SUBPOOL GROUP > For CICS V3.3 only, type KEY=nnnn after the command to show the storage> usage for one of the three storage protect keys, CICS, USER or READONLY.> The default is to combine the storage usage for all keys. STOR GROUP=TASK+ Tran Task Current DSA DSA EDSA EDSA+ ID Number Elements Used Alloc Used Alloc+ -------- -------- -------- -------- -------- -------- --------+ CSTP 2 1 1K 4K 0 0+ CSSY 4 1 1K 4K 0 0+ CSSY 5 1 1K 4K 0 0+ CSSY 6 1 1K 4K 0 0+ CSSY 7 1 1K 4K 0 0+ CSSY 17 2 1K 4K 0 0+ CSSY 18 3 3K 4K 0 0+ CSSY 19 3 5K 12K 0 0+ CSSY 20 3 6K 12K 0 0+ CSSY 21 3 9K 16K 0 0+ CSSY 22 3 9K 16K 0 0+ CSNC 23 2 2K 4K 0 0+ CSSY 29 1 1K 4K 0 0++ Total n/a 25 48K 92K 0 0===============================================================================



FIGURE 81. Storage Compressions for CICS/MVS Panel (S.J)

Program compressions can affect the response time of CICS applications so their occurrence should be kept down to not more than once every few minutes. You can reduce the program compression rate by reducing OSCOR size to increase the DSA size, or using MAXTASKS to limit task throughput rate.

________________ ZCOMP VTM TDOCS14 V520MW SYSG 02/03/93 14:05:23> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-Summary B-Violations C-Task Storage D-DSA E-EDSA> F-PAM DSA G-PAM EDSA H-Subpool Groups I-Region Storage J-Compressions===============================================================================> STORAGE COMPRESSIONS STOR COMPRESSIONS+ Compressions last 5 mins: 15 Total compressions . . : 23++ Time Program+ Period Comps+ -------- -------- 0--------10--------20--------30--------40--------50+ Current 3 |--> . . . . . . . . . |+ -1 min 0 | . . . . . . . . . |+ -2 min 0 | . . . . . . . . . |+ -3 min 12 |-----------> . . . . . . . |+ -4 min 0 | . . . . . . . . . |===============================================================================

MVS Storage Management


MVS Storage ManagementMVS storage management can play an important role in tuning CICS regions and troubleshooting problems. An insufficient amount of storage in the private area of CICS address space can lead to 80A or 40D abends. Excessive paging may cause response time degradation.

With OMEGAMON II, you can:

n Analyze storage usage by MVS subpools. This aids you in determining the source of excessive storage use.

n Display and alter the contents of virtual storage and dataspaces, in order to troubleshoot problems.

n Examine CICS address space storage utilization, including the MVS Common Area, to ensure that each area has sufficient storage available.

n View the working set size and paging rate of the CICS region. This helps you assess whether response time is being degraded due to an insufficient amount of real storage and excessive paging.


MVS Storage Management Displays

MVS Storage Management DisplaysOMEGAMON II can help you to analyze the following areas.

n MVS subpoolsn contents of virtual storage and dataspacesn storage utilizationn working set size

MVS subpoolsMVS manages virtual storage for each job by associating the storage with the MVS subtask that requested the storage and categorizing the storage into a subpool. These subpools, numbered 0–255, are different than the subpools associated with CICS.

By selecting the Subpools option (F) on the MVS path or entering fast path M.F from any panel, you can see virtual storage allocations for each MVS subpool as shown in the following figure.



FIGURE 82. CICS Region MVS Subpools Panel (M.F)

This panel shows virtual storage allocations per MVS subtask starting with the jobstep TCB which should be DFHSIP. Enter X preceding the SUBP statement on this panel to display all TCBs starting with the region control task TCB.

________________ ZMSUBP VTM $CICSTOR V520./I SYSA 02/03/93 16:54:21> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-System Graph B-System Summary C-PSW D-TCBs E-Modules F-Subpools===============================================================================> CICS REGION MVS SUBPOOLS PEEK $CICSTOR ASID=123 >> OB8112: Data Collection Initiated << subp+ Sbp-K Alloc Real #Blks Addr Free #Blks Mxfree Program+ 0-8 956K 376K 79 00005000 48008 73 4088 DFHSIP Shr+ 5044K 1340K 122 0516F000 2896 30 2048 >16M+ 230-5 4K 4K 1 007E0000 3888 1 3888 Own+ 236-1 216K 168K 44 00795000 3880 43 176 Shr+ 8K 0K 1 7F6CD000 0 0 0 >16M+ 251-8 5304K 1984K 11 00042000 15984 9 4032 Own+ 4112K 832K 2 051FA000 2536 1 2536 >16M+ 252-0 168K 32K 17 00008000 20184 21 3160 Own+ 848K 480K 78 05100000 29200 245 2920 >16M+ -----------------------------------------------------------------------------+ PVT-Lo:10432K 3328K 108 67904 276+ PVT-Hi: 4K 4K 1 3888 1+ SubTot:10436K 3332K 109 71792 277+ =============================================================================+ 0-8 956K 376K 79 00005000 48008 73 4088 DFHKETCB Shr+ 5044K 1340K 122 0516F000 2896 30 2048 >16M+ 230-0 12K 12K 3 007BF000 3008 3 1600 Own+ 230-1 8K 0K 1 007C9000 0 0 0 Own+ 4K 4K 1 7FFCD000 3584 1 3584 >16M+ 230-5 12K 12K 3 007CD000 8272 9 3888 Own+ 236-1 216K 172K 44 00795000 3880 43 176 Shr+ 8K 0K 1 7F6CD000 0 0 0 >16M+ -----------------------------------------------------------------------------+ PVT-Lo: 0K 0K 0 0 0+ PVT-Hi: 36K 28K 8 14864 13+ SubTot: 36K 28K 8 14864 13+ =============================================================================+ 0-8 956K 376K 79 00005000 48008 73 4088 DFHKETCB Shr+ 5044K 1340K 122 0516F000 2896 30 2048 >16M+ 230-0 4K 4K 1 007C4000 3440 1 3440 Own+ 4K 0K 1 7F6E9000 3480 1 3480 >16M+ 230-1 0K 0K 0 00000000 0 0 0 Own+ 4K 0K 1 7FFCA000 3584 1 3584 >16M



The first portion of the display for each TCB shows:

The next portion of the display summarizes the storage for that TCB.

The final section which appears after all the TCBs are listed, summarizes the storage for the address space.

Sbp-K Subpool number and storage protection key.

Alloc Amount of virtual storage currently allocated to the subpool in 4K increments.

Real Amount of real storage backing the virtual storage allocation.

#Blks Number of 4K blocks allocated to the subpool.

Addr Address of the first block in the subpool.

Free Number of free bytes in hexadecimal in that subpool.

#Blks Number of free blocks within the subpool.

Mxfree Size of the largest free block in hex within the subpool.

Program Program name of the TCB associated with the subpool.

Own | Shr Allocations marked SHR are displayed for each TCB that shares the allocation. Allocations marked OWN appear only for the owning TCB.

PVT-Lo Summary of user storage allocated to the TCB. This is from subpools 0–127 and 250–252.

PVT-Hi Summary of LSQA storage allocated to the TCB.

Subtot Total of user and LSQA storage allocated to the TCB.

Tot-Lo Summary of all user storage allocated to the address space. This is from subpools 0–127 and 250–252.

Tot-Hi Summary of all LSQA storage allocated to the address space.

Totals Total of user and LSQA storage allocated to the address space.



Region StorageOMEGAMON II can display the storage utilization within the private area of the CICS region. It shows the maximum region available, the portion currently in use, and the various areas within the region. To view this information, select the Region Storage option (I) on the Storage path or enter fast path S.I from any panel.

An example of the Region Storage display is shown in Figure 83 on page 192.

FIGURE 83. CICS Region Storage Panel (S.I)

________________ ZREGN VTM TDOCS01 V520./C SYSG 02/03/93 14:00:54> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-Summary B-Violations C-Task Storage D-DSA E-EDSA> F-PAM DSA G-PAM EDSA H-Subpool Groups I-Region Storage J-Compressions===============================================================================> CICS REGION STORAGE PEEK TDOCS01 ASID=112 >> OB8112: Data Collection Initiated << amap+ ===== 2 Gig Line ====== <== 7FFFFFFF Highest 31-bit address+ | |+ |---------------------| <== 7FFFFFFF Top of Extended Private+ | /////////////////// |+ | /// System Area /// | >----------- 4K ELSQA/SWA unallocated+ | /////////////////// | 48K Fragmented free space+ |---------------------| <== 7F6E6000 Current bottom of ELSQA/SWA+ | |+ | Available | >----------- 1,863M Avail. for ELSQA/SWA only+ | |+ |---------------------| <== 0AEFFFFF Extended User Area Limit+ | |+ | Available | >----------- 89,176K Avail. for ELSQA/SWA/USER+ | |+ |---------------------| <== 057E9FFF Current top of Ext. User Area+ | /////////////////// | 3K Largest free block+ | //// User Area //// | >----------- 0K Extended User unallocated+ | /////////////////// | 57K Fragmented free space+ |---------------------| <== 04F00000 Bottom of Extended Private+ | |+ ===== 16 Meg Line ===== <== 00FFFFFF Highest 24-bit address+ | |+ |---------------------| <== 006FFFFF Top of Private+ | /////////////////// |+ | /// System Area /// | >----------- 4K LSQA/SWA unallocated+ | /////////////////// | 78K Fragmented free space+ |---------------------| <== 006B8000 Current bottom of LSQA/SWA+ | |+ | Available | >----------- 1,296K Avail. for LSQA/SWA only+ | |+ |---------------------| <== 00573FFF User Area Limit+ | |+ | Available | >----------- 1,016K Avail. for LSQA/SWA/USER



This panel displays a virtual storage map of the CICS address space. You should ensure sufficient LSQA/SWA/USER(OSCOR) space to prevent S40D and S80A abends. For CICS/ESA, decreasing DSA size increases the free OSCOR space.

This panel provides the following information.

Highest 31-bit address Highest possible address in 31-bit architecture.

Top of extended private Highest address within the extended private area.

ELSQA,SWA unallocated

Amount of storage not currently allocated within the extended system area.

Fragmented free space Amount of free storage within allocated pages of the extended system area.

Current bottom of ELSQA,SWA

Lowest address allocated within the extended private area for the extended system area.

Avail. for ELSQA/SWA only

Amount of unallocated storage between the current bottom of the extended system area and the limit of the extended user area.

Extended User Area Limit

Highest address possible for the extended user area.

Avail. for ELSQA/SWA/USER

Amount of unallocated storage between the extended user area limit and the current top of extended user area. Note that the extended system area can allocate storage within this area.

Current Top of Ext. User Area

Highest address currently allocated within the extended private area for the extended user area.

Largest free block Largest contiguous piece of unallocated storage within the extended user area.

Extended User unallocated

Amount of storage not allocated within the extended user area.

Fragmented free space Amount of free storage within allocated pages of the extended user area.

Bottom of Extended Private

Lowest address currently allocated within the extended private area for the extended user area.



Area descriptions for below the 16M line are as follows:

Highest 24-bit address Highest possible address in 24-bit architecture.

Top of Private Highest address below the common area (start of CSA).

LSQA/SWA unallocated Total of contiguous 4K areas including LSQA, SWA and subpools 229/230.

Fragmented free space Total of areas within LSQA which are each less than the 4K available for allocation as defined by FQEs.

Current bottom of LSQA/SWA

Lowest address allocated to LSQA/SWA subpools.

Avail. for LSQA/SWA only

Total space available for LSQA/SWA allocation. This includes the LSQA/SWA unallocated value and the amount of space in the region available area.

User Area Limit Highest address available for user allocation (region size plus IEALIMIT).

Avail. for LSQA/SWA/USER

Amount of space available for problem program allocations, not including unallocated areas within the region used.

Current top of User Area Highest address currently allocated for problem program use.

Largest free block Largest contiguous area available within the region used.

User unallocated Total of the contiguous 4K areas within the region used which are available for problem program use.

Bottom of Private Lowest address within the private area (above the resident nucleus rounded up to the next 64K boundary).

Prefixed Storage Area Fixed storage location starting with absolute zero.


Storage Display and Alteration

Storage Display and AlterationOMEGAMON II allows you to display, modify and scan the virtual storage of any CICS region or owned dataspace. Refer to “Viewing and Modifying Storage” on page 316 for information on using these features.

Storage Display and Alteration


File Analysis 197

File Analysis

Chapter OverviewFiles such as VSAM and BDAM are key resources to CICS applications. A typical CICS application accepts a request from a terminal-user, searches through or updates files, and sends the results back to the terminal. File access is often the largest component of CICS response time and therefore should be monitored and well-tuned.

In addition to application files, CICS dumps, traces, transient data, and auxiliary temporary storage all reside in VSAM datasets. A VSAM dataset experiencing string or buffer waits, or excessive CI or CA splits, can adversely affect CICS performance.

CICS dump and trace datasets also need to be monitored in case they are filling up too fast. Insufficient library space or improper load library concatenations for STEPLIB or DFHRPL can also cause CICS problems.

Chapter Contents

Accessing the Files Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198

File Allocation and Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199Selecting datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200File detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202Application datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202CICS datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203STEPLIB datasets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204JES datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204DFHRPL datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205Journal datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205IMS datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205SYSIN dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206

VSAM Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207VSAM datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207LSR pools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210String waits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214

11

Accessing the Files Path


Accessing the Files PathTo analyze files such as VSAM, BDAM, load libraries, or journals, select the Files option (F) on the main menu or enter fast path F. from any panel. This displays the Application Datasets panel, which is the initial panel on the Files path. A horizontal menu of the remaining file-related topics appears in the upper portion of each panel in the Files path. For example, see the horizontal menu in the upper part of the panel in Figure 84 on page 199. To directly navigate to the other file options, enter the fast path F.x, where x is the selection letter.

In addition, you can find task-specific file statistics on any task detail display. To access a Task Detail panel, zoom on a specific task from any task summary display. You can find task summaries on the Tasks Path, the Historical Transaction Overview panel (fast path H.A), the VSAM String and Buffer Waits display (fast path F.I), several options on the Databases path, and the Enqueue Resource Detail display (fast path B.H). Scroll through the task detail information until you find file statistics. These statistics consist of counts by type of request for each VSAM or BDAM file accessed by the task.

File Analysis 199

File Allocation and Activity

File Allocation and ActivityTo display a summary of all the files allocated to CICS as shown in the following figure, select the Files option (F) on the main menu and then the All Datasets option (H) on the Files path or enter fast path F.H from any panel.

FIGURE 84. All Datasets Allocated to CICS Panel (F.H)

For each dataset allocated to this CICS region, the dataset summary panel shows the ddname, dataset name, volser, and attributes.

Attributes vary depending on the type of dataset. For CICS datasets, the attribute describes the type of dataset. For IMS datasets, the attribute is IMS/DLI. For CICS journals, the attribute

________________ ZFILE VTM $CICSTOR V520/I SYSA 02/03/99 11:56:29> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Application Datasets B-CICS Datasets C-STEPLIB D-JES Datasets> E-VSAM Datasets F-LSR Pools G-DFHRPL H-All Datasets> I-VSAM String Waits J-Journal Datasets K-IMS Datasets L-Select Files===============================================================================> ALL DATASETS ALLOCATED TO CICS FILE+ Number of files selected: 153 Skipped: 0+ DDname Dataset name VOLSER Attributes+ -------- -------------------------------------------- ------ ----------+ STEPLIB CICS.V3R1.LOADLIB1 PPSMP5 Blk=32760+ PP.DB2.TARG.DSNLOAD PPSMPE Blk=32760+ PP.DB2.V2R2.DSNEXIT PPSMP7 Blk=06233+ CANDLE.OCES.LOADLIB PPSMP4 Blk=06144+ DFHRPL PP.DB2.CICS.DSNLOAD PPSMP3 Blk=32760+ CICS.CICS52.ACF2LOAD PPSMP4 Blk=06144+ CICS.V3R1.LOADLIB PPSMP1 Blk=06144+ CICS.V210.DCSP.LOADLIB CAN003 Blk=32760+ PROD.FINDBS.CICSLOAD LRG002 Blk=06144+ PP.CSP.AE.V330.AELOAD PPSMPE Blk=06144+ PP.CSP.AE.V330.PRODLOAD PPSMPE Blk=06144+ PP.CSP.AD.V330.ADLOAD PPSMP2 Blk=06144+ CICS.MIGR.TABLOAD PPSMP8 Blk=06144+ IDMI.PROD.LOADLIB MIS001 Blk=23476+ IDMI.PROD.LOAD DB2002 Blk=23476+ CICS.PROD.USER.LOAD OMON28 Blk=06144+ PP.DB2.TARG.DSNLOAD PPSMPE Blk=32760+ PP.DB2.V2R1.RUNLIB.LOAD CAN001 Blk=06233+ PP.DB2.RUNLIB.LOAD PPSMPE Blk=06233+ CANDLE.OCES.LOADLIB PPSMP4 Blk=06144+ PP.PLI.PLIBASE PPSMPE Blk=32760+ PP.PLI.PLILINK PPSMP8 Blk=32760+ PP.PLI.PLICICS PPSMPE Blk=32760+ PP.INTERTST.V311.LOADLIB CAN003 Blk=06144+ PP.PLAY.LOADLIB CAN003 Blk=06144+ GLOBAL_OPTIONSAA NULLFILE *JES* Nullfile+ ACF2STRG PROD.CIMGNN.$CICSTOR.ACF2STRG PRI001 Disp=shr+ ACF2PARM CAN.PARMLIB CAN001 Disp=shr+ DFHDMPA CICSV.V311.$TOR.DFHDMPA PPSMP1 Dump(A)+ DFHDMPB CICSV.V311.$TOR.DFHDMPB PPSMP1 Dump(B)+ DFHSTM PROD.CIMGNN.$CICSTOR.DFHSTM PRI001 AutoStat



describes the status. For application datasets, the attribute describes the status or number of strings in use. For all other datasets, the attribute describes a JES-related status or disposition.

For a more detailed display of a specific dataset, place the cursor on your choice and press PF11 to zoom.

Selecting datasetsTo limit a dataset summary to a specific or generic ddname, enter FILE=ccccccc* (* indicates generic) after the FILE statement. For example, for ddnames starting with TEST:

FILE FILE=TEST*

To limit a dataset summary to a specific or generic high-level dsname qualifier, enter DSN=ccccccc* (* indicates generic) after the FILE statement. For example, for files with high-level dsname CICSTEST:

FILE DSN=CICSTEST

To limit a dataset summary to files on a specific or generic volser, enter VOL=volser* (* indicates generic) after the FILE statement. For example, for files on volsers starting with DEV1:

FILE VOL=DEV1*

To limit a dataset summary to files with a specific disposition, enter DISP=disp after the FILE statement, where disp may be MOD, NEW, OLD, or SHR. For example, for all files allocated to CICS with DISP=SHR:

FILE DISP=SHR

Also, you can limit the summary display to datasets that meet several different criteria at once. To help you specify the selection criteria, select the Select Files option (L) on the Files path or enter fast path F.L from any panel.

The summary display is identical to the one in the previous figure but the FILE statement includes the various parameters you can use to filter the summary display. The FILE statement is shown in the following figure.

File Analysis 201


FIGURE 85. Select Datasets Panel (F.L)

You can enter a specific or generic value for the ddname, high-level dataset name qualifier, volser, or disposition. A generic name is specified as any number of characters followed by an asterisk(*). The * by itself specifies ALL.

For example, to display datasets with ddname starting with ABC, a high-level dsname qualifier of TEST, that reside on volser CICS01, and are of any disposition:

FILE DDNAME=ABC* DSN=TEST VOL=CICS01 DISP=*

________________ ZFSEL VTM $CICSTOR V520/I SYSA 02/03/99 11:50:07> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Application Datasets B-CICS Datasets C-STEPLIB D-JES Datasets> E-VSAM Datasets F-LSR Pools G-DFHRPL H-All Datasets> I-VSAM String Waits J-Journal Datasets K-IMS Datasets L-Select Files===============================================================================> SELECT DATASETS ALLOCATED TO CICS > To limit the summary display to the desired datasets, modify ddname,> high-level dataset name qualifier, volume serial, or disposition. FILE DDNAME=* DSNHILEV=* VOLUME=* DISP=SHR+ Number of files selected: 119 Skipped: 0+ DDname Dataset name VOLSER Attributes+ -------- -------------------------------------------- ------ ----------+ STEPLIB CICS.V3R1.LOADLIB1 PPSMP5 Blk=32760+ DFHRPL PP.DB2.CICS.DSNLOAD PPSMP3 Blk=32760+ ACF2STRG PROD.CIMGNN.$CICSTOR.ACF2STRG PRI001 Disp=shr+ ACF2PARM CAN.PARMLIB CAN001 Disp=shr+ DFHDMPA CICSV.V311.$TOR.DFHDMPA PPSMP1 Dump(A)+ DFHDMPB CICSV.V311.$TOR.DFHDMPB PPSMP1 Dump(B)+ DFHSTM PROD.CIMGNN.$CICSTOR.DFHSTM PRI001 AutoStat+ DFHSTN PROD.CIMGNN.$CICSTOR.DFHSTN PRI001 AutoStat+ DFHAUXT CICSV.V311.$TOR.DFHAUXT PPSMP1 Trace(A)+ DFHBUXT CICSV.V311.$TOR.DFHBUXT PPSMP1 Trace(B)+ DFHCSD CICSV.V311.DTOR.DFHCSD PPSMP8 Closed+ DFHRSD CICSV.V311.$TOR.DFHRSD PPSMP1 Restart+ DFHLCD CICSV.V311.$TOR.DFHLCD PPSMP1 Catalog+ DFHGCD CICSV.V311.$TOR.DFHGCD PPSMP1 Catalog+ DFHJ01X CICSV.V311.$TOR.DFHJ01X PPSMP1 Closed+ DFHJ01A CICSV.V311.$TOR.DFHJ01A PPSMP1 Closed+ DFHJ01B CICSV.V311.$TOR.DFHJ01B PPSMP1 In use+ DFHJ02A PROD.CIMGNN.$CICSTOR.DFHJ02A PRI001 In use+ DFHJ02B PROD.CIMGNN.$CICSTOR.DFHJ02B PRI001 Closed+ PLAYIN1 PROD.CIMGNN.$CICSTOR.PLAYIN1 PRI001 Disp=shr+ PLAYIN2 PROD.CIMGNN.$CICSTOR.PLAYIN2 PRI001 Disp=shr



File detailTo view detailed information on a particular file, place the cursor on the dataset line of your choice on a dataset summary display and press PF11. The detailed display contains information common to all file types followed by an additional segment that varies depending on the file type. The following figure shows the information common to all file types.

FIGURE 86. File Detail Panel (Accessed by Zoom)

This panel displays file allocation and usage information for the selected file.

For further information on the file, place the cursor on a zoomable field and press PF11. Zoomable fields are highlighted in white.

Application datasetsApplication datasets are those datasets defined in the File Control Table (FCT). For CICS/ESA, you may define files via CEDA. To display application datasets, select the Application Datasets option (A) or enter fast path F.A from any panel.

For each dataset, you can see the ddname, dataset name, volser, and attributes. The Attributes field describes the status in the FCT:

n number of strings in use (yellow if some strings or red if all strings)

n closed (if VSAM)

n open/disabled (if VSAM)

n open/LSR (if VSAM, open, enabled, no strings in use, LSR)

n open/NSR (if VSAM, open, enabled, no strings in use, no LSR)

n open BDAM

n closed BDAM

____________ ZZFILE VTM TDOCS01 V520/C SYSA 02/03/99 12:00:41> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ===============================================================================> FILE DETAIL FILE DD=DEG++ Dataset name . . . . . : TDCICS1.TOC.TDOCS01.DEGFILE+ Volume serial number . : OMON25 Primary allocation . . : n/a+ Device address . . . . : 30B Secondary allocation . : n/a+ Organization . . . . . : VSAM Number of extents . . . : n/a+ Record format . . . . . : VSAM Disposition . . . . . . : Shr+ Record length . . . . . : n/a Creation date . . . . . : 04/18/90+ Blocksize . . . . . . . : n/a Expiration date . . . . : None+ EXCP count . . . . . . : 46===============================================================================

File Analysis 203


You can limit the application datasets summary to specific or generic ddnames, dsnames, volumes or dispositions by entering selection parameters after the FILE SELECT=FCT statement (see “Selecting datasets” on page 200).

The additional segment in the application file detail display shows statistics from the File Control Table entry. See “File Control Table (FCT)” on page 250 for more information about the FCT entry.

CICS datasetsCICS datasets begin with DFH except that DFHRPL and journals have separate options on the Files path. To display CICS datasets, select the CICS Datasets option (B) on the Files path or enter fast path F.B from any panel.

The Attributes field describes the dataset:

You can limit the CICS datasets summary to specific or generic ddnames, dsnames, volumes, or dispositions by entering selection parameters after the FILE SELECT=CICS statement (see “Selecting datasets” on page 200).

Trace (A/B) Trace datasets DFHAUXT and DFHBUXT.

RDO status CICS system definition dataset DFHCSD.

Dump (A/B) CICS dump datasets DFHDMPA and DFHDMPB.

Catalog Global catalog dataset DFHGCD.

TranData Transient data dataset DFHINTRA.

Jrn/Arch Journal output dataset DFHJOUT.

Jrn/Arch Journal partition dataset DFHJPDS.

Catalog Local catalog dataset DFHLCD.

Sysout Sysout datasets DFHSNAP or SYSUDUMP.

Sysprint Sysprint dataset DFHPRINT.

Restart Restart dataset DFHRSD.

Stats Statistics datasets DFHSTM and DFHSTN.

TempStor Temporary storage dataset DFHTEMP.

XRF/Cavm Extended recovery control dataset (CAVM) DFHXRCTL.

XRF/Msgs Extended recovery facility messages dataset DFHRMSG.



For CICS datasets, the additional segment in the file detail display is related to the type of file as follows:

STEPLIB datasetsThe STEPLIB summary contains all datasets in the STEPLIB concatenation in the order defined in the CICS job. To display STEPLIB datasets, select the STEPLIB option (C) on the Files path or enter fast path F.C from any panel.

The Attributes field shows the blocksize of each dataset. If the leading library in the concatenation is overridden with a larger blocksize, the attribute field still shows the true blocksize rather than the blocksize currently used.

The additional segment in the STEPLIB file detail display shows all the MVS loaded modules in the CICS address space. The list of modules is loaded from all datasets in the concatenation sequence, not necessarily from the one you selected by zooming.

JES datasetsTo display JES datasets allocated to the CICS region, select the JES Datasets option (D) on the Files path or enter fast path F.D from any panel.

The attribute field describes a JES-related status or disposition such as Sysout, Sysprint, Nullfile, DISP=Mod, New, Old, or Shr.

You can limit the JES dataset summary to specific or generic ddnames, dsnames, volumes, or dispositions by entering selection parameters after the FILE SELECT=JES statement (see “Selecting datasets” on page 200).

Trace dataset Trace component overview.

RDO dataset FCT entry.

Dump dataset Dump component overview.

Catalog dataset VSAM dataset information.

TD dataset Transient data overview.

TS dataset Temporary storage overview.

Restart dataset VSAM dataset information.

XRF dataset Extended recovery facility status.

File Analysis 205


DFHRPL datasetsTo display DFHRPL datasets, select the DFHRPL option (G) or enter fast path F.G from any panel.

The attributes field shows the blocksize of each dataset. If the leading library in the concatenation is overridden with a larger blocksize, the attribute field still shows the true blocksize rather than the blocksize currently used.

You can determine from which load library a load module originates. This can help you to identify whether the appropriate version or library is being used.

Space allocation, extent count, and creation date can help you anticipate the need to reorganize and compress libraries. This data displays when you request file detail. The additional segment of the file detail display for a DFHRPL dataset shows the PPT entries associated with that library.

Journal datasetsTo display journal datasets, select the Journal Datasets option (J) on the Files path or enter fast path F.J from any panel.

The summary display shows all journals allocated to CICS. The attribute field shows the status of the journal from among the following:

n in usen closedn switchingn waiting for an outstanding WTORn tapelogn no JCT entry found in the Journal Control TableA status of Waiting for an outstanding WTOR needs immediate attention as CICS transactions using that journal might not be able to continue until the WTOR is resolved.

You can limit the journal datasets display to generic or specific ddnames, dsnames, volumes, or dispositions by entering selection parameters after the FILE SELECT=JCT statement (see “Selecting datasets” on page 200).

The additional segment in a journal file detail display is the JCT entry.

IMS datasetsThe IMS summary display shows IMS datasets that begin with DFS, IMS or PROCLIB, that are allocated to the CICS region. To display IMS datasets, select the IMS Datasets option (K) on the Files path or enter fast path F.K from any panel.

You can limit the IMS datasets to specific or generic ddnames, dsnames, volumes, or dispositions by entering selection parameters after the FILE SELECT=IMS statement (see “Selecting datasets” on page 200).

The additional segment in the IMS file detail display contains DLI status information.



SYSIN datasetThe SYSIN dataset is available by selecting the All Datasets option (H) on the Files path. This dataset contains overrides to the CICS System Initialization Table values. The additional segment in the SYSIN file detail display shows the SIT.

File Analysis 207

VSAM Information

VSAM InformationVSAM information shows you activity related to:

n open VSAM datasets for which you can display string waits, I/O activity, and CI/CA splits

n LSR pools for which you can display string activity and successful lookaside ratios for strings and buffers in each pool

VSAM datasetsTo display summary information for all open VSAM files as shown in the following figure, select the VSAM Datasets option (E) on the Files path or enter fast path F.E from any panel.

FIGURE 87. VSAM Summary Panel (F.E)

________________ ZVSAM VTM $CICSTOR V520/I SYSA 02/03/99 14:56:53> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Application Datasets B-CICS Datasets C-STEPLIB D-JES Datasets> E-VSAM Datasets F-LSR Pools G-DFHRPL H-All Datasets> I-VSAM String Waits J-Journal Datasets K-IMS Datasets L-Select FIles===============================================================================> ALL OPEN VSAM FILES VSAM+ Number of files selected: 93 Skipped: 0+ File File Str Wts Str Wts Data Data Data+ ID Status Current Total Excps CI Split CA Split+ -------- -------- -------- -------- -------- -------- --------+ DFHLCD No FCT n/a n/a n/a 0 0+ DFHGCD No FCT n/a n/a n/a 456 0+ DFHRSD No FCT n/a n/a n/a 246 1+ APFH120 Enabled 0 0 80 0 0+ APFL905 Enabled 0 0 3277 117 13+ APFM100 Enabled 0 0 5315 179 25+ CCFM100 Enabled 0 0 182 0 0+ CCFM200 Enabled 0 0 660 8 0+ CCFM300 Enabled 0 0 0 0 0+ CM827 Enabled 0 0 0 0 0+ DMCUST Enabled 0 0 654 0 0+ DMDCF Enabled 0 0 0 0 0+ DMINV Enabled 0 0 0 0 0+ FCFMGMD Enabled 0 0 634 51 17+ FCFMPOL Enabled 0 0 98 0 0+ FCFMTMD Enabled 0 0 310 0 0+ GLFMBUD Enabled 0 0 0 6 6+ GLTRX1 Enabled 0 0 0 0 0+ GMF55 Enabled 0 0 0 0 0+ GMP11 Enabled 0 0 634 51 17+ GMP21 Enabled 0 0 0 0 0

VSAM Information


This panel shows a summary of all open VSAM files including:

n ddname or FCT entry name

n current file status if FCT-defined

n current number of string waits

n total string waits since file opened

n EXCPs on the data component

n number of control interval splits in the data component

n number of control area splits in the data component

A high number of splits, especially CA splits, can significantly degrade the time to access the file. String waits cause tasks to wait and too many can degrade response time.

To view detailed statistics on a particular VSAM file, position the cursor anywhere on the line describing the file and press PF11 or enter the 1- to 8-character file ID following the VSAM statement. For example, to view details for file APFM910, enter:

VSAM APFM910

The VSAM File Detail panel appears as shown in the following figure.

File Analysis 209

VSAM Information

FIGURE 88. VSAM File Detail Panel (Accessed by Zoom)

The VSAM file detail panel shows

n general information such as dsname, organization, ACB information, string information, open/close error code, active strings, and whether the file is using LSR

n data and index component information such as number and type of accesses, splits, freespace, extents, writechecks, and shareoptions

n FCT statistics if the file is FCT-defined n temporary storage or transient data usage statistics if the file contains TS or TD Note: Depending on the file organization or whether the file uses LSR or NSR, you may

receive different data on the panel.

________________ ZZVSAM VTM $CICSTOR V520/I SYSA 02/03/99 14:59:48> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down ===============================================================================> FILE DETAIL VSAM APFM910+ General Information+ File dataset name . . . : PROD.FINAPV.APFM910+ File organization . . . : KSDS ACB address . . . . . . : 007B5BA4+ Open/close error code . : 0 File is NSR or LSR . . : NSR+ ACB strings . . . . . . : 2 High water act. strings : 1+ Active strings . . . . : 0++ Data Component of KSDS Dataset+ Data Component . . . . : PROD.FINAPV.APFM910.DATA+ Control area splits . . : 1 Control interval splits : 18+ Number of EXCPs . . . . : 22684 Control interval size . : 4096+ Number of records . . . : 476630 Number of inserts . . . : 1186+ Number of retrieves . . : 953703 Number of updates . . . : 0+ Number of deletes . . . : 270 Freespace percentages . : 010,025+ Available space . . . . : 29216768 Allocated extents . . . : 4+ Volume serial number . : DBCR04 Device address . . . . : 162+ Allocation type . . . . : Cylinder Primary allocation amt : 25+ Secondary allocation amt: 17 Maximum record length . : 120+ Number of I/O buffers . : 3+ Writecheck used . . . . : No Shareoptions specified : (2,3)++ Index Component of KSDS Dataset+ Index Component . . . . : PROD.FINAPV.APFM910.INDEX+ Control area splits . . : 0 Control interval splits : 1+ Number of EXCPs . . . . : 5037 Control interval size . : 2048+ Number of records . . . : 54 Number of inserts . . . : 0+ Number of retrieves . . : 0 Number of updates . . . : 22+ Number of deletes . . . : 0 Number of index levels : 2+ Relative key position . : 0 Key length . . . . . . : 48+ Available space . . . . : 61440 Allocated extents . . . : 3+ Volume serial number . : DBCR04 Device address . . . . : 162+ Allocation type . . . . : Track Primary Allocation Amt : 2+ Secondary Allocation Amt: 1 Maximum Record Length . : 2041+ Number of I/O buffers . : 2+ Writecheck used . . . . : No Shareoptions specified : (2,3)+ Imbed or replicate . . : Neither+

VSAM Information


LSR poolsTo display summary information for local shared resource (LSR) pools in CICS, either for VSAM files or local DL/I databases, select the LSR Pools option (F) on the Files path or enter fast path F.F from any panel.

The LSR summary display appears as shown in the following figure.

FIGURE 89. LSR Pool Summary Panel (F.F)

This panel shows both CICS and VSAM information.

You should tune the number of strings for each pool to keep any string waits down to an absolute minimum. Overspecifying strings to eliminate string waits uses additional virtual storage.

The lookaside ratio shows the percentage of input requests that were able to be serviced from the buffers in virtual storage instead of having to read the file.

If CEDA was used to define the LSR pool, the index component buffers are separated from the data component buffers. In this case the lookaside ratio is based on the combined index and data component buffers. An LSR pool created without CEDA has no index component; its index and data components share buffers.

No buffer or Hiperspace statistics display for closed LSR pools. Hiperspace statistics do not exist for LSR pool 00.

CICS creates each LSR pool when the first file that uses it is opened, and deletes the pool when the last file that uses it is closed. OMEGAMON II collects all available statistics for each pool that has had at least one open dataset since OMEGAMON II startup.

To limit the summary to only DLI or CICS pools, enter IMS or CICS after the LSR statement. For example, to display all DLI LSR pools, enter:

________________ ZLSR VTM $CICSTOR V520/I SYSA 02/03/99 15:01:16> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Application Datasets B-CICS Datasets C-STEPLIB D-JES Datasets> E-VSAM Datasets F-LSR Pools G-DFHRPL H-All Datasets> I-VSAM String Waits J-Journal Datasets K-IMS Datasets L-Select Files===============================================================================> LOCAL SHARED RESOURCES POOLS SUMMARY LSR+ Number of pools selected: 8+ LSR Pool Active Str Wts Str Wts No. of Lk-aside+ Pool Status Strings Current HWM Strings Ratio+ -------- -------- -------- -------- -------- -------- --------+ CICS 01 Created 0 0 0 100 90.6%+ CICS 02 Notbuilt 0 0 0 0 0.0%+ CICS 03 Notbuilt 0 0 0 0 0.0%+ CICS 04 Notbuilt 0 0 0 0 0.0%+ CICS 05 Notbuilt 0 0 0 0 0.0%+ CICS 06 Notbuilt 0 0 0 0 0.0%+ CICS 07 Notbuilt 0 0 0 0 0.0%+ CICS 08 Notbuilt 0 0 0 0 0.0%===============================================================================

File Analysis 211

VSAM Information

LSR IMS

For a detailed view of an individual LSR pool, place the cursor on the line describing the pool and press PF11.

Or you can enter POOL=nn after the LSR statement. For example, to display detail for LSR pool 01, enter:

LSR POOL=01

The LSR Pool Detail panel appears as shown in the following figure.

VSAM Information


FIGURE 90. LSR Pool Detail Panel (Accessed by Zoom)

If you used CEDA to define the LSR pool, this panel displays separate data and index component buffers and Hiperspace buffers.

Lookaside success ratios for Hiperspace buffers are normally high, because CICS does not retrieve records from Hiperspace unless it determines that the record is likely to be there. CICS makes this determination by hashing the record to obtain a synonym and then checking its synonym table for the synonym. If CICS is swapped out, the Hiperspace buffers are

________________ ZZLSR VTM $CICSTOR V520/I SYSA 02/03/99 15:04:19> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ===============================================================================> LSR POOL DETAIL LSR POOL=01+ CICS Pool 01 - General Information++ Pool status . . . . . . : Created Location of pool . . . : >16M+ Time pool created . . . : 06:00:35 Time pool deleted . . . : n/a+ Number of open ACBs . . : 70 Maximum keylength . . . : 200+ Total strings . . . . . : 100 String waits (Total) . : 0+ Active strings (Current): 0 String waits (Current) : 0+ Active strings (HWM) . : 4 String waits (HWM) . . : 0++ VSAM Data Buffer Statistics+ Buffer No. of Lk-aside Buffer Buffer Writes Lk-aside+ Size Buffers Hits Reads Writes Non-user Ratio+ -------- -------- -------- -------- -------- -------- --------+ 1024 20 0 0 0 0 0.0%+ 2048 20 10309 1414 1156 0 87.9%+ 4096 20 44124 15216 6672 0 74.4%+ 24576 10 14320 5566 6315 0 72.0%++ VSAM Index Buffer Statistics+ Buffer No. of Lk-aside Buffer Buffer Writes Lk-aside+ Size Buffers Hits Reads Writes Non-user Ratio+ -------- -------- -------- -------- -------- -------- --------+ 512 50 47839 110 116 0 99.8%+ 1024 50 29524 157 30 0 99.5%+ 2048 20 81310 2340 189 0 97.2%+ 4096 20 12702 126 85 0 99.0%+ 8192 20 0 0 0 0 0.0%++ Hiperspace Data Buffer Statistics+ Buffer No. of Reads Reads Writes Writes Success+ Size Buffers Success Fail Success Fail Ratio+ -------- -------- -------- -------- -------- -------- --------+ 4096 15 0 0 0 0 0.0%+ 8192 10 0 0 0 0 0.0%+ 12288 10 0 0 0 0 0.0%++ Hiperspace Index Buffer Statistics+ Buffer No. of Reads Reads Writes Writes Success+ Size Buffers Success Fail Success Fail Ratio+ -------- -------- -------- -------- -------- -------- --------+ 12288 10 0 0 0 0 0.0%===============================================================================

File Analysis 213

VSAM Information

discarded, but the synonym table remains. This can cause the success ratio to fall. CICS regions that use Hiperspace buffers should be specified nonswappable.

To see the files using this LSR pool, place the cursor on the Number of Open ACBs field, and press PF11 to zoom.

The File Using Specific LSR Pool panel appears as shown in the following figure.

FIGURE 91. Files Using Specific LSR Pool (Accessed by Zoom)

This panel is an FCT summary display for FCT entries specifying LSR Pool 01 which shows:

n ddname or FCT name

n since LSR, access method is always VSAM

n status such as open, closed, enabled, disabled

n record format such as fixed blocked or variable blocked

n number of active strings

n if remote, SYSID of remote system where file resides

For more information about FCT displays, see “File Control Table (FCT)” on page 250.

________________ ZFLSR VTM $CICSTOR V520/I SYSA 02/03/99 15:05:44> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ===============================================================================> FILES USING SPECIFIC LSR POOL TABL FCT SEL=LSR01+ Entries selected: 87 Skipped: 0+ File File File Data Share Active Remote+ ID Access Status Format Control Strings System+ -------- -------- -------- -------- -------- -------- --------+ APFH120 VSAM Ena Ope FB Lsrpool1 0 n/a+ APFM100 VSAM Ena Ope VB Lsrpool1 0 n/a+ APFM200 VSAM Ena Ope FB Lsrpool1 0 n/a+ APFM400 VSAM Ena Ope VB Lsrpool1 0 n/a+ APFM930 VSAM Ena Ope VB Lsrpool1 0 n/a+ CCFM100 VSAM Ena Ope VB Lsrpool1 0 n/a+ CCFM200 VSAM Ena Ope VB Lsrpool1 0 n/a+ CCFM300 VSAM Ena Ope VB Lsrpool1 0 n/a+ CCFM910 VSAM Ena Ope FB Lsrpool1 0 n/a+ CCFM920 VSAM Ena Ope VB Lsrpool1 0 n/a+ CM827 VSAM Ena Ope FB Lsrpool1 0 n/a+ DMCUST VSAM Ena Ope FB Lsrpool1 0 n/a+ DMDCF VSAM Ena Ope FB Lsrpool1 0 n/a+ DMINV VSAM Ena Ope FB Lsrpool1 0 n/a+ FCDEMOG VSAM Ena Clo FB Lsrpool1 0 n/a+ FCDEMOT VSAM Ena Clo FB Lsrpool1 0 n/a+ FCFMARF VSAM Ena Clo FB Lsrpool1 0 n/a+ FCFMAUD VSAM Ena Clo FB Lsrpool1 0 n/a===============================================================================

VSAM Information


String waitsTo display the files currently experiencing VSAM string or LSR buffer waits, select the VSAM String Waits option (I) on the Files path or enter fast path F.I from any panel. The VSAM String and Buffer Waits panel appears as shown in the following figure.

FIGURE 92. String and Buffer Waits Panel (F.I)

Each string represents a concurrent request for access to a VSAM file. The summary display shows, for each file, the tasks that are currently using strings and the tasks that are waiting for strings and LSR buffers. Information appears only for files that are defined in the FCT.

For tasks holding strings, OMEGAMON II displays the wait reason and resource causing the wait. Since certain waits, such as a TC-I/O wait for terminal input could be long-running, you might want to purge that task to free up the string.

You can display detailed information for the task by placing the cursor on the transaction ID and pressing PF11. For information on the task detail display and the steps required to purge a task, see “Task Detail” on page 91 and “Killing a Task” on page 105.

To see detailed information on a file, place the cursor on the filename and press PF11. OMEGAMON II displays detailed file information as shown in Figure 88 on page 209.

____________ ZCVSW VTM TDOCS01 V520/C SYSA 02/03/99 12:51:57> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Application Datasets B-CICS Datasets C-STEPLIB D-JES Datasets> E-VSAM Datasets F-LSR Pools G-DFHRPL H-All Datasets> I-VSAM String Waits J-Journal Datasets K-IMS Datasets L-Select Files===============================================================================> VSAM STRING and BUFFER WAITS CVSW+ File Tran Task Task String Resource Resource+ ID ID Number Status Type Type Name+ -------- -------- -------- -------- -------- -------- --------+ DEG DEGV 57 Waiting Add/upd FCPSWAIT DEG+ DEG DEGV 38 Owning Add/upd KCCOMPAT SUSPEND++ File id=DEG : Current LSR buffer wait count=1, high water mark=3================================================================================

Database Analysis 215

Database Analysis

Chapter OverviewDatabases such as DLI or DB2 are key resources to major CICS applications. A typical CICS application accepts a request from a terminal-user, searches through or updates database(s), and sends the results back to the terminal. Large, complex applications rely on integrated data accessible through a database or sets of interrelated databases. Database access is often the slowest part of CICS response time and therefore should be monitored and well-tuned.

Chapter ContentsAccessing the Databases Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216DB2 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217DLI Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219

DLI Summary panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219DLI General Information panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221DLI databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222DLI subpools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224DLI ECBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225DLI addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226DBCTL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227

12

Accessing the Databases Path


Accessing the Databases PathTo access DLI or DB2 information, select the Databases option (D) on the main menu or enter fast path D. from any panel. The initial panel on the Database path varies depending on the type of database system installed in your CICS region; it may be DLI Summary, DB2 Interface, or DBCTL Interface. A horizontal menu of the remaining database-related topics appears in the upper portion of each panel in the Databases path. To directly navigate to the other database options, enter one of the selection letters listed on the horizontal menu. Or enter the fast path D.C from any menu system panel.

In addition, you can find task-specific database statistics on any task detail display. These statistics consist of counts by type of request or call for each DLI or third-party database. To access a Task Detail display, zoom on a specific task from any task summary display. You can find task summaries on several options on the Tasks path (fast path T.), the Historical Transaction Overview display (fast path H.), the VSAM String and Buffer Waits display (fast path F.I), several options on the Databases path, and the Enqueue Resources Detail display (fast path B.H). Note that one of the options on the Tasks path is a summary of Tasks using DLI (fast path T.F.D).


DB2 Interface

DB2 InterfaceTo display information on the status of the CICS/DB2 attachment facility as well as transaction activity, select the Databases option (D) on the main menu or enter fast path D. from any panel. The DB2 display is the initial selection on the Databases path if DB2 is attached to this CICS region.

DB2 interface information is shown in Figure 93 on page 217.

FIGURE 93. CICS/DB2 Interface Panel (D.)

The General Information portion of this panel shows DSNCRCT TYPE=INIT specifications. For information about these fields, refer to IBM’s DB2 System and Administration Guide.

________________ ZDB2 VTM TDOCS15 V520/C SYSG 02/03/99 11:18:08> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-DB2 B-DLI Summary C-DLI General Info D-DLI Databases> E-DLI Subpools F-DLI ECBs G-DLI Addresses H-DBCTL===============================================================================> CICS/DB2 INTERFACE SUMMARY DB2+ General Information+ DSNCRCT name . . . . . : DSNCRCT3 Statistics destination : CSSL+ Error message destid 1 : CSMT SNAP dump output class : A+ Error message destid 2 : n/a CICS authorization name : TDOCS15+ Error message destid 3 : n/a DB2 subsystem name . . : D23A+ Start wait . . . . . . : Yes THRD purge time interval: 30+ Traceid 1 . . . . . . . : 192 Traceid 2 . . . . . . . : 193+ Traceid 3 . . . . . . . : 194 MAX allowable threads . : 20+ Active MVS subtasks . . : 18++ Transactions With Active Threads++ Tran Count of Count of Count of Max Act Threads Threads+ ID Calls Waits Aborts Threads Used HWM In Use+ -------- -------- -------- -------- -------- -------- --------+ DSNC 8 1 0 1 0 0+ POOL 3 1 0 3 0 0===============================================================================

DB2 Interface


In the lower portion of the panel, you see a list of all transactions defined as part of the DB2 plan that have had some DB2 activity. Data is displayed by transaction, not task, as follows:

For detail information on an active transaction, place the cursor on the line containing the transaction ID and press PF11. For details about a transaction without an active thread, enter the transaction ID following the DB2 statement. For example, to display detail for inactive DB2 transaction D8CS, enter:

DB2 D8CS

DB2 transaction detail appears as in the following figure.

FIGURE 94. DB2 Transaction Detail Panel (Accessed by Zoom)

This panel shows a count of read-only commits only for DB2 release 2.2 and above.

Tran ID Transaction name.

Count of Calls Number of SQL calls issued.

Count of Waits Number of times the transaction had to wait for a thread.

Count of Aborts Number of aborts.

Max Act Threads Maximum number of active threads defined in the RCT.

Threads Used HWM Maximum number of threads used since the connection was started.

Threads In Use Current number of threads in use.

____________ ZZDB2 VTM TDOCS01 V520/C SYSA 02/03/99 13:14:02> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down ===============================================================================> DB2 TRANSACTION DETAIL DB2 D8CS+ Detail Information+ Transaction ID . . . . : D8CS Entry type . . . . . . : Txid+ Plan name . . . . . . . : DSN8CH13 Plan exit program . . . : E XITPGM3+ Thread TCB priority . . : Low Thread wait . . . . . . : POOL+ Rollback on deadlock . : No++ Statistics Information+ Count of calls . . . . : 17 Maximum threads . . . . : 7+ Count of commits . . . : 17 Maximum active threads : 5+ Count of authorization : 0 Thread subtasks started : 2+ Count of aborts . . . . : 0 Threads currently used : 2+ Count of waits . . . . : 2 Highwater thread use . : 1+ Count of RO commits . . : 12+ Authorization option . : (Userid,Userid,Userid)===============================================================================


DLI Analysis

DLI Analysis OMEGAMON II provides information on local DLI and DBCTL databases. Local DLI database support includes activity for each database and the transactions currently accessing them. DBCTL support includes the status of the CICS/DBCTL connection.

DLI Summary panelTo display information on the status of DLI activity, select the DLI Summary option (B) on the Databases path or enter fast path D.B from any panel. The DLI Summary panel is the initial selection when local DLI (and not DB2) is installed in the CICS region.

The DLI Summary panel appears as shown in the following figure.

FIGURE 95. DLI Summary Panel (D.B)

________________ ZDLI VTM TDOCS01 V520/C SYSG 02/03/99 11:26:06> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-DB2 B-DLI Summary C-DLI General Info D-DLI Databases> E-DLI Subpools F-DLI ECBs G-DLI Addresses H-DBCTL===============================================================================> DLI SUMMARY DLI+ CICS/DLI Activity Summary+ THREAD wait : 0 DMBPL wait : 0 PSBPL wait : 0+ DLTHREAD . : 5 In use . . : 0 Average . . : n/a+ DMBPL size : 18432 In use . . : 2320 Ratio . . . : 12.6%+ PSBPL size : 18432 In use . . : 3312 Ratio . . . : 18.0%+ ENQPL size : 18432 In use . . : 16 ENQPL HWM . : 1024+ Calls active for DLI . : 0 Calls active for DLI HWM: 1++ ISB Subpool Summary+ Tran Task Program Schedule PSB ISB PST+ ID Number Name Time Name Status Address+ -------- -------- -------- -------- -------- -------- --------+ TINQ 917 ZC2COINQ 11:26.01 PC2COINQ PSB Schd 00429000===============================================================================

DLI Analysis


The Activity Summary portion of this panel reflects subpool usage for local DLI requests as follows:

The ISB Subpool Summary portion in the lower part of the DLI Summary panel shows any transactions with scheduled PSBs as follows:

For detailed information about a transaction that has scheduled a PSB, place the cursor on the line containing the task and press PF11. See “Task Detail” on page 91 for a description of the task detail fields displayed.

Thread Wait Number of transactions which had to wait for a DLI thread to become available.

DMBPL Wait Number of transactions for data management block pool storage.

PSBPL Wait Number of transactions for program specification block pool storage.

DLTHREAD Total number of DLI threads defined in the SIT.

DMBPL Size Size of data management block pool defined in the SIT followed by amount in use and percentage used.

PSBPL Size Size of program specification block pool defined in the SIT followed by amount in use and percentage used.

ENQPL Size Size of the enqueue pool defined in the SIT followed by amount in use and percentage used.

Calls Active Current number of active DLI calls.

Calls Active HWM Highwater mark of active DLI calls.

Tran ID Transaction ID for this transaction.

Task Number Task Number assigned by CICS to this transaction.

Program Name Name of the scheduling program.

Schedule Time Time when ISB was scheduled.

PSB Name Name of the PSB for this transaction.

ISB Status Status of this ISB, such as waiting or scheduled.

PST Address Address of assigned PST.


DLI Analysis

DLI General Information panelTo display DLI general information, select the DLI General Info option (C) on the Databases path or enter fast path D.C from any menu system panel. DLI general information includes static parameter settings. The display is shown in the following figure.

FIGURE 96. DLI General Information Panel (D.C)

This panel shows:

IMS Release IMS release level.

PDIR Suffix PSB directory suffix from the SIT.

DDIR Suffix DMB directory suffix from the SIT.

DLI Startup Option DLI startup options, such as Cold or Emergency.

DLI Log Record No Record number of the next log record to be written.

Scheduling Lock Count

Number of scheduling locks for this DLI.

PI Scheduling Whether program isolation scheduling is in use.

DLI Modules from LPA

Whether the DLI modules from the LPA will be used.

IMS Lock Trace Whether the IMS lock tracing is enabled.

DBM Monitor Whether the DB Monitor is enabled.

DLXCPVR Whether DLI trace is active.

IMS Module Trace Whether DLI trace is active.

IRLM Whether IRLM is active, inactive, or unavailable.

DBRC Whether DBRC is active, inactive, or unavailable.

________________ ZDLGENL VTM TDOCS01 V520/C SYSG 02/03/99 11:26:41> PF1 Help PF3 Back PF4 Main Menu > A-DB2 B-DLI Summary C-DLI General Info D-DLI Databases> E-DLI Subpools F-DLI ECBs G-DLI Addresses H-DBCTL===============================================================================> DLI GENERAL INFORMATION DLI GENERAL+ DLI General Information+ IMS release . . . . . . : 310 PDIR suffix . . . . . . : 31+ DDIR suffix . . . . . . : 31 DLI start-up option . . : Cold+ DLI log record no. . . : 4 Scheduling lock count . : 0+ PI scheduling . . . . . : Yes DLI modules from LPA . : No+ IMS lock trace . . . . : Off DBMonitor . . . . . . . : Off+ DLXCPVR . . . . . . . . : No IMS module trace . . . : Off+ IRLM . . . . . . . . . : No DBRC . . . . . . . . . : No+ DTB records logged . . : 0 DTB buffer size . . . . : 0+ DTB records spill . . . : 0===============================================================================

DLI Analysis


DLI databasesTo display DLI databases, select the DLI Databases option (D) on the Databases path or enter fast path D.D from any menu system panel. You can see DLI database activity for all databases that are defined in the database directory (DDIR). The display is shown in the following figure.

FIGURE 97. DLI Databases Panel (D.D)

For each locally defined database (DBD), this summary display shows the number of get unique, get next, insert, replace and delete operations performed.

For counts of each call type performed for a particular database, place the cursor on the line containing the database name and press PF11.

The Database Detail panel appears as shown in Figure 98 on page 223.

DTB Records Logged

Number of dynamic transaction backout records logged.

DTB Buffer Size Size of dynamic transaction backout buffer.

DTB Records Spill Number of dynamic transaction backout record spills.

________________ ZDLDBD VTM TDOCS01 V520/C SYSG 02/03/99 11:27:03> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-DB2 B-DLI Summary C-DLI General Info D-DLI Databases> E-DLI Subpools F-DLI ECBs G-DLI Addresses H-DBCTL===============================================================================> DLI DATABASE ACTIVITY DLI DBD+ DLI Data Base Statistics+ DBD name GU GN ISRT REPL DLET+ -------- -------- -------- -------- -------- --------+ BE1CHKPT 0 0 0 0 0+ BE2ORDER 1 0 0 0 0+ BE2ORDRX 0 0 0 0 0+ BE2PARTS 0 0 0 0 0+ BE2PCUST 0 0 0 0 0===============================================================================


DLI Analysis

FIGURE 98. DLI Database Detail Panel (Accessed by Zoom)

For the selected local database, this panel displays the DBD name, the DDIR entry name, and statistics for the following types of access:

GU Get Unique.

GN Get Next.

GHU Get Hold Unique.

GNP Get Next in Parent.

ISRT Insert.

GHN Get Hold Next.

REPL Replace.

GHNP Get Hold Next in Parent.

DLET Delete.

____________ ZZDBD VTM TDOCS01 V520/C SYSA 02/03/99 13:14:02> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down ===============================================================================> DATABASE DETAIL DLI DBD=BE2ORDER+ DLI Data Base Statistics+ DBD name . . . . . . . : BE2ORDER DDIR entry . . . . . . : BE2ORDER+ GU count . . . . . . . : 1 GN count . . . . . . . : 0+ GHU count . . . . . . . : 2 GNP count . . . . . . . : 0+ ISRT count . . . . . . : 0 GHN count . . . . . . . : 16+ REPL count . . . . . . : 0 GHNP count . . . . . . : 0+ DLET count . . . . . . : 0===============================================================================

DLI Analysis


DLI subpoolsTo display DLI subpool statistics as shown in the following figure, select the DLI Subpools option (E) on the Databases path or enter fast path D.E from any panel.

FIGURE 99. DLI Subpool Statistics Panel (D.E)

This panel displays information about the ISAM/OSAM pools as defined in the DFSVSAMP dataset for local DLI files.

There is a one line display for each buffer size which includes the buffer size, the number of buffers, successful lookasides, reads, writes, and purges. There is a ratio of lookasides to reads which is lookasides as a percentage of lookasides plus reads.

The last line of the display shows the total virtual storage used by the ISAM/OSAM pools, plus all related control blocks (such as IBPOOL and ISUBPL).

____________ ZDLSUBP VTM TDOCS01 V520/C SYSA 02/03/99 13:14:02> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-DB2 B-DLI Summary C-DLI General Info D-DLI Databases> E-DLI Subpools F-DLI ECBs G-DLI Addresses H-DBCTL===============================================================================> DLI SUBPOOL STATISTICS DLI SUBPOOL+ Buffer Count of Success Buffer Buffer Buffer Lk-aside+ Size Buffers Lk-Aside Reads Writes Purges Ratio+ -------- -------- -------- -------- -------- -------- --------+ 4096 4 374 33 27 1 91.8%+ 8192 2 257 77 35 0 76.9%++ Totals 6 631 110 62 1 85.2%+ ISAM/OSAM IMS Subpools - total size = 32768===============================================================================


DLI Analysis

DLI ECBsTo display DLI interface event control blocks (ECBs), select the DLI ECBs option (F) on the Databases path or enter fast path D.F from any panel. The DLI Interface ECBs section of the panel shows the ECB status of various DLI functions. The last task requesting DLI services displays at the bottom of the panel. The DLI ECBs panel appears as shown in the following figure.

FIGURE 100. CICS/DLI Interface ECBs Panel (D.F)

This panel shows the addresses and current settings for the CICS/DLI interface event control blocks (ECBs) located in control block DLP. If any of the ECBs are not posted, a red waiting message displays on color terminals. The message is highlighted on noncolor terminals.

The last line displays the addresses of the ISB, PST, and TCA for the last task to call DLI.

________________ ZDLECB VTM TDOCS01 V520/C SYSG 02/03/99 11:27:30> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-DB2 B-DLI Summary C-DLI General Info D-DLI Databases> E-DLI Subpools F-DLI ECBs G-DLI Addresses H-DBCTL===============================================================================> CICS/DLI INTERFACE ECBs DLI ECB+ DLI Interface ECBs+ Single thread DLPSTECB : 0010DA98 ECB status . . . . . . : Posted+ PSB/DMB pool DLPISECB . : 0010DAA0 ECB status . . . . . . : Not set+ PSB scheduling DLPSBECB : 0010DB80 ECB status . . . . . . : Posted+ Free ISB DLISBECD . . . : 0010DB81 ECB status . . . . . . : Posted+ Scheduling code DLSCHECB: 0010DB82 ECB status . . . . . . : Posted+ DB quiesce DLDBDECB . . : 0010DB85 ECB status . . . . . . : Posted+ DFSDSST hold DLDSTECB . : 0010DB86 ECB status . . . . . . : Not set+ PSB pool wait DLPPSECB : 0010DBD8 ECB status . . . . . . : Posted+ DBRC SYNC DLPRCECB . . : 0010DB54 ECB status . . . . . . : Not set+ DBRC signon DLPSOECB . : 0010DB68 ECB status . . . . . . : Posted++ Last task requesting DLI service+ TCA . . . . : 003ABBE8 ISB . . . . : 00010AF0 PST . . . . : 00428050===============================================================================

DLI Analysis


DLI addressesTo display DLI interface addresses, select the DLI Addresses option (G) on the Databases path or enter fast path D.G from any panel. The DLI Interface Addresses panel appears as shown in the following figure.

FIGURE 101. CICS/DLI Interface Addresses Panel (D.G)

This panel displays the addresses of various local DLI control blocks such as the PDIR, DDIR, ISB pool, and PST pool.

________________ ZDLADDR VTM TDOCS01 V520/C SYSG 02/03/99 11:27:56> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-DB2 B-DLI Summary C-DLI General Info D-DLI Databases> E-DLI Subpools F-DLI ECBs G-DLI Addresses H-DBCTL===============================================================================> CICS/DLI INTERFACE ADDRESSES DLI ADDRESS+ DLI Interface Addresses+ Address of PDIR . . . . : 000D9958 Address of DDIR . . . . : 00078918+ Address of ISB pool . . : 00010760 Address of PST pool . . : 0042B050+ Address of DLQ . . . . : 003BC1EE Address of DLI . . . . : 8005C5B0+ Address of DLP . . . . : 0010DA60 Address of SCD . . . . : 003BD030+ Address of EDP . . . . : 80080CF0 Address of DLX . . . . : 00070488+ Address of DLR . . . . : 0006C958===============================================================================


DLI Analysis

DBCTLIf CICS is connected to DBCTL, OMEGAMON II displays the status of the connection and any transactions that have active requests pending with DBCTL. To access the DBCTL interface display, select the DBCTL option (H) on the Databases path or enter fast path D.H from any panel. When you select the Databases option (D) on the main menu, DBCTL is the initial panel on the Databases path if DBCTL (and not DLI and not DB2) is installed in this CICS region. The DBCTL panel appears as shown in Figure 102 on page 227.

FIGURE 102. CICS/DBCTL Interface Panel (D.H)

This panel displays CICS/DBCTL interface information and all transactions currently using DBCTL. For a description of fields on this panel, refer to “DBCTL” in the chapter on Resources in Volume 1 of this manual.

For task detail, place the cursor on a specific task and press PF11. Zoomable fields, including database statistics, are highlighted in white. For a description of the task detail display see “Task Detail” on page 91.

________________ ZDBCTL VTM TDOCS01 V520/C SYSG 02/03/99 11:27:56> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-DB2 B-DLI Summary C-DLI General Info D-DLI Databases> E-DLI Subpools F-DLI ECBs G-DLI Addresses H-DBCTL===============================================================================> CICS/DBCTL INTERFACE DLI DBCTL+ CICS/DBCTL General Information + Startup table suffix . : DK DBCTL interface status : Ready+ Session number . . . . : 32 Control Txn area address: 0003EC50+ DBCTL identification . : DBCT DBCTL job name . . . . : DBCTL001+ DBCTL ASID . . . . . . : 42 DBCTL JES job number . : STC00911+ Minimum threads . . . . : 2 Maximum threads . . . . : 8+ Active Thread RmCalls. : 1 Successful PSB Schedules: 24+ DBCTL CMD recognition ID: % Disconnect Type . . . . : Immediat+ The following fields relate to the previous DBCTL session+ Minimum thread hits . . : 0 Maximum thread hits . . : 0+ HWM for threads . . . . : 0 Time at thread max . . : 0:00:00 + DBCTL Threads Summary+ Tran Task Request Suspend Segment MAX Key ADDR of+ ID Number Type in DBCTL Length Length PCB list+ -------- -------- -------- -------- -------- -------- --------+ ABCD 2365 DSB INIT No 340 10 00050CE0+ ASMT 1472 DLI RQST Yes 440 25 000684C0+ PINQ 2392 DSB SCHD No 86 8 00077400===============================================================================

DLI Analysis


CICS System Analysis 229

CICS System Analysis

Chapter OverviewCICS is a dynamic environment. Control tables and settings can be modified dynamically. In maintaining the availability of CICS, it is helpful to view current control block entries and settings. In the CICS path, OMEGAMON II displays control blocks, control tables, facilities, exits, parameter settings, and status indicators that are internal to the region.

Looking at the contents of internal control blocks and the usage of exits and internal facilities can help you to isolate system and application problems in CICS. For example, exits or control tables entries may be incorrectly defined, or there may be an excessive accumulation of: tasks on chains, temporary storage or transient data queues, dumps, or traces.

Chapter ContentsAccessing the CICS Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231

Accessing control tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232Automatic Initiate Descriptors (AIDs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233AID Kill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235Common System Area (CSA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236Destination Control Table (DCT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238DLI Data Management Block Directory (DDIR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242DLI Program Specification Block Directory (PDIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244CICS Dumps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246CICS Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247Extended Recovery Facility (XRF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249File Control Table (FCT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250Interval Control Elements (ICEs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255ICE Kill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257Journal Control Table (JCT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258Processing Program Table (PPT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261System Initialization Table (SIT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264Terminal Control Table Prefix (TCTFX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266Temporary Storage Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267Temporary Storage Queues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269Terminal Control Table (TCT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271CICS Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276

13


Program Control Table (PCT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278Transient Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281CICS Shutdown Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284


Accessing the CICS Path

Accessing the CICS PathTo access the CICS internals displays, select the CICS option (C) on the Main Menu or enter fast path C. from any panel. This option starts you on the CICS path. The initial panel on the CICS path is a 2-column menu of CICS options in alphabetical order, as shown in the following figure.

FIGURE 103. CICS Options Menu Panel (C.)

When you select an option from this menu, the display includes a horizontal menu of CICS path options across the upper portion of the panel. The display of the control block or facility appears in the lower portion of the panel. Subsequent displays on the CICS path include the horizontal menu.

All of the panels on this path are display only. You can view relevant control blocks and control tables. But, you must make any updates or corrections through the usual IBM-provided facilities, such as resource definition online (RDO).

Several levels of detail are often available and can be accessed by zooming.

The CICS path also includes two Storage Options: PAM DSA (option O) and PAM EDSA (option P). These options take you directly to a map of the storage allocated to DSA or EDSA in the Storage path. From there you can choose other storage-related options from the horizontal storage menu.

In addition, the CICS path includes the DLI option (E) which takes you directly to the Databases path.

________________ ZCORE VTM $CICSTOR V520./I SYSA 02/03/99 12:> PF1 Help PF3 Back PF4 Main Menu > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR> H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill> O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS> V-TCT W-Trace X-PCT Y-TD=======================================================================> CICS INTERNAL CONTROL BLOCKS AND TABLES > A AIDs ... Automatic initiators N JCT .... Journal control> B AID Kill AIDs kill mechanism O PAM DSA DSA page allocat> C CSA .... Common system area P PAM EDSA EDSA page alloca> D DCT .... Destination control table Q PPT .... Processing progr> E DLI .... IMS/DLI overview R SIT .... System initializ> F DDIR ... IMS/DLI DMB directory S TCTFX .. TCT Prefix> G PDIR ... IMS/DLI PSB directory T TS ..... Temporary storag> H Dumps... CICS dump summary U TSQ .... Temporary storag> I Exits... CICS exits summary V TCT .... Terminal control> J XRF .... Extended recovery facility W Trace .. Trace control ov> K FCT .... File control table X PCT .... Program control> L ICEs ... Interval control elements Y TD ..... Transient data> M ICE Kill ICEs kill mechanism Z Return . Return to main m=======================================================================

Accessing the CICS Path


Accessing control tablesCICS control tables define all resources in CICS. CICS uses these control tables to find out the attributes of its resources and also to dynamically track their usage. Incorrect table entries may cause problems. When an application problem arises, it is helpful to check the relevant control table entries.

You define control table entries through macros or Resource Definition Online (RDO). Table entries include the parameters you specify, the contents of RDO profiles, and CICS indicators.

You access the contents of all the control tables in the same way as follows:

1. First, you see a list of attribute categories relevant to the specific table.2. When you zoom (PF11) on a category, one of which is All Table Entries, you then see a

summary of table entries that fit the category.3. The summary panel displays key elements for each entry.4. You can zoom (PF11) on a specific entry to display it in full detail.


Automatic Initiate Descriptors (AIDs)

Automatic Initiate Descriptors (AIDs)An AID represents a request to CICS to start a task where CICS is unable to do so because a resource such as a terminal or system link is not available. A common reason for an accumulation of AIDs is a printer, terminal, or remote connection out of service.

To view a summary display of all AIDs in your CICS region, select the AIDs option (A) on the CICS path or enter fast path C.A from any panel. A summary appears as shown in the following figure.

FIGURE 104. Automatic Initiate Descriptors (AIDs) Panel (C.A)

This panel shows:

Tran ID Transaction identifier of the task the AID will start.

Term ID Terminal device on which the task will start.

Term Status Terminal status of the device on which the task will start. For example, ACQ INS means that the device is acquired and in service.

Owning System Which CICS system owns the particular device.

AID Type Current AID type which may be:

BMS Sch Scheduled by Basic Mapping Support (BMS).

ICP Sch Interval Control Put data request.

IC Init Interval Control Initiate.

TDP Sch Scheduled by Transient Data.

ISC Sch Scheduled by Intersystem Communication

Rem Del Remote Delete request.

________________ ZAIDS VTM CICSP01 V520./I SYSA 02/03/99 16:28:28 > PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR > H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT > O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ > V-TCT W-Trace X-PCT Y-TD ================================================================================ > AUTOMATIC INITIATE DESCRIPTORS AIDS + Number of AIDS selected: 6 Skipped: 0 + Tran Term Term Owning AID Request AID + ID ID Status System Type ID Address + -------- -------- -------- -------- -------- -------- -------- + CRSR MIRS Ins TDOCSIRS IC Init None 00121090 + CRSR MIRX Ins TDOCSIRX IC Init None 001210E0 + CRSR SYS2 Ins TDOCS02 IC Init None 00121130 + CRSR SYS3 Ins TDOCS03 IC Init None 00121180 + CRSR SYS4 Ins TDOCS04 IC Init None 001211D0 + CRSR SY13 Ins TDOCS13 IC Init None 00121220 =================================================================================

Automatic Initiate Descriptors (AIDs)


You can limit the AID summary display to AIDs associated with a terminal or transaction by entering TERM=cccc or TRAN=cccc after the AIDS statement where cccc is a specific or generic terminal or transaction ID. Use * to specify a generic ID. For example,

AIDS TRAN=AB*

displays the AIDs associated with transactions starting with AB.

To display detailed information about an AID, place the cursor on the line describing the AID and press PF11.

A detail display appears as shown in Figure 105 on page 234.

FIGURE 105. AID Detail Panel (Accessed by Zoom)

The AID detail display helps you to analyze the target terminal so that you can find out why the AID is delayed. For more information on the target terminal, place the cursor on the Terminal ID field and press PF11.

For a hexadecimal and character equivalent of the AID, place the cursor on AID address and press PF11.

Request ID Request identifier associated with this AID.

AID Address Location of the AID in memory.

________________ ZZAID VTM CICSP01 V520./I SYSA 02/03/99 16:28:43 > PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ================================================================================== > AID DETAIL AIDS ADDRESS=00121090 + General Information + Transaction ID . . . . : CRSR AID address . . . . . . : 00121090 + Request ID . . . . . . : None Owning sysid . . . . . : TDOCSIRS + AID type . . . . . . . : IC Init Userid . . . . . . . . : None + AID status . . . . . . : Waiting for target system + + Terminal Information + Terminal ID. . . . . . : MIRS TCTTE address . . . . . : 0013B1B0 + Terminal type. . . . . : System Terminal model . . . . : None + Session status . . . . : n/a VTAM netname . . . . . : TDOCSIRS + Service status . . . . : Ins Session create status . : n/a ================================================================================


AID Kill

AID KillYou can terminate either a single AID or a group of AIDs. To identify AIDs to kill, select the AID Kill option (B) on the CICS path or enter fast path C.B from any panel. A summary of all AIDs appears that is the same as the AIDs summary in Figure 104 on page 233.

To select a specific AID for termination, scroll through the AIDs Kill Summary, place the cursor on the AID, and press PF11. To kill all AIDs associated with a terminal or transaction, enter TERM=cccc or TRAN=cccc after the AIDK statement, followed by KILL. cccc indicates a specific or generic terminal or transaction ID. Use * to specify a generic ID. For example,

AIDK TRAN=AB* KILL

kills the AIDs associated with transactions starting with AB.

When you request AIDs termination, a prompt panel appears for confirmation. Enter YES to continue with termination or press PF3 to cancel the request and return to the summary display.

You can use the AIDK limit keyword to limit the number of AIDS killed when you use the terminal or transaction ID qualifier. For example, the command

AIDK TERM=M444 KILL LIMIT=10

will eliminate the 10 first aids found for terminal M444.

Common System Area (CSA)


Common System Area (CSA)The CSA is a common area in CICS that contains status indicators and controls CICS activity. The CSA display presents selected fields from the CSA in four categories: general, counts and limits, addresses, and status. Status information highlights certain exceptional conditions such as short-on-storage (SOS) or MAXTASKS.

To display the CSA as shown in Figure 106 on page 236, select the CSA option (C) on the CICS path or enter fast path C.C from any panel.

You can enter CMXT or DUMP after CSA to display Classes or the dump.

FIGURE 106. Common System Area (CSA) Panel (C.C)

________________ ZCSA VTM CICSP01 V520./I SYSA 02/03/99 16:29:22 > PF1 Help PF3 Back PF4 Main Menu PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR > H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT > O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ > V-TCT W-Trace X-PCT Y-TD ============================================================================== > COMMON SYSTEM AREA CSA + General Information + CSA address . . . . . . : 003F6700 CICS time of day clock : 9:54:08 + MVS release . . . . . . : 4.3.0 CICS release . . . . . : 3.3.0 + Start-up date . . . . . : 11/18/93 Start-up time . . . . . : 7:42:46 + Partition lower bound . : 00000000 Partition upper bound . : 7FFFFFFF + + Counts and Limits + Maximum tasks . . . . . : 32 Times at maximum tasks. : 0 + Current task counter. . : 8 Max tasks at one time . : 17 + Total tasks . . . . . . : 26 Application interrupts. : n/a + Active maximum tasks. . : 10 Peak active tasks . . . : 3 + Classes 1-10 max tasks. : (4,4,4,4,4,4,4,4,4,4) + + Addresses + Current TCA . . . . . . : 084B0000 CWA . . . . . . . . . . : 0023A000 + DCT . . . . . . . . . . : 08475CE8 File control . . . . . : n/a + ICE chain . . . . . . . : 084B9030 Interval control . . . : 88D79634 + JCT . . . . . . . . . . : 000406A0 Optional features list : 0003BFB0 + Program control . . . . : 88DC9DBC SIT . . . . . . . . . . : 88410960 + SRT . . . . . . . . . . : 88476470 Static storage list . . : 08489000 + Task control . . . . . : 88D850C8 TCT prefix . . . . . . : 00046D90 + Terminal control . . . : 00047378 TST . . . . . . . . . . : 00000000 + TS first unit table . . : n/a XLT . . . . . . . . . . : 00000000 ================================================================================== CSA CMXT + Class Class Times at Current Peak Queueing Current + Name Limit Limit Tasks Tasks Limit Queued + -------- -------- -------- -------- -------- -------- -------- + CLASS01 4 0 0 0 0 0 + CLASS02 4 0 0 0 0 0 + CLASS03 4 0 0 0 0 0 + CLASS04 4 0 0 0 0 0 + CLASS05 4 0 0 0 0 0 ==================================================================================


Common System Area (CSA)

Note: In CICS/ESA Version 4, the Classes 1-10 max tasks field does not appear under the Counts and units section of this panel.

There are several fields for which additional detail is available. To select a field for more detail, place the cursor on the field and press PF11. These fields include: CSA address, Classes max tasks, ICE chain, SIT, and TCT prefix. Zoomable fields are highlighted in white.

Destination Control Table (DCT)


Destination Control Table (DCT)The DCT contains entries for extrapartition and intrapartition transient data queues (Dest IDs). Extrapartition queues provide access to sequential files outside of the CICS region. Intrapartition queues provide access to sequential queues within the CICS region and are often used with Automatic Transaction Initiation (ATI) to trigger transactions on another terminal.

To display DCT entry attributes as shown in the following figure, select the DCT option (D) on the CICS path or enter fast path C.D from any panel.

FIGURE 107. Destination Control Table Attributes Panel (C.D)

To select destinations with a specific attribute, place the cursor on the line describing the attribute and press PF11. To select a specific destination, you can enter ID=queuename after DCT.

TABL DCT,ID=DFH*

For a DCT entry in dump format, enter DUMP after queuename.

TABL DCT,ID=queuename DUMP

To select destinations with several attributes, enter SEL= followed by a list of attributes. The syntax is:

TABL DCT,SEL=(attr1,attr2,.....attrn)

________________ ZDCT VTM CICSP01 V520./I SYSA 02/03/99 16:29:32 > PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR > H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT > O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ > V-TCT W-Trace X-PCT Y-TD =============================================================================== > DESTINATION CONTROL TABLE TABL DCT + + Closed . . . . . . . . : CLO + Disabled . . . . . . . : DIS + Enabled. . . . . . . . : ENA + Extrapartition . . . . : EXT + Indirect . . . . . . . : IND + Intrapartition . . . . : INT + Opened . . . . . . . . : OPE + Remote . . . . . . . . : REM + + All table entries. . . : * ================================================================================



You can use the wildcard character * in queuename. For example:

If you zoom on the All Table Entries field, a DCT summary panel appears as shown in the following figure.

FIGURE 108. DCT Summary Panel (Accessed by Zoom)

ID=DFH* Specifies queuenames beginning with DFH.

ID=*YZ Specifies queuenames ending with YZ.

ID=A*B* Specifies queuenames beginning with A and having a B anywhere but at the end of the name.

________________ ZZTABLA VTM $CICSTOR V520./I SYSA 02/03/99 9:26:37> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ===============================================================================> ALL TABLE ENTRIES TABL DCT ID=’*’+ Entries selected: 24 Skipped: 0+ Dest Dest Dest Indirect ATI ATI Trigger+ ID Type Status Queue Facility Tran ID Level+ -------- -------- -------- -------- -------- -------- --------+ CADL Extra Ena Ope n/a n/a n/a n/a+ CDBC Indirect n/a CSSL n/a n/a n/a+ CDUL Indirect n/a CSSL n/a n/a n/a+ CPLD Extra Ena Ope n/a n/a n/a n/a+ CPLI Extra Ena Ope n/a n/a n/a n/a+ CRDI Indirect n/a CSSL n/a n/a n/a+ CSCS Indirect n/a CADL n/a n/a n/a+ CSDL Indirect n/a CADL n/a n/a n/a+ CSFL Indirect n/a CSSL n/a n/a n/a+ CSML Indirect n/a CSSL n/a n/a n/a+ CSMT Indirect n/a CSSL n/a n/a n/a+ CSSL Extra Ena Ope n/a n/a n/a n/a+ CSSM Extra Ena Ope n/a n/a n/a n/a+ CSSN Extra Ena Ope n/a n/a n/a n/a+ CSTL Indirect n/a CSSL n/a n/a n/a+ CXRF Extra Ena Clo n/a n/a n/a n/a===============================================================================



For each destination ID that fits the selected category, this panel shows:

To display detailed information on a particular Dest ID (queue name), place the cursor on that line and press PF11.

The detailed information displayed depends on the type of queue. For an extrapartition queue entry, the panel appears as shown in the following figure.

FIGURE 109. Extrapartition DCT Entry Panel (Accessed by Zoom)

For a detailed indirect intrapartition queue entry, the panel appears as shown in the following figure.

Dest ID Transient data queue name.

Dest Type Whether this is an intrapartition, extrapartition, indirect, or remote queue.

Dest Status Whether this destination is OPEN, ENABLED, OPIP (Open in Progress), or CLIP (Close in Progress).

Indirect Queue Final destination name for indirect queues.

ATI Facility Terminal or destination ID for automatic transaction initiation.

ATI Tran ID Transaction ID for automatic transaction initiation.

Trigger Level Transient data trigger level for automatic transaction initiation.

________________ ZZTABLE VTM $CICSTOR V520./I SYSA 02/03/99 12:21:39> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ================================================================================> SELECTED TABLE ENTRY TABL DCT ID=’CPLI’+ General Information+ Destination ID . . . . : CPLI DCTE address . . . . . : 0004DCC4+ Destination status . . : Ena Ope Facility associated . . : None+ Destination type . . . : Extra Resource security level : 0+ Use count . . . . . . . : 0++ Extrapartition Information+ Associated SDSCI . . . : PLIMSG Open option . . . . . . : Initial+ Address of owning TCA . : n/a Error conditions . . . : None++ Dataset Information+ Record format . . . . . : VB DDname . . . . . . . . : PLIMSG+ Record length . . . . . : 133 Dataset type . . . . . : Output+ Block size . . . . . . : 6144 DCB address . . . . . . : 0004DFC0+ Dataset name . . . . . : PROD.CIMGNN.$CICSTOR.PLIMSG===============================================================================



FIGURE 110. Indirect Intrapartition DCT Entry Panel (Accessed by Zoom)

________________ ZZTABLE VTM $CICSTOR V520./I SYSA 02/03/99 12:23:02> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ================================================================================> SELECTED TABLE ENTRY TABL DCT ID=’CSDL’+ General Information+ Destination ID . . . . : CSDL DCTE address . . . . . : 0004DE8C+ Destination status . . : n/a Facility associated . . : None+ Destination type . . . : Indirect Resource security level : 0+ Use count . . . . . . . : 42++ Indirect Information+ Indirect queue name . . : CADL Indirect queue type . . : Extra++ Extrapartition Information+ Associated SDSCI . . . : RDOMSG Open option . . . . . . : Initial+ Address of owning TCA . : n/a Error conditions . . . : None++ Dataset Information+ Record format . . . . . : V DDname . . . . . . . . : RDOMSG+ Record length . . . . . : 133 Dataset type . . . . . : Output+ Block size . . . . . . : 6144 DCB address . . . . . . : 0004E240+ Dataset name . . . . . : PROD.CIMGNN.$CICSTOR.RDOMSG================================================================================

DLI Data Management Block Directory (DDIR)


DLI Data Management Block Directory (DDIR)The DDIR contains entries describing each DLI database in the CICS region.

To display DDIR entry attributes as shown in Figure 111 on page 242, select the DDIR option (F) on the CICS path or enter fast path C.F from any panel.

FIGURE 111. DLI DMB Directory Attributes Panel (C.F)

To select DMBs with a specific attribute, place the cursor on the line describing the attribute and press PF11. To select a specific DMB, you can enter ID=dmbname after DDIR as in the following example.

TABL DDIR,ID=BASE*

For a DMB entry in dump format, enter DUMP after dmbname:

TABL DDIR,ID=dmbname DUMP

To select DMBs with several attributes, enter SEL= followed by a list of attributes. The syntax is:

TABL DDIR,SEL=(attr1,attr2,.....attrn)

You can use the wildcard character * in dmbname. For example:

If you zoom on the All Table Entries field, a DDIR summary appears as shown in the following figure.

ID=DFH* Specifies DMBs beginning with DFH.

ID=*YZ Specifies DMBs ending with YZ.

ID=A*B* Specifies DMBs beginning with A and having a B anywhere but at the end of the name.

________________ ZDDIR VTM CICSP01 V520./I SYSA 02/03/99 16:30:37 > PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR > H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT > O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ > V-TCT W-Trace X-PCT Y-TD ================================================================================= > DLI DMB DIRECTORY TABL DDIR + + Exclusive . . . . . . . : EXC + Non-startable . . . . . : NOS + Read . . . . . . . . . : REA + Readonly . . . . . . . : REO + Started . . . . . . . . : STA + Stopped . . . . . . . . : STO + Update eligible . . . . : UPD + + All table entries . . . : * =================================================================================


DLI Data Management Block Directory (DDIR)

FIGURE 112. DDIR Summary Panel (Accessed by Zoom)

For each database definition in the selected category, this panel shows:

To display detailed information on a particular DMB, place the cursor on that line and press PF11. The detailed information for a DMB includes the Database Share Level.

DMB ID Identifies the Data Management Block.

Database Status Current status of this database such as Started or Stopped.

Access Level Access level of this DMB: Read, Read Only, Update, and Exclude.

DMB Number Number of the current DMB.

Core Address Location of this DMB in storage.

DMB Size Size of this DMB.

Active PSTs Number of currently active PSTs.

________________ ZZTABLA VTM TDOCS01 V520./C SYSG 02/03/99 11:36:00> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom =================================================================================> ALL TABLE ENTRIES TABL DDIR ID=’*’+ Entries selected: 5 Skipped: 0+ DMB Database Access DMB Core DMB Active+ ID Status Level Number Address Size PSTs+ -------- -------- -------- -------- -------- -------- --------+ BE1CHKPT Started Excluse 1 00000000 61 0+ BE2ORDER Started Excluse 2 001A0194 87 0+ BE2ORDRX Started Excluse 3 001A0794 47 0+ BE2PARTS Started Excluse 4 001A0454 103 0+ BE2PCUST Started Excluse 5 001A0004 49 0=================================================================================

DLI Program Specification Block Directory (PDIR)


DLI Program Specification Block Directory (PDIR)The PDIR is a table defining PSBs which DLI application programs use to access DLI databases.

To display PDIR entry attributes as shown in the following figure, select the PDIR option (G) on the CICS path or enter fast path C.G from any panel.

FIGURE 113. DLI PSB Directory Attributes Panel (C.G)

To select PSBs with a specific attribute, place the cursor on the line describing the attribute and press PF11. To select a specific PSB, enter ID=psbname after PDIR as in the following example.

TABL PDIR,ID=PC2*

For a PDIR entry in dump format, enter DUMP after psbname.

TABL PDIR,ID=psbname DUMP

To select PSBs with several attributes, enter SEL= followed by the list of attributes. The syntax is:

TABL PDIR,SEL=(attr1,attr2,.....attrn)

You can use the wildcard character * in psbname. For example:

If you zoom on the All Table Entries field, a PDIR summary appears as shown in the following figure.

ID=DFH* Specifies PSBs beginning with DFH.

ID=*YZ Specifies PSBs ending with YZ.

ID=A*B* Specifies PSBs beginning with A and having a B anywhere but at the end of the name.

________________ ZPDIR VTM CICSP01 V520./I SYSA 02/03/99 16:30:50 > PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR > H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT > O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ > V-TCT W-Trace X-PCT Y-TD ================================================================================ > DLI PSB DIRECTORY TABL PDIR + + Remote . . . . . . . . : REM + Scheduled . . . . . . . : SCH + Unscheduleable. . . . . : UNS + + All table entries . . . : * ================================================================================


DLI Program Specification Block Directory (PDIR)

FIGURE 114. PDIR Summary Display (Accessed by Zoom)

For each PSB entry in the selected category, this panel shows:

To display detailed information on a particular PSB, place the cursor on that line and press PF11.

The detailed information for a PSB includes whether the PSB is locked.

PSB ID Identifies the Program Specification Block.

Schedule Status Whether this PSB is scheduled.

Readonly PSB Whether this is a read-only PSB.

Schedule Origin Origin of the PSB schedule such as: CICS, Batchtype 2, and Batchtype 3.

Core Address Location of this PSB in storage.

PSB Size Size of the PSB in bytes.

Intent List Address of the intent list for this PSB.

________________ ZZTABLA VTM TDOCS01 V520./C SYSG 02/03/99 11:38:26> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom =================================================================================> ALL TABLE ENTRIES TABL PDIR ID=’*’+ Entries selected: 4 Skipped: 0+ PSB Schedule Readonly Schedule Core PSB Intent+ ID Status PSB Origin Address Size List+ -------- -------- -------- -------- -------- -------- --------+ PC2CCNAM No No Batch T3 00000000 1760 00000000+ PC2COINQ No No Batch T3 00000000 3136 00000000+ PC2CPINV No No Batch T3 00000000 1984 00000000+ PC2CPPUR No No Batch T3 00000000 2864 00000000=================================================================================

CICS Dumps


CICS DumpsTo view general information and dump table entries for the CICS dump component, which manages system and transaction dumps, select the Dumps option (H) on the CICS path or enter fast path C.H from any panel. The Dump Component panel appears as shown in the following figure.

FIGURE 115. Dump Component Panel (C.H)

For all CICS releases, this panel shows general information on the status of the dump datasets, the number of dumps taken, the suppression status, and the number of dumps suppressed.

For CICS/ESA regions, this panel includes a summary of the dumpcodes that are in the CICS dump code table. CICS maintains a list of 8-character system dumpcodes and 4-character user dumpcodes that allows attributes to be associated with a dump request. These attributes include whether the dump request will provide a system and/or transaction dump and the maximum number of dumps to be taken for that dumpcode.

To view detailed file information on the dump dataset, place the cursor on the dataset name and press PF11.

________________ ZDUMP VTM CICSP01 V520./I SYSA 02/03/99 16:31:00 > PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR > H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT > O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ > V-TCT W-Trace X-PCT Y-TD =============================================================================== > DUMP COMPONENT DUMP + General Information + Dump taking place . . . : No Anchor address . . . . : 04772440 + Total dumps taken . . . : 3 System dump suppression : Off + System dumps taken . . : 1 System dumps suppressed : 88 + Transaction dumps taken : 2 Transaction dumps suppr : 55 + Dump dataset status . . : Closed Switch status . . . . . : Manual + Dumpid of last dump . . : 6/0007 Current dataset ddname : DFHDMPB + Initial dataset suffix : X + Current dataset dsname : TDCICS1.TOC.TDOCS22.DFHDMPB + + Number of dump table entries selected: 3 Skipped: 0 + Dump Maximum Type of System System Tran Tran + Code Allowed Dumpcode Taken Suppr Taken Suppr + -------- -------- -------- -------- -------- -------- -------- + MT0001 None System 1 0 0 0 + AFCY None System 0 3 2 0 + ATNI None Tran 0 3 0 0


CICS Exits

CICS ExitsExits provide installation or product specific enhancements to CICS. Third party products, including OMEGAMON II, use CICS exits as part of their processing. To display the usage of these exits, select the Exits option (I) on the CICS path or enter fast path C.I from any panel. The Exits panel appears as shown in the following figure.

FIGURE 116. Exits Panel (C.I)

This display contains two segments: Global Exit Programs and Exit Program Blocks.

The first segment shows which Global User Exits (GLUEs) have been enabled:

Exit Name CICS defined exit point. For more information on an exit point, refer to the IBM CICS Customization Guide for the appropriate release of your CICS system.

Entry Name Name used when the exit was enabled.

Program Name CICS program where the exit code resides.

Global Address Address of the exit’s work area, if requested at exit enablement. If no area is requested, the value is 0.

Global Length Size of the exit’s work area.

________________ ZEXIT VTM CICSP01 V520./I SYSA 02/03/99 16:31:11 > PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR > H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT > O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ > V-TCT W-Trace X-PCT Y-TD =============================================================================== > EXITS > Global Exit Programs: EXIT + Exit Entry Program Global Global Exit EPB + Name Name Name Address Length Status Address + -------- -------- -------- -------- -------- -------- ------- + XMNOUT GLUEEXIT KOC0ME00 0006DD64 392 Ena Act 060D30C0 + XDLIPRE GLUEEXIT KOC0ME00 0006DD64 392 Ena Act 060D30C0 + XDLIPOST GLUEEXIT KOC0ME00 0006DD64 392 Ena Act 060D30C0 + XEIOUT GLUEEXIT KOC0ME00 0006DD64 392 Ena Act 060D30C0 > Exit Program Blocks: EXIT EPBS + EPB Entry Global Global Tsk Area Exit Interest + Address Name Address Length Length Status Profile + -------- -------- -------- -------- -------- -------- -------- + 060D3030 DLI 00000000 0 4 Ena Act A + 060D3078 KOC0ME00 0006DD64 80 1096 Ena Act T,C,A + 060D30C0 GLUEEXIT 0006DD64 392 0 Ena Act A

CICS Exits


The second segment shows which exit programs exist for either GLUEs or Task Related User Exits (TRUEs):

Exit Status Status of CICS at exit which may be Act (Active), Stop (Stopped but defined), Ena (enabled but not active), or Dis (disabled).

EPB Address Address of the Exit Program Block.

EPB Address Address of the Exit Program Block containing the information in this display.

Entry Name Name used when the exit was enabled.

Global Address Address of the exit’s work area, if requested at exit enablement. If no area is requested, the value is 0.

Global Length For GLUEs, the size of the global work area.

Tsk Area Length For TRUEs, the size of the task work area. For GLUEs this value is 0.

Exit Status Status of GLUEs and TRUEs at exit which may be: Act (Active), Stop (Stopped but defined), Ena (enabled but not active), or Dis (disabled).

Interest Profile Interest profile schedule word for TRUEs, which defines the allowed calls to TRUEs. For GLUEs, this field is not applicable (n/a). The following characters indicate how the TRUE is invoked:

A By application calls using the DFHRMCAL macro.

T At the start and end of every task.

C During CICS termination.

S By CICS sync point processing.


Extended Recovery Facility (XRF)

Extended Recovery Facility (XRF)XRF provides recovery of a region by having a fully defined alternate region readily available to replace the operation of the failed region.

To display the health of your active and alternate CICS systems configured for XRF, select the XRF option (J) on the CICS path or enter fast path C.J from any panel. The Extended Recovery Facility Status panel appears as shown in the following figure.

FIGURE 117. Extended Recovery Facility Status Panel (C.J)

The heartbeat interval represents the rate in seconds at which the CICS Availability Manager (CAVM) writes records to the surveillance file. The last surveillance times for the CAVM and CICS indicate when the respective components initiated examination of surveillance data.

VTAM error data is collected as long as no XXRSTAT exit specifying a nonzero return code is active.

For information about the XRF-related SIT operands TAKEOVER, ADI, and JESDI, select the SIT option (R) on the CICS path (see “System Initialization Table (SIT)” on page 264).

________________ ZXRF VTM CICSP01 V520./I SYSA 02/03/99 16:31:20 > PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR > H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT > O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ > V-TCT W-Trace X-PCT Y-TD ============================================================================= > EXTENDED RECOVERY FACILITY STATUS XRF + Extended Recovery Facility Status + Generic Applid . . . . : CICSPROD Heartbeat interval . . : 3 + Last surveillance (CAVM): 16:30:13 Primary delay interval : 15 + Last surveillance (CICS): 16:31:05 + Control file DSN . . . : HILEV.CICS.V311.DFHXRCTL + Message file DSN . . . : HILEV.CICS.V311.DFHXRMSG + + XRF System information Active CICS region Alternate CICS region + ------------------------ ------------------ --------------------- + CAVM status . . . . . . : Signed On Normal Signon + CICS status . . . . . . : Signed On Normal Signon + Specific APPLID . . . . : CICSPROD CICSPRDX + SMF ID . . . . . . . . : SYSA SYSA + Jobname . . . . . . . . : CICSPROD CICSPRDX + JES job ID . . . . . . : STC01234 STC23456 + Start date . . . . . . : 06/06/61 06/06/61 + Start time . . . . . . : 00:01:30 00:01:35 + + VTAM Error Data + Total errors detected by XXRSTAT global exit = 0

===============================================================================

File Control Table (FCT)


File Control Table (FCT)VSAM files, BDAM files, and datatables that are accessed in the CICS region are defined in the FCT. Remote files include a SYSID indicator for function shipping.

Applications access files by filename. The remaining file attributes such as dsname, type, disposition, LSR pool, status, and strings are defined in the FCT.

To display FCT entry attributes, select the FCT option (K) on the CICS path or enter fast path C.K from any panel.

A list of FCT entry attribute categories appears as shown in the following figure.

FIGURE 118. File Control Table Attributes Panel (C.K)

To select files with a specific attribute, place the cursor on the line describing the attribute and press PF11. To select a specific file, enter ID=filename after FCT.

TABL FCT,ID=DFH*

For an FCT entry in dump format, enter DUMP after filename.

TABL FCT,ID=filename DUMP

To select files with several attributes, enter SEL= followed by a list of attributes. The syntax is:

TABL FCT,SEL=(attr1,attr2,.....attrn)

To list all datatables, use:

TABL FCT,SEL=DTB

From there, you can zoom to detail information about a specific data table.

________________ ZFCT VTM CICSP01 V520./I SYSA 02/03/99 16:31:30 > PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR > H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT > O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ > V-TCT W-Trace X-PCT Y-TD =============================================================================== > FILE CONTROL TABLE TABL FCT + + Closed . . . . . . . . : CLO + Disabled . . . . . . . : DIS + Data Table . . . . . . : DTB + Enabled. . . . . . . . : ENA + LSR . . . . . . . . . : LSR + NSR. . . . . . . . . . : NSR + Opened . . . . . . . . : OPE + Remote . . . . . . . . : REM + Unenabled. . . . . . . : UNE + Active strings . . . . : USE + + All table entries. . . : * ===============================================================================



You can use the wildcard character * in filename. For example:

If you zoom on the All Table Entries field, an FCT summary appears as shown in the following figure.

FIGURE 119. FCT Summary Panel (Accessed by Zoom)

For each file in the selected category, this panel shows:

ID=DFH* Specifies filenames beginning with DFH.

ID=*YZ Specifies filenames ending with YZ.

ID=A*B* Specifies filenames beginning with A and having a B anywhere but at the end of the name.

File ID Identifies the file in the FCT.

File Access Access method such as: VSAM, BDAM, or OSAM.

File Status Whether the file is enabled, disabled, open, or closed.

Data Format How the file was formatted, such as FB (Fixed Blocked) or VB (Variable Blocked).

Share Control Local Shared Resource pool information.

________________ ZZTABLA VTM $CICSTOR V520./I SYSA 02/03/99 9:31:15> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ================================================================================> ALL TABLE ENTRIES TABL FCT ID=’*’+ Entries selected: 99 Skipped: 0+ File File File Data Share Active Remote+ ID Access Status Format Control Strings System+ -------- -------- -------- -------- -------- -------- ---------+ APFH120 VSAM Ena Ope FB Lsrpool1 0 n/a+ APFL905 VSAM Ena Ope VB NSR 0 n/a+ APFM100 VSAM Ena Ope VB Lsrpool1 0 n/a+ APFM200 VSAM Ena Ope FB Lsrpool1 0 n/a+ CCFM100 VSAM Ena Ope VB Lsrpool1 0 n/a+ CCFM200 VSAM Ena Ope VB Lsrpool1 0 n/a+ CM827 VSAM Ena Ope FB Lsrpool1 0 n/a+ DFHCSD VSAM Une Clo VB Lsrpool7 0 n/a+ DMCUST VSAM Ena Ope FB Lsrpool1 0 n/a+ DMDCF VSAM Ena Ope FB Lsrpool1 0 n/a+ DMINV VSAM Ena Ope FB Lsrpool1 0 n/a+ FCDEMOG VSAM Ena Clo FB Lsrpool1 0 n/a+ FCDEMOT VSAM Ena Clo FB Lsrpool1 0 n/a+ FCFMARF VSAM Ena Clo FB Lsrpool1 0 n/a+ GLFMBUD VSAM Ena Ope VB Lsrpool1 0 n/a+ GLFMORG VSAM Ena Ope VB Lsrpool1 0 n/a+ GLFMRCF VSAM Ena Ope VB Lsrpool1 0 n/a



If you have a large number of filenames at your site, some of the file summary displays may exceed your OMEGAMON II LROWS (logical rows) limit. To scroll down through a long files listing, enter a character immediately preceding the TABL FCT statement. This character specifies the number of display lines to skip. It may be 1–9 or A–Z, referring to 1–9 or 10–36 lines on the display to skip.

To display detailed information on a particular file, place the cursor on that line and press PF11.

The detailed information displayed depends on whether the file is VSAM, BDAM, remote, or a datatable. A VSAM entry appears as shown in the following figure.

FIGURE 120. FCT Entry Panel for VSAM File (Accessed by Zoom)

A BDAM entry appears as shown in the following figure.

Active Strings Number of active strings.

Remote System System ID where remote file resides.

________________ ZZTABLE VTM $CICSTOR V520./I SYSA 02/03/99 9:32:01> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ================================================================================> SELECTED TABLE ENTRY TABL FCT ID=’CCFM200’+ General Information+ File ID . . . . . . . . : CCFM200 AFCTE address . . . . . : 00197180+ FCTE address . . . . . : 053BA5B0 File status . . . . . . : Ena Ope+ Time file opened . . . : 06:00:43 Access method . . . . . : VSAM+ Resource security level : 0+ File format . . . . . . : KSDS Disposition . . . . . . : Shr+ Record format . . . . . : VB Share control . . . . . : Lsrpool1+ Record length . . . . . : 400 Key length . . . . . . : 48+ Block size . . . . . . : n/a Relative key position . : 0+ Number of data buffers : 2 Number of strings . . . : 3+ Number of index buffers : 2 Active string count . . : 0+ Service requests . . . : (Add,Browse,Delete,Read,Update)++ Journal/Log Options+ Journal ID . . . . . . : None Logging . . . . . . . . : No++ File Statistics+ Number of adds . . . . : 9 Number of browses . . . : 9+ Number of deletes . . . : 0 Number of reads . . . . : 108+ Number of reads (Update): 2 Number of updates . . . : 2+ Buffer waits (Current) : 0 String waits (Current) : 0+ Buffer waits (HWM) . . : 0 String waits (HWM) . . : 0+ Buffer waits (Total) . : 0 String waits (Total) . : 0++ Dataset Information+ Dataset named in FCT . : PROD.FINAPV.CCFM200+ Dataset allocated . . . : PROD.FINAPV.CCFM200===============================================================================



FIGURE 121. FCT Entry Panel for BDAM File (Accessed by Zoom)

Note: The time the file was opened is not available for CICS Version 2.1.2.

If an FCT entry is for a remote file, the following section appears after the Resource Security Level.

FIGURE 122. FCT Entry - Remote Information

For a remote entry, the next part of the display starts from the File Statistics section.

If the FCT entry is a datatable, the following section appears.

________________ ZZTABLE VTM TDOCS01 V520./C SYSG 02/03/99 11:32:47> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ===============================================================================> SELECTED TABLE ENTRY TABL FCT ID=’BDAMFILE’+ General Information+ File ID . . . . . . . . : BDAMFILE AFCTE address . . . . . : 00157090+ FCTE address . . . . . : 0517E030 File status . . . . . . : Dis Clo+ Time file opened . . . : n/a Access method . . . . . : BDAM+ Resource security level : 17+ File format . . . . . . : Keyed Disposition . . . . . . : Shr+ Record format . . . . . : Undef Share control . . . . . : NSR+ Record length . . . . . : 86 Key length . . . . . . : 6+ Block size . . . . . . : 178 Relative key position . : 0+ Service requests . . . : (Browse,Key,Read,Exctl)++ Journal/Log Options+ Journal ID . . . . . . : None Logging . . . . . . . . : No++ File Statistics+ Number of adds . . . . : 0 Number of browses . . . : 0+ Number of deletes . . . : n/a Number of reads . . . . : 0+ Number of reads (Update): 0 Number of updates . . . : 0++ Dataset Information+ Dataset named in FCT . : PROD.BDAM.MASTER+ Dataset allocated . . . : PROD.BDAM.MASTER================================================================================

+ Remote Information+ Remote system name. . . : CSDD Remote file name. . . . : CSDD+ Record length . . . . . : 4000 Key length. . . . . . . : 26



FIGURE 123. FCT Entry - Data Table Information

For more information about files in your CICS region, see “Files” in the chapter on Resources in volume 1 of this manual.

+ CICS Data Table Information+ Data table status . . . : Open Data table loaded . . . : Yes+ Data table recoverable : No Records have been lost : No+ Entries (current) . . . : 104 Entries (maximum) . . . : 4000+ Entries in use (current): 104 Allowed in use (max) . : 7679+ Data table size . . . . : 4000 table entries (HWM) . . : 104+ Successful reads . . . : 0 Failing reads . . . . . : 0+ Records loaded . . . . : 104 Records added . . . . . : 0+ Adds/loads rejected . . : 0 Adds failed for full . : 0+ Successful updates . . : 0 Successful deletes . . : 0


Interval Control Elements (ICEs)

Interval Control Elements (ICEs)An ICE is created whenever a time-dependent request for a CICS service is made. When the expiration time for the ICE is reached, the CICS service requested is initiated if the resources required for the service are available. If the requested service is task initiation, CICS creates an AID on ICE expiration. The AID will either initiate the task or wait until required resources become available.

To view a summary display of all ICEs in your CICS region as shown in the following figure, select the ICEs option (L) on the CICS path or enter fast path C.L from any panel.

FIGURE 124. Interval Control Elements (ICEs) Panel (C.L)

This panel shows:

To limit the ICE summary display to ICEs associated with a terminal or transaction, enter TERM=cccc or TRAN=cccc after the ICES statement where cccc is a specific or generic terminal or transaction ID. Use * to specify a generic ID. For example,

ICES TRAN=AB*

displays the ICEs associated with transactions starting with AB.

Expiry Time Time of ICE expiration.

Expiry Date Day of ICE expiration.

Tran ID Transaction ID invoked when the ICE expires.

Term ID Terminal ID indicating the terminal device on which the task will start.

ICE Type The same types as AIDS except for Rem Del. Two additional types include:

Wait ICE wait.

Post ICE post.

Request ID Request identifier associated with this ICE.

ICE Address Location of ICE in memory.

________________ ZICES VTM $CICSTOR V520./I SYSA 02/03/93 9:20:32> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR> H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT> O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ> V-TCT W-Trace X-PCT Y-TD===================================================================================> INTERVAL CONTROL ELEMENTS ICES+ Number of ICES selected: 2 Skipped: 0+ Expiry Expiry Tran Term ICE Request ICE+ Time Date ID ID Type Id Address+ -------- -------- -------- -------- -------- -------- --------+ 09:25:08 02/03/93 ACFT None IC Init DF0003EC 00152200+ 14:10:00 02/03/93 CRSQ None IC Init DF00030F 001522A0================================================================================

Interval Control Elements (ICEs)


To display detailed information about an ICE, place the cursor on the line describing the ICE and press PF11. An ICE Detail panel appears as shown in the following figure.

FIGURE 125. ICE Detail Panel (Accessed by Zoom)

For a hexadecimal and character equivalent of the ICE, place the cursor on ICE address and press PF11.

________________ ZZICE VTM $CICSTOR V520./I SYSA 02/03/93 9:21:57> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom =================================================================================> ICE DETAIL ICES ADDRESS=00152200+ General Information+ Transaction ID . . . . : ACFT ICE address . . . . . . : 00152200+ Terminal ID . . . . . . : None Destination ID . . . . : None+ Expiry time . . . . . . : 09:25:08 Expiry date . . . . . . : 02/03/93+ Request ID . . . . . . : DF0003EC Timer event area . . . : None+ ICE type . . . . . . . : IC Init Userid . . . . . . . . : $TOR+ ICE status . . . . . . : Awaiting expiration=================================================================================


ICE Kill

ICE KillYou can kill either a single ICE or a group of ICEs. To select ICEs to kill, select the ICE Kill option (M) on the CICS path or enter fast path C.M from any panel. A summary of all ICEs appears which is the same as the summary shown in Figure 124 on page 255.

To isolate a specific ICE for termination, place the cursor on that ICE and press PF11. To kill all ICEs associated with a terminal or transaction, enter TERM=cccc or TRAN=cccc after the ICEK statement, followed by KILL.. cccc indicates a specific or generic terminal or transaction ID. Use * to specify a generic ID. For example,

ICEK TRAN=AB* KILL

kills the ICEs associated with transactions starting with AB.

When you request ICE termination, a confirmation panel appears. Enter YES to continue with termination or press PF3 to cancel the request and return to the summary display.

Journal Control Table (JCT)


Journal Control Table (JCT)CICS journals contain before-images for dynamic transaction backout (DTB) and may contain afterimages for forward recovery of files or databases. Also, applications may write user journal records. Each journal used by the region is defined in the JCT. Journals are accessed by number.

To display JCT entry attributes as shown in the following figure, select the JCT option (N) on the CICS path or enter fast path C.N from any panel.

FIGURE 126. Journal Control Table Attributes Panel (C.N)

To select journals with a specific attribute, place the cursor on the line describing the attribute and press PF11. To select a specific journal, you can enter ID=journalnumber after JCT.

TABL JCT,ID=0*

The above statement produces a summary display of journals 1–9.

For a JCT entry in dump format, enter DUMP after journalnumber.

TABL JCT,ID=journalnumber DUMP

To select journals with several attributes, enter SEL= followed by a list of attributes. The syntax is:

TABL JCT,SEL=(attr1,attr2,.....attrn)

If you zoom on the All Table Entries field, a JCT summary appears as shown in the following figure.

________________ ZJCT VTM $CICSTOR V520./I SYSA 02/03/93 9:33:24> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR> H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT> O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ> V-TCT W-Trace X-PCT Y-TD==============================================================================> JOURNAL CONTROL TABLE TABL JCT++ Closed . . . . . . . . : CLO+ Opened . . . . . . . . : OPE+ SMF format . . . . . . : SMF++ All table entries . . . : *==============================================================================



FIGURE 127. JCT Summary Panel (Accessed by Zoom)

For each journal, this panel shows:

To display detailed information on a particular journal, place the cursor on that line and press PF11. The journal entry appears as shown in the following figure.

Journal ID Journal identifier in the JCT.

Journal Type Type of journal such as Tape, Disk, or SMF.

I/O Type Whether this is an input or output journal.

Journal Status Whether this journal is open, closed, or switching.

Current Extent CICS ddname for this journal.

Switch Options Options this journal will use when switching and pausing.

Error Options Options this journal will use when I/O errors are encountered, such as Retry and Crucial.

________________ ZZTABLA VTM $CICSTOR V520./I SYSA 02/03/93 9:34:04> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ================================================================================> ALL TABLE ENTRIES TABL JCT ID=’*’+ Entries selected: 2 Skipped: 0+ Journal Journal I/O Journal Current Switch Error+ ID Type Type Status Extent Options Options+ -------- -------- -------- -------- -------- -------- --------+ 01 Disk/2 Input Open DFHJ01A None Crucial+ 02 SMF Output Open None None None===============================================================================



FIGURE 128. JCT Entry Panel (Accessed by Zoom)

________________ ZZTABLE VTM $CICSTOR V520./I SYSA 02/03/93 9:34:40> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ================================================================================> SELECTED TABLE ENTRY TABL JCT ID=’01’+ General Information+ Journal ID . . . . . . : 01 JCTE address . . . . . : 00052CC8+ Journal status . . . . : Open Data format . . . . . . : CICS+ Journal type . . . . . : Disk/2 Open option . . . . . . : Initial+ Resource security level : 0 Owning CSSY TCA address : 0053ABE8+ Owning CSSY task number : 17 Syswait option . . . . : Start/IO++ Journal Options+ Crucial . . . . . . . . : Yes I/O type . . . . . . . : Input+ Retry . . . . . . . . . : Yes Auto/archive . . . . . : No+ Pause . . . . . . . . . : No++ Data Information+ Logical record count . : 309 Buffer start address . : 00539128+ Physical block count . : 71 Buffer shift-up address : 00539928+ Average block size . . : 436 Buffer end address . . : 0053A980+ Buffer full count . . . : 0 Buffer size . . . . . . : 6232+ Buffer shift-up count . : 0 Buffer shift-up value . : 2048++ Dataset Information+ Current journal extent is DFHJ01B : CICSV.V311.$TOR.DFHJ01B==================================================================================


Processing Program Table (PPT)

Processing Program Table (PPT)All programs (load modules) managed by CICS Program Management are defined in the PPT. PPT entries are defined through macros or RDO and also include information from the Loader Domain for CICS/ESA.

To display PPT entry attributes as shown in the following figure, select the PPT option (Q) on the CICS path or enter fast path C.Q from any panel.

FIGURE 129. Processing Program Table Attributes Panel (C.Q)

To select programs with a specific attribute, place the cursor on the line describing the attribute and press PF11. To select a specific program, you can enter ID=program after PPT as in the following example.

TABL PPT ID=DFHABCD

For a program entry in dump format, enter DUMP after program.

TABL PPT,ID=program DUMP

To select programs with several attributes, enter SEL= followed by a list of attributes. The syntax is:

TABL PPT,SEL=(attr1,attr2,.....attrn)

________________ ZPPT VTM $CICSTOR V520./I SYSA 02/03/93 9:37:59> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR> H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT> O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ> V-TCT W-Trace X-PCT Y-TD================================================================================> PROCESSING PROGRAM TABLE (PROGRAMS) TABL PPT++ Assembler . . . . . . . : ASM+ COBOL . . . . . . . . . : COB+ C programs . . . . . . : C+ Disabled . . . . . . . : DIS+ Enabled . . . . . . . . : ENA+ Macro level . . . . . . : MAC+ BMS map . . . . . . . . : MAP+ PL1 . . . . . . . . . . : PL1+ RPL loaded . . . . . . : RPL+ Non-zero use count . . : USE++ All table entries . . . : *================================================================================



You can use the wildcard character * in program. For example:

If you zoom on the All Table Entries field, a PPT summary appears as shown in the following figure.

FIGURE 130. PPT Summary Panel (Accessed by Zoom)

For programs in the selected category, this panel shows:

ID=DFH* Specifies programs beginning with DFH.

ID=*YZ Specifies programs ending with YZ.

ID=A*B* Specifies programs beginning with A and having a B anywhere but at the end of the name.

Program Name Program load module name.

Program Attributes Attributes of this program, such as enabled or disabled, and programming language.

Note: In a CICS/ESA Version 4 system, the programming language shown will be the deduced language. If the language has not been deduced, the defined language will be shown.

Program Address Location of the program in storage.

Program Length Size of the program.

________________ ZZTABLA VTM $CICSTOR V520./I SYSA 02/03/93 9:38:29> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ================================================================================> ALL TABLE ENTRIES TABL PPT ID=’*’+ Entries selected: 1471 Skipped: 0+ Program Program Program Program Load Current Total+ ID Attribs Address Length Count Usage Usage+ -------- -------- -------- -------- -------- -------- --------+ ACFAECMD Ena Asm 0 98560 0 0 0+ ACFAECXP Ena Asm 0 1496 0 0 0+ ACFAEMTP Ena Asm 0 79088 0 0 0+ ACFAESIP Ena Asm 0 18976 1 0 1+ ACFAESPI Ena Asm 0 1328 0 0 0+ ACFAETSP Ena Asm 0 1008 1 0 27+ ACFAEUCC Ena Asm 0 1056 0 0 0+ ACFAEUCM Ena Asm 001E4C00 704 1 0 2225+ ACFAEUSP Ena Asm 001F7000 10992 1 0 739+ ACF6ACF Ena Asm 0 0 0 0 0+ ACF6ASCP Ena Asm 0 0 0 0 0+ ACF6BRUL Ena Asm 0 0 0 0 0+ ACF6INF Ena Asm 0 0 0 0 0+ ACF60ACF Ena Asm 0 0 0 0 0+ ACTP1 Ena PL1 0 179496 0 0 0+ ACTP2 Ena PL1 0 8 0 0 0+ APLLOS01 Ena Asm 0 7904 0 0 0+ APLLOS10 Ena Asm 0 9760 0 0 0



To display detailed information on a particular program, place the cursor on that line and press PF11.

The PPT entry appears as shown in the following figure.

FIGURE 131. PPT Entry Panel (Accessed by Zoom)

Note: The Loaded from field may contain the following values:

Load Count Number of times this program has been loaded.

Current Usage Current number of tasks using this program.

Total Usage Number of times this program has been used in this CICS run.

RPL indicates a private copy of the module was loaded from the relocatable program library (RPL)

REGION indicates a private copy of the module was loaded from either the STEPLIB or LINKLIST concatenation

LPA indicates a shared version of the module from the Link Pack Area (LPA) is being used

________________ ZZTABLE VTM $CICSTOR V520./I SYSA 02/03/93 9:38:58> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ================================================================================> SELECTED TABLE ENTRY TABL PPT ID=’DFHCRQ’+ General Information+ Program ID . . . . . . : DFHCRQ PPTE address . . . . . : 0882B990+ Program status . . . . : Enabled Defined program language: Assemblr+ Resource security level : n/a Deduced program language: Assemblr+ Program length . . . . : 904 Total use count . . . . : 1+ Current use count . . . : 0 Total load count . . . : 1+ Current copies . . . . : 1 Load status . . . . . . : Loaded+ Load point . . . . . . : 087B6760 Loaded from . . . . . . : RPL+ Entry point . . . . . . : 887B6780+ RPL dataset . . . . . . : CICS.CICS410.SDFHLOAD++ Usage Attributes+ Command level . . . . . : Yes PCLASS=system . . . . . : No+ CEDF allowed . . . . . : No Install type . . . . . : Grplist+ Amode . . . . . . . . . : 31 Rmode . . . . . . . . . : Any+ Program attribute . . . : Reusable Data location . . . . . : Any+ Exec key . . . . . . . : CICS++ Program Statistics+ Use count . . . . . . . : 1 Fetch count . . . . . . : 1+ Deletes by compression : 0 Refreshes . . . . . . . : 0+ Statistics last reset . : 9:00:01================================================================================

System Initialization Table (SIT)


System Initialization Table (SIT)The SIT is used by CICS at initialization time. The SIT contains global, startup parameters for the CICS region.

To display entries from the SIT, select the SIT option (R) on the CICS path or enter fast path C.R from any panel.

An alphabetical list of all SIT parameters showing the keyword, description and value appears. For more information on a keyword, refer to the appropriate IBM CICS publication.

The SIT contains numerous parameters. A partial example of the SIT display is shown in the following figure.


System Initialization Table (SIT)

FIGURE 132. System Initialization Table (SIT) Panel (C.R)

To display a particular keyword and all subsequent keywords in alphabetical order, enter

SEL=keyword

after the SIT statement on this panel.

To display the SIT in dump format, place the cursor on SIT address and press PF11. Several SIT parameters are zoomable. Look for zoomable fields which are highlighted in white.

________________ ZSIT VTM $CICSTOR V520./I SYSA 02/03/93 14:01:31> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR> H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT> O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ> V-TCT W-Trace X-PCT Y-TD=================================================================================> SYSTEM INITIALIZATION TABLE SIT+ SIT suffix . . . . . . : A1 SIT address . . . . . . : 00043990++ Keyword Description Value+ -------- ------------------------------------------------ --------+ ADI Alternate delay interval (s) . . . . . . . . . : 30+ AIEXIT Autoinstall exit program . . . . . . . . . . . : CANZATDX+ AILDELAY Autoinstall delete delay interval (hhmmss) . . : 0+ AIQMAX Autoinstall max concurrent logons . . . . . . : 100+ AIRDELAY Autoinstall restart logon delay (hhmmss) . . . : 520+ AKPFREQ Activity keypoint frequency . . . . . . . . . : 2000+ AMXT Maximum active tasks . . . . . . . . . . . . . : 50+ APPLID Generic VTAM application ID . . . . . . . . . : $CICSTOR+ Specific VTAM application ID . . . . . . . . . : $CICSTOR+ AUTCONN XRF autoconnect delay (hhmmss) . . . . . . . . : 0+ AUXTR Auxiliary trace . . . . . . . . . . . . . . . : Off+ AUXTRSW Auxiliary trace autoswitch facility . . . . . : No+ BFP Built-in functions support . . . . . . . . . . : Yes+ BMS Basic mapping support . . . . . . . . . . . . : Full+ BMS start-up option . . . . . . . . . . . . . : Cold+ BMS map alignment . . . . . . . . . . . . . . : Unalign+ BMS device dependent suffixing . . . . . . . . : NODDS+ CHKSTRM Terminal storage violation checking . . . . . : None+ CHKSTSK Task storage violation checking . . . . . . . : None+ CICSSVC CICS type 3 SVC . . . . . . . . . . . . . . . : 235+ CLSDSTP CLSDST pass notify . . . . . . . . . . . . . . : Notify+ CLT Command list table suffix . . . . . . . . . . :+ CMXT Maximum tasks transaction class 1 . . . . . . : 1+ Maximum tasks transaction class 2 . . . . . . : 1+ Maximum tasks transaction class 3 . . . . . . : 1+ Maximum tasks transaction class 4 . . . . . . : 1+ Maximum tasks transaction class 5 . . . . . . : 1+ Maximum tasks transaction class 6 . . . . . . : 1+ Maximum tasks transaction class 7 . . . . . . : 1===============================================================================

Terminal Control Table Prefix (TCTFX)


Terminal Control Table Prefix (TCTFX)The TCT prefix (TCTFX) includes options global to CICS terminal control and specific to autoinstall, the receive-any pool, and XRF.

To display entries from the TCT prefix as shown in the following figure, select the TCTFX option (S) on the CICS path or enter fast path C.S from any panel.

For the TCT prefix in dump format, place the cursor on the TCT ad and press PF11. Or, enter DUMP after TCTV.

FIGURE 133. Terminal Control Table Prefix Panel (C.S)

The zoomable fields on this screen are:

n TCT addressn Exit program namen VTAM is XRF capable

Note: When HPO is not active, its value appears in yellow. When the VTAM ACT state is closed, its value appears in red.

________________ ZTCTV VTM $CICSTOR V520./I SYSA 02/03/93 9:22:27> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR> H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT> O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ> V-TCT W-Trace X-PCT Y-TD===============================================================================> TERMINAL CONTROL TABLE PREFIX TCTV+ General Information+ TCT address . . . . . . : 0007F300 TCT suffix . . . . . . : DY+ OPNDST/CLSDST limit . . : 10 HPO is active . . . . . : No+ CICS specific applid . : $CICSTOR Print key value . . . . : X’FF’+ CICS generic applid . . : $CICSTOR CICS system jobname . . : $CICSTOR+ VTAM ACB state . . . . : Open RA high water mark . . : 3+ Maximum RA size . . . . : 256 Times at RA HWM . . . . : 1+ RAs currently in use . : 0+ Fully qualified LU name : USCACO01.$CICSTOR++ AUTOINSTALL Information+ Exit program name . . . : CANZATDX Total deletes . . . . . : 9+ Total requests . . . . : 20 Requests rejected . . . : 0+ Peak requests . . . . . : 1 Times at peak requests : 20+ Externally enabled . . : Yes Internally enabled . . : No+ Max requests . . . . . : 100 Times at max requests . : 0+ Postponed logons . . . : 0 Peak postponed logons . : 0++ XRF Information+ VTAM is XRF capable . . : Yes Current/last catch-up ID: X’0000’+ Clean-up=none . . . . . : 0 Clean-up=clear/sdt . . : 0+ Clean-up=unbind . . . . : 0 XRF reconnect try number: 1===============================================================================


Temporary Storage Usage

Temporary Storage UsageTemporary storage is used by CICS for application common areas and by CICS as well as applications for passing data between transactions. Each queue is accessed by an 8-character unique queue name. When an application creates a queue, it assigns the queue name. Each record in the queue is an item. Only recoverable or remote queues need to be defined in the Temporary Storage Table.

Temporary storage queues created by applications remain until an application program deletes it. This may result in the Temporary Storage dataset filling up. Once the dataset is full, problems arise because no new queues can be created. Also, high CA/CI split activity on the Temporary Storage dataset can degrade performance.

Queues remain available until a CICS or Temporary Storage cold start. Temporary Storage queues may be recoverable or nonrecoverable. Recoverable queues are indicated in the Temporary Storage Table (TST).

To display temporary storage file and usage statistics as shown in the following figure, select the TS option (T) on the CICS path or enter fast path C.T from any panel.

FIGURE 134. Temporary Storage Panel (C.T)

________________ ZTMPS VTM $CICSTOR V520./I SYSA 02/03/93 9:23:57> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR> H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT> O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ> V-TCT W-Trace X-PCT Y-TD================================================================================> TEMPORARY STORAGE TMPS+ General Temporary Storage Information+ Common area address . . : 00191028 Aux control area address: 001910D0+ Byte map address . . . : 00000000 Current queues . . . . : 0+ Queues HWM . . . . . . : 1 Total queues created . : 1+ Items in any queue HWM : 1 Unit table compressions : 0+ Requests suspended . . : No Total requests suspended: 0+ Records PUTQ . . . . . : 2 Records PUT . . . . . . : 0+ Records PUT(Q) to main : 1 Records PUT(Q) to aux . : 0+ Records GET from main . : 1 Records GET from aux . : 0+ Entries per TSGID . . . : 8 TSGID extensions . . . : 0+ Entries per initial UTE : 254 Unit table frees . . . : 0++ Main Temporary Storage Information+ Virtual storage used . : 0 Virtual storage used HWM: 164++ Auxiliary Temporary Storage Information+ No auxiliary temporary storage information available=======================================================================

Temporary Storage Usage


This panel includes:

Common Area Address Address of the common temporary storage area in memory.

Aux Control Area Addr Address of the auxiliary control area in memory.

Byte Map Address Location of the temporary storage control interval byte map.

Current Queues Number of TS queues currently in existence.

Queues HWM Highwater mark of the number of simultaneous TS queues for this CICS run.

Total Queues Created Total number of TS queues created for this CICS run.

Items in any Queue HWM Highwater mark of the number of simultaneous items in any queue.

Unit Table Compressions Number of times the TS unit table has been compressed.

Requests Suspended Whether TS requests are currently suspended.

Total Reqs Suspended Total number of TS requests suspended for this CICS run.

Records PUTQ Count of TS PUTQ records.

Records PUT Count of TS PUT records.

Records PUT(Q) to Main Count of records PUT(Q) to main TS.

Records PUT(Q) to Aux Count of records PUT(Q) to auxiliary TS.

Records GET from Main Count of record GETs from main TS.

Records GET from Aux Count of record GETs from auxiliary TS.

Entries per TSGID Number of entries per TS group identification.

TSGID Extensions Number of extensions to TS group identification.

Entries per Initial UTE Number of entries per initial unit table.

Unit Table Frees Number of TS unit table frees for this CICS run.

Virtual Storage Current amount of virtual storage usage by temporary storage.

Used Virtual Storage Used HWM

Highwater mark of virtual storage usage for this CICS run.


Temporary Storage Queues

Temporary Storage QueuesTo display the current temporary storage queues, place the cursor on the Current Queues field and press PF11. Alternatively, you can select the TSQ option (U) on the CICS path or enter fast path C.U from any panel. Temporary storage queues appear as shown in the following figure.

FIGURE 135. Temporary Storage Queues Panel (C.U)

________________ ZTSQ VTM $CICSTOR V520./I SYSA 02/03/93 9:23:57> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR> H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT> O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ> V-TCT W-Trace X-PCT Y-TD================================================================================> TEMPORARY STORAGE QUEUES TSQ+ Number of TS queues selected: 16 Skipped: 0+ Queue Queue Items in Current Queue Overlen Recovery+ ID Location Queue Item Size Items Option+ -------- -------- -------- -------- -------- -------- --------+ ACCTQ123 Main 12 3 14K 0 No+ .NXQ.... Aux 14 1 26K 0 No+ .NXQ... Aux 14 1 26K 0 No+ .NXQ.... Aux 14 1 26K 0 No+ .NXQ.... Aux 14 1 26K 0 No+ .NXQ.... Aux 14 1 26K 0 No+ BATCHFIL Aux 13 1 51K 13 No+ CHECKDUP Aux 1 2 64 0 No================================================================================

Temporary Storage Queues



Queue ID Identifies the queue with an 8-character name. Queue names that start with ‘.’ are created by CICS when the length of the data record exceeds the CI size. Queues that start with ‘.NXQ’ are nonrecoverable while ‘.RXQ’ are recoverable queues.

Queue Location Location of the queue: Main Storage (Main) or Auxiliary Storage (Aux).

Items in Queue Count of records in the queue.

Current Item Item retrieved by the current READQ NEXT.

Queue Size Amount of space that this queue occupies, in bytes.

Overlen Records Number of TS records that are larger than a single CI. CICS can write TS records to a single TS queue only up to the CI size of the auxiliary TS dataset. To handle requests for larger amounts of data, CICS writes the data to CICS overflow queue(s).

If a queue contains overlength records, the queue size does not reflect data written to overflow queues.

Recovery Option Whether the queue is recoverable as specifed in the CICS Temporary Storage Table.


Terminal Control Table (TCT)

Terminal Control Table (TCT)Whether you define your terminals directly in the TCT or by autoinstall, there is a resulting TCT. With autoinstall, TCT entries exist only while terminals are active.

To display TCT entry attributes as shown in the following figure, select the TCT option (V) on the CICS path or enter fast path C.V from any panel.

FIGURE 136. Terminal Control Table Attributes Panel (C.V)

To select terminals with a specific attribute, place the cursor on the line describing the attribute and press PF11. To select a specific terminal, you can enter ID=termid after TCT as in the following example.

TABL TCT,ID=L624

For a terminal entry in dump format, enter DUMP after termid.

TABL TCT,ID=termid DUMP

To select terminals with several attributes, enter SEL= followed by a list of attributes. The syntax is:

TABL TCT,SEL=(attr1,attr2,.....attrn)

________________ ZTCT VTM $CICSTOR V520./I SYSA 02/03/93 9:40:15> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR> H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT> O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ> V-TCT W-Trace X-PCT Y-TD================================================================================> TERMINAL CONTROL TABLE TABL TCT++ Acquired . . . . . . . : ACQ+ ATI eligible . . . . . : ATI+ Autoinstall . . . . . . : AUT+ BSAM terminals . . . . : BSA+ Console . . . . . . . . : CNS+ Connections . . . . . . : CON+ CRE eligible . . . . . : CRE+ In service . . . . . . : INS+ IRC links . . . . . . . : IRC+ ISC links . . . . . . . : ISC+ No ATI . . . . . . . . : NAT+ No CRE . . . . . . . . : NCR+ No TTI . . . . . . . . : NTT+ Out service . . . . . . : OUT+ Released . . . . . . . : REL+ Remote . . . . . . . . : REM+ TTI eligible . . . . . : TTI+ Storage violations . . : VIO+ VTAM terminals . . . . : VTA++ All table entries . . . : *=============================================================================



You can use the wildcard character * in termid. For example:

If you zoom on the All Table Entries field, a TCT summary panel appears as shown in the following figure.

FIGURE 137. TCT Summary Panel (Accessed by Zoom)

For terminals in the selected TCT category, this panel shows:

ID=DFH* Specifies terminals beginning with DFH.

ID=*YZ Specifies terminals ending with YZ.

ID=A*B* Specifies terminals beginning with A and having a B anywhere but at the end of the name.

Term ID Terminal ID for this entry.

Term Type Type of terminal, such as: console, 3270, or LU2.

Term Status Status of this terminal, such as: in service, out of service, released, or acquired.

Initiate Status Method of initiation, such as TTI (Terminal Transaction Initiation) and ATI (Automatic Transaction Initiation).

________________ ZZTABLA VTM $CICSTOR V520./I SYSA 02/03/93 9:40:47> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ===============================================================================> ALL TABLE ENTRIES TABL TCT ID=’*’+ Number of entries: 476 Skipped: 0+ Term Term Term Initiate Paging VTAM Active+ ID Type Status Status Status Netname Tran ID+ -------- -------- -------- -------- -------- -------- --------+ $TOR Sys/LOC Ins n/a n/a $CICSTOR n/a+ CIMS Sys/IRC Ins n/a n/a CIMS n/a+ DB2E Sys/IRC Ins n/a n/a $DB2CICS n/a+ ACEZ 3270 Rel Ins Ati Tti Page AACLC030 None+ ACFZ 3270 Rel Ins Ati Tti Page AACLC031 None+ AC0Z LU2 Rel Ins Ati Tti Page AACLC000 None+ AC00 LU2 Rel Ins Ati Tti Page AACLC000 None+ AC1E 3270 Rel Ins Ati Tti Page AACLC030 None+ AC1F 3270 Rel Ins Ati Tti Page AACLC031 None+ AC1Z LU2 Rel Ins Ati Tti Page AACLC016 None+ AC10 LU2 Rel Ins Ati Tti Page AACLC016 None+ CERR Console Ins Tti Page n/a None+ CNSA Console Ins Tti Page n/a None+ CNSB Console Ins Tti Page n/a None+ CNSC Console Ins Tti Page n/a None+ CNSD Console Ins Tti Page n/a None+ CNSE Console Ins Tti Page n/a None+ CNSF Console Ins Tti Page n/a None+ CNSL Console Ins Tti Page n/a None+ CNS2 Console Ins Tti Page n/a None===============================================================================



To display detailed information on a particular terminal, place the cursor on that line and press PF11. The TCT entry varies depending on whether it is a 3270, BDAM, console, or remote terminal, or it is a system connection or link.

A TCT entry for a 3270 terminal is shown in the following figure.

FIGURE 138. TCT 3270 Entry Panel (Accessed by Zoom)

If you select a TCT entry for a BSAM terminal, the General Information section appears as shown in this figure.

Paging Status Status of paging, such as Auto or Page.

VTAM Netname Name VTAM uses for this terminal.

Active Tran ID Transaction identifier currently running on this terminal.

________________ ZZTABLE VTM $CICSTOR V520./I SYSA 02/03/93 9:41:17> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ================================================================================> SELECTED TABLE ENTRY TABL TCT ID=’AC1E’+ General Information+ Terminal ID . . . . . . : AC1E TCTTE address . . . . . : 0015F8F0+ Terminal type . . . . . : 3270 Terminal model . . . . : 2+ Session status . . . . : Released VTAM netname . . . . . : AACLC030+ Service status . . . . : Ins Session create status . : Create+ Initiate status . . . . : Ati Tti Paging status . . . . . : Page+ Screen size . . . . . . : 24x80 Alternate screen size . : None+ Page size . . . . . . . : 24x80 Alternate page size . . : 24x80+ User area length . . . : 8 Read timeout value . . : 0+ Auto-installed . . . . : No Shippable . . . . . . . : Yes+ Terminal features . . . : (Audalarm,Uctran,Selpen)+ Extended attributes . . : (Extds,Color)++ Transaction Information+ Active transaction ID . : None Task number . . . . . . : n/a+ Next transaction ID . . : None Commarea address . . . : None++ Terminal Statistics+ Number of inputs . . . : 0 Transmission errors . . : 0+ Number of outputs . . . : 0 Transaction errors . . : 0+ Number of transactions : 0 Storage violations . . : 0================================================================================



FIGURE 139. TCT BSAM Entry (Accessed by Zoom)

If you select a TCT entry for a console terminal, the General Information section appears as shown in the this figure.

FIGURE 140. TCT Console Entry (Accessed by Zoom)

A connection entry shows the status and session traffic for a connection or group of links between CICS and another system (CICS or IMS). If you select a TCT entry for a connection, the entry appears as shown in this figure.

FIGURE 141. TCT Connection Entry (Accessed by Zoom)

+ General Information+ Terminal ID . . . . . . : SEQ1 TCTTE address . . . . . : 0003B400+ Terminal type . . . . . : CRLP Terminal model . . . . : 0+ Session status . . . . : n/a VTAM netname . . . . . : None+ Service status . . . . : Ins Session create status . : n/a+ Auto-installed . . . . : No Shippable . . . . . . . : no+ TCTLE address . . . . . : 0008B690 Record length . . . . . : 0+ Input DCB . . . . . . . : 0008B51C Output DCB . . . . . . : 00002B34+ I/O block address . . . : 00000000 I/O area address . . . : 00000000

+ General Information+ Terminal ID . . . . . . : CNSA TCTTE address . . . . . : 00175310+ Terminal type . . . . . : Console Console ID . . . . . . : 10+ Service status . . . . : Ins Session create status . : n/a+ Initiate status . . . . : Tti Paging status . . . . . : Page+ Screen size . . . . . . : None Alternate screen size . : None+ Page size . . . . . . . : 06x80 Alternate page size . . :+ User area length . . . : 100 Read timeout value . . :

+ General Information+ Terminal ID . . . . . . : CICS TCTTE address . . . . . : 0883E2D0+ Terminal type . . . . . : System Terminal model . . . . : None+ Session status . . . . : Acquired VTAM netname . . . . . : G410S10+ Service status . . . . : Ins Session create status . : n/a++ System Information+ System type . . . . . . : ISC/LU62 XRF system name . . . . : None+ Bind security operative : n/a CONNECT=ALL specified . : No+ Bind security specified : No++ System Statistics+ Primary links . . . . . : 8 Secondary links . . . . : 0+ Primary links in use . : 1 Secondary links in use : 0+ Total link allocates . : 0 Queued link allocates . : 0+ Failed link allocates . : 0 Max allocs outstanding : 0+ Number of AIDs queued . : 0 FC requests . . . . . . : 0+ IC requests . . . . . . : 0 TD requests . . . . . . : 0+ TS requests . . . . . . : 0 DL1 requests . . . . . : 0



An IRC entry describes an individual link between CICS and another system (CICS or IMS). If you select a TCT entry for an IRC link, the entry appears as shown in this figure.

FIGURE 142. TCT SYS/IRC Entry (Accessed by Zoom)

If you select a TCT entry for a remote terminal, which is a terminal residing in another region, the General Information section appears as shown in this figure.

FIGURE 143. TCT Remote Entry (Accessed by Zoom)

___________ ZZTABLE VTM TDOCS01 V520./C SYSA 02/03/93 14:05:02> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ===============================================================================> SELECTED TABLE ENTRY TABL TCT ID=’RI1’+ General Information+ Terminal ID . . . . . . : RI1 TCTTE address . . . . . : 00142BB0+ Terminal type . . . . . : IRC Link Terminal model . . . . : None+ Session status . . . . : n/a VTAM netname . . . . . : TDOCSIRS+ Service status . . . . : Ins Session create status . : n/a++ Transaction Information+ Active transaction ID . : None Task number . . . . . . : n/a+ Next transaction ID . . : None Commarea address . . . : None++ Terminal Statistics+ Number of inputs . . . : 0 Transmission errors . . : 0+ Number of outputs . . . : 0 Transaction errors . . : 0+ Number of transactions : 0 Storage violations . . : n/a

+ General Information+ Terminal ID . . . . . . : MMLL TCTTE address . . . . . : 001D7030+ Terminal type . . . . . : Remote Terminal model . . . . : None+ Remote system name . . : CICS Remote terminal id . . : CCSS+ Remote system netname . : TDOCS10

CICS Trace


CICS TraceA CICS trace is a recording of CICS activity at points in CICS or application processing that aid in problem diagnosis. The places where activity is traced may be controlled by CICS or by application request. For example, activity that can be traced includes: I/O, storage acquisition, storage release, or transfer of control.

To view general information about the CICS trace component which manages CICS traces, select the Trace option (W) on the CICS path or enter fast path C.W from any panel. The display for CICS/ESA regions appears as shown in the following figure.

FIGURE 144. CICS Trace Overview Panel for CICS/ESA (C.W)

________________ ZTRAC VTM $CICSTOR V520./I SYSA 02/03/93 9:23:12> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR> H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT> O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ> V-TCT W-Trace X-PCT Y-TD===============================================================================> CICS TRACE OVERVIEW TRAC+ Trace Control Information+ Internal trace status . : Started Internal trace size . . : 500K+ Aux trace status . . . : Stopped Aux trace extent . . . : DFHAUXT+ GTF trace status . . . : Stopped Aux switch status . . . : No+ Master system trace . . : On Master user trace . . . : On+ Aux trace dataset name : CICSV.V311.$TOR.DFHAUXT++ Trace Component Standard Special+ Comp Name Tracing Tracing+ -------- ------------------ -------- --------+ AP Application domain 1 1-2+ BF Built-in function 1 1+ BM BMS 1 1+ DC Dump compatibility 1 1+ DI Data interchange 1 1+ DM Domain manager 1 1-2+ DS Dispatcher domain Off Off+ DU Dump domain 1 1-2+ EI Exec interface 1 1+ FC File control 1 1-2+ GC Global catalog 1 1-2+ IC Interval control 1 1+ IS ISC 1 1-2+ JC Journal control 1 1+ KC Task control 1 1+ KE Kernel 1 1-2+ LC Local catalog 1 1-2+ LD Loader domain 1 1-2+ LM Lock domain 1 1-2+ ME Message domain 1 1-2+ MN Monitoring domain 1 1-2+ PA Parameter domain 1 1-2+ PC Program control 1 1


CICS Trace

In CICS/ESA, each component can have trace turned on or off independently. This panel shows which components are being traced and the level of trace, including whether special tracing and/or standard tracing is active. It also shows which of the three trace destinations is active: GTF, internal, or auxiliary. See the IBM CICS Problem Determination Guide for more information.

The display for CICS/MVS regions appears as shown in the following figure.

FIGURE 145. CICS Trace Overview Panel for CICS/MVS (C.W)

This panel shows the level of tracing and monitoring in your CICS system. You can zoom on the Program Check/Abend Trace Table field for more information about abends that have occurred. And you can zoom on the Trace Table Address field to see a dump of the trace table header.

________________ ZTRAC VTM $CICSCAN V520./I SYSA 02/03/93 9:37:41> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR> H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT> O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ> V-TCT W-Trace X-PCT Y-TD================================================================================> CICS TRACE OVERVIEW TRAC+ Trace Control Information+ Trace entry address . . : 005E71D0 Prog Chk/Ab Trace table : 0068E268+ MCT address . . . . . . : 00698AE8 CICS Trace table . . . : 00691960+ Trace program address . : 006966CC Trace control stub . . : 00000000+ Return address . . . . : n/a Storage violation trap : No+ Storage trace flag . . : X’00’++ Trace/Monitoring Flags+ Master trace flag . . . : System Trace FE entries . . . : No+ Auxiliary trace . . . . : No Monitor class=EXCP . . : No+ Monitor class=PERF . . : No Monitor class=ACCT . . : No++ Trace Level Indicators+ Task control . . . . . : Yes Storage control . . . . : Yes+ Program control . . . . : Yes Interval control . . . : Yes+ Dump control . . . . . : Yes File control . . . . . : Yes+ Transient data control : Yes Temp/Storage control . : Yes+ Responses . . . . . . . : Yes Exec/Interface . . . . : Yes+ Data/Interchange . . . : Yes Synchpoint . . . . . . : Yes+ Terminal . . . . . . . : Yes Built-in function . . . : Yes+ BMS . . . . . . . . . . : Yes Journal control . . . . : Yes+ ISC . . . . . . . . . . : Yes User exit . . . . . . . : Yes===============================================================================

Program Control Table (PCT)


Program Control Table (PCT)All CICS transactions for the region are defined in the PCT. Transactions to be executed in another region include a SYSID indicator for transaction routing. The table entries shown include the parameters you define through macros or RDO as well as the attributes from the associated common RDO profile.

To display PCT entry attributes as shown in the following figure, select the PCT option (X) on the CICS path or enter fast path C.X from any panel.

FIGURE 146. Program Control Table Attributes Panel (C.X)

To select transactions with a specific attribute, place the cursor on the line describing the attribute and press PF11. To select a specific transaction, you can enter ID=transid after PCT.

TABL PCT,ID=M2*

For a PCT entry in dump format, enter DUMP after transid.

TABL PCT,ID=transid DUMP

To select transactions with several attributes, enter SEL= followed by a list of attributes. The syntax is:

TABL PCT,SEL=(attr1,attr2,.....attrn)

You can use the wildcard character * in transid. For example:

ID=DFH* Specifies transactions beginning with DFH.

ID=*YZ Specifies transactions ending with YZ.

ID=A*B* Specifies transactions beginning with A and having a B anywhere but at the end of the name.

________________ ZPCT VTM $CICSTOR V520./I SYSA 02/03/93 9:35:41> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR> H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT> O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ> V-TCT W-Trace X-PCT Y-TD================================================================================> PROGRAM CONTROL TABLE (TRANSACTIONS) TABL PCT++ Disabled . . . . . . . : DIS+ Enabled . . . . . . . . : ENA+ Remote . . . . . . . . : REM+ Non-zero TWA length . . : TWA+ Non-zero use count . . : USE+ Storage violations . . : VIO++ All table entries . . . : *================================================================================



If you zoom on the All Table Entries field, a PCT summary appears as shown in the following figure.

FIGURE 147. PCT Summary Panel (Accessed by Zoom)

For each transaction in the selected category, this panel shows:

To display detailed information on a particular transaction code, place the cursor on that line and press PF11. A PCT entry appears as shown in the following figure.

Tran ID Transaction identifier for this table entry.

Tran Status Status for this transaction (Enabled, Disabled).

Tran Priority Transaction priority for this transaction. Priority can be numbered up to 255.

Tran Class Transaction class (TCLASS) of the current transaction.

Program ID Identifier of the first program invoked by this transaction.

TWA Size Size of the Transaction Work Area for this transaction.

Use Count Number of times this transaction has been invoked.

________________ ZZTABLA VTM $CICSTOR V520./I SYSA 02/03/93 9:36:11> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ===============================================================================> ALL TABLE ENTRIES TABL PCT ID=’*’+ Entries selected: 310 Skipped: 0+ Tran Tran Tran Tran Program TWA Use+ ID Status Priority Class ID Size Count+ -------- -------- -------- -------- -------- -------- --------+ -REC Enabled 1 0 DSNCCOM1 1068 0+ -STA Enabled 1 0 DSNCCOM1 1068 0+ -STO Enabled 1 0 DSNCCOM1 1068 0+ ACFM Enabled 1 0 ACFAEMTP 0 0+ ACFT Enabled 1 0 ACFAETSP 0 2+ ADYN Enabled 1 0 DFH99 0 0+ BB Enabled 64 0 DFHCRP 0 0+ BBRE Enabled 64 0 DFHCRP 0 0+ CATD Enabled 255 0 DFHZATD 0 39+ CBRC Enabled 1 0 DFHBRCP 0 0+ CD Enabled 64 0 DFHCRP 0 34+ CDAE Enabled 64 0 DFHCRP 0 19+ CDBC Enabled 255 0 DFHDBME 0 0+ CDBD Enabled 255 0 DFHDBDI 0 0+ CDBI Enabled 1 0 DFHDBIQ 0 0+ CDBT Enabled 255 0 DFHDBDSC 0 0+ CDCA Enabled 64 0 DFHCRP 0 0



FIGURE 148. PCT Entry Panel (Accessed by Zoom)

Note: Fields preceded by an asterisk (*) appear only in CICS/ESA Version 4. The section titled Security Attributes appears only in CICS/MVS.

________________ ZZTABLE VTM $CICSTOR V520./I SYSA 02/03/93 9:37:07> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ================================================================================> SELECTED TABLE ENTRY TABL PCT ID=’CATD’+ General Information+ Transaction ID . . . . : CATD Entry address . . . . . : 0881A1E0+ Program ID . . . . . . : DFHZATD Profile ID . . . . . . : DFHCICSV+ TWA size . . . . . . . : 0 Transaction status . . : Enabled+ *Transaction priority . : 255 *Transaction class : (none)+ Storage violations . . : 0 Screen selection . . . : Primary+ Use count . . . . . . . : 0 Partitionset name . . . : None+ *Task data location . . : Any *Task data key . . . . . : CICS+ *Storage clear . . . . . : No *Task runaway . . . . . : 0+ *Transaction isolate . . : Yes++ Remote Attributes+ Dynamic routing . . . . : No Local dyn/route count . : 0+ Remote system . . . . . : None Remote dyn/route count : 0+ Remote name . . . . . . : None++ Recovery Attributes+ Deadlock timeout (s) . : 0 Read timeout . . . . . : 0+ Stall purge . . . . . . : No Terminal purge . . . . : No+ Dump . . . . . . . . . : Yes Trace . . . . . . . . . : Yes+ Restart . . . . . . . . : No Restart counter . . . . : 0++ Security Attributes+ Trans security . . . . : Yes Trans security level . : 1+ Resource security . . . : No Resource security level : 0===============================================================================


Transient Data

Transient DataIntrapartition transient data queues reside on the Transient Data dataset. These queues provide sequentially accessible storage for CICS or applications. They can be created by application programs and may be deleted automatically after use or explicitly. Each queue is accessed by a 4-character queue name which must be defined in the DCT.

Extrapartition transient data queues are ordinary sequential datasets residing outside of CICS. In order to be accessed within CICS, they must be defined in the DCT as extrapartition queues.

CICS uses Transient Data to build queues of data for later processing, put messages on system queues for printing, initiate tasks based on a queue trigger level, and request logging for recovery.

Applications use Transient Data to print messages when a trigger level is reached (ATI), transfer data between tasks, and capture data for batch processing.

Transient Data looks at the Destination Control Table (DCT) for definitions of intrapartition queues (destinations) and extrapartition datasets. See “Destination Control Table (DCT)” on page 238 for more information on DCT entries.

Excessive CI/CA splits or insufficient space in the Transient Data dataset may degrade CICS performance.

To display Transient Data dataset statistics and usage as shown in the following figure, select the TD option (Y) on the CICS path or enter fast path C.Y from any panel.

Transient Data


FIGURE 149. Transient Data Panel (C.Y)


Static Area Address Location of the transient data static area in storage.

Buffer Common Area Location of the buffer common area in storage.

String Common Area Location of the string common area in storage.

Control Interval Size Size of the TD control interval, in bytes.

Total Control Intervals Total number of currently formatted control intervals.

CIS in use HWM Highwater mark of allocated control intervals.

Control Intervals in Use Current number of allocated control intervals.

% of CIs in Use Percentage of formatted CIs that are currently allocated.

Total I/O Errors Number of transient data I/O errors.

Times NOSPACE Returned

Number of times the NOSPACE condition was returned for a TD request.

Records GET Number of GET requests for TD records.

Records PUT Number of PUT requests for TD records.

Maximum Record Length

Maximum record length of a TD record.

________________ ZTRND VTM $CICSTOR V520./I SYSA 02/03/93 9:25:16> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-AIDs B-AID Kill C-CSA D-DCT E-DLI F-DDIR G-PDIR> H-Dumps I-Exits J-XRF K-FCT L-ICEs M-ICE Kill N-JCT> O-PAM DSA P-PAM EDSA Q-PPT R-SIT S-TCTFX T-TS U-TSQ> V-TCT W-Trace X-PCT Y-TD================================================================================> TRANSIENT DATA TRND+ General Transient Data Information+ Static area address . . : 05394000 Buffer common area . . : 05394070+ String common area . . : 053940E0 Control interval size . : 4096+ Total control intervals : 0 CIs in use HWM . . . . : 0+ Control intervals in use: 0 % of CIs in use . . . . : 0%+ Total I/O errors . . . : 0 Times NOSPACE returned : 0+ Records GET . . . . . . : 0 Records PUT . . . . . . : 0+ Maximum record length . : 4064 Minimum record length . : 1+ Buffers requested . . . : 3 Buffers allocated . . . : 3+ Buffer size . . . . . . : 4096 Total buffers used . . : 0+ Buffers in use . . . . : 0 Buffers in use HWM . . : 0+ Current buffer waits . : 0 Buffer waits HWM . . . : 0+ Total buffer waits . . : 0 Total format requests . : 0+ Strings allocated . . . : 3 Total strings used . . : 0+ Strings in use . . . . : 0 Strings in use HWM . . : 0+ Current string waits . : 0 String waits HWM . . . : 0+ Total string waits . . : 0===============================================================================


Transient Data

Minimum Record Length Minimum record length of a TD record.

Buffers Requested Number of buffers requested for TD processing.

Buffers Allocated Number of buffers allocated for TD processing.

Buffer Size Size of each buffer, in bytes.

Total Buffers Used Total number of TD buffers used.

Buffers in Use Number of TD buffers currently in use.

Buffers in Use HWM Highwater mark of concurrent buffers in use by transient data.

Current Buffer Waits Number of transient data requests currently waiting for buffers.

Buffer Waits HWM Highwater mark of concurrent TD requests that had to wait for buffers.

Total Buffer Waits Total number of TD requests that had to wait for buffers.

Total Format Requests Total number of format requests.

Strings Allocated Number of strings currently allocated.

Total Strings Used Total number of strings currently used.

CICS Shutdown Option


CICS Shutdown OptionOMEGAMON II enables you to control whether or not and in what manner you want tasks to be purged when a CICS shutdown is issued. If OMEGAMON II is running, you can automatically purge tasks that are waiting for terminal output during CICS shutdown. CICS will not terminate during normal shutdown if these tasks are not purged.

Select CICS Shutdown Options (Q) on the Control Options path or enter fast path O.Q from any panel. The current CICS shutdown purge option appears as shown in the following figure.

FIGURE 150. CICS Shutdown Purge Option

This panel displays the current shutdown option as well as the available options and their descriptions. To modify the shutdown option, enter one of the following options after the OPT statement:

PURGE enables you to automate the purge procedure. You can speed up CICS shutdown, because you do not have to rely on operator intervention.

? Displays the current shutdown purge option.

PURGE OMEGAMON II purges all conversational tasks waiting for terminal input at CICS shutdown.

NOPURGE No tasks are purged at CICS shutdown.

OPER Operator specifies whether tasks are to be purged at shutdown time in response to a WTOR. Possible values are YES or NO.

________________ ZCOPT VTM TDOCS01 V520./C SYSG 02/03/93 12:46:30> PF1 Help PF3 Back PF4 Main Menu > A-RTA On B-RTA Off C-RTA Status D-RTA Intervals E-RTA Scaling> F-ONDV On G-ONDV Off H-ONDV Status I-Bottleneck Ctl J-Wait Reasons> K-INTR Ctl L-IANL On M-IANL Off N-IANL Settings O-IANL Groups> P-Collection Control Q-CICS Shutdown Options===============================================================================> CICS SHUTDOWN PURGE OPTION > To alter CICS shutdown purge option, enter over current option displayed: OPT NOPURGE++ Display/Change the CICS shutdown purge option++ ? . . . . . : Display current shutdown purge option++ PURGE . . . : Purge all tasks waiting for terminal input++ NOPURGE . . : Do not purge any tasks++ OPER . . . : Have operator specify whether tasks are to be+ purged at shutdown time in response to WTOR============================================================================

MVS Analysis 285

MVS Analysis

Chapter OverviewMVS system factors can affect the availability and response time of your CICS system. In order to determine whether any key categories of MVS system activity are adversely affecting CICS, OMEGAMON II analyzes CPU utilization and paging activity. For additional levels of detail, OMEGAMON II also provides information on the PSW, the structure of currently running CICS Task Control Blocks (TCBs), and MVS load modules.

Chapter Contents

CPU and Paging Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286

Program Status Word (PSW). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291TCB Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292MVS Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293

14

CPU and Paging Utilization


CPU and Paging UtilizationOMEGAMON II’s CPU utilization displays show TCB and SRB usage for the CICS region. This can indicate if your CICS region is in a loop or using excessive amounts of CPU.

CICS runs mainly on a single TCB, and is heavily impacted by page-ins.

OMEGAMON II provides information, such as private area statistics and working set size, to allow you to define the storage requirements for your region, and thereby minimize paging for a critical region.

You can display CPU and paging utilization in graphic or report format.

To produce a graph as shown in the following figure, select the System Graphs option (A) on the MVS path or enter M.A to fast path from any panel.

FIGURE 151. CICS System Analysis Panel (M.)

________________ ZMSYSA VTM CICSP01 V520/I SYSA 02/03/99 16:37:07> PF1 Help PF3 Back PF4 Main Menu > A-System Graph B-System Summary C-PSW D-TCBs E-Modules F-Subpools================================================================================> To complete initialization, press ENTER. CSYS GRAPH+ CICS System Environment+ System Data- Short|0.1.2.3.4.5.6.7.8.9.0| Long |0.1.2.3.4.5.6.7.8.9.0|+ TCB Time(%) 5.6 |->. . . . . . . . . .| 1.1 |> . . . . . . . . . .|++ SRB Time(%) .6 |> . . . . . . . . . .| .1 |> . . . . . . . . . .|++ Page-ins/s_ 3.8 |------=>. . . . . . .| .7 |->. . . . . . . . . .|++ Page-outs/s .0 |> . . . . . . . . . .| .0 |> . . . . . . . . . .|+ I/O’s/sec__ 25.7 |----->. . . . . . . .| 5.1 |->. . . . . . . . . .|++ SU’s/sec___ 1731 |--->. . . . . . . . .| 352 |> . . . . . . . . . .|++ Working Set 3228K |------> . . . . . . .| 3077K|------> . . . . . . .|++ Pg-in/CPU-s 62.6 |------======> . . . .| 12.5 |--> . . . . . . . . .|+================================================================================

MVS Analysis 287


The graph shows short and long-term figures for the following items.

To produce a comprehensive listing of MVS-related utilization information in report format, select the System Summary option (B) on the MVS path or enter M.B to fast path from any panel. The System Summary panel appears as shown in the following figure.

TCB Time (%) Displays current task control block (TCB) usage as a percentage of total CPU consumption for 1 CPU.

TCB% is computed as CPU seconds attributed to all TCBs in an address space divided by the elapsed seconds in a reporting interval. For example, if .5 CPU seconds are used in 1 second, OMEGAMON II reports 50% TCB Time. Values over 100% represent the time of multiple TCBs running on a processor with multiple engines.

SRB Time (%) Displays the service request block (SRB) time used by this address space as a percentage of total CPU consumption for 1 CPU.

SRB% is computed as CPU seconds spent by the address space, in SRB mode, divided by the elapsed seconds in a reporting interval. For example, if .5 CPU seconds are used in 1 second, OMEGAMON II reports 50% SRB Time.

Page-ins/s Number of page-ins that have occurred for this address space in the reporting interval divided by the elapsed seconds in that interval.

Page-outs/s Number of page-outs that have occurred in this address space in the reporting interval divided by the elapsed seconds in that interval.

I/O’s/sec Number of non-terminal I/O requests completed for this address space in the reporting interval divided by the elapsed seconds in that interval.

SU’s/sec Number of MVS service units (SU) that have been used by the monitored address space in the reporting interval divided by the elapsed seconds in that interval.

Working Set Amount of storage (1K=1024 bytes) frequently recalled to prevent this storage from being paged-out. This also may be viewed as the minimum amount of storage required for CICS to continue executing without having to wait for page-ins to complete.

Page-ins/CPU-s Number of page-ins that have occurred for this address space in the reporting interval divided by the CPU seconds allocated to the address space in that interval.



FIGURE 152. System Summary Panel (M.B)

All information in the above display is address space related as follows:

Jobname Jobname of the CICS job.

Procstep Procedure stepname of the CICS job.

Stepname Name of the current step of the CICS job.

Total SRB time Total Service Request Block time used.

Total TCB time Total Task Control Block time used by the CICS job.

Total CPU Time Sum of the SRB and TCB times.

System Init Time Start time for the current CICS run.

System Init Date Start date for the current CICS run.

Elapsed Time Time elapsed since CICS was started.

________________ ZMSYS VTM $CICSTOR V520/I SYSA 02/03/99 10:42:56> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-System Graph B-System Summary C-PSW D-TCBs E-Modules F-Subpools===============================================================================> SYSTEM SUMMARY CSYS+ General Information+ Jobname . . . . . . . . : $CICSTOR Procstep . . . . . . . : CICS+ Stepname . . . . . . . : $CICSTOR Total SRB time . . . . : 56.83+ Total TCB time . . . . : 324.50 Total (SRB+TCB) CPU time: 381.33+ System initiation time : 21:51:57 System initiation date : 02/03/99+ Elapsed time . . . . . : 12:50 HR Time in transaction . . : 12:51 HR+ Dispatching algorithm . : MTW Dispatching priority . : (61) 97+ I/O dispatching priority: (60) 96 I/O counts . . . . . . : 21105+ SRM performance group . : 51 SRM domain number . . . : 8+ Highest UIC . . . . . . : 243 Fixed frame count . . . : 63+ VIO slot count . . . . : 0 Non-VIO slot count . . : 2333+ Total CPU service units : 3223240 Total I/O service units : 185094+ Storage service units . : 0 Total SRB service units : 568712+ Total service units used: 3977046++ Private Area Statistics+ Page-in count . . . . . : 2637 Page-out count . . . . : 0+ Page-in time units . . : RESIDENT Page-in rate/second . . : .00+ PPGRT(R) minimum . . . : 1 PPGRT(R) maximum . . . : 2+ Target working set size : None Real working set size . : 4804K+ Expand working set size : 516K Actual working set size : 5320K+ Minimum working set size: None Maximum working set size: None++ Common Area Statistics+ Page-in count . . . . . : 18 Page-in rate/second . . : 0+ CPGRT minimum . . . . . : 2 CPGRT maximum . . . . . : 4+ Target working set size : 200K Actual working set size : 27116K+ Minimum working set size: 200K Maximum working set size: 8192G===============================================================================

MVS Analysis 289


Time in Transaction Time elapsed since the performance group of the CICS region changed or since a new IPS was set into effect.

Dispatching Algorithm

Dispatching algorithm in use: Mean Time to Wait, Rotate, Time Slice, or Fixed.

Dispatching Priority Address space control block dispatching priority.

I/O Dispatching Priority

Address space control block I/O dispatching priority.

I/O Counts Number of I/Os since the start of the job.

SRM Performance Group

System Resources Manager (SRM) performance group number.

SRM Domain Number

System Resources Manager domain number.

Highest UIC Highest unreferenced interval count.

Fixed Frame Count Number of frames that are fixed in real storage.

VIO Slot Count Number of slots for virtual I/O datasets.

Non-VIO Slot Count Number of slots for nonvirtual I/O datasets.

Total CPU Service Units

Number of CPU service units used by this CICS.

Total I/O Service Units

Number of I/O service units used by this CICS.

Storage Service Units

Number of MSO service units used by this CICS.

Total SRB Service Units

Number of Service Request Block service units used by this CICS.

Total Service units Total service units used by this CICS.



The remaining part of the display contains paging statistics for the CICS private area and the common area.

Page-in Count Number of page-ins for this job.

Page-out Count Number of page-outs for this job.

Page-in Time Units Category of time unit, in seconds, for page-in rate: RESIDENT, CPU, or ELAPSED.

Page-in Rate/Second Current page-in rate per second.

PPGRT(R) min Minimum private page-in rate.

PPGRT(R) max Maximum private page-in rate.

Target Working Set Size

Target working set size chosen by SRM.

Real Working Set Size

Size of the working set in real storage.

Expand Working Set Size

Size of the working set in expanded storage.

Actual Working Set Size

Current working set size (real and expanded).

Minimum Working Set Size

Minimum working set size according to SRM.

Maximum Working Set Size

Maximum working set size according to SRM.

CPGRT Minimum Minimum common page-in rate.

CPGRT Maximum Maximum common page-in rate.

MVS Analysis 291

Program Status Word (PSW)

Program Status Word (PSW)To display information about the Program Status Word (PSW), select the PSW option (C) on the MVS path or enter fast path M.C. For CICS/ESA, the display in the following figure shows the PSW and the general purpose registers (GPRs) for the most significant CICS TCBs: the quasi-reentrant (QR), the concurrent (CO), and the resource-owning (RO). For CICS/MVS, the display shows only one PSW and set of registers.

The data is taken from the last time the CICS program request block (PRB) lost control of the CPU. You can use the PSW display to help debug CICS problems such as loops or unusual waits.

FIGURE 153. PSW and Registers Panel (M.C)

________________ ZMPSW VTM $CICSTOR V520/I SYSA 02/03/99 16:11:13> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-System Graph B-System Summary C-PSW D-TCBs E-Modules F-Subpools===============================================================================> PSW and REGISTERS PSW+ Quasi-Reentrant TCB+ PSW : 078D1000 85108F0A+ R0 . : 00000001 R1 . : FA974000 R2 . : 00000004 R3 . : 85108308+ R4 . : 0568B000 R5 . : 05109307 R6 . : 80FAE934 R7 . : 00000048+ R8 . : 0568E000 R9 . : 00006179 R10 : 0568C020 R11 : 00000000+ R12 : 00000001 R13 : 05176A50 R14 : 00000114 R15 : 807E2F20++ Concurrent TCB+ PSW : 078D2000 85108FD2+ R0 . : 00000001 R1 . : 05690018 R2 . : 0568B2E8 R3 . : 85108308+ R4 . : 0568B000 R5 . : 05109307 R6 . : 00000090 R7 . : 00000048+ R8 . : 05690000 R9 . : 000008D1 R10 : 00000000 R11 : 00000090+ R12 : 0568B258 R13 : 0517AA50 R14 : 00000007 R15 : 807E22C0++ Resource-Owning TCB+ PSW : 078D2000 85108FD2+ R0 . : 00000001 R1 . : 0568F018 R2 . : 0568B2A0 R3 . : 85108308+ R4 . : 0568B000 R5 . : 05109307 R6 . : 00000048 R7 . : 00000048+ R8 . : 0568F000 R9 . : 0000010A R10 : 00000000 R11 : 00000048+ R12 : 0568B258 R13 : 05178A50 R14 : 0000001B R15 : 807E33A0===============================================================================

TCB Structure


TCB StructureRunning a program under a TCB allows a certain amount of independence from other programs running in the same address space. This includes the ability of the program to be dispatched and perform work despite the fact that other tasks are waiting.

OMEGAMON II analyzes the structure of CICS TCBs, allowing you to assess how a program is performing. Further, since many third-party products attach multiple TCBs, you can use this feature to locate where they are attached.

To display the TCB structure in your CICS region, select the TCB option (D) on the MVS path or enter fast path M.D from any panel. The following figure shows the TCB Structure display for CICS/ESA.

FIGURE 154. CICS TCB Structure Panel (M.D)

For further information about each TCB, enter X preceding the TCBS statement which is below PEEK.

________________ ZMTCBS VTM $CICSTOR V520/I SYSA 02/03/99 17:23:02> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-System Graph B-System Summary C-PSW D-TCBs E-Modules F-Subpools===============================================================================> CICS TCB STRUCTURE PEEK $CICSTOR ASID=209 >> OB8112: Data Collection Initiated << tcbs Program Mother Daughter Sister Jobstep+ IEAVAR00 IEESB605 (Self) (Region Control Task)+ IEESB605 IEAVAR00 DFHSIP IEAVTSDT (Self) (Started Task Control)+ DFHSIP IEESB605 DFHKETCB (Self)+ DFHKETCB DFHSIP DFHKETCB DFHTRTCB DFHSIP+ DFHKETCB DFHKETCB DFHSKTSK DFHSIP+ DFHSKTSK DFHKETCB ACFF9SUB DFHSIP+ ACFF9SUB DFHKETCB ACFF9SUB DFHSIP+ ACFF9SUB DFHKETCB OCXMCR0D DFHSIP+ OCXMCR0D DFHKETCB DFHJCTSK DFHSIP+ DFHJCTSK DFHKETCB DFHKETCB DFHSIP+ DFHKETCB DFHKETCB DFHSIP+ DFHTRTCB DFHSIP DFHSIP+ IEAVTSDT IEAVAR00 (Self) (SVC Dump Task)===============================================================================

MVS Analysis 293

MVS Modules

MVS ModulesTo display modules that have been loaded into the CICS region by an MVS load macro, select the Modules option (E) on the MVS path or enter fast path M.E from any panel. The MVS Loaded Modules panel appears as shown in the following figure.

FIGURE 155. MVS Loaded Modules in the CICS Address Space Panel (M.E)

This panel includes the name of each module along with its entry point address, length, use count, and load module attributes. The modules displayed may include monitors, vendor packages, DB2, DLI, and certain nucleus modules. Note that the display does not include CICS programs loaded into DSA.

________________ ZMMODS VTM $CICSTOR V520/I SYSA 02/03/99 16:11:44> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-System Graph B-System Summary C-PSW D-TCBs E-Modules F-Subpools===============================================================================> MVS LOADED MODULES IN THE CICS ADDRESS SPACE PEEK $CICSTOR ASID=223 >> OB8112: Data Collection Initiated << mods+ Module Entry Length Users Attributes+ #CA-ENF# 00001000 00001000 256 RENT,REUS,AUTH,AC=1+ DFHSKTSK 000080C0 00000028 1 RENT,REUS,AUTH+ DFHMNSVC 85797250 00000790 1 RENT,REUS,AUTH+ ACFF9SUB 00644730 000058D0 3 RENT,REUS,AUTH+ ACFFEPCS 00643820 000007E0 1 RENT,REUS,AUTH+ ACF75DCM 0063F5A0 00002A60 1 RENT,REUS,AUTH+ ACF70CMP 00639600 00005A00 1 RENT,REUS,AUTH+ ACF61CMD 0062F090 00009F70 2 RENT,REUS,AUTH+ ACFCMPLR 0062F090 00009F70 0 RENT,REUS,AUTH,ALIAS(ACF61CMD)+ ACFDCMPL 0062F750 00009F70 0 RENT,REUS,AUTH,ALIAS(ACF61CMD)+ ACFAEENR 0058F288 00000578 1+ ACFAEENF 000433D8 00000598 1+ ACFAEACX 005EA3E0 00009C20 1+ ACFAEICX 005DE640 0000B9C0 1+ ACFAEDFH 005D8000 00006000 1+ ACFAEOM1 005D4D08 000032F8 1+ OCCCENFD 851D4BB8 00000240 1 RENT,REUS,AUTH+ OCDBINFD 8577A5A8 000008A0 1 RENT,REUS,AUTH+ OCDBSP0D 851ED288 000003E0 1 RENT,REUS,AUTH+ OCDBST0D 857B0EA8 00002240 1 RENT,REUS,AUTH+ OCEXECFD 005D3298 00000DE0 1 RENT,REUS,AUTH+ OCGLUEFD 857AE9B8 000016C0 1 RENT,REUS,AUTH+ OCTRUEFD 00595590 00000A00 1 RENT,REUS,AUTH+ OCQRYCFD 851D4DF8 000002E0 1 RENT,REUS,AUTH+ OCXMCR0D 85798748 00001640 1 RENT,REUS,AUTH+ OCXMST0D 8527B640 00000740 1 RENT,REUS,AUTH+ OCOMK0FD 851D3D08 00000320 1 RENT,REUS,AUTH+ OCCOMM00 005D1028 00001040 1 AUTH+ DFHIRW00 84A666A0 00000228 1 RENT,REUS,AUTH+ DFHJCOCP 00597278 00000DB0 1 AUTH+ DFHWTI 8577C628 000029F8 1 RENT,REUS,AUTH+ DFHXSS 00595F9C 00001148 1 RENT,REUS,AUTH+ DFHASV 00594690 00000990 2 RENT,REUS,AUTH

MVS Modules


DASD Performance 295

DASD Performance

Chapter OverviewHeavily used DASD volumes will affect the response time of CICS applications. By viewing the activity on DASD volumes, you can better balance their usage.

Chapter Contents

DASD Response Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296

Devices Exceeding a Threshold. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298DASD Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299Device Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300

DASD plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .302

15

DASD Response Times


DASD Response TimesTo display the DASD response time for specified volumes, select the DASD option (A) on the I/O path or enter fast path I.A from any panel. The CICS DASD Statistics panel appears as shown in the following figure.

FIGURE 156. CICS DASD Statistics Panel (I.A)

This panel shows device statistics for all volumes allocated to your CICS region. To see all MVS allocated volumes, remove the F preceding the PDSK statement which is below CDEV. To select devices for display, enter a pattern containing the starting character of the volser followed by an * after the PDSK statement.

________________ ZDASD VTM $CICSTOR V520/I SYSA 02/03/99 13:49:56> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom>> A-DASD B-DASD Degradation C-DASD Users D-DASD Detail E-DASD Plot ==============================================================================> CICS DASD STATISTICS> For all MVS-allocated devices, remove the F preceding PDSK.> For device usage, place the cursor on the volser and press PF11.> CDEV Interval Start Time: 13:44:04 Elapsed: 5:52 MN Length: 14:55 MNFpdsk * <-- Volser Pattern+ Volser I/O per second Util% Avg.Q Resp = IOSQ + Pend + Conn + Disc+ ------ Total CICS ----- ----- ------ ------ ------ ------ ------+ 153 MIS001+ 160 DBCR01 12.2 4.7 7.4 .02 12.6 3.1 .2 1.8 7.4+ 162 DBCR04 11.2 .9 3.9 .01 14.2 3.7 .3 2.1 8.1+ 163 DBCR02 2.5 1.4 4.1 .01 24.0 7.0 .3 3.1 13.5+ 164 CAN001 10.2 3.1 7.4 .5 .6 2.7 3.5+ 165 CAN003 6.1 4.7 13.0 1.3 .3 2.6 8.8+ 16B PPSMP1 .5 .1 .2 10.4 1.1 3.1 6.0+ 16F PPSMP7 .3 .2 14.5 .2 9.2 5.0+ 177 PPSMP8 9.5 4.8 7.6 .7 .3 3.9 2.6+ 302 OMON28 .9 2.8 17.4 .7 6.9 9.7+ 308 PRI001 6.9 1.0 6.3 .01 21.2 3.2 .2 2.7 15.0+ 309 PPSMP4 .6 4.0 .2 1.8 1.9+ 314 PPSMP5 .9 1.4 11.5 2.1 4.8 4.5+ 315 PPSMP2 .8 1.3 4.7 1.1 2.9 .6+ 31A PPSMPE 5.6 2.7 5.4 .5 .2 2.7 1.8 ==============================================================================


DASD Response Times

The start time, elapsed time of the RMF interval during which these statistics have been collected, and length are displayed to the right of the line beginning with the CDEV statement. The meanings of the columns are as follows:

Total I/O per second I/O rate for total usage of this device.

CICS I/O per second I/O rate for usage of this device.

Util % Device utilization percent.

Avg Q Average I/O queue depth.

Resp Average total device response time in milliseconds.

IOSQ Average I/O queue time in milliseconds.

Pend Average pending time in milliseconds.

Conn Average connect time in milliseconds.

Disc Average disconnect time in milliseconds.

Devices Exceeding a Threshold


Devices Exceeding a ThresholdTo display the same statistics for devices exceeding a threshold, select the DASD Degradation option (B) on the I/O path or enter fast path I.B from any panel. The DASD Exceeding Thresholds panel appears as shown in the following figure.

FIGURE 157. DASD Exceeding Thresholds Panel (I.B)

This panel display DASD devices exceeding the specified threshold which in this case is 35 milliseconds of response time (RSP035). Instead of RSP035, enter one or more threshold values beneath the CDEV statement from the following list:

Only one of the above criteria must be met for a threshold to be exceeded.

Note: In order to use these thresholds for subsequent sessions, you must save them in your profile. See the OMEGAMON II for CICS Configuration and Customization Guide for details.

The F preceding the XDSK statement requests only CICS allocated volumes that meet the specified criteria. To display all volumes that meet the specified criteria, remove the F preceding the XDSK statement.

AVQnnn Average length > nn.n.

RSPnnn Average total response time > nnn milliseconds.

IOSnnn Average IOS queue time > nnn milliseconds.

CONnnn Average device connect time > nnn milliseconds.

DSCnnn Average device disconnect time > nnn milliseconds.

DUTnnn Device utilization > nnn %.

PNDnnn Average request pending time > nnn milliseconds.

________________ ZDASX VTM TDOCS01 V520/C SYSG 02/03/99 10:35:38> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-DASD B-DASD Degradation C-DASD Users D-DASD Detail E-DASD Plot===============================================================================> DASD EXCEEDING THRESHOLDS> For device usage, place the cursor on the volser and press PF11. CDEV Interval Start Time: 10:29:06 Elapsed: 6:31 MN Length: 14:53 MN rsp035Fxdsk+ Volser I/O per second Util% Avg.Q Resp = IOSQ + Pend + Conn + Disc+ ------ Total CICS ----- ----- ------ ------ ------ ------ ------+ 303 OMON29 2.4 .2 44.3 27.5 3.3 13.5+ 319 OMON35 47.9 5.1 10.6 .06 73.1 19.1 22.2 8.8 23.0+ 329 IMS100 .2 .1 41.2 .1 28.3 12.7+ 338 OMON20 10.7 3.4 37.5 2.5 3.9 17.6 13.5===============================================================================


DASD Users

DASD UsersTo find the current users of a device as shown in the following figure, select the DASD Users option (C) on the I/O path or enter fast path I.C from any panel.

FIGURE 158. DASD Allocation, User, and Number of Open DCBs Panel (I.C)

For each device, this panel shows:

DISK Volser.

DADR Device unit address.

DUSR User last allocated to the device (when device busy).

DOPN Number of open DCBs on this device.

________________ ZDASU VTM $CICSTOR V520/I SYSA 02/03/99 13:51:55> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-DASD B-DASD Degradation C-DASD Users D-DASD Detail E-DASD Plot===============================================================================> DASD ALLOCATION, USER, and NUMBER of OPEN DCBs> For device detail, place the cursor on the volser and press PF11. DISK CHKPT2 SYSG21 SYSG22 MP422G XASRES SV0001 MIS002 MIS001+ dadr 140 141 142 143 150 151 152 153 dusr dopn 1 12 10 ============================================================================== DISK PRI003 MT422G CAN002 MVSG21 HSM004 OMON30 VMXA11 OMON26+ dadr 154 155 156 157 158 159 15A 15B dusr dopn 2 78 1 1 9 67 ============================================================================== DISK SYSA25 MP422H SYSA22 MP420A PRI001 PPSMP4 QM0001 OMON25+ dadr 304 305 306 307 308 309 30A 30B dusr dopn 84 31 24 4 20 ==============================================================================

Device Detail


Device DetailTo view detailed information for a particular device and a list of files allocated on that device, place the cursor on a volser on the DASD Users panel, as shown in the previous figure, and press PF11. The Examine One Device panel displays.

FIGURE 159. Examining a Specific Device (Accessed by Zoom)

The DEV statement and the statements below it display the following device information:

DEV ccc Device address.

DBsy D indicates device busy and S indicates suspended channel program.

IOQ Depth of I/O queue, where a plus sign (+) indicates more than 9.

IO# I/O number, where a greater than sign (>)indicates the start of I/O.

CPU Vertical bar (|) indicates dispatchable tasks and period (.) indicates nondispatchable tasks (no ready TCBs).

User User of the device.

Cyl Cylinder being accessed.

Nrdy N indicates that the device is not ready.

Resv R indicates that the device is reserved.

________________ ZZDPLT VTM TDOCS01 V520/C SYSG 02/03/99 10:44:18> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ===============================================================================> EXAMINE ONE DEVICE DEV 314 Volser=PPSMP5 Online Alloc dplt 2 ________ OMEGAMON Peek at Unit=314 Volser=PPSMP5 ____+ |DBsy DDDDDDDDDDDDDDDDDDDDDDDDDSSSSSSSSSSSSSSSSSSSSSSSSS| Samples: 50+ |IOQ | Interval: 2+ |I/O# >62 | I/O’s: 1+ |CPU .........................|+ |User |+ |Cyl >0548 |+ |Nrdy |+ |Resv | > To scroll the display, enter number in column 1 of FILE> For file details, place the cursor on your choice and press PF11. FILE VOL=PPSMP5+ Number of files selected: 4 Skipped: 0+ DDname Dataset name VOLSER Attributes+ -------- -------------------------------------------- ------ ----------+ STEPLIB CICS.V311.LOADLIB PPSMP5 Blk=06144+ STEPLIB CICS.V311.LOADLIB1 PPSMP5 Blk=32760+ DFHRPL CICS.V311.LOADLIB PPSMP5 Blk=06144+ DFHRPL CICS.V311.LOADLIB1 PPSMP5 Blk=32760===============================================================================


Device Detail

You can also obtain detailed information on a specific device by entering the DASD Detail option (D) on the I/O path or fast path I.D from any panel. The DASD Detail panel appears as shown in the following figure. You can then enter the device address.

FIGURE 160. DASD Detail Panel (I.D)

To select another device, replace the address after DEV with the unit address you want.

The DEV statement and the statements below it display the following device detail:

DEV Unit information.

DIO Device I/O count from RMF.

DIO.R Device I/O rate per second from RMF.

DIOQ Depth of I/O queue.

DOPN Number of open DCBs.

DUSR Current user of this device.

DRES Device reserve count.

DSTA Mount status of this volume (Private, Public or Storage).

________________ ZDASV VTM TDOCS01 V520/C SYSG 02/03/99 10:39:18> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-DASD B-DASD Degradation C-DASD Users D-DASD Detail E-DASD Plot===============================================================================> DASD DETAIL> Replace the address following DEV with the unit address you want. DEV 141 Volser=SYSG21 Online Alloc dio .R ....... dioq dopn dusr dres dsta Private dtyp 3380 dvmp Mount Status:Perm Res Private Shared+ Status:+ User: *MASTER* Waiting I/O’s:+ Status: - Suspended Channel Program <Paging Device>++ UCB Prefix: F32790+ 00040140 00FC5900 00FC5900 0001002E 189C0002 F00020F0 3C3D7C7D 00000000+ 01080000 00000001 00000000 00FC5900++ UCB Common + DASD Device Dependent Segment: F327C0+ 008AFF8C 01410800 00F32860 00F1F4F1 3030200E 00F32770 000F0100 E2E8E2C7+ F2F15000 00000003++ Common Extension: F32770+ 00000940 20220040 01BC6F10 00000000 00000000 00FD0188 00F327E8 00000000===============================================================================

Device Detail


DASD plotTo view a plot of recent device activity as shown in the following figure, select the DASD Plot option (E) on the I/O path or enter fast path I.E from any panel.

FIGURE 161. DASD Plot Panel (I.E)

This graph displays 50 samples of activity on a selected device taken every nn milliseconds. Enter the number of milliseconds you want between each sample after the DPLT statement. For example,

DPLT05

sets the sampling interval to 5 milliseconds. The default setting is 1 millisecond.

Each column of the graph represents 1 sample. The symbol shown in the column represents the drive’s status during that interval. In particular, watch for an IOQ depth consistently greater than 1. A string of Ds across the graph indicates that the device is constantly busy.

DTYP Device type.

DVMP Hex dump of UCB for this device.

________________ ZDASP VTM TDOCS01 V520/C SYSG 02/03/99 10:40:32> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-DASD B-DASD Degradation C-DASD Users D-DASD Detail E-DASD Plot===============================================================================> DASD PLOT> Replace the address following DEV with a valid DASD address or volser. DEV 141 Volser=SYSG21 Online Alloc dplt01 ________ OMEGAMON II Peek at Unit=141 Volser=SYSG21_____+ |DBsy DDDDDDDDDDDDDDDDDDDDDDDDDSSSSSSSSSSSSSSSSSSSSSSSSS| Samples: 50+ |IOQ | Interval: 2+ |I/O# >62 | I/O’s: 1+ |CPU .........................|+ |User |+ |Cyl >0548 |+ |Nrdy |+ |Resv |===============================================================================

Utilities 303

Utilities

Chapter OverviewThe OMEGAMON II utility functions enable you to issue MVS console, CICS master terminal, and common interface commands. Also, this path includes debugging options which take a snapshot of your CICS region, print OMEGAMON II debugging panels, verify key OMEGAMON II components, and display current maintenance levels. In addition, there are several options that enable you to view, scan, or modify various types of storage: OMEGAMON II common interface, operating system common area, CICS, and dataspaces.

The options that issue commands, or list or modify storage, include statements that must be preceded by a hyphen (-). When the statement executes, the hyphen changes to >, making the statement a comment, and a message is returned. To reissue the statement, you must uncomment it. Instead of a hyphen, you may precede these statements with <. In this case, a message is returned but the statement remains, so that you can merely press Enter to reissue it.

Chapter ContentsAccessing Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .304Issuing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305

Issuing operating system console commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305Issuing CICS master terminal commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .306Issuing OMEGAMON II common interface commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .307

Obtaining Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308Taking a CICS snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308Obtaining OMEGAMON II diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .309Verifying OMEGAMON II components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311Verifying OMEGAMON II maintenance levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315

Viewing and Modifying Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316Common interface or common area storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316CICS storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318Dataspace storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320

16

Accessing Utilities


Accessing UtilitiesTo access the Utilities menu, select the Utilities option (U) on the main menu or enter fast path U. from any panel. The Utilities menu appears.

FIGURE 162. Utilities Menu Panel (U.)

In order to maintain the integrity of your system, your installation may secure many or all of the options on this menu. If authorization is required, enter /PWD on the Info-line.

To select an option from the Utilities menu, enter the selection letter on the Info-line.

Press PF3 to return to the above menu and then make your next selection. You can also enter the fast path to navigate directly from one menu option to another.

_______________ ZUTIL> PF1 Help PF3 Exit PF4 Main Menu ============================================================================> Enter your selection on the top line.> Authorized Functions (Enter /PWD on the top line.)> UTILITIES> A CONSOLE ............ Issue MVS console commands and view messages> B OMEGAMON DISPLAY.... Display OMEGAMON or common area storage> C OMEGAMON SCAN ...... Scan OMEGAMON or common area storage> D OMEGAMON ZAP ....... Modify OMEGAMON or common area storage> E CICS DISPLAY........ Display CICS address space storage> F CICS SCAN .......... Scan CICS address space storage> G CICS ZAP ........... Modify CICS address space storage> H DATASPACE DISPLAY .. Display dataspace storage> I DATASPACE SCAN ..... Scan dataspace storage> J DATASPACE ZAP ...... Modify dataspace storage> K DATASPACE LIST ..... List dataspaces for CICS job and common inter face> L MASTER TERMINAL .... Display or change CICS master terminal settings> M INTERFACE .......... Issue common interface commands> N SNAPSHOT ........... Perform OMEGAMON Snapshot of CICS region> Diagnostic Aids> O DEBUG .............. Print OMEGAMON diagnostics (First enter /PWD)> P VERIFY ............. Verify OMEGAMON component availability> Q MAINTENANCE ........ Current release levels and OMEGAMON maintenance ============================================================================

Utilities 305

Issuing Commands

Issuing CommandsThe Utilities menu includes options to issue commands that can control MVS, JES, CICS, or the OMEGAMON II common interface.

Issuing operating system console commandsTo issue an MVS or JES console command, select the Console option (A) on the Utilities menu or enter fast path U.A from any panel. The Operating System Console panel appears.

FIGURE 163. Operating System Console Panel (U.A)

To issue an operator command,

n If there is a > preceding the OCMD statement, replace it with a hyphen.

n Enter any MVS or JES2 command after the OCMD command, on the same line.

To display MVS/JES2 command output or MVS console output,

n Enter an MVS console ID after the CONS statement. Blanks after CONS indicate the master console.

n Replace 10 after the LINE statement with the number of console output bottom lines to display.

When issuing MVS or JES2 commands,

n OMEGAMON II will issue the command that you supply following the OCMD statement.

n OMEGAMON II has the same MVS console authority as the console you indicate.

n Omit the console ID to specify the master console.

n You may specify the console ID which is the UCMID (internal MVS identifier) of the console on which the MVS response displays.

n To see the console number for each of your MVS consoles, issue the D CONSOLES command at a real MVS console.

For example, to modify CICS and display the results on console 04, the KOCMD statement looks like this:

-OCMD04 F DBDCCICS,CEMT INQUIRE TASKS

________________ ZUCON> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down =======================================================================> OPERATING SYSTEM CONSOLE DISPLAY WITH COMMAND LINE -CONS LINE20 =======================================================================-OCMD =======================================================================

Issuing Commands


Issuing CICS master terminal commandsThe Utilities menu includes an option to display or modify the following master terminal settings: active max tasks, class max tasks, runaway task interval, scan delay interval, and region exit interval. To display or modify any other master terminal settings, select the Console option (A) on the Utilities menu (fast path U.A) and enter CEMT commands as if you were issuing them at a console. To display or modify the subset of CICS master terminal settings listed above, select the Master Terminal option (L) on the Utilities menu or enter fast path U.L from any menu system panel. The following panel appears.

FIGURE 164. Display or Change CICS Master Terminal Settings Panel (U.L)

To display the current setting of a parameter, enter one of the keywords shown on the panel following the -CMT statement. The current value displays and the hyphen preceding CMT changes to >. To display the value of another setting, replace the > preceding CMT with a hyphen and enter the keyword after CMT. To modify a setting, enter the new value over the current value displayed. Or you can enter the entire statement, which includes the keyword, a comma, and the new value after -CMT. For example,

-CMT AMX,20

sets the maximum number of active tasks in CICS to 20. The comma after the keyword and the hyphen preceding CMT are required.

Note: Use this option with care. Its access should be restricted in order to insure the integrity of your CICS region.

________________ ZUCEMT> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down =======================================================================> DISPLAY or CHANGE CICS MASTER TERMINAL SETTINGS > CMT ccc,n is the syntax where:> ccc = AMX Active max task, n must be >= 2> CMX,CLASS=m Class max task, m is numeric class ID> RUN Runaway task interval> SCAN Scan delay interval> TIM Region exit interval> n = new value to be set If omitted, current value displays -CMT =======================================================================

Utilities 307

Issuing Commands

Issuing OMEGAMON II common interface commandsThis path includes an option to issue commands to the OMEGAMON II common interface. Use it only when directed by Candle Customer Support. Select the Interface option (M) on the Utilities menu or enter fast path U.M from any panel. A panel of instructions appears to guide you as shown in the following figure.

FIGURE 165. Issue Common Interface Command Panel (U.M)

This panel shows the syntax required. The CICM statement issues an MVS modifier to the common interface address space. It allows you to perform functions such as displaying common interface subtasks, starting or stopping an interface subtask, or sending a message to the MVS console. For example,

CICM DISPLAY

displays all the subtasks that are currently active in the common interface.

The CONS statement displays lines from the specified MVS console so that you can view the results of the MVS modifier to the common interface address space.

To ensure the integrity of OMEGAMON II, this option should be used with care and its access should be restricted.

________________ ZUOCCI> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down =======================================================================> ISSUE COMMON INTERFACE COMMAND > To issue a KOCCI command, replace the > preceding CICM with a hyphen and> replace DISPLAY with the required KOCCI command. >CICM DISPLAY > To display console output:> - Blanks after CONS indicate the master terminal. You may enter an MVS> console ID after CONS.> - Replace 10 after LINE with the number of lines at the bottom to display. -CONS LINE10 > If a password is required, enter /PWD on the top line. At the prompt, enter> the password. =======================================================================

Obtaining Diagnostics


Obtaining DiagnosticsThe Utilities path includes several diagnostic options which can take an OMEGAMON II snapshot of your CICS region, verify OMEGAMON II components and maintenance levels, and obtain debugging information for OMEGAMON II itself.

Taking a CICS snapshotTo help diagnose CICS problems, the Utilities menu includes the Snapshot option which takes a snapshot of key diagnostic factors in your CICS region. Select the Snapshot option (N) on the Utilities menu or enter fast path U.N from any panel. The Snapshot introductory panel appears.

FIGURE 166. CICS Snapshot Panel (U.N)

The Snapshot facility is composed of a sequence of predefined OMEGAMON II displays, similar to the realtime OMEGAMON II panels you are currently using in the menu system. This Candle-supplied sequence of displays reports on the state and content of CICS.

These panels execute without intervention. After invoking Snapshot, the next screen you see is the completion screen. There may be a short time interval between invoking Snapshot and completion. The time depends on the size and state of the CICS region being diagnosed.

The results of the snapshot appear on the screen log file. To print the screen log file, select the Profile option (P) on the main menu, then select the Logging option (H), and then select the Log Out option (D). Or you can enter fast path P.H.D from any panel.

Snapshot is a debugging aid to be used along with a CICS or MVS system dump. It is designed to facilitate your job of locating and chaining through storage.

________________ ZUSNAP> PF1 Help PF3 Back PF4 Main Menu > **************************************************************> * OMEGAMON II/CICS SNAPSHOT FACILITY *> **************************************************************> * *> * You have requested a SNAPSHOT of the CICS Region you *> * are monitoring; the results of which will immediately *> * be printed out to the OMEGAMON/CICS log file. *> * *> * The SNAPSHOT is a series of OMEGAMON for CICS/ESA screens *> * covering tasks, storage, files, and all other aspects *> * of a CICS region including problems and bottlenecks. *> * Special features include detection of VSAM conflicts, *> * enqueue lockouts, MRO/IRC and MRO/ISC overviews, full *> * details on all LSR pools, and database information. *> * *> * Press ENTER to proceed with SNAPSHOT or PF3 to cancel *> * *> * *> ************************************************************** .SGO SNAP01

Utilities 309


Obtaining OMEGAMON II diagnosticsIn the event that OMEGAMON II experiences a problem, Customer Support may ask you to capture debugging information. OMEGAMON II diagnostics use the Snapshot facility and produce both CICS and OMEGAMON II debugging information.

To obtain OMEGAMON II diagnostics, select the Debug option (O) on the Utilities menu or enter fast path U.O from any panel. A Debug introductory panel appears.

FIGURE 167. OMEGAMON II Diagnostics Introductary Panel (U.O)

If you proceeded by pressing Enter, a banner page appears as shown in the following figure.

________________ ZUDBUG 50> PF1 Help PF3 Back PF4 Main Menu > **************************************************************> * OMEGAMON II/CICS AUTOMATIC DIAGNOSTIC FACILITY *> **************************************************************> * *> * This is the OMEGAMON/CICS automatic SNAPSHOT facility *> * which will record comprehensive details on both the *> * CICS region being monitored and OMEGAMON/CICS itself. *> * It is intended as a Candle Corporation diagnostic aid. *> * *> * The results of the SNAPSHOT will be directed straight *> * to the JES print queue without any required action on *> * your part. The resultant output does include a banner *> * page which should be “filled-in” before sending to the *> * Candle Corporation Customer Support Center. *> * *> * Press ENTER to proceed with SNAPSHOT or PF3 to cancel *> * *> * *> ************************************************************** .SGO DEBUG01



FIGURE 168. OMEGAMON II Diagnostics Banner Page Panel (U.O then Enter)

This panel collects information about your site which will appear as a banner page when the OMEGAMON II diagnostics are printed. Type the requested information in the spaces provided. Then press Enter to proceed or if you prefer to bypass the diagnostics, press PF3 to cancel and return to the Utilities menu.

This option is composed of a sequence of predefined OMEGAMON II displays, similar to the realtime OMEGAMON displays you are currently using in the menu system. These Candle-supplied displays contain everything included in the Snapshot option (fast path U.N) which reports on the target CICS region. In addition, this option also produces extensive diagnostics and statistics about the OMEGAMON II region itself.

This Debug option is designed as a service and debugging aid for Candle Customer Support, to reduce the time taken to resolve problems with either CICS or OMEGAMON II.

The complete sequence of the Snapshot and Debug displays execute without any intervention on your part. After invoking Debug, the next panel you see is the completion panel. There will be a short time interval between invoking Debug and completing the process. The time period depends largely on the size and state of the CICS region being diagnosed.

.SGO KOCOMEG00 > ******************************************************************> Please enter the following customer information requested before> sending the Diagnostic Screen Output to !Candle Customer Support:> ****************************************************************** > NAME:________________________ TITLE:_____________________________ > COMPANY AND ADDRESS:_____________________ TEL:___________________ > __________________________________________________________________ > __________________________________________________________________ > CANDLE PROBLEM NUMBER (IF YOU HAVE BEEN ASSIGNED ONE):____________ > CICS PUT LEVEL:______________ MVS PUT LEVEL:____________________ > DESCRIPTION OF PROBLEM AND OTHER VENDOR PRODUCTS INSTALLED: > __________________________________________________________________ > __________________________________________________________________ > __________________________________________________________________ > __________________________________________________________________ > __________________________________________________________________

Utilities 311


These diagnostics appear directly on the JES print queue. Collect the printed output. Enter the information required on the leading banner page. Mail the diagnostics to Candle, with any accompanying documentation requested by Customer Support.

Verifying OMEGAMON II componentsThis option lets you verify the status of and, if necessary, enable major OMEGAMON II components. You may use this option to verify OMEGAMON II after installation. You can use this option at any time to verify and enable components, as an alternative to selecting individual options on the Control Options menu (main menu option O). If you are experiencing a problem, Customer Support may ask you to use this option and may walk through the data displayed with you.

The Verify display takes several panels. These panels consist of questions about whether each major component is available, followed by a display of the component’s status, followed by the model of a statement you can use to start the component.

Select the Verify option (P) on the Utilities menu or enter fast path U.P from any panel. The first of several verification panels (depending on the status of your system) appears as shown in the following figure.



FIGURE 169. Verify OMEGAMON II Components Panel - Part 1 (U.P)

Press PF8 to scroll to the next panel which appears as shown in the following figure.

________________ ZUVER VTM $CICSTOR V520/I SYSA 02/03/99 17:54:06> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down ===============================================================================> VERIFY OMEGAMON COMPONENTS > Is the CICS exit for OMEGAMON enabled? EXIT+ Exit Entry Program Global Global Exit EPB+ Name Name Name Address Length Status Address+ -------- -------- -------- -------- -------- -------- --------+ XTCIN CAS ........ 00000000 0 Ena Stop 0064C2C0+ XTCOUT CAS ........ 00000000 0 Ena Stop 0064C300+ XTCATT CAS ........ 00000000 0 Ena Stop 0064C340+ XTCTIN CAS ........ 00000000 0 Ena Stop 0064C380+ XTCTOUT CAS ........ 00000000 0 Ena Stop 0064C3C0+ XKCREQ CAS ........ 00000000 0 Ena Stop 0064C400+ XFCREQ CAS ........ 00000000 0 Ena Stop 0064C440+ XFCIN CAS ........ 00000000 0 Ena Stop 0064C480+ XFCOUT CAS ........ 00000000 0 Ena Stop 0064C4C0+ XFCINC CAS ........ 00000000 0 Ena Stop 0064C500+ XDBINIT CAS ........ 00000000 0 Ena Stop 0064C540+ XDBIN CAS ........ 00000000 0 Ena Stop 0064C580+ XDBFERR CAS ........ 00000000 0 Ena Stop 0064C5C0+ XDBDERR CAS ........ 00000000 0 Ena Stop 0064C600+ XGMTEXT CAS ........ 00000000 0 Ena Stop 0064C640+ XMNOUT GLUEEXIT KOCOME00 00207724 392 Ena Act 002076E0+ XRCINIT CAS ........ 00000000 0 Ena Stop 0064C680+ XRCINPT CAS ........ 00000000 0 Ena Stop 0064C6C0+ XRCFCER CAS ........ 00000000 0 Ena Stop 0064C700+ XRCOPER CAS ........ 00000000 0 Ena Stop 0064C740+ XICREQ CAS ........ 00000000 0 Ena Stop 0064C780+ XICEXP CAS ........ 00000000 0 Ena Stop 0064C7C0+ XISLCLQ CAS ........ 00000000 0 Ena Stop 0064C800+ XJCWR CAS ........ 00000000 0 Ena Stop 0064C840+ XPCFTCH CAS ........ 00000000 0 Ena Stop 0064C880+ XPCABND CAS ........ 00000000 0 Ena Stop 0064C8C0+ XTDREQ CAS ........ 00000000 0 Ena Stop 0064C900+ XTDIN CAS ........ 00000000 0 Ena Stop 0064C940+ XTDOUT CAS ........ 00000000 0 Ena Stop 0064C980+ XTSREQ CAS ........ 00000000 0 Ena Stop 0064C9C0+ XTSIN CAS ........ 00000000 0 Ena Stop 0064CA00+ XTSOUT CAS ........ 00000000 0 Ena Stop 0064CA40

Utilities 313



Press PF8 to scroll forward again to the last verify panel as shown in the following figure. The row of equal signs (=) indicates the bottom of the data.

________________ ZUVER VTM $CICSTOR V520/I SYSA 02/03/99 17:54:06 42+ XZCIN CAS ........ 00000000 0 Ena Stop 0064CA80+ XZCOUT CAS ........ 00000000 0 Ena Stop 0064CAC0+ XZCATT CAS ........ 00000000 0 Ena Stop 0064CB00+ XZCOUT1 CAS ........ 00000000 0 Ena Stop 0064CB40+ XXRSTAT CAS ........ 00000000 0 Ena Stop 0064CB80+ XXDFA CAS ........ 00000000 0 Ena Stop 0064CBC0+ XXDFB CAS ........ 00000000 0 Ena Stop 0064CC00+ XXDTO CAS ........ 00000000 0 Ena Stop 0064CC40+ XDLIPRE CAS ........ 00000000 0 Ena Stop 0064CC80+ XDLIPOST CAS ........ 00000000 0 Ena Stop 0064CCC0+ XFCSREQ CAS ........ 00000000 0 Ena Stop 0064CD00+ XEIIN CAS ........ 00000000 0 Ena Stop 0064CD40+ XEIOUT GLUEEXIT KOCOME00 00207724 392 Ena Act 002076E0+ XALTENF CAS ........ 00000000 0 Ena Stop 0064CD80+ XICTENF CAS ........ 00000000 0 Ena Stop 0064CDC0>------------------------------------------------------------------------------> Is bottleneck analysis available? DEX+ Bottleneck Analysis Control Information+ Status . . . . . . . . : Active+ Start time . . . . . . : 13:14:43 Start date . . . . . . : 02/03/99+ Short term interval . . : 10 MN Long term interval . . : 30 MN+ Cycle timer . . . . . . : 2.0 SEC Display threshold . . . : 10%+ Short term elapsed time : 8:39 MN Long term elapsed time : 18:40 MN+ Short term cycles . . . : 260 Long term cycles . . . : 560> To start the bottleneck analysis collector, remove the > before DEX below:>DEX START>------------------------------------------------------------------------------> Is the response time monitor available? RTA+ RTA Control Information+ Status . . . . . . . . : Active+ Start time . . . . . . : 13:14:43 Start date . . . . . . : 02/03/99+ Moving time slot scale : 0.2 Moving time slot window : 10> To activate the response time monitor, remove the > before RTA below:>RTA START>------------------------------------------------------------------------------> Is the interval record collector available? INTR+ Interval Recording Control Information+ Status . . . . . . . . : Active+ Activation time . . . . : 13:14:42 Activation date . . . . : 02/03/99




These panels show whether the following major components are enabled:

n CICS global and task related user exits

n bottleneck analysis

n response time monitor

n automatic response time collector

n online historical transaction viewing

If the OMEGAMON II program is not enabled as an exit, then the response time monitor, the automatic response time collector, and online historical transaction data viewing are unavailable. Check your PLT, PCT, and PPT entries, and check that the OMEGAMON II modules are in the DFHRPL concatenation in your CICS JCL. Also, look for any error message at CICS startup.

If the CICS exit is available, you can activate bottleneck analysis, the response time monitor, the automatic response time collector, or online historical transaction data viewing. To enable a component, remove the > preceding the START statement that follows the component’s status and press Enter.

________________ ZUVER VTM $CICSTOR V520/I SYSA 02/03/99 17:54:06 84+ Initialize performed . : Yes Last function performed : Report+ Reason for termination : n/a SMFID . . . . . . . . . : 255+ Depth of analysis . . . : 50 Records since activate : 1118+ Last record time . . . : 17:54:02 Records since initialize: 1118> To start the interval record collector, remove the > before INTR below> (the bottleneck analysis and response time monitor must first be> active):>INTR START>------------------------------------------------------------------------------> Is online historical transaction viewing available? ONDV STATUS+ ONDV Control Information+ Status . . . . . . . . : Active Data store wraparound . : 13+ Start time . . . . . . : 13:14:45 Start date . . . . . . : 02/03/99+ Data store type . . . . : Dataspac Display requests . . . : 0+ Data store size . . . . : 956K Xmem posts . . . . . . : 250+ Data store size (recs) : 940 Cycle time (seconds) . : 2+ Records received . . . : 12535++ Function Elapsed CPU Paging+ Time Time+ -------- -------- -------- --------+ Initial 0.022 0.001 0+ Collect 12.032 0.904 316+ Display 0.000 0.000 0+ Wait 4:39:05 n/a n/a> To start historical viewing, remove the > before ONDV below:>ONDV START===============================================================================

Utilities 315


Verifying OMEGAMON II maintenance levelsThe Utilities path also includes an option to display current release levels, OMEGAMON II maintenance information, and RMF settings. To view this information as shown in the following figure, select the Maintenance option (Q) on the Utilities menu or enter fast path U.Q from any panel.

FIGURE 172. Current OMEGAMON II Maintenance Panel (U.Q)

The upper portion of this panel shows current release levels of CICS and the operating system, CPU serial numbers, and OMEGAMON II maintenance. The OMEGAMON II maintenance information is for use by Candle Customer Support. The bottom portion of the panel shows RMF version and version code, the current interval length, and the cycle time.

________________ ZUMAINT VTM $CICSTOR V520/I SYSA 02/03/99 17:55:56> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down ===============================================================================> CURRENT OMEGAMON MAINTENANCE APPLIED .ZAP+ Product Code:+ Base = 01-000000-00000-00+ Product = 01-000000-00000-00++ MVS: SP4.2.2 CPU: 9021 #023237+ MVS: SP4.2.0 CPU: 9021 #123237+ CICS: 3.2.1 Global suffix: ‘ ‘+ Assembled with BASE V300, Executing with BASE V300+ CANDLE Profile version V102 last modified on 01/05/93++ Maintenance Applied by Component:+ BASE Version 300, level 00 - component identifier “OB”+ PTF - BASE QOB3004 BMSG QOB3001 CMDV QOB3003 DEV QOB3010+ DSPC QOB3008 EXCD QOB3001 ICMD QOB3007 ICM3 QOB3002+ INIT QOB3009 INT QOB3008 INTX QOB3008 INT1 QOB3008+ PDEV QOB3008 PEEK QOB3008 PPRF QOB3010 SHAR QOB3009+ SRBD QOB3002 SUB QOB3002 SUBE QOB3008 SUB1 QOB3008+ SUB2 QOB3009 SUB4 QOB3008 TERM QOB3003 UPFI QOB3001+ XMZP QOB3002++ PRODUCT Version 100, level 00 - component identifier “OC”+ Regular - no zaps applied+ Special - no zaps applied+++ OBVTAM Version 300, level 00 - component identifier “OB”+ PTF - VDRV QOB3008 VEXI QOB3008 VGET QOB3008 VINI QOB3008+ VLOG QOB3008 VPUT QOB3008 VTER QOB3008 VUTL QOB3008 .RMF >> RMF Monitor I active <<+ The RMF version code is 421F; RMF version 4.2.1+ Current Interval Length: 14:58 MN Cycle Time: 1000 ms===============================================================================

Viewing and Modifying Storage


Viewing and Modifying StorageCommon interface private area, operating system common area, CICS, and dataspace storage are accessible through OMEGAMON II. For each of these storage types, the following options are available:

n List the storage beginning at a specified location.

n Scan for a specified string within the storage.

n Verify and modify (zap) the contents of a specified location.

Common interface or common area storageCommon interface storage is OMEGAMON II storage. Use the following options for common interface storage only as directed by Customer Support.

You can also use these options to view or modify the contents of the operating system common area, which includes the: Common Storage Area (CSA), System Queue Area (SQA), and nucleus.

To display common interface private area or operating system common area storage, select the OMEGAMON II Display option (B) on the Utilities menu or enter fast path U.B from any panel. The following panel appears.

FIGURE 173. Display OMEGAMON II or Common Area Storage Panel (U.B)

This panel describes the required syntax. Enter the parameters, as shown in the model, following the -MLST statement. You must specify the type of display format, the starting address of the storage, and the amount of storage in hexadecimal bytes that you want to display.

The addr field is very flexible. OMEGAMON II allows the field to be calculated using a small set of operators and address variables. It is similar to the syntax used by the TSO TEST command. See Figure 177 on page 319 for instructions on calculating the addr field.

To scan for a specified string within the common interface private area or the operating system common area, select the OMEGAMON II Scan option (C) on the Utilities menu or enter fast path U.C from any panel. The following panel appears.

_______________ ZUMLST> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down =======================================================================> DISPLAY OMEGAMON OR COMMON AREA STORAGE >MLSTc addr,dlen is the syntax where:> c = Display format: Blank=dump, C=character, X=hex.> addr = Starting address of memory to display> dlen = Display length (1 to 8 hex digits). -MLST =======================================================================

Utilities 317


FIGURE 174. Scan OMEGAMON II or Common Area Storage Panel (U.C)

This panel shows the required syntax and instructions for supplying necessary parameters. Enter the information required, as shown in the model, following the -MSCN statement. You must specify the type of display format, the starting storage address, the hexadecimal or character string for which you want to search, the amount of storage to scan, and the number of bytes to display when the string is found.

To modify the common interface private area or the operating system common area, select the OMEGAMON II Zap option (D) on the Utilities menu or enter fast path U.D from any panel. A panel appears as shown in the following figure.

Note: Modify OMEGAMON II storage only if instructed by Candle Customer Support. Modify common area storage with care.

FIGURE 175. Modify OMEGAMON II or Common Area Storage Panel (U.D)

________________ ZUMSCN> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down =======================================================================> SCAN OMEGAMON OR COMMON AREA STORAGE >MSCNc addr,string,slen,dlen is the syntax where:> c = Display format: Blank (dump), C (character), or X (hex).> addr = Starting address of memory to scan.> string = Scan comparison string in hex or character. Surround character> string in quotes.> slen = Hex length of memory (1 to 8 hex bytes) to scan (default is> 256 or x’100’).> dlen = Number of bytes (1 to 8 hex bytes) to display (default is> 16 or x’10’). -MSCNB =======================================================================

________________ ZUMZAP> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down =======================================================================> MODIFY OMEGAMON OR COMMON AREA STORAGE >MZAP addr,ver,rep is the syntax where:> addr = Starting address of memory to modify.> ver = Current hexadecimal value to verify.> rep = Replacement value in hexadecimal.> Ver and rep lengths must match. -MZAP =======================================================================



This panel displays the required syntax. Follow the instructions for entering the necessary parameters. As shown in the model, enter the required information following the -MZAP statement. You must specify the beginning storage address of the memory to modify, the current hexadecimal value in that location for verification, and the hexadecimal value which should replace the current verified value. You can modify up to 32 bytes of storage at a time. The verify and replacement strings must be the same length.

If the common area storage that you modify resides in the Pageable Link Pack Area (PLPA), OMEGAMON II automatically does a long-term page fix to ensure that the storage remains modified. In this case, the message PAGE(S) FIXED appears.

CICS storageYou can display or modify CICS storage within any CICS region on the same Central Electronic Complex (CEC) as the currently monitored CICS. To list CICS storage, select the CICS Display option (E) on the Utilities menu or enter fast path U.E from any panel. The following panel appears.

FIGURE 176. Display CICS Storage Panel (U.E)

This panel displays the required syntax and an example. Enter the required information, as shown in the model, after the -XMLS statement. You must specify the type of display format, the CICS region jobname ($ indicates the currently monitored CICS), the starting address of storage, and the amount of storage in hexadecimal bytes that you want to display.

Note: The maximum number of bytes that you can display with the XMLS command is x’1000’, or decimal 4096.

The addr field is very flexible. OMEGAMON II allows the field to be calculated using a small set of operators and address variables. It is similar to the syntax used by the TSO TEST command. See Figure 177 on page 319 for instructions on calculating the addr field. OMEGAMON II provides a limited set of named virtual storage addresses: ASCB, CSA, DLP,

________________ ZUXMLS> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down =======================================================================> DISPLAY CICS ADDRESS SPACE STORAGE >XMLSc jobname,addr,dlen is the syntax where:> c = Display format: Blank=dump, C=character, H=hex.> jobname = Enter $ for the currently monitored CICS region.> addr = Starting address of memory to display.> dlen = Length of data to display. -XMLSB > For example:> To display 32 bytes of storage in TDOCS01 at location 123456 <XMLS $,123456,20 =======================================================================

Utilities 319


OPFL, and TCB. These names are equated to their virtual storage locations. They may be used as reference points in determining an address to be zapped.

OMEGAMON II also allows you to create your own named addresses. To do this, use the MDEF command on the Display CICS Address Space Storage panel. The syntax of the MDEF command is described in the following figure.

FIGURE 177. Sample MDEF Command

You can also press F1 to view the help panel. The MDEF command and its syntax display.

To scan for a specified string within CICS storage, select the CICS Scan option (F) on the Utilities menu or enter fast path U.F from any panel. The following panel appears.

FIGURE 178. Scan CICS Storage Panel (U.F)

MDEF addr,name addr Address calculation to be assigned. It should start with a hex value or an already defined MDEF string. Operators are allowed based on that value: + Add the following value to the current pointer. - Subtract the following value from the current pointer. % Fullword at the current pointer is a 24-bit, indirect address to replace the current pointer. ? Fullword at the current pointer is a 31-bit, indirect address to replace the current pointer. name The name to be associated with the addr string. EXAMPLES: MDEF 10%,CVT Define CVT via location 16.MDEF CVT%+4%,TCB OMEGAMON II’s current TCB.MDEF TCB%,RB OMEGAMON II’s current RB via current TCB.

________________ ZUXMSC> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down =======================================================================> SCAN CICS ADDRESS SPACE STORAGE >XMSCc jobname,addr,string,slen,dlen is the syntax where:> c = Display format: Blank=dump, C=character, X=hex.> jobname = Enter $ for the currently monitored CICS region.> addr = Starting address of memory to scan.> string = Scan comparison string in hex or character.> Surround a character string with single quotes.> slen = Hex scan length (default is 256 or x’100’).> dlen = Hex display length (default is 16 or x’10’). -XMSC =======================================================================



This panel shows the required syntax. Enter the information required, as shown in the model, following the -XMSC statement. You must specify the type of display format, the CICS region jobname ($ indicates the currently monitored region, the starting storage address, the hexadecimal or character string for which you want to search, the amount of storage to scan, and the number of bytes to display when the string is found.

To modify CICS storage, select the CICS Zap option (G) on the Utilities menu or enter fast path U.G from any panel. The Modify CICS Storage panel appears as shown in the following figure.

Note: Perform this option with care in order to ensure the integrity of your CICS system.

FIGURE 179. Modify CICS Storage Panel (U.G)

This panel displays the required syntax. Follow the instructions for entering the necessary parameters. As shown in the model, enter the information following the -XMZP statement. You must specify the jobname of the CICS region ($ indicates the currently monitored region), the beginning storage address of the memory to modify, the current hexadecimal value in that location for verification, and the hexadecimal value which should replace the current verified value.

Dataspace storageA dataspace is an operating system address space, apart from a CICS or OMEGAMON II address space. It is not a job and is used solely for storage of data.

To display dataspace storage associated with any CICS region within the same CEC as the currently monitored CICS, select the Dataspace Display option (H) on the Utilities menu or enter fast path U.H from any panel. The following panel appears.

________________ ZUXZAP> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down =======================================================================> MODIFY CICS ADDRESS SPACE STORAGE >XMZP jobname,addr,ver,rep is the syntax where:> jobname = Enter $ for the currently monitored CICS region.> addr = Starting address of memory to modify.> ver = Current value in hex to verify.> rep = Replacement value in hex.> The lengths of ver and rep must match. -XMZP =======================================================================

Utilities 321


FIGURE 180. Display Dataspace Storage Panel (U.H)

This panel displays the required syntax and an example. Enter the required information, as shown in the model, after the -SLST statement. You must specify the type of display format, the CICS region jobname ($ indicates the currently monitored CICS), the dataspace name, the starting address of storage, and the amount of storage in hexadecimal bytes that you want to display.

To scan for a specified string within dataspace storage associated with any CICS region within the same CEC as the currently monitored CICS, select the Dataspace Scan option (I) on the Utilities menu or enter fast path U.I from any panel. A panel displays as shown in the following figure.

FIGURE 181. Scan Dataspace Storage Panel (U.I)

________________ ZUSLST> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down =======================================================================> DISPLAY DATASPACE STORAGE >SLSTc jobname,spacename,addr,dlen is the syntax where:> c = Display format: Blank=dump, C=character, or X=hex.> jobname = Use $ for the currently monitored CICS region.> spacename = Dataspace name.> addr = Starting address of memory to display.> dlen = Display length (1 to 8 hex digits, default is 16 (x’10’).> 16 (x’10’). -SLST =======================================================================

________________ ZUSSCN> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down =======================================================================> SCAN DATASPACE STORAGE >SSCNc jobname,spacename,addr,string,slen,dlen is the syntax where:> c = Display format: Blank=dump, C=character, or X=hex.> jobname = Use $ for the currently monitored CICS region.> spacename= Dataspace name.> addr = Starting address of memory to scan.> string = Scan comparison string in hex or character. Surround a> character string with single quotes.> slen = Scan length in hex (default is 256 or x’100’).> dlen = Display length in hex (default is 16 or x’10’). -SSCN =======================================================================



This panel shows the required syntax. Enter the information required, as shown in the model, after the -SSCN statement. You must specify the type of display format, the CICS region jobname ($ indicates the currently monitored region), the dataspace name, the starting storage address, the hexadecimal or character string for which you want to search, the amount of storage to scan, and the number of bytes to display when the string is found.

To modify dataspace storage associated with any CICS region on the same CEC as the currently monitored CICS, select the Dataspace Zap option (J) on the Utilities menu or enter fast path U.J from any panel. A panel displays as shown in the following figure.

Note: Perform this option with care in order to insure the integrity of the data stored in the dataspace.

FIGURE 182. Modify Dataspace Storage Panel (U.J)

This panel displays the required syntax. Follow the instructions for entering the necessary parameters. As shown in the model, enter the required information following the -SZAP statement. You must specify the jobname of the CICS region ($ indicates the currently monitored region), the dataspace name, the beginning storage address of the memory to modify, the current hexadecimal value in that location for verification, and the hexadecimal value which should replace the current verified value.

You can list dataspaces associated with any CICS region on the same CEC as the currently monitored CICS as well as dataspaces associated with the common interface. Select the Dataspace List option (K) on the Utilities menu or enter fast path U.K from any panel. The following panel appears.

________________ ZUSZAP> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down =======================================================================> MODIFY DATASPACE STORAGE >SZAP jobname,spacename,addr,ver,rep is the syntax where:> jobname = Enter $ for the currently monitored CICS region.> spacename = Dataspace name.> addr = Starting address of memory to scan.> ver = Current value to be verify in hexadecimal.> rep = Replacement value in hexadecimal,> The lengths of ver and rep must match. -SZAP =======================================================================

Utilities 323


FIGURE 183. List Dataspaces Panel (U.K)

This panel lists the dataspaces associated with the CICS region being monitored, followed by the dataspaces associated with the OMEGAMON II common interface. For each dataspace, this panel shows:

To list dataspaces associated with another CICS region, replace the current CICS jobname with the new CICS jobname and press Enter.

Name Name of the dataspace.

Type Type of storage which may be:

Basic Central, expanded, or disk storage.

Cache Central or expanded storage.

Owning Task Name of the task that created the dataspace followed by the address of the TCB for the creating task.

Current Size Current amount of storage used by the dataspace.

Maximum Size Maximum amount of storage allocated for the dataspace.

________________ ZUDSPC VTM TDOCS01 V520/C SYSG 02/03/99 9:55:53> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down ===============================================================================> LIST DATASPACES > Dataspaces associated with the CICS job: PEEK TDOCS01 ASID=169 >> OB8112: Data Collection Initiated << data Name Type Owning Task Current Size Maximum Size+ 00000VHS Cache DFHSIP (006FF450) 60K 60K+ 00001VHS Cache DFHSIP (006FF450) 80K 80K+ 00002VHS Cache DFHSIP (006FF450) 120K 120K+ 00003VHS Cache DFHSIP (006FF450) 120K 120K+ 00004VHS Cache DFHSIP (006FF450) 60K 60K+ 00005VHS Cache DFHSIP (006FF450) 80K 80K+ 00006VHS Cache DFHSIP (006FF450) 120K 120K+ 00007VHS Cache DFHSIP (006FF450) 120K 120K > Dataspaces associated with the common interface: PEEK TDOCS33 ASID=184, collected at 9:55:57 data Name Type Owning Task Current Size Maximum Size+ OMDATA00 Basic OMCICS (006DA968) 24K 24K+ OMDATA01 Basic OMCICS (006EC7C0) 24K 24K+ OMDATA02 Basic OMCICS (006C9E88) 24K 24K+ OMDATA03 Basic OMCICS (006D2CA8) 24K 24K===============================================================================



Group Definition and Activation 325

Group Definition and Activation

Chapter OverviewThis chapter describes the dynamic method of defining, modifying, and activating groups and their associated response time thresholds. For instructions on permanently changing the group and element definitions, see the OMEGAMON II for CICS Customization Guide.

Chapter ContentsBackground . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .326Stopping and Starting the Response Time Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327Group Definition Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .328Element Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329Default Group Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .330Group Definition Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .331

Summarizing groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .331Displaying elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .331Creating groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .332Adding elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334Updating groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .335Updating elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .336Deleting elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .337Clearing groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .338Listing group types and elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .339

17

Background


BackgroundThe OMEGAMON II response time monitoring and bottleneck analysis features collect and analyze data based on groups of like elements. These elements may be transactions, programs, VTAM Logical Units (LUs), or terminals. OMEGAMON II helps you organize the information you see on bottleneck analysis and response time displays by letting you define groups and assign resources (elements) to them. In fact, in order to obtain response time data on an element, it must be defined and it must belong to at least one monitoring group. Elements in your region that are not defined in a group, will not appear on response time displays. The primary bottleneck analysis display does not depend on groups, but the bottleneck analysis by group displays (fast paths B.C and B.D) do require predefined groups.

You can define groups of like elements using two methods: permanent and dynamic.

The permanent method allows you to change the system defaults and define groups that are available every time OMEGAMON II starts monitoring. To accomplish this, you change the group and element definitions in the Global Data Area module. After making the changes, you reassemble the module. In order to access the newly assembled global module, you must recycle the Common Interface to get a new copy into the address space.

The dynamic method of defining groups is performed through the Groups path. To start on the Groups path, select the Groups option (G) on the main menu or enter fast path G. from any panel. The changes made on this path remain in effect until OMEGAMON II is recycled and while the CICS region(s) being monitored are running. Even if you switch monitoring through an overview product (OMEGAVIEW) or through the REGIONS option (W) on the main menu, the dynamic group changes remain in effect while OMEGAMON II and the CICS region(s) are up.

Since dynamic changes are designed to be short-term, you should plan on using them when investigating current problems. For example, if your facility recently installed a new line that is experiencing problems, you can add a logical unit group and analyze its host and network response times.


Stopping and Starting the Response Time Data Collector

Stopping and Starting the Response Time Data CollectorBefore dynamically changing group definitions, you must turn off the response time data collector. Stopping response time monitoring also stops the interval record collector. Select the Control Options option (O) on the main menu and then select the RTA Off option (B) or enter fast path O.B from any panel.

After you finish changing your group and element definitions, restart the response time collectors to begin gathering response time data by selecting the RTA On option (A) on the Control Options path or enter fast path O.A from any panel. Restarting response time monitoring also restarts the interval record collector. For more information on the interval record collector and reporter see, OMEGAMON II for CICS Historical Reporting Guide.

Group Definition Limits


Group Definition LimitsKeep in mind the following group definition limits for a CICS region:

n You can define a total of up to 30 groups.

n Each group can contain one or more element names, such as a CICS transaction ID or terminal ID.

n All the elements in a group must be of the same resource type.

n A maximum aggregate of 2000 elements across all groups can be defined.

n The same element can appear in multiple groups.


Element Names

Element NamesFor CICS transactions, programs and terminals you can use a specific or generic name. A generic name is one or more characters followed by an asterisk (*). For example, a program element of TST* specifies all programs starting with TST. Generic names are not valid for VTAM LU groups.

When you define specific element names to a group, you will be able to see individual response times for each element. For example, if you define transactions ABCA, ABCB, and ABCD, you will be able to see individual response times for each of these three transaction IDs. However, when you define generic element names (using the wildcard character *), you will only see average response times for all the elements meeting the generic specification. For example, the transaction element ABC* can only show an average response time for the transaction IDs starting with ABC.

Default Group Definitions


Default Group DefinitionsIf no group definition changes were made to the Global Data Area module, by default, OMEGAMON II uses the first letter of the transactions in the PCT to assign all transactions to transaction groups 1–26. Thus, transaction IDs beginning with A are assigned to Group 01 (TRAN=A*), those beginning with B are assigned to Group 02 (TRAN=B*), those beginning with C are assigned to Group 03 (TRAN=C*), and so on.


Group Definition Panels

Group Definition PanelsThe following panels enable you to view, create, update, and delete monitoring groups and their elements.

Summarizing groupsTo view a list of the groups that are presently in use, select the Groups option (G) on the main menu or enter fast path G. from any panel. This is the first panel on the Groups path. The Group Summary panel appears as shown in the following figure.

FIGURE 184. Group Summary Panel (G.)

The Group Summary panel identifies each group by its number, resource type (transaction, program, terminal or LU), and name. The average threshold for each group refers to the response time threshold used by the interval record reporter for all elements within the group. The far right column lists the number of elements belonging to each group.

Displaying elementsTo view the elements within a group, position the cursor on a group line in the Group Summary panel and press PF11. This produces a Group Detail Information panel as shown in the following figure.

________________ ZGSUMM VTM TDOCS01 V520/C SYSG 02/03/99 10:00:52> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom > A-Group Summary B-Create Group C-Add Element D-Update Group> E-Update Element F-Delete Element G-Clear Group H-List Group===============================================================================> GROUP SUMMARY GRPS Number of groups : 4 Group Group Group Average Current Number Type Name Threshld Elements -------- -------- ------------ -------- -------- 01 Tran BUDGET 1.5 5 02 Prog MAIL1 1.8 12 03 LU LA LOG UNITS 5.0 44 04 Term LOS ANGELES 2.0 44 ===============================================================================



FIGURE 185. Group Detail Information Panel (Accessed by Zoom)

This panel lists each element ID in the selected group. OMEGAMON II uses the response time threshold for each element to highlight those elements exceeding the threshold on response time displays.

If a group contains VTAM LUs, thresholds are defined separately for host and network response time. Otherwise, n/a (not applicable) is displayed.

Creating groupsTo be monitored, elements must be contained in at least one group. To create a group, select the Create Group option (B) on the Groups path or enter fast path G.B from any panel. This produces a panel to create a group and specify its attributes as shown in the following figure.

FIGURE 186. Create Group Panel (G.B)

________________ ZZGRPS VTM TDOCS01 V520/C SYSG 02/03/99 10:00:52> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down PF11 Zoom ===============================================================================> GROUP DETAIL INFORMATION GRPS GROUP=01+ Elements: 1 Skipped: 0+ BUDGET Group Details+ Element Tran Host Network Response+ Number ID Threshld Threshld Threshld+ -------- -------- -------- -------- --------+ 001 DDF4 n/a n/a 3.5+ 002 DDC4 n/a n/a 3.0+ 003 VBBG n/a n/a 3.0+ 004 AA21 n/a n/a 1.0+ 005 SA21 n/a n/a 2.0 ===============================================================================

________________ ZGADDG VTM TDOCS01 V520/C SYSG 02/03/99 10:00:52> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-Group Summary B-Create Group C-Add Element D-Update Group> E-Update Element F-Delete Element G-Clear Group H-List Group=======================================================================> CREATE GROUP > To create a group, modify the GRPS statement below as follows:> - Remove the > preceding GRPS> - group may be 1 - 30> - name may be a 1 - 12 character group name (default is ‘GROUP nn’)> - type may be TRAN, TERM, PROG, or LU> - n.n is the group average response time threshold (default is 2.0 seconds) >GRPS ADD,GROUP=group,NAME=name,TYPE=type,AVERAGE=n.n=======================================================================



Remember to stop the response time collector (fast path O.B) prior to using this panel and any other panels that add or change group or element definitions. Reactivate the collector after you are finished (fast path O.A).

Text on this panel explains how to define a new group. Enter the group number, a name for easy identification, the type of resource this group will contain, and the average response time for the elements within the group.

1. Begin by moving the cursor to the line containing the GRPS statement.

2. Remove the greater-than symbol (>) preceding GRPS.

3. Modify the group definition (GRPS) statement.

4. Follow the syntax shown in the figure and these guidelines:n Use group numbers from 1–30.

n The group name is for informational purposes. It appears on certain displays to facilitate identification of a group’s contents.

n The group type must be defined as either a transaction, terminal, program or LU group. All elements in the group must be of the type defined.

n The average response time threshold is used to activate the interval record collector and highlight elements that exceed the threshold.

For example, to create group number 30 as a transaction group for the new Payroll application with an average CICS response time threshold of 1.2 seconds, the GRPS statement looks like this:

GRPS ADD,GROUP=30,NAME=’PAYROLL’,TYPE=TRAN,AVERAGE=1.2

To create group 27 as an LU group for line 15 with an average end-to-end response time of 1.8 seconds, the GRPS statement looks like this:

GRPS ADD,GROUP=27,NAME=’LINE 15’,TYPE=LU,AVERAGE=1.8

When transaction, programs, or terminals or monitored, OMEGAMON II obtains CICS response time. When LUs are monitored, OMEGAMON II uses the End-to-End Response Time Feature to obtain host, network, and ETE response times. Refer to the OMEGAMON II for CICS Configuration and Customization Guide and the End-to-End Response Time Feature (ETE) Reference Manual for additional information about end-to-end response time.



Adding elementsTo be monitored, an element must be defined and contained within a group. To define new elements for an existing group, select the Add Element option (C) on the Groups path or enter fast path G.C from any panel. The elements you define must correspond with the group TYPE definition. You can define the same element in multiple groups. A panel to add one or more elements to a group appears as shown in the following figure.

FIGURE 187. Add Elements to Group Panel (G.C)

Follow the instructions on this panel to modify the GRPS ADD statement. Enter the group number. An asterisk (*) specifies all groups. Also supply the element (resource) type (TRAN, PROG, TERM, or LU), the element ID, and the appropriate response time threshold(s). If you add an LU group, you specify end-to-end response time for the RESP parameter, which is a total of host and network response time. Otherwise, the RESP parameter refers to CICS response time. Also, if it is an LU group, you must specify individual response times for the host and network components of ETE response time. Otherwise, HOST and NET do not apply.

For example, to add transaction ID SA21 to Group 01, with a response time threshold of 3.5 seconds, modify the GRPS statement on the last line of the display to look like this:

GRPS ADD,GROUP=1,TRAN=SA21,RESP=3.5

________________ ZGADDE VTM TDOCS01 V520/C SYSG 02/03/99 10:00:52> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-Group Summary B-Create Group C-Add Element D-Update Group> E-Update Element F-Delete Element G-Clear Group H-List Group=============================================================================> ADD ELEMENT(S) TO GROUP > To add element(s) to a group, modify GRPS below as follows:> - Remove the > preceding GRPS> - group may be 1 - 30 or * for all groups> - elem must be TRAN, PROG, TERM, or LU> - cccc may be trans ID, terminal ID, program name, or logical unit> - Resp is the response time threshold in seconds. It is ETE response time,> if elements are logical units. The default is 1 second.> - Host is the host response time threshold for logical units (default 1).> - Net is the network response time threshold for logical units (default 1). >GRPS ADD,GROUP=group,elem=(cccc,cccc....),RESP=nnn,HOST=nnn,NET=nnn=============================================================================



Updating groupsTo modify the group name, group type, or average response time threshold for the group as a whole, select the Update Group option (D) on the Groups path or enter fast path G.D from any panel. A panel for updating group attributes appears as shown in the following figure.

FIGURE 188. Update Group Panel (G.D)

Follow the instructions on this panel to modify the GRPS UPD statement. Enter the group number, the group name (optional), the type of elements contained in the group, and the average group response time for all elements within the group. If it is an LU group, average response time is end-to-end; otherwise it refers to CICS response time.

For example, to change the average CICS response time for transaction group 30 to 2.1 seconds, the GRPS statement looks like this:

GRPS UPD,GROUP=30,AVERAGE=2.1

If you are changing the group type, you must first delete all elements in that group. To do so, select the Clear Group option (G) on the Groups path.

________________ ZGUPDG VTM TDOCS01 V520/C SYSG 02/03/99 10:00:52> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-Group Summary B-Create Group C-Add Element D-Update Group> E-Update Element F-Delete Element G-Clear Group H-List Group=============================================================================> UPDATE GROUP > To update a group, modify the GRPS statement below as follows:> - Remove the > preceding GRPS> - group may be 1 - 30> - name may be a 1 - 12 character group name> - type may be TRAN, TERM, PROG, or LU> - n.n is the group average response time threshold in seconds >GRPS UPD,GROUP=group,NAME=element,TYPE=type,AVERAGE=n.n=============================================================================



Updating elementsTo update the response time thresholds for individual elements within a group, select the Update Element option (E) on the Groups path or enter fast path G.E from any panel. A panel for updating the attributes of an element in one or more groups appears as shown in the following figure.

FIGURE 189. Update Elements in Group Panel (G.E)

Follow the instructions on this panel to modify the GRPS UPD statement. Enter the type of element, the element ID, and the applicable response time(s) for the element. RESP refers to ETE response time if the element is an LU. If the element is a transaction, program, or terminal, RESP refers to CICS response time. If the element is an LU, the host and network response time components of ETE also apply.

For example, if you want to change the network response time threshold for LU L624001 to 4 seconds, modify the GRPS UPD statement to look like this:

GRPS UPD,LU=L624001,NET=4

This change effects all groups containing LU L624001.

________________ ZGUPDE VTM TDOCS01 V520/C SYSG 02/03/99 10:00:52> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-Group Summary B-Create Group C-Add Element D-Update Group> E-Update Element F-Delete Element G-Clear Group H-List Group=============================================================================> UPDATE ELEMENT(S) IN GROUP(S) > To update element(s) in group(s), modify GRPS below as follows:> - Remove the > preceding GRPS> - elem=TRAN, PROG, TERM, or LU> - cccc may be trans ID, terminal ID, program name, or logical unit> - Resp is the response time threshold in seconds. It is ETE response time,> if elements are logical units.> - Host is the host response time threshold for logical units> - Net is the network response time threshold for logical units >GRPS UPD,elem=(cccc,cccc....),RESP=nnn,HOST=nnn,NET=nnn=============================================================================



Deleting elementsTo delete individual elements from a group, select the Delete Element option (F) on the Groups path or enter fast path G.F from any panel. A panel for deleting one or more elements from a group appears as shown in the following figure.

FIGURE 190. Delete Elements from a Group Panel (G.F)

Follow the instructions on this panel to modify the GRPS DEL statement. Enter the group number, the element type, and a list of the element IDs that you want to delete from the group (separated by commas).

For example, to delete terminals AB01, CD06, and EF12 from Group 08, modify the GRPS DEL statement to look like this:

GRPS DEL,GROUP=08,TERM=(AB01,CD06,EF12)

________________ ZGDELE VTM TDOCS01 V520/C SYSG 02/03/99 10:00:52> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-Group Summary B-Create Group C-Add Element D-Update Group> E-Update Element F-Delete Element G-Clear Group H-List Group=============================================================================> DELETE ELEMENT(S) FROM A GROUP > To delete element(s) from a group, modify GRPS below as follows:> - Remove the > preceding GRPS.> - group may be 1 - 30 or * for all groups> - elem may be TRAN, PROG, TERM, or LU> - cccc is transaction ID, program name, terminal ID, or logical unit >GRPS DEL,GROUP=group,elem=(cccc,cccc....)=============================================================================



Clearing groupsIf you want to delete all elements from a group, select the Clear Group option (G)) on the Groups path or enter fast path G.G from any panel. A panel for clearing groups appears as shown in the following figure.

FIGURE 191. Clear a Group Panel (G.G)

Follow the instructions on this panel to modify the GRPS CLR statement. Simply enter the number of the group that you want to clear out.

For example to clear out all elements of Group 12, modify the GRPS CLR statement to look like this:

GRPS CLR,GROUP=12

________________ ZGCLRG VTM TDOCS01 V520/C SYSG 02/03/99 10:00:52> Help PF1 Back PF3 Up PF7 Down PF8 OR > A-Group Summary B-Create Group C-Add Element D-Update Group> E-Update Element F-Delete Element G-Clear Group H-List Group=============================================================================> CLEAR A GROUP > To delete all elements from a group, modify GRPS below as follows:> - Remove the > preceding GRPS.> - group may be 1 - 30 >GRPS CLR,GROUP=group=============================================================================



Listing group types and elementsTo list groups of a specific type or find out which groups contain specific elements, select the List Group option (H) on the Groups path or enter fast path G.H from any panel. A panel for listing specified groups appears as shown in the following figure.

FIGURE 192. List Groups Panel (G.H)

Follow the instructions on this panel to modify the GRPS statements. To list groups of a specified element type, enter the element type (TRAN, TERM, PROG, or LU) after TYPE=. To list the groups that contain a particular element, enter the element type and the element ID.

For example, to list all terminal groups, modify the GRPS TYPE= statement to look like this:

GRPS TYPE=TERM

To list all the groups containing the transaction ID HJ14, modify the GRPS elem= statement to look like this:

GRPS TRAN=HJ14

Remember that all the updates to group definitions made through the Groups path in the menu system remain in effect only while your monitored CICS region(s) are running and for the duration of this OMEGAMON II session.

________________ ZGLIST VTM TDOCS01 V520/C SYSG 02/03/99 10:00:52> PF1 Help PF3 Back PF4 Main Menu PF7 Up PF8 Down > A-Group Summary B-Create Group C-Add Element D-Update Group> E-Update Element F-Delete Element G-Clear Group H-List Group=============================================================================> LIST GROUPS > To list groups whose elements are of a specific type, modify GRPS below:> - remove the > preceding GRPS> - type may be TRAN, TERM, PROG, or LU >GRPS TYPE=type > To list groups which contain a specific element, modify GRPS below:> - Remove the > preceding GRPS> - elem may be TRAN, TERM, PROG, or LU> - cccc may be trans ID, terminal ID, program name, or logical unit >GRPS elem=cccc=============================================================================



Menu System Fastpath Index 341

Menu System Fastpath Index

IntroductionThe menu system Fastpath Index lists CICS performance monitoring topics and directions on how to find these topics in OMEGAMON II’s menu system.

Appendix Contents

Using the Fastpath Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .342

A

Using the Fastpath Index


Using the Fastpath IndexTo use the index, locate a topic in the column labelled Topic and then follow the line across to find the fastpath that corresponds to that topic.

This index is also available online. To go to the online index, press PF1 from any menu system panel. This gives you associated help for the panel. Then press PF1 again to go to the General Help menu. From the General Help menu, select A to go to the index. Topics for A then appear. To see topics for another letter, enter that letter on the entry field. Scroll through the topics. When you find the topic you want, enter S in the entry field preceding the topic, or enter the fastpath on the INFO-line.

For advanced users who need to use commands, the online version of the fastpath index shows the corresponding command(s) for each topic listed.

A

Subject Main Menu Option Fastpath

ADABAS H - History H.A

ADABAS Statistics for a Task T - Tasks T.

Addresses, DLI D - Databases D.G

Add Element to Group G - Groups G.C

AIDs C - CICS C.A

AIDs Kill C - CICS C.B

All Clear Message P - Profile P.A.L

All Datasets Allocated to CICS F - Files F.H

All Tasks T - Tasks T.A

Another CICS Region,

Switch to

W - REGIONS W.

Application Datasets F - Files F.A

Application Domain Tasks T - Tasks T.B

Applied Maintenance U - Utilities U.Q

Automatic Screen Facility (ASF) On P - Profile P.E.F

Automatic Screen Facility (ASF) Off P - Profile P.E.G

Automatic Update Mode (AUP) On P - Profile P.F

Automatic Update Mode (AUP) Off P - Profile P.G

Averages, Response Time R - Response R.J



B

C


Blue and Other Color Settings P - Profile P.D

Bottleneck Analysis B - Bottlenecks B.B

Bottleneck Analysis Control O - Control Options O.I

Bottleneck Analysis in Overview V - Overview V.

Bottleneck Analysis Verify U - Utilities U.P

Bottleneck Analysis Wait Reasons O - Control Options O.J

Buffer Waits F - Files F.I


CEMT Functions U - Utilities U.L

CICS Control Blocks C - CICS C.

CICS Datasets F - Files F.B

CICS Dataspaces U - Utilities U.K

CICS Exception Settings P - Profile P.A.J

CICS Region Snapshot U - Utilities U.N

CICS Region Storage S - Storage S.I

CICS Shutdown Options O - Control Options O.Q

CICS Storage, List U - Utilities U.E

CICS Storage, Scan U - Utilities U.F

CICS Storage, Zap U - Utilities U.G

CICS Trace Overview C - CICS C.W

REGIONS W - REGIONS W.

Class, Tasks by T - Tasks T.F.A

Clear Group G - Groups G.G

CMAX Held Tasks T - Tasks T.F.B

CMXT Statistics C - CICS C.C

Collector, Interval Recording O - Control Option O.K

Collectors, Database O - Control Option O.P

Color Settings P - Profile P.D.A

Compressions, Storage S - Storage S.J



D

Common Interface Command U - Utilities U.M

Common Interface Data Spaces U - Utilities U.K

Common Interface Storage, List U - Utilities U.B

Common Interface Storage, Scan U - Utilities U.C

Common Interface Storage, Zap U - Utilities U.D

Concurrent TCB Dispatchable Queue T - Tasks T.F.C

Console Command U - Utilities U.A

Control Blocks, CICS C - CICS C.

Control Blocks, MVS M - MVS M.

Control Options for OMEGAMON II P - Profile P.B.B

Control Tables, CICS C - CICS C.

Create Group G - Groups G.B

CSA C - CICS C.C


Daily Overview, CICS Response R - Response R.G

Daily Overview, ETE Response R - Response R.H

Daily Overview, Group Response R - Response R.I

DASD I - I/O I.A

DASD Degradation I - I/O I.B

DASD Exceeding Thresholds I - I/O I.B

DASD Detail I - I/O I.D

DASD Plot I - I/O I.E

DASD Statistics I - I/O I.A

DASD Users I - I/O I.C

Database Collectors O - Control Options O.P

Database Directory C - CICS C.F

Database Exception Settings P - Profile P.A.A

Databases, DLI D - Databases D.D

Datasets, All Allocated to CICS F - Files F.H

Datasets, Application F - Files F.A

Datasets, CICS F - Files F.B




Datasets, DFHRPL F - Files F.G

Datasets, IMS F - Files F.K

Datasets, JES F - Files F.D

Datasets, Journal F - Files F.J

Datasets, Select F - Files F.L

Datasets, STEPLIB F - Files F.C

Datasets, VSAM F - Files F.E

Dataspaces, CICS U - Utilities U.K

Dataspaces, Common Interface U - Utilities U.K

Data Space Storage, List U - Utilities U.H

Data Space Storage, Scan U - Utilities U.I

Data Space Storage, Zap U - Utilities U.J

Data Tables C - CICS C.K

Date Format P - Profile P.B

DBCTL D - Databases D.H

DBCTL Tasks T - Tasks T.F.D

DBDs C - CICS C.F

DB2 D - Databases D.A

DDIR C - CICS C.F

Debug OMEGAMON II U - Utilities U.O

Delete Group G - Groups G.G

Delete Group Element G - Groups G.F

Delete Profile, Install P - Profile P.C.F

Delete Profile, User P - Profile P.C.D

Destinations, Transient Data C - CICS C.D

DFHRPL Datasets F - Files F.G

Display CICS Storage U - Utilities U.E

Display Common Interface Storage U - Utilities U.B

Display Data Space Storage U - Utilities U.H

Display Options P - Profile P.B.A

DLI D - Databases D.B

DLI Databases D - Databases D.D

DLI Definition D - Databases D.C




E

DLI History H - History H.A

DLI Tasks T - Tasks T.F.D

DLI Tuning Information D - Databases D.B

DSA S - Storage S.D

DTA Address, Task with T - Tasks T.F.E

Dump Component C - CICS C.H


ECBs, DLI D - Databases D.F

EDSA Page Allocation Map S - Storage S.G

EDSA Statistics S - Storage S.E

ETE Response, All LUs R - Response R.K

ETE Response, Current R - Response R.L

ETE Response, Exceeded R - Response R.M

Enqueue Resources Bottlenecks B.H

Enqueues Bottlenecks B.H

Enqueues in Overview V - Overview V.

Environment, CICS M - MVS M.B

Environment Graph, CICS M - MVS M.A

European Date Format P - Profile P.B.A

Exception Logging Facility (XLF) On P - Profile P.E.D

Exception Logging Facility (XLF) Off P - Profile P.E.E

Exceptions, Current E - Exceptions E.A

Exceptions in Overview V - Overview V.

Exceptions, Summary this Session E - Exceptions E.B

Exception, Setting P - Profile P.A

Exit Program Blocks (EPBs) C - CICS C.I

Exit (Global Exit Programs) C - CICS C.I

Exit Verify, OMEGAMON II in CICS U - Utilities U.P

Extended Color P - Profile P.D.B

Extended Recovery Facility Status C - CICS C.J




F

G


Facility ID, Tasks by T - Tasks T.F.G

Facility Type, Tasks by T - Tasks T.F.H

FCT C - CICS C.K

Files, All Allocated to CICS F - Files F.H

Files, Application F - Files F.A

Files, CICS F - Files F.B

Files, DFHRPL F - Files F.G

Files, IMS F - Files F.K

Files, JES F - Files F.D

Files, Journal F - Files F.J

Files, Select F - Files F.L

Files, STEPLIB F - Files F.C

Files, VSAM F - Files F.E

Fold (Uppercase OMEGAMON II Display) P - Profile P.B.A

Fold (Uppercase Screen Log Print) P - Profile P.H.A


Green and Other Color Settings P - Profile P.D

Global User Exits C - CICS C.I

Graph, Bottleneck B - Bottlenecks B.A

Graph, Group Bottleneck B - Bottlenecks B.C

Graph, Impact Analysis B - Bottlenecks B.F

Graph, Response Time Problems R - Response R.F

Graph, System M - MVS M.A

Group Response Time R - Response R.A

Groups, Impact Analysis O - Control Options O.O

Groups, Response Time G - Groups G.

Groups, Subpool S - Storage S.H



H

I


Handpostable Queue, Tasks in T - Tasks T.F.I

Hiperspace, LSR Pools F - Files F.F

Historical, Data Viewing, Verify U - Utilities U.P

History of Exceptions E - Exceptions E.B

History, ADABAS H - History H.A

History, DLI H - History H.A

History, IDMS H - History H.A

History Off O - Control Options O.G

History On O - Control Options O.F

History Select H - History H.B

History Status O - Control Options O.H

History, Transaction H - History H.A

History, VSAM H - History H.A


ICEs C - CICS C.L

ICEs Kill C - CICS C.M

IDMS H - History H.A

IDMS Statistics for a Task T - Tasks T.

Impact Analysis Activation O - Control Options O.L

Impact Analysis Deactivation O - Control Options O.M

Impact Analysis Groups B - Control Options O.O

Impact Analysis Long-Term Interval O - Control Options O.N

Impact Analysis Sampling Interval O - Control Options O.N

Impact Analysis Severity Threshold O - Control Options O.N

Impact Analysis Short-Term Interval O - Control Options O.N

Impact Analysis Timeout Interval O - Control Options O.N

Impact Analysis Workload B - Bottlenecks B.E

Impact Analysis Workload Detail B - Bottlenecks B.G

Impact Analysis Workload Profile B - Bottlenecks B.F



J

K

IMS Datasets F - Files F.K

Install Profile, Delete P - Profile P.C.F

Install Profile, Save P - Profile P.C.E

Interval Recording Control O - Control Options O.K

Intervals, Set End-to-End Display O - Control Options O.D

Intervals, Set Response Time O - Control Options O.D

I/O, DASD Allocation and Users I - I/O I.C

I/O, DASD Degradation I - I/O I.B

I/O, DASD Detail I - I/O I.D

I/O, DASD Plot I - I/O I.E

I/O, DASD Statistics I - I/O I.A

I/O Exception Settings P - Profile P.A.B

ISC/MRO, AIDs C - CICS C.A

ISC/MRO, AIDs C - CICS C.V


JCT C - CICS C.N

JES Datasets F - Files F.D

Journal Datasets F - Files F.J.D

Journal Tasks T - Tasks T.F.J

Journals C - CICS C.N


Kill AIDs C - CICS C.B

Kill ICEs C - CICS C.M

Kill Task T - Tasks T.G




L

M


Last Dispatched Task T - Tasks T.F.K

Libraries, DFHRPL F - Files F.G

Libraries, STEPLIB F - Files F.C

List CICS Data Spaces U - Utilities U.K

List CICS Storage U - Utilities U.E

List Common Interface Data Spaces U - Utilities U.K

List Data Space Storage U - Utilities U.H

List Group G - Groups G.H

List OMEGAMON II Storage U - Utilities U.B

List Profiles P - Profile P.C

Log Off P - Profile P.H.C

Log Off and Log On to other CICS W - REGIONS W.

Log On P - Profile P.H.B

Log Out P - Profile P.H.D

Log Printer/Routing Options P - Profile P.H.A

Logical Unit Response Times R - Response R.E

LSR Buffer Waits F - Files F.I

LSR Pools F - Files F.F


Maintenance Applied U - Utilities U.Q

Master Queue, Tasks in T - Tasks T.B

MAXR Exception Setting P - Profile P.A.K

MAXR Limit Setting P - Profile P.A.K

MAXR, Tasks Exceeding Limit T - Tasks T.D

MAXTASK Queue, Tasks in T - Tasks T.F.L

Modules M - MVS M.E

Monitor another CICS region W - REGIONS W.

MRO Bottlenecks B - Bottlenecks B.B

MRO Exception Display E - Exceptions E.A



N

O

MRO Tasks T - Tasks T.

MRO/ISC AIDS C - CICS C.A

MRO/ISC TCT Entries C - CICS C.V

MVS Console Command U - Utilities U.A

MVS Control Blocks M - MVS M.

MVS Subpools M - MVS M.F


New Queue, Tasks in T - Tasks T.F.M

Non-executable Queue, Tasks in T - Tasks T.F.O

Non-Journal Tasks T - Tasks T.F.N

Number, Task by T - Tasks T.F.P


Occupancy, Historical Task H - History H.

Occupancy, Task T - Task T.

OMEGAMON II Exception Settings P - Profile P.A.E

OMEGAMON II Performance Options P - Profile P.B.C

OMEGAMON II Storage, List U - Utilities U.B

OMEGAMON II Storage, Scan U - Utilities U.C

OMEGAMON II Storage, Zap U - Utilities U.D

Online Data Viewing H - History H.A

Online Data Viewing, Verify U - Utilities U.P

Overview, CICS Trace C - CICS C.W

Overview, Response Time R - Response R.A

Overview Performance, Bottlenecks V - Overview V.

Overview Performance, Enqueues V - Overview V.

Overview Performance, Exceptions V - Overview V.

Overview Performance, Tasks V - Overview V.




P

Q


Pink and Other Color Settings P - Profile P.D

Page Allocation Map, DSA S - Storage S.F

Page Allocation Map, EDSA S - Storage S.G

PCT C - CICS C.X

PDIR C - CICS C.G

Performance Options, OMEGAMON II P - Profile P.B.C

Performance Overview, Bottlenecks V - Overview V.

Performance Overview, Engueues V - Overview V.

Performance Overview, Exceptions V - Overview V.

Performance Overview, Response V - Overview V.

Performance Overview, Tasks V - Overview V.

Pools, LSR F - Files F.F

PPT C - CICS C.Q

Problems, Response Time R - Response R.F

Profile Maintenance, Install P - Profile P.C.E

Profile Maintenance, User P - Profile P.C.C

Program Check/Abend Trace Table C - CICS C.W

Program Response Times R - Response R.D

Programs C - CICS C.Q

PSBs C - CICS C.G

PSW and Registers M - MVS M.C


Quasi-Re-entrant Queue,

Tasks in

T - Tasks T.F.Q

Queues, Tasks in various T - Tasks T.F

Queues, Temporary Storage C - CICS C.U

Queues, Transient Data C - CICS C.D



R

S


Rate, Transaction T - Tasks T.H

Recent Response Times, Averages R - Response R.J

Recording Interval O - Control Options O.K

Red and Other Color Settings P - Profile P.D

Region Snapshot U - Utilities U.N

Region Storage S - Storage S.I

Registers and PSW M - MVS M.C

Resource-owning Queue,

Tasks in

T - Tasks T.F.S

Resources, Enqueue B - Bottlenecks B.H

Response Time Collector O - Control Options O.K

Response Times, Averages R - Response R.K

Response Times, End-to-End R - Response R.K

Response Times, Group R - Response R.A

Response Times, Transaction R - Response R.B

Response Times, Terminal R - Response R.C

Response Times, Program R - Response R.D

Response Times, Logical Unit R - Response R.E

Response Time in Overview V - Overview V.

Response Time Problems Graph R - Response R.F

Resume Queue, Tasks in T - Tasks T.F.R

RMF Version, Interval, Cycle U - Utilities U.Q

Response Time Monitor Start O - Control Options O.A

Response Time Monitor Stop O - Control Options O.B

Response Time Monitor Status O - Control Options O.C

Response Time Monitor Verify U - Utilities U.P


Save Profile, Install P - Profile P.C.E

Save Profile, User P - Profile P.C.C

Scale, Set Response Time Display O - Control Options O.E



Scan CICS Storage U - Utilities U.F

Scan Data Space Storage U - Utilities U.I

Scan OMEGAMON II Storage U - Utilities U.C

Select Datasets F - Files F.L

Shutdown Options, CICS O - Control Options O.Q

SIT C - CICS C.R

SMDSA Wait Reason T - Tasks T.A

SMEDSA Wait Reason T - Tasks T.A

Snapshot of CICS Region U - Utilities U.N

SOS, Tasks Held T - Tasks T.F.T

Storage, CICS S - Storage S.

Storage, CICS Region S - Storage S.I

Storage Compressions S - Storage S.J

Storage, MVS Subpools M - MVS M.F

Storage, Task S - Storage S.C

Storage Exception Settings P - Profile P.A.G

Storage Violations S - Storage S.B

String Waits F - Files F.I

Subpool Groups S - Storage S.H

Subpools, DLI D - Databases D.E

Subpools, MVS M - MVS M.F

Summary, DLI D - Databases D.B

Summary, Exceptions E - Exceptions E.B

Summary, Group G - Groups G.A

Summary, LSR F - Files F.F

Summary, Storage S - Storage S.A

Switch Monitoring to another CICS W - REGIONS W.

System Exception Settings P - Profile P.A.F

System Graph M - MVS M.A

System Summary M - MVS M.B




T


Turquoise and Other Color Settings P - Profile P.D

Tables, Data C - CICS C.K

Task Analysis T - Tasks T.

Task Analysis in Overview V - Overview V.

Task Exception Settings P - Profile P.A.C

Task Statistics, DLI T - Tasks T.

Task Statistics, VSAM T - Tasks T.

Task Storage S - Storage S.C

Tasks Waiting for Enqueues B - Bottlenecks B.H

TCB Structure M - MVS M.D

TCT C - CICS C.V

TCT Prefix C - CICS C.S

TD/TS Exception Settings P - Profile P.A.H

Temporary Storage Queues C - CICS C.U

Temporary Storage Usage C - CICS C.T

Terminal Exception Settings P - Profile P.A.D

Terminal Response Times R - Response R.C

Terminals C - CICS C.V

Terminal, Tasks by T - Tasks T.F.V

Textware Last Updated U - Utilities U.Q

Timed Screen Facility (TSF) Entry P - Profile P.E.A

Timed Screen Facility (TSF) Off P - Profile P.E.C

Timed Screen Facility (TSF) On P - Profile P.E.B

Time Slots, Response, CICS R - Response R.G

Time Slots, Response, End-to-End R - Response R.H

Time Slots, Response,

Single Group

R - Response R.I

Today’s CICS Response Times R - Response R.G

Today’s End-to-End Response Times R - Response R.H

Today’s Group Response Times R - Response R.I

Token, Tasks with T - Tasks T.F.W

TQE, Task with T - Tasks T.F.X



U

V

Trace Overview, CICS C - CICS C.W

Transactions C - CICS C.X

Transaction Class Statistics C - CICS C.C

Transaction Rate T - Tasks T.H

Transaction Response Times R - Response R.B

Transaction, Tasks by T - Tasks T.F.Y

Transient Data Queues C - CICS C.D

Transient Data Usage C - CICS C.Y


Umbrella Transaction, Tasks by T - Tasks T.F.ZZ

Update Group G - Groups G.D

Update Group Element G - Groups G.E

User Exits C - CICS C.I

User Exits C - CICS C.J

User Profile, Delete P - Profile P.C.D

User Profile, Save P - Profile P.C.C

User Profile Facility P - Profile P.

Userid, Tasks by T - Tasks T.F.Z


Verify Bottleneck Analysis U - Utilities U.P

Verify CICS Exit for OMEGAMON II U - Utilities U.P

Verify Historical Reporting U - Utilities U.P

Verify Interval Recording U - Utilities U.P

Verify Response Time Monitor U - Utilities U.P

Violations, Storage S - Storage S.B

VSAM Datasets F - Files F.E

VSAM Exception Settings P - Profile P.A.I

VSAM History H - History H.A




W

X

Y

VSAM String Waits F - Files F.I

VSAM Task Statistics T - Tasks T.


Waiting Enqueues B - Bottlenecks B.H

Waiting Tasks T - Tasks T.C

Wait Reason Control O - Control Options O.J

Wait Reasons, Bottlenecks B - Bottlenecks B.B

Wait Reasons, Tasks T - Tasks T.

Waits, VSAM String F - Files F.I

White and Other Color Setting P - Profile P.D

Window, Set Response Time Display O - Control Options O.E

Workload Impact, CICS B - Bottlenecks B.E

Workload Impact, CICS, Detail B - Bottlenecks B.G

Workload Impact, CICS, Profile B - Bottlenecks B.F


XLF Off P - Profile P.E.E

XLF On P - Profile P.E.D

XLF Printer/Routing Options P - Profile P.H.E

XLF Printer, Activate P - Profile P.H.E

XRF Status C - CICS C.J


Yellow and Other Color Settings P - Profile P.D

Yellow Warning Condition Various Displays




Z


Zap CICS Storage U - Utilities U.G

Zap Data Space Storage U - Utilities U.J

Zap OMEGAMON II Storage U - Utilities U.D

Zaps Applied U - Utilities U.Q

Guide to Candle Customer Support 359

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360– 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364– Assigned Support Center Representative (ASCR)– Maintenance Assessment Services (MAS)– Multi-Services Manager (MSM)

Customer Support Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . 365– Link to Worldwide Support Telephone and E-mail information

B

Base Maintenance Plan



OverviewCandle offers a comprehensive Base Maintenance Plan to ensure that you realize the greatest value possible from your Candle software investments. We have more than 200 technicians providing support worldwide, committed to being responsive and to providing expedient resolutions to support requests. Technicians are available worldwide at all times during the local business day. In the event of an after-hours or weekend emergency, our computerized call management and forwarding system will ensure that a technician responds to Severity One situations within one hour. For customers outside of North America, after-hours and weekend support is provided in English language only by Candle Customer Support technicians located in the United States.

Telephone supportCandle provides consistently reliable levels of service—thanks to our worldwide support network of dedicated experts trained for specific products and operating systems. You will always work with a professional who truly understands your problem.

We use an online interactive problem management system to log and track all customer-reported support requests. We give your support request immediate attention by routing the issue to the appropriate technical resource, regardless of geographic location.

Level 0 Support is where your call to Candle Customer Support is first handled. Your support request is recorded in our problem management system, then transferred to the appropriate Level 1 support team. We provide Level 0 manual interaction with our customers because we support more than 170 products. We feel our customers would prefer personal interaction to a complex VRU or IVR selection menu.

Level 1 Support is the service provided for initial support requests. Our Level 1 team offers problem determination assistance, problem analysis, problem resolutions, installation assistance, and preventative and corrective service information. They also provide product usage assistance.

Level 2 Support is engaged if Level 1 cannot provide a resolution to your problem. Our Level 2 technicians are equipped to analyze and reproduce errors or to determine that an error is not reproducible. Problems that cannot be resolved by Level 2 are escalated to Candle’s Level 3 R&D support team.

Level 3 Support is engaged if a problem is identified in Candle product code. At Level 3, efforts are made to provide error correction, circumvention or notification that a correction or circumvention is not available. Level 3 support provides available maintenance modifications and maintenance delivery to correct appropriate documentation or product code errors.

eSupportIn order to facilitate the support process, Candle also provides eSupport, an electronic full-service information and customer support facility, via the World Wide Web at www.candle.com/support/. eSupport allows you to open a new service request and update

http://www.candle.com/support/



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.

Candle has established the following service-level objectives:

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.

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

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.



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.

Call Status Severity 1 Goal

Severity 2 Goal

Severity 3 Goal

Severity 4 Goal

Severity 5Goal

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.



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.

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 supportn eSupport using the World Wide Webn Regularly scheduled product updates and maintenance provided at no additional chargen 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


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 367

Symbols$VSMXCYC macro 81.IATH 165.SCC 85.task analysis (Menu) 70

AA 273abends

40D 18880A 188after task termination 106bottleneck analysis task 75code 120transaction 75

ADABAS 99, 125address space

storagemap 193

ADI operand 249Adobe portable document format 19AIDs 32alerts 53alerts (Menu) 53

response time 63AMAXT 70AMAXTASKS 70AMXP exception 70AMXT

exception 70ASCR

assigned support center representative 364ASF 40assigned support center representative

ASCR 364ATI 240attribute parameter 85autoinstall 266, 271automatic

diagnostic facility 309automatic initiate descriptors (Menu) 32

exception 70automatic screen facility (ASF) 40automatic transaction initiation (ATI) 240, 273, 281

auxiliarycontrol area address 268trace destination 277

average response time 62, 297, 298

Bbasic mapping support 233BDAM 250, 252bell 40BMS 233bottleneck analysis (Menu) 32, 51, 75, 135, 135–

152collection 136, 146customization 136group definition 326operational considerations 145restarting 75sampling 136wait reasons 136

box parameters 86

CCA split

area split 81CAVM 249CDEV 298CEMT 105, 107CICM statement 307CICS 167CICS analysis (Menu) 32, 229

automatic initiate descriptors (Menu) 233availability manager 249BDAM 252Common System Area (CSA) 236control tables 232datatable 253destination control table 238dumps 246exits 247FORCE option 107global user exit facility 54kill 107monitoring facility 54owning system 233program management 261remote file 253

Index


shutdown option 284snapshot 308storage 318token 100trace 276transient data 281VSAM 252

CICS analysis (Menu)monitor control table (MCT) 54

class max tasksactive 70

CML locks 160CMXP exception 70CMXT exception 70collector abend 75color 41, 85

workload impact profile 161commands (Menu) 40

CICS master terminal 306common interface 307console 305EXEC level 111

common interface (CI) 316commands 307storage 316subtasks 307

Common System Area (CSA) 236concurrent TCB (CO) 291CONS statement 307contention

CPU 160enqueue 160graphic display 161holding CML lock 160I/O 160mount pending 160resource 154SRM delay 160

controlarea split 88, 208, 267, 281blocks 32, 229CA split 81interval byte map 268interval split 88, 267, 281storage subpool 169tables 229, 232

Control Optionspage locations for 29

Control Options (Menu) 28CPHI exception 70CPLO exception 70

CPU (Menu)dispatching waits 154global threshold 69utilization 70, 77

CSA 236CSLT 57current free OSCOR 174cushion size 174, 178customer service

telephone support 360customer support

base maintenance plan 360contact information 365enhanced support services 364eSupport 360severity levels 361

cycle parameters 87

DD CONSOLES command 305DASD (Menu)

devices not responding 72dropped ready 72plot 302response time 295statistics 295

data management block 242attributes 242pool utilization 72stopped or failed 72

database analysis 33, 215–227DB2 215directory 222DLI 215, 219, 242locally defined 222statistics 216

DATACOMstatistics 126

datasetsselecting 200

dataspace 188i2.storage 320

datatables 250date 40DB

monitor 71DB2 (Menu) 215–218

attach 71DB21 exception 71DB22 exception 71DB2A exception 71DB2M exception 71

Index 369

DB2T exception 71DB2W exception 71DBCTL (Menu) 227

database 128DBD 128, 222DBM monitor 221DBMN exception 71DBON exception 71DBUP exception 71DCB

open 299, 301DCT 238, 281DDIR 222, 226, 242

suffix 221summary display 242

debug 75, 79, 308, 309dedicated

mode 31terminal 50

defaultsettings

changing response time 53defining groups

dynamic method 326permanent method 326

degradation 149destination

intrapartition 80destination control table 238–240, 281device

activity 302address 300busy 300detail 300file list 300I/O 301not ready (Nrdy) 300reserve count 301reserved (Resv) 300statistics 296type 302unit address 299user 300utilization 297, 298

DFHRPL datasets 205DFSVSAMP 224diagnostics 308dispatchable tasks 300dispatching

algorithm 289

priority 72, 289display parameters 84DL/I (Menu) 71, 215, 219–226, 227, 231

addresses 226data management block directory 242databases 222DBCTL 227event control blocks 225statistics 99, 125, 128subpools 224threads 72

DLCL exception 72DLDB exception 72DLTH exception 72DLXCPVR 221DMB 72DMBP exception 72DNRS exception 72DPLT statement 302DPRO exception 72DRDY exception 72dropped ready 72

tape device 80DSA 73DSAV exception 73DSHI exception 74DSIZ exception 74DSLO exception 74DSTO exception 74DTB 258dump (Menu)

codes 246datasets 229, 246exception 74storage violation 79system 74transaction 77

DUMP parameter 238, 242, 244, 250, 258, 261, 265, 271, 278

DXAB exception 75dynamic storage area 73, 167, 231

end address 179extended 177extents allocated 174extents in use 174largest free area 174percent allocated 178, 179size 174, 178start address 179

dynamic transaction backout 222, 258


EECB 225EDSA 177elapsed time 288elements

adding 334deleting 337displaying 331listing 339updating 336

end-to-end response time 56, 60ENQC exception 75ENQP exception 75enqueue (Menu) 149–152

analysis 51holding 160pool utilization 75resource 51

ENQW exception 75EPB 248ESAV exception 75ESHI exception 75ESIZ exception 75ESLO exception 75ESOS exception 76ESTO exception 76eSupport

customer support 360event control block 225exceeding thresholds 298exception analysis 32, 51

attribute parameter 85box parameters 86current 66customizing 83–87cycle parameters 87display parameters 84displaying 66exceptions 70global CPU threshold 69logging facility (XLF) 85recommendation screens 68threshold parameters 85VSAM analysis 88

exception anlaysiscolor settings 85

EXCP 31EXEC level command 111execute channel program 31

per second 76exit

implications to CICS 247Exit Program Blocks (EPBs) 248extended recovery facility (XRF) 82

alternate CICS 249extent 81, 88

displaying current total 81journal 259

Ffast pathing (Menu) 43, 341–358FCT 250file analysis (Menu) 33, 197–214

allocation 202application datasets 202attributes 199CA splits 208CICS 199CICS datasets 203control 124

statistics 124dataset detail 200dataset selection 200dataset types 199datasets 199detail 202detail panel 202DFHPRL datasets 205DL/I 124file control table (FCT) 202hiperspace statistics 210IMS datasets 205JES datasets 204journal datasets 205journals 199LSR pools 210, 212navigation 198statistics 124steplib datasets 204string waits 210, 214summary 199SYSIN datasets 206third-party 124type of file 204usage 202VSAM dataset 204, 207

File Control Table (FCT) 250fixed time period 57fragmentation 186function index 341, 341–358function keys (Menu) 40

Index 371

Ggeneral help 44general purpose registers 291generic name 201GET

records 268requests 282

globaldata area 63, 69, 111, 112, 113, 145, 326exit program 247resource limit 69startup parameters 264user exit 247

GLUEs 247graphic contention display 161group

bottlenecks 138group definition 325–339

clearing 338creating 332defaults 330elements 329limits 328listing 339LUs 332updating 335

GROUPS option 61GRPS

CLR statement 338DEL statement 337statement 333TYPE statement 339UPD statement 335, 336

GRSP exception 76GTF trace destination 277

Hheartbeat interval 249help 44hiperspace

statistics 210horizontal menu 37

II/O

contention 159on paging string 78

DASD 72, 297number 300queue 301

depth 300rate 76

tape device request 80trace 276waits 154

IACL 164IACS 164IANC 164IANL 159, 161, 163, 165IAST 163IBPOOL 224ICEs 32ICV (CICS exit interval) 82ID

= parameter 238, 242, 250, 258, 261, 271, 278group

response time 53POOL 71

IDMSstatistics 126

impact analysis 33, 153–165buckets 164collection parameters 154, 156, 163contention 157, 158, 160display parameters 156, 163enqueue types 159execution states 154groups 164I/O devices 159interval description area 157plot threshold 156productivity analysis 157profile display 161response time 161sampling interval 156, 163severity threshold 165sources 158starting and stopping 155synchronization 163time-out facility 164workload impact profile 161

IMS datasets 205IMS lock trace 221INAB exception 76index

component split 81object 81option 45

indirectqueue 240

INFO-line 39, 40input area, INFO-line 40interest profile 248internal trace destination 277intersystem communication 233


intervalactivity 32control 233record collector 76, 327

interval control element (Menu) 32, 255–257exception 76

intrapartitiondestination 80

IOHI exception 76IRLM address space 75ISAM pools 224ISB pool 226ISC/IRC attach header 100ISPF mode 30ISUBPL 224

JJCJS exception 76JCT 258JES

commands 305datasets 204

JESDI operand 249jobname 40journal (Menu) 258

control table 258datasets 205valid WTOR response 76waiting for response 76

Kkey fields 41KEY= parameter 170, 176kill

AID 235ICE 257task 105

KOCMD statement 305

Lload modules 293Local Shared Resources (Menu) 251

pools 78, 210, 212log abend information 75logging status 40logical units 326

defining groups 61response time 59, 60

LSQA 169exception 76storage 191

LSR 251LU 326

Mmain menu 35

options 341–358maintenance assessment service

MAS 364maintenance verify 315MAS

maintenance assessment service 364master terminal settings 306maximum tasks active 70MAXP exception 77MAXR exception 77MAXT exception 77MAXTASKS 236

option 77menu system

colors 41interface 35selecting options from 43

MLST statement 316modes of operation 40module trace 221monitor control table 54moving time

period 58slot 60

MRO/ISC (Menu) 100links 78

MSCN statement 317MSM

multi-services manager 364multi-services manager

MSM 364MVS

commands 305console message 307effect on CICS 153wait for resource 154

MVS analysis 33, 285–293common area 188CPU utilization 286modules 293MVS analysis 188paging utilization 286, 288program status word 291storage management 167, 188subpools 189system initialization time 288TCB 291

Index 373

time in transaction 289total CPU time 288total SRB time 288total TCB time 288

MXT analysis 77MZAP statement 318

Nnavigation

menu system 36, 43NDMP exception 77network response time 56

changing threshold 336news option 45nondispatchable tasks 300nonresident program 78NOPURGE option 284NOSPACE 282

OOMEGAVIEW 30ONDV 117, 131OPER option 284operator

command 305OSAM 224, 251OSCH exception 77OSCL exception 77OSCOR 75, 169

amount free 174area 77fragmentation 77largest free 174requested 173SIT parameter 169size 187

OSCOR requested field 173overview panels 47, 51

Ppage

-ins 78size 178

page allocation map 179, 181, 231PAGE exception 78paging (Menu) 78, 188

delays 160PAM 179PCRT exception 78PCT 278

PDIR 226, 244suffix 221summary 244

performancecurrent system status 50overview panel 50

performance monitoringdedicated terminal 50options 341–358switching regions 48

PF keys 43PI enqueue pool utilization 75PPT 261printing problems 19processing program table (PPT) 261product ID 40program

compression 78, 186management 261nonresident 78response time 53specification block 72, 244status word (PSW) 291storage subpool 169

program control table 278storage violation 79

PSB 72PSBP exception 78PST

active 243pool 226

PURGE option 284purge tasks at shutdown 284PUT

records 268requests 282

PUTQ records 268

Qquasi-reentrant (QR) 291queue 269

RRATE statement 109RCT 71RDO 231READ ONLY-key storage 170real storage 191recommendation screens 68recovery

forward 258


regionattached to DB2 71currently available 48summary panel 48switching 48

regions display 48remote delete request 233RENTRSM keyword 170resource 150resource definition online (RDO) 231, 232, 278resources (Menu)

contention 154, 157limiting 111-owning (RO) 291

response time 53response time (Menu)

analysis 32, 53changing settings 63collector 327, 333color highlighting 58conversation 54DASD 295data collection settings 63definition 54degradation 76, 82End-to-End feature (ETE) 56fixed time period 57group definition 326groups 76I/O time 54ID groups 53, 58impact analysis 161intervals 53, 63LU 59, 61moving time period 58network 56period 57, 63programs 53terminals 53threshold, changing 336thresholds 53, 61, 63time scale 63transactions 53VTAM LU 53

RMF 315RMTH exception 78RMTT exception 78RPC storage subpool 169

Sscreen

format 39

space 40stacking 40

scrolling 40SDMP exception 78SEL= parameter 238, 242, 244, 250, 258, 262,

265, 271, 278severity levels

customer support 361shared storage subpool 169Short-on-Storage 82short-on-storage 73, 75, 76, 174, 178, 186, 236shutdown CICS 284Sign On panel

menu system interface 30SIT 70SLST statement 321snapshot of CICS 308SOS 73splits

control area 267, 281control interval 267, 281

SRHm exceptions 78SRLM exception 78SRTm exceptions 78SSCN statement 322startup parameters 264statistics

device 296DL/I 124file control 124third-party 124

statusindicators 236information 39

steplib datasets 204STIMER 154STIO exception 78STOR command 170storage (Menu)

abends 188analysis 167–195CICS 318CICS version 3.3 167, 170, 176, 181, 183, 185common interface 316current tasks suspended 178cushion 73, 74, 174, 178, 186dataspace 320DMBPL 220DSA or EDSA start/end address 179DSA size 174, 178extents allocated 174extents in use 174free 178

Index 375

freemain 184freemain requests 178getmain 180, 184getmain requests 178global 180HWM tasks suspended 178insufficient 174key types 170KEY= parameter 176largest free area 174LWM free space 178main 169management 167, 169modify 316MVS 188MVS subpools 189OSCOR 169, 173, 174over-allocation 74page size 178paging 188paging (Menu) 188PAM 179, 231percent DSA allocated 178, 179private area 169program compression 186program specification block location 245protection 170, 191PSBPL 220real 191recovery option 173region 192resident programs 183shared 180short-on 73, 82, 174, 178, 186, 236statistics 179storm 195subpools 169, 178, 180, 181tasks 178, 180TCB 190, 191temporary 32, 81, 229, 267trace 276unused 174usage by task 176violation 79, 80, 173, 174virtual 167, 188, 191, 268virtual storage map 193VTAM 183working set size 188

storage analysis 33STR-derived token 100string

temporary storage 81

transient data 80, 283utilization 78waits 78, 79, 208, 210, 214

STRU exception 78STRW exception 79STRX exception 79STSPROT keyword 170subpools

CICS 169groups 183MVS 188storage 180, 181, 183

usage 188SUPRA statistics 127suspended channel program 300suspended tasks 174, 178SVSY exception 79SVTK exception 79SVTR exception 79, 80switching

journal 259regions 48

SYSID indicator 278SYSIN datasets 206system

dump 246ID, on INFO-line 40start date 288

system initialization table (CUA) 70system initialization table (Menu) 70, 75

AMXT parameter 70parameters 75, 77, 264XRF related operands 249

System Management Facility (SMF)records 133

SZAP statement 322

Ttable entries 32TAKEOVER operand 249tape device

dropped ready 80target working set size 290task analysis (Menu) 33, 51, 89

abend 75bottleneck analysis 75categories 102database statistics 99detail display 91dispatchable 300file control statistics 99killing 105


purge status 93purgeable 93purging tasks 284specifying maximum number 77statistics 98status 90storage 95storage subpool 169summary 89task termination abends 106termination option 89time statistics 98unit of work 100

task analysis (menu)control area 176

task control block (Menu)multiple 292storage 191structure 292

task history 117record selection 129

task-related user exits (TRUEs) 248TCA 176TCLASS 279TCT 271TCTFX

terminal control 266TDBU exception 80TDBW exception 80TDCI exception 80TDHI exception 80TDQU exception 80TDSH exception 80TDST exception 80telephone support

customer service 360temporary storage (Menu) 229, 267, 269

degradation 81percent utilization 81usage 32

terminal (Menu)dedicated 31response time 53storage violation 80transaction initiation 273

terminal control table 271–275terminal control table (Menu)

prefix 266storage violation 79

thread waits 71

threshold (Menu)CALL DL/I 111change 63

values 298database request 111DB2 111default response time settings 53exceeding 298EXEC level file control 111parameters 85resource limiting 111storage 111third-party database 111

timeinterval 63scale 63slots 57window 63, 64

time-of-day clock 82TNRS exception 80TOD clock 82TP storage subpool 169TPDR exception 80TQE flag 93trace

datasets 229destination 276

transaction (Menu)abend 75dump 77, 246MACRO level 111mirror 128OMEG INIT/SHUT 114rate 90, 109response time 53work area (TWA) 279

transient datastring wait 80usage 32

transient data (Menu) 229, 233, 238, 281ATI 281destination control table 281

TRLO exception 81TRUEs 248TSBU exception 81TSBW exception 81TSO mode 31TSPU exception 81TSSH exception 81TSST exception 81TST 267TTI 273

Index 377

UUCB 302umbrella data section 100unit

information 301UOWID 100user

averages 62exits 248journal records 258profile suffix 40TCB storage 191

user exitfacility 54

user-defined time intervals 62USER-key storage 170utilities 303–323

common interface commands 307console commands 305dataspace storage 320diagnostics 308maintenance 315master terminal commands 306snapshot 308storage 316verify components 311zaps 315

VVCAS exception 81VCIS exception 81Version 520 enhancements 23vertical menu 37VINX exception 81virtual storage 188, 191, 268VMEX exception 81volser 299volume mount status 301VSAM 252

analysis 88datasets 207extensions 81files 250summary 208

VTAM (Menu)ACB

not open 81error data 249LU 53mode 30netname 273storage 183

VTMA exception 81

Wwait

enqueue 32I/O events 32reasons 51, 137, 139, 140remote processing 144, 147resource 90short-on-storage (Menu) 32string 32VSAM buffer 32

working set size 82, 188workload impact profile 161WSHI exception 82WSLO exception 82WTOR response 76

XXACB 79XLF

XLF parameters 85XLF Parameters field 85XMLS statement 318XMSC statement 320XMZP statement 320XRFA exception 82XSOS exception 82XTOD exception 82XXRSTAT exit 249

Zzaps 315zoom

within the menu system 42


Date post:	24-Jul-2018
Category:	Documents
Upload:	nguyenkien
View:	257 times
Download:	0 times

OMEGAMON II for CICS Reference Manual, Volume 2,...

Documents