historical reporting guide -...

Historical Reporting GuideOMEGAMON II® for DB2

Version 540

G2512468000

August 2004

Candle Corporation100 North Sepulveda Blvd.

El Segundo, California 90245-9796

2 OMEGAMON II for DB2 Historical Reporting Guide, Version 540

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

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

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

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

3

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Candle Customer Service and Satisfaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Historical Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Storing Data in DB2 Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Storing Data in Sequential Datasets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Reporting Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36Accessing Historical Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Chapter 2. Online Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40Data Collection Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Chapter 3. Data Extraction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Extractor Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Data Extraction Customization Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58Data Extraction Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

Chapter 4. Data Summarization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86Data Summarization Customization Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87Data Summarization Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

Chapter 5. IFCID-Based Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104Generating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

Chapter 6. Using the Historical Reporter Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112

Table of Contents


Setting Reporter Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114Generating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119Printing Reports in Batch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135

Chapter 7. Using the Report Request Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140Report Subjects for ACCOUNTING Report Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . .147Filtering and Other Report Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169

Chapter 8. Using Other Historical Reporting Methods . . . . . . . . . . . . . . . . . . . . . . . . . . .173Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174SAS Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175COBOL and C Reporting for IFCID-based Reports . . . . . . . . . . . . . . . . . . . . . . . . . . .176QMF Sample Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177

Chapter 9. IFICD-based Accounting Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Buffer Pool Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182Group Buffer Pool Activity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184Distributed Data Facility (DDF) Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186Accounting Package Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188Lock Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191Global Lock Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193SQL Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195Package and DBRM Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198

Chapter 10. IFCID-based Statistics Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Buffer Pool Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202Address Space Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203

Chapter 11. IFCID-based DSNZPARM Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205System Installation Parameters (DSNZPARM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206

Chapter 12. Historical Reporter Accounting Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Buffer Pool Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216Group Buffer Pool Activity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220Distributed Data Facility (DDF) Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225Accounting Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232Lock Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239Global Lock Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243Resource Limit Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247Parallel Task Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251Scan Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254Sort Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258SQL Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261

5

Accounting Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268Accounting Termination Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272Time Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275Accounting Package Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280

Chapter 13. Historical Reporter Statistics Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287Buffer Pool Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288Group Buffer Pool Activity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296Command Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301CPU Time Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305 Statistics Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308EDM Pool Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316Lock Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .319 Global Lock Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .322Log Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .326 SQL Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .330 Subsystem Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .336 Statistics Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .339Bind Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .342 Distributed Data Facility (DDF) Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .346 Open/Close Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .350

Chapter 14. Historical Reporter Audit Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353Authorization Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .354Authorization Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .357Audited DDL (Data Definition Language) Access . . . . . . . . . . . . . . . . . . . . . . . . . . . .360Audited DML (Data Manipulation Language) Access . . . . . . . . . . . . . . . . . . . . . . . . .363DML (Data Manipulation Language) Statements at Bind. . . . . . . . . . . . . . . . . . . . . . .366Authorization ID Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .369Utility Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372Audit Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .375

Chapter 15. Historical Reporter DSNZPARM Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . .379Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .380System Installation Parameters (DSNZPARM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .381

Chapter 16. Historical Reporter Performance Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . .393Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .394Application Trace Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395 Application Trace Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .400Application SQL Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .414Application Event Trace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .422Application Buffer Pool Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .430Application Buffer Pool I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .433System Buffer Pool Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .438


System Buffer Pool I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .442EDM Pool I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .446Lock Suspension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .449Global Lock Suspensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .454 Lock Contention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .459P-Lock Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .467System Event Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .472Negative Application SQL Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .476

Chapter 17. Input Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .479Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .480Input Record Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .481Input Record Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .484Input Record Dump. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .486

Appendix A. Accessing OMEGAMON II Messages and the Data Dictionary . . . . . . . . . . . . 489Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .490

Appendix B. Guidelines for Sizing VSAM Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .494

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497

7

Table 1. Symbols in Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Table 2. Data Collection Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Table 3. Definitions of Data Extraction Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68Table 4. Descriptions of Data Summarization Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92Table 5. Statistics Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106Table 6. Accounting Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107Table 7. DSNZPARM Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108Table 8. Audit Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109Table 9. Statistics Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121

Table 10. Accounting Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124Table 11. Audit Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127Table 12. DSNZPARM Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128Table 13. Performance Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129Table 14. Input Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131Table 15. Graphical Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132Table 16. Historical Reporter Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135Table 17. VSAM Dataset Allocation Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .494

List of Tables

9

FIGURE 1. OMEGAMON II for DB2 ISPF Primary Options Menu. . . . . . . . . . . . . . . . . . . . . . . . . .37FIGURE 2. Historical Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37FIGURE 3. IFCID-based Reports - Accounting Buffer Pool Activity Report . . . . . . . . . . . . . . . . . .183FIGURE 4. IFCID-based Reports - Accounting Group Buffer Pool Activity Report . . . . . . . . . . . . .185FIGURE 5. IFCID-based Reports - Accounting DDF Activity Report . . . . . . . . . . . . . . . . . . . . . . .187FIGURE 6. IFCID-based Reports - Accounting Report - Time Summary . . . . . . . . . . . . . . . . . . . .190FIGURE 7. IFCID-based Reports - Accounting Lock Activity Report . . . . . . . . . . . . . . . . . . . . . . .192FIGURE 8. IFCID-based Reports - Accounting Global Lock Activity Report . . . . . . . . . . . . . . . . .194FIGURE 9. IFCID-based Reports - Accounting SQL Activity Report . . . . . . . . . . . . . . . . . . . . . . .196

FIGURE 10. IFCID-based Reports - Accounting SQL Activity Report (continued) . . . . . . . . . . . . . .197FIGURE 11. IFCID-based Reports - Accounting Report - Package and DBRM Detail . . . . . . . . . . .199FIGURE 12. IFCID-based Reports - Address Space Data Report . . . . . . . . . . . . . . . . . . . . . . . . . . .204FIGURE 13. IFCID-based Reports - DNSZPARM Report (Page 1) . . . . . . . . . . . . . . . . . . . . . . . . . .207FIGURE 14. IFCID-based Reports - DNSZPARM Report (Page 2) . . . . . . . . . . . . . . . . . . . . . . . . . .208FIGURE 15. IFCID-based Reports - DNSZPARM Report (Page 3) . . . . . . . . . . . . . . . . . . . . . . . . . .209FIGURE 16. IFCID-based Reports - DNSZPARM Report (Page 4) . . . . . . . . . . . . . . . . . . . . . . . . . .210FIGURE 17. IFCID-based Reports - DNSZPARM Report (Page 5) . . . . . . . . . . . . . . . . . . . . . . . . . .211FIGURE 18. IFCID-based Reports - DNSZPARM Report (Page 6) . . . . . . . . . . . . . . . . . . . . . . . . . .211FIGURE 19. IFCID-based Reports - DNSZPARM Report (Page 7) . . . . . . . . . . . . . . . . . . . . . . . . . .212FIGURE 20. IFCID-based Reports - DNSZPARM Report (Page 8) . . . . . . . . . . . . . . . . . . . . . . . . . .212FIGURE 21. IFCID-based Reports - DNSZPARM Report () . . . . . . . . . . . . . . . . . . . . . . . . . .213FIGURE 22. Accounting Buffer Pool Activity Report (Group by DB2ID, Planname) . . . . . . . . . . . .219FIGURE 23. Accounting Group Buffer Pool Activity (Group by None) . . . . . . . . . . . . . . . . . . . . . .224FIGURE 24. Accounting DDF Activity Report (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230FIGURE 25. Accounting DDF Activity Report (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231FIGURE 26. Accounting Detail Report (1 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235FIGURE 27. Accounting Detail Report (2 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236FIGURE 28. Accounting Detail Report (3 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237FIGURE 29. Accounting Detail Report (4 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238FIGURE 30. Accounting Lock Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242FIGURE 31. Accounting Global Lock Activity (Group by None) . . . . . . . . . . . . . . . . . . . . . . . . . . .246FIGURE 32. Accounting Resource Limit Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250FIGURE 33. Parallel Task Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253FIGURE 34. Accounting Scan Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257FIGURE 35. Accounting Sort Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260FIGURE 36. Accounting SQL Activity Report (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266FIGURE 37. Accounting SQL Activity Report (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267FIGURE 38. Accounting Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271FIGURE 39. Accounting Termination Summary Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274FIGURE 40. Accounting Time Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279

List of Figures


FIGURE 41. Accounting Package Detail Report (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284FIGURE 42. Accounting Package Detail Report (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285FIGURE 43. Statistics Buffer Pool Activity Report (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294FIGURE 44. Statistics Buffer Pool Activity Report (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .295FIGURE 45. Statistics Group Buffer Pool Activity (Group by None). . . . . . . . . . . . . . . . . . . . . . . . .300FIGURE 46. Statistics Command Activity Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .304FIGURE 47. Statistics CPU Time Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .307FIGURE 48. Statistics Detail Report (1 of 6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310FIGURE 49. Statistics Detail Report (2 of 6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311FIGURE 50. Statistics Detail Report (3 of 6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312FIGURE 51. Statistics Detail Report (4 of 6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313FIGURE 52. Statistics Detail Report (5 of 6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314FIGURE 53. Statistics Detail Report (6 of 6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315FIGURE 54. Statistics EDM Pool Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318FIGURE 55. Accounting Lock Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .321FIGURE 56. Statistics Global Lock Activity (Group by DBID, Day) . . . . . . . . . . . . . . . . . . . . . . . . .325FIGURE 57. Statistics Log Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329FIGURE 58. Statistics SQL Activity Report (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334FIGURE 59. Statistics SQL Activity Report (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .335FIGURE 60. Subsystem Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .338FIGURE 61. Statistics Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .341FIGURE 62. Bind Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .345FIGURE 63. Statistics Distributed Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .349FIGURE 64. Statistics Open/Close Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .352FIGURE 65. Authorization Failures Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .356FIGURE 66. Authorization Control Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .359FIGURE 67. Audited DDL Access Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .362FIGURE 68. Audited DML Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365FIGURE 69. DML Statements at Bind Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368FIGURE 70. Authorization ID Changes Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371FIGURE 71. Utility Access Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374FIGURE 72. Audit Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .377FIGURE 73. (Part 1 of 4). System Installation Parameters Report . . . . . . . . . . . . . . . . . . . . . . . . . .389FIGURE 74. (Part 2 of 4) System Installation Parameters Report . . . . . . . . . . . . . . . . . . . . . . . . . . .390FIGURE 75. (Part 3 of 4) System Installation Parameters Report . . . . . . . . . . . . . . . . . . . . . . . . . . .391FIGURE 76. (Part 4 of 4) System Installation Parameters Report . . . . . . . . . . . . . . . . . . . . . . . . . . .392FIGURE 77. Application Trace — Summary (Group by THREAD) Report . . . . . . . . . . . . . . . . . . .397FIGURE 78. Application Trace-Summary (Group by UNIT_OF_WORK Report. . . . . . . . . . . . . . . .398FIGURE 79. Application Trace-Summary (Group by PROGRAM) Report . . . . . . . . . . . . . . . . . . . .399FIGURE 80. (Part 1 of 3) Application Trace Detail (Group by Program) . . . . . . . . . . . . . . . . . . . . .411FIGURE 81. (Part 2 of 3) Application Trace Detail (Group by Program) . . . . . . . . . . . . . . . . . . . . .412FIGURE 82. (Part 3 of 3) Application Trace Detail (Group by Program) . . . . . . . . . . . . . . . . . . . . .413FIGURE 83. Application SQL Trace Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .421FIGURE 84. Application Trace (Events) Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .429FIGURE 85. Application Buffer Pool Access (Group by HOUR Report) . . . . . . . . . . . . . . . . . . . . . .432

11

FIGURE 86. Application Buffer Pool Report (Group by HOUR, AUTHID, PLANNAME, CONNID, CORRID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .437

FIGURE 87. System Buffer Pool Access Report (Group by HOUR) . . . . . . . . . . . . . . . . . . . . . . . . .441FIGURE 88. System Buffer Pool IO Report (Group by Hour) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .445FIGURE 89. EDM Pool Performance Report (Group by THREAD) . . . . . . . . . . . . . . . . . . . . . . . . .448FIGURE 90. Lock Suspension Report (Group by SYSID, DB2ID, Planname, Connid, Corrid,

Authid) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .453FIGURE 91. Global Lock Suspension (Group by SYSID, DB2ID, Planname, Connid, Corrid,

Authid) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .458FIGURE 92. (Part 1 of 2) Lock Contention Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .465FIGURE 93. (Part 2 of 2) Lock Contention Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .466FIGURE 94. (Part 1 of 2) Data Sharing P-Lock Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .470FIGURE 95. (Part 2 of 2) Data Sharing P-Lock Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .471FIGURE 96. System Event Trace Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .475FIGURE 97. Negative Application SQL Coded Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .478FIGURE 98. Input Record Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .483FIGURE 99. Input Record Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .485

FIGURE 100. Input Record Dump. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .487FIGURE 101. Print JCL Options Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .490FIGURE 102. Set Dataset High-Level Qualifier Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .491

13

What’s New

IntroductionThis section identifies the enhancements made to OMEGAMON II for DB2 for Version 540. These changes were made in conjunction with the OMEGAMON XE for DB2 on z/OS Version 300 release. The changes and additions in OMEGAMON II for DB2 provide new function in addition to reflecting support for features in IBM DB2 Version 8.1.

OMEGAMON II for DB2 enables you to obtain additional information about the performance of your systems. This additional information allows you more flexibility in managing various types of threads. An overview of each new or changed function follows.

Note: With this release, OMEGAMON II for DB2 no longer supports IBM DB2 Version 5.

Historical Reporter redesignSignificant enhancements were made to the historical reporting component of OMEGAMON II for DB2. Some of these new features are:

� Sequential output files are now produced from the online collector.

� All record types can be loaded into DB2 tables using either the LOAD utility or using SQL INSERT.

� Near term history collector for displays is now configured separately from long term history for reports.

� New fields have been added to the Summarizer.

New IFCID-based reports� Numerous new IFCID-based reports are provided. See “Specify IFCIDs” on page 60

for a list of the supported IFCIDs. See the README provided with this product for instructions on generating the IFCID-based reports.

� You can generate your own reports, based on the IFCIDS selected, using the product-provided COBOL, C, and SAS record layouts. All instrumentation record types (IFCIDs) are supported. The data are extracted from SMF, GTF or from the Online Collector input.

W


64-bit addressing supportVersion 8 of DB2 UDB for z/OS supports 64-bit virtual storage. The zSeries 64-bit architecture allows DB2 UDB for z/OS to move various storage areas above the 2-GB bar. OMEGAMON II for DB2 now provides the ability to display information from above the 2-GB bar structures.

64-bit addressing support applies to the:

� EDM pool

� buffer pools

� sort pools

� RID pools

Long name supportOMEGAMON II for DB2 includes support for long object names. New displays are provided in support of this feature.

Unicode supportUnicode support includes character conversion from Unicode to EBCDIC for online displays and batch reports.

Enclave supportNew displays for stored procedures using Work Load Manager (WLM) enclaves include:

� Enclave Token

� Service Class Period

� Performance Index

� Service Class

� WLM Environment Name

Stored procedure Address Spaces is being phased out in DB2 Version 8. All stored procedures now use WLM.

New filtering for Near Term History displayThese keywords are added to the Near Term History display:

� COMMIT

� CORRID

� DB2 CPU TIME

� DB2 ELAP TIME

� DEADLK/TIMEOUT

� I/O ELAP TIME

15

� GETPAGES

� LOCK ESCAL

� PACKAGE

See the OMEGAMON II for DB2 Reference Manual for descriptions of these new fields.

New DSNZPARM fieldsThe DSNZPARM Thread Parameters panel now includes numerous new fields.

Distributed Thread display improvementsThe Distributed Thread display improvements include the addition of these fields:

� Host Name

� Workstation identifier

� End user ID on workstation

� Transaction ID on workstation

17

Preface

OMEGAMON II for DB2, Version 540 is a component of OMEGAMON XE for DB2 on z/OS. This document describes the historical reporting capabilities of OMEGAMON II for DB2®. It describes the historical components of OMEGAMON II, data collection and setting data collection options, and historical reports and setting report options.

Part I: “Collecting Historical Data” on page 25 describes the data collector, data extractor, and data summarizer, which are the historical components of OMEGAMON II. These components gather the data used for historical reporting. The chapters in this portion of the manual explain how to set collection options for each component.

Part II: “Creating Historical Reports” on page 101 describes how to set reporting options and generate historical reports. Other reporting methods you can use also are described briefly.

Part III: “OMEGAMON II for DB2 Reports” on page 179 provides detailed information about each report available. It describes the report elements for each report and provides definitions for most report fields. You can use the information in this part of the manual to help you determine what type of data you need to collect and what the reporting options are for the reports you want to create.

P

About This Book


About This Book

Who should read this bookYou may want to read this document before you begin customization of the historical components, if you are responsible for customization. Or you may simply want to generate historical reports after your historical data has been captured. In either case, this manual provides detailed information about how to collect the appropriate data for the reports that you want, and how to create historical reports.

This document first provides an introduction to historical reporting. It describes the historical components, methods for gathering data, types of storage for historical data, and reporting tools. The remainder of the manual is divided into three parts so that you can easily access the information you need.

Documentation set information In addition to the manuals listed below, OMEGAMON II for DB2 includes an online data dictionary for the historical component. The OMEGAMON II for DB2 Historical Reporting Guide contains information on browsing and printing these documents.

� OMEGAMON II for DB2 User’s Guide: CUA Interface, Version 540

� OMEGAMON II for DB2 Reference Manual: Classic Interface, Version 540

� OMEGAMON II for DB2 Tuning Guide, Version 540

� OMEGAMON II for DB2 Historical Reporting Guide, Version 540

� OMEGAMON II for DB2 Configuration and Customization Guide, Version 540

� Installation and Configuration of Candle Products on OS/390 and z/OS, Version 350

� Candle Products Messages Manual

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

� technical documentation CD-ROM that came with your product

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

� online help provided with this product

19

Adobe Portable Document Format


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

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

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

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

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

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

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

Universal Printer driver from Adobe. This free printer driver is available at www.adobe.com.)

� the halftone/graphics color adjustment for printing color on black and white printers (check the printer properties under Start > Settings > Printer). For more information, see the online help for the Acrobat Reader.

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

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

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

http://www.adobe.com



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

21

Documentation Conventions


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

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

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

!!!!eBA*ServiceMonitor!!!!0990221161551000

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

Variables and literals in command syntax examplesIn examples of command syntax for the OS/390, VM, OS/400, and NonStop Kernel platforms, uppercase letters indicate actual values (literals) that the user should type; lowercase letters indicate variables that represent data supplied by the user:

LOGON APPLID (cccccccc)

However, for the Windows and UNIX platforms, variables are shown in italics:

-candle.kzy.instrument.control.file=instrumentation_control_file_name-candle.kzy.agent.parms=agent_control_file_name

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

SymbolsThe following symbols may appear in command syntax:

Table 1. Symbols in Command Syntax

Symbol Usage

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

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



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

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

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

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

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

_ Default values are underscored. Example:

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

Table 1. Symbols in Command Syntax

Symbol Usage

23

Candle Customer Service and Satisfaction

Candle Customer Service and Satisfaction

BackgroundTo assist you in making effective use of our products, Candle offers a variety of easy-to-use online support resources. The Candle Web site provides direct links to a variety of support tools that include these services:

eSupport allows you to create and update service requests opened with Customer Service and Satisfaction (CSS).

eDelivery allows you to download products, documentation, and maintenance 24 hours a day, 7 days a week.

eNotification notifies you of product updates and new releases.

In addition, you can find information about training, maintenance plans, consulting and services, and other useful support resources. Refer to the Candle Web site at www.candle.com for detailed customer service information.

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

http://www.candle.com

http://www.candle.com

25

Part I: Collecting Historical Data

Introduction 27

Introduction

The historical components of OMEGAMON II for DB2 collect and store historical information about DB2 activity. You can view historical information online or print a variety of reports using the Historical Reporter or other reporting facilities.

Note: To use the historical reporting capability of OMEGAMON II, you must first customize the historical components (refer to the OMEGAMON II for DB2 Configuration and Customization Guide). The Historical Reporting Guide provides information about data collection and report options for historical reporting. You may find this information helpful in making customization decisions.

Chapter ContentsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Historical Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Storing Data in DB2 Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Storing Data in Sequential Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Storing Data in Sequential Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Reporting Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Accessing Historical Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

1

Overview


Overview

This figure illustrates the relationship between the data management, data storage, and data reporting aspects of historical reporting.

Historical componentsThe historical components of OMEGAMON II provide different ways for you to gather the DB2 data that you will use for historical reports. These components are:

� online data collector

� data extractor

� data summarizer

Types of storageThe following types of storage are available for historical data:

� VSAM datasets

� DB2 tables

� sequential datasets

The storage type that you choose depends on the method you use for gathering data and the reporting tool you plan to use.

Data Management

Data Storage

Data Reporting

OnlineATF

ReportingOnline Data Collector

Data Summarizer

Data Extractor

VSAM Datasets

DB2Tables

Sequential Files

HistoricalReporter

SAS/COBOL Reports

IFCID-basedReports

Introduction 29

Overview

Reporting methodsYou can report on historical data or print reports using the following reporting methods:

� OMEGAMON II for DB2 Historical Reporter

� IFCID-based COBOL sample reports

� SAS reporting

� QMF reporting

� online ATF reporting

� near-term history displays

Some reporting methods may require input data from a particular storage source.

Additionally, you can create your own reports based on the COBOL, C or C++ record layouts provided. See “Using Other Historical Reporting Methods” on page 173.

Collection optionsBefore using the collector, extractor, or summarizer, you must set data collection options for each component. Data collection options include the types of data to collect, the DB2 subsystems to use, and filtering parameters.

Report optionsBefore generating a historical report using the Historical Reporter, you must set reporting options. Report options include how the data will be sorted, the source for data input, filtering criteria, and the reporting period.

Historical Components



IntroductionOMEGAMON II provides historical data management components that enable you to collect, extract and summarize historical information about the performance of your DB2 subsystem. These components include:

� online data collector

� data extractor

� data summarizer

Online data collectorThe online data collector gathers statistical and accounting information, audit information, DSNZPARM information, and limited performance information from the DB2 subsystem. The data collector runs in realtime and provides DB2 trace data for near-term accounting and statistics history displays.

A maximum of only one online data collector can be monitoring a DB2 subsystem at a time. You cannot simultaneously run multiple data collectors to gather historical data on the same DB2 subsystem.

The collector can store the collected data in DB2 tables, in sequential files, or in VSAM datasets as the activity occurs. This data is available immediately for reporting purposes. Any data stored in VSAM datasets can be archived automatically to a sequential dataset as each VSAM dataset becomes full.

For information on setting data collection options, see “Online Data Collection” on page 39.

Data extractorThe data extractor enables you to submit batch jobs that extract historical data from SMF datasets, GTF datasets, or from the online collector files. The data extractor stores the data in DB2 tables or in sequential datasets. These data include statistical, accounting, audit, DSNZPARM, and performance information, as well as data for any record type that can be produced by DB2.

If you do not require the immediate access to historical data that the collector provides, you may choose to capture data with the extractor. The extractor allows you to capture DB2 activity without using DB2 resources. This eliminates any impact on performance during the day. It also eliminates the possible loss of data in the event of a DB2 failure.

For information on setting data extraction options, see “Data Extraction” on page 53.

Introduction 31


Data summarizerThe data summarizer enables you to consolidate detailed historical statistical and accounting data that has been stored in either DB2 tables or in sequential datasets. The data is summarized and then written to DB2 tables or sequential datasets. This allows you to store historical data over long periods of time without using prohibitive amounts of storage space. The summarizer can also copy data from one type of storage to another.

For information on setting summarizer options, see “Data Summarization” on page 85.

Storing Data in DB2 Tables



IntroductionYou can store collected, extracted, or summarized data in DB2 tables. OMEGAMON II provides a set of table definitions that allow you to allocate DB2 tables during customization. There is at least one table for each type of data that OMEGAMON II formats (for example, the DB2 Statistics Table).

Note: The online data dictionary provides a description of each table and each column within the table. This document can be browsed online and/or printed. See “Accessing OMEGAMON II Messages and the Data Dictionary” on page 489 for instructions on accessing the data dictionary.

Storing data from the extractorYou can extract historical data from SMF, from GTF datasets, or from online collector datasets using the extractor and specify DB2 tables as the storage destination. You can write the data in insert mode or in load mode.

Insert Mode

When you choose to write historical data using insert mode (OUTPUT DB2), the extractor uses DB2 INSERT statements to place data into the DB2 tables. Insert mode is the default mode of extractor execution.

Load Mode

When you choose to write historical data using load mode (OUTPUT DB2LOAD), the extractor reads the input dataset and externalizes the DB2 data to a temporary (by default) sequential dataset. The DB2 load utility then uses this dataset as its input source.

Load mode is recommended when the volume of data you want to extract would cause DB2 to generate large amounts of log data if you used insert mode.

When you use load mode, you can prevent the generation of log data by specifying LOG=NO for the DB2 load utility. Use the DB2 load utility control statements in rhilev.RKD2SAM(LDCNcccc), where cccc refers to the DB2 subsystem ID.

Storing data from the summarizerYou can summarize detailed DB2 table data with the data summarizer and then store the summarized data in DB2 tables.

Introduction 33


Creating reports from DB2 tablesYou can create historical reports from DB2 tables using the following reporting methods:

� Historical Reporter

� QMF

You can use the sample QMF queries and forms that OMEGAMON II provides or use QMF to develop your own reports. These queries apply to the DB2 tables for the Historical Reporter.

� SQL

You can write SQL queries to access the data stored in DB2 tables.

For more information about the Historical Reporter, see “Using the Historical Reporter Menu” on page 111. For information about other reporting methods, see “Using Other Historical Reporting Methods” on page 173.

Storing Data in Sequential Datasets



You can store collected data in sequential datasets. To do this, you must define and initialize your datasets to store DB2 data. If, during customization, you selected sequential as your choice for storage, OMEGAMON II generates the necessary sample JCL in rhilev.RKD2SAM(HRCRVcccc). Otherwise, you can use the sample JCL in rhilev.RKD2SAM(HRCRVcccc) to define and initialize your datasets.

Storing data from the online collectorThe online collector collects data directly from DB2 and writes it to the specified VSAM or sequential dataset. When the active dataset becomes full, the collector automatically switches to another VSAM dataset or to a sequential dataset, using the switch-and-archive facility. This capability prevents data loss.

Switch and archive facility

In order to use the switch-and-archive facility, you must define at least two VSAM or two sequential datasets for data collection; however, three datasets are recommended as follows:

� a dataset for storing data (active)

� a dataset ready to begin storing data (available)

� a dataset being archived and reinitialized for next use (unavailable)

To specify these datasets (sometimes called H2 datasets), enter their names on the Data Collection Destination panel, or in the collection options member using the H2DATASET keyword (see “Online Data Collection” on page 39). You can specify as many as three datasets for each collection options member.

Switch and archive manually

You also can switch and archive datasets manually by issuing the following command:

F O2CI, F H2cccc, SWITCH

where cccc is the ID of the DB2 subsystem from which data is being collected; however, this will not substitute the variables @DB2, @DATE, and @TIME.

Before issuing the switch and archive command, use the CI display command

F O2CI, F H2cccc, LISTH2DS

described below, to make sure a dataset is available.

If OMEGAMON II cannot find an available dataset to switch to, it will issue a message indicating that the DB2 data cannot be stored. OMEGAMON II will periodically check for an available dataset until it finds one. Then it will issue a message stating how many historical records were lost.

Introduction 35


CI display command

Use the following Common Interface command to display the name, status, and usage percentage of your datasets:

F O2CI, F H2cccc, LISTH2DS

where cccc is the ID of the DB2 subsystem from which data is being collected.

This is an example of the resulting display:

H2 DATASET STATUS %FULL

O20561 CANDLE.H2LOG.DATA1 UNAVAIL 100.0

O20561 CANDLE.H2LOG.DATA2 ACTIVE 56.0

O20561 CANDLE.H2LOG.DATA3 AVAIL 0.0

Resource usage considerationsThe following are resource considerations:

� Historical data stored in sequential datasets does not use DB2 resources.

� The switch-and-archive facility allows OMEGAMON II to collect and store DB2 data continuously.

Creating reports from data in sequential datasetsYou can create historical reports from data in sequential datasets using the following methods:

� Historical Reporter

The Historical Reporter can generate accounting, statistics, audit, DSNZPARM, and performance reports.

� IFCID-based Reports

Using the IFCID-based product-provided reports, you can generate your own reports. These are based on the IFICDs you selected while using the Extractor. For instructions, see the README for this product.

� COBOL, C or C++, and SAS

You can create your own reports based on the IFCIDs selected while using the Extractor. Sample record layouts are provided.

For more information about the Historical Reporter, see “Using the Historical Reporter Menu” on page 111. For more information about the application trace facility, see “Using Other Historical Reporting Methods” on page 173.

Reporting Methods


Reporting Methods

IntroductionOMEGAMON II allows you to report on historical data using the following reporting methods:

� the Historical Reporter

� IFCID-based product-provided reports

� sample SAS and QMF reports

� creating your own reports in COBOL, C or C++ from the library of JCL programs

� creating your own reports in SAS from the library of JCL programs

These reporting methods are described briefly in this section.

For detailed information, see “Using the Historical Reporter Menu” on page 111 and “Using Other Historical Reporting Methods” on page 173.

Historical ReporterThe Historical Reporter is a self-contained reporting facility that runs on an ISPF platform. You can customize reporting options and create historical reports for the reporter using either the Historical Reporter Menu or the report request language. The Historical Reporter can produce reports from the sequential output of the extractor. These can be:

� H2X (historical) datasets

� DB2 tables

� SMF or GTF datasets

Note: The SMF, GTF, and online collector files must be run through the extractor before the collector can use them.

The Historical Reporter provides accounting, statistics, audit, DSNZPARM, and performance reports.

SAS and QMF reportingOMEGAMON II provides a library of SAS and QMF sample reports. You can use these samples to produce historical reports, or create your own reports from the samples.

COBOL, C and C++ record layoutsOMEGAMON II provides a library of COBOL, C, and C++ record layouts. You can use these record layouts to produce historical reports, or develop your own reports from the samples.

Introduction 37

Accessing Historical Functions


Accessing the Historical Main MenuTo access the Historical Main Menu:

1. Access the ISPF dialog in either of the following ways:– Enter %KD2SPF from native TSO (outside of ISPF).

– Enter TSO %KD2SPF from any command line within ISPF.

Result: The OMEGAMON II for DB2 ISPF Primary Options menu appears.

FIGURE 1. OMEGAMON II for DB2 ISPF Primary Options Menu

From this menu, you can access the Historical Main Menu, the realtime component, or DB2 Tools.

2. Type 2 on the OPTION line of the OMEGAMON II for DB2 Primary Options Menu.Result: The Historical Main Menu appears.

FIGURE 2. Historical Main Menu

8:30:12Candle --------- OMEGAMON II FOR DB2 V540 -------------------OPTION ===> 1 REALTIME - Execute realtime functions 2 HISTORICAL - Generate reports/graphs; execute data management functions 3 DB2 TOOLS - Execute DB2 tools X EXIT - Exit dialog Enter END command to exit dialog

Candle -------------- HISTORICAL MAIN MENU -------------- OMEGAMON II for DB2OPTION ===> 1 REPORT - Generate historical reports 2 COLLECT - Edit data collection specifications 3 EXTRACT - Edit SMF/GTF extract specifications 4 SUMMARIZE - Edit data summarization specifications 5 DICTIONARY - Display data dictionary 6 MESSAGES - Display OMEGAMON messages 7 ATF REPORT - Display ATF trace from VSAM dataset X EXIT - Return to OMEGAMON primary menu Enter END command to return to OMEGAMON primary menu



Historical Main Menu optionsThe Historical Main Menu allows you to access the historical reporting features of OMEGAMON II.

� Select Report to access the Historical Reporter Menu from which you can set reporting options and generate historical reports.

� Select Collect, Extract, or Summarize to access panels from which you can set collection options for the data collector, data extractor, and data summarizer.

� Select Dictionary to access the data dictionary, which describes all the DB2 table column names.

� Select Messages to access explanations of the messages that may appear during a realtime or historical session.

� Select ATF Report to access the application trace facility, which allows you to view trace information from a VSAM dataset.

Online Data Collection 39

Online Data Collection

This chapter describes the online data collector.

Chapter ContentsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Data Collection Keywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

2

Overview


Overview

The online data collector gathers statistical and accounting information, audit information, DSNZPARM information, and limited performance information from the DB2 subsystem. The data collector runs in realtime and provides DB2 trace data for near-term accounting and statistics history displays.

The collector can store the collected data in either DB2 tables, in VSAM datasets,or in sequential datasets as the activity occurs. This data is available immediately for reporting purposes.

Initially, you define collector options and storage destinations during customization of the historical components. You also specify whether you want data collection to begin automatically at startup. However, you can change your collection options or create additional collection options members at any time.

The online data collector runs under the Common Interface (CI). You can start one collector or start multiple collectors with different collection options. This allows you to monitor multiple DB2 subsystems under a single CI. Each collector monitors a single DB2 subsystem.

For instructions on starting and stopping the collector or multiple collectors under the CI and issuing collector commands, see the OMEGAMON II for DB2 Configuration and Customization Guide.

Types of informationThe types of information the collector can gather and store are as follows:

� statistical data

� accounting data

� audit data

� DSNZPARM data

� performance data

Data collection optionsThe options that you set for data collection specify the following:

� the type of data to collect

� which DB2 subsystem or subsystems to use

� the collection interval

� storage locations


Overview

Prerequisites for collecting data on multiple subsystemsMeet the following prerequisites to run multiple history collectors.

Multiple history collectors cannot use the same VSAM file.

Collection options membersData collection options are stored in a collection options member in the rhilev.RKD2PAR dataset. When you start a collector, you specify the name of the member containing the collection options you want to use for that collection period. To use multiple collectors, you can create multiple collection options members.

There are two ways to create or modify a collection options member:

� Use the collector customization panels provided in the ISPF dialog.

� Use the collector keywords.

The sections that follow describe how to use these methods.

IF... AND... THEN...

You are running multiple DB2 subsystems on a single MVS

you want to run multiple history collectors,

you must have a separate sequential file for each DB2 subsystem.

Data Collection Keywords



Setting data collection optionsData collection keywords allow you to specify data collection options by modifying the keywords in the default collection options member, or by modifying the keywords in a collection options member you created using the customization panels.

Creating a collection options member

To specify collection options using keywords, you can create or edit a collection options member, which can be invoked at collector startup.

To do this, copy the default collection options member in rhilev.RKD2PAR(COPTcccc), where cccc is the DB2 subsystem ID. Then use keywords to modify the collection options in the copied member.

Keyword syntax

The syntax of the data collection keywords is as follows:

Keyword(value)

or

Keyword(value,value,value,...)

When a keyword accepts only one value, enter the value in parentheses after the keyword. When a keyword accepts multiple values, enter the values in parentheses after the keyword, separated by commas or spaces.

Considerations for keyword syntax

Observe these considerations when using keywords for the COPTxxx member:

� If you need to continue statements on another line for the keywords: AUTHID, CONNID, CORRID, ORIGAUTH, and PLAN

– do not use a continuation character. This means do not repeat the “keyword(“ entry on the next line.

– do not start the continuation line in column 1. Only the keyword should begin in column 1.

Example continuation line

PLAN(¬DSNQ* ¬DSNTI* ¬FINAN1 ¬FINAN2 ¬DSNG*

¬DSNZZ ¬FINAN3 ¬FINAN4 ¬DSNR* ¬DSNRR*

¬FINAN5 ¬FINAN6)

� You cannot use filtering on the GROUPBY keyword.



Define DB2 subsystem and collection interval

The keywords used to define the DB2 subsystem name and collection interval are as follows:

� DB2SYS

� DB2SYSWRITE

� INTERVAL

Define data types to collect

The keywords used to define the types of data to collect are as follows:

� ACCTG

� AUDIT

� DSNZPARM

� DYNAMICSQL

� LOCKCONT

� LOCKSUSP

� NEGSQL

� SCAN

� SORT

� STATISTICS

Specify storage destination

The keywords used to specify where the historical data is to be stored are as follows:

� DESTINATION

� H2DATASET

� WRITEOPTION

� SEQDATASET

Control frequency

The keyword used to control frequency is COMMIT.

Define filter and group options

The keywords used to define filtering and grouping options are as follows:

� AUTHID

� CONNID

� CONNTYPE

� CORRID

� GROUPBY



� ORIGAUTH

� PLAN

Note: Candle recommends that you use one or more of the filtering/grouping keywords. This will reduce demands on CPU time and DASD space, especially if you are running in a high-volume transaction environment.

Define IFCID

Used to define one or more IFCIDs for which you would like to collect data. Used with the WRITEOPTION keyword.

Performance Options

The keywords used to control the collection of IFI trace record information are as follows:

� BUFSIZE

� IFIREADTIME

Data collection keyword descriptionsTable 2: Data Collection Keywords on page 44 lists the keywords in alphabetic order, and provides a complete description of each. Within this table, default values are underscored.

Table 2. Data Collection Keywords

Keyword Description Value

@DB2 Used within the specification of a dataset name to indicate the substitution of the DB2 subsystem name as part of the dataset name.

1 – 4-character DB2 subsystem name.

@TIME Used within the specification of a dataset name to indicate the substitution of the current time as part of the dataset name.

Format is Thhmmss, where:� T = constant� hh = hour� mm = minute� ss = second

@DATE Used within the specification of a dataset name to indicate the substitution of the date as part of the dataset name

Format is Dyymmmdd, where:� D = constant� yy = year� mm = month� dd = day



ACCTG The type of accounting data to collect. If this keyword is not specified, no accounting data will be collected. Multiple classes can be specified in this keyword.

ARCHIVEJCL The keyword in the COPTnnnn member. This keyword points to ARCVcccc, which is the member name in the dataset rhilev.RKD2PAR. This dataset contains the JCL required to archive the VSAM log dataset and reinitialize it for future use.

1 – 8-character member name.

AUDIT The class of audit data to collect. If this keyword is omitted, no audit data will be collected. Multiple classes can be specified in this keyword.

AUTHID The authorization ID about which OMEGAMON II should collect data. This keyword is a filter for information that is collected. If this keyword is omitted, OMEGAMON II selects all data from all authorization IDs.

The 1 – 8-character authorization ID.

See “Keyword syntax” on page 42 for examples of how to specify this value.

BUFSIZE Specifies the size (in kilobytes) of the buffer used to hold IFI records until they can be written out by the collector.

Table 2. Data Collection Keywords (continued)


1 Collect accounting class 1 data.

2 Collect accounting class 1 and 2 data.

3 Collect accounting class 1, 2, 3.



1 Collect audit class 1.








n A number ranging from 50 – 1024, with 300 being the default.



COMMIT The frequency with which inserts are committed to the DB2 tables during periods of insert activity.

CONNID The connection ID about which OMEGAMON II should collect data. This keyword is a filter for information to be collected. If this keyword is omitted, OMEGAMON II selects all data from all connection IDs.

The 1 – 8-character connection ID.


CORRID The correlation ID about which OMEGAMON II should collect data. This keyword is a filter for information to be collected. If this keyword is omitted, OMEGAMON II selects all data from all correlation IDs.

The 1 – 12-character correlation ID.


DB2SYS The DB2 subsystem to be monitored. This subsystem must be executing on the same processor as the Common Interface (CI). This keyword is required.


DB2SYSWRITE The DB2 subsystem to which collected data will be written. This subsystem must be executing on the same processor as the Common Interface (CI). This keyword is optional. If this keyword is not specified, the value contained in DB2SYS is used.


DESTINATION The backup destination for the trace output from the DB2 traces started by the collector. If no destination is specified, the only trace destination will be the Instrumentation Facility Interface (IFI).

The default is no backup destination.

DSNZPARM Directs OMEGAMON II to collect installation parameter data.



n A number ranging from 1 – 9999999.

500 A commit is performed once for every 500 inserts.

SMF Record trace output to SMF (record types 100, 101, and 102).

GTF Record trace output to GTF.

YES Collect DSNZPARM data.

NO Do not collect DSNZPARM data.



DYNAMICSQL Specifies whether to collect SQL text and access path information for dynamic SQL.

GROUPBY Specifies how accounting data is to be grouped (summarized). If this keyword is omitted, data is recorded for each individual thread. This keyword accepts multiple arguments, for example, GROUPBY(CONNID, PLANNAME).

When this keyword is used, data is grouped based on the selected options, and it is written at every n minutes (as specified with the INTERVAL keyword).

H2DATASET The name of a VSAM dataset in which historical data is to be stored. As many as 3 datasets can be specified. This keyword must be specified when WRITEOPTION(VSAM) is specified.

Up to three 1 – 44-character VSAM dataset names.

IFCID Allows you to collect any type of record data. Used with the WRITEOPTION keyword.

Integer. You can specify as many integers as you like, separated by a comma.

See “Specify IFCIDs” on page 60 for a list of the IFCIDs supported.

IFIREADTIME Controls the frequency with which the collector reads new IFI trace records into its buffer. Decreasing the interval increases the READA frequency; however, it also increases CPU cycle usage.



YES Collect SQL text and access path information for dynamic SQL.

NO Do not collect SQL text and access path information for dynamic SQL.

AUTHID Group by authorization ID.

CONNID Group by connection ID.

CORRID Group by correlation ID.

ORIGAUTHID Group by original authorization ID.

PLANNAME Group by plan name.

mmssth Where mmssth is minutes, seconds, tenths and hundredths of seconds. The default is 010000 (1 minute). The maximum value that should be specified for IFIREADTIME is 1 minute.



INTERVAL The time interval used to record statistics or accounting data if the GROUPBY keyword is specified.

LOCKCONT Specifies whether to collect lock timeout and deadlock information.

LOCKSUSP Specifies whether to collect lock suspension information.

MAXHOURS Specifies the maximum number of Near Term History buckets. This keyword is used to limit the amount of data collected for Near Term History. As a result, memory usage is limited.

nn A one- or two-digit number ranging from 1 to 168.

NEGSQL Specifies whether to collect negative SQL code IFCID 58. This keyword must be on to generate the Negative Application Codes SQL report.

ORIGAUTH The original authorization ID for which OMEGAMON II should select data. This keyword is a filter for information to be collected. If this keyword is omitted, the collector selects all data from all original authorization ID names that had accounting activity in DB2.

1 – 8-character original authorization ID.




n An interval ranging from 1 – 60 minutes.

RMF Synchronizes the collection interval with the RMF interval. If RMF is not active, a 15-minute interval is assumed.

YES Collect lock timeout and deadlock information.

NO Do not collect lock timeout and deadlock information.

YES Collect lock suspension information.

NO Do not collect lock suspension information.

YES Collect negative SQL text and produce the Negative Application SQL Codes report.

NO Do not collect negative SQL text.



PLAN The plan name about which OMEGAMON II should collect data. This keyword is a filter for information to be collected. If this keyword is omitted, OMEGAMON II selects all data from all plan names.

1 – 8-character plan name.


SEQDATASET Allows the entry of multiple sequential dataset names. This keyword must be specified when WRITEOPTION(SEQ) is specified.

� @DB2 - substitute DB2 subsystem name

� @TIME - substitute current time� @DATE - substitute date

SCAN Directs OMEGAMON II to collect scan data.

SORT Directs OMEGAMON II to collect sort data.

SPACE(xxx,nnn,nnn2)

Used within the specification of a dataset name to indicate the space allocation for datasets created by the collector.

The value format is xxx,nnn,nnn2, where:� xxx = CYL for cylinders; TRK

for tracks� nnn = the number for primary

allocation� nnn2 = the number for

secondary allocation

STATISTICS Directs OMEGAMON II to collect statistics trace data.



YES Collect scan data.

NO Do not collect scan data.

YES Collect sort data.

NO Do not collect sort data.

YES Collect statistics data.

NO Do not collect statistics data.



WRITEOPTION The desired storage medium for historical data.

If you specify VSAM, you also must enter a value for the H2DATASET keyword. (You must specify VSAM for near-term accounting data to be displayed.)

If you select NONE, you must also specify STATISTICS(YES).

� DB2 - DB2 tables� VSAM - VSAM datasets� SEQ - Sequential file output� VSAM,SEQ - Near-term

history data is collected in VSAM files. Different IFCDs can be collected in VSAM files. Long-term history is collected in sequential files. Archiving of near-term history is optional.

� None - Data is not saved, but statistics data is available to the near-term history displays while the collector is active.





Historical data filtering

Introduction

By default, OMEGAMON II collects all of the available data for each of the specified keywords. To limit the data that OMEGAMON II collects, you can specify a keyword followed by a value. You can also use the value with a not (¬) operator.

Not operator

In this example, the CONNID keyword is used with values and the not (¬) operator. It specifies that OMEGAMON II will collect data for all connection IDs, except the two IDs specified.

CONNID(¬IM3D ¬I210)

Wildcard character (*)

You can use the asterisk (*) wildcard character at the end of a value. All data matching the characters preceding the asterisk will be collected.

In this example, the PLAN keyword is used with the asterisk (*) wildcard character. It specifies that OMEGAMON II will collect data for all plans that begin with the characters ABCD.

PLAN(ABCD*)

Wildcard character (?)

You can use the question mark (?) wildcard character as a replacement for any single character within a value.

In this example, the DB2ID keyword is used with the question mark (?) wildcard character. It specifies that OMEGAMON II will select data for all DB2 subsystems that contain a first character of D and a last character of T, with two characters in between.

DB2ID(D??T)

Data Extraction 53

Data Extraction

This chapter describes the data extractor.

Chapter ContentsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Extractor Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Data Extraction Customization Panels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Setting data extraction options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Data Extraction Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Setting Data Extraction Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Data Extraction Keyword Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

3

Overview


Overview

The data extractor runs as a batch job and extracts DB2 trace data from SMF, GTF, or the D2 online collector. The data is stored in either DB2 tables or in sequential datasets.

Each type of storage allows the data to be accessed for historical reporting. For information about what type of storage to choose, see “Storing Data in DB2 Tables” on page 32 and “Storing Data in Sequential Datasets” on page 34.

When to use data extractionYou may want to use data extraction for

� storing data that does not need to be accessed immediately

� merging data from multiple systems

� gathering and storing historical data when a system outage interrupts the collector, but DB2 continues to run

Types of information for extractionThe types of information the extractor can gather and store are as follows:

� statistical data (including distributed data)

� accounting data (including distributed data)

� audit data

� DSNZPARM data

� performance data

Setting extraction optionsBefore performing data extraction from SMF, GTF, or from the D2 online collector, you first must specify the types of data that you want to extract and the storage destination for the data. Then you must generate and submit the JCL for the extractor. Sample JCL resides in rhilev.RKD2SAM.

See “Data Extraction Customization Panels” on page 58 and “Data Extraction Keywords” on page 59 for additional information.

Data Extraction 55

Extractor Input

Extractor Input

The data extractor accepts input from SMF, GTF datasets, or from the D2 online collector. To extract the data to these datasets, you must issue DB2 START TRACE commands. The commands described in this section are samples that you may use.

Statistics traceThe following is a sample statistics trace command:

START TRACE (STAT) DEST(ccc)

where ccc is either SMF or GTF.

Accounting traceThe following is a sample accounting trace command:

START TRACE (ACCTG) DEST(ccc) TDATA(COR,CPU,DIST) CLASS(1,2,3)

where ccc is either SMF or GTF. If you want package level information, you also must start classes 7 and 8.

If you want sort and scan information as well, issue the following command (for sort only, use IFCIDS 95 and 96; for scan only, use IFCIDs 15, 16, 17, and 18):

START TRACE (PERFM) DEST(ccc) TDATA(COR,CPU,DIST) CLASS(nn)IFCID(15,16,17,18,95,96)

where ccc is either SMF or GTF and nn is an available installation-defined performance trace class (30, 31, or 32).

Audit traceThe following is a sample audit trace command:

START TRACE (AUDIT) DEST(ccc) TDATA(COR,CPU,DIST) CLASS(1,2,3,4,5,6,7,8)

where ccc is either SMF or GTF.

To ensure that the database and pageset IDs are translated to names, also issue the following command:

START TRACE (PERFM) DEST(ccc) CLASS(nn) IFCID(105,107)

where ccc is either SMF or GTF, and nn is an available installation-defined performance trace class (30, 31, or 32).

Extractor Input


Application traceThe following is a sample application trace command:

START TRACE (PERFM) DEST(ccc) TDATA(COR,CPU) CLASS(nn)IFCID(15,16,17,18,21,22,58,59,60,61,62,63,64,65,66,68,69,70,71,73,74,84,85,86,87,88,89,95,96,105,107)

where ccc is either SMF or GTF, and nn is an available installation-defined performance trace class (30, 31, or 32).

The START TRACE command turns on trace information for all DB2 activity. Candle strongly recommends that you limit each trace by specifying certain authorization IDs and plans by using the AUTHID and PLAN keywords of the START TRACE command.

You can further limit the amount of data gathered by filtering IFCIDs. The IFCIDs that generate especially large numbers of trace records are as follows:

� 21 (lock detail record)

� 15, 16, 17, and 18 (begin and end scan records)

Other candidates for exclusion are as follows:

� 95 and 96 (begin and end sort records)

� 22 (access plan record).

You should specify all other IFCIDs to ensure that application trace extraction and reporting will function properly.

Furthermore, if you want to insert the IN DB2 CPU TIME in field AUHUCPU and to display this time on the Historical Performance reports, then you must include TDATA (COR, CPU) in the START TRACE Performance command. For more information, refer to the section titled “Complete configuration of the Classic Interface” in the Omegamon II for DB2 Configuration and Customization Guide.

Data extraction rulesThe following applies to data used as input to the extractor:

� SMF data

– Data first must be processed by the SMF dump program. The extractor cannot process active datasets.

– Multiple datasets with records in ascending date/time sequence can be processed at one time.

– Records without a sort are acceptable input to the extractor.

Data Extraction 57

Extractor Input

� GTF data

– Wrapped datasets without a sort are acceptable input to the extractor.

– One dataset at a time is processed by the extractor. This restriction allows for wrapped datasets.

Multiple GTF datasets can be used in the new extractor.

– A timestamp on GTF records is required by the extractor.

In the GTF procedure, set TIME=YES on the PARM statement for EXEC PGM=AHLGTF.

Data Extraction Customization Panels


Data Extraction Customization Panels

Setting data extraction optionsUse the customization panels accessed through the Historical Main Menu to specify your data extraction options. These settings remain in effect until they are changed.

You also can set or modify extraction options using keywords, instead of the customization panels. To use keywords, refer to “Data Extraction Keywords” on page 59.

Online help

You can press F1 from any customization panel to get panel and field help.

Accessing the customization panels

To access the customization panels through the OMEGAMON II dialog:

� Select EXTRACT from the Historical Reporting Main Menu.

Result: The Data Extraction Specifications panel appears.

Setting data extraction specifications

The Data Extraction Specification panel allows you to specify information such as time and date ranges, filtering parameters, and the types of data (for example, accounting) to be extracted.

When you finish entering your specifications on this panel, press Enter to go to the Data Extraction Destination panel.

Defining destination for extracted data

The Data Extraction Destination panel allows you to specify whether to write extracted data to DB2 tables or to sequential datasets. If you specify DB2 tables, you must choose either insert mode or load mode. For information about writing to DB2 tables, see “Storing Data in DB2 Tables” on page 32.

When you finish entering your specifications on this panel, press Enter to go to the Extract JCL Options panel.

Editing and submitting the job

The Extract JCL Options panel creates the JCL for the data extractor, using the options you defined on the previous customization panels. Additionally, you either can edit the JCL or automatically submit the job.

Verify that the information on this panel is correct or modify it, as needed. Then follow the instructions on the panel to create and submit the extraction job.

Data Extraction 59

Data Extraction Keywords


Setting Data Extraction Options

Using sample JCL

Data extraction keywords allow you to specify extraction options using sample JCL, or by modifying the extraction options members you created using the customization panels.

To specify extraction options using sample JCL, follow the instructions in rhilev.RKD2SAM. You either can change the value of any keyword or use the default values.

Dataset members to modify

Use the following dataset members in rhilev.RKD2SAM to specify extraction options:

� EXTIcccc when writing to DB2 tables in insert mode

� EXTLcccc when writing to DB2 tables in load mode

Define storage destination

The keyword used to specify how the historical data is to be stored is OUTPUT.

Define source of trace data

The keyword used to define the source of trace data is SOURCE.

Specify commit frequency

The keyword used to control commit frequency is COMMIT.

Specify the CREATOR

The tables into which data is inserted are prefixed with an identifier of your choosing. The prefix is an eight-character identifier. The CREATOR keyword lets you specify this identifier. CANDLE is the default CREATOR.

Format of table names

When you specify an IFCID, the data extracted and inserted into tables applies to the type of data supported by that IFCID. It also depends upon the version of DB2 that you are running. Each table name is prefixed by the CREATOR identifier.

For example, IFCID 1 (System Statistics) generates a table that contains system statistics data, called

CANDLE.V6_QW0001

where

– CANDLE is the CREATOR identifier. CANDLE is the default identifier.

– V6 is the version of DB2. This could be V6, V7, or V8, depending upon the version of DB2 being used.



– QW0001 - the name of the table generated for a particular IFCID. See “Specify IFCIDs” on page 60 for a list of the IFCIDs supported.

Subsets of 1, for example CANDLE.V6_QW0001_1, apply to a specific section of the record for that IFCID.

Specify IFCIDs

The keywords used to specify the type of data to extract. These IFCIDs are supported:� 1 System Statistics� 2 Database Statistics� 3 Accounting Record� 4 DB2 Trace Start/Modify� 5 DB2 Trace Stop� 6 Read I/O Start� 7 Read I/O Start� 8 Write I/O Start� 9 Write I/O End� 10 Async Write I/O Start� 11 Validation Exit� 12 Edit Encode Exit� 13 Hash Scan Start� 14 Hash Scan End� 15 Index Scan Start� 16 Insert Start� 17 Sequential Scan Start� 18 Scan End� 19 Edit Decode Exit� 20 Page Locks Summary� 21 Detail Lock Request� 22 Mini-plans Generated� 23 Utility Start� 24 Utility Object/Phase Change� 25 Utility End� 26 Obtain Sort Workfile� 27 Sort Info: #Records� 28 Sort Info: #Runs� 29 EDM Request Start� 30 EDM Request End� 31 EDM Pool Full� 32 Log Mgr Wait Start� 33 Log Mgr Wait End� 34 Log Mgr Read I/O Wait Start� 35 Log Mgr Read I/O Wait End� 36 Log Mgr Non-I/O Wait Start� 37 Log Mgr Non-I/O Wait End� 38 Log Mgr Active Log Write Start� 39 Log Mgr Active Log Write End� 40 Log Mgr Archive Log Write Start� 41 Log Mgr Archive Log Write End� 42 Checkpoint Started� 43 Checkpoint Ended

Data Extraction 61


� 44 Lock Suspend/ID Call� 45 Lock Suspend/ID Resume� 46 Agent Exec Unit Switch� 47 SRB Exec Unit Start� 48 SRB Exec Unit End� 49 TCB Exec Unit Start� 50 TCB Exec Unit End� 51 Shared Latch Resume� 52 Shared Latch Wait� 53 SQL Commit/Descr/Rollback/Error� 54 Lock Contention Info� 55 Set Current SQL ID� 56 Exclusive Latch Wait� 57 Exclusive Latch Resume� 58 SQL Statement End� 59 SQL Start: Fetch� 60 SQL Start: Select� 61 SQL Start: Ins/Upd/Del� 62 DDL Statement Start� 63 SQL Statement Text� 64 SQL Start: Prepare� 65 SQL Start: Open Cursor� 66 SQL Start: Close Cursor � 67 Accounting Start� 68 Abort Request Start� 69 Abort Request End� 70 Commit Phase 2 Start� 71 Commit Phase 2 End� 72 Create Thread Start� 73 Create Thread End� 74 Terminate Thread Start� 75 Terminate Thread End� 76 End Of Memory Start� 77 End Of Memory End� 78 End Of Task Start� 79 End Of Task End� 80 Establish Exit Start� 81 Establish Exit End� 82 Identify Start� 83 Identify End� 84 IMS/CICS Prepare Start� 85 IMS/CICS Prepare End� 86 IMS/CICS Signon Start� 87 IMS/CICS Signon End� 88 TSO Sync Start� 89 TSO Sync End� 90 DB2 Cmd Text Entered� 91 DB2 Cmd End Status� 92 AMS Cmd Start & Text� 93 Suspend Called� 94 TCB Or SRB Resumed� 95 Sort Execution



� 96 Sort Ended� 97 AMS Cmd End Status� 98 Non-pool Get/Free Start� 99 Non-pool Get/Free End� 100 Pool Storage Get/Free Start� 101 Pool Storage Get/Free End� 102 Short On Storage Detected� 103 Short On Storage Set Off� 104 Log Dataset Mapping� 105 DBID/OBID Database/Tablespc Map� 106 DSNZPARM System Parameters� 107 DB/PS Open/Close Info� 108 Bind/Rebind Start� 109 Bind/Rebind End� 110 Bind Free Start� 111 Bind Free End� 112 Allied Thread Plan Attributes� 113 System Agent Plan Attributes� 114 Archive I/O Wait Start� 115 Archive DASD Wait End� 116 Archive Tape Wait End� 117 Archive Read Start� 118 Archive Read End� 119 BSDS Write I/O Start� 120 BSDS Write I/O End� 121 Thread Entry Into DB2� 122 Thread Exit From DB2� 123 SRV Generated Record� 124 SQL Detail Record� 125 Multi-Index Path Select� 126 Log Buffer Write� 127 Agent Suspend - I/O In Progress� 128 Agent Resumed By I/O Initiator� 129 Log Buffer Write� 140 Authorization Failure� 141 Explicit Grant/Revoke� 142 Create, Alter or Drop� 143 Attempted DDL Change� 144 Attempted DDL Access� 145 DML Session Log Record� 146 Site Defined Log Record� 147 Monitor Detail Record 1� 148 Monitor Detail Record 2� 149 Lock Info: Resource� 150 Lock Info: Agent� 151 Accounting: Site Record� 152 Statistics: Site Record� 153 Performance: Site Def, Rare� 154 Performance: Site Def, Normal� 155 Performance: Site Monitoring� 156 Serviceability: Site Defined� 157 DRDS RDS Interface Data

Data Extraction 63


� 158 DRDS Converse Mgr Intfc Data� 159 DRDS Conversation Create & Wait� 160 DC Requesting Agent Data� 161 DC Responding Agent Data� 162 DTM Requesting Agent Data� 163 DTM Responding Agent Data� 164 VTAM Exits to DB2� 165 VTAM Macro Call/Return� 166 Buffer Sent/Received� 167 Conversation Alloc Req Queued� 168 Distributed SQL Statement Text� 169 Distributed Authid Translation� 170 DB2 Service Wait Agent Suspend� 171 DB2 Service Wait Agent Resume� 172 Deadlock UOW’s Detail� 173 DUW/RUW DBAT Start DB2 Time� 174 Archive Log Quiesce Start� 175 Archive Log Quiesce End� 176 DUW/RUW DBAT End DB2 Time� 177 Successful Package Allocate� 178 DSNJW117 Exit Invocation Start� 179 DSNJW117 Exit Invocation End� 180 DC Communication Trace Buffers� 181 DDM Level 6B Objects - DDIS� 182 DDM Level 6B Objects - FDOCA� 183 DRDS RDS/SCC Interface Data� 185 IFI Reads Request� 186 Portion Of MEPL Trace Record� 187 Accounting class 5 flag� 188 IFI Reads Request Completion� 190 Hybrid Join Overflow, RDS Info� 191 First Failure Data Capture� 192 DDM Level 6A Header Errors� 193 UOV Disp/SQLCODE Mismatch� 194 Invalid SNA FMH-5 Received� 195 First Failure DRDS Data Capture� 196 Timeout UOW’s Detail� 198 Buffer Pool Access� 199 Buffer Mgr Dataset LSTATS Trace� 200 Accounting - nesting� 201 Alter Buffer Pool Results� 202 Dynamic System Parameters� 203 Heuristic Decision Occurred� 204 DB2 Partner ColdStart Detected� 205 Incorrect WarmStart Parameters� 206 SNA CompStates Protocol Error� 207 SNA CompStates Heuristic Damage� 208 SNA SyncPoint Protocol Error� 209 SNA SyncPoint Comm Failure� 210 LogName Change on WarmStart� 211 Claim Made/Released/Modified� 212 Drain Made/Released



� 213 Lock Suspend for Drain Lock� 214 Lock Resume for Drain Lock� 215 Wait for Zero Claim Count� 216 End Wait for Claim Count� 217 Storage Manager Pool Statistics� 218 UOW Lock Avoidance Summary� 219 Utility LISTDEF record� 220 Utility dataset close record� 221 Degree of Parallelism� 222 Parallel Group Processing� 223 UOW Lock Avoidance Detail� 224 Select Procedure Bypassed� 225 Storage Manager Pool Summary Statistics� 226 Agent Suspend for Page Latch� 227 Agent Resumed for Page Latch� 228 Tape Unit Deallocation Start� 229 Tape Unit Deallocation Stop� 230 Data Sharing Global Statistics� 231 Parallel Group Task Time� 232 Thread Entry/Exit from DB2� 233 Stored Procedure Call� 234 CICS or IMS NID Unknown� 235 Conditional Restart Data Loss� 236 SNA XLN Protocol Error � 237 Set Current Degree� 238 DB2 Restart ERror � 239 Pkg/DBRM Acctg Info (>10)� 240 Pkg/DBRM Exec Start/End� 241 Pkg/DBRM Susp Start/End� 242 Begin Stored Procedure Wait� 243 End Stored Procedure Wait� 247 Input Host Variable Trace� 248 Output Host Variable Trace� 249 EDM Pool Invalidate DBD� 250 Grp BufferPool Connect/Disc� 251 Partition P-lock Dynamics� 252 Begin XES Request� 254 Grp BufferPool Cache Stats� 255 Group Buffer Pool Refresh� 256 Alter Group BufPool Results� 257 Inter-DB2 Notify Message� 258 Monitoring extend and space growth� 259 Page P-lock Dynamics� 260 End XES Request� 261 Group Buffer Pool Checkpoint� 262 Group Buffer Pool Castout Threshold� 263 Pageset and Partition Castout Detail� 265 Begin SCA Access Request� 266 End SCA Access Request� 267 Begin CF Maint Operation� 268 End CF Maint Operation� 272 ASSOCIATE LOCATORS statement info

Data Extraction 65


� 273 ALLOCATE CURSOR statement info� 274 INPUT SQLDA/host variable ctrl blk� 275 OUTPUT SQLDA/host variable ctrl blk� 276 INPUT SQLDA/transition variable � 277 Routine Get Storage� 278 Routine Free Storage� 305 Table Check Constraint� 306 Log Records� 311 GLOBAL TEMPORARY TABLES� 313 LONG RUNNING UR’S AT CHKPT� 314 ACCESS CONTROL AUTH EXIT PARAMETERS� 316 PREPARED STATEMENT CACHE STATS� 317 PREPARED STATEMENT CACHE STATEMENT� 319 Non RACF identity mapping� 321 Begin force-at-commit� 322 End force-at-commit� 324 FUNCTION RESOLUTION TRACE� 325 Start or End of a Trigger Activation� 327 LE RUNTIME DIAGNOSIS� 329 Asynch IXLCACHE/IXLFCOMP requests� 330 ACTIVE LOG SHORTAGE SITUATION� 331 Locator service� 332 TransCSO service� 333 Traverse CSO� 334 DRDA Exceptions for scrollable cur� 335 System Event Stalled Notification� 336 OUTPUT CCSID cntl block� 337 Lock Escalation Occurences� 341 Incremental bind for special reg� 342 WF/TD usage per Agent� 350 THE SQL STATEMENT - PRODUCED BY THE PARSER

Specify time options

The keywords used to define time options are as follows:

� ENDDATE

� ENDTIME

� STARTDATE

� STARTTIME


The keywords used to define filtering are as follows:� ALTERDATABASE� ALTERINDEX� ALTERSTOGROUP� ALTERSYNONYM� ALTERTABLE� ALTERTABLESPACE� ALTERVIEW



� AUTHID� BPID� CICSTRAN� CLOSE� COMMIT� CONNID� CONTYPE� CORRID� CORRNAME� CPU� CREATEALIAS� CREATEDATABASE� CREATEINDEX� CREATETABLE� CREATETABLESPACE� CREATESYNONYM� CREATESTOGROUP� CREATEVIEW� DB2CPU� DB2ID� DB2TIME� DBNAME� DEADLOCKS� DELETE� DESCRIBE� DROPALIAS� DROPDATABASE� DROPINDEX� DROPSTOGROUP� DROPSYNONYM� DROPTABLE� DROPTABLESPACE� DROPVIEW� ELAPSED� EXECUTE� FETCH� GETPAGE� GRANT� GROUP� HOSTNAME� IBINDS� IFCID� INSERT� JOBNAME� LOCATION� LOCKTABLE� LUWID� MAXDEGREE

Data Extraction 67


� MEMBER� OPEN� OUTPUT� ORIGAUTHID� PACKAGE� PGMSTART� PLANNAME� PREPARE� PSID� PSNAME� REVOKE� ROLLBACK� SELECT_COUNT� SETSQLID� SORTS� SPCALL� SPTERM� SPWAIT� SQLSTMTS� SYSID� TCPIP� TEMPTABLE� THREADSTART� TIMEOUTS� TOTALGROUPS� UOWSTART� UPDATE� WAIT

Keyword syntaxThe syntax of the data extraction keywords is as follows:

Keyword(value)

Keywords accept only one value. To extract multiple values for the same keyword, supply each value in parentheses after the keyword, separated by the AND operator or by the OR operator.

Keyword(value) AND Keyword(value) AND Keyword(value) OR Keyword(value)

Historical data filtering

By default, OMEGAMON II collects all of the available data for each of the specified keywords. To limit the data that OMEGAMON II collects, you can specify a keyword followed by a value. You can also use the value with a not (¬) operator.



Not operator





In this example, the PLAN keyword is used with the asterisk (*) wildcard character. It specifies that OMEGAMON II will collect data for all plans that begin with the characters ABCD.

PLAN(ABCD*)




DB2ID(D??T)

Data Extraction Keyword DefinitionsThis table lists the keywords that are used as filters for information extracted from SMF, GTF, or from the D2 online collector. The keywords are listed and described in alphabetic order. Within this table, default values are underscored.

Table 3. Definitions of Data Extraction Keywords


ALTERDATABASE Directs OMEGAMON II to compare the number specified for this keyword to the number of ALTERDATABASE SQL statements in each record. If the condition in the ALTERDATABASE SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of ALTERDATABASE statements.

Integer.


ALTERINDEX Directs OMEGAMON II to compare the number specified for this keyword to the number of ALTERINDEX SQL statements in each record. If the condition in the ALTERINDEX SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of ALTERINDEX statements

Integer.


Data Extraction 69


ALTERSTOGROUP Directs OMEGAMON II to compare the number specified for this keyword to the number of ALTERSTOGROUP SQL statements in each record. If the condition in the ALTERSTOGROUP SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of ALTERSTOGROUP statements.

Integer.


ALTERSYNONYM Directs OMEGAMON II to compare the number specified for this keyword to the number of ALTERSYNONYM SQL statements in each record. If the condition in the ALTERSYNONYM SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of ALTERSYNONYM statements.

Integer.


ALTERTABLE Directs OMEGAMON II to compare the number specified for this keyword to the number of ALTERTABLE SQL statements in each record. If the condition in the ALTERTABLE SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of ALTERTABLE statements.

Integer.


ALTERTABLESPACE Directs OMEGAMON II to compare the number specified for this keyword to the number of ALTERTABLESPACE SQL statements in each record. If the condition in the ALTERTABLESPACE SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all data from all ALTERTABLESPACE statements.

Integer.


ALTERVIEW Directs OMEGAMON II to compare the number specified for this keyword to the number of ALTERVIEW SQL statements in each record. If the condition in the ALTERVIEW SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of ALTERVIEW statements.

Integer.


AUTHID The authorization ID about which OMEGAMON II should extract data. If this keyword is omitted, OMEGAMON II selects all data from all authorization IDs.

The 1- to 8-character authorization ID.


Table 3. Definitions of Data Extraction Keywords (continued)




BPID The buffer pool ID about which OMEGAMON II should extract data. This keyword is a filter for information extracted from SMF, GTF, or from the D2 online collector. If this keyword is omitted, OMEGAMON II selects all data from all buffer pool IDs.

The 1- to 12-character buffer pool ID.


CICSTRAN The CICS transaction ID about which OMEGAMON II should extract data. This keyword is a filter for information extracted from SMF, GTF, or from the D2 online collector. If this keyword is omitted, OMEGAMON II selects all data from all CICS transaction IDs.

The 1- to 12-character CICS transaction ID.


CLOSE Directs OMEGAMON II to compare the number specified for this keyword to the number of CLOSE SQL statements in each record. If the condition in the CLOSE SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of CLOSE statements.

Integer.


COMMIT The frequency with which inserts are committed to the DB2 tables. This keyword applies only when you extract historical data using insert mode.

CONNID The connection ID about which OMEGAMON II should extract data. This keyword is a filter for information extracted from from SMF, GTF, or from the D2 online collector. If this keyword is omitted, OMEGAMON II selects all data from all connection IDs.

The 1- to 8-character connection ID.


CONTYPE The connection type about which OMEGAMON II should extract data. This keyword is a filter for information extracted from from SMF, GTF, or from the D2 online collector. If this keyword is omitted, OMEGAMON II selects all data from all connection types.

Integer.


CORRID The correlation ID about which OMEGAMON II should extract data. This keyword is a filter for information extracted from SMF, GTF or from the D2 online collector. If this keyword is omitted, OMEGAMON II selects all data from all correlation IDs.

The 1- to 12-character correlation ID.




n A number ranging from 1 to 9999999.


Data Extraction 71


CORRNAME The name portion of the DB2 correlation identifier for which OMEGAMON II should extract data. This keyword is a filter for information to be extracted extracted from SMF, GTF, or from the D2 online collector. If this keyword is omitted, the extractor selects all data from all correlation names that were included in the source tables or datasets.

The 1- to 8-character connection type.


CPU The total amount of processor time about which OMEGAMON II should extract data. This keyword is a filter for information extracted from SMF, GTF or from the D2 online collector. If this keyword is omitted, OMEGAMON II selects all data from all CPU times.

The amount of CPU service units.


CREATEALIAS Directs OMEGAMON II to compare the number specified for this keyword to the number of CREATEALIAS SQL statements in each record. If the condition in the CREATEALIAS SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of CREATEALIAS statements.

Integer.


CREATEDATABASE Directs OMEGAMON II to compare the number specified for this keyword to the number of CREATEDATABASE SQL statements in each record. If the condition in the CREATEDATABASE SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of CREATEDATABASE statements.

Integer.


CREATEINDEX Directs OMEGAMON II to compare the number specified for this keyword to the number of CREATEINDEX SQL statements in each record. If the condition in the CREATEINDEX SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of CREATEINDEX statements.

Integer.






CREATEINDEX Directs OMEGAMON II to compare the number specified for this keyword to the number of CREATEINDEX SQL statements in each record. If the condition in the CREATEINDEX SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of CREATEINDEX statements.

Integer.


CREATETABLESPACE

Directs OMEGAMON II to compare the number specified for this keyword to the number of CREATETABLESPACE SQL statements in each record. If the condition in the CREATETABLESPACE SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of CREATETABLESPACE statements.

Integer.


CREATESYNONYM Directs OMEGAMON II to compare the number specified for this keyword to the number of CREATESYNONYM SQL statements in each record. If the condition in the CREATESYNONYM SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of CREATESYNONYM statements.

Integer.


CREATESTOGROUP Directs OMEGAMON II to compare the number specified for this keyword to the number of CREATESTOGROUP SQL statements in each record. If the condition in the CREATESTOGROUP SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of CREATESTOGROUP statements.

Integer.


CREATEVIEW Directs OMEGAMON II to compare the number specified for this keyword to the number of CREATEVIEW SQL statements in each record. If the condition in the CREATEVIEW SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of CREATEVIEW statements.

Integer.




Data Extraction 73


DB2CPU The amount of DB2 CPU time about which OMEGAMON II should extract data. This keyword is a filter for information extracted from SMF, GTF or from the D2 online collector. If this keyword is omitted, OMEGAMON II selects all data from all DB2 CPU times.

hh:mm

DBID The DB2 subsystem about which OMEGAMON II should extract data. This keyword is a filter for information extracted from SMF, GTF or from the D2 online collector. If this keyword is omitted, OMEGAMON II selects all data from all DB2 subsystems.

A 1- to 4-character DB2 subsystem identifier.


DB2TIME The accumulated amount of elapsed DB2 time about which OMEGAMON II should extract data. This keyword is a filter for information extracted from SMF, GTF or from the D2 online collector. If this keyword is omitted, OMEGAMON II selects all data from all elapsed DB2 times.

hh:mm

DBNAME The DB2 subsystem to which extracted data will be written. This keyword is required when writing to DB2 tables in insert mode.

A 1- to 4-character DB2 subsystem name.

DDLTAB The fully qualified DB2 table name in which OMEGAMON II saves the extracted audited DDL access trace data (audit class 3). The default DB2 table name is CANDLE.H2AUDIT_DDL.

A 1- to 8-character authorization ID concatenated with a DB2 table name, which can be up to 18 characters long. The fully qualified DB2 table name is 27 characters maximum.

DEADLOCKS Directs OMEGAMON II to compare the number specified for this keyword to the number of DEADLOCKS SQL statements in each record. If the condition in the DEADLOCKS SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of DEADLOCKS statements.

Integer.


DELETE Directs OMEGAMON II to compare the number specified for this keyword to the number of DELETE SQL statements in each record. If the condition in the DELETE SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of DELETE statements.

Integer.






DESCRIBE Directs OMEGAMON II to compare the number specified for this keyword to the number of DESCRIBE SQL statements in each record. If the condition in the DESCRIBE SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of DESCRIBE statements.

Integer.


DROPALIAS Directs OMEGAMON II to compare the number specified for this keyword to the number of DROPALIAS SQL statements in each record. If the condition in the DROPALIAS SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of DROPALIAS statements.

Integer.


DROPDATABASE Directs OMEGAMON II to compare the number specified for this keyword to the number of DROPDATABASE SQL statements in each record. If the condition in the DROPDATABASE SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of DROPDATABASE statements.

Integer.


DROPINDEX Directs OMEGAMON II to compare the number specified for this keyword to the number of DROPINDEX SQL statements in each record. If the condition in the DROPINDEX SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of DROPINDEX statements.

Integer.


DROPSTOGROUP Directs OMEGAMON II to compare the number specified for this keyword to the number of DROPSTOGROUP SQL statements in each record. If the condition in the DROPSTOGROUP SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of DROPSTOGROUP statements.

Integer.




Data Extraction 75


DROPSYNONYM Directs OMEGAMON II to compare the number specified for this keyword to the number of DROPSYNONYM SQL statements in each record. If the condition in the DROPSYNONYM SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of DROPSYNONYM statements.

Integer.


DROPTABLE Directs OMEGAMON II to compare the number specified for this keyword to the number of DROPTABLE SQL statements in each record. If the condition in the DROPTABLE SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of DROPTABLE statements.

Integer.


DROPTABLESPACE Directs OMEGAMON II to compare the number specified for this keyword to the number of DROPTABLESPACE SQL statements in each record. If the condition in the DROPTABLESPACE SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of DROPTABLESPACE statements.

Integer.


DROPVIEW Directs OMEGAMON II to compare the number specified for this keyword to the number of DROPVIEW SQL statements in each record. If the condition in the DROPVIEW SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of DROPVIEW statements.

Integer.


ELAPSED The accumulated amount of elapsed time about which OMEGAMON II should extract data. This keyword is a filter for information extracted from SMF, GTF or from the D2 online collector. If this keyword is omitted, OMEGAMON II selects all data from all elapsed times.

hh:mm

ENDDATE Directs OMEGAMON II to extract records within a range of dates ending in a specified end date. If this keyword is omitted, extraction will stop when the last record is encountered, as long as other time restrictions are not specified.

mm/dd/yy





ENDTIME Directs OMEGAMON II to extract records within a range of times ending in a specified end time. If this keyword is omitted, extraction will stop when the last record is encountered, as long as other time restrictions are not specified.

hh:mm

EXECUTE Directs OMEGAMON II to compare the number specified for this keyword to the number of EXECUTE SQL statements in each record. If the condition in the EXECUTE SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of EXECUTE statements.

Integer.


FETCH Directs OMEGAMON II to compare the number specified for this keyword to the number of FETCH SQL statements in each record. If the condition in the FETCH SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of FETCH statements.

Integer.


GETPAGE Directs OMEGAMON II to compare the number specified for this keyword to the number of GETPAGE SQL statements in each record. If the condition in the GETPAGE SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of GETPAGE statements.

Integer.


GRANT Directs OMEGAMON II to compare the number specified for this keyword to the number of GRANT SQL statements in each record. If the condition in the GRANT SQL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of GRANT statements.

Integer.


GROUP The datasharing group name for which OMEGAMON II should extract data. This keyword is a filter for information to be extracted extracted from SMF, GTF, or from the D2 online collector. If this keyword is omitted, the extractor selects all data from all datasharing groups that were included in the source tables or datasets.

The 1- to 8-character datasharing group identifier.




Data Extraction 77


HOSTNAME The hostname ID for which OMEGAMON II should extract data. This keyword is a filter for information to be extracted. If this keyword is omitted, the extractor selects all data from all hostname identifiers that were included in the source tables or datasets.

The 1- to 8-character hostname identifier.


IBINDS Directs OMEGAMON II to compare the number specified for this keyword to the number of IBINDS statements in each record. If the condition in the IBINDS statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of IBINDS statements.

Integer.


IFCID The IFCID number for which OMEGAMON II should extract data. This keyword is a filter for information to be extracted. If this keyword is omitted, the extractor selects all data from all IFCIDs that were included in the source tables or datasets.

Integer.


INSERT Directs OMEGAMON II to compare the number specified for this keyword to the number of INSERT statements in each record. If the condition in the INSERT statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of INSERT statements.

Integer.


JOBNAME The job name for which OMEGAMON II should extract data. This keyword is a filter for information to be extracted extracted from SMF, GTF, or from the D2 online collector. If this keyword is omitted, the extractor selects all data from all job names that were included in the source tables or datasets.

A 1- to 12-character job name.


LOAD The method by which the extracted trace data is stored in the DB2 table. If this keyword is omitted, the extracted trace data is stored using an SQL INSERT statement.

This keyword is ignored if you select WRITEOPTION(VSAM).



YES Specifies that the extracted trace data is saved into the DB2 table via the DB2 load utility.

NO Specifies that the extracted trace data is saved into the DB2 table using SQL INSERT statements.



LOCATION The location name for which OMEGAMON II should extract data. This keyword is a filter for information to be extracted. If this keyword is omitted, the extractor selects all data from all location names that were included in the source tables or datasets.

A 1- to 16-character location name.


LOCKTABLE Directs OMEGAMON II to compare the number specified for this keyword to the number of LOCKTABLE statements in each record. If the condition in the LOCKTABLE statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of LOCKTABLE statements.

Integer.


LUWID The logical unit of work ID for which OMEGAMON II should select data. This keyword is a filter for information to be extracted. If this keyword is omitted, the extractor selects all data from all logical units of work identifiers that were included in the source tables or datasets.

A 1- to 8-character logical unit of work ID.


MAXDEGREE Directs OMEGAMON II to compare the number specified for this keyword to the number of MAXDEGREE statements in each record. If the condition in the MAXDEGREE statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of MAXDEGREE statements.

Integer.


MEMBER The datasharing group member ID for which OMEGAMON II should extract data. This keyword is a filter for information to be extracted. If this keyword is omitted, the extractor selects all data from all datasharing group members that were included in the source tables or datasets.

A 1- to 8-character datasharing group member ID.


NETWORK ID The network ID about which OMEGAMON II should extract data. This keyword is a filter for information extracted from SMF, GTF or from the D2 online collector. If this keyword is omitted, OMEGAMON II selects all data from all network IDs.

A 1- to 8-character network ID.

See “Keyword syntax” on page 67 for examples of how to specify this value



Data Extraction 79


OPEN Directs OMEGAMON II to compare the number specified for this keyword to the number of OPEN statements in each record. If the condition in the OPEN statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of OPEN statements.

Integer.


ORIGAUTHID The original authorization ID for which OMEGAMON II should select data. This keyword is a filter for information to be extracted. If this keyword is omitted, the extractor selects all data from all original authorization ID names that exist in the input.

A 1- to 8-character original authorization ID.


OUTPUT The desired storage medium for historical data.

Note: When you use OUTPUT=DB2, you can write historical data to a DB2 database. To do this, an ODBC database driver must be installed. If your system is already configured with an ODBC database driver, OMEGAMON II for DB2 will use it for this purpose. Additionally, member PP.DB2.V810.SDSNAMP(DSNAOINI) needs to be configured. If your system is not configured with an ODBC database driver, please review the IBM documentation relating to configuring ODBC database drivers.

PACKAGE The package name for which OMEGAMON II should extract data. This keyword is a filter for information to be extracted. If this keyword is omitted, the extractor selects all data from all package names that were included in the source tables or datasets.

A 1- to 8-character package name identifier.


PERFORMANCE Directs OMEGAMON II to extract performance data, to be used by the application trace facility (ATF) or the OMEGAMON II for DB2 reporter. The data will be stored in the VSAM dataset specified in the extraction panel, in the H2VSAM ddname, or through the H2DATASET keyword.



DB2 DB2 tables or DB2 database.

DD Sequential datasets.

DB2LOAD

DELIMITED

Format used by DB2 LOAD utility.

Creates a comma-separated value output file

YES Extract performance data.

NO Do not extract performance data.



PGMSTART Directs OMEGAMON II to extract records within a range of times beginning with a specified program start time. If this keyword is omitted, extraction will stop when the last record is encountered, as long as other time restrictions are not specified.

hh:mm

PLANNAME The plan name about which OMEGAMON II should extract data. This keyword is a filter for information to be extracted. If this keyword is omitted, OMEGAMON II selects all data from all plan names.

The 1- to 8-character plan name.


PREPARE Directs OMEGAMON II to compare the number specified for this keyword to the number of PREPARE statements in each record. If the condition in the PREPARE statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of PREPARE statements.

Integer.


REVOKE Directs OMEGAMON II to compare the number specified for this keyword to the number of REVOKE statements in each record. If the condition in the REVOKE statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of REVOKE statements.

Integer.


ROLLBACK Directs OMEGAMON II to compare the number specified for this keyword to the number of ROLLBACK statements in each record. If the condition in the ROLLBACK statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of ROLLBACK statements.

Integer.


SELECT_COUNT Directs OMEGAMON II to compare the number specified for this keyword to the number of SELECT_COUNT statements in each record. If the condition in the SELECT_COUNT statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of SELECT_COUNT statements.

Integer.




Data Extraction 81


SETSQLID Directs OMEGAMON II to compare the number specified for this keyword to the number of SETSQLID statements in each record. If the condition in the SETSQLID statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of SETSQLID statements.

Integer.


SORTS Directs OMEGAMON II to compare the number specified for this keyword to the number of SORTS statements in each record. If the condition in the SORTS statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of SORTS statements.

Integer.


SPCALL Directs OMEGAMON II to compare the number specified for this keyword to the number of SPCALL statements in each record. If the condition in the SPCALL statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of SPCALL statements.

Integer.


SPTERM Directs OMEGAMON II to compare the number specified for this keyword to the number of SPTERM statements in each record. If the condition in the SPTERM statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of SPTERM statements.

Integer.


SPWAIT Directs OMEGAMON II to compare the number specified for this keyword to the number of SPWAIT statements in each record. If the condition in the SPWAIT statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of SPWAIT statements.

Integer.


SQLSTMTS Directs OMEGAMON II to compare the number specified for this keyword to the number of SQLSTMTS statements in each record. If the condition in the SQLSTMTS statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of SQLSTMTS statements.

Integer.






STARTDATE Directs OMEGAMON II to extract records within a range of dates starting with a specified start date. If this keyword is omitted, extraction will start with the first record, as long as other time restrictions are not specified.

mm/dd/yy

STARTTIME Directs OMEGAMON II to extract records within a range of times starting with a specified start time. If this keyword is omitted, extraction will start with the first record, as long as other time restrictions are not specified.

hh:mm

SYSID The MVS system ID for which OMEGAMON II should extract data. This keyword is a filter for information to be extracted. If this keyword is omitted, the extractor selects all data from all MVS system IDs that were included in the source tables or datasets.

The 1- to 4-character MVS system ID.


TCPIP The TC/PIP address for which OMEGAMON II should extract data. This keyword is a filter for information to be extracted. If this keyword is omitted, the extractor selects all data from all TC/PIP addresses that were included in the source tables or datasets.

The 1- to 8-character TC/PIP address.

See “Keyword syntax” on page 67 for examples of how to specify this value

TEMPTABLE Directs OMEGAMON II to compare the number specified for this keyword to the number of TEMPTABLE statements in each record. If the condition in the TEMPTABLE statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of TEMPTABLE statements.

Integer.


THREADSTART Directs OMEGAMON II to extract records within a range of times beginning with a specified thread start time. If this keyword is omitted, extraction will stop when the last thread is encountered, as long as other time restrictions are not specified.

hh:mm



Data Extraction 83


TIMEOPTION Determines whether to treat a specified start and end time as a continuous period of time or isolated periods of time within a date range.

TIMEOUTS Directs OMEGAMON II to compare the number specified for this keyword to the number of TIMEOUTS statements in each record. If the condition in the TIMEOUTS statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of TIMEOUTS statements.

Integer.


TOTALGROUPS Directs OMEGAMON II to compare the number specified for this keyword to the number of TOTALGROUPS statements in each record. If the condition in the TOTALGROUPS statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of TOTALGROUPS statements.

Integer.


UOWSTART Directs OMEGAMON II to extract records within a range of times beginning with a specified unit of work start time. If this keyword is omitted, extraction will stop when the last record is encountered, as long as other time restrictions are not specified.

hh:mm

UPDATE Directs OMEGAMON II to compare the number specified for this keyword to the number of UPDATE statements in each record. If the condition in the UPDATE statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of UPDATE statements.

Integer.




BAND Extract data in periods which begin after the start time and before the end time on each day selected.

RANGE Extract data continuously for the period starting on a specified date and time and ending at a specified date and time.



WAIT Directs OMEGAMON II to compare the number specified for this keyword to the number of WAIT statements in each record. If the condition in the WAIT statement is true, that record is extracted. If this keyword is omitted, OMEGAMON II selects all records without comparing the number of WAIT statements.

Integer.




Data Summarization 85

Data Summarization

This chapter describes data summarization.

Chapter ContentsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Data Summarization Customization Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Data Summarization Keywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Setting Summarization Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Data Summarization Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Historical data filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

4

Overview


Overview

The data summarizer enables you to consolidate detailed statistical and accounting data from DB2 tables or sequential datasets. The data is summarized according to a specified time interval and then is stored in either DB2 tables or in sequential datasets. This provides information that is useful in performance analysis, trending, or capacity planning, while reducing the amount of storage needed for historical data.

You can summarize historical data using the following time intervals:

� hourly summarization of detail data

� daily summarization of hourly or detail data

� weekly summarization of daily, hourly, or detail data

� monthly summarization of weekly, daily, hourly, or detail data

� yearly summarization of detail data

Most information within a summary interval (hourly, for example) is totaled, with the exception of high-water marks (maximum taken) and snapshot values (average taken).

You can also use the summarizer to copy data from one type of storage to another.


Data Summarization Customization Panels


Setting data summarization optionsYou can use the customization panels, accessed through the Historical Main Menu, to specify your data summarization options. These options remain in effect until they are changed.

You can also set or modify summarization options using keywords instead of the customization panels. See “Data Summarization Keywords” on page 89 for information on using keywords.

Online help


Accessing the customization panels

To access the summarizer customization panels through the OMEGAMON II ISPF dialog:

� Select SUMMARIZE from the Historical Reporting Main Menu.

Result: The Data Summarization Specifications panel appears.

Setting summarization specifications

The Data Summarization Specifications panel allows you to specify summarization options. This includes the level of detail for summarization, the date and time period of the summarization, the source and target for summarized data, and the DB2 subsystem to use if the source or target is DB2.

Specify either sequential datasets or DB2 tables as the source for data summarization or as the target destination to which the summarized data is written.

When you finish entering your specifications on this panel, press Enter to go to the Data Summarization Source panel.

Specify source for data summarization

The Data Summarization Source panel enables you to specify the names of the DB2 tables or sequential datasets from which data is summarized.

When you finish entering your specifications on this panel, press Enter to go to the Data Summarization Target panel.

Defining destination for summarized data

The Data Summarization Target panel enables you to specify the names of the DB2 tables or sequential datasets to which summarized data is written.

If DB2 tables names were changed from the defaults, you must specify the new table names on this panel.



If you want to retain the original statistics trace data, you can make the target table names different from the source table names. Check with your database administrator to make sure the new table names have been allocated.

When you finish entering your specifications on this panel, press Enter to go to the Summarization JCL Options panel.

Editing and submitting the job

The Summarization JCL Options panel creates the JCL for the summarizer, using the options you defined on the previous customization panels. Additionally, you can either edit the JCL or automatically submit the job.


Data Summarization Keywords


Setting Summarization Options

Using sample JCL

Data summarization keywords allow you to specify summarization options using sample JCL, or by modifying the summarization options members you created using the customization panels.

To specify summarization options using sample JCL, follow the instructions in rhilev.RKD2SAM(SUMMcccc), where cccc is the DB2 subsystem ID. You either can change the value of any keyword or use the default values.

Keyword syntax

The syntax of the data summarization keywords is as follows:

Keyword(value)

or

Keyword(value,value,value)

When a keyword accepts only one value, supply the value in parentheses after the keyword. When a keyword accepts multiple values, supply the values in parentheses after the keyword, separated by commas or spaces.

Define type of data to summarize

The keywords used to define the types of data to summarize are as follows:

� ACCOUNTING

� STATISTICS

Define how data is summarized

The keyword used to define how data is summarized is SUMTYPE.

Specify the CREATOR

The tables into which data is inserted are prefixed with an identifier of your choosing. The prefix is an eight-character identifier. The CREATOR keyword lets you specify this identifier. CANDLE is the default CREATOR.



Format of table names

Each table name is prefixed by the CREATOR identifier, followed by V1, followed by the name of the table, then by either the hour of the day, the day of the year, the month of the year, or the year.

For example,

CANDLE.V1_SMACCT_HOUR

where

– CANDLE - the CREATOR identifier. CANDLE is the default identifier.

– V1 - represents Version 1.

– SMACCT- the name of the generated table that contains accounting data.

– HOUR - data is summarized by hour. All data for a given hour is contained into one record. The format is yyyymmddhh.

– DAY - data is summarized by day. All data for a given day is contained into one record. The format is yyyymmdd00. Since hour does not apply, the hour field shows as two zeros.

– WEEK - data is summarized by week. All data for a given week is contained into one record. The format is yyyyww0000. Since hour and day do not apply, the hour and day fields show as zeros.

– MONTH - data is summarized by month. All data for a given month is contained into one record. The format is yyyymm0000. Since day and week do not apply, the day and week fields show as zeros.

– YEAR - data is summarized by year. All data for a given year is contained into one record. The format is yyyy000000. Since hour, day, and month do not apply, those fields show as zeros.

DB2 table names

The target DB2 table names are fixed. They cannot be modified. See “Format of table names” on page 90 for information on the table format. The tables generated for accounting and statistics data are as follows:

� CANDLE.V1_SMACCT_HOUR or /DAY or /WEEK or /MONTH or /YEAR

This table contains accounting data.

� CANDLE.V1_SMACCTBP_HOUR or /DAY or /WEEK or /MONTH or /YEAR

This table contains accounting buffer pool data.

� CANDLE.V1_SMACCTGBP_HOUR or /DAY or /WEEK or /MONTH or /YEAR

This table contains accounting group buffer pool data.

� CANDLE.V1_SMACCTPACK_HOUR or /DAY or /WEEK or /MONTH or /YEAR

This table contains accounting packages data.

� CANDLE.V1_SMACCTDDF_HOUR or /DAY or /WEEK or /MONTH or /YEAR



This table contains accounting distributed data facility information.

� CANDLE.V1_SMSTAT_HOUR or /DAY or /WEEK or /MONTH or /YEAR

This table contains statistics data.

� CANDLE.V1_SMSTATBP_HOUR or /DAY or /WEEK or /MONTH or /YEAR

This table contains statistics buffer pool data.

� CANDLE.V1_SMSTATGBP_HOUR or /DAY or /WEEK or /MONTH or /YEAR

This table contains statistics group buffer pool data.

� CANDLE.V1_SMSTATDDF_HOUR or /DAY or /WEEK or /MONTH or /YEAR

This table contains statistics distributed data facility information.

Define time options

The keywords used to define time options are as follows:

� STARTDATE

� ENDDATE

� STARTTIME

� ENDTIME

� SUMTYPE


The keywords used to define filtering and grouping options are as follows:

� AUTHID

� BPID

� CONNID

� CONTYPE

� CORRID

� CORRNAME

� DB2ID

� GROUP

� HOSTNAME

� LUWID

� MEMBER

� ORIGAUTH

� PACKAGE

� PLANNAME

� SYSID



� TCPIP

Miscellaneous keywords

Other miscellaneous keywords used with the data summarization function include:

� COMMIT

� DB2SYS

� DELDATA

Data Summarization Keyword DescriptionsThe following table lists the keywords associated with data summarization in alphabetic order and provides a complete description of each. Within this table default values are underscored.

Table 4. Descriptions of Data Summarization Keywords


ACCOUNTING Directs the summarizer to summarize accounting tables.

AUTHID The authorization ID for which the summarizer should select data. This keyword is a filter for information to be summarized. If this keyword is omitted, the summarizer selects all data from all authorization IDs that were included in the source tables or datasets. This keyword accepts multiple values and wildcard characters.

The 1- to 8-character authorization ID.

See “Historical data filtering” on page 99 for examples of how to specify this value.

BPID The buffer pool ID for which the summarizer should select data. This keyword is a filter for information to be summarized. If this keyword is omitted, the summarizer selects all data from all buffer pool IDs that were included in the source tables or datasets. This keyword accepts multiple values and wildcard characters.

A number representing a valid DB2 bufferpool identifier (0 – 49 or 80 – 89). May also be a string identifying a valid 32K bufferpool (32K, 32K1, 32K2, ..., 32K9).


COMMIT The frequency with which inserts are committed to the DB2 tables. If this keyword is omitted, OMEGAMON II will commit the data in the summarization table once for every 500 inserts.

YES Summarize accounting data.

NO Do not summarize accounting data.

n A number ranging from 1 to 9999999.




CONNID The connection ID for which the summarizer should select data. This keyword is a filter for information to be summarized. If this keyword is omitted, the summarizer selects all data from all connection IDs that were included in the source tables or datasets. This keyword accepts multiple values and wildcard characters.

The 1- to 8-character connection ID.


CONNTYPE The connection type for which the summarizer should select data. This keyword is a filter for information to be summarized. If this keyword is omitted, the summarizer selects all data from all connection types that were included in the source tables or datasets. This keyword accepts multiple values and wildcard characters.

The 1- to 8-character connection type.

See “Historical data filtering” on page 99 for examples of how to specify this value. See also “Filtering and Other Report Specifications” on page 152.

CORRID The correlation ID for which OMEGAMON II should select data. This keyword is a filter for information to be summarized. If this keyword is omitted, the summarizer selects all data from all correlation IDs that were included in the source tables or datasets. This keyword accepts multiple values and wildcard characters.

The 1- to 12-character correlation ID.


CORRNAME The name portion of the DB2 correlation identifier for which OMEGAMON II should select data. This keyword is a filter for information to be summarized. If this keyword is omitted, the summarizer selects all data from all correlation names that were included in the source tables or datasets. This keyword accepts multiple values and wildcard characters.

The 1- to 8-character name portion of the correlation ID.


DB2ID The DB2 subsystem about which OMEGAMON II should summarize data. This keyword is a filter for information during data summarization. If this keyword is omitted, OMEGAMON II selects all data from all DB2 subsystems that were included in the source tables or datasets. This keyword accepts multiple values and wildcard characters.

A list of 1- to 4-character DB2 subsystem names.


DELDATA Directs OMEGAMON II to delete source data upon completion of the summarization process. This keyword is applicable only when you specify SOURCE (DB2).

Table 4. Descriptions of Data Summarization Keywords (continued)


YES Delete source data.

NO Do not delete source data.



ENDDATE Directs OMEGAMON II to summarize records within a range of dates ending on a specified end date. If this keyword is omitted, summarization will stop when the last record is encountered, as long as other time restrictions are not specified.

mm/dd/yy

ENDTIME Directs OMEGAMON II to summarize records within a range of times ending at a specified end time. If this keyword is omitted, summarization will stop when the last record is encountered, as long as other time restrictions are not specified.

hh:mm

GROUP The name of the datasharing group for which OMEGAMON II should select data. This keyword is a filter for information to be summarized. If this keyword is omitted, the summarizer selects all data from all datasharing groups that were included in the source tables or datasets. This keyword accepts multiple values and wildcard characters.

A 1- to 8-character datasharing group ID.






GROUPBY Specifies how accounting data is to be grouped. This keyword accepts multiple arguments, for example, GROUPBY(CONNID, PLANNAME).

AUTHID Group by authorization ID.

BPID Group by buffer pool ID.

CONNID Group by connection ID.

CONTYPE Group by connection type.

CORRID Group by correlation ID.

DB2ID Group by DB2 subsystem ID.

GROUP Group by datasharing group name.

HOSTNAME Group by hostname ID.

LUWID Group by logical unit of work ID.

MEMBER Group by datasharing group member ID.

ORIGAUTHID Group by original authorization ID.

PACKAGE Group by package ID.

PLANNAME Group by plan name.

SYSID Group by MVS system ID.

TCPIP Group by TC/PIP address.

HOSTNAME The hostname ID for which OMEGAMON II should select data. This keyword is a filter for information to be summarized. If this keyword is omitted, the summarizer selects all data from all hostname identifiers that were included in the source tables or datasets. This keyword accepts multiple values and wildcard characters.

A 1- to 8-character hostname ID.






LUWID The logical unit of work ID for which OMEGAMON II should select data. This keyword is a filter for information to be summarized. If this keyword is omitted, the summarizer selects all data from all logical units of work identifiers that were included in the source tables or datasets. This keyword accepts multiple values and wildcard characters.

A 1- to 30-character logical unit of work ID.


MEMBER The datasharing group member ID for which OMEGAMON II should select data. This keyword is a filter for information to be summarized. If this keyword is omitted, the summarizer selects all data from all datasharing group members that were included in the source tables or datasets. This keyword accepts multiple values and wildcard characters.

A 1- to 8-character datasharing group member ID.


ORIGAUTH The original authorization ID for which OMEGAMON II should select data. This keyword is a filter for information to be summarized. If this keyword is omitted, the summarizer selects all data from all original authorization ID names that were included in the source tables or datasets. This keyword accepts multiple values and wildcard characters.

A 1- to 8-character original authorization ID.


PACKAGE The package name for which OMEGAMON II should select data. This keyword is a filter for information to be summarized. If this keyword is omitted, the summarizer selects all data from all package names that were included in the source tables or datasets. This keyword accepts multiple values and wildcard characters.

The 1- to 8-character package name.


PLANNAME The plan name for which OMEGAMON II should select data. This keyword is a filter for information to be summarized. If this keyword is omitted, the summarizer selects all data from all plan names that were included in the source tables or datasets. This keyword accepts multiple values and wildcard characters.

The 1- to 8-character plan name.


SOURCE Directs OMEGAMON II to summarize records from either the DB2 tables specified or from the sequential datasets specified.



DB2 DB2 table

DD Sequential dataset



STARTDATE Directs OMEGAMON II to summarize records within a range of dates starting with a specified start date. If this keyword is omitted, summarization will start with the first record, as long as other time restrictions are not specified.

mm/dd/yy

STARTTIME Directs OMEGAMON II to summarize records within a range of times starting with a specified start time. If this keyword is omitted, summarization will start with the first record, as long as other time restrictions are not specified.

hh:mm

STATISTICS Directs OMEGAMON II to summarize statistics trace data.

SUMTYPE Specifies the desired summarization interval.



YES Summarize statistics data.

NO Do not summarize statistics data.

HOUR Summarize detail data hourly.

DAY Summarize detail or hourly data daily.

WEEK Summarize detail, hourly, or daily data weekly.

MONTH Summarize detail, hourly, daily, or weekly data monthly.

YEAR Summarize detail, hourly, daily, weekly, or monthly data annually.

NONE Copy without any summarization. (For migration from DB2 tables to sequential datasets, or vice versa.)



SYSID The MVS system ID for which OMEGAMON II should select data. This keyword is a filter for information to be summarized. If this keyword is omitted, the summarizer selects all data from all MVS system IDs that were included in the source tables or datasets. This keyword accepts multiple values and wildcard characters.

The 1- to 4-character MVS system ID.


TCPIP The TC/PIP address for which OMEGAMON II should select data. This keyword is a filter for information to be summarized. If this keyword is omitted, the summarizer selects all data from all TC/PIP addresses that were included in the source tables or datasets. This keyword accepts multiple values and wildcard characters.

The 1- to 8-character TC/PIP address.






Historical data filteringBy default, OMEGAMON II collects all of the available data for each of the specified keywords. To limit the data that OMEGAMON II collects, you can specify a keyword followed by a value. You can also use the value with a not (¬) operator.

Not operator





In this example, the PLANNAME keyword is used with the asterisk (*) wildcard character. It specifies that OMEGAMON II will collect data for all plans that begin with the characters ABCD.

PLAN(ABCD*)




DB2ID(D??T)

For additional information regarding filtering, see “Filtering and Other Report Specifications” on page 152.

101

Part II: Creating Historical Reports

: . . . . . . . . .

IFCID-Based Reports 103

IFCID-BasedReports

This chapter describes the product-provided IFCID-based reports. See the README for instructions on generating these types of reports.

Chapter ContentsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Generating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

5

Overview


Overview

This chapter describes the IFCID-based historical reports available. See the README file for instructions on generating these IFCID-based reports.

Source dataThe IFCID-based reports use input data from sequential files that contain data generated by the online collector, the extractor, or the summarizer.

Report typesThe types of historical information you can report on are as follows:

� statistics� accounting� audit� DSNZPARM� performance� miscellaneous

For a description of each report type, see “Types of historical reports” on page 105.

IFCIDs supported

The IFCID-based reports contain information based on the IFCIDs that you selected while using the Extractor. All instrumentation record types (IFCIDs) are supported. When you specify an IFCID, the data extracted and inserted into tables applies to the type of data supported by that IFCID. The data extracted also depends upon the version of DB2 that you are running. See “Specify IFCIDs” on page 60 for a list of the supported IFCIDs.

Report formatAll reports within a report type (for example, Accounting) have some common features. This makes it easy to find information quickly on all reports of that type. For more information on report formats, see “Report format” on page 135.


Generating Reports

Generating Reports

Types of historical reportsUsing the sample product-provided library of COBOL and C (or C++) source programs, you can produce historical reports in print format. The types of historical information you can report on are as follows:

� statistics

� accounting

� audit

� DSNZPARM

� miscellaneous

Statistics reports

These reports provide information on a DB2 subsystem or DB2 subsystems in a data sharing environment. The reports are based on data gathered from statistics trace records generated at specified intervals. This includes information such as subsystem service activity levels and buffer pool statistics. See “IFCID-based Statistics Reports” on page 201.

Accounting reports

These reports provide information on application programs in a DB2 subsystem or DB2 subsystems in a data sharing environment. They can help you determine if a plan is the source of excessive resource utilization. With these reports, you can examine how the addition of or change to an application has affected DB2 and CPU time per commit, lock wait time and lock activity, and buffer manager activity. Available accounting reports are generated based on IFCID number 3 and its subtypes that you selected while using the Extractor. See “IFICD-based Accounting Reports” on page 181.

Audit reports

These reports provide information about auditable activity, including a record of unauthorized attempts to access audited objects and of attempts to change an object or execute a utility job.

DSNZPARM report

This report provides information about DB2 configuration parameters. “IFCID-based DSNZPARM Report” on page 205.

Miscellaneous

This report provides information about the Global Temporary Table. This data is generated from IFCID 62.

Generating Reports


Statistics reportsStatistics reports are based on information in the statistics trace. The statistics trace provides data on

� DB2 subsystem services

� pool usage

� SQL statements and DB2 commands issued

� logging and locking

Types of statistics reports

These are some of the statistics reports provided.

Accounting reportsAccounting reports provide thread-related information including

� the amount of time the thread spent executing in DB2

� accumulated CPU time

� buffer pool activity

� group buffer pool activity

� locking activity

� global locking activity

� resource limit facility activity

� SQL activity

� parallel task activity

Table 5. Statistics Reports

Report Name Description

Address Space Activity Displays information about the DB2 address spaces.

Buffer Pool Activity Displays all buffer pool statistics, including resources used, read, write, and request activity, and key ratios and percentages.

Use this report to view overall buffer pool activity and exceptions within a DB2 subsystem.

Command Activity Displays information about DB2 command activity.

Group Buffer Pool Activity Displays group buffer pool statistics.

Use this report to determine group buffer pool efficiency, and evaluate group buffer pool size, directory to data ratio, and castout thresholds.


Generating Reports

These reports provide information about the overall performance of DB2 application programs, and about how well DB2 resources are being utilized. In addition, they enable you to compare performance before and after application programs are modified or added. This can help detect applications that may start degrading performance.

Accounting class traces

Accounting reports use accounting class 1 trace data (classes 2 and 3 optional). The trace data is created when the corresponding accounting class traces are activated.

� Accounting class 1

Accounting class 1 provides elapsed time, buffer pool, locking information, information about the resource limit facility, and SQL information.

� Accounting classes 2 and 3 (optional)

Accounting classes 2 and 3 provide additional information, as indicated in the report descriptions in Table 6, “Accounting Reports,” on page 107. Sort and scan information is also provided if IFCIDs 95 and 96 (for sort data) and IFCID 15, 16, 17, and 18 (for scan data) were active at collection time.

� Accounting classes 7 and 8

Accounting classes 7 and 8 are necessary for generating the package level report.

Types of accounting reports

Accounting reports include:

Table 6. Accounting Reports

Report Names Description

Package and DBRM Detail

This report provides the user with a summary of activity that has occurred for all packages/DBRMs that have been executed by a thread.

This report provides information collected if accounting class 7 and 8 were active.

Buffer Pool Activity Displays information about the use of buffer pools by a thread or group of threads.

Use this report to determine read I/O activity and buffer pool efficiency.

Group Buffer Pool Activity

Displays information about global buffer pool activity for a thread or group of threads for a maximum of 60 buffer pools per data sharing group. Information includes the number of reads and read hit percentages.

Use this report to evaluate the size of the group buffer pool and to determine group buffer pool efficiency.

Lock Activity Displays information about locking activity.

Use this report to review the total number of deadlocks and timeouts that occurred, and to analyze whether these activities are within normal limits.

Generating Reports


DSNZPARM reportThe DSNZPARM report contains information about the DB2 installation parameters.

Type of DSNZPARM report

The DSNZPARM report is:

Global Lock Activity Displays global lock activity for a thread or group of threads in a data sharing group, including global lock requests, lock requests propagated to XES, and the number of false contentions.

Use this report to monitor the amount of data sharing global locking activity that occurred.

SQL Activity Displays the count of each type of SQL statement that was executed during the report interval.

Use this report to monitor the type and volume of SQL activity.

Distributed Data Facility Activity

Displays accounting information about the distributed data facility and communication between DB2 subsystems.

Use this report to monitor DDF activity between DB2 subsystems.

Accounting Package Detail

Displays accounting information about elapsed, CPU, and wait times at the program level.

Use this report to monitor activity by packages.

Table 7. DSNZPARM Reports


DB2 Configuration Parameters (DSNZPARM)

Displays the parameter settings for DB2 subsystem initialization, such as execution time values for the DB2 subsystem, pool sizes, logging and locking parameters, maximum batch/online threads, authorization settings, naming conventions, and usage of trace functions.

Use this report to monitor initial and current DSNZPARM parameter settings.

Table 6. Accounting Reports (continued)



Generating Reports

Audit reportsAudit reports contain data collected from DB2 audit trace records. Audit trace data provides a record of actions involving DB2 activity. This can be useful to DB2 subsystem administrators, security administrators, and EDP auditors. Recorded actions include:

� unauthorized attempts to access the audited objects

� attempts to execute utility jobs

� authorizations that have been granted to or revoked from users

Types of audit reports

Audit reports include:

Miscellaneous reportsCurrently, the Global Temporary Table is the only report in this category.

Table 8. Audit Reports


Authorization Failures Displays information about an operation that has failed DB2 authorization checking.

Use this report to determine which user tried to access a DB2 object or perform a DB2 function without authorization.

Authorization Control Displays information about a user who has been granted access to a DB2 object or function, or whose authorization to access the object or function has been revoked.

Use this report to determine who has been given authority to perform certain functions, and who has granted or revoked that authority.

Audited DDL Access Displays information about create, alter, or drop operations that have been performed.

Use this report to monitor data definition language (DDL) activity.

Audited DML Access Displays information about a table that has been read or changed within a unit of recovery for the first time.

Use this report to monitor tables that have changed or have been accessed as a result of any data manipulation language (DML) statement.

DML Statements at BIND

Displays information about a bind performed for a dynamic or static SQL statement.

Use this report to monitor plans when they are rebound, especially to monitor changes to production plans.

Generating Reports


Using the Historical Reporter Menu 111

Using the Historical Reporter Menu

This chapter describes how to use the Historical Reporter menu.

Chapter ContentsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Setting Reporter Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Historical reporter options menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Setting reporter specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Specifying Source Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Specifying source DB2 tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Specifying Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Specifying Date and Time Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Generating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Types of historical reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Using the report panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Statistics reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Accounting reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Audit reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126DSNZPARM report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Performance Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Input Reports Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Graphical Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Printing Reports in Batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Return codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Report format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

6

Overview


Overview

This chapter describes how you can create historical reports using the OMEGAMON II for DB2 Historical Reporter. To assist you in creating these reports, you can use the Historical Reporter Menu. This menu is available through the OMEGAMON II ISPF dialog. The information that you provide through these panels generates the JCL required to run your reports.

This chapter describes how to do the following tasks through the Historical Reporter Menu:

� set reporter options

� select the reports you want to generate

� print reports in batch

Note: To perform these tasks using the report request language and writing your own JCL, see “Using the Report Request Language” on page 139.

Source dataThe Historical Reporter uses input data from any of the following sources:

� DB2 tables

Contain data generated by the online collector, extractor, or summarizer.

� Historical VSAM or archived datasets

Contain data generated by the online collector, extractor, summarizer, or from ATF capture.

� SMF (active or archived) datasets

Contain trace data generated by DB2.

� GTF datasets


Report typesThe six types of historical information you can report on are as follows:

� statistics� accounting� audit� DSNZPARM� performance� input



Overview

Accessing the Historical Reporter MenuTo access the Historical Reporter Menu:

� Select Report from the Historical Main Menu

Result: The Historical Reporter Menu appears.

For information on how to access the Historical Main Menu, see “Accessing Historical Functions” on page 37.

Historical Reporter MenuThe Historical Reporter Menu provides access to panels where you can set reporter options and generate historical reports. It also allows you to select historical reports to submit in a batch report job. The Graphics option provides access to online graphs of statistics and accounting information.

Setting Reporter Options



Historical reporter options menuThe Historical Report Options Menu allows you to specify reporting options, which control the data on the reports that you print.

You can specify the following reporting options:

You can also access these options by entering the appropriate command (SPECS, SOURCE, TABLES, SELECT, DATE) on the Command line of any historical reporter panel.

Accessing historical reporter options

To access the Historical Reporter Options Menu:

� Select Options from the Historical Reporter Menu.

Result: The Historical Reporter Options Menu appears.

Confirm or cancel options

After specifying your options on any panel you access through the Historical Reporter Options menu, perform one of the following actions:

� Press Enter to save the options and return to the Historical Reporter Options Menu.

or

� Press End to cancel any changes you made to the options panel.

Once you save reporter options, they remain in effect from one OMEGAMON II historical session to another.

Online help


Specifications General reporting options (for example, Group by and date format).

Source Input datasets to use for reporting.

Tables Input DB2 tables to use for reporting.

Selections Filtering criteria (for example, DB2 IDs and plan names) to use for reporting.

Date/Time Date and time criteria (for example, date ranges) to use for reporting.



Setting reporter specificationsThis panel allows you to specify how report information is grouped, how it is sorted, and which input source (datasets or DB2 tables) to use for the reports.

Accessing historical reporter specifications

To access the Historical Reporter Specifications panel:

� Select Specifications from the Historical Reporter Options Menu.

Or, enter SPECS on the Command line of any historical panel.

Result: The Historical Reporter Specifications panel appears.

The Use DB2 tables for input field specifies whether the source data for the reports comes from the datasets you specify on the Historical Reporter Source Datasets panel or from the DB2 tables you specify on the Historical Reporter Source DB2 Tables panel. See “Specifying Source Datasets” on page 116 and “Specifying source DB2 tables” on page 116 for information about these panels.

Note: For reports run at the same time, the source data must be from either DB2 tables or from source datasets, but not from both.

Reporter options

You can set the following reporter options from this panel:

Date display format

Specifies the format (U for USA, E for European, I for ISO, J for Japanese, A for American) in which dates and times are displayed on the report. Refer to “Output Specification” on page 162 for a description of these formats.

Use DB2 tables for input

Specifies whether DB2 tables (Y) or specified datasets (N) are to be used as input for the reports.

Group by Specifies the elements (HOUR, DAY, DB2ID, PLANNAME, CONNID, CORRID, AUTHID, ORIGAUTH, THREAD, PROGRAM, UOW, SYSID, LUWID, GROUP, MEMBER) by which information is grouped on the report, and where control breaks will occur.

For example, to identify application programs that are causing poor performance and to identify users running those programs, you would group by PLANNAME and AUTHID. A control break occurs for each PLANNAME and AUTHID pair in the table; all information for a unique pair is combined and presented as one entry.

Order by Specifies the elements (TIME, DB2ID, PLANNAME, CONNID, CORRID, AUTHID, ORIGAUTH, SYSID, LUWID, GROUP, MEMBER) by which information is ordered on the report.

Values Specifies the data values that display on a report. (T for total value, C for average value per commit, H for average value per thread)

Note: When you specify PERCOMMIT or PERTHREAD, the Package Detail report shows averages computed per package invocation within the group.



Specifying Source DatasetsThis panel allows you to specify the collection method and up to 12 datasets that the reporter will read to produce historical reports.

The values you specify on this panel are valid only if you chose datasets as your input source on the Historical Reporter Specifications panel. If you did not, these values are ignored.

Types of source datasets

The datasets you specify can be one of the following types:� H2X datasets

Contain data from the OMEGAMON II collector, extractor, or summarizer, or from ATF capture, in VSAM or QSAM (archived).

� SMF datasets

Contain DB2 trace data, in VSAM or QSAM (archived).

� GTF datasets

Contain DB2 trace data.

Accessing the source datasets specifications

To access the Historical Reporter Source Datasets panel:

� Select Source from the Historical Reporter Options Menu.

Or, enter SOURCE on the Command line of any historical panel.

Result: The Historical Reporter Source Datasets panel appears. Enter the dataset type and the name (or names) of the datasets in which the data resides. Use single quotes around the dataset name if it is fully qualified. If you do not use single quotes, TSO adds the prefix that has been specified for your profile.

Press Enter to process your entries and return to the Historical Reporter Options Menu.

Specifying source DB2 tablesThis panel allows you to specify the DB2 tables that the reporter will read to produce historical reports. These tables contain historical data generated by the OMEGAMON II collector, extractor, or summarizer.

The values you specify on this panel are valid only if you chose DB2 tables as your input source on the Historical Reporter Specifications panel. If you did not, these values are ignored.

Accessing source DB2 table specifications

To access the Historical Reporter Source DB2 Tables panel:

� Select Tables from the Historical Reporter Options Menu.

Or, enter TABLES on the Command line of any historical panel.

Result: The Historical Reporter Source DB2 Tables panel appears.



Specify the DB2 subsystem and enter the names of the DB2 tables containing the source data for each report you want to produce.

Note: Since performance data does not reside in DB2 tables, you cannot use DB2 tables as input to generate performance reports.


Specifying Selection CriteriaThis panel allows you to specify the selection criteria that will filter the data that appears on historical reports.

Some select elements are applicable only to certain reports. When you specify multiple reports, the elements that do not apply to a particular report are ignored. See the detailed report descriptions in Part III: ”OMEGAMON II for DB2 Reports” on page 179 for a list of the select elements that apply to each report.

Accessing selection criteria

To access the Historical Reporter Selection Criteria panel:

� Select Selections from the Historical Reporter Options Menu.

Or, enter SELECT on the Command line of any historical panel.

Result: The Historical Reporter Selection Criteria panel appears.


Filtering selection criteria

You can filter values for any character field (PLAN, OAUTH, and any field ending in ID) on the Historical Reporter Selection Criteria panel by using operators and wildcard characters.

� Operators

To filter data with an operator, specify one of the operators shown on this panel, followed by a value.

For example, if you enter ¬= IM3D I210 at the CONNID field, data is selected for all connection IDs, except those specified. For descriptions of the operators shown, refer to“Selection Specification” on page 155.

� Wildcard characters

You can also filter data by specifying wildcard characters. You can use the wildcard character * (asterisk) at the end of a value, which causes all data that matches characters before the asterisk to be selected.

For example, if you enter = IM3* at the CONNID field, data for all connections whose IDs begin with IM3 will be selected.

The wildcard character ? (question mark) replaces any single character within a value.



Specifying Date and Time CriteriaThis panel enables you to specify the reporting period for historical reports.

Accessing date and time criteria

To access the Date/Time Criteria panel:

� Select Date/Time from the Historical Reporter Options Menu.

Result: The Date/Time Criteria panel appears.

Rules

The following rules apply to setting date and time criteria:

� You can omit leading zeros from month, day, or hour.

� If you omit the year, it defaults to the current year.



Generating Reports

Generating Reports

Types of historical reportsUsing the Historical Reporter Menu, you can produce historical reports in both print and online format. The six types of historical information you can report on are as follows:

� statistics

� accounting

� audit

� DSNZPARM

� performance

� input

In addition, online graphics for various statistics and accounting data are available if you have GDDM installed at your site.

Online help


Statistics reports

These reports provide information on a DB2 subsystem or DB2 subsystems in a data sharing environment. The reports are based on data gathered from statistics trace records generated at specified intervals. This includes information such as subsystem service activity levels and buffer pool statistics.

Accounting reports

These reports provide information on application programs in a DB2 subsystem or DB2 subsystems in a data sharing environment. They can help you determine if a plan is the source of excessive resource utilization. With these reports, you can examine how the addition of or change to an application has affected DB2 and CPU time per commit, lock wait time and lock activity, and buffer manager activity. Available accounting reports are generated from DB2 accounting class 1, 2, 3, 7 and 8 trace data.

Audit reports

These reports provide information about auditable activity, including a record of unauthorized attempts to access audited objects and of attempts to change an object or execute a utility job.

DSNZPARM reports

These reports provide information about DB2 configuration parameters.

Generating Reports


Performance reports

These reports provide detailed information about various events in a DB2 subsystem or DB2 subsystems in a data sharing environment, such as lock and I/O requests. They are based on DB2 performance traces. With these reports, you can perform application or DB2 subsystem-related tuning.

Input report

This report provides information about the number and types of input records found in all of the input files, as well as the date-time ranges of those records, by DB2 subsystem.

Graphical reports

These reports provide a graphical view of DB2 subsystem and application activity, both on a detail and a summary level, for statistics and accounting data.

Using the report panelsYou can print or view historical reports using the report panels accessed through the Historical Reporter Menu.

When you select a report category on the Historical Reporter Menu, a panel appears listing all the reports available in that category.

For any report, you can

� show the report online

� print the report

� display help for the report

� submit the report as a batch job

Note: You must specify your reporting options before you generate reports. See “Setting Reporter Options” on page 114 for this information.

Action codes

The following describes the action codes you can use on any report panel:B

Using action codes

To use an action code on a report panel:

� Enter the action code next to the report name, and press Enter.

S Generates a report and shows it online.

P Generates a report and prints it.

H Displays online help about a report.

For navigation assistance within the help facility, press PF1 on any help panel. Navigation conventions for the ISPF help tutorial are displayed.

B Selects one or more reports for submission as a batch job. See “Printing Reports in Batch” on page 133 for more information.


Generating Reports

Statistics reportsStatistics reports are based on information in the statistics trace. The statistics trace provides data on


� pool usage


� logging and locking

Accessing statistics reports

To access the list of statistics reports you can generate:

� Select Statistics from the Historical Reporter Menu.

Result: The Statistics Reports panel appears.

Report options

You can create reports in detail or summary format. Use the groupby specification (explained under “Report request language” on page 143) to summarize the data as you require.

Types of statistics reports

These are some of the statistics reports provided.

Table 9. Statistics Reports


Statistics Summary Displays a summary of the most important DB2 subsystem statistics information, including SQL activity, resource usage, key I/O ratios, and exceptions. Use this report for an overview of the entire DB2 subsystem.

Statistics Detail Displays detailed information for all types of statistics activity (including buffer pool, EDM pool, subsystem, CPU, log, lock, command, bind, and RID pool activity).

Use this all-purpose report for complete information about resource utilization and the performance of your DB2 subsystem.

Statistics CPU Time Summary

Displays a summary of CPU usage information about the DB2 address spaces.

Subsystem Activity Displays the subsystem service statistics, including thread creation, queuing at create thread time, identity, signon, and termination. This report also provides counts of commits, aborts, recovery indoubt situations (including those resolved successfully), subsystem allied memory EOM and EOT conditions, and system event checkpoints.

Use this report to examine the overall service activity level for a DB2 subsystem.

Generating Reports


Buffer Pool Activity Displays all buffer pool statistics, including resources used, read, write, and request activity, and key ratios and percentages.

Use this report to view overall buffer pool activity and exceptions within a DB2 subsystem.

Group Buffer Pool Activity Displays group buffer pool statistics.

Use this report to determine group buffer pool efficiency, and evaluate group buffer pool size, directory to data ratio, and castout thresholds.

EDM Pool Activity Displays EDM pool statistics including the percentage of environment descriptor requests satisfied from within the pool without reading from DASD. This report also provides information about usage of the EDM pool, broken down by pool elements: database descriptors (DBDs), cursor tables (CTs), skeleton cursor tables (SKCTs), package tables (PTs), and skeleton package tables (SKPTs).

Use this report to examine the status of the EDM pool for a DB2 subsystem.

Log Activity Displays log manager statistics including read and write activity to both active and archive logs and activity against the bootstrap datasets.

Use this report to monitor the current and archive logging activity for a DB2 subsystem.

Lock Activity Displays information about locking activity for a DB2 subsystem. This information includes the number and type of suspensions, deadlock and timeout conditions, lock escalations, and lock manager requests.

Use this report to examine locking activity in a DB2 subsystem.

Global Lock Activity Displays information about global locking activity for a DB2 member in a data sharing group. Information includes the number of lock requests, the number of lock requests propagated to XES, and the number of false contentions.

Use this report to determine whether the size of the lock structure is appropriate, and to determine whether values for lock requests propagated to XES and false contentions are too high.

SQL Activity Displays statistics about manipulative (DML), control (DCL), definitional (DDL) SQL statements, rid pool access, query parallelism, and stored procedure activity.

Use this report to review the SQL activity within a DB2 subsystem.

Command Activity Displays statistics about DB2 command activity.

Use this report to examine DB2 command activity for the DB2 subsystem.

Table 9. Statistics Reports (continued)



Generating Reports

Accounting reportsAccounting reports provide thread-related information including

� the amount of time the thread spent executing in DB2

� accumulated CPU time


� group buffer pool activity

� locking activity

� global locking activity

� resource limit facility activity

� SQL activity

� parallel task activity

These reports provide information about the overall performance of DB2 application programs, and about how well DB2 resources are being utilized. In addition, they enable you to compare performance before and after application programs are modified or added. This can help detect applications that may start degrading performance.

Accessing accounting reports

To access the list of accounting reports you can generate:

� Select Accounting from the Historical Reporter Menu.

Result: The Accounting Reports panel appears.

Bind Activity Displays statistics about automatic binds, static binds, rebinds, and free plans. The statistics include the total number of attempts, the number of successful attempts, and the number of unsuccessful attempts.

Use this report to gather bind statistics for a DB2 subsystem.


Displays statistics about the distributed data facility and communication between DB2 subsystems.

Use this report to gather DDF statistics about interaction with another DB2 subsystem, and to evaluate DBAT-related DSNZPARM parameters.

Open/Close Activity Displays statistics about database open and close activity, such as the number of opens and closes of datasets, and deferred close activity.

Use this report to examine open/close activity within a DB2 subsystem.

Table 9. Statistics Reports (continued)


Generating Reports


Accounting class traces

Accounting reports use accounting class 1 trace data (classes 2 and 3 optional). The trace data is created when the corresponding accounting class traces are activated.

� Accounting class 1

Accounting class 1 provides elapsed time, buffer pool, locking information, information about the resource limit facility, and SQL information.

� Accounting classes 2 and 3 (optional)

Accounting classes 2 and 3 provide additional information, as indicated in the report descriptions in Table 10, “Accounting Reports,” on page 124. Sort and scan information is also provided if IFCIDs 95 and 96 (for sort data) and IFCID 15, 16, 17, and 18 (for scan data) were active at collection time.

� Accounting classes 7 and 8

Accounting classes 7 and 8 are necessary for generating the package level report.

Report options

Each report can be generated in detail or summary format, depending on the groupby specification and the input dataset (detailed or summarized data). Use the groupby specification (explained under “Report request language” on page 143) to summarize the data as you require.

Types of accounting reports

Accounting reports include:

Table 10. Accounting Reports


Accounting Summary Displays summary information about the most important thread activity and performance. You can specify multiple groupby variables, which determine how the data is summarized.

Use this report to track resource utilization and detect potential problem areas that may require further investigation.

Accounting Detail Displays detailed information for all types of accounting activity (including time summary, buffer pool, lock, SQL, sort, scan, RID pool, and parallel task activity).

Use this report for complete information about the performance of your DB2 applications and the utilization of DB2 resources.


Generating Reports

Time Summary Displays time-related information about a thread or group of threads. The report includes elapsed time, CPU time, in-DB2 times, and wait times.

This report requires accounting trace class 1 to produce elapsed time information, accounting trace class 2 to produce in-DB2 time information, and accounting trace class 3 to produce wait time information.

Use this report to determine if any of these times are excessive, requiring further investigation.

Buffer Pool Activity Displays information about the use of buffer pools by a thread or group of threads.

Use this report to determine read I/O activity and buffer pool efficiency.


Displays information about global buffer pool activity for a thread or group of threads for a maximum of 60 buffer pools per data sharing group. Information includes the number of reads and read hit percentages.

Use this report to evaluate the size of the group buffer pool and to determine group buffer pool efficiency.

Lock Activity Displays information about locking activity.

Use this report to review the total number of deadlocks and timeouts that occurred, and to analyze whether these activities are within normal limits.

Global Lock Activity Displays global lock activity for a thread or group of threads in a data sharing group, including global lock requests, lock requests propagated to XES, and the number of false contentions.

Use this report to monitor the amount of data sharing global locking activity that occurred.

SQL Activity Displays the count of each type of SQL statement that was executed during the report interval.

Use this report to monitor the type and volume of SQL activity.

Sort Activity Displays information about thread sort activity. Information for this report is derived from IFCIDs 95 and 96.

Use this report to monitor sort activity that can cause high CPU overhead.

Parallel Task Activity Displays information about parallel tasks that were created for a thread.

Use this report to monitor amount and effectiveness of CPU parallelism.



Generating Reports


Audit reportsAudit reports contain data collected from DB2 audit trace records. Audit trace data provides a record of actions involving DB2 activity. This can be useful to DB2 subsystem administrators, security administrators, and EDP auditors. Recorded actions include:

� unauthorized attempts to access the audited objects

� attempts to execute utility jobs

� authorizations that have been granted to or revoked from users

Accessing audit reports

To access the list of audit reports you can generate:

� Select Audit from the Historical Reporter Menu.

Result: The Audit Reports panel appears.

Report options

With the exception of the Audit Summary report, audit reports contain event data and allow only filtering (Select When). See “Specifying Selection Criteria” on page 117 for more information on filtering options.

Scan Activity Displays information about thread scan activity. Information for this report is derived from IFCID 18.

Use this report to monitor scan activity that can cause high CPU overhead.

Termination Summary Displays summary information about application terminations for a group of threads.

Use this report to review the number of normal and abnormal application terminations and units of work indoubt.

Resource Limit Activity Displays information about resource limit facility usage and activity, including the highest amount of CPU time used and the number of times that each thread exceeded the maximum CPU time limit.

Use this report to determine which applications are using large amounts of CPU. This report can also help you decide how to adjust the resource limit for an application.


Displays accounting information about the distributed data facility and communication between DB2 subsystems.

Use this report to monitor DDF activity between DB2 subsystems.


Displays accounting information about elapsed, CPU, and wait times at the program level.

Use this report to monitor activity by packages.




Generating Reports

Types of audit reports

Audit reports include:

Table 11. Audit Reports


Audit Summary Displays the total number of times a user has triggered an audit record to be generated by DB2.

Use this report to track audit activity and detect potential problem areas that may require further investigation.

Authorization Failures Displays information about an operation that has failed DB2 authorization checking.

Use this report to determine which user tried to access a DB2 object or perform a DB2 function without authorization.

Authorization Control Displays information about a user who has been granted access to a DB2 object or function, or whose authorization to access the object or function has been revoked.

Use this report to determine who has been given authority to perform certain functions, and who has granted or revoked that authority.

Audited DDL Access Displays information about create, alter, or drop operations that have been performed.

Use this report to monitor data definition language (DDL) activity.

Audited DML Access Displays information about a table that has been read or changed within a unit of recovery for the first time.

Use this report to monitor tables that have changed or have been accessed as a result of any data manipulation language (DML) statement.

DML Statements at BIND

Displays information about a bind performed for a dynamic or static SQL statement.

Use this report to monitor plans when they are rebound, especially to monitor changes to production plans.

Authorization ID Change

Displays information about an authorization ID that has been changed by a SET CURRENT SQLID command, a new IMS™ or CICS™ signon, an IMS, CICS, or TSO IDENTIFY request, or inbound or outbound distributed data requests.

Use this report to detect possible security violations during the execution of any transaction or program.

Utility Access Displays information about DB2 utility jobs that have been performed.

Use this report to monitor utility jobs that could affect the content of DB2 tables.

Generating Reports


DSNZPARM reportThe DSNZPARM report contains information about the DB2 installation parameters.

Accessing DSNZPARM reports

To access the list of DSNZPARM reports you can generate:

� Select DSNZPARM from the Historical Reporter Menu.

Result: The DSNZPARM Reports panel appears.

Type of DSNZPARM report

The DSNZPARM report is:

Performance ReportsPerformance reports provide comprehensive information on DB2 system events such as lock and I/O requests, and in a data sharing environment, global lock suspensions, P-lock, and page P-lock activity. They can assist you in tuning your application or DB2 subsystem.

Performance reports are based on detailed DB2 performance trace records. Each set of reports requires that a corresponding set of performance trace IFCIDs are available to use as report input. Part III: ”OMEGAMON II for DB2 Reports” on page 179 explains the IFCID requirements in detail.

Accessing performance reports

To access the list of performance reports you can generate:

� Select DSNZPARM from the Historical Reporter Menu.

Result: The Performance Reports panel appears.

Table 12. DSNZPARM Reports


DB2 Configuration Parameters (DSNZPARM)

Displays the parameter settings for DB2 subsystem initialization, such as execution time values for the DB2 subsystem, pool sizes, logging and locking parameters, maximum batch/online threads, authorization settings, naming conventions, and usage of trace functions.

Use this report to monitor initial and current DSNZPARM parameter settings.


Generating Reports

Types of performance reports

Performance reports include:

Table 13. Performance Reports


Application Trace Summary

Displays an overview of DB2 trace information about an application at the thread, unit of work, or program level.

Use this report for an overview of information collected from an application trace, or to determine which threads require further analysis.

Application Trace Detail Displays application resource use at the thread, unit of work, or program level. Information is broken down into these categories: SQL Summary, Sort Summary, Scan Summary, Lock Summary, Buffer Pool Access Summary, Stored Procedure Summary, and Parallel Processing Summary.

Use this report to determine resource usage and activity within an application.

Application SQL Trace Displays summary information for each SQL activity that occurred for each thread that was active within the reporting period.

Use this report to look at SQL flow within an application, and the performance of individual SQL statements.

Application Event Trace Displays detailed information about an application. This information appears as a series of events, with each entry representing a single event or action. This report also provides computed data for record pairs such as elapsed and CPU times for matched events.

Depending upon filtering specifications, you can use this report to obtain information about application flow, lock activity, I/O activity, and access path processing.

Application Buffer Pool Access

Displays information about the logical (page) access to buffer pools from an application point of view.

Use this report to determine volume and type of activity and/or I/O performance for DB2 pagesets, or to determine trends in volume or performance related to I/O activity.

Application Buffer Pool I/O

Displays information about buffer pool I/O activity at the database or pageset level.

Use this report to determine volume, type of I/O activity, or I/O performance for a specific application. You can also determine trends in these areas.

System Buffer Pool Access

Displays information about logical (page) accesses to DB2 buffer pools from a system point of view.

Use this report to determine volume and type of activity and/or I/O performance for DB2 pagesets, or to determine trends in volume or performance related to I/O activity.

Generating Reports


Input Reports MenuThe input report provides summary counts for each record type and IFCID found in the input dataset. It also shows the first and last timestamps per DB2 subsystem for which input records exist. This allows you to determine if your dataset contains the necessary trace records to generate the reports you want.

Accessing input reports

To access the list of input reports you can generate:

� Select Input from the Historical Reporter Menu.

System Buffer Pool I/O Displays information about buffer pool I/O activity at the database or pageset level.

Use this report to determine volume, types of I/O activity, or I/O performance for the DB2 subsystem. You can also determine trends in volume or performance related to I/O activity.

EDM Pool I/O Activity Displays information about EDM pool I/O activity at the object level.

Use this report to determine the EDM object requests resulting in I/O for a specific application or for the DB2 subsystem. You can also determine trends in these areas.

Lock Suspension Displays a summary of lock suspensions that have occurred.

Use this report to determine the frequency, type, and duration of lock suspensions and the resources involved.

Lock Contention Displays all timeouts and deadlocks that have occurred.

Use this report to monitor the frequency and type of lock contentions occurring, and the resources involved.

Global Lock Suspensions

Displays a summary of global lock suspensions in a data sharing environment.

Use this report when running in a data sharing environment to determine the frequency, type, and duration of lock suspensions and the resources involved.

P-Lock Detail Displays information related to pageset P-lock and page P-lock activity in a data sharing environment. It provides detailed locking activity on an object or set of objects, and information about global locking events on a resource.

Use this report to investigate inter-DB2 object access.

System Event Trace Displays the contents of performance trace records. This report also provides computed data for record pairs such as elapsed and CPU times for matched events.

Use this report to display the contents of desired performance trace records.

Table 13. Performance Reports (continued)



Generating Reports

Result: The Input Reports panel appears.

Types of input reports

Input reports include:

Graphical ReportsGraphical reports display online accounting and statistics data in graphical format. They provide an overall graphical summary of DB2 subsystem and application activity.

You can use these graphs to detect potential problems in subsystem usage, or problems resulting from the addition or modification of applications over time. Then you can use statistics or accounting reports to further investigate a specific time period or application.

Accessing graphical reports

To access the list of graphical reports you can generate:

� Select Graphical from the Historical Reporter Menu.

Result: The Graphical Reports panel appears.

Software requirements

Following are the program products required to support DB2 graphics.

� Graphical Data Display Manager (GDDM)

� GDDM Presentation Graphics Facility (PGF)

Table 15, “Graphical Reports,” on page 132 lists the graphical accounting and statistics reports.

Table 14. Input Reports


Input Record Summary Displays a summary count of records by record type and by IFCID type.

Use this report to identify file contents.

Input Record Trace Displays a 1- or 2- line summary of each of the input records found in all of the input files. It also provides a summary of the number and types of input records found in all of the input files, as well as the date-time ranges of those records by DB2 subsystem.

This report is used for serviceability purposes.

Input Record Dump Displays a full hexadecimal and character dump of the input records found in all of the input files. It also provides a summary of the number and types of input records found in all of the input files, as well as the date-time ranges of all of those records by DB2 subsystem.


Generating Reports


Types of graphical reports

Graphical accounting and statistics reports include:

Table 15. Graphical Reports


Hourly Thread Activity Displays the number of commits, signons, and create thread requests, grouped by hour.

Address Space CPU Analysis

Displays the CPU percentage of each of the DB2 address spaces, grouped by statistics intervals.

CT Load Analysis Displays the number of cursor table requests and EDM pool loads, grouped by statistics intervals.

DBD Load Analysis Displays the number of DBD requests and EDM pool loads, grouped by statistics intervals.

Deadlock/ Timeout Analysis

Displays the number of deadlocks and timeouts, grouped by statistics intervals.

Pageset Open Activity Displays the number of open datasets for each buffer pool, grouped by statistics intervals.

EDM Pool Usage Analysis Displays statistics about EDM pool use, including the number of CTs, DBDs, SKCTs, and free pages, grouped by statistics intervals.

Getpages Per Commit Displays the ratio of getpages to commits and read I/Os to commits, grouped by statistics intervals.

Getpage Activity by Hour Displays the number of getpages and read I/Os, grouped by hour.

Lock Suspension Analysis

Displays the number of lock suspensions and commits, grouped by statistics intervals.

In-DB2 Time Per Commit Displays the average amount of in-DB2 time per commit. In-DB2 time is the time accumulated when the thread is executing in DB2.

In-DB2 CPU Time Per Commit

Displays the average amount of in-DB2 CPU time per commit. In-DB2 CPU time is the CPU time accumulated when the thread is executing in DB2.

I/O Wait Time Per Commit

Displays the average I/O wait time per commit. I/O wait time is the time the thread spent waiting for I/O to occur.

Lock Wait Time Per Commit

Displays the average lock wait time per commit. Lock wait time is the time the thread spent waiting for resources to become available.

Read I/Os Per Commit Displays the average number of read I/Os per commit.


Printing Reports in Batch


To print reports in batch, you first must select the reports you want to print, and then generate the batch job.

Use the Historical Reporting Menu to select a report type and access the report panels. For information about accessing report panels, see “Historical reporter options menu” on page 114.

Selecting reports for batch executionTo select reports for batch execution from any of the report panels:

� Type B next to all the reports you want to include in a single batch job, and press Enter.

Result: After you press Enter, an asterisk (*) appears next to each report that you selected for batch processing. The asterisk disappears when you generate the batch report, as described below.

The batch job uses the reporting options that are currently specified.

Changing reporting optionsIf you want to change your reporting options and submit another batch job, do the following:

1. Change your reporting options. (See “Setting Reporter Options” on page 114)2. On the report panels, type B next to the reports you want to submit.3. Press Enter.4. Repeat steps 1 – 3, if necessary, to change options for another batch job.

Generating a batch jobEach report you select for batch job execution during your session is appended to a batch report queue. This batch report queue then is submitted along with the batch job request through the Batch Job Generation Options panel. This panel enables you to create the JCL required to submit the batch job.

To access the Batch Job Generation Options panel:

� Select Batch from the Historical Reporter Menu.

Result: The Batch Job Generation Options panel appears.

The Batch Generation Options panel also appears automatically when you exit from the Historical Reporter Menu, if any reports have been selected for batch processing and have not been submitted.

You can perform the following actions from this panel:

� edit the JCL

� submit the job



� cancel the batch job request, but retain the current report queue for later processing

� delete the current report queue


Report Information

Report Information

Return codesThe following table describes the return codes that may be issued by the OMEGAMON II reporter.

Report formatAll reports within a report type (for example, Accounting) have some common features. This makes it easy to find information quickly on all reports of that type.

In the sections that follow, the common elements of each report type are described.

Report page heading

The page heading of all reports contains the name and version of the product (OMEGAMON II for DB2 V540), the report title, and the page number. The second line contains the grouping elements used when generating the report.

If no grouping elements were used, NONE is displayed. The report titles shown in these example headers are the default titles. However, titles can be customized with the title specification.

Table 16. Historical Reporter Return Codes

Return Code

Explanation

00 Processing was completed successfully; all report requests generated output.

04 One or more report requests were accepted for processing, but one or more report requests failed to generate output. This may be due to one or more of the following reasons:� One or more (but not all) report requests were rejected due to errors.� One or more report requests failed to produce any output because no data was

found in the input file(s) to match the criteria for the report.� One or more report requests failed to produce all requested output because

ERRORS IGNORE was not specified and a record processing error occurred.

08 No report request was accepted for processing; all report requests failed to produce all requested output because ERRORS IGNORE was not specified and a record processing error occurred.

12 Termination entered due to unrecoverable processing error.

Note: If you specify ERRORS IGNORE, the return code will not reflect any record processing errors unless no output is generated. If you specify ERRORS IGNORE, any record processing error will cause that report to be terminated, and the return code will be set to 04 or 08, depending on whether other reports were processed successfully.

Report Information


Report entry header

The report entry header is written before each group of data is written out. The format depends on the report type and the level of summarization.

Statistics reports

If no grouping is performed at report time, the report header looks like this:

If grouping is performed, only the grouping elements are displayed. For example, if you use DB2ID and DAY as the groupby specifications, the report header looks like this:

If the data is generated from a data sharing environment, the report header shows the group and member name.

Accounting reports

If the accounting data displayed is at the detail level (one entry per thread), the report header will look like this:

If the data pertains to a distributed thread, the following line is also displayed:

Omegamon II for DB2 V540 Accounting Buffer Pool Activity Page 1Run Date=mm/dd/yyyy Grouped by Hour, PlanName Time=08:37:00

Sysid=SYSG, DB2id=D61A, Date=mm/dd/yyyy, Time=16:16

Sysid=SYSG, DB2id=D23A, Date=mm/dd/yyyy

Sysid=SP22, DB2id=D412, Group=TDDB241G, Member=D412, Date=mm/dd/yyyy, Time=07:16

Start Timestamp=1993-10-09-15.04.24.953819; End Timestamp=1993-10-10-06.11.23.746383; Termination=RES/INDT; ConnType=TSOSysid=SYSG, DB2id=D41B, Planname=H2270PLN, Connid=DB2CALL, Corrid=TDO2S07, Authid=TDO2S07, Original Authid=TDO2S07Commits=1, Aborts=0, Parallel Tasks=8

Network ID=USCACO01, LU Name=O2D23A, Unique ID=0A5F385FE184, Requesting Location=D61A


Report Information

If the accounting data has been summarized, either at reporting time or at collection time (extract with groupby or summarization), the report header will look like this:

The heading lines display the grouping elements. (In the example above, the grouping elements were SYSID, DB2ID, and PLANNAME.)

If the groupby specification was any combination of four or less (of HOUR, DAY, AUTHID, ORIGAUTH, CONNID, CORRID, PLANNAME, DB2ID, SYSID, LUWID, MEMBER, GROUP), the report header will be in this format:

If the accounting data is from a data sharing environment, the report header looks like this:

Audit reports

The audit report entry header for detail reports looks like this:


If the data is generated from a data sharing environment, the report header shows GROUP= and MEMBER= after the timestamp.

Start Date=mm/dd/yyyySysid=SYSG, DB2id=D22A, Planname=DSNESPRR, Threads=30, Commits=37, Aborts=11

grpby #1=VALUE, grpby #2=VALUE, grpby #3=VALUE, grpby #4=VALUE, ...

StartTimestamp=2001-09-09-12.11.01.775456; EndTimestamp=2001-09-09-12.15.16.207443;Termination=DeallocSysid=SP22, DB2id=D612, Group=TDDB261G, Member=D612, Planname=JACK2020, Connid=DB2CALL, Corrid=TDDB20A, Original Authid=TDDB20ACommits=5, Aborts=1

Timestamp=2001-07-10-17.20.21.044779Sysid=SYSG, DB2id=D61A, Planname=DSNESPRR, Connid=TSO, Corrid=PT01TST2, Authid=USERDB01, Original Authid=USERDB01


Timestamp=2001-08-24-11.13.51.838455, Group=TDDB261G, Member=D611Sysid=SP13, DB2id=D611, Planname=DSNESPCS, Connid=TSO, Corrid=JWAYG3, Authid=JWAYG3, Original Authid=JWAYG3

Report Information


Performance reports

The Application Trace Summary report has an overall slightly different format depending on the groupby option specified.

The following headers apply to all other performance reports.

If no grouping is performed at report time (the event default), or the data has been grouped by thread (which is also the default if no groupby option is specified) the report header looks like this:

Some performance reports cannot have a groupby option specified. These reports are as follows:

� Application SQL Trace

� Application Event Trace

� System Event Trace

� Lock Contention

If the performance data has been grouped by unit of work, the report header looks like this:

If the performance data has been grouped by program, the report header looks like this:

If the groupby specification was any combination of four or less (of HOUR, DAY, AUTHID, ORIGAUTH, CONNID, CORRID, PLANNAME, DB2ID, SYSID, LUWID, MEMBER, GROUP), the report header will look like this:

Timestamp=2001-08-26-07.00.12.646743DB2Id=$DB2, Planname=MIRPLAN, Connid=$CICSTOR, Corrid=GT00MI, Authid=SSH, Original Authid=SSH

Timestamp=2001-02-26-07.00.12.646743DB2Id=$DB2, Planname=MIRPLAN, Connid=$CICSTOR, Corrid=GT00MI, Authid=SSH, Original Authid=SSH, Program=PGM003



Using the Report Request Language 139

Using the Report Request Language

This chapter describes how you can create historical reports using the OMEGAMON II for DB2 Historical Reporter.

Chapter ContentsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

JCL for the OMEGAMON II for DB2 Historical Reporter . . . . . . . . . . . . . . . . . . 141Report request language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Report Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Report Subjects for STATISTICS Report Type. . . . . . . . . . . . . . . . . . . . . . . . . . . 145Report Subjects for ACCOUNTING Report Type . . . . . . . . . . . . . . . . . . . . . . . . 147Report Subjects for AUDIT Report Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Report Subject for DSNZPARM Report Type . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Report Subjects for PERFORMANCE Report Type . . . . . . . . . . . . . . . . . . . . . . . 149Report Subject for INPUT Report Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Filtering and Other Report Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Time Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Selection Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Groupby Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Orderby Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Values Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Output Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Input Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Title Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Errors Specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Report format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

7

Overview


Overview

This chapter describes how you can create historical reports using the OMEGAMON II for DB2 Historical Reporter. You can generate these reports by writing your own JCL to submit report requests. The report request language, which defines the reports you want to create, is included in the JCL that invokes the OMEGAMON II for DB2 reporter in batch. (You can also generate a CLIST to run in foreground.)

This chapter includes

� sample invocation JCL and the ddnames you can use

� format of the report request language

� return codes issued by the OMEGAMON II for DB2 reporter

Note: To create historical reports with the OMEGAMON II for DB2 Historical Reporter using the Historical Reporter Menu panels, see “Using the Historical Reporter Menu” on page 111.

Source data

The OMEGAMON II for DB2 Historical Reporter uses input data from any of the following sources:

� DB2 tables

Contain data generated by the online collector, extractor, or summarizer.

� Historical VSAM or archived datasets

Contain data generated by the online collector, extractor, summarizer, or from ATF capture.

� SMF (active or archived) datasets


� GTF datasets


Report types

The six types of historical information you can report on are:

� statistics� accounting� audit� DSNZPARM� performance� input



Overview

JCL for the OMEGAMON II for DB2 Historical Reporter

Sample JCL dataset

OMEGAMON II provides sample report job invocation JCL in the dataset rhilev.RKD2SAM(REPTcccc), where cccc is the DB2 subsystem name.

Example of JCL

The following is a sample of JCL to invoke the OMEGAMON II for DB2 reporter:

Ddnames

The following is a list of all ddnames that can be used by the OMEGAMON II for DB2 Historical Reporter.

GTFccccc A ddname that defines a Generalized Trace Facility (GTF) format input file. These input files should not be concatenated, so that they can be processed for timestamp wrap if necessary. You can include in the jobstep as many of these DD statements as are needed to define all of the input for the report.

SMFccccc A ddname that defines a System Management Facility (SMF) format input file. You can concatenate these input files if they are non-VSAM; however, since input summary messages and some reports may refer to the source ddname, these will be more specific if you use a separate DD statement for each file. You can include in the jobstep as many of these DD statements as are needed to define all of the input for the report.

//cccccccc JOB (cccccc,cccc),'cccccccc',CLASS=c,MSGCLASS=c//JOBLIB DD DISP=SHR,DSN=hilev.RKANMOD ** OM/DB2 LOAD DATASET// DD DISP=SHR,DSN=cccccccc.DSNLOAD ** DB2 LOAD DATASET//*** ** (IF DB2 TABLE INPUT)//H2REPORT OUTPUT CLASS=X//***//O2REPORT EXEC PGM=KO2RPRTB,DYNAMNBR=20,REGION=4096K//O2RMLOG DD SYSOUT=* ** MSG DSN//O2CMSGS DD SYSOUT=* ** STD C MSG DSN//SYSUDUMP DD SYSOUT=* ** DEBUG DSN (NOT USED)//O2SRMSG DD SYSOUT=* ** SORT MSGS//H2REPORT DD SYSOUT=(,),OUTPUT=*.H2REPORT ** REPORT OUTPUT DEFAULT//*//GTFcccc DD DISP=SHR,DSN=cccccc ** GTF INPUT DATASET//*** ** (REPEAT AS NECESSARY)//*//SMFcccc DD DISP=SHR,DSN=cccccc ** SMF INPUT DATASET//*** ** (REPEAT AS NECESSARY)//*//H2Xcccc DD DISP=SHR,DSN=cccccc ** H2 HISTORICAL DATASET//*** ** (REPEAT AS NECESSARY)//*//O2RPT1 DD SYSOUT=(,),OUTPUT=*.H2REPORT ** ACCT SUMMARY REPORT//O2RPT2 DD SYSOUT=(,),OUTPUT=*.H2REPORT ** ACCT DETAIL REPORT//*//O2RPARM DD * ** REPORT REQUEST PARMS SET GLOBAL ERRORS IGNORE INPUT FOR DATES FROM mm/dd/yyy SELECT DB2ID = 'D31A' VALUES AS PERTHREAD OUTPUT TO H2REPORT REPORT ACCT SUMMARY OUTPUT TO O2RPT1 REPORT ACCT DETAIL OUTPUT TO O2RPT2

Overview


H2Xccccc A ddname that defines an OMEGAMON II historical data file produced by the H2 collector, extractor, or summarizer, or by ATF capture. These input files cannot be concatenated if they are in VSAM format. If they are sequential format archive copies of the VSAM files, you can concatenate them. However, since input summary messages and some reports may refer to the source ddname, these will be more specific if you use a separate DD statement for each file. You can include in the jobstep as many of these DD statements as are needed to define all of the input for the report.

O2Rcccc A default ddname that defines a report output file or destination. Each report that can be produced by the OMEGAMON II for DB2 reporter will have a default ddname for the output produced by that report. The default name will begin with the prefix O2R. Default names are provided with the descriptions of the individual reports in Part III: ”OMEGAMON II for DB2 Reports” on page 179. Each report you want to produce requires a corresponding unique DD statement to describe the output file or destination for that report. The output can be directed to SYSOUT or to a dataset.

APSUM2 An example of a ddname that defines a report output file or destination. This ddname is specified by the user in the OUTPUT clause of the REPORT request statement. This ddname is not required unless the same report is generated by multiple REPORT statements in the same jobstep. In this case, the name you specified is needed to differentiate the output for each report. Each report you want to produce must have a corresponding unique DD statement to describe the output file or destination for that report. The output can be directed to SYSOUT or to a dataset.

O2RMLOG This ddname defines the output file or destination for any messages that the OMEGAMON II for DB2 reporter produced during the jobstep. (Some messages may be directed to the console or job log.) It also directs any summaries of input or intermediate-phase processing statistics to this file. This file is required and is shared by all reports.

O2SRMSG If any information or diagnostic messages are produced by a sort during the jobstep, this ddname directs the messages to the O2SRMSG file. This file is required and is shared by all reports. To suppress these messages, code this statement with the DUMMY parameter.

SYSUDUMP or SYSABEND

If any diagnostic information is produced by the operating system during abnormal termination of the jobstep, this ddname directs the information to the SYSUDUMP file. Use the ddname SYSABEND for a more extensive dump, which will help Candle resolve problems. This file is optional. To suppress dumps, omit the statement with this ddname. This file is shared by all reports.

O2RPARM This ddname identifies the file (O2RPARM) that contains all parameters for report processing. The format of each statement included in this file is described in “Report request language” on page 143. This file is required and is shared by all reports.


Overview

Report request languageThis section describes the format of the report request language. You will use this language to generate a report if you elect to manually create your own JCL to submit report requests. The report request language is included in the JCL that invokes the OMEGAMON II for DB2 Historical Reporter.

Report request format

The format of a report request is as follows:

REPORT report-specification

FOR time-specification

SELECT selection-specification

GROUP BY groupby-specification

ORDER BY orderby-specification

VALUES values-specification

OUTPUT output-specification

TITLE title-specification

SET GLOBAL statement

To specify default options that apply to multiple report requests, use the SET GLOBAL statement. It should precede all report requests to which it applies.

You also can use the SET GLOBAL statement to define options for the report requests that follow it. Unspecified options in the report request will be defined by their values in the previous SET GLOBAL statement. The following is the format of the SET GLOBAL statement:

SET GLOBAL

FOR time-specification

SELECT selection-specification

GROUP BY groupby-specification

ORDER BY orderby-specification

VALUES values-specification

OUTPUT output-specification

INPUT input-specification

TITLE title-specification

ERRORS errors-specification

Overview


Using the report request language

The sections that follow describe the report request language in detail. “Report Specification” on page 144 describes how to specify the report types and subjects for the reports you want to create. “Filtering and Other Report Specifications” on page 152 describes how to specify filtering options and other report options, such as input specification and title information.

Report SpecificationThe report specification identifies the report you want to create. It consists of a high-level report category and report subject in the following format:

report-category report-subject [report-subject-qualifiers]

For example:

REPORT STATISTICS BIND_ACTIVITY [DATES FROM mm/dd/yy TO mm/dd/yy]

Report categories

You can use the following report categories in your report specification.

Report subjects

Refer to the sections that follow for a description of the report subjects for each report category.

STATISTICS For reports based on statistics trace records.

Alternate Specifications: STAT, STATS, S

ACCOUNTING For reports based on accounting trace records.

Alternate Specifications: ACCT, ACCTG, A

AUDIT For reports based on audit trace records.

Alternate Specifications: AUDT, U

DSNZPARM For reports based on DSNZPARM trace records.

Alternate Specifications: ZPRM, ZPARM, Z

PERFORMANCE For reports based on performance trace records.

Alternate Specifications: PERF, PERFM, P

INPUT For reports that provide information about the number and types of input records.

Alternate Specifications: INP, I


Overview

Report Subjects for STATISTICS Report Type

Report subjects

You can use the following report subjects for the STATISTICS report category.

SUMMARY Displays a one-line summary for each time interval.

Alternate Specifications: SUM

DETAIL Displays all statistics data.

Alternate Specifications: DTL

CPU_TIME_SUMMARY Displays CPU times of the DB2 address spaces.

Alternate Specifications: CPU, CPUTIME, CPUTIMESUM

SUBSYSTEM_ACTIVITY Displays subsystem activity.

Alternate Specifications: SUBSYS, SYSTEM, SUBSYSACT, SYSACT

BUFFER_POOL_ACTIVITY Displays buffer pool activity for 1 or more buffer pools.

Alternate Specifications: BPACT, BUFPOOLACT

GROUP_BUFFER_POOL_ACTIVITY Displays group buffer pool activity for 1 or more group buffer pools in a data sharing group.

Alternate Specifications: GBPACT, GRPBUFPOOLACT

EDM_POOL_ACTIVITY Displays EDM pool activity.

Alternate Specifications: EDM, EDMACT

LOG_ACTIVITY Displays logging activity.

Alternate Specifications: LOG, LOGACT

LOCK_ACTIVITY Displays lock activity.

Alternate Specifications: LOCK, LOCKACT

GLOBAL_LOCK_ACTIVITY Displays global lock activity in a data sharing environment.

Alternate Specifications: GLOCK, GLBLOCKACT

SQL_ACTIVITY Displays SQL activity.

Alternate Specifications: SQL, SQLACT

COMMAND_ACTIVITY Displays command activity.

Alternate Specifications: COMMAND, CMD, CMDACT

BIND_ACTIVITY Displays bind activity.

Alternate Specifications: BIND, BINDACT

Overview


DISTRIBUTED_DATA_FACILITY_ACTIVITY

Displays distributed activity.

Alternate Specifications: DDF, DDFACT

OPEN_CLOSE_ACTIVITY Displays database open/close activity.

Alternate Specifications: OC, OCACT, OPCLACT


Report Subjects for ACCOUNTING Report Type


Report subjectsYou can use the following report subjects for the ACCOUNTING report category.

SUMMARY Displays a one-line summary of thread activity.


DETAIL Displays all thread activity data.

Alternate Specifications: DTL

TIME_SUMMARY Displays thread time information.

Alternate Specifications: TIME, TIMESUM

BUFFER_POOL_ACTIVITY Displays buffer pool activity for all buffer pools.

Alternate Specifications: BUFPOOL, BUFPOOLACT, BPACT

GROUP_BUFFER_POOL_ACTIVITY Displays group buffer pool activity for 1 or more buffer pools in a data sharing group.

Alternate Specifications: GBPACT, GRPBUFPOOLACT

LOCK_ACTIVITY Displays lock activity.

Alternate Specifications: LOCK, LOCKACT

GLOBAL_LOCK_ACTIVITY Displays global lock activity in a data sharing environments.

Alternate Specifications: GLOCK, GLBLOCKACT

SQL_ACTIVITY Displays SQL activity.

Alternate Specifications: SQL, SQLACT

SORT_ACTIVITY Displays sort activity.

Alternate Specifications: SORT, SORTACT

SCAN_ACTIVITY Displays scan activity.

Alternate Specifications: SCAN, SCANACT

TERMINATION_SUMMARY Displays thread termination information.

Alternate Specifications: TERM, TERMSUM

RESOURCE_LIMIT_FACILITY_SUMMARY

Displays resource limit facility information.

Alternate Specifications: RLF, RLFSUM

PACKAGE_DETAIL Displays package detail information

Alternate Specifications: PKG, PKGDTL



Report Subjects for AUDIT Report Type

Report subjects

You can use the following report subjects for the AUDIT report category.

Report Subject for DSNZPARM Report Type

Report subject

You can use the following report subject for the DSNZPARM report category.

DISTRIBUTED_DATA_FACILITY_ACTIVITY

Displays distributed activity.

Alternate Specifications: DDF, DDFACT

PARALLEL_TASKS Displays summary of parallel task activity.

Alternate Specifications: TASKS, PARALLEL, PTASKS, CHILDTASKS

SUMMARY Displays, for each AUTHID, a summary of audited activity.


AUTHORIZATION_FAILURE Displays attempts to perform DB2 functions that failed due to inadequate authorization.

Alternate Specifications: AUTHFAIL, FAILURE, CLASS 1

AUTHORIZATION_CONTROL Displays GRANT/REVOKE activity.

Alternate Specifications: AUTHCNTL, CNTL, CLASS 2, CONTROL

DDL_ACCESS Displays CREATE, DROP, ALTER activity against auditable tables.

Alternate Specifications: DDL, CLASS 3

DML_ACCESS Displays read or write access to auditable tables.

Alternate Specifications: DML, CLASS 4, CLASS 5

BIND_ACTIVITY Displays DML statements resulting in bind activity.

Alternate Specifications: BIND, BINDACT, CLASS 6

AUTHORIZATION_ID_CHANGE Displays changes to authorization IDs.

Alternate Specifications: AUTHID, IDCHG, CLASS 7

UTILITY_ACTIVITY Displays utility activity.

Alternate Specifications: UTILITY, UTIL, UTILACT, CLASS 8

INSTALLATION_PARAMETERS Displays DB2 configuration parameters.

Alternate Specifications: DTL, DETAIL, DSNZPARM, INSTPARMS, PARAMETERS, PARMS



Report Subjects for PERFORMANCE Report Type

Report subjects

You can use the following report subjects for the PERFORMANCE report category.

APPLICATION_SUMMARY Displays summary information about each thread.

Alternate Specifications: APPLSUM, APPLSUMMARY

APPLICATION_DETAIL Displays detailed information about each thread.

Alternate Specifications: APPLDTL, APPLDETAIL

APPLICATION_SQL_TRACE Displays information about SQL activity.

Alternate Specifications: APPLSQL, SQLTRACE, SQLTRC

APPLICATION_EVENT_TRACE Displays the contents of every desired trace record, as in SYSTEM_TRACE, but sorts and displays records in date-time sequence within each thread.

Alternate Specifications: APPLTRC, APPLTRACE

APPLICATION_BUFFER_POOL_ACCESS Displays buffer pool page activity on a pageset basis. This report shows synchronous READS and WRITES only, since they are the only I/O that can be tied back to an applications request.

Alternate Specifications: APPLBPACC, APPLBPA

APPLICATION_BUFFER_POOL_IO Displays buffer pool I/O application activity for each pageset. This report shows synchronous READS and WRITES, and asynchronous READS (prefetch). Asynchronous WRITES (deferred WRITES) are not included, since they cannot be tied back to an applications request.

Alternate Specifications: APPLBPIO, APPLBUFPOOL

EDM_POOL_IO Displays EDM pool I/O activity.

Alternate Specifications: EDMIO, EDM

LOCK_SUSPENSIONS Displays lock suspension activity for a pageset.

Alternate Specifications: LOCKSUSP, SUSPENSIONS



GLOBAL_LOCK_SUSPENSIONS Displays information about global lock suspensions and timeout/deadlock activity in a data sharing environment.

Alternate Specifications: GLOCKSUSP, GLOBAL_SUSPENSIONS, G_SUSPENSIONS

LOCK_CONTENTION_TRACE Displays information about timeout and deadlock activity.

Alternate Specifications: LOCKCONT, CONTENTIONS

NEGATIVE_SQL_DETAIL Displays detailed information about negative SQL activity.

Alternate Specifications: SQL

P_LOCK_DETAIL Displays detailed information about pageset and page P-Lock activity in a data sharing environment.

Alternate Specifications: PLOCKDTL, P_LOCK_DTL

SYSTEM_EVENT_TRACE Displays the contents of every desired trace record in date-time sequence. For paired trace records (BEGIN and END events), elapsed times are calculated and displayed with END event data.

Alternate Specifications: SYSTRACE, TRACE

SYSTEM_BUFFER_POOL_ACCESS Displays buffer pool page activity for each pageset.

Alternate Specifications: SYSBPACC, SYSBPA

SYSTEM_BUFFER_POOL_IO Displays buffer pool I/O activity for each pageset. This report shows synchronous READS and WRITES, and asynchronous READS (prefetch) and WRITES (deferred WRITES).

Alternate Specifications: SYSBPIO, SYSBUFPOOL



Report Subject for INPUT Report Type

Report subjects

You can use the following report subject for the INPUT report category.

RECORD_SUMMARY This report displays a summary of the number and types of input records found in all of the input files, as well as the date-time ranges of those records, by DB2 subsystem.

Alternate Specifications: RECSUM, RECORD SUMMARY, RS, SUMMARY

RECORD_TRACE Displays a 1- or 2-line summary of each of the input records found in all of the input files.

Alternate Specification: RECTRC, RECORD TRACE, RT, TRACE

RECORD_DUMP Displays a full hexadecimal and character dump of the input records found in all of the input files.

Alternate Specifications: RECDMP, RECORD DUMP, RD, DUMP

Filtering and Other Report Specifications



The specifications that you can use in addition to the report specification are:

� time specification

� selection specification

� groupby specification

� orderby specification

� values specification

� output specification

� input specification

� title specification

� errors specification

� default SYSID specification

Each specification is described in detail in this section.

Time Specification

Introduction

The time specification is used to limit the report to a specific date range or time range, or date and time range within each day. The Time Specification consists of a TIME specification, a DATE specification, or both.

To control the time range within each day that is to be included in the report, enter the TIME specification using the following format:

[TIME starttime-endtime]

To control the date or date range that is to be reported, use only one of the following date specifications for each REPORT or SET GLOBAL statement.

[DATE date]

[DATE[S] [FROM startdate [starttime]] [TO|UNTIL enddate [endtime]]]

[DATE[S] [STARTING] date]

[DATE[S] [STARTING] date FOR value timemeasure]

[DATE[S] [STARTING] date TO|UNTIL enddate]

[DATE[S] [STARTING] value timemeasure AGO]

[DATE[S] [STARTING] value timemeasure AGO TO|UNTIL enddate]

[DATE[S] [STARTING] value timemeasure AGO FOR value timemeasure]

The following paragraphs describe each of the allowed specifications.



Specify time range

The format for specifying a time range is:

TIME starttime-endtime

Specifies the time range within each day of the date range to be reported. The time must be specified as hh:mm:ss. If the start time is greater than the end time, the time range is assumed to wrap around midnight. Trailing zeros are assumed if the complete time field is not specified.

Specify single date

The format for specifying a single date is:

DATE date

Specifies the single date to be reported on. The date must be specified as mm/dd/yyyy or dd.mm.yyyy or yyyy-mm-dd.

DATE is mutually exclusive with DATE[S] FROM/TO... and DATE[S]...AGO. If a TO/UNTIL... or FOR... subclause is specified, this date is interpreted as a start date of a date range.

Specify range of dates

The format for specifying a range of dates is:

DATE[S]...

Specifies a range of dates to be used. The following subclauses provide a number of ways to specify the date range.

� [FROM startdate [starttime]] [TO|UNTIL enddate [endtime]]

Specifies a range of dates to be used.

The date must be specified as mm/dd/yyyy, or dd.mm.yyyy, or yyyy-mm-dd. You can use only a beginning date, omitting the TO/UNTIL date, and the current date will be used as the default end date. You can use only an ending date, omitting the FROM date, and the current date will be used as the default start date. You can also specify a time with the starting and ending dates. The time must be specified as hh:mm:ss (where trailing zeroes are assumed).

DATE[S] FROM/TO... is mutually exclusive with any other DATE[S]... subclause.

The following are sample date ranges:

DATES FROM mm/dd/yyy TO mm/dd/yyy

DATES FROM mm/dd/yyy 8:00 TO mm/dd/yyy 17:00

DATES FROM mm/dd/yyy

DATES TO mm/dd/yyy 17:00

� [STARTING] date

Specifies a start date for the date range to be used.



The date must be specified as mm/dd/yyyy or dd.mm.yyyy or yyyy-mm-dd. If no subclause is specified for an end date for the daterange, the current date will be used as the default end date (unless the keyword STARTING is also omitted, in which case this subclause specifies a single date to be reported on).

This form of DATE[S]... is mutually exclusive with DATE... and DATE[S] FROM/TO...

Examples include:

DATES mm/dd/yyy UNTIL mm/dd/yyy

DATES STARTING mm/dd/yyy

DATES STARTING mm/dd/yyy FOR 31 DAYS

� [STARTING] value timemeasure AGO

Specifies a relative date to be used as a start date for the daterange to be used.

Value must be a numeric value. Timemeasure must be either DAYS, WEEKS, or MONTHS. When specified, the reporting period will start the specified amount of time prior to the current date and end with the current date.

DATE[S]...AGO is mutually exclusive with DATE... and DATE[S] [FROM/TO/STARTING]... where a specific start date is specified.

Note: The relative value is subtracted from the current date, so that 1 day ago means yesterday. See the note below regarding the FOR subclause relative value.

Examples include:

DATES 4 MONTHS AGO UNTIL mm/dd/yyy

DATES 5 DAYS AGO

DATES STARTING 14 DAYS AGO FOR 5 DAYS

� FOR value timemeasure

Specifies a relative date to be used as an end date for the daterange to be used.

Value must be a numeric value. Timemeasure must be either DAYS, WEEKS, or MONTHS. When specified, the reporting period will end the specified amount of time after the start date specified. This subclause must follow a subclause specifying the start date.

FOR... is mutually exclusive with DATE[S] FROM/TO...

Note: The relative value, minus 1 day, is added to the start date, so that a date range starting 1 day ago for 1 day means yesterday only (it does not include today as the default end date). In effect, the FOR period starts counting with the specified start date. Likewise, a date range starting 1 week ago for 1 week means 1 week that ends with yesterday.

Examples include:

DATES STARTING mm/dd/yyy FOR 31 DAYS

DATES STARTING 14 DAYS AGO FOR 5 DAYS

� TO|UNTIL enddate



Specifies an end date for the daterange to be used.

The date must be specified as mm/dd/yyyy or dd.mm.yyyy or yyyy-mm-dd. This subclause must follow a subclause specifying the start date.

Examples include:

DATES STARTING mm/dd/yyy TO mm/dd/yyy

DATES 4 MONTHS AGO UNTIL mm/dd/yyy

Selection SpecificationSelection specifications limit the type of data reported on. The following is the format for a selection specification:

field-name operator field-value [additional-field-values ...] [AND...]

field names

Identifies the field that is to be compared to the specified value (or values). Possible values:

AUTHID Primary authorization identifier.

BPID Buffer pool identifier.

CONNID DB2 connection identifier.

CONNTYPE DB2 connection type.

CORRID DB2 correlation identifier.

CORRNAME Name portion of the DB2 correlation identifier.

DB2ID DB2 subsystem identifier.

GROUP Name of the data sharing group.

HOSTNAME Hostname identifier.

LUWID Logical unit of work identifier.

MEMBER Name of the member within a data sharing group.

ORIGAUTH Original authorization identifier.

PACKAGE Package identifier.

PLANNAME Execution plan name.

PROGRAM Execution program name.

SYSID MVS system identifier.

TCPIP TC/PIP address.



Accounting field names - The following field names are for reports in the accounting category only:

Note: Quantity values (ELAPTIME, DB2TIME, and DB2CPU) are calculated on individual records before grouping. For example, if you specified the value PERCOMMIT (average value per commit) and an ELAPTIME greater than 10, only threads with an ELAPTIME greater than 10 per commit will be included in the report.

Performance field names - The following field names are for reports in the performance category only:

operators

Specifies the operation to be performed. Possible operators are as follows:

DB2TIME Time spent executing within the DB2 subsystem.

DB2CPU CPU time spent executing within the DB2 subsystem.

ELAPTIME For accounting reports, ELAPTIME is the total time elapsed for an accounting record or unit of work, depending on the values specification.

IFCID DB2 IFC record identifier.

DBID Database identifier.

PSID Database pageset identifier.

DBNAME Database name.

PSNAME Database pageset name.

THREADSTART Start timestamp for a thread.

UOWSTART Start timestamp for a unit-of-work.

PGMSTART Start timestamp for a program.

ELAPTIME For performance reports, the total time elapsed for an event (such as I/O or lock suspend) to be completed.

Note: ELAPTIME values are calculated on individual events before grouping. For example, if you specify an ELAPTIME greater than 10, only events with an elapsed time greater than 10 will be included in the report.

= The field must match the following value exactly (or one of the following values, if a list is specified).

¬= The field must not match the following value (or any of the following values, if a list is specified). This operator can also be specified as <>.

> The field must contain a value greater than the following value.

>= The field must contain a value greater than or equal to the following value. This operator can also be specified as =>.



field values

Specifies the value or list of values to be used for comparison.

If a list of values is specified, the values should be separated by commas or blanks. When you specify a list of values, it is compared to the specified field, and an implied logical OR is assumed between comparisons. Wildcard characters * (suffix only, 0 or more characters) and ? (single character position) may be used for character fields. The field value allowed is dependent upon the field specified.

Possible field values are described below for each field.

< The field must contain a value less than the following value.

<= The field must contain a value less than or equal to the following value.

This operator can also be specified as =<.

AUTHID A character value no longer than 8 in length.

ORIGAUTH A character value no longer than 8 in length.

PLANNAME A character value no longer than 8 in length.

PROGRAM A character value no longer than 8 in length.

CONNID A character value no longer than 8 in length.

CONNTYPE A character value no longer than 8 in length. Possible values are:� BATCH� TSO� CALLATCH� DLI� CICS � IMSBPP� IMSMPP� SYSDIR� APPLDIR� IMSCNTL

CORRID A character value no longer than 12 in length.

CORRNAME A character value no longer than 8 in length.

For CICS threads, this value will be compared with bytes 5 – 8 of the correlation identifier (TRANID). For IMS threads, this value will be compared with bytes 5 – 12 of the correlation identifier (PSBNAME). For all other threads, this value will be compared with the first 8 bytes of the correlation identifier.

DB2ID A character value no longer than 4 in length.

BPID A number representing a valid DB2 bufferpool identifier (0 – 49 or 80 – 89). May also be a string identifying a valid 32K bufferpool (32K, 32K1, 32K2, ..., 32K9).

SYSID A character value no longer than 4 in length.



Accounting field values - The following field-values are for reports in the accounting category only:

Performance field values - The following field-values are for reports in the performance category only:

LUWID A character value no longer than 30 in length in the following format:

networkname.luname.instance

GROUP A character value no longer than 8 in length.

MEMBER A character value no longer than 8 in length.

HOSTNAME A character value no longer than 8 in length.

TCPIP A character value no longer than 8 in length.

PACKAGE A character value no longer than 8 in length.

ELAPTIME A time value or an integer value. The full time is typed in the format hh:mm:ss.thtthm. The integer value represents seconds.

DB2TIME A numeric value with assumed units that vary depending on the report, or a time value. The full time is typed in the format hh:mm:ss.thtthm. Or, you can enter an integer whose units will vary according to the report being produced. For accounting reports, the integer value represents seconds. For performance reports, the integer value represents milliseconds.

DB2CPU A numeric value with assumed units that vary depending on the report, or a time value. The full time is typed in the format hh:mm:ss.thtthm. Or, you can enter an integer whose units will vary according to the report being produced. For accounting reports, the integer value represents seconds. For performance reports, the integer value represents milliseconds.

IFCID A decimal number value. Must be a valid DB2 trace record IFC identifier.

DBID A decimal number value. It must be a valid database identifier for the database to be used in the events being reported.

PSID A decimal number value. It must be a valid database pageset identifier for the pageset to be used in the events being reported.

DBNAME A character value no longer than 8 in length, identifying database name to be selected. IFCID's 105 and 107 must be present in the report input for this selection criteria to be effective.

PSNAME A character field no longer than 8 in length, identifying pageset name to be selected. IFCID's 105 and 107 must be present in the report input for this selection criteria to be effective.

T

networkname The network name (up to 8 characters).

LUname The originating VTAM LUname (up to 8 characters).

instance A unique identifier that represents hexadecimal digits (up to 12 characters).



AND ...

Repeats the selection condition as necessary to specify multiple fields to be matched. A logical AND will connect each of the field test results.

Groupby Specification

The groupby specification indicates how records should be grouped (summarized) in report entries. The allowed values are listed below.

Note: If you use the groupby specification, it will determine the default orderby specification.

The following is the format for a groupby specification:

key-field [additional-key-fields ...]

key field names

Specifies the key field(s) for which values are to be accumulated. Use one of the following field names:

THREADSTART Value is the timestamp of the first SQL statement in the thread. The format is yyyy-mm-dd-hh.mm.ss.nnnnnn. Leading zeroes can be omitted from month, day, or hour.

UOWSTART Value is the timestamp of the first SQL statement in the unit-of-work. The format is yyyy-mm-dd-hh.mm.ss.nnnnnn. Leading zeroes can be omitted from month, day, or hour.

PGMSTART Value is the timestamp of the first SQL statement in the program. The format is yyyy-mm-dd-hh.mm.ss.nnnnnn. Leading zeroes can be omitted from month, day, or hour.

ELAPTIME A time value or an integer value. The full time is typed in the format hh:mm:ss.thtthm. The integer value represents milliseconds.

HOUR All information for each hour will be grouped. You cannot use HOUR with DAY.

DAY All information for each day will be grouped. You cannot use DAY with HOUR.

DB2ID All information for each DB2ID will be grouped.

AUTHID All information for each authorization ID will be grouped.

ORIGAUTH All information for each original authorization ID will be grouped.

PLANNAME All information for each plan will be grouped.

CONNID All information for each connection ID will be grouped.

CONNTYPE All information for each connection type will be grouped.

CORRID All information for each correlation ID will be grouped.



Performance key fields

The following are logical key fields used only for the performance category of reports. If you specify these grouping key fields, you cannot use any other grouping elements. These key fields are:

Rule

If no groupby is specified, the data will be presented at the level of detail in the input dataset.

Orderby SpecificationOrderby specifications indicate how you want the entries on a report to be ordered (sorted).

The following is the format for an orderby specification:

key-field [additional key fields...]

CORRNAME All information with the same correlation name will be grouped.

For CICS threads, the correlation name is bytes 5 – 8 of the correlation ID (TRANID). For IMS threads, the correlation name is bytes 5 – 12 of the correlation ID (PSBNAME). For all other threads, the correlation name is the first 8 bytes of the correlation ID.

SYSID All information for each MVS system ID will be grouped.

LUWID All information for each logical unit of work (LUWID) will be grouped. The LUWID consists of:� the network name� the originating VTAM LUname� a unique identifierYou can use the identifier to uniquely identify a distributed thread. Distributed allied (requestor) threads and the associated database access (server) threads have the same LUWID.

GROUP All information for each data sharing group will be summarized.

MEMBER All information for each data sharing member will be grouped.

HOSTNAME All information for each hostname will be grouped.

TCPIP All information for each TC/PIP address will be grouped.

PACKAGE All information for each package will be grouped.

THREAD All information for each thread will be grouped.

UNIT_OF_WORK All information for each unit of work will be grouped.

PROGRAM All information for each program within a unit of work will be grouped.



key field names

Identifies the key field(s) for which values are to be accumulated. Use one of the following field names:

Rules

If you do not use the groupby specification, the defaults will be:

� SYSID

� DB2ID

� PLAN

� CONNID

� CORRID

� AUTHID

TIME Order by time.

DB2ID Order by DB2ID.

AUTHID Order by authorization ID value.

ORIGAUTH Order by original authorization ID value.

PLANNAME Order by plan name value.

CONNID Order by connection ID value.

CONNTYPE Order by connection type value.

CORRID Order by correlation ID value.

CORRNAME Order by the name portion of the correlation identifier.

For CICS threads, the correlation name is bytes 5 – 8 of the correlation ID (TRANID). For IMS threads, the correlation name is bytes 5 – 12 of the correlation ID (PSBNAME). For all other threads, the correlation name is the first 8 bytes of the correlation ID.

SYSID Order by MVS system identifier.

LUWID Order by logical unit of work identifier. The LUWID consists of:� the network name� the originating VTAM LUname� a unique identifier that can be used to uniquely identify a distributed

thread. Distributed allied (requestor) threads and the associated database access (server) threads have the same LUWID.

GROUP Order by data sharing group name.

MEMBER Order by name of the member within a data sharing group.

PACKAGE Order by package name.

HOSTNAME Order by data hostname.

TCPIP Order by TC/PIP address.



� ORIGAUTH

If you use the groupby specification, the default will be the same as the groupby specification.

If groupby is specified, orderby must be a subset of groupby.

Values SpecificationThe values specification is used to indicate how data values will be displayed on a report.

Note: The values specification is used only for accounting reports. It does not apply to all fields in those reports (for example, ratios and percentages are not affected).

The following is the format for a values specification:

[AS] value-display-type

Value display type

Possible value display types are as follows:

Rule

When you specify PERCOMMIT or PERTHREAD, the Package Detail report shows averages computed per package invocation within the group.

Output SpecificationThe output specification is used to control report output. It includes options for the output of the report, such as the ddname, which describes the output file or destination.

The following is the format for an output specification:

TO ddname

DATES [AS|IN] format-type [FORMAT]

CASE [AS] MIXED|UPPER

NO PAGE [HEADINGS|BREAK]

integer LPP|LINES [PER [PAGE]]

TOTALS Displays total value. (Default)

PERCOMMIT Displays average value per commit.

Alternate Specifications: PER_COMMIT, PC, COMMIT

PERTHREAD Displays average value per thread.

Alternate Specifications: PER_THREAD, PT, THREAD



Specifications

The following is a list of allowed output specifications.

TO ddname

Specifies the output destination for the report, by specifying a ddname that describes an output file. If you omit the ddname here, a default ddname will be used, if this is the only report generated for this report type and subject in this jobstep. If more than one report of the same report type and subject is generated in the same jobstep, you must specify alternate ddnames to differentiate the output for each report. Refer to the individual reports descriptions in Part III: ”OMEGAMON II for DB2 Reports” on page 179 for the default ddname of each report.

DATES [AS|IN] format-type [FORMAT]

Specifies the format in which dates will be displayed on the report.

Possible format types are as follows:

Default: USA

CASE [AS] MIXED | UPPER

Specifies whether report output should be displayed in mixed-case or upper-case only. Default is mixed-case. This output specification is valid only in the SET GLOBAL statement.

NO PAGE [HEADINGS | BREAK]

Specifies that page headings and/or breaks should be suppressed so that only the body of the report is displayed on one “report-length” page. This option is useful for TSO terminal display or when piping the report output to another program (used for GDDM interface).

integer LPP | LINES [PER [PAGE]]

Specifies how many lines should be output to each page.

AMERICAN Produces dates in the format mm/dd/yyyy, and times in the format hh:mm [AM|PM].

EUROPEAN Produces dates in the format dd.mm.yyyy, and times in the format hh.mm.ss.

ISO Produces dates in the format yyyy-mm-dd, and times in the format hh.mm.ss.

JAPANESE Produces dates in the format yyyy-mm-dd, and times in the format hh:mm:ss.

USA Produces dates in the format mm/dd/yyyy, and times in the format hh:mm:ss.



Input SpecificationThe input specification indicates additional information about the input to the report(s). The following is the format for an input specification:

FROM DB2ID db2id

[TABLE [FOR] report category [report-subject] [IS] table-name] ...

Specifications

The following is a list of allowed input specifications.

FROM DB2ID db2id

Specifies a 4-character identifier for the DB2 subsystem in which the desired input tables reside.

TABLE [FOR] report-category [report-subject] [IS] table-name

Specifies the fully qualified name of the DB2 table to be used for input to the specified report category and the report subject, where necessary. This clause can be repeated as many times as necessary to specify all input DB2 table names needed to produce the report.



The report category and subject must be one of the following:

STATISTICS For reports based on statistics trace records.

The following subject tables can be specified:

ACCOUNTING For reports based on accounting trace records.


DDF For input to the Distributed Data Facility Activity report.

This report subject requires input from the main STATISTICS category in addition to the DDF subject.

BUFPOOL For input to the Buffer Pool Activity and Exception reports.

This report subject requires input from the main STATISTICS category in addition to the BUFPOOL subject.

GRPBUFPOOL For input to the Group Buffer Pool Activity report.

This report subject requires input from the main STATISTICS category in addition to the GRPBUFPOOL subject.

DDF For input to the Distributed Data Facility Activity report.

This report subject requires input from the main ACCOUNTING category in addition to the DDF subject.

BUFPOOL For input to the Buffer Pool Activity report.

This report subject requires input from the main ACCOUNTING category in addition to the BUFPOOL subject.

GRPBUFPOOL For input to the Group Buffer Pool Activity report.

This report subject requires input from the main ACCOUNTING category in addition to the GRPBUFPOOL subject.

PACKAGE For input to the Package Detail Report.

This report subject requires input from the main ACCOUNTING category in addition to the PACKAGE subject.



Title SpecificationThe title specification allows you to create custom report title information for the report(s). You can override any of the report title lines and also provide additional subtitles. At execution time, you can insert variables, such as page number and date, into the report title. The first two report title lines use default values unless you explicitly override them with a null or blank value.

Title line specifications must be entered in a top-to-bottom, and left-to-right sequence. Each title line specification must begin with the TITLE keyword, followed by the line number. If you omit title lines or left/center/right specifications, the default report title for that position (if any) will be used.

The following is the format for a title specification:

line# [left-title][/[center-title][/[right-title]]]

line number

Specifies the line number of the page that this title specification describes. Line 1 starts at the top of the page. A line number value of 1 or 2 will override default title values. A line number greater than 2 indicates an additional subtitle(s) to be added. Any unspecified lines, up to the maximum specified, will be left blank. A blank line will appear after the last title and before the report output is started.

AUDIT For reports based on audit trace records. The Audit Summary report requires input from all of the audit category tables.


DSNZPARM For report of DB2 system configuration parameters.

AUTHFAIL For input to the Authorization Failures report.

AUTHCNTL For input to the Authorization Control report.

DDL For input to the Audited DDL Access report (shows create, alter or drop operations).

DML For input to the Audited DML Access report (showing read or write access to auditable tables).

BIND For input to the DML Statements at Bind report.

AUTHID For input to the Authorization ID Changes report.

UTILITY For input to the Utility Access report.

Note: Any of the alternate specifications defined for report subjects in the AUDIT report category (see “Report Subjects for AUDIT Report Type” on page 148) can be used in place of the corresponding subject keywords defined above.



title segment

Specifies the left, center, and right title segments of the report title line, which is specified by the line# parameter.

All title items to the left of the first slash (or all title items, if no slash is present) will be left justified on the title line.

All title items between the first slash (if present) and the second slash (if present) or all remaining items (if the second slash is not present), will be centered on the title line.

All title items to the right of the second slash (if present) will be right justified on the title line.

Multiple title items within one title segment will be concatenated with no intervening spaces (unless you enclose spaces in quotes as part of a string literal value).

Each title item must be one of the following:

literal-value - A literal string enclosed in a pair of quotes, that is to be printed as part of the report title (subject to the placement rules described earlier). The quotes can be either single or double, but the pairs must match. To suppress a report title segment, specify a null literal value (‘“or ““) at the appropriate position.

Note: To include quotes in the string, enclose the string in the opposite style of quotes. For example, ‘”Daily” Report’.

variable - A run-time variable name that will be substituted with a value at execution time. The variable name must be one of the following:

PAGE This variable inserts the current page number of the report into the title line at this point.

R_DATE This variable inserts the current report date (date the report started execution) into the title line at this point.

R_NAME This variable inserts the default report name that normally appears in the center of the first line of this report) into the title line at this point. This allows the report name to be relocated to another position.

R_TIME This variable inserts the current report time (time the report started execution) into the title line at this point.

F_DATES This variable inserts the requested FOR date or date range for the data to be included into the title line at this point. It may include a start or end time, if you specified one as part of the start or end date on the report request.

F_TIMES This variable inserts the requested FOR time range for the data to be included into the title line at this point.

GROUPBY This variable inserts the requested GROUP BY field(s) used to group information on the report into the title line at this point. The field names will be preceded by the text “Grouped by.”.

ORDERBY This variable inserts the requested ORDER BY field(s) used to order the report into the title line at this point. The field names will be preceded by the text “Ordered by.”



Note: The default report title contains the following definitions:

title 1 “Omegamon II for DB2 “ version / r_name / “Page “ page

title 2 “Run date=” r_date / values “ " groupby / “Run time=” r_time

The center segment of the second line of the title may vary slightly by report, as appropriate. Refer to the individual reports descriptions in Part III: ”OMEGAMON II for DB2 Reports” on page 179 for the default title of each report.

Errors SpecificationThe errors specification allows you to produce a report even if input errors occur. For example, if a record needed as input for a report is empty, you can still generate the report.

The following is the format for the errors specification:

ERRORS [OPTIONS] IGNORE|BYPASS INPUT

For example: ERRORS IGNORE INPUT

VALUES This variable inserts the requested VALUES specification for the units of certain values in the report into the title line at this point. The specification will be preceded by the text “Values” (followed by “totals”, “per commit”, or “per thread” as requested).

VERSION This variable inserts the version of the reporter that produced this report into the title line at this point.


Report Information

Report Information

Report formatAll reports within a report type (for example, Accounting) have some common features. This makes it easy to find information quickly on all reports of that type.

In the sections that follow, we will isolate and describe the common elements of each report type.

Report page heading

The page heading of all reports contains the name and version of the product, the report title, and the page number. The second line contains the grouping elements used when generating the report.

If no grouping elements were used, NONE is displayed. The report titles shown in these example headers are the default titles. However, titles can be customized with the title specification.

Report entry header

The report entry header is written before each group of data is written out. Its format depends on the report type and the level of summarization.

Statistics reports - If no grouping is performed at report time, the report header looks like this:

If grouping is performed, only the grouping elements are displayed. For example, if you use DB2ID and DAY as the groupby specifications, the report header looks like this:

If the data is generated from a data sharing environment, the report header shows the group and member name.

Omegamon II for DB2 V540 Accounting Buffer Pool Activity Page 1Run Date=mm/dd/yyy Grouped by Hour, PlanName Run Time=08:37:00

Sysid=SYSG, DB2id=D61A, Date=mm/dd/yyy, Time=16:16

Sysid=SYSG, DB2id=D61A, Date=mm/dd/yyy

Sysid=SP22, DB2id=D612, Group=TDDB261G, Member=D612, Date=mm/dd/yyy, Time=07:16

Report Information


Accounting reports - If the accounting data being displayed is at the detail level (one entry per thread), the report header will look like this:


If the accounting data has been summarized, either at reporting time or at collection time (extract with Group By or summarization), the report header will look like this:

The heading lines display the grouping elements. (In the example above, the grouping elements were SYSID, DB2ID, and PLANNAME.)

If the groupby specification was any combination of four or less (of HOUR, DAY, AUTHID, ORIGAUTH, CONNID, CORRID, PLANNAME, DB2ID, SYSID, LUWID, MEMBER, GROUP, HOSTNAME, TC/PIP, PACKAGE), the report header will be in this format:

If the accounting data is from a data sharing environment, the report header looks like this:

Audit reports - The audit report entry header for detail reports looks like this:

Start Timestamp=2001-10-09-15.04.24.953819; End Timestamp=2001-10-10-06.11.23.746383; Termination=RES/INDT; ConnType=TSOSysid=SYSG, DB2id=D61B, Planname=H2270PLN, Connid=DB2CALL, Corrid=TDO2S07, Authid=TDO2S07, Original Authid=TDO2S07Commits=1, Aborts=0, Parallel Tasks=5


Start Date=mm/dd/yyySysid=SYSG, DB2id=D61B, Planname=DSNESPRR, Threads=30, Commits=37, Aborts=11


Start Timestamp=2001-09-09-12.11.01.775456; End Timestamp=2001-09-09-12.15.16.207443; Termination=DeallocSysid=SP22, DB2id=D612, Group=TDDB261G, Member=D412, Planname=JACK2020, Connid=DB2CALL, Corrid=TDDB20A, Original Authid=TDDB20ACommits=5, Aborts=1

Timestamp=2001-07-10-17.20.21.044779Sysid=SYSG, DB2id=D61A, Planname=DSNESPRR, Connid=TSO, Corrid=PT01TST2, Authid=USERDB01, Original Authid=USERDB01


Report Information


If the data is generated from a data sharing environment, the report header shows GROUP= and MEMBER= after the timestamp.

Performance reports - The Application Trace Summary report has an overall slightly different format depending on the groupby option specified. Refer to Part III: ”OMEGAMON II for DB2 Reports” on page 179 for the entire sample report.

The following headers apply to all other performance reports.

If no grouping is performed at report time (the event default), or the data has been grouped by thread (which is also the default if no groupby option is specified) the report header looks like this:

Some performance reports cannot have a groupby option specified. These reports are as follows:

� Application SQL Trace� Application Event Trace� System Event Trace� Lock Contention

Refer to Part III: ”OMEGAMON II for DB2 Reports” on page 179 for samples of these reports.

If the performance data has been grouped by unit of work, the report header looks like this:

If the performance data has been grouped by program, the report header looks like this:


Timestamp=2001-04-24-11.13.51.838455, Group=TDDB261G, Member=D611Sysid=SP13, DB2id=D611, Planname=DSNESPCS, Connid=TSO, Corrid=JWAYG3, Authid=JWAYG3, Original Authid=JWAYG3

Timestamp=2001-02-26-07.00.12.646743DB2Id=$DB2, Planname=MIRPLAN, Connid=$CICSTOR, Corrid=GT00MI, Authid=SSH, Original Authid=SSH



Report Information


If the groupby specification was any combination of four or less (of HOUR, DAY, AUTHID, ORIGAUTH, CONNID, CORRID, PLANNAME, DB2ID, SYSID, LUWID, MEMBER, GROUP, HOSTNAME, TCPIP, PACKAGE), the report header will be in this format:


Using Other Historical Reporting Methods 173

Using Other HistoricalReporting Methods

Chapter ContentsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174SAS Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175QMF Sample Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

8

Overview


Overview

This chapter describes the historical reporting capabilities of OMEGAMON II, in addition to the OMEGAMON II for DB2 Reporter. You can create historical reports or view information online as follows:

� SAS reports

You can create SAS reports using the SAS sample report library to format data extracted from SMF or GTF. You can also create SAS reports based on the IFCIDS selected while using the Extractor.

� COBOL, C or C++ record layouts

This product provides COBOL, C or C++ record layouts. You can create your own reports, based on the IFCIDS selected while using the Extractor. The data is extracted from SMF, GTF or D2 Online Collector input.

� QMF reports

You can use QMF sample queries to generate reports from data stored in DB2 tables.


SAS Reporting

SAS Reporting

OMEGAMON II includes a library that contains SAS programs and sample SAS reports, which allow you to create accounting and statistics reports. SAS uses the output dataset generated by the data extractor as source data for historical reports. SAS reporting requires that the Historical Reporter execute in load mode.

SAS libraryThe SAS library (rhilev.RKANSAS) assists users who prefer to use SAS-formatted reports. This library contains

� JCL to execute the report programs

� macros that perform data collection from the OMEGAMON II extract dataset and reformat the data into a SAS database

� macros that generate accounting and statistics reports from the SAS database

� a member (KO2$INDX) that contains documentation describing the programs and how to use them

The SAS library includes a SAS version of each accounting and statistics report that is available through QMF.

IFCID-based SAS reportsYou can create IFCID-based SAS reports depending on the IFCIDs you selected while using the Extractor. See the README for instructions on generating these types of reports. See “Specify IFCIDs” on page 60 for a list of the supported IFCIDs.

COBOL and C Reporting for IFCID-based Reports


COBOL and C Reporting for IFCID-based Reports

OMEGAMON II includes a library that contains COBOL and C (or C++) programs that allow you to create accounting and statistics reports based on IFCIDS selected while using the Extractor. These programs use the output dataset generated by the data extractor as source data for historical reports. See the $$README file for instructions on generating these types of reports. See “Specify IFCIDs” on page 60 for a list of the supported IFCIDs.

COBOL and C libraryThe COBOL and C library assists users who prefer to use COBOL-formatted or C-formatted reports. This library contains

� a PDS (rhilev.TKANSAMP) that contains numerous members to be used in creating IFCID-based reports

� a PDS (rhilev.TKANTEST) that contains sample JCL to execute the report programs. This dataset contains a member ($$README) that provides instructions describing the programs and how to use them

� macros that perform data collection from the OMEGAMON II extract dataset and reformat the data into a COBOL or a C database

� macros that generate accounting and statistics reports from the COBOL database

The COBOL library includes a COBOL and C (or C++) version of each accounting and statistics report that is available.


QMF Sample Queries

QMF Sample Queries

OMEGAMON II provides a sample QMF library. It can be used to produce accounting and statistics reports using data from DB2 tables. You can invoke QMF directly to establish an interactive QMF session. The command

LIST PROC (O=CANDLE N=H2%

lists the QMF sample PROCs (if they are available at your site). Use these PROCs to access the QMF sample reports and graphs. Member KO2$PIDX in the dataset rhilev.RKD2SAM contains a description of the available sample PROCs.

Assigning global variablesBefore you execute any PROC listed, you must assign values to the global variables. A sample PROC, CANDLE.H2_GLOBALS, allows you to set these variables for the duration of the QMF session.

Note: The owner of the QMF objects may have an ID other than CANDLE. Check with your database administrator for more information.

Using native QMFIf you are familiar with QMF queries, procedures, and forms, you can also use native QMF to modify the Candle-supplied queries or create your own reports against the historical tables. For example, you may wish to modify a query to return rows for which the in-DB2 CPU time exceeds a specified value. See the appropriate QMF and SQL reference documentation for more information.

Online data dictionaryAn online data dictionary contains a description of all the historical table column names. This will help you specify the elements you need for creating reports with QMF. For more information about the online data dictionary, see “Accessing OMEGAMON II Messages and the Data Dictionary” on page 489.

QMF Sample Queries


179

Part III: OMEGAMON II for DB2 Reports

IFICD-based Accounting Reports 181

IFICD-basedAccounting Reports

IntroductionThe IFCID-based Accounting reports contain information based on IFCID number 3 and its subtypes that you selected while using the Extractor. See “Specify IFCIDs” on page 60 for a list of the supported IFCIDs. See the README for instructions on generating these types of reports.

Chapter ContentsBuffer Pool Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Group Buffer Pool Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Distributed Data Facility (DDF) Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186Accounting Package Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Lock Activity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Global Lock Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193SQL Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Package and DBRM Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

9

Buffer Pool Activity



IntroductionThis report displays summary information about the buffer manager and describes, for a particular thread, the activity in a variable number of buffer pools.

This report is used to determine the read I/O and buffer pool efficiency for a thread or group of threads.

Default DDnameQBAC

Default TitleAccounting Buffer Pool Activity

Data SourceIFCID 3

Data ElementsFor definitions of the data elements displayed in this report, see the online help



FIGURE 3. IFCID-based Reports - Accounting Buffer Pool Activity Report




IntroductionThis report displays information about the global buffer pool activity for a thread or a group of threads for a maximum of 60 buffer pools per DB2 data sharing group. Information includes the number of reads due to cross invalidation. This report applies only to those DB2s within a DB2 data sharing group.

Possible uses for this report are as follows:

� determining if the group buffer pool size is set properly

� determining group buffer pool efficiency

Default DDnameQBGA

Default TitleAccounting Group Buffer Pool Activity

Data SourceIFCID 3

Data ElementsFor definitions of the data elements displayed in this report, see the online help.



FIGURE 4. IFCID-based Reports - Accounting Group Buffer Pool Activity Report

Distributed Data Facility (DDF) Activity



IntroductionThis report displays accounting information about the Distributed Data Facility (DDF), such as the amount of CPU time that elapsed at the local and remote sites, the type of thread involved (distributed allied thread or database access thread), and the activity involving communication between the local and remote systems.

This report shows potential problems with applications using the DDF, such as an excessive number of queued conversations or long remote-wait times.

Default DDnameQLAC

Default TitleAccounting DDF Activity

Data SourceIFCID 3




FIGURE 5. IFCID-based Reports - Accounting DDF Activity Report




IntroductionThis report provides the user with a summary of activity that has occurred for all packages/DBRMs that have been executed by a thread.


When VALUES PERCOMMIT or VALUES PERTHREAD is specified, averages on this report are computed per package invocation within the group.

Default DDnameQPAC

Default TitleAccounting Package Detail

Data SourceIFCID 3, 239




FIGURE 6. IFCID-based Reports - Accounting Report - Time Summary


Lock Activity

Lock Activity

IntroductionThis report displays a summary of lock activity for an individual thread or group of threads, including the total number of deadlocks and timeouts, lock manager requests, and lock escalations, as well as the number of claim and drain requests.

This report is used to view the total number of deadlocks and timeouts occurring within specific applications and to analyze whether or not the number conforms to your standards. The report information can help you determine whether or not the number of lock escalations or timeout/deadlock occurrences is high for a specific application.

Default DDnameQTXA

Default TitleAccounting Locking Activity

Data SourceIFCID 3


Lock Activity


FIGURE 7. IFCID-based Reports - Accounting Lock Activity Report


Global Lock Activity


IntroductionThis report displays global lock activity for an individual thread or group of threads. Data includes global lock requests, lock requests propagated to XES, and the number of false contentions. This report applies only to those DB2s within a DB2 data sharing group.


� determining if the size of the lock structure is set properly

� determining if the number of lock requests propagated to XES is too high

� determining if false contention is too high

Default DDnameQTGA

Default TitleAccounting Global Lock Activity

Data SourceIFCID 3




FIGURE 8. IFCID-based Reports - Accounting Global Lock Activity Report


SQL Activity

SQL Activity

IntroductionThis report displays counts of each type of SQL statement used by a specific application for an individual thread. In addition, this report shows when an application is performing dynamic SQL calls, incremental binds, and other high-overhead Data Control Language (DCL) and Data Definition Language (DDL) SQL statements, as well as RID Pool activity and I/O Parallelism activity.

This report is used to monitor the type of SQL statements that are used most frequently. The report information can reveal potential problems such as excessive incremental binds and dynamic SQL calls.

Default DDnameQXST

Default TitleAccounting SQL Activity

Data SourceIFCID 3


SQL Activity


FIGURE 9. IFCID-based Reports - Accounting SQL Activity Report


SQL Activity

FIGURE 10. IFCID-based Reports - Accounting SQL Activity Report (continued)







Default DDnameQPAC


Data SourceIFCID 3

Group By ElementsAUTHID, HOUR, DAY, DB2ID, CONNID, CORRID, CONTYPE, CORRNAME, ORIGAUTHID, PLANNAME, SYSID, LUWID, MEMBER, GROUP

Order By ElementsAUTHID, TIME, DB2ID, CONNID, CORRID, CONTYPE, CORRNAME, ORIGAUTHID, PLANNAME, SYSID, LUWID, MEMBER, GROUP

Select ElementsAUTHID, DB2ID, CONNID, CORRID, CONTYPE, CORRNAME, ORIGAUTHID, PLANNAME, PROGRAM, SYSID, LUWID, MEMBER, GROUP




FIGURE 11. IFCID-based Reports - Accounting Report - Package and DBRM Detail

IFCID-based Statistics Reports 201

IFCID-basedStatistics Reports

IntroductionThe IFCID-based statistics reports contain information based on IFCID number 1 and its subtypes that you selected while using the Extractor. See “Specify IFCIDs” on page 60 for a list of the supported IFCIDs. See the README for instructions on generating these types of reports.

The statistics trace provides data on the following:

� address space data


This information provides a starting point for tuning the DB2 subsystem.

Chapter ContentsBuffer Pool Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Address Space Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

10




IntroductionThis report displays the buffer manager statistics for a variable number of buffer pools, up to 60 per DB2 subsystem. Use this report to view overall buffer pool activity for a DB2 subsystem.

A buffer pool is storage reserved to satisfy the buffering requirements for tablespaces or indexes.

Default DDnameO2RSBPA

Default TitleStatistics Buffer Pool Activity

Data SourceIFCIDs 2, 202


IFCID-based Statistics Reports 203

Address Space Data

Address Space Data

IntroductionThis report displays information about the DB2 address spaces.

Default DDnameK02CQWSA

Default TitleAddress Space Data

Data SourceIFCID 1


Address Space Data


FIGURE 12. IFCID-based Reports - Address Space Data Report

IFCID-based DSNZPARM Report 205

IFCID-basedDSNZPARM Report

IntroductionThe IFCID-based DSNZPARM report contains information based on IFCID number 106 and its subtypes that you selected while using the Extractor. See “Specify IFCIDs” on page 60 for a list of the supported IFCIDs. See the README for instructions on generating these types of reports.

Chapter ContentsSystem Installation Parameters (DSNZPARM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

11

System Installation Parameters (DSNZPARM)



IntroductionThe IFCID-based DSNZPARM report displays the current settings of the DB2 installation (configuration) parameters for a particular DB2 subsystem. These parameters are set at installation time to establish execution time values for the DB2 subsystem, such as pool sizes, logging and locking parameters, maximum batch/online threads, authorization settings, naming conventions, and usage of trace functions. In addition to the value of each parameter, this report displays the initialization macro and parameter name as used in DSNZPARM.

Since this report presents the state of DSNZPARM parameters at a specified time (DB2 initialization time), it does not necessarily apply to the entire specified time interval. If any DSNZPARM parameter has changed during the course of the specified time interval, multiple reports are produced. Each report (two pages in length) displays one complete set of DSNZPARM parameters that were used for DB2 initialization.

This report is used to provide the user with a detailed list of the current DSNZPARM parameter values, or the DSNZPARM parameter values at the selected time. The report shows you when the parameters values have changed.

Default DDname O2RZPRM

Default TitleSystem Installation Parameters

Data SourceIFCID 106

Group By ElementsNot applicable

Order By ElementsNot applicable

Select ElementsDB2ID, SYSID, GROUP, MEMBER

Data ElementsFor definitions of the data elements displayed in this report, see the online help



FIGURE 13. IFCID-based Reports - DNSZPARM Report (Page 1)

Historical Reporter Accounting Reports 215

Historical ReporterAccounting Reports

IntroductionThe Historical Reporter accounting reports contain information from the DB2 accounting trace. Report information depends on which accounting classes are turned on.

� Accounting class 1 provides elapsed time, buffer pool, locking, resource limit facility, and SQL information.

� Accounting class 2 provides in-DB2 time and in-DB2 CPU time.

� Accounting class 3 provides wait time information.

� Accounting class 7 provides in-DB2 time at the package level.

� Accounting class 8 provides package level wait time information.

Accounting reports provide information on application programs to help you analyze resource utilization: You can examine how adding or changing an application affects DB2 and CPU time per commit, lock activity, read I/O, or buffer manager activity.

Chapter ContentsBuffer Pool Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Group Buffer Pool Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220Distributed Data Facility (DDF) Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225Accounting Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Lock Activity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239Global Lock Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Resource Limit Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247Parallel Task Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Scan Activity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254Sort Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258SQL Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261Accounting Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268Accounting Termination Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272Time Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275Accounting Package Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

12




IntroductionThis report displays summary information about the buffer manager and describes, for a particular thread, the activity in a variable number of buffer pools.

This report is used to determine the read I/O and buffer pool efficiency for a thread or group of threads.

Default DDnameO2RABPA

Default TitleAccounting Buffer Pool Activity

Data SourceIFCID 3



Select ElementsAUTHID, DB2ID, CONNID, CORRID, CONTYPE, CORRNAME, ORIGAUTHID, PLANNAME, SYSID, LUWID, MEMBER, GROUP, BPID

BPID indicates the buffer pools that are displayed.



Data Elements

Sysid The MVS system ID. This column contains blanks if data is extracted from a GTF dataset. (ZWHMVSID)

DB2id The DB2 subsystem name. (QWHSSSID)

Group The name of the DB2 data sharing group. Applies only to DB2 Version 4 and above. (QWHADSGN)

Member The name of the member within a DB2 data sharing group. Applies only to DB2 Version 4 and above. (QWHAMEMN)

Planname The name of the thread. (QWHCPLAN)

Threads The number of threads that are included in this group when Groupby is used.

Commits The number of successful commits completed by the thread. For attachments that use the two phase commit protocol, this count reflects the number of phase two commits. For attachments that do not use the two phase commit protocol, this count reflects the number of successful sync requests processed. (QWACCOMM)

Aborts The number of successful abort requests by the thread. (QWACABRT)

Parallel Tasks The number of parallel tasks for this thread. (QWACPCNT)

Buffer Pool The ID of the buffer pool to which this data refers. (QBACPID)

Possible values for this field are as follows:� 0 – 49: BP0 – BP49� 80 – 89: BP32K – BP32K9If you are running DB2 Version 6.1, additional possible values for this field are:� 100 – 109: BP8K0 – BP8K9� 120 – 129: BP16K0 – BP16K9

Getpage Requests

The number of getpage requests issued. (QBACGET)

Failed Getpage Requests

The number of conditional getpage requests that could not be satisfied. A conditional getpage is used with parallel processing only, and will not wait for a page that is not currently in the buffer pool. (QBACNGT)

Synchronous Read I/O

The number of synchronous read I/Os issued. (QBACRIO)

Getpage/Read I/O

The ratio of getpage request to read I/Os. (QBACGET/QBACRIO)

Page Updates The number of buffer pool page updates. This count is incremented by one each time a row within a page is updated. (QBACSWS)

Seq Prefetch Requests

The number of times that a sequential prefetch was requested. (QBACSEQ)

Dynamic Prefetch Req

The number of dynamic prefetch requests. (QBACDPF)



List Prefetch Req The number of times that a list prefetch was requested. (QBACLPF)

Prefetch Pg Reads

The number of pages read asynchronously via prefetch. (QBACSIO)

Prefetch Pg in Hiperpool

The number of pages that were found in a hiperpool and moved to the virtual buffer pool as a result of a prefetch request. (QBACHPG)

Hiperpool Reads The number of successful synchronous requests to move a page from a hiperpool to a virtual buffer pool. (QBACHRE)

Failed HP Reads The number of times the requested page was found in the hiperpool, but had been discarded by MVS. (QBACHRF)

Hiperpool Writes The number of successful synchronous requests to move a page from a virtual buffer pool to a hiperpool. (QBACHWR)

Failed Hiperpool Writes

The number of unsuccessful requests to write a page to a hiperpool because of a shortage of expanded storage. (QBACHWF)

Immediate Writes

The number of immediate (synchronous) writes performed. (QBACIMW)

BP Hit Percentage

The percentage of getpages that were satisfied by a page already in the bufferpool. If this value is low, it indicates that page residency in the bufferpool is too low. This may mean that the bufferpool may be too small. ((QBACGET - (QBACRIO + QBACSIO)) / QBACGET)

HP Hit Percentage

The percentage of getpages directed to the hiperpool that were satisfied by a page found in the hiperpool. If this value is too low, it indicates that many unsuccessful reads to the hiperpool occurred when the page requested was found in the hiperpool, but the backing expanded storage was stolen by the system. ((QBACHRE + QBACHPG) / (QBACHRE + QBACHPG + QBACHRF)) * 100

Historical R

eporter Accounting R

eports219

Buffer Pool A

ctivity

FIG

UR

E 22.

Acco

un

ting

Bu

ffer Po

ol A

ctivity Rep

ort (G

rou

p b

y DB

2ID, P

lann

ame)

Omegamon II for DB2 V540 Accounting Buffer Pool Activity Page 1Run Date=mm/dd/yyy Group by DB2id, PlanName Run Time=10:41:39 Sysid=SYSG, DB2id=D31A, Planname=JACK2020, Threads=1, Commits=1, Aborts=1------------------------------------------------------------------------------------------------------------------------------------Buffer Pool = 0 Getpage Requests = 7060 Failed Getpage Requests = 0 Synchronous Read I/0 = 59 Getpage/Read I/O = 116.43Page Updates = 832 Seq Prefetch Requests = 152 Dynamic Prefetch Req = 201 List Prefetch Req = 1Prefetch Pg Reads = 1293 Prefetch Pg in Hiperpool= 0 Hiperpool Reads = 0 Failed HP Reads = 0Hiperpool Writes = 0 Failed Hiperpool Writes = 0 Immediate Writes = 0BP Hit Percentage = 85% HP Hit Percentage = 0% Buffer Pool = 1 Getpage Requests = 424 Failed Getpage Requests = 0 Synchronous Read I/0 = 1 Getpage/Read I/O = 0Page Updates = 0 Seq Prefetch Requests = 13 Dynamic Prefetch Req = 0 List Prefetch Req = 0Prefetch Pg Reads = 3 Prefetch Pg in Hiperpool= 0 Hiperpool Reads = 0 Failed HP Reads = 0Hiperpool Writes = 0 Failed Hiperpool Writes = 0 Immediate Writes = 0BP Hit Percentage = 99% HP Hit Percentage = 0% Buffer Pool = 4 Getpage Requests = 548 Failed Getpage Requests = 0 Synchronous Read I/0 = 64 Getpage/Read I/O = 8.56Page Updates = 157 Seq Prefetch Requests = 0 Dynamic Prefetch Req = 0 List Prefetch Req = 0Prefetch Pg Reads = 0 Prefetch Pg in Hiperpool= 0 Hiperpool Reads = 0 Failed HP Reads = 0Hiperpool Writes = 0 Failed Hiperpool Writes = 0 Immediate Writes = 0BP Hit Percentage = 88% HP Hit Percentage = 0% Sysid=SYSG, DB2id=D31A, Planname=ALECV23X, Threads=2, Commits=2, Aborts=0------------------------------------------------------------------------------------------------------------------------------------Buffer Pool = 0 Getpage Requests = 22 Failed Getpage Requests = 0 Synchronous Read I/0 = 3 Getpage/Read I/O = 7.33Page Updates = 13 Seq Prefetch Requests = 1 Dynamic Prefetch Req = 0 List Prefetch Req = 0Prefetch Pg Reads = 9 Prefetch Pg in Hiperpool= 0 Hiperpool Reads = 0 Failed HP Reads = 0Hiperpool Writes = 0 Failed Hiperpool Writes = 0 Immediate Writes = 2BP Hit Percentage = 45% HP Hit Percentage = 0%




IntroductionThis report displays information about the global buffer pool activity for a thread or a group of threads for a maximum of 60 buffer pools per DB2 data sharing group. Information includes the number of reads due to cross invalidation. This report applies only to those DB2s within a DB2 data sharing group.




Default DDnameO2RAGBP

Default TitleAccounting Group Buffer Pool Activity

Data SourceIFCID 3


Order By ElementsAUTHID, TIME, DB2ID, CONNID, CORRID, CONTYPE, CORRNAME, ORIGAUTHID, PLANNAME, SYSID, LUWID, MEMBER

Select ElementsAUTHID, DB2ID, CONNID, CORRID, CONTYPE, CORRNAME, ORIGAUTHID, PLANNAME, SYSID, LUWID, MEMBER, GROUP



Data Elements

Start Timestamp The beginning timestamp for the period covered by this accounting row. It reflects either the time the thread was created or the time of DB2 signon processing that caused DB2 to externalize the accounting data. (QWHSSTCK)

End Timestamp The ending timestamp for the period covered by this accounting row. It either reflects the time thread terminated or the time of DB2 signon processing that caused DB2 to externalize the accounting data. (ZWHESTCK)

Termination Indicates the reason the accounting record was externalized. (ZWACRINV)

Sysid The MVS system ID. This field is blank if data is extracted from a GTF dataset. (ZWHMVSID)




Planname The planname of the thread. (QWHCPLAN)

Connid The DB2 connection identifier of the thread. (QWHCCN)

Corrid The correlation identifier. The actual value depends upon the type of connection. (QWHCCV)

Original Authid The original authorization ID of the thread. (QWHCOPID)



Group Buffer Pool

Group buffer pool identifier. (QBGAGN)

Reads Due to Cross Invalidation

The percentage of total reads to the group buffer pool required because the page in the member’s buffer pool was invalidated. ((QBGAXD + QBGAXR + QBGAXN) / (QBGAXD + QBGAXR + QBGAXN + QBGAMD + QBGAMR + QBGAMN)) * 100

CICS Connection type, thread type, thread number, and transaction ID.

IMS PST number and PSB name.

TSO User ID of jobname.



Reads Due To Cross Invalidation - Data Returned

The number of reads to the group buffer pool required because the page in the member’s buffer pool was invalidated, where the data was found and returned to the member. (QBGAXD)

Reads Due To Cross Invalidation - Data Not Returned (R/W Interest)

The number of reads to the group buffer pool required because the page in the member’s buffer pool was invalidated, where� the data was not found in the group buffer pool and the member had

to go to DASD to read the page, and� other members had read/write interest in the pageset, so DB2 created a

directory entry for this page if it did not already exist. (QBGAXR)

Reads Due To Cross Invalidation - Data Not Returned (No R/W Interest)


to go to DASD to read the page, and� no other member had read/write interest in the pageset, so DB2 did

not have to register the page, since another member cannot cause a cross-invalidation by updating a page. (QBGAXN)

Reads Due to Page Not Found In Buffer

The percentage of total reads to the group buffer pool required because the page was not in the member’s buffer pool. ((QBGAMD + QBGAMR + QBGAMN) / (QBGAXD + QBGAXR + QBGAXN + QBGAMD + QBGAMR + QBGAMN)) * 100

Reads Due To Page Not Found In Buffer - Data Returned

The number of reads to the group buffer pool required because the page was not in the member’s buffer pool, where the data was found and returned to the member. (QBGAMD)

Reads Due To Page Not Found In Buffer - Data Not Returned (R/W Interest)

The number of reads to the group buffer pool required because the page was not in the member’s buffer pool, where� the data was not found in the group buffer pool and the member had


directory entry for this page if it did not already exist. (QBGAMR)

Reads Due To Page Not Found In Buffer - Data Not Returned (No R/W Interest)


to go to DASD to read the page, and� no other member had read/write interest in the pageset, so DB2 did

not have to register the page, since another member cannot cause a cross-invalidation by updating a page. (QBGAMN)

Total Number of Reads

The total number reads under the user task. (QBGAXD + QBGAXR + QBGAXN + QBGAMD + QBGAMR + QBGAMN)

Read Hit Percentage

The percentage of data returned to the total number of reads. If the percentage is small, it may indicate that the group buffer pool size is set too small. ((QBGAXD + QBGAMD) / (QBGAXD + QBGAXR + QBGAXN + QBGAMD + QBGAMR + QBGAMN)) * 100



Percent Not Returned - R/W Interest

The percentage of reads for which data was not returned and other members had read/write interest in the pageset. ((QBGAXR + QBGAMR) / (QBGAXD + QBGAXR + QBGAXN + QBGAMD + QBGAMR + QBGAMN)) * 100

Percent Not Returned - No R/W Interest

The percentage of reads for which data was not returned and no other members had read/write interest in the pageset. ((QBGAXN + QBGAMN) / (QBGAXD + QBGAXR + QBGAXN + QBGAMD + QBGAMR + QBGAMN)) * 100

Changed Pages Number of writes for changed pages. (QBGASW)

Clean Pages Number of writes for clean pages. (QBGAWC)

Group B

uffer Pool Activity

224O

ME

GA

MO

N II for D

B2 H

istorical Reporting G

uide, Version 540

Omegamon II for DB2 V540 Accounting Group Buffer Pool Activity Page 1Run Date=mm/dd/yyy Group by None Run Time=16:38: 32 Start Timestamp=1995-01-24-07.41.21.583811; End Timestamp=1995-01-24-07.43.51.282277; Termination=DEALLOC; ConnType=TSOSysid=SP22, DB2id=D412, Group=TDDB241G, Member=D412, Planname=DSNESPCS, Connid=TSO, Corrid=PANZA, Authid=PANZA,Original Authid=PANZA, CorrName=PANZA, Commits=1, Aborts=1------------------------------------------------------------------------------------------------------------------------------------Group Buffer Pool = 0---------------------------------Read Operations: Reads Due To Cross Invalidation = 20% Reads Due To Page Not Found in Buffer Pool = 80% Data Returned = 0 Data Returned = 2 Data Not Returned - R/W Interest = 2 Data Not Returned - R/W Interest = 6 Data Not Returned - No R/W Interest = 0 Data Not Returned - No R/W Interest = Total Number of Reads = 10 Read Hit Percentage = 20% Data Not Returned - R/W Interest = 80% Data Not Returned - No R/W Interest = 0%Write Operations: Changed Pages = 0 Clean Pages = 0 Start Timestamp=1995-01-24-08.14.38.973183; End Timestamp=1995-01-24-11.18.50.221256; Termination=EOT/ABND; ConnType=TSOSysid=SP22, DB2id=D412, Group=TDDB241G, Member=D412, Planname=DSNESPCS, Connid=TSO, Corrid=PANZA, Authid=PANZA,Original Authid=PANZA, CorrName=PANZA, Commits=0, Aborts=1------------------------------------------------------------------------------------------------------------------------------------Group Buffer Pool = 0---------------------------------Read Operations: Reads Due To Cross Invalidation = 100% Reads Due To Page Not Found in Buffer Pool = 0% Data Returned = 3 Data Returned = 0 Data Not Returned - R/W Interest = 0 Data Not Returned - R/W Interest = 0 Data Not Returned - No R/W Interest = 0 Data Not Returned - No R/W Interest = 0 Total Number of Reads = 3 Read Hit Percentage = 100% Data Not Returned - R/W Interest = 0% Data Not Returned - No R/W Interest = 0%Write Operations: Changed Pages = 4 Clean Pages = 0

FIGURE 23. Accounting Group Buffer Pool Activity (Group by None)




IntroductionThis report displays accounting information about the Distributed Data Facility (DDF), such as the amount of CPU time that elapsed at the local and remote sites, the type of thread involved (distributed allied thread or database access thread), and the activity involving communication between the local and remote systems.

This report shows potential problems with applications using the DDF, such as an excessive number of queued conversations or long remote-wait times.

Note: Refer to the IBM statement in hilev.SDSNMACS (member DSNDQWAC) about the calculation of these values: Total Elapsed Time, Remote Elapsed Time, and Remote CPU Time.

Default DDnameO2RADDF

Default TitleAccounting DDF Activity

Data SourceIFCID 3






Data Elements




ConnType Indicates the type of connecting system (QWHCATYP). Possible values are as follows:� CALLATCH� CICS � DLI� DUW� IMSBMP� IMSBPP� IMSMPP� RUW� TSO



Group Name of the DB2 data sharing group. Applies only to DB2 Version 4 and above. (QWHADSGN)

Member Name of the member within a DB2 data sharing group. Applies only to DB2 Version 4 and above. (QWHAMEMN)




Authid The primary authorization identifier. Actual values depend on the specific DB2 installation and type of connection. (QWHCAID)









Parallel Tasks The number of parallel tasks for this thread. Applies only to DB2 Version 4 and above. (QWACPCNT)

Network ID The network ID. This column contains blanks if the thread is not a distributed thread. (QWHDNETI)

LU Name The logical unit name for this DB2 subsystem. This column contains blanks if the thread is not a distributed thread. (QWHDLUMN)

Unique ID The instance number which, when combined with the network ID and the Luname, uniquely identifies the thread. (QWHDUNIQ)

Requesting Location

The DDF location name of the requesting site. This column contains blanks if the thread is not a distributed thread. (QWHDRQNM)

Requesting Server

The DDF server name of the requesting site. (SRVNAM parameter of DRDA EXCSAT command.) This column contains blanks if the thread is not a distributed thread. (QWHDRQNM)

Remote Location The DDF location name of the remote site associated with the subsequent block of data. (QLACLOCN)

Protocol Used Indicates the protocol used for communication. (QLACFLGS)

Possible values are as follows:� BOTH � SYSTEM� APPLICATION

Message Buffer Rows

Number of rows in the message buffer if block fetch is being used. (QLACBROW)

Block Mode Switches

Number of times a switch was made for continuous block mode to limited block mode. (QLSTCCBLB)

Binds for Remote

Number of SQL statements that were bound for remote access. (QLACBRND)

aTotal Elapsed Time

The amount of time that elapsed at the local site waiting for completion of work by the remote site. (QLACCPUL)

aRemote Elapsed Time

The amount of elapsed time spent processing requests at the remote DB2. This field applies only to system directed access (private protocols). If application directed access (DRDA protocols) is used, this field will be 0. (QLACCPUR)

aRemote CPU Time

The amount of CPU time that elapsed at the remote site. This field applies only to system directed access (private protocols). If application directed access (DRDA protocols) is used, this field will be 0. (QLACDBAT)



Conversations Allocated

Number of successful conversation allocations. (QLACCNVA)

Conversations Queued

The number of conversation requests queued by DDF waiting for allocation. (QLACCNVQ)

Conversations Deallocated

Number of conversations deallocated. (QLACCNVT)

Conversations Max Allocated

Maximum number of allocated conversations. (QLACCIEL)

Remote Coordinated Commits

The number of commit operations performed with the remote location as coordinator. (QLACCPTR)

Remote Coordinated Rollbacks

The number of rollback operations performed with the remote location as coordinator. (QLACRBTR)

Remote Coordinated Indoubts

The number of threads that went indoubt with the remote location as coordinator. (QLACINDT)

Transactions Sent/Received

The number of transactions sent to or received from the remote site. (QLACTRNS/QLACTRNR)

Conversations Sent/Received

The number of conversations sent or received from the remote site. (QLACCNVS/QLACCNVR)

Statements Sent/Received

The number of SQL statements sent to or received from the remote site. (QLACSQLS/QLACSQLR)

Commits Sent/Received

The number of commit requests sent to or received from the remote site. (QLACCOM/QLACCOMR)

Aborts Sent/Received

The number of abort requests sent to or received from the remote site. (QLACABRS/QLACABRR)

Rows Sent/Received

The number of rows sent to or received from the remote site. (QLACROWS/QLACROWR)

Messages Sent/Received

The number of messages sent to or received from the remote site. (QLACMSGS/QLACMSGR)

Bytes Sent/Received

The number of bytes sent to or received from the remote site. (QLACBYTS/QLACBYTR)

Blocks Sent/Received

Number of blocks transmitted or received using block fetch. (QLACBTBF/QLACBRBF)

2-PHASE COMMIT:

Prepares Sent/Received

The number of prepare requests sent to the participant and received from the coordinator. Used only for 2-phase commit. (QLACPRSE/QLACPRRC)

Last Agents Sent/Received

The number of last agent requests sent to the participant and received from the coordinator. Used only for 2-phase commit. (QLACLASE/QLACLARC)


The number of commit requests sent to the participant and received from the coordinator. Used only for 2-phase commit. (QLACCRSE/QLACCRRC)



Backouts Sent/Received

The number of backout requests sent to the participant and received from the coordinator. Used only for 2-phase commit. (QLACBKSE/QLACBKRC)

Forgets Sent/Received

The number of forget requests sent to the coordinator and received from the participant. Used only for 2-phase commit. (QLACRRSE/QLACRRRC)

CommitResps Sent/Received

The number of request commit responses sent to the coordinator and received from the participant. Used only for 2-phase commit. (QLACVYSE/QLACVYRC)

BackoutResps Sent/Received

The number of backout responses sent to the coordinator and received from the participant. Used only for 2-phase commit. (QLACVNSE/QLACVNRC)

a. Refer to the IBM statement in hilev.SDSNMACS (member DSNDQWAC) about the calcu-lation of this value.

Distributed D

ata Facility (DD

F) Activity

230O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 Accounting DDF Activity Page 1Run Date=mm/dd/yyy Grouped by None Run Time=19:59:37 Start Timestamp=1993-10-20-09.42.16.155936; End Timestamp=1993-10-20-09.42.48.378746; Termination=DEALLOC; ConnType=SYSDIRSysid=SYSG, DB2id=D23B, Planname=DSNESPRR, Connid=TSO, Corrid=TDO206B, Authid=TDO206B, Original Authid=TDO206B, Commits=1, Aborts=0LUWID=USCACO01.O2D31A.A84379A7C339, Requesting Location=D31A------------------------------------------------------------------------------------------------------------------------------------Remote Location = D31A Protocol Used = n/a Conversations: (requestor) Message Buffer Rows = 17 Allocated = 0 Block Mode Switches = 0 Queued = 0 Binds for Remote = 0 Deallocated = 0 Max Allocated = 0 Transactions Conversations Statements Commits Aborts Rows Messages Bytes Blocks ------------ ------------- ---------- ----------- ---------- ---------- ---------- ------------ ------------ SENT 0 0 0 0 0 18 3 5258 1 RECEIVED 1 1 2 1 0 0 3 1497 0 Start Timestamp=1993-10-20-09.41.57.005832; End Timestamp=1993-10-20-09.42.47.501422; Termination=DEALLOC; ConnType=TSOSysid=SYSG, DB2id=D31A, Planname=DSNESPRR, Connid=TSO, Corrid=TDO206B, Authid=TDO206B, Original Authid=TDO206B, Commits=2, Aborts=0LUWID=USCACO01.O2D31A.A84379A7C339, Requesting Location=D31A------------------------------------------------------------------------------------------------------------------------------------Remote Location = D23B Protocol Used = SYSTEM Conversations: Remote Coordinated: (server) Message Buffer Rows = 17 Allocated = 1 Commits = 0 Block Mode Switches = 0 Queued = 0 Rollbacks = 0 Binds for Remote = 0 Deallocated = 0 Indoubts = 0 Total Elapsed Time = 00:00:34.099905 Max Allocated = 1 Remote Elapsed Time = 00:00:30.192567 Remote CPU Time = 00:00:00.074291 Transactions Conversations Statements Commits Aborts Rows Messages Bytes Blocks ------------ ------------- ---------- ----------- ---------- ---------- ---------- ------------ ------------ SENT 1 1 2 1 0 0 3 1497 0 RECEIVED 0 0 0 0 0 17 3 5258 1 2-PHASE COMMIT: Prepares Last Agents Commits Backouts Forgets CommitResps BackoutResps ---------- ----------- ---------- ---------- ---------- ------------ ------------ SENT 0 0 0 0 0 0 0 RECEIVED 0 0 0 0 0 0 0

FIGURE 24. Accounting DDF Activity Report (1 of 2)

Historical R


eports231

Distributed D

ata Facility (DD

F) Activity

Start Timestamp=1993-10-11-16.58.27.475789; End Timestamp=1993-10-11-16.58.47.719476; Termination=DEALLOC; ConnType=TSOSysid=SYSG, DB2id=D23B, Planname=DSNESPRR, Connid=TSO, Corrid=TDO209B, Authid=TDO209B, Original Authid=TDO209BCommits=3, Aborts=0Network ID=USCACO01, LU Name=O2D23B, Unique ID=A8388A703337, Requesting Location=D23B------------------------------------------------------------------------------------------------------------------------------------Remote Location = D23A Protocol Used = Application Convs Queued = 0 Convs Allocated = 0 Convs Deallocated = 0 Commits/Remote = 0 Msg Buffer Rows = 0 Max Allocated Convs = 0 Rollbacks/Remote = 0 Binds for Remote = 0 Block Mode Switches = 0 Indoubts/Remote = 0 Total Elapsed Time = 15.880430 Remote Elapsed Time = 13.221047 Remote CPU Time = 0.175184 Trans Convs Statements Commits Aborts Rows Messages Bytes Blocks ---------- ---------- ---------- ----------- ---------- ---------- ---------- ----------- ------------ SENT 0 0 0 0 0 0 2 218 0 RECEIVED 1 1 0 1 0 0 2 159 0 Remote Location = D23C Protocol Used = System Convs Queued = 0 Convs Allocated = 0 Convs Deallocated = 0 Commits/Remote = 0 Msg Buffer Rows = 0 Max Allocated Convs = 0 Rollbacks/Remote = 0 Binds for Remote = 0 Block Mode Switches = 0 Indoubts/Remote = 0 Total Elapsed Time = 15.880430 Remote Elapsed Time = 13.221047 Remote CPU Time = 0.175184 Trans Convs Statements Commits Aborts Rows Messages Bytes Blocks ---------- ---------- ---------- ----------- ---------- ---------- ---------- ----------- ------------ SENT 0 0 0 0 0 0 2 218 0 RECEIVED 1 1 0 1 0 0 2 159 0

FIGURE 25. Accounting DDF Activity Report (2 of 2)

Accounting Detail


Accounting Detail

IntroductionThis report displays detailed information about all aspects of a thread or a group of threads on a one-page report. It contains information that is also found in other separate accounting reports.

Default DDnameO2RADTL

Default TitleAccounting Detail

Data SourceIFCIDs 3, 18, 95, 96




Data Elements





Accounting Detail

ConnType Indicates the type of connecting system (QWHCATYP). Possible values are as follows:� CALLATCH� CICS � DLI� DUW� IMSCNTL� IMSBMP� IMSBPP� IMSMPP� RUW� TSO





Planname The name of the thread. (QWHCPLAN)







TIME AND UNIT OF WORK INFORMATION:

For field definitions for this portion of the Accounting Detail report, refer to “Time Summary” on page 275.




Accounting Detail


PACKAGE DETAIL:

For field definitions for this portion of the Accounting Detail report, refer to “Accounting Package Detail” on page 280.

RESOURCE LIMIT INFORMATION:

For field definitions for this portion of the Accounting Detail report, refer to “Resource Limit Activity” on page 247.

SQL INFORMATION:

For field definitions for this portion of the Accounting Detail report, refer to “SQL Activity” on page 261.

SCAN INFORMATION:

For field definitions for this portion of the Accounting Detail report, refer to “Scan Activity” on page 254.

SORT INFORMATION:

For field definitions for this portion of the Accounting Detail report, refer to “Sort Activity” on page 258.

LOCK INFORMATION:

For field definitions for this portion of the Accounting Detail report, refer to “Lock Activity” on page 239.

BUFFER MANAGER:

For field definitions for this portion of the Accounting Detail report, refer to “Buffer Pool Activity” on page 216.

DISTRIBUTED INFORMATION:

For field definitions for this portion of the Accounting Detail report, refer to “Distributed Data Facility (DDF) Activity” on page 225.

PARALLEL TASK INFORMATION:

This section appears only if no grouping is performed and parallel tasks were created. For field definitions for this portion of the Accounting Detail report, refer to “Parallel Task Activity” on page 251.

Historical R


eports235

Accounting D

etail

Omegamon II for DB2 V540 Accounting Detail Page 1Run Date=mm/dd/yyy Grouped by None Run Time=15:21:04 Start Timestamp=1995-07-12-09.48.40.544650; End Timestamp=1995-07-12-09.48.40.875611; Termination=DEALLOC; ConnType=TSOSysid=SP13, DB2id=D411, Planname=DSNESPCS, Connid=TSO, Corrid=PANZA2, Authid=PANZA2, Original Authid=PANZA2Commits=0, Aborts=1, Parallel Tasks=8LUWID=USCACO01.O2D31A.A84379EC007A, Requesting Location=D31A------------------------------------------------------------------------------------------------------------------------------------*** TIME AND UNIT OF WORK INFORMATION: Elapsed Time TCB Time SRB Time StProc TCB TimeTotals: 001:21:25.592153 000:00:23.307078 000:00:24.779917 000:00:00.000000In-DB2: 000:08:44.889655 000:00:23.108399 000:00:24.551310 000:00:00.000000 Count Time Count TimeWaits: Lock Waits = 569 000:00:22.965773 I/O Waits = 8 000:00:00.363278 Drain Lock Waits = 0 000:00:00.000000 Asynch Read Waits = 113 000:00:10.955616 Claimer Drain Waits = 0 000:00:00.000000 Asynch Write Waits = 0 000:00:00.000000 Service Waits = 1 000:00:00.007169 Archive Log Waits = 0 000:00:00.000000 Page Latch Waits = 0 000:00:00.000000 Archive Read Waits = 0 000:00:00.000000 Send Message Waits = 0 000:00:00.000000 StProc Schedule Waits = 0 000:00:00.000000 Global Lock Waits = 0 000:00:00.000000 *** RESOURCE LIMITING INFORMATION:RLF Table Suffix = 01 RLF Limit Origin = Limit from blank Authid & Plan (default row)Limit in MVS SU’s = 565000 Limit in Cputime = 03:51.120303 CPU Used High Water Mark = 00:00.008639 *** SQL INFORMATION:DML Statements: Select = 0 Insert = 0 Open Cursor = 6 Prepare = 6 Update = 0 Fetch = 10705 Describe = 1 Delete = 0 Close Cursor = 6 Describe Table = 0 DDL Statements: --------------- Create -------- Drop ------ Alter ------------------ Create ---------- Drop --------- Alter Table = 0 0 0 Tablespace = 0 0 0 View = 0 0 n/a Index = 0 0 0 Alias = 0 0 n/a Database = 0 0 0 Synonym = 0 0 n/a StoGroup = 0 0 0 Package = n/a 0 n/a DCL Statements: Grant = 0 Revoke = 0 Set Host Var = 0 Set Cur SQLid = 0 Lock Table = 0 Set Cur Rules = 0 Set Cur Degree = 1 Release = 0 Connect 1 = 0 Connect 2 = 0 Set Connection = 0

FIGURE 26. Accounting Detail Report (1 of 4)

Accounting D

etail

236O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Miscellaneous: SQL Call = 0 Comment On = 0 Label On = 0 Incremental Bind = 0 Rid Pool Access: Successful = 91 Not Used due to Limit Exceeded = 0 Not Used due to No Storage = 0 Query Parallelism: Max Degree = 4 Parallel Groups Executed = 2 Sequential Mode - Cursor = 0 Planned Parallel Degree Executed = 2 Sequential Mode - No Buffer = 0 Reduced Parallel Degree Executed = 0 Sequential Mode - No ESA Sort = 0 Parallelism Disabled By RLF = No Sequential Mode - No Enclave = 0 Stored Procedure: SQL Call = 0 Stored Procedure Abended = 0 SQL Call Statement Timed Out = 0 SQL Call Statement Rejected = 0*** SORT INFORMATION:Sort Count = 5 Elapsed Time = 000:00:00.000000 Workfiles = 4 Workfile Inserts = 9035Recs Sorted = 9688 CPU Time = 000:00:00.000000 Workfile Retrievals = 9035 *** SCAN INFORMATION:Data Type Scan Count Rows Processed Rows Updated Rows Inserted Rows Deleted Pg Scanned Rows Del/RI Pg Scanned/RI--------- ---------- --------------- --------------- --------------- --------------- ---------- ----------- -------------Data 52 71085 0 0 0 5546 0 0Index 177 234 0 0 0 257Workfile 16 18723 0 18692 0 1268 *** LOCK INFORMATION:Lock Requests = 269 Deadlocks = 0 Lock Suspends = 0 Other Suspends = 0Unlock Requests = 33 Timeouts = 0 Latch Suspends = 1 Escalations/SHR = 0Change Requests = 1 Claim Requests = 12 Drain Requests = 0 Escalations/EXCL = 0Query/Other Reqs = 0 Failed Claims = 0 Failed Drains = 0 Maximum Page Locks = 16 *** GLOBAL LOCK INFORMATION:P-Lock Lock Requests = 23 Lock Requests Propagated to XES = 120 Suspends - IRLM Global Contention = 0P-Lock Change Requests = 0 Change Requests Propagated to XES = 0 Suspends - XES Global Contention = 0P-Lock Unlock Requests = 0 Unlock Requests Propagated to XES = 0 Suspends - False Contention = 15Incompatible Retained Locks = 0 % of L-Locks Propagated to XES = 0% % of Suspends - False Contention = 100%Notify Messages Sent = 0


Historical R


eports237

Accounting D

etail

*** BUFFER MANAGER INFORMATION:Buffer Pool = 0----------------------------Getpage Requests = 48864 Failed Getpage Requests = 0 Synchronous Read I/O = 9 Getpage/Read I/O = 7.67Page Updates = 0 Seq Prefetch Requests = 1536 Dynamic Prefetch Req = 0 List Prefetch Req = 0Prefetch Pg Reads = 925 Prefetch Pg in Hiperpool= 0 Hiperpool Reads = 0 Failed HP Reads = 0Hiperpool Writes = 0 Failed Hiperpool Writes = 0 Immediate Writes = 0BP Hit Percentage = 95% HP Hit Percentage = 0% *** BUFFER MANAGER INFORMATION:Group Buffer Pool = 0----------------------------Read Operations: Reads Due To Cross Invalidation = 25% Reads Due To Page Not Found in Buffer Pool = 75% Data Returned = 100 Data Returned = 300 Data Not Returned - R/W Interest = 15 Data Not Returned - R/W Interest = 45 Data Not Returned - No R/W Interest = 10 Data not Returned - No R/W Interest = 30 Total Number of Reads = 500 Read Hit Percentage = 80% Percent Not Returned - R/W Interest = 12% Percent Not Returned - No R/W Interest = 8%Write Operations: Changed Pages = 15 Clean Pages = 2*** DISTRIBUTED INFORMATION:Remote Location = D31A Protocol Used = n/a Conversations: Remote Coordinated: (requestor) Message Buffer Rows = 17 Allocated = 0 Commits = 2 Block Mode Switches = 0 Queued = 0 Rollbacks = 0 Binds for Remote = 0 Deallocated = 0 Indoubts = 0 Max Allocated = 0 Transactions Conversations Statements Commits Aborts Rows Messages Bytes Blocks ------------ ------------- ---------- ----------- ---------- ---------- ---------- ------------ ------------ SENT 0 0 0 0 0 2 2 3528 0 RECEIVED 1 1 2 1 0 0 3 1718 0 2-PHASE COMMIT: Prepares Last Agents Commits Backouts Forgets CommitResps BackoutResps ---------- ----------- ---------- ---------- ---------- ------------ ------------ SENT 0 0 0 0 0 0 0 RECEIVED 0 0 0 0 0 0 0


Accounting D

etail

238O

ME

GA

MO

N II for D

B2 H


uide, Version 540

*** PACKAGE DETAIL:Program = DSNESM68 Type = Package Collection = DSNESPCS Token = 149EEA901A79FE48 Location = D41G General: In-DB2 Time = 00:08:44.889556 SQL Requests = 14 In-DB2 CPU Time = 00:00:23.108322 Entry/Exit Events = 38 Count Time Count TimeWaits: Lock Waits = 569 00:00:22.965773 I/O Waits = 8 00:00:00.363278 Drain Lock Waits = 0 00:00:00.000000 Asynch Read Waits = 113 00:00:10.955616 Claimer Drain Waits = 0 00:00:00.000000 Asynch Write Waits = 0 00:00:00.000000 Page Latch Waits = 0 00:00:00.000000 Archive Log Waits = 0 00:00:00.000000 Service Waits = 1 00:00:00.007169 Archive Read Waits = 0 00:00:00.000000 Send Message Waits = 0 00:00:00.000000 StProc Schedule Waits = 0 00:00:00.000000 Global Lock Waits = 0 00:00:00.000000 *** PARALLEL TASK DETAIL: Read I/O I/O Other OtherStart Timestamp End Timestamp Elapsed Time CPU Time Getpages I/O Prefetch Waits Wait Time Waits Wait Time----------------------- ----------------------- ------------ --------- ---------- ------- -------- ------ --------- ------ ---------1995-07-12-11.08.17.955 1995-07-12-11.09.06.061 00:00:48.105 00:02.608 6101 1 192 22 00:01.839 61 00:02.4511995-07-12-11.08.17.964 1995-07-12-11.09.06.348 00:00:48.383 00:02.603 6101 1 192 25 00:02.370 65 00:02.0371995-07-12-11.08.17.983 1995-07-12-11.09.06.914 00:00:48.931 00:02.613 6101 1 192 19 00:01.437 63 00:02.1991995-07-12-11.08.18.037 1995-07-12-11.09.06.630 00:00:48.593 00:02.624 6101 1 192 21 00:02.498 61 00:02.3321995-07-12-11.09.07.102 1995-07-12-11.10.04.129 00:00:57.027 00:03.137 6101 1 192 5 00:00.461 77 00:04.2851995-07-12-11.09.07.103 1995-07-12-11.10.00.407 00:00:53.304 00:03.082 6101 1 192 10 00:01.195 76 00:02.4921995-07-12-11.09.07.117 1995-07-12-11.10.04.181 00:00:57.063 00:03.109 6101 1 192 9 00:00.546 77 00:02.6981995-07-12-11.09.07.170 1995-07-12-11.10.04.118 00:00:56.947 00:03.229 6101 1 192 10 00:00.970 88 00:04.447



Lock Activity

Lock Activity

IntroductionThis report displays a summary of lock activity for an individual thread or group of threads, including the total number of deadlocks and timeouts, lock manager requests, and lock escalations, as well as the number of claim and drain requests.

This report is used to view the total number of deadlocks and timeouts occurring within specific applications and to analyze whether or not the number conforms to your standards. The report information can help you determine whether or not the number of lock escalations or timeout/deadlock occurrences is high for a specific application.

Default DDnameO2RALCK

Default TitleAccounting Locking Activity

Data SourceIFCID 3




Lock Activity


Data Elements



Termination Indicates the reason the accounting record was externalized. (ZQACRINV)













Lock Requests The number of lock requests issued to IRLM. (QTXALOCK)

Unlock Requests The number of unlock requests issued to IRLM. (QTXAUNLK)

Change Requests

The number of change requests issued to IRLM. (QTXACHG)





Lock Activity

Query/Other Requests

The number of other types of lock manager requests issued to IRLM. (QTXAIRLM)

Deadlocks The number of deadlocks detected. (QTXADEA)

Timeouts The number of lock timeouts detected. (QTXATIM)

Claim Requests The number of claim requests. (QTXACLNO)

Failed Claims The number of unsuccessful claim requests. (QTXACLUN)

Lock Suspends The number of lock suspensions detected due to locking conflict. (QTXASLOC)

Latch Suspends The number of suspensions due to a latch conflict. (QTXASLAT)

Drain Requests The number of drain requests. (QTXADRNO)

Failed Drains The number of unsuccessful drain requests. (QTXADRUN)

Other Suspends The number of suspensions due to a reason other than locking or latching. (QTXASOTH)

Escalations/SHR The number of shared lock escalations incurred. (QTXALES)

Escalations/EXCL

The number of exclusive lock escalations incurred. (QTXALEX)

Max Page Row Locks

The maximum number of page locks held during applications execution. (QTXANPL)

Lock Activity

242O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 Accounting Lock Activity Page 1Run Date=mm/dd/yyy Grouped by None Run Time=12.43.07 Ordered by DB2id Start Timestamp=1995-03-09-12.11.01.774567; End Timestamp=1995-03-09-12.15.16.207443; Termination=DEALLOCSysid=SP22, DB2ID=A410, Planname=JACK4040, Connid=DB2CALL, Corrid=TDDB20A, Original Authid=TDDB20ACommits=8, Aborts=2------------------------------------------------------------------------------------------------------------------------------------Lock Requests = 11653 Deadlocks = 5 Lock Suspends = 8 Other Suspends = 3Unlock Requests = 8065 Timeouts = 2 Latch Suspends = 9 Escalations/SHR = 0Change Requests = 421 Claim Requests = 206 Drain Requests = 10 Escalations/EXCL = 0Query/Other Requests = 5 Failed Claims = 0 Failed Drains = 0 Max Page/Row Locks = 12 Start Timestamp=1995-03-09-13.21.01.797123; End Timestamp=1995-03-09-13.25.16.298714; Termination=DEALLOCSysid=SYSG, DB2ID=B310, Planname=JACK3030, Connid=DB2CALL, Corrid=TDDB20B, Original Authid=TDDB20BCommits=4, Aborts=1------------------------------------------------------------------------------------------------------------------------------------Lock Requests = 2593 Deadlocks = 0 Lock Suspends = 1 Other Suspends = 1Unlock Requests = 436 Timeouts = 1 Latch Suspends = 29 Escalations/SHR = 0Change Requests = 109 Claim Requests = 181 Drain Requests = 22 Escalations/EXCL = 0Query/Other Requests = 1 Failed Claims = 0 Failed Drains = 0 Maximum Page Locks = 19 Start Timestamp=1995-03-09-14.31.01.987647; End Timestamp=1995-03-09-14.35.06.876253; Termination=DEALLOCSysid=SYSG, DB2ID=C230, Planname=JACK2020, Connid=DB2CALL, Corrid=TDDB20C, Original Authid=TDDB20CCommits=6, Aborts=1------------------------------------------------------------------------------------------------------------------------------------Lock Requests = 6434 Deadlocks = 0 Lock Suspends = 0 Escalations/SHR = 0Unlock Requests = 2825 Timeouts = 0 Latch Suspends = 129 Escalations/EXCL = 0Change Requests = 224 Query/Other Reqs = 0 Other Suspends = 0 Maximum Page Locks = 10

FIGURE 30. Accounting Lock Activity Report




IntroductionThis report displays global lock activity for an individual thread or group of threads. Data includes global lock requests, lock requests propagated to XES, and the number of false contentions. This report applies only to those DB2s within a DB2 data sharing group.




� determining if false contention is too high

Default DDnameO2RAGLK

Default TitleAccounting Global Lock Activity

Data SourceIFCID 3




Data Elements

Group The name of DB2 data sharing group. Applies only to DB2 Version 4 and above. (QWHADSGN)

Member The name of the DB2 member within a DB2 data sharing group. Applies only to DB2 Version 4 and above. (QWHAMEMN)









P-Lock Lock Requests

Number of lock requests for P-locks. (QTGALPLK)

P-Lock Change Requests

Number of change requests for P-locks. (QTGACPLK)

P-Lock Unlock Requests

Number of unlock requests for P-locks. (QTGAUPLK)

Notify Messages Sent

Number of notify messages sent. (QTGANTFY)

Incompatible Retained Locks

The number of global lock or change requests that failed because of an incompatible retained lock. When certain P-locks are retained because of a system failure. Another DB2 member cannot access the data that the retained P-lock is protecting unless it requests a P-lock in a compatible state. (QTGADRTA)

Lock Requests Propagated to XES

Number of lock requests (both logical and physical) that are propagated to MVS XES synchronously under the caller’s execution unit. This count does not include suspended requests. Only the most restrictive lock for a particular resource is propagated to XES and the coupling facility. (QTGALSLM)

Change Requests Propagated to XES

Number of change requests (both logical and physical) that are propagated to MVS XES synchronously under the caller’s execution unit. This count does not include suspended requests. (QTGACSLM)

Unlock Requests Propagated to XES

Number of unlock requests (both logical and physical) that are propagated to MVS XES synchronously under the caller’s execution unit. This count does not include suspended requests. (QTGAUSLM)






% of L-Locks Propagated to XES

Percentage of total L-lock requests (lock, change, and unlock) that were propagated to XES. ((((QTGALSLM - QTGALPLK) * 2) + (QTGACSLM - QTGACPLK))/((QTXALOCK * 2) + QTXACHG)) * 100

Suspends - IRLM Global Contention

Number of suspends caused by IRLM Global resource contention. IRLM lock states were in conflict and intersystem communication is required to resolve the conflict. (QTGAIGLO)

Suspends - XES Global Contention

Number of suspends caused by XES global resource contention that were not IRLM-level contentions. XES lock states were in conflict but the IRLM lock states were not. (QTGASGLO)

Suspends - False Contention

Number of suspends caused by MVS XES false contentions. XES detects hash class contention when two different locks on different resources hash to the same entry in the coupling facility lock table. The requester is suspended until it is determined that there is no real lock contention. (QTGAFLSE)

% of Suspends - False Contention

Percentage of suspends caused by false contentions relative to all suspends due to IRLM/XES contention. This indicates the ratio of false versus real contentions. This number should be no more than 50%. (QTGAFLSE/(QTGAFLSE + QTGASGLO + QTGAIGLO)) * 100

Global L

ock Activity

246O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 Accounting Global Lock Activity Page 1Run Date=mm/dd/yyy Group by None Run Time=16:34:54 Start Timestamp=1995-10-27-12.58.48.199554; End Timestamp=1995-10-27-13.01.52.128129; Termination=DEALLOC; ConnType=TSODB2id=D411, Sysid=SP13, Group=TDDB241G, Member=D411, Planname=DSNESPCS, Connid=TSO, Corrid=PANZA3, Authid=PANZA3,Original Authid=PANZA3, CorrName=PANZA3, Commits=2, Aborts=0------------------------------------------------------------------------------------------------------------------------------------P-Lock Lock Requests = 2 Lock Requests Propagated to XES = 11 Suspends - IRLM Global Contention = 0P-Lock Change Requests = 0 Change Requests Propagated to XES = 0 Suspends - XES Global Contention = 0P-Lock Unlock Requests = 0 Unlock Requests Propagated to XES = 8 Suspends - False Contention = 0Notify Messages Sent = 0 % of L-Locks Propagated to XES = 32% % of Suspends - False Contention = 0%Incompatible Retained Locks = 0 Start Timestamp=1995-10-27-13.01.34.374128; End Timestamp=1995-10-27-13.07.50.860273; Termination=DEALLOC; ConnType=TSODB2id=D411, Sysid=SP13, Group=TDDB241G, Member=D411, Planname=DSNESPCS, Connid=TSO, Corrid=PANZA2, Authid=PANZA2,Original Authid=PANZA2, CorrName=PANZA2, Commits=2, Aborts=0------------------------------------------------------------------------------------------------------------------------------------P-Lock Lock Requests = 68 Lock Requests Propagated to XES = 208 Suspends - IRLM Global Contention = 8P-Lock Change Requests = 4 Change Requests Propagated to XES = 7 Suspends - XES Global Contention = 0P-Lock Unlock Requests = 13 Unlock Requests Propagated to XES = 124 Suspends - False Contention = 12Notify Messages Sent = 6 % of L-Locks Propagated to XES = 47% % of Suspends - False Contention = 60%Incompatible Retained Locks = 0

FIGURE 31. Accounting Global Lock Activity (Group by None)


Resource Limit Activity


IntroductionThis report displays information for the Resource Limit Facility, including the average or highest CPU time used and the number of times threads exceeded the maximum CPU time limit.

This report identifies the applications that used the most CPU time. The report information can help you determine the resource limit value for each application.

Note: Refer to the IBM statement in hilev.SDSNMACS (member DSNDQWAC) about the calculation of these values: Avg CPU Time, and Max CPU Time.

Default DDnameO2RARLF

Default TitleAccounting Resource Limit Activity

Data SourceIFCID 3

Group By ElementsAUTHID, HOUR, DAY, DB2ID, CONNID, CORRID, CONNTYPE, CORRNAME, ORIGAUTHID, PLANNAME, SYSID, LUWID, MEMBER, GROUP



Data Elements







Authid The primary authorization identifier. Actual values depend on the specific DB2 installation and the type of connection. (QWHCAID)


Threads The number of threads that are included in this group when Group By is used.

Commits The number of successful commits completed by the thread. For attachments that use the 2-phase commit protocol, this count reflects the number of phase-2 commits. For attachments that do not use the 2-phase commit protocol, this count reflects the number of successful sync requests processed. (QWACCOMM)



Limit Origin:

Limit Origin How the Resource Limit Facility origin was derived, if RLF was active for the thread. (ZTXAPREC)

Total Count The number of individual threads with that limit origin.

aAvg CPU Time The average CPU time per thread.

aMax CPU Time The maximum CPU time for all threads of that origin.

Plan/Authid Limit by specific authid and plan. (QTXAPREC=QTXAPRC1)

Authid Any Plan Limit by specific authid. (QTXAPREC=QTXAPRC2)

Plan Any Authid Limit by specific plan. (QTXAPREC=QTXAPRC3)

Any Plan/Authid Limit by any plan/authid. (QTXAPREC=QTXAPRC4)

Default/No Entry Limit by DSNZPARM default. (QTXAPREC=QTXAPRC5)

Default/I/O Error Limit by DSNZPARM I/O error. (QTXAPREC = QTXAPRC6)

No Limit The number of threads that ran not limited because the DSNZPARM default was specified as NOLIMIT, or the ASUTIME was set to NULL in the resource limit table entry that qualifies the thread or the user had SYSADM/ SYSOPR authority. (QTXAILMT)

SysAdm No limit applied to Sysadm or Sysopr. (QTXAPREC=QTXAPRC7)

No Run The number of threads not run because either NORUN was specified as the DSNZPARM default or an ASUTIME of zero or less was set in the resource limit table entry that limited the thread. (QTXANRUN)

Limit Met The number of threads that exceeded the ASU limit in effect for the limit origin. (QTSACHUZ > QTXACLMT).

Authid/Coll/Pkg Limit by specific authid, collection, and package. (QTXAPREC = QTXAPRC8)

Authid Any Pkg Limit by specific authid running any package. (QTXAPREC = QTXAPRC9)



Authid Any Coll Limit by specific authid running any collection. (QTXAPREC = QTXAPRC10)

Authid Any Coll/Pkg

Limit by specific authid running any collection and package. (QTXAPREC = QTXAPRC11)

Coll/Pkg Any Authid

Limit by specific collection and package for any authid. (QTXAPREC = QTXAPRC12)

Any Pkg/Authid Limit by any authid or package. (QTXAPREC = QTXAPRC13)

Any Coll/Authid Limit by any authid or collection. (QTXAPREC = QTXAPRC14)

Any Coll/Authid/Pkg

Limit by any authid or collection or package. (QTXAPREC = QTXAPRC15)


Resource L

imit A

ctivity

250O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 Accounting Resource Limit Activity Page 1Run Date=mm/dd/yyy Grouped by DB2id, Authid, PlanName Run Time=10:39:11 Sysid=SYSG, DB2id=D22A, Authid=TDDB20A, Planname=JACK2020, Threads=1, Commits=1, Aborts=1------------------------------------------------------------------------------------------------------------------------------------ Authid Plan Any Plan/ Default/ Default/Limit Origin: Plan/Authid Any Plan Any Authid Authid No Entry I/O Error No Limit SysAdm No Run Limit Met------------- ----------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ----------Total Count 0 0 0 0 0 0 0 0 0 0Avg CPU Time 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000Max CPU Time 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 Authid/ Authid Authid Authid Any Pkg/Coll Any Pkg/ Any Coll/ Any Coll/ Pkg/Coll Any Pkg Any Coll Pkg/Coll Any Authid Authid Authid Authid/Pkg ----------- ---------- ---------- ---------- ---------- ---------- ---------- ----------Total Count 0 0 0 0 0 0 0 0Avg CPU Time 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000Max CPU Time 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 Sysid=SYSG, DB2id=D23A, Authid=MX20, Planname=JNLP1PLN, Threads=8, Commits=0, Aborts=4------------------------------------------------------------------------------------------------------------------------------------ Authid Plan Any Plan/ Default/ Default/Limit Origin: Plan/Authid Any Plan Any Authid Authid No Entry I/O Error No Limit SysAdm No Run Limit Met------------- ----------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ----------Total Count 0 0 0 0 0 0 0 0 0 0Avg CPU Time 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000Max CPU Time 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 Authid/ Authid Authid Authid Any Coll/Pkg Any Pkg/ Any Coll/ Any Coll/ Coll/Pkg Any Pkg Any Coll Coll/Pkg Any Authid Authid Authid Authid/Pkg ----------- ---------- ---------- ---------- ---------- ---------- ---------- ----------Total Count 0 0 0 0 0 0 0 0Avg CPU Time 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000Max CPU Time 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000

FIGURE 32. Accounting Resource Limit Activity Report


Parallel Task Activity


IntroductionThis report:

� provides a summary of activity performed by each individual parallel task.

� helps you determine the effectiveness of parallel processing.

� applies only to DB2 Version 4 and above.

Note: Refer to the IBM statement in hilev.SDSNMACS (member DSNDQWAC) about the calculation of these values: Elapsed, and CPU Time.

Default DDnameO2RATSK

Default TitleAccounting Parallel Task Activity

Data SourceIFCID 3

Group By ElementsMEMBER, GROUP



Data Elements

Start Timestamp The time the parallel task was created.

End Timestamp The time the parallel task terminated.










aElapsed The total elapsed time of the parallel task.

aCPU Time The total CPU time used by a parallel task expressed in seconds.

Getpages The number of getpage requests for a parallel task.

Read I/O The number of synchronous read I/O requests.

Prefetch The number of sequential/list/dynamic prefetch requests.

I/O Waits The total number of times that a parallel task had to wait for an I/O event to complete, including synchronous and asynchronous reads or writes. N/A is displayed if accounting class 3 is not active.

I/O Wait Time The total amount of time that a parallel task had to wait for an I/O event to complete. N/A is displayed if accounting class 3 is not active.

Other Waits The total number of times that a parallel task had to wait for a non-I/O related class 3 event to complete. This number includes waits for locks, latches, drains, service tasks, and log reads. N/A is displayed if accounting class 3 is not active.

Other Wait Time The total amount of time that a parallel task had to wait for a non-I/O related class 3 event to complete. N/A is displayed if accounting class 3 is not active.





Historical R


eports253


Omegamon II for DB2 V540 Accounting Parallel Task Activity Page 1 Run Date=16.10.1995 Grouped by None Run Time=16.54.39 Start Timestamp=1995-10-16-15.04.54.266627; End Timestamp=1995-10-16-15.07.56.196900; Termination=DEALLOC; ConnType=TSO Sysid=SP13, DB2id=D41B, Planname=DSNESPCS, Connid=TSO, Corrid=PANZA2, Authid=PANZA2, Original Authid=PANZA2 Commits=2, Aborts=0, Parallel Tasks=4 ------------------------------------------------------------------------------------------------------------------------------------ Read I/O I/O Other Other Start Timestamp End Timestamp Elapsed Time CPU Time Getpages I/O Prefetch Waits Wait Time Waits Wait Time ----------------------- ----------------------- ------------ -------- ---------- ------- -------- ------ --------- ------ --------- 1995-10-16-15.04.57.090 1995-10-16-15.05.59.231 62.142 0.006 0 0 0 0 0.000 3 61.744 1995-10-16-15.04.57.096 1995-10-16-15.05.59.587 62.491 0.005 0 0 0 0 0.000 3 62.208 1995-10-16-15.04.57.109 1995-10-16-15.05.59.881 62.772 0.005 0 0 0 0 0.000 3 62.502 1995-10-16-15.04.57.127 1995-10-16-15.06.57.684 120.557 0.005 0 0 0 0 0.000 4 120.318 Start Timestamp=1995-10-16-16.41.06.184994; End Timestamp=1995-10-16-16.41.49.950641; Termination=DEALLOC; ConnType=TSO Sysid=SP13, DB2id=D411, Planname=DSNESPCS, Connid=TSO, Corrid=PANZA2, Authid=PANZA2, Original Authid=PANZA2 Commits=3, Aborts=0, Parallel Tasks=4 ------------------------------------------------------------------------------------------------------------------------------------ Read I/O I/O Other Other Start Timestamp End Timestamp Elapsed Time CPU Time Getpages I/O Prefetch Waits Wait Time Waits Wait Time ----------------------- ----------------------- ------------ -------- ---------- ------- -------- ------ --------- ------ --------- 1995-10-16-16.41.09.447 1995-10-16-16.41.31.724 22.278 2.974 6103 3 192 137 6.123 89 1.812 1995-10-16-16.41.09.450 1995-10-16-16.41.35.197 25.746 2.916 6103 3 192 123 5.810 120 5.174 1995-10-16-16.41.09.458 1995-10-16-16.41.41.521 32.064 2.949 6103 3 192 169 15.506 107 2.644 1995-10-16-16.41.09.459 1995-10-16-16.41.36.691 27.233 3.003 6103 3 192 134 5.988 116 6.360 Start Timestamp=1995-10-16-16.41.58.026601; End Timestamp=1995-10-16-16.42.23.189121; Termination=DEALLOC; ConnType=TSO Sysid=SP13, DB2id=D411, Planname=DSNESPCS, Connid=TSO, Corrid=PANZA2, Authid=PANZA2, Original Authid=PANZA2 Commits=3, Aborts=0, Parallel Tasks=4 ------------------------------------------------------------------------------------------------------------------------------------ Read I/O I/O Other Other Start Timestamp End Timestamp Elapsed Time CPU Time Getpages I/O Prefetch Waits Wait Time Waits Wait Time ----------------------- ----------------------- ------------ -------- ---------- ------- -------- ------ --------- ------ --------- 1995-10-16-16.41.59.763 1995-10-16-16.42.17.213 17.449 2.904 6101 1 192 172 9.877 108 0.427 1995-10-16-16.41.59.767 1995-10-16-16.42.17.709 17.942 2.846 6101 1 192 167 9.467 113 0.259 1995-10-16-16.41.59.771 1995-10-16-16.42.18.306 18.535 2.890 6101 1 192 171 10.726 123 0.426 1995-10-16-16.41.59.772 1995-10-16-16.42.17.361 17.589 2.864 6101 1 192 169 9.561 123 0.355

FIGURE 33. Parallel Task Activity Report

Scan Activity


Scan Activity

IntroductionThis report provides a summary of scan activity.

This report identifies the application programs that should be reviewed if scan activity is frequently causing high CPU or I/O overhead. The report information reveals which applications are triggering an excessive amount of scan activity.

Default DDnameO2RASCN

Default TitleAccounting Scan Activity




Select ElementsAUTHID, DB2ID, CONNID, CORRID, CONTYPE, CORRNAME, ORIGAUTHID,

PLANNAME, SYSID, LUWID, MEMBER, GROUP

Data Elements

Start Date The beginning date for the period covered by this accounting row. (ZWHSDATE)

Hour The beginning hour for the period covered by this accounting row. (ZWHSHOUR)




Scan Activity



Threads The number of threads in the group.




Data Type N/A for draft

The valid data types are as follows:� data � index� workfile

Data:

Scan Count The number of data pagesets scanned. (ZWSD18CT)

Rows Processed The number of data rows processed. (ZWSD18RP)

Rows Updated The number of data rows updated. (ZWSD18UP)

Rows Inserted The number of data rows inserted. (ZWSD18IN)

Rows Deleted The number of data rows deleted. (ZWSD18DE)

Pg Scanned The number of data pages scanned. (ZWSD18PS)

Rows Del/RI The number of rows deleted or set to null to enforce referential integrity constraints. (ZW0018DR)

Pg Scanned/RI The number of pages scanned to enforce referential integrity constraints. (ZW0018PR)

Index:

Scan Count The number of index pagesets scanned. (ZWIX18CT)

Rows Processed The number of index rows processed. (ZWIX18RP)

Rows Updated The number of index rows updated. (ZWIX18UP)

Rows Inserted The number of index rows inserted. (ZWIX18IN)

Rows Deleted The number of index rows deleted. (ZWIX18DE)

Pg Scanned The number of index pages scanned. (ZWIX18PS)

Workfile:

Scan Count The number of data workfiles scanned. (ZWSW18CT)

Rows Processed The number of data workfile rows processed. (ZWSW18RP)

Scan Activity


Rows Updated The number of data workfile rows updated. (ZWSW18UP)

Pg Inserted The number of data workfile rows inserted. (ZWSW18IN)

Pg Deleted The number of data workfile rows deleted. (ZWSW18DE)

Pg Scanned The number of data workfile pages scanned. (ZWSW18PS)

Historical R


eports257

Scan A

ctivity

OMEGAMON II for DB2 V540 Accounting Scan Activity Page 1Run Date=mm/dd/yyy Grouped by Hour, PlanName Run Time=08:50:13 Start Date=mm/dd/yyy, Hour=17Sysid=SYSG, Planname=BINDCT, Threads=4, Commits=6, Aborts=0------------------------------------------------------------------------------------------------------------------------------------Data Type Scan Count Rows Processed Rows Updated Rows Inserted Rows Deleted Pg Scanned Rows Del/RI Pg Scanned/RI--------- ---------- -------------- ------------ ------------- ------------ ---------- ----------- -------------Data 2306 166 2 2068 1037 4117 0 0Index 686 862 0 243 114 1246Workfile 0 0 0 0 0 0 Start Date=mm/dd/yyy, Hour=17Sysid=SYSG, Planname=DBD22AX, Threads=1, Commits=0, Aborts=1------------------------------------------------------------------------------------------------------------------------------------Data Type Scan Count Rows Processed Rows Updated Rows Inserted Rows Deleted Pg Scanned Rows Del/RI Pg Scanned/RI--------- ---------- -------------- ------------ ------------- ------------ ---------- ----------- -------------Data 12 60748 0 0 0 2043 0 0Index 17 67 0 0 0 40Workfile 4 2126 0 380 0 53 Start Date=mm/dd/yyy, Hour=17Sysid=SYSG, Planname=TSTPLAN, Threads=52, Commits=53, Aborts=0------------------------------------------------------------------------------------------------------------------------------------Data Type Scan Count Rows Processed Rows Updated Rows Inserted Rows Deleted Pg Scanned Rows Del/RI Pg Scanned/RI--------- ---------- -------------- ------------ ------------- ------------ ---------- ----------- -------------Data 124 18212 0 0 0 1230 0 0Index 198 252 0 0 0 360Workfile 18 173 0 166 0 45

FIGURE 34. Accounting Scan Activity

Sort Activity


Sort Activity

IntroductionThis report displays a summary of sort activity.

This report identifies the application programs that should be reviewed if sort activity is causing high CPU overhead. The report information reveals which applications are triggering an excessive amount of sort activity per execution.

Note: Refer to the IBM statement in hilev.SDSNMACS (member DSNDQWAC) about the calculation of these values: Elapsed Time, and CPU Time.

Default DDnameO2RASRT

Default TitleAccounting Sort Activity

Data SourceIFCIDs 3, 95, 96




Data Elements

Start Date The beginning date for the period covered by this accounting row. (ZWHSDATE)

Hour The beginning hour for the period covered by this accounting row. (ZWHSHOUR)



Sort Activity




Threads The number of threads in the group.



Sort Count The total number of sorts observed during the report time interval. (ZW0096CT)

Recs Sorted The total number of records sorted during the report time interval. (QW0096NR)

Workfiles The number of logical workfiles used for the sort activity. This is a high-water mark; maximum value is 255. (QW0096WF)

WF Inserts The number of records inserted into the work files. (QW0096IN)

WF Retrievals The number of records retrieved from the work files. (QW0096RD)

aElapsed Time The total elapsed time spent performing sort processing. (ZW0096ET)

aCPU Time The total CPU time spent performing sort processing. (ZW0096PT)


Sort A

ctivity

260O

ME

GA

MO

N II for D

B2 H


uide, Version 540

OMEGAMON II for DB2 V540 Accounting Sort Activity Page 1Run Date=mm/dd/yyy Grouped by Hour, Pl anName Run Time=08:50:33 Start Date=mm/dd/yyy, Hour=12Sysid=SYSG, Planname=DBD22AR, Threads=3, Commits=3, Aborts=0------------------------------------------------------------------------------------------------------------------------------------Sort Count = 3 Recs Sorted = 0 Workfiles = 0 WF Inserts = 0 WF Retrievals = 0Elapsed Time = 3.882 CPU Time = 0.008 Start Date=mm/dd/yyy, Hour=12Sysid=SYSG, Planname=DBD22AX, Threads=1, Commits=0, Aborts=1------------------------------------------------------------------------------------------------------------------------------------Sort Count = 2 Recs Sorted = 380 Workfiles = 2 WF Inserts = 380 WF Retrievals = 0Elapsed Time = 10.601 CPU Time = 0.459 Start Date=mm/dd/yyy, Hour=12Sysid=SYSG, Planname=TSTPLAN, Threads=52, Commits=53, Aborts=0------------------------------------------------------------------------------------------------------------------------------------Sort Count = 8 Recs Sorted = 34 Workfiles = 2 WF Inserts = 34 WF Retrievals = 0Elapsed Time = 53.681 CPU Time = 0.076 Start Date=mm/dd/yyy, Hour=13Sysid=SYSG, Planname=H2777PLN, Threads=2, Commits=1, Aborts=1------------------------------------------------------------------------------------------------------------------------------------Sort Count = 4 Recs Sorted = 72 Workfiles = 1 WF Inserts = 0 WF Retrievals = 0Elapsed Time = 1.445 CPU Time = 0.014 Start Date=mm/dd/yyy, Hour=13Sysid=SYSG, Planname=H2888PLN, Threads=1, Commits=1, Aborts=0------------------------------------------------------------------------------------------------------------------------------------Sort Count = 4 Recs Sorted = 72 Workfiles = 1 WF Inserts = 0 WF Retrievals = 0Elapsed Time = 3.090 CPU Time = 0.014 Start Date=mm/dd/yyy, Hour=13Sysid=SYSG, Planname=KTEDB2CA, Threads=1, Commits=5, Aborts=0------------------------------------------------------------------------------------------------------------------------------------Sort Count = 16 Recs Sorted = 173 Workfiles = 1 WF Inserts = 0 WF Retrievals = 0Elapsed Time = 5.055 CPU Time = 0.165

FIGURE 35. Accounting Sort Activity


SQL Activity

SQL Activity

IntroductionThis report displays counts of each type of SQL statement used by a specific application for an individual thread. In addition, this report shows when an application is performing dynamic SQL calls, incremental binds, and other high-overhead Data Control Language (DCL) and Data Definition Language (DDL) SQL statements, as well as RID Pool activity and I/O Parallelism activity.

This report is used to monitor the type of SQL statements that are used most frequently. The report information can reveal potential problems such as excessive incremental binds and dynamic SQL calls.

Default DDnameO2RASQL

Default TitleAccounting SQL Activity

Data SourceIFCID 3




Data Elements




SQL Activity



Authid The primary authorization identifier. Actual values depend on the specific DB2 installation and the type of connection. (QWHCAID)


Threads Number of threads in the group.




DML Statements:

Select The number of SQL SELECT statements executed. (QXSELECT)

Insert The number of SQL INSERT statements executed. (QXINSRT)

Update The number of SQL UPDATE statements executed. (QXUPDTE)

Delete The number of SQL DELETE statements executed. (QXDELET)

Open Cursor The number of SQL OPEN CURSOR statements executed. (QXOPEN)

Fetch The number of SQL FETCH statements executed. (QXFETCH)

Close Cursor The number of SQL CLOSE CURSOR statements executed. (QXCLOSE)

Prepare The number of SQL PREPARE statements executed. (QXPREP)

Describe The number of SQL DESCRIBE statements executed. (QXDESC)

Describe Table Number of DESCRIBE TABLE statements. (QXDSCRTB)

DDL Statements:

Create Table The number of SQL CREATE TABLE statements executed. (QXCRTAB)

Create View The number of SQL CREATE VIEW statements executed. (QXDEFVU)

Create Alias The number of SQL CREATE ALIAS statements executed. (QXCRALS)

Create Synonym The number of SQL CREATE SYNONYM statements executed. (QXCRSYN)

Create Tablespace

The number of SQL CREATE TABLESPACE statements executed. (QXCTABS)

Create Index The number of SQL CREATE INDEX statements executed. (QXCRINX)

Create Database The number of SQL CREATE DATABASE statements executed. (QXCRDAB)

Create StoGroup The number of SQL CREATE STOGROUP statements executed. (QXCRSTG)


SQL Activity

Drop Table The number of SQL DROP TABLE statements executed. (QXDRPTA)

Drop View The number of SQL DROP VIEW statements executed. (QXDRPVU)

Drop Alias The number of SQL DROP ALIAS statements executed. (QXDRPAL)

Drop Synonym The number of SQL DROP SYNONYM statements executed. (QXDRPSY)

Drop Tablespace The number of SQL DROP TABLESPACE statements executed. (QXDRPTS)

Drop Index The number of SQL DROP INDEX statements executed. (QXDRPIX)

Drop Database The number of SQL DROP DATABASE statements executed. (QXDRPDB)

Drop StoGroup The number of SQL DROP STOGROUP statements executed. (QXDRPST)

Drop Package Number of DROP PACKAGE statements. (QXDRPPKG)

Alter Table The number of SQL ALTER TABLE statements executed. (QXALTTA)

Alter Tablespace The number of SQL ALTER TABLESPACE statements executed. (QXALTTS)

Alter Index The number of SQL ALTER INDEX statements executed. (QXALTIX)

Alter Database Number of ALTER DATABASE statements. (QXALDAB)

Alter StoGroup The number of SQL ALTER STOGROUP statements executed. (QXALTST)

DCL Statements:

Grant The number of SQL GRANT statements executed. (QXGRANT)

Release The number of RELEASE statements executed by the thread. (QXREL)

Revoke The number of SQL REVOKE statements executed. (QXREVOK)

Lock Table The number of SQL LOCK TABLE statements executed. (QXLOCK)

Connect 1 The number of CONNECT type 1 statements executed by the thread. (QXCON1)

Set Host Var Number of SET host-variable statements. (QXSETHV)

Set Cur Rules The number of SET CURRENT RULES statements executed. This tells DB2 whether an SQL statement should be processed in the ‘DB2’ way or the ‘standard’ way. (QXSETCRL)

Connect 2 The number of CONNECT type 2 statements executed by the thread. (QXCON2)

Set Cur SQLid The number of SQL SET SQLID statements executed. (QXSETSQL)

Set Cur Degree The number of SET DEGREE statements executed by the thread. (QXSETCDG)

Set Connection The number of SET CONNECTION statements executed by the thread. (QXSETCON)

Miscellaneous Statements:

Comment On The number of SQL COMMENT ON statements executed. (QXCMTON)

Label On The number of SQL LABEL ON statements executed. (QXLABON)

SQL Activity


Incremental Bind The number of incremental binds processed, excluding prepares. (QXINCRB)

Rid Pool Access:

Successful The number of times a multiple index access path was used. (QXMIAP)

Not Used due to Limit Exceeded

The number of times a multiple index path was not used because the number of RIDs retrieved exceeded the maximum limit. (QXMRMIAP)

Not Used due to No Storage

The number of times a multiple index path was not used because no storage was available for RIDs. (QXNSMIAP)

Query Parallelism:

Max Degree The maximum degree of parallelism processed for the thread. (QXMAXDEG)

Parallel Groups Executed

The total number of parallel groups executed for the thread. (QXTOTGRP)

Sequential Mode - Cursor

Number of parallel groups that fallback to sequential mode because of a cursor that allows update or delete. (QXDEGCUR)

Planned Parallel Degree Executed

The total number of parallel groups that were executed at the planned parallel degree. (QXNORGRP)

Sequential Mode - No Buffer

The total number of parallel groups that went back to sequential processing because of storage shortage or buffer pool contention. (QXDEGBUF)

Reduced Parallel Degree Executed

The total number of parallel groups that were processed at a parallel degree less than planned because of storage shortage or buffer pool contention. (QXREDGRP)

Sequential Mode - No ESA Sort

The total number of parallel groups that went back to sequential processing because there was no ESA sort support available. (QXDEGESA)

Parallelism Disabled By RLF

Query Parallelism was disabled by RLF. Y indicates that query parallelism was disabled by the resource limit facility for at least one dynamic SQL statement. If data is grouped, this field will contain the number of threads in which query parallelism was disabled. Applies only to DB2 Version 4 and above. (QXRLFDPA)

Sequential Mode - No Enclave

The number of parallel groups executed in sequential mode due to unavailable enclave services. Applies only to DB2 Version 4 and above. (QXDEGENC)

Stored Procedure:

SQL Calls The number of time SQL calls were issued to invoke stored procedures. Applies only to DB2 Version 4 and above. (QXCALL)

Stored Procedure Abended

The number of time a stored procedure abended. Applies only to DB2 Version 4 and above. (QXCALLAB)


SQL Activity

SQL Call Statement Time Out

The number of times an SQL call statement timed out waiting to be scheduled. Applies only to DB2 Version 4 and above. (QXCALLTO)

SQL Call Statement Rejected

The number of times an SQL CALL statement was rejected. Applies only to DB2 Version 4 and above. (QXCALLRJ)

SQ

L A

ctivity

266O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 Accounting SQL Activity Page 1Run Date mm/dd/yyy Group by None Run Time 12.43.07 Start Timestamp=1995-03-09-12.11.01.774567; End Timestamp=1995-03-09-12.15.16.207443; Termination=DEALLOCSysid=SP22, DB2ID=D412, Group=TDDB241G, Member=D412, Planname=JACK2020, Connid=DB2CALL, Corrid=TDDB20A, Original Authid=TDDB20ACommits=5, Aborts=1------------------------------------------------------------------------------------------------------------------------------------DML Statements: Select = 3 Insert = 312 Open Cursor = 118 Prepare = 150 Update = 0 Fetch = 97969 Describe = 0 Delete = 0 Close Cursor = 118 Describe Table = 0 DDL Statements: --------------- Create -------- Drop ------ Alter ------------------ Create ---------- Drop --------- Alter Table = 2 0 0 Tablespace = 3 0 0 View = 0 0 0 Index = 5 3 0 Alias = 0 0 n/a Database = 2 1 0 Synonym = 0 0 n/a StoGroup = 0 0 0 Package = n/a 1 n/a DCL Statements: Grant = 10 Revoke = 0 Set Host Var = 0 Set Cur SQLid = 10 Lock Table = 9 Set Cur Rules = 4 Set Cur Degree = 3 Release = 0 Connect 1 = 0 Connect 2 = 0 Set Connection = 0 Miscellaneous: SQL Call = 10 Comment On = 0 Label On = 0 Incremental Bind = 0 RID Pool Access: Successful = 661 Not Used due to Limit Exceeded = 0 Not Used due to No Storage = 0 Query Parallelism: Max Degree = 8 Parallel Groups Executed = 4 Sequential Mode - Cursor = 0 Planned Parallel Degree Executed = 4 Sequential Mode - No Buffer = 0 Reduced Parallel Degree Executed = 0 Sequential Mode - No ESA Sort = 0 Parallelism Disabled By RLF = 0 Sequential Mode - No Enclave = 0 Stored Procedure: SQL Call = 0 Stored Procedure Abended = 0 SQL Call Statement Time Out = 0 SQL Call Statement Rejected = 0

FIGURE 36. Accounting SQL Activity Report (1 of 2)

Historical R


eports267

SQ

L A

ctivity

Omegamon II for DB2 V540 Accounting SQL Activity Page 2Run Date mm/dd/yyy Group by None Run Time 12.43.07 Start Timestamp=1995-03-09-12.11.01.774567; End Timestamp=1995-03-09-12.15.16.207443; Termination=DEALLOCSysid=SYSG, DB2ID=D31A, Planname=JACK2020, Connid=DB2CALL, Corrid=TDDB20A, Original Authid=TDDB20A, Commits=5, Aborts=1------------------------------------------------------------------------------------------------------------------------------------DML Statements: Select = 1 Insert = 3 Open Cursor = 35 Prepare = 52 Update = 3 Fetch = 2176 Describe = 0 Delete = 0 Close Cursor = 34 Describe Table = 0 DDL Statements: --------------- Create -------- Drop ------ Alter ------------------ Create ---------- Drop --------- Alter Table = 3 0 0 Tablespace = 3 0 0 View = 0 0 0 Index = 0 0 0 Alias = 0 0 n/a Database = 5 0 0 Synonym = 0 0 n/a StoGroup = 0 0 0 Package = n/a 0 n/a DCL Statements: Grant = 0 Revoke = 0 Set Host Var = 0 Set Cur SQLid = 0 Lock Table = 0 Set Cur Degree = 0 Release = 0 Connect 1 = 0 Connect 2 = 0 Set Connection = 0 Miscellaneous: Comment On = 0 Label On = 0 Incremental Bind = 0 RID Pool Access: Successful = 0 Not Used due to Limit Exceeded = 0 Not Used due to No Storage = 0 Query Parallelism: Max Degree = 0 Parallel Groups Executed = 0 Sequential Mode - Cursor = 0 Planned Parallel Degree Executed = 0 Sequential Mode - No Buffer = 0 Reduced Parallel Degree Executed = 0 Sequential Mode - No ESA Sort = 0

FIGURE 37. Accounting SQL Activity Report (2 of 2)

Accounting Summary


Accounting Summary

IntroductionThis report displays an overview of thread activity (at either the summary or detail level), providing information such as elapsed time, wait times, getpage requests, and locking activity.

The summary report is used to group threads into applications or categories in order to view performance at a summary level.

This report can be used to track resource utilization and detect potential problem areas that may require further investigation. The report information can reveal problems such as high elapsed time values, and high I/O wait time values by thread.

Note: Refer to the IBM statement in hilev.SDSNMACS (member DSNDQWAC) about the calculation of these values: Total ElapTime, Total CPU Time, and In-DB2 Time.

Default DDnameO2RASUM

Default TitleAccounting Summary

Data SourceIFCIDs 3, 18, 95, and 96





Accounting Summary

Data Elements

Date The beginning date for the period covered by this accounting row. This column is provided to allow for SQL GROUP BY date. (ZWHSDATE)

Hour The beginning hour for the period covered by this accounting row. This column is provided to allow for SQL GROUP BY hour. (ZWHSHOUR)

Sysid The MVS system ID. This column contains blanks if data is extracted from a GTF dataset, or if DB2NAME is not selected as a groupby element. (ZWHMVSID)



Planname The planname of the thread. This column will contain blanks if PLANNAME was not selected as a groupby element. (QWHCPLAN)

Threads The number of individual threads included in this group.

Commits The number of successful commits completed. For attachments that use the two phase commit protocol, this count reflects the number of phase two commits. For attachments that do not use the two phase commit protocol, this count reflects the number of successful sync requests processed. (QWACCOMM)

Aborts The number of successful abort requests. (QWACABRT)


aTotal ElapTime The total elapsed time of all threads. (ZWACTSC)

aTotal CPU Time The total CPU time for all threads.

In-DB2 Time The total In-DB2 time of the threads. This column represents the total amount of time the threads spent executing within DB2. (QWACASC)

In-DB2 CPU Time The amount of CPU time a thread spends executing within DB2. (QWACAJST + QWACASRB)

I/O Wait Time The amount of elapsed time spent waiting for physical I/O completion. The value is expressed in seconds. (QWACAWTI)

Lock Wait Time The amount of elapsed time spent waiting for lock and latch requests to be granted. The value is expressed in seconds. (QWACAWTL)

Total SQL Requests

Summary of all fields that are available on the Accounting SQL Activity report.

GetPage Requests

The number of getpage requests executed. (QBACGET)

Read Requests The number of read I/O operations performed. (QBACRIO)

Accounting Summary


Prefetch Requests

The sum of list prefetch, dynamic prefetch, and sequential prefetch requests.

Lock Requests The number of locks requested. (QTXALOCK)


Historical R


eports271

Accounting S

umm

ary

Omegamon II for DB2 V540 Accounting Summary Page 1Run Date=mm/dd/yyy Grouped by DB2id, Day Run Time=15:29:07 Start Date=mm/dd/yyy; Threads=25, Commits=124, Aborts=1 Sysid=SYSG, DB2id=D23A ------------------------------------------------------------------------------------------------------------------------------------ Total Total In-DB2 In-DB2 I/O wait Lock Wait Total SQL GetPage Read Prefetch Lock ElapTime CPU time Time CPU time Time Time Requests Requests Requests Requests Requests --------------- ------------ -------------- ------------ ----------- ----------- ---------- ---------- --------- --------- --------- 24684.540094 38.688476 880.457773 11.924915 138.111945 2.160644 1260 7483 4485 65 5434 Start Date=mm/dd/yyy; Threads=8, Commits=8, Aborts=0 Sysid=SYSG, DB2id=D23B ------------------------------------------------------------------------------------------------------------------------------------ Total Total In-DB2 In-DB2 I/O wait Lock Wait Total SQL GetPage Read Prefetch Lock ElapTime CPU time Time CPU time Time Time Requests Requests Requests Requests Requests --------------- ------------ -------------- ------------ ----------- ----------- ---------- ---------- --------- --------- --------- 18349.504779 2.166464 307.098353 0.668907 15.295933 1.957370 265 3604 371 136 3071 Start Date=mm/dd/yyy; Threads=69, Commits=97, Aborts=13 Sysid=SYSG, DB2id=D31A ------------------------------------------------------------------------------------------------------------------------------------ Total Total In-DB2 In-DB2 I/O wait Lock Wait Total SQL GetPage Read Prefetch Lock ElapTime CPU time Time CPU time Time Time Requests Requests Requests Requests Requests --------------- ------------ -------------- ------------ ----------- ----------- ---------- ---------- --------- --------- --------- 14979.938069 17.263158 1520.550853 10.555023 104.259574 351.011993 20356 30837 1133 1959 12352

FIGURE 38. Accounting Summary Report

Accounting Termination Summary



IntroductionThis report displays summary information about application termination for a group of threads, including the number of normal terminations, abnormal terminations, and indoubt conditions per application.

This report shows application terminations, both normal and abnormal. The report information can reveal problems such as excessive abnormal terminations and indoubt conditions.

Default DDnameO2RATRM

Default TitleAccounting Termination Summary

Data SourceIFCID 3




Data Elements


DB2id The DB2 subsystem name. The DB2 subsystem name. This column contains blanks if DB2NAME is not selected as a groupby element. (QWHSSSID)






Threads The number of threads that are included in this group when Group By is used.



Dealloc The number of individual threads terminated. (ZWACRI12)

Newuser The number of individual threads terminated by a user signon. (ZWACRI08)

Reads The number of individual threads terminated by IFI Reads. (ZWACRI04)

EOT/Term The number of individual threads terminated because the application terminated normally. (ZWACRI16)

EOT/Abend The number of individual threads terminated because the application terminated abnormally. (ZWACRI20)

EOM/Abend The number of individual threads terminated abnormally due to end of memory. (ZWACRI24)

Res Indoubt The number of individual threads terminated because of resolved indoubt processing. (ZWACRI28)

Force The number of individual threads terminated because of stop force, MVS cancel of DB2, or MVS force of DB2. (ZWACRI32)

IEOT/Term The number of individual threads terminated because the application terminated normally and the unit of work is indoubt. (ZWACRI40)

IEOT/Abend The number of individual threads terminated because the application terminated abnormally and the unit of work is indoubt. (ZWACRI44)

IEOM/Abend The number of individual threads terminated because the application terminated abnormally and the unit of work is indoubt due to end of memory. (ZWACRI48)

IRes Indoub The number of individual threads terminated because of resolved indoubt processing. (ZWACRI52)

IForce The number of individual threads terminated because of stop force, MVS cancel of DB2, or MVS force of DB2 and indoubt. (ZWACRI56)

Resignon The number of individual threads terminated because the same user signed on with the same authid. (ZWACRI06)

Inactive DDF The number of times the reason for termination was because the distributed thread was going inactive. (ZWACRI10)

Accounting Term

ination Sum

mary

274O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 Accounting Termination Summary Page 1Run Date=mm/dd/yyy Grouped by DB2id, PlanName Run Time=10:41:39 Sysid=SYSG, DB2id=D22A, Planname=JACK2020, Threads=1, Commits=1, Aborts=1------------------------------------------------------------------------------------------------------------------------------------Dealloc = 1 Newuser = 0 Reads = 0 EOT/Term = 0 EOT/Abend = 0 EOM/Abend = 0Res Indoubt = 0 Force = 0 IEOT/Term = 0 IEOT/Abend = 0 IEOM/Abend = 0 IRes Indoub = 0IForce = 0 Resignon = 0 Inactive DDF= 0 Sysid=SYSG, DB2id=D23A, Planname=ALECV23X, Threads=2, Commits=2, Aborts=0------------------------------------------------------------------------------------------------------------------------------------Dealloc = 2 Newuser = 0 Reads = 0 EOT/Term = 0 EOT/Abend = 0 EOM/Abend = 0Res Indoubt = 0 Force = 0 IEOT/Term = 0 IEOT/Abend = 0 IEOM/Abend = 0 IRes Indoub = 0IForce = 0 Resignon = 0 Inactive DDF= 0 Sysid=SYSG, DB2id=D23A, Planname=JNLP1PLN, Threads=14, Commits=3, Aborts=4------------------------------------------------------------------------------------------------------------------------------------Dealloc = 4 Newuser = 10 Reads = 0 EOT/Term = 0 EOT/Abend = 0 EOM/Abend = 0Res Indoubt = 0 Force = 0 IEOT/Term = 0 IEOT/Abend = 0 IEOM/Abend = 0 IRes Indoub = 0IForce = 0 Resignon = 0 Inactive DDF= 0

FIGURE 39. Accounting Termination Summary Report


Time Summary

Time Summary

IntroductionThis report displays time-related information about thread activity (at either the summary or detail level), providing information such as elapsed time, MVS CPU time, in-DB2 time, in-DB2 CPU time, and wait times.

The summary report is used to group threads into applications or categories in order to view performance at a summary level.

This report is used to determine if any of these times are excessive, requiring further investigation. The report information can reveal problems such as excessive values for the application TCB and in-DB2 times.

Note: Refer to the IBM statement in hilev.SDSNMACS (member DSNDQWAC) about the calculation of these values: Total Elapsed Time, and In-DB2 Elapsed Time.

Default DDnameO2RATIM

Default TitleAccounting Time Summary

Data SourceIFCID 3


Order By ElementsAUTHID, TIME, DB2ID, CONNID, CORRID, CONTYPE, CORRNAME ORIGAUTHID, PLANNAME, SYSID, LUWID, MEMBER, GROUP


Time Summary


Data Elements

Start Date The beginning date for the period covered by this accounting row. This column is provided to allow for SQL GROUP BY date. (ZWHSDATE)

Hour The beginning hour for the period covered by this accounting row. This column is provided to allow for SQL GROUP BY hour. (ZWHSHOUR)




Threads The number of individual thread records combined in this summarization instance.

Commits The number of successful commits completed. For attachments that use the 2-phase commit protocol, this count reflects the number of phase-2 commits. For attachments that do not use the 2-phase commit protocol, this count reflects the number of successful sync requests processed. (QWACCOMM)

Aborts The number of successful abort requests. (QWACABRT)

Parallel Tasks The number of parallel tasks for this thread. This will not appear on reports when the group by option is specified. Applies only to DB2 Version 4 and above. (QWACPCNT)

aTotal Elapsed Time

The total elapsed time of all the threads. (ZWACTSC)

aIn-DB2 Elapsed Time

The total In-DB2 time of the threads. This column represents the total amount of time the threads spent executing within DB2. (QWACASC)

Total TCB Time The total amount of MVS TCB CPU time spent during the life of the thread. This does not include TCB time consumed in DB2 while processing SQL statements in a stored procedure. (QWACEJST-QWACBJST)

In-DB2 TCB Time The amount of MVS TCB CPU time spent while executing within DB2. (QWACAJST)

bTotal SRB Time The amount of MVS SRB CPU time used during the timeframe covered by the summarization row. The SRB time may or may not be applicable to DB2 access. For additional information, see the DB2 documentation for fields QWACBSRB and QWACESRB. (ZWACTSRB)

bIn-DB2 SRB Time

The amount of MVS SRB CPU time spent while executing within DB2. (QWACATCB)

Total StProc TCB Time

The amount of TCB time spent in the DB2 stored procedure address space processing the stored procedures. Applies only to DB2 Version 4 and above. (QWACSPCP)


Time Summary

In-DB2 StProc TCB Time

The amount of TCB time spent in DB2 processing SQL statements issued by stored procedures. Applies only to DB2 Version 4 and above. (QWACSPTT)

Waits:

Lock Waits Number of waits processed for local lock or latch suspensions. (QWACARN2)

Lock Wait Time The amount of elapsed time spent waiting for local lock and latch requests to be granted. The value is expressed in seconds. (QWACAWTL)

Drain Lock Waits The number of waits for drain lock. (QWACARND/2)

Drain Lock Wait Time

The amount of time spent waiting to acquire drain lock. (QWACAWDR)

Claimer Drain Waits

The number of waits for claims to be released. (QWACARNC/2)

Claimer Drain Wait Time

The amount of time spent waiting for claims to be released for a drain. (QWACAWCL)

Page Latch Waits The number of waits due to page latch contention. (QWACARNH/2)

Page Latch Wait Time

The amount of time spent waiting to acquire page latch. (QWACAWTP)

Service Waits Number of waits for DB2 service execution. (QWACARNS)

Service Wait Time

Accumulated wait time for synchronous execution of a DB2 service task such as open/close of a dataset, DFHSM recall of a dataset, SYSLGRNG update, or definition/extension of a dataset. (QWACAWTE)

Send Message Waits

The number of waits due to sending messages to other members in the data sharing group. Applies only to DB2 Version 4 and above. (QWACARNG)

Send Message Wait Time

The amount of time spent waiting to send messages to other DB2 members in the data sharing group. Applies only to DB2 Version 4 and above. (QWACAWTG)

Global Lock Waits

The number of waits caused by global lock contention. Applies only to DB2 Version 4 and above. (QWACARNJ)

Global Lock Wait Time

The amount of time spent waiting due to global lock contention. Applies only to DB2 Version 4 and above. (QWACAWTJ)

I/O Waits Number of waits processed for synchronous I/O. (QWACARN2)

I/O Wait Time The amount of elapsed time spent waiting for physical I/O completion. The value is expressed in seconds. (QWACAWTI)

Asynch Read Waits

Number of waits for read I/O under another thread (sequential prefetch). (QWACARNR)

Asynch Read Wait Time

Accumulated time spent waiting for read I/O under another thread (deferred writes). (QWACARNW)

Asynch Write Waits

Number of waits for write I/O under another thread (deferred writes). (QWACARNW/2)

Time Summary


Asynch Write Wait Time

Accumulated time spent waiting for waits for write I/O under another thread (deferred writes). (QWACAWTW)

Archive Log Waits

Number of suspensions due to ARCHIVE LOG MODE(QUIESCE) processing. (QWACALCT)

Archive Log Wait Time

Total time suspended due to ARCHIVE LOG MODE(QUIESCE) command. (QWACALOG)

Archive Read Waits

The number of waits for archive log reads from tape. (QWACANAR/2)

Archive Read Wait Time

The amount of time spent waiting for read of archive log from tape. (QWACAWAR)

StProc Schedule Waits

The number of times an SQL CALL statement had to wait for an available TCB before the stored procedure could be scheduled. Applies only to DB2 Version 4 and above. (QWACCANM)

StProc Schedule Wait Time

The amount of time spent waiting for an available TCB before the stored procedure could be scheduled. Applies only to DB2 Version 4 and above. (QWACCAST)


b. The values for SRB time appear for DB2 Version 5 and below.

Historical R


eports279

Time S

umm

ary

Omegamon II for DB2 V540 Accounting Time Summary Page 1Run Date=mm/dd/yyy Grouped by None Run Time=13:37:20 Start Timestamp=1995-03-09-12.11.01.774567; End Timestamp=1995-03-09-12.15.16.207443; Termination=DeallocSysid=SP22, DB2id=D41A, Group=TDDB241G, Member=D412, Planname=JACK2020, Connid=DB2CALL, Corrid=TDDB20A, Original Authid=TDDB20ACommits=5, Aborts=0, Parallel Tasks=3------------------------------------------------------------------------------------------------------------------------------------ Elapsed Time TCB Time SRB Time StProc TCB TimeTotals: 013:49:20.454489 000:05:02.497948 000:00:57.118388 000:00:00.000000In-DB2: 000:40:49.472096 000:04:03.625478 000:00:00.487236 000:00:00.000000 Count Time Count TimeWaits: Lock Waits = 2715 000:00:02.759226 I/O Waits = 1291 000:00:38.977660 Drain Lock Waits = 0 000:00:00.000000 Asynch Read Waits = 647 000:00:49.810899 Claimer Drain Waits = 0 000:00:00.000000 Asynch Write Waits = 15 000:00:04.494237 Page Latch Waits = 642 000:04:38.797046 Archive Log Waits = 0 000:00:00.000000 Service Waits = 152 00:02:02.3552080 Archive Read Waits = 0 000:00:00.000000 Send Message Waits = 10 000:00:00.222876 StProc Schedule Waits = 0 000:00:00.000000 Global Lock Waits = 44 000:01:10.407819 Start Timestamp=1995-03-10-12.16.01.774567; End Timestamp=1995-03-10-12.20.16.207443; Termination=DeallocSysid=SYSG, DB2id=D31A, Planname=JACK2020, Connid=DB2CALL, Corrid=TDDB20A, Original Authid=TDDB20ACommits=5, Aborts=0------------------------------------------------------------------------------------------------------------------------------------ Elapsed Time TCB Time SRB TimeTotals: 001:06:58.792029 000:00:19.025568 000:00:00.671153In-DB2: 000:07:03.135580 000:00:14.209746 000:00:00.047706 Count Time Count TimeWaits: Lock Waits = 202 000:01:01.425025 I/O Waits = 162 000:00:03.397124 Drain Lock Waits = 0 000:00:00.000000 Asynch Read Waits = 9 000:00:00.501575 Claimer Drain Waits = 0 000:00:00.000000 Asynch Write Waits = 9 000:00:00.537592 Page Latch Waits = 0 000:00:00.000000 Archive Log Waits = 0 000:00:00.000000 Service Waits = 10 000:00:00.222876 Archive Read Waits = 0 000:00:00.000000

FIGURE 40. Accounting Time Summary Report







Note: Refer to the IBM statement in hilev.SDSNMACS (member DSNDQWAC) about the calculation of this value: In-DB2 CPU Time.

Default DDnameO2RAPKG





Select ElementsAUTHID, DB2ID, CONNID, CORRID, CONTYPE, CORRNAME, ORIGAUTHID, PLANNAME, PROGRAM, SYSID, LUWID, MEMBER, GROUP

Data Elements








Planname The planname of the thread. This column contains blanks if PLANNAME is not selected as a groupby element. (QWHCPLAN)

Threads The number threads that are included in this group when Group By is used.




Program The program name. (QPACPKID)

Collection The package collection ID. This field will be displayed only if a package is being used. (QPACCOCN)

Token The consistency token. This field will be displayed if only a package is being used. (QPACCONT)

Location The name of the location where the package was executed. This field will be displayed only for remote packages. All times for this package represent the time spent locally to execute the remote package. (QPACLOCN)

General:

SQL Requests The number of SQL statements issued by this program. (QPACSQLC)

Loaded by Stored Procedure

This package was loaded by a stored procedure. Applies only to DB2 Version 4 and above. (QPACINSP)

aIn-DB2 CPU Time

The amount of CPU time spent processing this program. (QPACTJST)

Entry/Exit Events

The number of entry or exit events processed while executing this program. (QPACARNA)

DBRM_PACKAGE The type of package:

D DBRM

P Package

S Stored Procedure

Waits:

Lock Waits The number of waits for locks or latches while executing this program. (QPACARNL/2)

Lock Wait Time The amount of time spent waiting for locks or latches while executing this program. (QPACAWTL)



Drain Lock Waits The number of waits for drain locks while executing this program. (QPACARND/2)

Drain Lock Wait Time

The amount of time spent waiting for drain locks while executing this program. (QPACAWFDR)

Claimer Drain Waits

The number of waits for claims to be released while executing this program. (QPACARNC/2)

Claimer Drain Wait Time

The amount of time spent waiting for claims to be released for a drain while executing this program. (QPACAWCL)

Page Latch Waits The number of waits for page latches while executing this program. (QPACARNH/2)

Page Latch Wait Time

The amount of time spent waiting for page latches while executing this program. (QPACAWTP)

Service Waits The number of waits for DB2 services while executing this program. (QPACARNS/2)

Service Wait Time

The amount of time spent waiting for DB2 services while executing this program. (QPACAWTE)

DB2 service waits are as follows:� dataspace manager services� define/delete/extend dataset� DFHSM recall� open/close dataset� SYSLGRNG update

Send Message Waits

The number of waits processed for messages within the DB2 data sharing group. Applies only to DB2 Version 4 and above. (QPACARNG)

Send Message Wait Time

The amount of time spent waiting for sending messages within the DB2 data sharing group. Applies only to DB2 Version 4 and above. (QPACAWTG)

Global Lock Waits

The number of times a wait for resolution of global lock contention occurred. Applies only to DB2 Version 4 and above. (QPACARNJ)

Global Lock Wait Time

The amount of time spent waiting for global lock contention. Applies only to DB2 Version 4 and above. (QPACAWTJ)

I/O Waits The number of waits for I/O done under this thread. (QPACARNE/2)

I/O Wait Time The amount of time spent waiting for read or write I/O done under this thread to complete while executing this program. (QPACAWTI)

Asynch Read Waits

The number of waits for read I/O done under another thread (prefetch). (QPACARNR/2)

Asynch Read Wait Time

The amount of time spent waiting for read I/O done under another thread while executing this program. (QPACAWTR)

Asynch Write Waits

The number of waits for write I/O done under another thread (deferred writes). (QPACARNW/2)

Asynch Write Wait Time

The amount of time spent waiting for write I/O done under another thread while executing this program. (QPACAWTW)



Archive Log Waits

The number of suspensions due to processing of ARCHIVE LOG MODE(QUIESCE) commands while executing this program. (QPACALCT)

Archive Log Wait Time

The amount of time spent waiting due to processing of ARCHIVE LOG MODE(QUIESCE) commands while executing this program. (QPACALOG)

Archive Read Waits

The number of waits for archive log reads from tape while executing this program. (QPACANAR/2)

Archive Read Wait Time

The amount of time spent waiting to read the archive log from tape while executing this program. (QPACAWAR)

StProc Schedule Waits

The number of times where an SQL CALL statement had to wait for an available TCB before the stored procedure could be scheduled. Applies only to DB2 Version 4 and above. (QPACCANM)

StProc Schedule Wait Time

The amount of time spent waiting for an available TCB for a stored procedure to be scheduled. Applies only to DB2 Version 4 and above. (QPACCAST)


Accounting Package D

etail

284O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 Accounting Package Detail Page 1Run Date=mm/dd/yyy Grouped by DB2id, Authid, PlanName Run Time=10:39:11 Sysid=SYSG, DB2id=D41A, Authid=TDDB20A, Planname=JACK2020, Threads=1, Commits=1, Aborts=1-----------------------------------------------------------------------------------------------------------------------------------Program = GRETBN4 Type = PACKAGE Collection = GREGROUP Token = 0000000000000000 Location = D23B General: In-DB2 Time = 00:00:01.425001 SQL Requests = 236700 Loaded by Stored Procedure In-DB2 CPU Time = 00:00:00.123456 Entry/Exit Events = 1 Count Time Count TimeWaits: Lock Waits = 2 00:00:01.425025 I/O Waits = 1 00:00:00.001202 Drain Lock Waits = 0 00:00:00.000000 Asynch Read Waits = 0 00:00:00.000000 Claimer Drain Waits = 0 00:00:00.000000 Asynch Write Waits = 0 00:00:00.000000 Page Latch Waits = 0 00:00:00.000000 Archive Log Waits = 0 00:00:00.000000 Service Waits = 26 00:00:00.220022 Archive Read Waits = 0 00:00:00.000000 Send Message Waits = 0 00:00:00.000000 StProc Schedule Waits = 0 00:00:00.000000 Global Lock Waits = 0 00:00:00.000000 Program = GRETBN51 Type = PACKAGE Collection = GREGROUP Token = 0000000000000000 Location = D23B General: In-DB2 Time = 00:00:01.425001 SQL Requests = 236700 In-DB2 CPU Time = 00:00:00.123456 Entry/Exit Events = 1 Count Time Count TimeWaits: Lock Waits = 2 00:00:01.425025 I/O Waits = 1 00:00:00.001202 Drain Lock Waits = 0 00:00:00.000000 Asynch Read Waits = 0 00:00:00.000000 Claimer Drain Waits = 0 00:00:00.000000 Asynch Write Waits = 0 00:00:00.000000 Page Latch Waits = 0 00:00:00.000000 Archive Log Waits = 0 00:00:00.000000 Service Waits = 26 00:00:00.220022 Archive Read Waits = 0 00:00:00.000000 Send Message Waits = 0 00:00:00.000000 StProc Schedule Waits = 0 00:00:00.000000 Global Lock Waits = 0 00:00:00.000000

FIGURE 41. Accounting Package Detail Report (1 of 2)

Historical R


eports285

Accounting Package D

etail

Sysid=SYSG, DB2id=D31A, Authid=TDDB20A, Planname=JACK2020, Threads=1, Commits=1, Aborts=1-----------------------------------------------------------------------------------------------------------------------------------Program = GRETBN31 Type = PACKAGE Collection = GREGROUP Token = 0000000000000000 Location = D23B General: In-DB2 Time = 00:00:01.425001 SQL Requests = 236700 In-DB2 CPU Time = 00:00:00.123456 Entry/Exit Events = 1 Count Time Count TimeWaits: Lock Waits = 2 00:00:01.425025 I/O Waits = 1 00:00:00.001202 Drain Lock Waits = 0 00:00:00.000000 Asynch Read Waits = 0 00:00:00.000000 Claimer Drain Waits = 0 00:00:00.000000 Asynch Write Waits = 0 00:00:00.000000 Page Latch Waits = 0 00:00:00.000000 Archive Log Waits = 0 00:00:00.000000 Service Waits = 26 00:00:00.220022 Archive Read Waits = 0 00:00:00.000000

FIGURE 42. Accounting Package Detail Report (2 of 2)

Historical Reporter Statistics Reports 287

Historical ReporterStatistics Reports

IntroductionStatistics reports contain information from the DB2 statistics trace. The statistics trace provides data on the following:


� pool usage


� logging and locking statistics

� other subsystem-wide information

This information provides a starting point for tuning the DB2 subsystem.

Chapter ContentsBuffer Pool Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288Group Buffer Pool Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296Command Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301CPU Time Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305Statistics Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308EDM Pool Activity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316Lock Activity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319Global Lock Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322Log Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326SQL Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330Subsystem Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336Statistics Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339Bind Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342Distributed Data Facility (DDF) Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346Open/Close Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350

13




IntroductionThis report displays the buffer manager statistics for a variable number of buffer pools, up to 60 per DB2 subsystem. Use this report to view overall buffer pool activity for a DB2 subsystem.

A buffer pool is storage reserved to satisfy the buffering requirements for tablespaces or indexes.

Default DDnameO2RSBPA

Default TitleStatistics Buffer Pool Activity


Group By ElementsDB2ID, HOUR, DAY, SYSID, MEMBER, GROUP

Order By ElementsDB2ID, TIME, SYSID, MEMBER, GROUP

Select ElementsDB2ID, BPID, SYSID, MEMBER, GROUP

Data Elements





Date The date from the timestamp of the statistics end record used in constructing the row. (QWHSSTCK)



Time The time from the timestamp of the statistics end record used in constructing the row. (QWHSSTCK)

Buffer Pool The ID of the buffer pool to which this data refers. (QBSTPID)

Possible values for this field are as follows:� 0 – 49: BP0 – BP49� 80 – 89: BP32K – BP32K9� If you are running DB2 Version 6.1, additional possible values for this

field are:� 100 – 109: BP8K0 – BP8K9� 120 – 129: BP16K0 – BP16K9

BP Parameters:

VP Size Size of the virtual buffer pool. (QDBPVPSZ)

VP Sequential Thresh

Sequential steal threshold for the virtual buffer pool VPSEQT. (QDBPVPSH)

Defer Write Thresh

Deferred write threshold for the virtual buffer pool DWQT. (QDBPDWQT)

HP Size Size of the hiperpool. (QDBPHPSZ)

HP Sequential Thresh

Sequential steal threshold for the hiperpool HPSEQT. (QDBPHPSH)

Vert Defer Write Thresh

Vertical deferred write threshold for the virtual buffer pool VDWQT. (QDBPVDQT)

Castout Attribute The castout attribute of the hiperspaces used to back the hiperpool. (QDBPCAST)

VP Parallel Seq Thresh

Parallel I/O sequential threshold VPPSEQT. (QDBPPSQT)

General:

VP Buffer Allocated

The number of virtual buffer pool pages that were allocated at the end of the interval. (QBSTVPL)

Active Buffer The number of virtual buffer pool pages that were in use (nonstealable) at the end of the interval. (QBSTCBA)

VP Expand/Contract

Number of successful virtual buffer pool expansions or contractions because of the ALTER BUFFERPOOL command. (QBSTVPA)

HP Buffer Allocated

The number of hiperpool pages that were allocated at the end of the interval. (QBSTHPL)

HP Buffer Backed

The number of hiperpool pages that were backed by expanded storage at the end of the interval. (QBSTHBE)

HP Expand/Contract

Number of successful hiperpool expansions or contractions because of the ALTER BUFFERPOOL command. (QBSTHPA)

Recall Migrated Dataset

Attempts to access datasets that were migrated. (QBSTMIG)

Dataset Open Number of datasets opened successfully. (QBSTDSO)



VP/HP Expand Fail

Number of virtual buffer pool or hiperpool expansion failures. (QBSTXFV)

Recall Timeout Unsuccessful recall attempts because the timeout limit (DSNZPARM RECALL) was exceeded. (QBSTRTO)

Read Operations:

Getpage Request Total number of getpage requests issued. (QBSTGET)

Getpage Reqs - Seq

Number of getpage requests issued by sequential access requestors. (QBSTSGT)

Getpage Reqs - Random

Number of getpage requests issued by random access requestors. (QBSTGET-QBSTSGT)

GetP Fail - VP Full

Number of getpage failures due to unavailable buffers because the virtual buffer pool was full. Applies only to DB2 Version 4 and above. (QBSTXFL)

GetP Fail - Cond Req

Number of conditional getpage requests that could not be satisfied for this buffer pool. A conditional getpage is used with parallel processing only. (QBSTNGT)

GetP/Sync Read I/O

Ratio of getpage requests to synchronous read I/O operations. (QBSTGET/QBSTRIO)

Sync Read I/Os Total number of synchronous read I/O operations performed. (QBSTRIO)

Sync Read I/O - Seq

Number of synchronous read I/O operations performed by sequential requests. (QBSTSIO)

Sync Read I/O - Random

Number of synchronous read I/O operations performed by random requests. (QBSTRIO-QBSTSIO)

Seq Prefetch Request

Sequential prefetch requests for the buffer pool. (QBSTSEQ)

List Prefetch Req List prefetch requests for the buffer pool. (QBSTLPF)

Dynamic Prefetch Request

Dynamic prefetch requests for the buffer pool. (QBSTDPF)

Seq Prefetch Page

Number of pages read because of sequential prefetch. (QBSTSPP)

List Prefetch Page

Number of pages read because of list prefetch. (QBSTLPP)

Dynamic Prefetch Page

Number of pages read because of dynamic prefetch. (QBSTDPP)

Seq Prefetch I/O Number of asynchronous read I/Os caused by sequential prefetch. (QBSTPIO)

List Prefetch I/O Number of asynchronous read I/Os caused by list prefetch. (QBSTLIO)

Dynamic Prefetch I/O

Number of asynchronous read I/Os caused by dynamic prefetch. (QBSTDIO)

Pgs Read/Seq Pfetch I/O

Pages read per sequential prefetch I/O operation. (QBSTSPP/QBSTPIO)



Pgs Read/Lst Prefetch I/O

Pages read per list prefetch I/O operation. (QBSTLPP/QBSTLIO)

Pgs Rd/Dyn Prefetch I/O

Pages read per dynamic prefetch I/O operation. (QBSTDPP/QBSTDIO)

Pfetch Fail - No Buff

Number of times sequential prefetch was disabled because the sequential prefetch threshold was reached. (QBSTSPD)

Pfetch Fail - No Engine

Number of times sequential prefetch was disabled because a read engine was unavailable. (QBSTREE)

Page-in Due to Read

Number of page-ins required for read I/O. (QBSTRPI)

BP Hit % - Random

The percentage of random getpages that were satisfied by a page already in the bufferpool. If this value is low, it indicates that page residency in the bufferpool is too low, therefore the bufferpool may be too small.

(QBSTGET - QBSTSGT) - QBSTRIO/(QBSTGET - QBSTSGT)

BP Hit % - Sequential

The percentage of sequential getpages that were satisfied by a page already in the bufferpool. (QBSTSGT - (QBSTSPP + QBSTLPP + QBSTDPP)/(QBSTSGT)

HP Hit % The percentage of all reads to the hiperpool for which the requested data was returned. If this value is low, it indicates that many unsuccessful reads to the hiperpool occurred when the page requested was found in the hiperpool, but the backing expanded storage was stolen by the system.

((QBSTHRE + QBSTARA + QBSTHRA) /

(QBSTHRE + QBSTARA + QBSTHRA + QBSTARF + QBSTHRF))

HP Pg Read Sync

Number of pages moved from the hiperpool to the virtual buffer pool under the control of a synchronous task. (QBSTHRE)

HP Pg Rd Async-No ADM

Number of pages moved from the hiperpool to the virtual buffer pool under the control of an asynchronous task such as prefetch. This count does not include pages moved by the Asynchronous Data Mover Facility. (QBSTHRA)

HP Pg Rd Async - ADM

Number of pages moved from the hiperpool to the virtual buffer pool by the Asynchronous Data Mover Facility for an asynchronous task such as prefetch. (QBSTARA)

HP Read Fail - No ADM

Number of unsuccessful reads from the hiperpool, synchronous and asynchronous. This happens when a page was found in the hiperpool, but backing expanded storage was stolen. (QBSTHRF)

HP Read Fail - ADM

Number of reads from the hiperpool that failed using the Asynchronous Data Mover Facility, because the backing expanded storage was stolen or some other error occurred. (QBSTARF)

Write Operations:

Page Updated Number of times a page in the buffer pool was updated. (QBSTSWS)

Page Written Number of pages written to DASD. (QBSTPWS)



Update/Page Written

Ratio page updates to page writes. (QBSTSWS/QBSTPWS)

Write I/O Operation

Number of asynchronous I/Os performed. (QBSTWIO)

Immed (Sync) Write

Number of immediate writes to DASD. (QBSTIMW)

Pages/Write I/O Ratio of pages written to physical writes. (QBSTPWS/(QBSTWIO+QBSTIMW))

VDWTH Reached Number of times the vertical deferred write threshold was reached. (QBSTDWV)

DWTH Reached Number of times the deferred write threshold was reached. (QBSTDWT)

DMTH Reached Number of times the data manager threshold was reached. (QBSTDMC)

Write Engine Not Avail

Number of times that a write engine was not available for I/O. (QBSTWEE)

Page-in Due to Write

Number of page-ins required for write I/O operations. (QBSTWPI)

HP Pg Written Sync

Number of pages moved synchronously from the virtual buffer pool to the hiperpool. Pages accessed by parallel I/O queries are not cached in the hiperpool. (QBSTHWR)

HP Pg Wrt Async-No ADM

Number of pages moved from the virtual buffer pool to the hiperpool under the control of an asynchronous task such as prefetch. This count does not include pages moved by the Asynchronous Data Mover Facility. (QBSTHWA)

HP Pg Wrt Async - ADM

Number of pages moved from the virtual buffer pool to the hiperpool by the Asynchronous Data Mover Facility for an asynchronous task such as prefetch. (QBSTAWA)

HP Write Fail - No ADM

Number of unsuccessful writes to the hiperpool, synchronous and asynchronous, because of a shortage of expanded storage. This count does not include pages moved by the Asynchronous Data Mover Facility. (QBSTHWF)

HP Write Fail - ADM

Number of writes to the hiperpool that failed using the Asynchronous Data Mover Facility, because the backing expanded storage was stolen or some other error occurred. (QBSTAWF)

Query Parallelism:

Parallel Group Request

Number of requests made for processing queries in parallel. (QBSTPQO)

Parallelism Downgraded

Number of times the requested number of buffers to allow a parallel group to run to the planned degree could not be allocated because of a buffer pool shortage. (QBSTPQF)

Prefetch IO Strm Reduce

Number of requested prefetch I/O streams that were denied because of a buffer pool shortage. This applies only for nonworkfile pagesets for queries that are processed in parallel. (QBSTJIS)



Max Prefetch I/O The highest number of concurrent prefetch I/O streams that were allocated to support parallelism. (QBSTXIS)

Prefetch Reduced to 1/2

Number of times the sequential prefetch quantity was reduced from normal to one-half of normal. This is done to continue to allow queries processing in parallel. (QBSTPL1)

Prefetch Reduced to 1/4

Number of times the sequential prefetch quantity was reduced from one-half to one-quarter of normal. (QBSTPL2)

Sort/Merge:

Sort Merge Pass Request

Number of merge passes requested to determine the number of workfiles to support each merge pass. (QBSTWFR)

Workfile Request Number of workfiles requested for all merge passes. (QBSTWFT)

Workfile Req Denied

Number of workfiles rejected because of insufficient buffers. (QBSTWFD)

Merge Pass - Low Buffer

Number of times that sort/merge could not be efficiently performed because of a buffer shortage. (QBSTWFF)

WF Prefetch Disabled

Number of times workfile prefetch was not scheduled because the prefetch quantity was zero. (QBSTWKPD)

WF Create Fail - No Buff

Number of times a workfile was not created due to insufficient buffers. (QBSTMAX)

Workfile Maximum

Maximum number of workfiles in use concurrently. (QBSTWFM)

Destruct Read Req

Pages requested for destructive read processing. (QBSTWDRP)

Destruct Rd Page Dequeue

Pages dequeued from deferred write for destructive read requests. (QBSTWBVQ)

Buffer Pool A

ctivity

294O

ME

GA

MO

N II for D

B2 H


uide, Version 540

FIG

UR

E 43.

Statistics B

uffer P

oo

l Activity R

epo

rt (1 of 2)

Omegamon II for DB2 V540 Statistics Buffer Pool Activity Page 1Run Date=mm/dd/yyyy Grouped by None Run Time=15:35:39 Sysid=SP22, DB2id=D41A, Date=mm/dd/yyyy, Time=06:16------------------------------------------------------------------------------------------------------------------------------------Buffer Pool = BP0--------------------------BP Parameters: VP Size = 2000 VP Sequential Thresh = 80% Defer Write Thresh = 50% HP Size = 0 HP Sequential Thresh = 80% Vert Defer Write Thresh = 10% Castout Attribute = YES VP Parallel Seq Thresh = 50%General: VP Buffer Allocated = 2000 Active Buffer = 23 VP Expand/Contract = 0 HP Buffer Allocated = 0 HP Buffer Backed = 0 HP Expand/Contract = 0 Recall Migrated Dataset = 0 Dataset Open = 1 VP/HP Expand Failed = 0 Recall Timeout = 0Read Operations: Getpage Request = 195 Getpage Request - Seq = 101 Getpage Request - Random= 94 Getpage Fail - VP Full = 0 Getpage Fail - Cond Req = 0 Getpages/Sync Read I/O = 9.75 Sync Read I/O = 20 Sync Read I/O - Seq = 1 Sync Read I/O - Random = 19 Seq Prefetch Request = 5 List Prefetch Request = 0 Dynamic Prefetch Request= 2 Seq Prefetch Page = 157 List Prefetch Page = 0 Dynamic Prefetch Page = 49 Seq Prefetch I/O = 5 List Prefetch I/O = 0 Dynamic Prefetch I/O = 2 Pgs Rd/Seq Prefetch I/O = 31.40 Pgs Rd/Lst Prefetch I/O = 0.00 Pgs Rd/Dyn Prefetch I/O = 24.50 PFetch Fail - No Buffer = 0 PFetch Fail - No Engine = 0 Page-in Due to Read = 0 BP Hit % - Random = 0% BP Hit % - Sequential = 0% HP Hit % = 0% HP Page Read Sync = 0 HP Pg Rd Async - No ADM = 0 HP Pg Rd Async - ADM = 0 HP Read Fail - No ADM = 0 HP Read Fail - ADM = 0Write Operations: Page Updated = 44 Page Written = 12 Updates/Page Written = 3.67 Write I/O Operation = 4 Immed (Sync) Write = 4 Pages/Write I/O = 1.50 VDWTH Reached = 0 DWTH Reached = 0 DMTH Reached = 0 Write Engine Not Avail = 0 Page-in Due to Write = 0 HP Page Written Sync = 0 HP Pg Wrt Async - No ADM= 0 HP Pg Wrt Async - ADM = 0 HP Write Fail - No ADM = 0 HP Write Fail - ADM = 0Query Parallelism: Parallel Group Request = 0 Parallelism Downgraded = 0 Prefetch I/O Strm Reduce= 0 Max Prefetch I/O = 0 Prefetch Reduced to 1/2 = 0 Prefetch Reduced to 1/4 = 0Sort/Merge: Sort Merge Pass Request = 0 Workfile Request = 0 Workfile Req Denied = 0 Merge Pass - Low Buffer = 0 WF Prefetch Disabled = 0 WF Create Fail-No Buff = 0 Workfile Maximum = 0 Destructive Read Req = 0 Destruct Rd Pg Dequeue = 0

Historical R

eporter Statistics R

eports295

Buffer Pool A

ctivity

Buffer Pool = BP14--------------------------BP Parameters: VP Size = 2000 VP Sequential Thresh = 80% Defer Write Thresh = 50% HP Size = 0 HP Sequential Thresh = 80% Vert Defer Write Thresh = 10% Castout Attribute = YES VP Parallel Seq Thresh = 50%General: VP Buffer Allocated = 2000 Active Buffer = 23 VP Expand/Contract = 0 HP Buffer Allocated = 0 HP Buffer Backed = 0 HP Expand/Contract = 0 Recall Migrated Dataset = 0 Dataset Open = 1 VP/HP Expand Failed = 0 Recall Timeout = 0Read Operations: Getpage Request = 195 Getpage Request - Seq = 101 Getpage Request - Random= 94 Getpage Fail - VP Full = 0 Getpage Fail - Cond Req = 0 Getpages/Sync Read I/O = 9.75 Sync Read I/O = 20 Sync Read I/O - Seq = 1 Sync Read I/O - Random = 19 Seq Prefetch Request = 5 List Prefetch Request = 0 Dynamic Prefetch Request= 2 Seq Prefetch Page = 157 List Prefetch Page = 0 Dynamic Prefetch Page = 49 Seq Prefetch I/O = 5 List Prefetch I/O = 0 Dynamic Prefetch I/O = 2 Pgs Rd/Seq Prefetch I/O = 31.40 Pgs Rd/Lst Prefetch I/O = 0.00 Pgs Rd/Dyn Prefetch I/O = 24.50 PFetch Fail - No Buffer = 0 PFetch Fail - No Engine = 0 Page-in Due to Read = 0 BP Hit % - Random = 0% BP Hit % - Sequential = 0% HP Hit % = 0% HP Page Read Sync = 0 HP Pg Rd Async - No ADM = 0 HP Pg Rd Async - ADM = 0 HP Read Fail - No ADM = 0 HP Read Fail - ADM = 0Write Operations: Page Updated = 44 Page Written = 12 Updates/Page Written = 3.67 Write I/O Operation = 4 Immed (Sync) Write = 4 Pages/Write I/O = 1.50 VDWTH Reached = 0 DWTH Reached = 0 DMTH Reached = 0 Write Engine Not Avail = 0 Page-in Due to Write = 0 HP Page Written Sync = 0 HP Pg Wrt Async - No ADM= 0 HP Pg Wrt Async - ADM = 0 HP Write Fail - No ADM = 0 HP Write Fail - ADM = 0Query Parallelism: Parallel Group Request = 0 Parallelism Downgraded = 0 Prefetch I/O Strm Reduce= 0 Max Prefetch I/O = 0 Prefetch Reduced to 1/2 = 0 Prefetch Reduced to 1/4 = 0Sort/Merge: Sort Merge Pass Request = 0 Workfile Request = 0 Workfile Req Denied = 0 Merge Pass - Low Buffer = 0 WF Prefetch Disabled = 0 WF Create Fail-No Buff = 0 Workfile Maximum = 0 Destructive Read Req = 0 Destruct Rd Pg Dequeue = 0

FIGURE 44. Statistics Buffer Pool Activity Report (2 of 2)




IntroductionThis report displays group buffer pool statistics. This report applies only to those DB2s within a DB2 data sharing group. Possible uses for this report are as follows:


� determining if the directory to data ratio is set properly

� determining if the castout thresholds are set properly


Default DDnameO2RSGBP

Default TitleStatistics Group Buffer Pool Activity




Select ElementsDB2ID, SYSID, MEMBER, GROUP

Data Elements


Sysid The MVS system ID. This field is blank if data is extracted from a GTF dataset.(ZWHMVSID)

Date The date on which DB2 generated the statistics data. (ZWHSDATE)

Time The time at which DB2 generated the statistics data. (ZWHSHOUR)

Group The name of DB2 data sharing group. (QWHADSGN)



Member The name of the DB2 member within a DB2 data sharing group. (QWHAMEMN)

Group Buffer Pool

Group buffer pool identifier. (QBGBGN)

Current Directory To Data Ratio

The current ratio of directory entries to data pages. (QBGBGR1)

Pending Directory To Data Ratio

The pending ratio of directory entries to data pages. This value is different from the current ratio if an ALTER GROUPBUFFERPOOL command has been issued with a new value of the RATIO parameter. The change will not take effect until next time the group bufferpool is allocated. (QBGBGR2)

Number of Directory Entries

Actual number of allocated directory entries. (QBGBGDR)

Number of Data Pages

Actual number of allocated data pages. (QBGBGDT)

Allocated Size of Group Buffer Pool

Allocated size of the group buffer pool in KB. (QBGBGSZ * 4)

Checkpoint Interval

Group buffer pool checkpoint interval in hours & minutes. (QBGBGCK)

Castout Threshold

Group buffer pool castout level threshold. (QBGBGGT)

Castout Threshold Reached

Number of times castout was initiated due to the group buffer pool castout threshold being detected. (QBGLGT)

Castout Class Threshold

Castout class level threshold. (QBGBGCT)

Castout Class Threshold Reached

Number of times castout was initiated due to the castout class threshold being detected. (QBGLCT)

Reads Due to Cross Invalidation

The percentage of total reads to the group buffer pool required because the page in the member’s buffer pool was invalidated. ((QBGLXD + QBGLXR + QBGLXN) / (QBGLXD + QBGLXR + QBGLXN + QBGLMD + QBGLMR + QBGLMN + QBGLAD + QBGLAR + QBGLAN)) * 100

Reads Due to Cross Invalidation - Data Returned

The number of reads to the group buffer pool required because the page in the member’s buffer pool was invalidated, where the data was found and returned to the member. (QBGLXD)

Reads Due to Cross Invalidation - Data Not Returned - R/W Interest



directory entry for this page if it did not already exist. (QBGLXR)



Reads Due to Cross Invalidation - Data Not Returned - No R/W Interest


to go to DASD to read the page, and� no other member had read/write interest in the pageset, so DB2 did not

have to register the page, since another member cannot cause a cross-invalidation by updating a page. (QBGLXN)

Reads Due to Page Not Found In Buffer

The percentage of total reads to the group buffer pool required because the page was not in the member’s buffer pool. ((QBGLMD + QBGLMR + QBGLMN) / (QBGLXD + QBGLXR + QBGLXN + QBGLMD + QBGLMR + QBGLMN + QBGLAD + QBGLAR + QBGLAN)) * 100

Reads Due to Page Not Found In Buffer - Data Returned

The number of reads to the group buffer pool required because the page was not in the member’s buffer pool, where the data was found and returned to the member. (QBGLMD)

Reads Due to Page Not Found In Buffer - Data Not Returned - R/W Interest



directory entry for this page if it did not already exist. (QBGLMR)

Reads Due to Page Not Found In Buffer - Data Not Returned - No R/W Interest



have to register the page, since another member cannot cause a cross-invalidation by updating a page. (QBGLMN)

Reads Done By Prefetch

The percentage of total group buffer pool reads that were due to prefetch.

((QBGLAD + QBGLAR + QBGLAN) / (QBGLXD + QBGLXR + QBGLXN + QBGLMD + QBGLMR + QBGLMN + QBGLAD + QBGLAR + QBGLAN)) * 100

Reads Done By Prefetch - Data Returned

The number of reads to the group buffer pool performed for prefetch processing, where the data was found and returned to the member. (QBGLAD)

Reads Done By Prefetch - Data Not Returned - R/W Interest

The number of reads to the group buffer pool performed for prefetch processing, where� the data was not found in the group buffer pool and the member had

to go to DASD to read the page, and� other members had read/writ e interest in the pageset, so DB2 created

a directory entry for this page if it did not already exist. (QBGLAR)

Reads Done By Prefetch - Data Not Returned - No R/W Interest

The number of reads to the group buffer pool performed for prefetch processing, where� the data was not found in the group buffer pool and the member had


have to register the page, since another member cannot cause prefetch processing by updating a page. (QBGLAN)



Total Number of Reads

The total number of group buffer pool reads. (QBGLXD + QBGLXR + QBGLXN + QBGLMD + QBGLMR + QBGLMN + QBGLAD + QBGLAR + QBGLAN))

Read Hit Percentage

The percentage of all reads to the group buffer pool for which the needed data was found and returned to the member. ((QBGLXD + QBGLMD + QBGLAD) / (QBGLXD + QBGLXR + QBGLXN + QBGLMD + QBGLMR + QBGLMN + QBGLAD + QBGLAR + QBGLAN)) * 100

Percent Not Returned - R/W Interest

The percentage of all reads to the group buffer pool for which the data was not returned but other members had read/write interest in the pageset, so DB2 created an entry for the page if it did not already exist. ((QBGLXR + QBGLMR + QBGLAR) / (QBGLXD + QBGLXR + QBGLXN + QBGLMD + QBGLMR + QBGLMN + QBGLAD + QBGLAR + QBGLAN)) * 100

Percent Not Returned - No R/W Interest

The percentage of all reads to the group buffer pool for which the data was not found and no other member had read/write interest in the pageset, so DB2 did not have to register the page.

((QBGLXN + QBGLMN + QBGLAN) / (QBGLXD + QBGLXR + QBGLXN + QBGLMD + QBGLMR + QBGLMN + QBGLAD + QBGLAR + QBGLAN)) * 100

Other Requests Number of other requests. (QBGLOS)

Reads Failed - No Storage

Number of read requests failed because of a lack of storage resources. (QBGLRF)

Changed Pages - Sync

Number of writes under the user task for changed pages. (QBGLSW)

Clean Pages - Sync

Number of writes under the user task for clean pages. (QBGLWC)

Changed Pages - Async

Number of writes under a DB2 system execution unit for changed pages. (QBGLAW)

Clean Pages - Async

Number of writes under a DB2 system execution unit for clean pages. (QBGLAC)

Castout Engine Not Available

Number of times a castout engine was not available. (QBGLCN)

Write Engine Not Available

Number of times a write engine facility was not available for coupling writes. (QBGLSU)

Write Failed - No Storage

Number of write requests that failed because of a lack of storage resources. (QBGLWF)

Pages Castout From GBP to DASD

Number of pages castout to DASD from the group buffer pool. (QBGLRC)

Group B

uffer Pool Activity

300O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 Statistics Group Buffer Pool Activity Page 1Run Date=mm/dd/yyyy Group by None Run Time =16:37: 09 Sysid=SP22, DB2id=D412, Group=TDDB241G, Member=D412, Date=mm/dd/yyyy, Time=09:23------------------------------------------------------------------------------------------------------------------------------------Group Buffer Pool = 0---------------------------------General: Current Directory to Data Ratio = 5 Checkpoint Interval = 8 Pending Directory to Data Ratio = 5 Castout Threshold = 50% Number of Directory Entries = 442 Castout Threshold Reached = 0 Number of Data Pages = 84 Castout Class Threshold = Allocated Size of Group Buffer Pool = 512 KB Castout Class Threshold Reached = 0Read Operations: Reads Due To Cross Invalidation = 0% Reads Due To Page Not Found in Buffer Pool = 0% Data Returned = 0 Data Returned = 0 Data Not Returned - R/W Interest = 0 Data Not Returned - R/W Interest = 0 Data Not Returned - No R/W Interest = 0 Data Not Returned - No R/W Interest = 0 Reads Done by Prefetch = 0% Total Number of Reads = 0 Data Returned = 0 Read Hit Percentage = 0% Data Not Returned - R/W Interest = 0 Percent Not Returned - R/W Interest = 0% Data Not Returned - No R/W Interest = 0 Percent Not Returned - No R/W Interest = 0% Other Requests = 5 Reads Failed - No Storage = 0Write Operations: Changed Pages - Sync = 3 Castout Engine Not Available = Clean Pages - Sync = 0 Write Engine Not Available = 0 Changed Pages - Async = 0 Write Engine Failed - No Storage = 0 Clean Pages - Async = 0 Pages Castout from GBP to DASD = 0 Group Buffer Pool = 1---------------------------------General: Current Directory to Data Ratio = 5 Checkpoint Interval = 8 Pending Directory to Data Ratio = 5 Castout Threshold = 50% Number of Directory Entries = 442 Castout Threshold Reached = 0 Number of Data Pages = 84 Castout Class Threshold = 10% Allocated Size of Group Buffer Pool = 512 KB Castout Class Threshold Reached = 7Read Operations: Reads Due To Cross Invalidation = 0% Reads Due To Page Not Found in Buffer Pool = 100% Data Returned = 0 Data Returned = 0 Data Not Returned - R/W Interest = 0 Data Not Returned - R/W Interest = 49 Data Not Returned - No R/W Interest = 0 Data Not Returned - No R/W Interest = 0 Reads Done by Prefetch = 0% Total Number of Reads = 49 Data Returned = 0 Read Hit Percentage = 0% Data Not Returned - R/W Interest = 0 Percent Not Returned - R/W Interest = 100% Data Not Returned - No R/W Interest = 0 Percent Not Returned - No R/W Interest = 0% Other Requests = 20 Reads Failed - No Storage = 0Write Operations: Changed Pages - Sync = 80 Castout Engine Not Available = 0 Clean Pages - Sync = 0 Write Engine Not Available = 0 Changed Pages - Async = 0 Write Engine Failed - No Storage = Clean Pages - Async = 0 Pages Castout from GBP to DASD = 49

FIGURE 45. Statistics Group Buffer Pool Activity (Group by None)


Command Activity

Command Activity

IntroductionThis report displays the total number of times each DB2 command was issued. It is used to examine DB2 command activity for a DB2 subsystem.

Default DDnameO2RSCMD

Default TitleStatistics Command Activity





Data Elements







Start Database The number of START DB commands issued. (Q9STCTR5)

Stop Database The number of STOP DB commands issued. (Q9STSTR8)

Command Activity


Display Database

The number of DISPLAY DATABASE commands issued. (Q9STCR0)

Display Location The number of DISPLAY LOCATION commands issued. (Q9STCRL)

Set Archive The number of SET ARCHIVE commands executed to change the maximum tape units and the deallocation time parameters originally set in the installation parameters. (Q9STCTRP)

Display Archive The number of DISPLAY ARCHIVE commands executed to display input archive log information. (Q9STCTRQ)

Archive Log The number of ARCHIVE LOG commands issued. (Q9STCTRM)

Start DB2 The number of START DB2 commands issued. (Q9STCTR7)

Stop DB2 The number of STOP DB2 commands issued. (Q9STCTRA)

Start DDF The number of START DDF commands issued. (Q9STCTRI)

Stop DDF The number of STOP DDF commands issued. (Q9STCTRJ)

Start Proc The number of START PROCEDURE commands issued. Applies only to DB2 Version 4 and above. (Q9STCTRV)

Stop Proc The number of STOP PROCEDURE commands issued. Applies only to DB2 Version 4 and above. (Q9STCTRW)

Display Proc The number of DISPLAY PROCEDURE commands issued. Applies only to DB2 Version 4 and above. (Q9STCTRU)

Display Thread The number of DISPLAY THREAD commands issued. (Q9STCTR1)

Cancel Thread The number of CANCEL THREAD and CANCEL DDF THREAD commands issued. Applies only to DB2 Version 4 and above. (Q9STCTRK)

Cancel DDF The number of CANCEL DDF THREAD commands issued. (Q9STCTRK)

Display BPOOL The number of DISPLAY BUFFERPOOL commands executed to display statistics for active or inactive buffer pools. (Q9STCTRO)

Alter BPOOL The number of ALTER BUFFERPOOL commands executed to alter attributes for active or inactive buffer pools. (Q9STCTRN)

Display Group The number of DISPLAY GROUP commands issued. Applies only to DB2 Version 4 and above. (Q9STCTRX)

Display GBPOOL The number of DISPLAY GROUP BUFFER POOL commands issued. Applies only to DB2 Version 4 and above. (Q9STCTRT)

Alter GBPOOL The number of ALTER GROUP BUFFER POOL commands issued. Applies only to DB2 Version 4 and above. (Q9STCTRS)

Start Trace The number of START TRACE commands issued. (Q9STCTR6)

Stop Trace The number of STOP TRACE commands issued. (Q9STCTR9)

Display Trace The number of DISPLAY TRACE commands issued. (Q9STCTRC)

Modify Trace The number of MODIFY TRACE commands issued. (Q9STCTRH)

Start RLimit The number of START RLIMIT commands issued. (Q9STCTRE)

Stop RLimit The number of STOP RLIMIT commands issued. (Q9STCTRF)


Command Activity

Display RLimit The number of DISPLAY RLIMIT commands issued. (Q9STCRG)

Display Utility The number of DISPLAY UTILITY commands issued. (Q9STCTR2)

Term Utility The number of TERM UTILITY commands issued. (Q9STCTRB)

Recover BSDS The number of RECOVER BSDS commands issued. (Q9STCTR3)

Recover InDoubt The number of RECOVER INDOUBT commands issued. (Q9STCTR4)

Reset Indoubt The number of RESET INDOUBT commands executed to purge indoubt thread information. (Q9STCTRR)

Reset GenericLU The number of RESET GENERICLU commands issued. Applies only to DB2 Version 4 and above. (Q9STCTRD)

Unknown The number of invalid command requests issued. (Q9STEROR)

Com

mand A

ctivity

304O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 Statistics Command Activity Page=1Run Date=mm/dd/yyyy Grouped by DB2id Run Time=12.43.07 DB2id=A410------------------------------------------------------------------------------------------------------------------------------------Start Database = 0 Start DB2 = 4 Display Thread = 3 Start Trace = 49 Display Utility = 0Stop Database = 0 Stop DB2 = 0 Cancel Thread = 0 Stop Trace = 28 Term Utility = 0Display Database = 8 Start DDF = 0 Display BPOOL = 0 Display Trace = 2 Recover BSDS = 0Display Location = 0 Stop DDF = 0 Alter BPOOL = 0 Modify Trace = 0 Recover Indoubt = 0Set Archive = 0 Start Proc = 0 Display Group = 0 Start RLimit = 0 Reset Indoubt = 0Display Archive = 0 Stop Proc = 0 Display GBPOOL = 0 Stop RLimit = 0 Reset GenericLU = 0Archive Log = 0 Display Proc = 0 Alter GBPOOL = 0 Display RLimit = 0 Unknown = 0 DB2id=B310------------------------------------------------------------------------------------------------------------------------------------Start Database = 0 Start DB2 = 1 Display Thread = 1 Start Trace = 5 Display Utility = 1Stop Database = 0 Stop DB2 = 0 Cancel DDF = 0 Stop Trace = 5 Term Utility = 0Display Database = 2 Start DDF = 0 Start RLimit = 0 Display Trace = 1 Recover BSDS = 0Display Location = 0 Stop DDF = 0 Stop RLimit = 0 Modify Trace = 0 Recover Indoubt = 0Set Archive = 0 Archive Log = 0 Display RLimit = 0 Display BPOOL = 0 Reset Indoubt = 0Display Archive = 0 Alter BPOOL = 0 Unknown = 1 DB2id=C230------------------------------------------------------------------------------------------------------------------------------------Start Database = 0 Start DB2 = 2 Display Thread = 1 Start Trace = 12 Display Utility = 0Stop Database = 0 Stop DB2 = 0 Cancel DDF = 0 Stop Trace = 8 Term Utility = 0Display Database = 0 Start DDF = 0 Start RLimit = 0 Display Trace = 0 Recover BSDS = 0Display Location = 0 Stop DDF = 0 Stop RLimit = 0 Modify Trace = 0 Recover Indoubt = 0 Archive Log = 0 Display RLimit = 0 Unknown = 0 Reset Indoubt = 0

FIGURE 46. Statistics Command Activity Report


CPU Time Summary

CPU Time Summary

IntroductionThis report displays information about the CPU utilization of the DB2 address spaces.

Default DDnameO2RSCPU

Default TitleStatistics CPU Time Summary





Data Elements



Group The name of the DB2 data sharing group. (QWHADSGN)

Member The name of the member within a DB2 data sharing group. (QWHAMEMN)


Time The time at which DB2 generated the statistics data. (ZWHSTIME)

Total CPU The sum of all TCB and SRB times for all four DB2 address spaces (DBAS TCB, IRLM TCB, DDF TCB, SSAS SRB, DBAS SRB, IRLM SRB, DDF SRB).

SSAS TCB The amount of MVS TCB CPU time used by DB2 SSAS address space. (ZWSATCBS)

CPU Time Summary


DBAS TCB The amount of MVS TCB CPU time used by DB2 DBAS address space. (ZWASTCBD)

IRLM TCB The amount of MVS TCB CPU time used by DB2 IRLM address space. (ZWSATCBI)

DDF TCB The amount of MVS TCB CPU time used by DB2 DDF address space. (ZWASTCBF)

SSAS SRB The amount of MVS SRB CPU time used by DB2 SSAS address space. (ZWSASRBS)

DBAS SRB The amount of MVS SRB CPU time used by DB2 DBAS address space. (ZWASSRBD)

IRLM SRB The amount of MVS SRB CPU time used by DB2 IRLM address space. (ZWSASRBI)

DDF SRB The amount of MVS SRB CPU time used by DB2 DDF address space. (ZWASSRBF)

Historical R


eports307

CP

U Tim

e Sum

mary

Omegamon II for DB2 V540 Statistics CPU Time Summary Page 1Run Date=mm/dd/yyyy Grouped by Day Run Time=20:37:44 Date=mm/dd/yyyy------------------------------------------------------------------------------------------------------------------------------------Total CPU = 000:00:06.927885 TCB: SSAS = 000:00:04.412410 DBAS = 000:00:00.057613 IRLM = 000:00:00.008180 DDF = 000:00:00.000000 SRB: SSAS = 000:00:00.764847 DBAS = 000:00:00.070242 IRLM = 000:00:01.614588 DDF = 000:00:00.000000 Date=mm/dd/yyyy------------------------------------------------------------------------------------------------------------------------------------Total CPU = 000:01:08.029600 TCB: SSAS = 000:00:43.008030 DBAS = 000:00:00.594684 IRLM = 000:00:00.075474 DDF = 000:00:00.000000 SRB: SSAS = 000:00:07.737730 DBAS = 000:00:00.733434 IRLM = 000:00:15.880243 DDF = 000:00:00.000000 Date=mm/dd/yyyy------------------------------------------------------------------------------------------------------------------------------------Total CPU = 000:05:01.475212 TCB: SSAS = 000:03:08.639777 DBAS = 000:00:10.285407 IRLM = 000:00:00.746682 DDF = 000:00:00.485697 SRB: SSAS = 000:00:32.640209 DBAS = 000:00:09.855825 IRLM = 000:00:58.505726 DDF = 000:00:00.315882 Date=mm/dd/yyyy------------------------------------------------------------------------------------------------------------------------------------Total CPU = 000:03:00.919373 TCB: SSAS = 000:01:54.480874 DBAS = 000:00:10.529703 IRLM = 000:00:00.995854 DDF = 000:00:00.451481 SRB: SSAS = 000:00:17.810509 DBAS = 000:00:04.862321 IRLM = 000:00:31.577930 DDF = 000:00:00.210694

FIGURE 47. Statistics CPU Time Summary Report

Statistics Detail


Statistics Detail

IntroductionThis report displays detailed information about all aspects of the DB2 subsystem. It contains all the information that appears in the other statistics reports in this chapter.

Default DDnameO2RSDTL

Default TitleStatistics Detail





Data Elements

TITLE:







SUBSYSTEM ACTIVITY:

For field definitions for this portion of the Statistics Detail report, refer to “Subsystem Activity” on page 336.


Statistics Detail

SUBSYSTEM CPU TIME (IN SECONDS):

For field definitions for this portion of the Statistics Detail report, refer to “CPU Time Summary” on page 305.

BIND ACTIVITY: For field definitions for this portion of the Statistics Detail report, refer to “Bind Activity” on page 342.

DB2 COMMAND ACTIVITY:

For field definitions for this portion of the Statistics Detail report, refer to “Command Activity” on page 301.

SQL ACTIVITY: For field definitions for this portion of the Statistics Detail report, refer to “SQL Activity” on page 330.

EDM POOL ACTIVITY:

For field definitions for this portion of the Statistics Detail report, refer to “EDM Pool Activity” on page 316.

LOCK ACTIVITY: For field definitions for this portion of the Statistics Detail report, refer to “Lock Activity” on page 319.

LOG ACTIVITY: For field definitions for this portion of the Statistics Detail report, refer to “Log Activity” on page 326.

OPEN/CLOSE ACTIVITY:

For field definitions for this portion of the Statistics Detail report, refer to “Open/Close Activity” on page 350.

BUFFER POOL ACTIVITY:

For field definitions for this portion of the Statistics Detail report, refer to “Buffer Pool Activity” on page 288.

DISTRIBUTION INFORMATION:

For field definitions for this portion of the Statistics Detail report, refer to “Distributed Data Facility (DDF) Activity” on page 346.

Statistics D

etail

310O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 Statistics Detail Page 1Run Date=mm/dd/yyyy Grouped by None Run Time=15:22:11 Sysid=SP13, DB2id=D41B, Group=TDDB241G, Member=D41B, Date=mm/dd/yyyy, Time=09:10------------------------------------------------------------------------------------------------------------------------------------SUBSYSTEM ACTIVITY: Identify = 0 Synchronous Commit = 3 Abort = 0 Queued Create Thread = 0Signon = 0 Read Only Commit = 0 InDoubt = 0 System CheckPoint = 0Create Thread = 0 Commit Phase 1 = 0 End of Task = 0Terminate Thread = 0 Commit Phase 2 = 0 End of Memory = 0 SUBSYSTEM CPU TIME (IN SECONDS): Total CPU = 000:00:01.152477 TCB: SSAS = 000:00:00.573243 DBAS = 000:00:00.099423 IRLM = 000:00:00.000580 DDF = 000:00:00.055361 SRB: SSAS = 000:00:00.085862 DBAS = 000:00:00.100314 IRLM = 000:00:00.137295 DDF = 000:00:00.100392 BIND ACTIVITY: Auth Chk : Attempts = 2 Successes = 2 Using Cache = 0 Public = 0Plan : Alloc = 1 Alloc Success = 1 Autobind = 0 Autobind Suc= 0 Autobind Fail= 0 Rebind Cmd= 0 Rebind Attempt= 0 Rebind Succes= 0 Free Cmd = 0 Free Attempt = 0 Free Suc = 0 Bind Add = 0 Bind Replace = 0 Bind Test = 0 Bind Success = 0Package : Alloc = 0 Alloc Success = 0 Autobind = 0 Autobind Suc= 0 Autobind Fail= 0 Rebind Cmd= 0 Rebind Attempt= 0 Rebind Succes= 0 Free Cmd = 0 Free Attempt = 0 Free Suc = 0 Bind Add = 0 Bind Replace = 0 Bind Test = 0 Bind Success = 0 DB2 COMMAND ACTIVITY: Start Database = 0 Start DB2 = 0 Display Thread = 0 Start Trace = 1 Display Utility = 0Stop Database = 0 Stop DB2 = 0 Cancel Thread = 0 Stop Trace = 0 Term Utility = 0Display Database = 0 Start DDF = 0 Display BPOOL = 0 Display Trace = 0 Recover BSDS = 0Display Location = 0 Stop DDF = 0 Alter BPOOL = 0 Modify Trace = 0 Recover Indoubt = 0Set Archive = 0 Start Proc = 0 Display Group = 0 Start RLimit = 0 Reset Indoubt = 0Display Archive = 0 Stop Proc = 0 Display GBPOOL = 0 Stop RLimit = 0 Reset GenericLU = 0Archive Log = 0 Display Proc = 0 Alter GBPOOL = 0 Display RLimit = 0 Unknown = 0

FIGURE 48. Statistics Detail Report (1 of 6)

Historical R


eports311

Statistics D

etail

SQL ACTIVITY: DML Statements: Select = 0 Insert = 11 Open Cursor = 1 Prepare = 1 Update = 0 Fetch = 6 Describe = 1 Delete = 0 Close Cursor = 1 Describe Table = 0 DDL Statements: --------------- Create -------- Drop ------ Alter ------------------ Create ---------- Drop --------- Alter Table = 0 0 0 Tablespace = 0 0 0 View = 0 0 n/a Index = 0 0 0 Alias = 0 0 n/a Database = 0 0 0 Synonym = 0 0 n/a StoGroup = 0 0 0 Package = n/a 0 n/a DCL Statements: Grant = 0 Revoke = 0 Set Host Var = 0 Set Cur SQLid = 0 Lock Table = 0 Set Cur Rules = 0 Set Cur Degree = 0 Release = 0 Connect 1 = 0 Connect 2 = 0 Set Connection = 0 Miscellaneous: SQL Call = 0 Comment On = 0 Label On = 0 Incremental Bind = 0 Rid Pool Access: Successful = 0 Not Used due to Limit Exceeded = 0 Not Used due to No Storage = 0 Query Parallelism: Max Degree = 4 Parallel Groups Executed = 0 Sequential Mode - Cursor = 0 Planned Parallel Degree Executed = 0 Sequential Mode - No Buffer = 0 Reduced Parallel Degree Executed = 0 Sequential Mode - No ESA Sort = 0 Sequential Mode - No Enclave = 0 Stored Procedure: SQL Call = 0 Stored Procedure Abended = 0 SQL Call Statement Timed Out = 0 SQL Call Statement Rejected = 0 EDM POOL ACTIVITY: EDM Failed (Full) = 0 DBD: Avg Pages Used = 29 ( 1% of pool) Requests = 6 Loads = 0 ( 0% from pool)Avg Pages in Pool = 1828 CT: Avg Pages Used = 6 ( 0% of pool) Requests = 11 Loads = 2 ( 18% from pool)Avg Free Pages = 1756 PT: Avg Pages Used = 0 ( 0% of pool) Requests = 0 Loads = 0 ( 0% from pool)% Free Pages = 96 SKCT: Avg Pages Used = 36 ( 1% of pool) SKPT: Avg Pages Used = 1 ( 0% of pool)LOCK ACTIVITY: Lock Requests = 200 Deadlocks = 0 Lock Suspends = 0 Other Requests = 0Unlock Requests = 43 Timeouts = 0 Latch Suspends = 0 Other Suspends = 0Change Requests = 2 Claim Requests = 35 Drain Requests = 4 Escalations/SHR = 0Query Requests = 0 Failed Claims = 0 Failed Drains = 0 Escalations/EXCL = 0


Statistics D

etail

312O

ME

GA

MO

N II for D

B2 H


uide, Version 540

GLOBAL LOCK ACTIVITY: P-Lock Lock Requests = 11 Lock Requests Propagated to XES = 89 Suspends - IRLM Global Contention = 0P-Lock Change Requests = 0 Change Requests Propagated to XES = 0 Suspends - XES Global Contention = 0P-Lock Unlock Requests = 11 Unlock Requests Propagated to XES = 0 Suspends - False Contention = 49Incompatible Retained Locks = 0 Asynch Locks Propagated to XES = 78% % of Suspends - False Contention = 100%Notify Messages Sent = 0 Negotiate Pageset P-Locks = 10 Max Engines - P-Lock/Notify Exit = 0Notify Messages Received = 10 Negotiate Page P-Locks = 3 Engine Not Available Occurrences = 0CHANGEP Requests = 0 Negotiate Other P-Locks = 0

LOG ACTIVITY: Read Output Buffer = 0 Write Request = 10 CI Create = 4 Archive Read Allocate = 0Read Active Log = 0 Write No Wait = 82 CI Offload = 0 Archive Write Allocate = 0Read Archive Log = 0 Write Force = 4 Look-ahead Mt Attempt = 0 Read Delay Contention = 0BSDS Request = 0 Buffer Wait = 0 Look-ahead Mt Success = 0 Read Delay No Unit = 0High RBA = 000007E9F42F Checkpoint = 0

OPEN/CLOSE ACTIVITY: Open Datasets = 90 Not-in-use Datasets = 88 Not-in-use DS Accessed = 35 DS Converted to Read-Only = 4Max Open Datasets = 91 Max Not-in-use Datasets = 88 Not-in-use DS Closed = 0


Historical R


eports313

Statistics D

etail

BUFFER POOL ACTIVITY: Buffer Pool = 0---------------------------BP Parameters: VP Size = 2000 VP Sequential Thresh = 80% Defer Write Thresh = 50% HP Size = 0 HP Sequential Thresh = 80% Vert Defer Write Thresh = 10% Castout Attribute = YES VP Parallel Seq Thresh = 50%General: VP Buffer Allocated = 2000 Active Buffer = 23 VP Expand/Contract = 0 HP Buffer Allocated = 0 HP Buffer Backed = 0 HP Expand/Contract = 0 Recall Migrated Dataset = 0 Dataset Open = 1 VP/HP Expand Failed = 0 Recall Timeout = 0Read Operations: Getpage Request = 195 Getpage Request - Seq = 101 Getpage Request - Random= 94 Getpage Fail - VP Full = 0 Getpage Fail - Cond Req = 0 Getpages/Sync Read I/O = 9.75 Sync Read I/O = 20 Sync Read I/O - Seq = 1 Sync Read I/O - Random = 19 Seq Prefetch Request = 5 List Prefetch Request = 0 Dynamic Prefetch Request= 2 Seq Prefetch Page = 157 List Prefetch Page = 0 Dynamic Prefetch Page = 49 Seq Prefetch I/O = 5 List Prefetch I/O = 0 Dynamic Prefetch I/O = 2 Pgs Rd/Seq Prefetch I/O = 31.40 Pgs Rd/Lst Prefetch I/O = 0.00 Pgs Rd/Dyn Prefetch I/O = 24.50 PFetch Fail - No Buffer = 0 PFetch Fail - No Engine = 0 Page-in Due to Read = 0 BP Hit % - Random = 0% BP Hit % - Sequential = 0% HP Hit % = 0% HP Page Read Sync = 0 HP Pg Rd Async - No ADM = 0 HP Pg Rd Async - ADM = 0 HP Read Fail - No ADM = 0 HP Read Fail - ADM = 0Write Operations: Page Updated = 44 Page Written = 12 Updates/Page Written = 3.67 Write I/O Operation = 4 Immed (Sync) Write = 4 Pages/Write I/O = 1.50 VDWTH Reached = 0 DWTH Reached = 0 DMTH Reached = 0 Write Engine Not Avail = 0 Page-in Due to Write = 0 HP Page Written Sync = 0 HP Pg Wrt Async - No ADM= 0 HP Pg Wrt Async - ADM = 0 HP Write Fail - No ADM = 0 HP Write Fail - ADM = 0Query Parallelism: Parallel Group Request = 0 Parallelism Downgraded = 0 Prefetch I/O Strm Reduce= 0 Max Prefetch I/O = 0 Prefetch Reduced to 1/2 = 0 Prefetch Reduced to 1/4 = 0Sort/Merge: Sort Merge Pass Request = 0 Workfile Request = 0 Workfile Req Denied = 0 Merge Pass - Low Buffer = 0 WF Prefetch Disabled = 0 WF Create Fail-No Buff = 0 Workfile Maximum = 0 Destructive Read Req = 0 Destruct Rd Pg Dequeue = 0


Statistics D

etail

314O

ME

GA

MO

N II for D

B2 H


uide, Version 540

GROUP BUFFER POOL ACTIVITY: Group Buffer Pool = 0----------------------------General: Current Directory To Data Ratio = 5.6 Checkpoint Interval = 0:08 Pending Directory To Data Ratio = 6.0 Castout Threshold = 50% Number of Directory Entries = 61394 Castout Threshold Reached = 0 Number of Data Pages = 11370 Castout Class Threshold = 10% Allocated Size of Group Buffer Pool = 61440 KB Castout Class Threshold Reached = 0Read Operations: Reads Due To Cross Invalidation = 20% Reads Due To Page Not Found in Buffer Pool = 50% Data Returned = 170 Data Returned = 425 Data Not Returned - R/W Interest = 20 Data Not Returned - R/W Interest = 50 Data Not Returned - No R/W Interest = 10 Data not Returned - No R/W Interest = 25 Reads Done by Prefetch = 30% Total Number of Reads = 1000 Data Returned = 255 Read Hit Percentage = 85% Data Not Returned - R/W Interest = 30 Percent Not Returned - R/W Interest = 10% Data Not Returned - No R/W Interest = 15 Percent Not Returned - No R/W Interest = 5% Other Requests = 0 Reads Failed - No Storage = 0Write Operations: Changed Pages - Sync = 0 Castout Engine Not Available = 0 Clean Pages - Sync = 0 Write Engine Not Available = 0 Changed Pages - Async = 0 Write Failed - No Storage = 0 Clean Pages - Async = 0 Pages Castout From GBP to DASD = 0


Historical R


eports315

Statistics D

etail

DISTRIBUTED DATA FACILITY ACTIVITY: Cold Start Connections = 0 Resync Connections Attempted = 0 Current Inactive DBAT’s = 0Warm Start Connections = 0 Resync Connections Failed = 0 Maximum Inactive DBAT’s = 1 Conversations Dealloc - ZPARM Reached = 0 Current Active DBAT’s = 0 DBAT’s Queued - ZPARM Reached = 0 Maximum Active DBAT’s = 1 Maximum DBAT’s = 1 Remote Location = D41A Conversations Queued = 0 Message Buffer Rows = 5 Remote Coordinated Commits = 2 Block Mode Switches = 0 Remote Coordinated Rollbacks = 0 Binds for Remote = 0 Remote Coordinated Indoubts = 0 Transactions Conversations Statements Commits Aborts Rows Messages Bytes Blocks ------------ ------------- ---------- ----------- ---------- ---------- ---------- ------------ ------------ SENT 0 0 0 0 0 6 2 2344 1 RECEIVED 1 1 2 1 0 0 3 2344 0 2-PHASE COMMIT: Prepares Last Agents Commits Backouts Forgets CommitResps BackoutResps ---------- ----------- ---------- ---------- ---------- ----------- ------------ SENT 0 0 0 0 0 0 0 RECEIVED 0 0 0 0 0 0 0


EDM Pool Activity


EDM Pool Activity

IntroductionThis report displays EDM pool statistics, including data on the percentage of environment descriptor requests satisfied from within the pool without reading from DASD and EDM pool usage by the different types of pool elements: database descriptors (DBDs), cursor tables (CTs), skeleton cursor tables (SKCTs), and package tables (PTs) and skeleton package tables (SKPTs).

The DBD is the internal representation of DB2 database definitions, which reflect the data definitions in the DB2 catalog. The SKCT is a control structure produced during the bind process. The CT is a copy of an SKCT. It is used by DB2 to process SQL statements encountered during application execution. Each concurrent user of an application plan requires an individual copy of the CT in the EDM pool. The SKPT and PT are similar in function to SKCTs and CTs, but are used when packages are executed.

This report is used to examine the status of the EDM pool (and the pool elements) for any DB2 subsystem.

Default DDnameO2RSEDM

Default TitleStatistics EDM Activity





Data Elements






EDM Pool Activity



EDM Failed (Full) The number of EDM request failures due to EDM pool being full. (QISEFAIL)

DBD: Avg Pages Used

The number of pages in the EDM pool used by database descriptors (DBDs). This field is a snapshot value taken by DB2 at the time the statistics record was written. (QISEDBD)

DBD: Requests The number of EDM requests for database descriptors (DBDs). (QISEDBDG)

DBD: Loads The number of EDM requests for database descriptors (DBDs) resulting in loads from DASD. (QISEDBDL)

Avg Pages in Pool

The number of pages in the EDM pool. This field is a snapshot value taken by DB2 at the time the statistics record was written. (QISEPAGE)

CT: Avg Pages Used

The number of pages in the EDM pool used by cursor tables. This field is a snapshot value taken by DB2 at the time the statistics record was written. (QISECT)

CT: Requests The number of EDM requests for cursor table (CT) sections. (QISECTG)

CT: Loads The number of EDM requests for cursor table (CT) sections resulting in loads from DASD. (QISECTL)

Avg Free Pages The number of pages in the EDM pool available for use. This field is a snapshot value taken by DB2 at the time the statistics record was written. (QISEFREE)

PT: Avg Pages Used

Number of pages in the EDM pool used by package tables. This field is a snapshot value taken by DB2 at the time the statistics record was written. (QISEKT)

PT: Requests Number of EDM requests for package table sections. (QISEKTG)

PT: Loads Number of EDM requests for package table sections resulting in loads from DASD. (QISEKTG)

% Free Pages The number of pages in the EDM pool available for use. This field is a snapshot value taken by DB2 at the time the statistics record was written. (QISEFREE)

DSC: Avg Pages Used

The number of pages used for dynamic SQL cache. (QISEDSC)

DSC: Requests The number of EDM requests for dynamic SQL cache.(QISEDSG)

DSC: Loads The number of EDM requests for dynamic SQL cache resulting in inserts from DASD. (QISEDSI)

SKCT: Avg Pages Used

The number of pages in the EDM pool used by skeleton cursor tables (SKCTs). This field is a snapshot value taken by DB2 at the time the statistics record was written. (QISESKCT)

SKPT: Avg Pages Used

The number of pages in the EDM pool used by skeleton package tables (SPPTs). This field is a snapshot value taken by DB2 at the time the statistics record was written. (QISESKPCT)

ED

M Pool A

ctivity

318O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V520 Statistics EDM Activity Page 1Run Date=mm/dd/yyyy Grouped by None Run Time=10:26:35 Sysid=TCSF, DB2id=D61D, Group=DB01, Member=PAJ0, Date=mm/dd/yyyy, Time=08:13------------------------------------------------------------------------------------------------------------------------------------EDM Failed (Full) = 0 DBD: Avg Pages Used = 247 ( 3% of pool) Requests = 6722 Loads = 1 ( 0% from dasd)Avg Pages in Pool = 8000 CT: Avg Pages Used = 118 ( 1% of pool) Requests = 638 Loads = 8 ( 1% from dasd)Avg Free Pages = 997 PT: Avg Pages Used = 96 ( 0% of pool) Requests = 12426 Loads = 21 ( 0% from dasd)% Free Pages = 12 DSC: Avg Pages Used = 5054 ( 63% of pool) Requests = n/a Loads = n/a ( n/a from dasd)

SKCT: Avg Pages Used = 269 ( 3% of pool) SKPT: Avg Pages Used = 1219 ( 15% of pool) Sysid=SYSG, DB2id=D61A, Date=mm/dd/yyyy, Time=08:43------------------------------------------------------------------------------------------------------------------------------------EDM Failed (Full) = 0 DBD: Avg Pages Used = 251 ( 3% of pool) Requests = 6956 Loads = 5 ( 0% from dasd)Avg Pages in Pool = 8000 CT: Avg Pages Used = 114 ( 1% of pool) Requests = 578 Loads = 12 ( 2% from dasd)Avg Free Pages = 829 PT: Avg Pages Used = 41 ( 0% of pool) Requests = 14344 Loads = 140 ( 2% from dasd)% Free Pages = 10 DSC: Avg Pages Used = 5172 ( 64% of pool) Requests = 6281 Loads =

SKCT: Avg Pages Used = 284 ( 3% of pool) SKPT: Avg Pages Used = 1309 ( 16% of pool)

FIGURE 54. Statistics EDM Pool Activity Report


Lock Activity

Lock Activity

IntroductionThis report displays information about locking activity for a DB2 subsystem, including the number and type of suspensions, deadlock and timeout conditions, lock escalations, and lock manager requests. Claim and drain activity are displayed in this report as well.

A lock is a means of serializing events and/or access to data. DB2 locking is performed by the IMS/VS Resource Lock Manager (IRLM). Locking is the process by which integrity of data is ensured by preventing concurrent users from accessing inconsistent data.

A thread is suspended when it requests a lock held by another thread, the IRLM is busy processing another request, or the IRLM does not have enough storage to process the request.

A deadlock occurs when two applications require the locks that are held by each other. Based on the value specified in the IRLM PROC (DEADLOK), the IRLM scans its locks to discover any resource deadlock between two or more applications. If a deadlock is found, DB2 rolls back the thread that has written the smallest number of log records, and the other application is allowed to continue executing.

A timeout occurs when a thread is suspended while waiting for an unavailable resource longer than a predetermined time. That time is specified in the DSNZPARM parameters IRLMRWT and UTIMOUT.

A claim tells DB2 than an object is being accessed. A claim ensures that the object cannot be drained until a commit is reached.

A drain acquires a locked resource by quiescing access to that object. The drain lock prevents a claim from occurring.

This report is used to examine the status of the lock manager activity. The report information can reveal problems such as excessive lock escalation activity, deadlocks, and timeouts.

Default DDnameO2RSLCK

Default TitleAccounting Lock Activity



Lock Activity




Data Elements







Lock Requests The number of lock requests issued to IRLM. (QTXALOCK)

Deadlocks The number of deadlocks detected. (QTXADEA)

Lock Suspends The number of lock suspensions detected due to locking conflict. (QTXASLOC)

Other Requests The number of other types of lock manager requests issued to IRLM. (QTXAIRLM)

Unlock Requests The number of unlock requests issued to IRLM. (QTXAUNLK)

Timeouts The number of lock timeouts detected. (QTXATIM)

Latch Suspends The number of suspensions due to a latch conflict. (QTXASLAT)

Other Suspends The number of suspensions due to a reason other than locking or latching. (QTXASOTH)

Change Requests

The number of change requests issued to IRLM. (QTXACHG)

Claim Requests The number of claim requests. (QTXACLNO)

Drain Requests The number of drain requests. (QTXADRNO)

Escalations/SHR The number of shared lock escalations incurred. (QTXALES)

Query Requests The number of query requests issued to IRLM. (QTXAQRY)

Failed Claims The number of unsuccessful claim requests. (QTXACLUN)

Failed Drains The number of unsuccessful drain requests. (QTXADRUN)

Escalation/EXCL The number of exclusive lock escalations incurred. (QTXALEX)

Historical R


eports321

Lock A

ctivity

Omegamon II for DB2 V540 Accounting Lock Activity Page 1Run Date=mm/dd/yyyy Grouped by None Run Time=12.43.07 Ordered by DB2id Start Timestamp=1995-03-09-12.11.01.774567; End Timestamp=1995-03-09-12.15.16.207443; Termination=DEALLOCSysid=SP22, DB2ID=A410, Planname=JACK4040, Connid=DB2CALL, Corrid=TDDB20A, Original Authid=TDDB20ACommits=5, Aborts=1------------------------------------------------------------------------------------------------------------------------------------Lock Requests = 1653 Deadlocks = 2 Lock Suspends = 5 Other Requests = 4Unlock Requests = 2015 Timeouts = 3 Latch Suspends = 9 Other Suspends = 16Change Requests = 7 Claim Requests = 16 Drain Requests = 2 Escalations/SHR = 0Query Requests = 1 Failed Claims = 3 Failed Drains = 0 Escalations/EXCL = 0 Start Timestamp=1995-03-09-13.21.01.728719; End Timestamp=1995-03-09-13.25.16.209813; Termination=DEALLOCSysid=SYSG, DB2ID=B310, Planname=JACK3030, Connid=DB2CALL, Corrid=TDDB20B, Original Authid=TDDB20BCommits=3, Aborts=1------------------------------------------------------------------------------------------------------------------------------------Lock Requests = 274 Deadlocks = 2 Lock Suspends = 3 Other Requests = 2Unlock Requests = 65 Timeouts = 0 Latch Suspends = 33 Other Suspends = 2Change Requests = 13 Claim Requests = 19 Drain Requests = 19 Escalations/SHR = 0Query Requests = 1 Failed Claims = 0 Failed Drains = 0 Escalations/EXCL = 0 Start Timestamp=1995-03-09-14.31.01.789723; End Timestamp=1995-03-09-14.35.16.298792; Termination=DEALLOCSysid=SYSG, DB2ID=C230, Planname=JACK2020, Connid=DB2CALL, Corrid=TDDB20C, Original Authid=TDDB20CCommits=2, Aborts=0------------------------------------------------------------------------------------------------------------------------------------Lock Requests = 593 Deadlocks = 0 Lock Suspends = 1 Other Suspends = 1Unlock Requests = 240 Timeouts = 1 Latch Suspends = 12 Escalations/SHR = 0Change Requests = 23 Query Requests = 0 Other Requests = 3 Escalations/EXCL = 0

FIGURE 55. Accounting Lock Activity Report




IntroductionThis report displays information about global locking activity for a DB2 member in a data sharing group. Information includes the number of lock requests, the number of lock requests propagated to XES and the number of false contentions.

This report applies only to DB2s within a DB2 data sharing group.




� determining if the number of false contentions is too high

Default DDnameO2RSGLK

Default TitleStatistics Global Lock Activity





Data Elements







Group The name of the DB2 data sharing group. (QWHADSGN) Applies only to DB2 Version 4 and above.

Member The name of the DB2 member within the DB2 data sharing group. Applies only to DB2 Version 4 and above. (QWHAMEMN)

P-Lock Lock Requests

Number of lock requests for P-locks. (QTGSLPLK)

P-Lock Change Requests

Number of change requests for P-locks. (QTGSCPLK)

P-Lock Unlock Requests

Number of unlock requests for P-locks. (QTGSUPLK)

Incompatible Retained Locks

The number of global lock or change requests that failed because of an incompatible retained lock. Certain P-locks can be retained because of a system failure. Another DB2 member cannot access the data that the retained P-lock is protecting unless it requests a P-lock in a compatible state. (QTGSDRTA)

Notify Messages Sent

Number of notify messages sent. (QTGSNTFY)

Notify Messages Received

Number of notify messages received. (QTGSNTFR)

CHANGEP Requests

Number of CHANGEP requests. (QTGSCHNP)

Lock Requests Propagated to XES

Number of lock requests (both logical and physical) that are propagated to MVS XES synchronously under the caller’s execution unit. This count does not include suspended requests. Only the most restrictive lock for a particular resource is propagated to XES and the coupling facility. (QTGSLSLM)

Change Requests Propagated to XES

Number of change requests (both logical and physical) that are propagated to MVS XES synchronously under the caller’s execution unit. This count does not include suspended requests. (QTGSCSLM)

Unlock Requests Propagated to XES

Number of unlock requests (both logical and physical) that are propagated to MVS XES synchronously under the caller’s execution unit. This count does not include suspended requests. (QTGSUSLM)

Asynch Locks Propagated to XES

Number of L-locks and P-locks propagated by IRLM to XES asynchronously. This occurs when new inter-DB2 interest occurs on a parent resource or when a request completes after the requestor’s execution unit has been suspended. (QTGSKIDS)

Negotiate Pageset P-locks

Number of times this DB2 was driven to negotiate a pageset/ partition P-lock because of changing inter-DB2 interest levels on the pageset/partition. (QTGSPPPE)

Negotiate Page P-locks

Number of times this DB2 was driven to negotiate a page P-lock because of inter-DB2 P-lock contention. (QTGSPGPE)

Negotiate Other P-locks

Number of times this DB2 was driven to negotiate another P-lock type (other than pageset/partition or page). (QTGSOTPE)



Suspends - IRLM Global Contention

Number of suspends caused by IRLM Global resource contention. IRLM lock states were in conflict and inter-system communication is required to resolve the conflict. (QTGSIGLO)

Suspends - XES Global Contention

Number of suspends caused by XES Global resource contention, that were not IRLM-level contentions. XES lock states were in conflict but the IRLM lock states were not. (QTGSSGLO)

Suspends - False Contention

Number of suspends caused by MVS XES false contentions. XES detects hash class contention when two different locks on different resources hash to the same entry in the coupling facility lock table. The requester is suspended until it is determined that there is no real lock contention. (QTGSFLSE)

% of Suspends - False Contention

Percentage of suspends caused by false contentions relative to all suspends due to IRLM/XES contention. This indicates the ratio of false versus real contentions. This number should be no more than 50%. (QTGSFLSE/(QTGSFLSE + QTGSSGLO + QTGSIGLO)) * 100

Max Engines - P-Lock/Notify Exit

Maximum number of engines available for P-lock exit or Notify exit requests. (QTGSPEMX)

Engine Not Available Occurrences

Number of times an engine is not available for a P-lock exit or a Notify exit request. (QTGSPEQW)

Historical R


eports325

Global L

ock Activity

Omegamon II for DB2 V540 Statistics Global Lock Activity Page 1Run Date=mm/dd/yyyy Group by DB2ID, Day Run Time=17:09:57 DB2id=D411, Date=mm/dd/yyyy------------------------------------------------------------------------------------------------------------------------------------P-Lock Lock Requests = 47 Lock Requests Propagated to XES = 7683 Suspends - IRLM Global Contention = 0P-Lock Change Requests = 22 Change Requests Propagated to XES = 22 Suspends - XES Global Contention = 0P-Lock Unlock Requests = 1 Unlock Requests Propagated to XES = 7638 Suspends - False Contention = 0Notify Messages Sent = 0 Asynch Locks Propagated to XES = 0 % of Suspends - False Contention = 0%Notify Messages Received = 0 Max Engines - P-Lock/Notify Exit = 10 Negotiate Pageset P-Locks = 0Incompatible Retained Locks = 0 Engine Not Available Occurrences = 0 Negotiate Page P-Locks =CHANGEP Requests = 0 Negotiate Other P-Locks = 0 DB2id=D411, Date=mm/dd/yyyy------------------------------------------------------------------------------------------------------------------------------------P-Lock Lock Requests = 30 Lock Requests Propagated to XES = 5938 Suspends - IRLM Global Contention = 2P-Lock Change Requests = 0 Change Requests Propagated to XES = 0 Suspends - XES Global Contention = 0P-Lock Unlock Requests = 2 Unlock Requests Propagated to XES = 5915 Suspends - False Contention = 2Notify Messages Sent = 3 Asynch Locks Propagated to XES = 4 % of Suspends - False Contention = 50%Notify Messages Received = 3 Max Engines - P-Lock/Notify Exit = 10 Negotiate Pageset P-Locks = 0Incompatible Retained Locks = 0 Engine Not Available Occurrences = 0 Negotiate Page P-Locks = 0CHANGEP Requests = 0 Negotiate Other P-Locks = 0

FIGURE 56. Statistics Global Lock Activity (Group by DBID, Day)

Log Activity


Log Activity

IntroductionThis report displays log manager statistics, including read and write activity to both active and archive logs and activity against the bootstrap datasets (BSDS).

A log is a collection of records that describe the events that occur during DB2 execution. (It includes the sequence of the events.) This information is used for recovery in the event of a failure during DB2 execution.

The active log is the portion of the DB2 log to which log records are written as they are generated. The active log always contains the most recent log records (the most current log records are first located in memory and then written to the active log), whereas the archive log holds those records that are older and no longer will fit on the active log.

The BSDS is a VSAM dataset that contains name and status information for DB2, as well as RBA range specifications for all active and archive log datasets. It also contains passwords for the DB2 directory and catalog, and lists of conditional restart and checkpoint records. In a distributed DB2 environment, the BSDS includes a distributed database facility communication record. This record contains the DB2-defined location name, the VTAM-defined LUname, and the password used to connect DB2 to VTAM.

Single or dual logging can be specified and implemented for a given DB2 subsystem. Dual logging means that primary active log records are also copied to a secondary active log.

This report is used to examine the status of the log manager activity. The report information can reveal problems such as excessive read activity from the archive log.

Default DDnameO2RSLOG

Default TitleStatistics Log Activity





Log Activity


Data Elements







Read Output Buffer

The number of log read requests satisfied from log output buffer. (QJSTRBUF)

Read Active Log The number of log read requests satisfied from an active log dataset. (QJSTRACT)

Read Archive Log

The number of log read requests satisfied from an archive log dataset. (QJSTRARH)

BSDS Request The number of BSDS access requests performed. (QJSTBSDS)

High RBA The high used RBA of the active log. (QWSDLR)

Write Request The number of log write requests. Log write requests may result in one or more physical I/Os being processed. (QJSTBFWR)

Write No Wait The number of log write nowait requests issued. (QJSTWRNW)

Write Force The number of log write force requests issued. (QJSTWRF)

Buffer Wait The number of waits because no log output buffers were available. (QJSTWTB)

Checkpoint The number of DB2 checkpoints. (QWSDCKPT)

CI Created The number of active log CIs created. (QJSTBFFL)

CI Offload The number of active log CIs offloaded to an archive log. (QJSTCIOF)

Look Ahead Mt Attempt

The number of look-ahead tape mounts attempted. (QJSTLAMA)

Look Ahead Mt Success

The number of successful look-ahead tape mounts. (QJSTLAMS)

Archive Read Allocate

The number of archive log allocations due to archive log read I/O. (QJSTALR)

Archive Write Allocate

The number of archive log allocations due to archive log write I/O. (QJSTALW)

Log Activity


Read Delay Contention

The number of log reads delayed due to contention (a tape volume was already in use). (QJSTTVC)

Read Delay No Unit

The number of archive log reads that were delayed because of unavailable tape units, or because the maximum amount of read parallelism is being used. (QJSTWUR)

Historical R


eports329

Log Activity

Omegamon II for DB2 V540 Statistics Log Activity Page 1Run Date=mm/dd/yyyy Grouped by DB2id Run Time=12.43.07 DB2id=A410------------------------------------------------------------------------------------------------------------------------------------Read Output Buffer = 0 Write Request = 109 CI Create = 269 Archive Read Allocate = 0Read Active Log = 8305 Write No Wait = 2733 CI Offload = 0 Archive Write Allocate = 0Read Archive Log = 0 Write Force = 47 Look-ahead Mt Attempt = 0 Read Delay Contention = 0BSDS Request = 28 Buffer Wait = 0 Look-ahead Mt Success = 0 Read Delay No Unit = 0High RBA = 000003A0712C Checkpoint = 1 DB2id=B310------------------------------------------------------------------------------------------------------------------------------------Read Output Buffer = 178 Write Request = 679 CI Create = 774 Archive Read Allocate = 0Read Active Log = 291 Write No Wait = 10677 CI Offload = 1200 Archive Write Allocate = 2Read Archive Log = 0 Write Force = 222 Look-ahead Mt Attempt = 0 Read Delay Contention = 0BSDS Request = 303 Buffer Wait = 0 Look-ahead Mt Success = 0 Read Delay No Unit = 0High RBA = 000044A7C5D4 DB2id=C230------------------------------------------------------------------------------------------------------------------------------------Read Output Buffer = 0 Write Request = 10 CI Create = 4 Archive Read Allocate = 4Read Active Log = 183757 Write No Wait = 166 CI Offload = 0 Archive Write Allocate = 0Read Archive Log = 219602 Write Force = 3 BSDS Request = 100 Read Delay Contention = 0High RBA = 0002DB48525C Buffer Wait = 0 DB2id=D221------------------------------------------------------------------------------------------------------------------------------------Read Output Buffer = 0 Write Request = 21 CI Create = 54 Archive Read Allocate = 1Read Active Log = 1057 Write No Wait = 296 CI Offload = 902 Archive Write Allocate = 1Read Archive Log = 2702 Write Force = 33 BSDS Request = 20High RBA = 0002DB47C5D4 Buffer Wait = 0

FIGURE 57. Statistics Log Activity Report

SQL Activity


SQL Activity

IntroductionThis report displays statistics about Data Manipulation Language (DML), Data Control Language (DCL), and Data Definition Language (DDL) SQL statements, as well as information about RID Pool and Parallel I/O processing.

This report is used to monitor SQL activity. The report information can reveal problems such as excessive incremental binds, drop table activity, and lock table requests.

Default DDnameO2RSSQL

Default TitleStatistics SQL Activity





Data Elements








SQL Activity

DML Statements:

Select The number of SQL SELECT statements executed. (QXSELECT)

Insert The number of SQL INSERT statements executed. (QXINSRT)

Update The number of SQL UPDATE statements executed. (QXUPDTE)

Delete The number of SQL DELETE statements executed. (QXDELET)

Open Cursor The number of SQL OPEN CURSOR statements executed. (QXOPEN)

Fetch The number of SQL FETCH statements executed. (QXFETCH)

Close Cursor The number of SQL CLOSE CURSOR statements executed. (QXCLOSE)

Prepare The number of SQL PREPARE statements executed. (QXPREP)

Describe The number of SQL DESCRIBE statements executed. (QXDESC)

Describe Table The number of SQL DESCRIBE TABLE statements executed. (QXDSCRTB)

DDL Statements:

Create Table The number of SQL CREATE TABLE statements executed. (QXCRTAB)

Create View The number of SQL CREATE VIEW statements executed. (QXDEFVU)

Create Alias The number of SQL CREATE ALIAS statements executed. (QXCRALS)

Create Synonym The number of SQL CREATE SYNONYM statements executed. (QXCRSYN)

Create Tablespace

The number of SQL CREATE TABLESPACE statements executed. (QXCTABS)

Create Index The number of SQL CREATE INDEX statements executed. (QXCRINX)

Create Database The number of SQL CREATE DATABASE statements executed. (QXCRDAB)

Create StoGroup The number of SQL CREATE STORAGEGROUP statements executed. (QXCRSTG)

Drop Table The number of SQL DROP TABLE statements executed. (QXDRPTA)

Drop View The number of SQL DROP VIEW statements executed. (QXDRPVU)

Drop Alias The number of SQL DROP ALIAS statements executed. (QXDRPAL)

Drop Synonym The number of SQL DROP SYNONYM statements executed. (QXDRPSY)

Drop Tablespace The number of SQL DROP TABLESPACE statements executed. (QXDRPTS)

Drop Index The number of SQL DROP INDEX statements executed. (QXDRPIX)

Drop Database The number of SQL DROP DATABASE statements executed. (QXDRPDB)

Drop StoGroup The number of SQL DROP STOGROUP statements executed. (QXDRPST)

Drop Package The number of SQL DROP PACKAGE statements executed. (QXDRPPKG)

Alter Table The number of SQL ALTER TABLE statements executed. (QXALTTA)

SQL Activity


Alter Tablespace The number of SQL ALTER TABLESPACE statements executed. (QXALTTS)

Alter Index The number of SQL ALTER INDEX statements executed. (QXALTIX)

Alter Database The number of SQL ALTER DATABASE statements executed. (QXALDAB)

Alter StoGroup The number of SQL ALTER STOGROUP statements executed. (QXALTST)

DCL Statements:

Grant The number of SQL GRANT statements executed. (QXGRANT)

Release The number of SQL RELEASE statements executed by the thread to place one or more connections in the released state. (QXREL)

Revoke The number of SQL REVOKE statements executed. (QXREVOK)

Lock Table The number of SQL LOCK TABLE statements executed. (QXLOCK)

Connect 1 The number of SQL CONNECT (Type 1) statements executed by the thread to connect an application process to a designated server. (QXCON1)

Set Host Var The number SQL SET host variable statements executed. (QXSETHV)

Set Cur Rules The number of SET CURRENT RULES statements executed. This tells DB2 whether an SQL statement should be processed in the ‘DB2’ way or the ‘standard’ way. (QXSETCRL)

Connect 2 The number of SQL CONNECT (Type 2) statements executed by the thread to connect an application process to a designated server. (QXCON2)

Set Cur SQLid The number of SQL SET CURRENT SQLID statements executed. (QXSETSQL)

Set Cur Degree The number of SQL SET CURRENT DEGREE statements executed by the thread to assign a value to the CURRENT DEGREE special register. (QXSETCDG)

Set Connection The number of SQL SET CONNECTION statements executed by the thread to establish the application server of the process. (QXSETCON)

Miscellaneous Statements:

Comment On The number of SQL COMMENT ON statements executed. (QXCMTON)

Label On The number of SQL LABEL ON statements executed. (QXLABON)

Incremental Bind The number of incremental binds processed. (QXINCRB)

Rid Pool Access:

Successful The number of times RID list processing was used. RID list processing can be used with single index access as in list prefetch, or multiple access. (QXMIAP)

Not Used due to No Storage

Number of times RID list processing was terminated because of insufficient storage to hold the list of RIDs. (QXNSMIAP)


SQL Activity

Not Used due to Limit Exceeded

Number of times RID list processing was terminated because the number of RIDs would exceed a RID limit or threshold. (QXMRMIAP)

Query Parallelism:

Max Degree The maximum degree of parallelism processed for the thread. (QXMAXDEG)

Parallel Groups Executed

The total number of parallel groups executed for the thread. (QXTOTGRP)

Sequential Mode - Cursor

The total number of parallel groups that went back to sequential processing because cursor could be used for UPDATE or DELETE.(QXDEGCUR)

Planned Parallel Degree Executed

The total number of parallel groups that were executed at the planned parallel degree. (QXNORGRP)

Sequential Mode - No Buffer

The total number of parallel groups that went back to sequential processing because of storage shortage or buffer pool contention. (QXDEGBUF)

Reduced Parallel Degree Executed

The total number of parallel groups that were processed at a parallel degree less than planned because of storage shortage or buffer pool contention. (QXREDGRP)

Sequential Mode - No ESA Sort

The total number of parallel groups that went back to sequential processing because there was no ESA sort support available. (QXDEGESA)

Sequential Mode - No Enclave

The number of parallel groups executed in sequential mode due to unavailable enclave. Applies only to DB2 Version 4 and above. (QXDEGENC)

Stored Procedure:

SQL Call The number of times SQL calls were issued to invoke stored procedure. Applies only to DB2 Version 4 and above. (QXCALL)

Stored Procedure Abended

The number of time a stored procedure abended. Applies only to DB2 Version 4 and above. (QXCALLAB)

SQL Call Statement Time Out

The number of times an SQL call statement timed out waiting to be scheduled. Applies only to DB2 Version 4 and above. (QXCALLTO)

SQL Call Statement Rejected

The number of times an SQL CALL statement was rejected. Applies only to DB2 Version 4 and above. (QXCALLRJ)

SQ

L A

ctivity

334O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 Statistics SQL Activity Page 1Run Date=mm/dd/yyyy Group by None Run Time 12.43.07 Sysid=SP22, DB2ID=D41A, Date=mm/dd/yyyy, Time=07:16------------------------------------------------------------------------------------------------------------------------------------DML Statements: Select = 3 Insert = 0 Open Cursor = 7 Prepare = 0 Update = 0 Fetch = 68 Describe = 0 Delete = 0 Close Cursor = 7 Describe Table = 0 DDL Statements: --------------- Create -------- Drop ------ Alter ------------------ Create ---------- Drop --------- Alter Table = 0 0 0 Tablespace = 0 0 0 View = 0 0 0 Index = 0 0 0 Alias = 0 0 n/a Database = 0 0 0 Synonym = 0 0 n/a StoGroup = 0 0 0 Package = n/a 0 n/a DCL Statements: Grant = 0 Revoke = 0 Set Host Var = 0 Set Cur SQLid = 0 Lock Table = 0 Set Cur Rules = 0 Set Cur Degree = 0 Release = 0 Connect 1 = 0 Connect 2 = 0 Set Connection = 0 Miscellaneous: SQL Call = 0 Comment On = 0 Label On = 0 Incremental Bind = 0 RID Pool Access: Successful = 3 Not Used due to No Storage = 0 Not Used due to Limit Exceeded = 0 Query Parallelism: Max Degree = 0 Parallel Groups Executed = 0 Sequential Mode - Cursor = 0 Planned Parallel Degree Executed = 0 Sequential Mode - No Buffer = 0 Reduced Parallel Degree Executed = 0 Sequential Mode - No ESA Sort = 0 Sequential Mode - No Enclave = 0 Stored Procedure: SQL Call = 0 Stored Procedure Abended = 0 SQL Call Statement Time Out = 0 SQL Call Statement Rejected = 0

FIGURE 58. Statistics SQL Activity Report (1 of 2)

Historical R


eports335

SQ

L A

ctivity

Omegamon II for DB2 V540 Statistics SQL Activity Page 2Run Date=mm/dd/yyyy Group by None Run Time 12.43.07 Sysid=SYSG, DB2ID=D31A, Date=mm/dd/yyyy, Time=08:45------------------------------------------------------------------------------------------------------------------------------------DML Statements: Select = 3 Insert = 0 Open Cursor = 7 Prepare = 0 Update = 0 Fetch = 68 Describe = 0 Delete = 0 Close Cursor = 7 Describe Table = 0 DDL Statements: --------------- Create -------- Drop ------ Alter ------------------ Create ---------- Drop --------- Alter Table = 0 0 0 Tablespace = 0 0 0 View = 0 0 0 Index = 0 0 0 Alias = 0 0 n/a Database = 0 0 0 Synonym = 0 0 n/a StoGroup = 0 0 0 Package = n/a 0 n/a DCL Statements: Grant = 0 Revoke = 0 Set Host Var = 0 Set Cur SQLid = 0 Lock Table = 0 Set Cur Degree = 0 Release = 0 Connect 1 = 0 Connect 2 = 0 Set Connection = 0 Miscellaneous: Comment On = 0 Label On = 0 Incremental Bind = 0 RID Pool Access: Successful = 3 Not Used due to No Storage = 0 Not Used due to Limit Exceeded = 0 Query Parallelism: Max Degree = 0 Parallel Groups Executed = 0 Sequential Mode - Cursor = 0 Planned Parallel Degree Executed = 0 Sequential Mode - No Buffer = 0 Reduced Parallel Degree Executed = 0 Sequential Mode - No ESA Sort = 0

FIGURE 59. Statistics SQL Activity Report (2 of 2)

Subsystem Activity


Subsystem Activity

IntroductionThis report displays the subsystem service statistics, including thread creation, queuing at create-thread time, identify, signon, and termination. This report also provides counts of commits, aborts, recovery indoubt situations (including those resolved successfully), system event checkpoints, and subsystem allied memory conditions—end of memory (EOM) and end of task (EOT).

This report is used to examine the overall subsystem service activity level for a DB2 subsystem. The report information can reveal problems such as an excessive number of indoubt conditions and an excessive abort rate.

Default DDnameO2RSSSA

Default TitleStatistics Subsystem Activity





Data Elements






Subsystem Activity


Hour The hour at which DB2 generated the statistics data. (ZWHSHOUR)

Identify The number of successful DB2 identify requests. (Q3STIDEN)

Signon The number of DB2 signon thread requests. (Q3STSIGN)

Create Thread The number of create thread requests. (Q3STCTHD)

Terminate Thread

The number of terminate thread requests. (Q3STTERM)

Synchronous Commit

The number of synchronous (not two-phase) commit requests. (Q3STSYNC)

Read Only Commit

The number of read only commits processed. (Q3STRDON)

Commit Phase 1 The number of commit phase 1 requests. (Q3STPREP)

Commit Phase 2 The number of commit phase 2 requests. (Q3STCOMM)

Abort The number of abort requests. (Q3STABRT)

InDoubt The number of successful resolve indoubt unit of recovery requests. (Q3STRIUR)

End of Task The number of times allied agents tasks abended while connected to DB2. (Q3STMEOT)

End of Memory The number of times allied agents terminated due to end of memory condition while connected to DB2. (Q3STMEOM)

Queued Create Thread

The number of create thread requests queued due to maximum number of threads (CTHREAD) being reached. (Q3STCTHW)

System Checkpoint

The number of system checkpoints incurred. (QWSDCKPT)

Subsystem

Activity

338O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 Statistics Subsystem Activity Page 1Run Date=mm/dd/yyyy Grouped by DB2id Run Time=20:37:44 DB2id=D23A------------------------------------------------------------------------------------------------------------------------------------Identify = 34 Synchronous Commit = 30 Abort = 1 Queued Create Thread = 0Signon = 1 Read Only Commit = 0 InDoubt = 0 System CheckPoint = 1Create Thread = 25 Commit Phase 1 = 0 End of Task = 8Terminate Thread = 60 Commit Phase 2 = 0 End of Memory = 0 DB2id=D23B------------------------------------------------------------------------------------------------------------------------------------Identify = 19 Synchronous Commit = 16 Abort = 0 Queued Create Thread = 0Signon = 0 Read Only Commit = 0 InDoubt = 0 System CheckPoint = 6Create Thread = 17 Commit Phase 1 = 0 End of Task = 2Terminate Thread = 33 Commit Phase 2 = 0 End of Memory = 0 DB2id=D31A------------------------------------------------------------------------------------------------------------------------------------Identify = 69 Synchronous Commit = 108 Abort = 17 Queued Create Thread = 0Signon = 0 Read Only Commit = 0 InDoubt = 0 System CheckPoint = 12Create Thread = 80 Commit Phase 1 = 0 End of Task = 12Terminate Thread = 149 Commit Phase 2 = 0 End of Memory = 0

FIGURE 60. Subsystem Activity


Statistics Summary

Statistics Summary

IntroductionThis report displays a summary of the key DB2 subsystem statistics information, including SQL activity, resource usage, and I/O activity.

This report provides summary information on the DB2 subsystem activity. The report information can reveal potential problems within several components of the DB2 subsystem.

Default DDnameO2RSSUM

Default TitleStatistics Summary





Data Elements







Statistics Summary


Create Threads The number of create thread requests. (Q3STCTHD)

Units of Work The total number of commits and aborts.(Q3STCOMM + Q3STABRT + Q3STSYNC + Q3STRDON)

DML Activity The total number of SQL data manipulative language statements.

DDL Activity The total number of SQL data definitional language statements.

DCL Activity The total number of SQL data control language statements.

Synch Read I/O The total number of synchronous read I/Os issued. (QBSTRIO)

Prefetch I/O The total number of asynchronous read I/Os caused by list, dynamic, and sequential prefetch I/O operations. (QBSTLIP + QBSTDIO + QBSTPIO)

Write I/O Number of synchronous and asynchronous I/Os performed. (QBSTWIO + QBSTIMW)

GetPg/Read I/O The number of getpages per synchronous read I/O. (QBSTGET/QBSTRIO)

Load PT CT DBD The number of CT, PT, and DBD requests that resulted in loads from DASD. (ZISELOAD)

%Load PT CT DBD

The percentage of DBD (database descriptor) requests that resulted in loads from DASD. This value should be kept low; 20% or lower is considered acceptable. (ZISELODP)

Lock Suspnds The number of lock suspensions detected due to locking conflict. (QTXASLOC)

Deadlck Timeout The number of deadlock timeouts detected. (QTXADEA)

Historical R


eports341

Statistics S

umm

ary

Omegamon II for DB2 V540 Statistics Summary Page 1Run Date=mm/dd/yyyy Grouped by None Run Time=15:42:47 Create Units DML DDL DCL Synch Prefetch Write GetPg Load PT %LoadPT Lock DeadlckDB2id Date Time Threads of Work Activity Activity Activity Read I/O I/O I/O /ReadIO CT DBD CT DBD Suspnds Timeout----- ---------- ----- ------- -------- -------- -------- -------- -------- -------- ------ ------- -------- ------- ------- -------D23A 10/20/1993 08:13 1 0 0 0 0 20 0 0 2 1 14 0 0D23A 10/20/1993 08:43 0 0 0 0 0 0 0 0 0 0 0 0 0D23A 10/20/1993 09:12 1 2 203 0 0 150 14 3 2 2 50 0 0D23A 10/20/1993 09:42 2 2 0 0 0 9 0 0 62904 0 0 0 0D23A 10/20/1993 10:12 2 3 0 0 0 4159 19 3 104 27 0 0 0D23A 10/20/1993 10:42 1 1 0 0 0 1 0 0 202958 0 0 0 0D23A 10/20/1993 11:12 5 5 0 0 0 3 0 0 127545 0 0 0 0D23A 10/20/1993 11:42 1 1 0 0 0 0 0 0 0 0 0 0 0D23A 10/20/1993 12:12 0 0 0 0 0 0 0 0 0 0 0 0 0D23A 10/20/1993 12:42 1 0 203 0 0 121 13 0 3031 0 0 0 0D23A 10/20/1993 13:12 3 6 854 0 0 37 1 0 8617 0 0 0 0D23A 10/20/1993 13:42 0 2 0 0 0 0 0 0 0 0 0 0 0D23A 10/20/1993 14:12 7 8 0 0 0 1 0 0 320098 0 0 0 0D23A 10/20/1993 14:41 1 1 0 0 0 0 0 0 0 0 0 0 0D23A 10/20/1993 15:11 0 0 0 0 0 0 0 0 0 0 0 0 0D23A 10/20/1993 15:41 0 0 0 0 0 0 0 0 0 0 0 0 0D23A 10/20/1993 16:11 0 0 0 0 0 1 0 0 313883 0 0 0 0D23A 10/20/1993 16:41 0 0 0 0 0 0 0 0 0 0 0 0 0D23B 10/20/1993 00:42 1 0 0 0 0 43 0 0 3 2 22 0 0D23B 10/20/1993 01:12 0 0 0 0 0 0 0 0 0 0 0 0 0D23B 10/20/1993 01:42 0 0 0 0 0 0 0 0 0 0 0 0 0D23B 10/20/1993 02:12 0 0 0 0 0 0 0 0 0 0 0 0 0D23B 10/20/1993 02:42 0 0 0 0 0 0 0 0 0 0 0 0 0D23B 10/20/1993 04:36 1 0 0 0 0 43 0 0 3 2 22 0 0D23B 10/20/1993 05:06 0 0 0 0 0 0 0 0 0 0 0 0 0D23B 10/20/1993 05:36 0 0 0 0 0 0 0 0 0 0 0 0 0D23B 10/20/1993 06:05 0 0 0 0 0 0 0 0 0 0 0 0 0D23B 10/20/1993 06:35 0 0 0 0 0 0 0 0 0 0 0 0 0D23B 10/20/1993 07:05 0 0 0 0 0 0 0 0 0 0 0 0 0D23B 10/20/1993 07:35 0 0 0 0 0 0 0 0 0 0 0 0 0D23B 10/20/1993 08:05 0 0 0 0 0 0 0 0 0 0 0 0 0D23B 10/20/1993 08:35 0 0 0 0 0 0 0 0 0 0 0 0 0

FIGURE 61. Statistics Summary Report

Bind Activity


Bind Activity

IntroductionThis report displays the bind statistics, such as automatic bind, static bind, rebind, and free statistics.

Before you can execute an application program, you must bind a plan to establish a relationship between the program and its DB2 data or objects. The bind process validates DB2 objects using the DB2 catalog, validates SQL statement syntax, performs an authorization check, selects the access path(s) needed to access the DB2 data, and builds a plan/package to allow DB2 to access the data when the application is executed. The plan/package is copied into the EDM pool as the skeleton cursor table (SKCT) or skeleton package table (SKPT).

This report provides information on bind and free activity for a DB2 subsystem during the reporting interval. The report information can reveal excessive bind activity as well as the percentage of bind failures.

Default DDnameO2RSBND

Default TitleStatistics Bind Activity





Data Elements




Bind Activity





Auth Chk:

Attempts The number of authorization check attempts performed against plans. (QTAUCHK)

Successes The number of successful authorization check attempts. (QTAUSUC)

Using Cache The number of successful authorization checks using cache. (QTAUCCH, QTAUPUB)

Public Number of successful authorization checks based upon execute authority granted to public. (QTAUPUB)

Plan:

Alloc The number of plan allocation attempts that occurred during create thread processing. (QTALLOCA)

Alloc Success The number of plan allocation attempts that were successful. (QTALLOC)

Autobind The number of times DB2 attempted an automatic bind. (QTABINDA)

Autobind Suc The number of times automatic bind processing was successful. (QTABIND)

Autobind Fail The number of times plan allocation failed because the plan was not located. (QTABINDA-QTABIND)

Rebind Cmd The number of REBIND subcommands issued. More than one plan can be rebound for each REBIND subcommand. (QTREBIND)

Rebind Attempt The number of REBIND attempts. This count is incremented for each plan rebound for each REBIND subcommand request. (QTRBINDA)

Rebind Success The number of times a plan was successfully rebound. (QTPLNRBD)

Free Cmd The number of FREE subcommands issued. It is possible to free more than one plan in a single FREE subcommand request. (QTFREE)

Free Attempt The number of attempts to free a plan. This number may be larger than FREE command because a single FREE subcommand request can free multiple plans. (QTFREEA)

Free Suc The number of successful attempts to free a plan. (QTPLNFRD)

Bind Add The number of BIND ADD subcommands processed. (QTBINDA)

Bind Replace The number of BIND REPLACE subcommands attempted. (QTBINDR)

Bind Test The number of BIND TEST subcommands processed. (QTTESTB)

Bind Success The number of plans bound successfully. This field is equal to the sum of BIND ADD and BIND REPLACE totals if all were successful. (QTPLNBD)

Bind Activity


Package:

Alloc The number of attempts to allocate a new package. (QTPKALLA)

Alloc Success The number of packages successfully allocated. (QTPKALL)

Autobind The number of times DB2 attempted to automatically bind a package. (QTAUTOBA)

Autobind Suc The number of times automatic bind of a package was successful. (QTPKABND)

Autobind Fail The number of times package allocation failed because the package was not located. (QTAUTOBA-QTPKABND)

Rebind Cmd The number of REBIND package subcommands issued. (QTRBINDP)

Rebind Attempt The number of attempts to rebind a package. (QTRBNDPA)

Rebind Success The number of packages successfully rebound. (QTPKGRBD)

Free Cmd The number of FREE package subcommands issued. (QTFREEP)

Free Attempt The number of attempts to free a package. (QTFREEAP)

Free Suc The number of packages successfully freed. (QTPKGFRD)

Bind Add The number of BIND (ADD) package subcommands processed. (QTBINDPA)

Bind Replace The number of BIND (REPLACE) package subcommands. (QTBINPR)

Bind Test he number of BIND TEST subcommands processed. (QTTESTB)

Bind Success The number of packages successfully bound. This field is equal to the sum of BIND ADD and BIND REPLACE totals if all were successful. (QTPKGBD)

Historical R


eports345

Bind A

ctivity

Omegamon II for DB2 V540 Statistics Bind Activity Page 1Run Date=mm/dd/yyyy Grouped by None Run Time=10:15:38 Sysid=SYSG, DB2id=D23A, Date=mm/dd/yyyy, Time=08:13------------------------------------------------------------------------------------------------------------------------------------Auth Chk : Attempts = 6 Successes = 6 Using Cache = 0 Public = 0Plan : Alloc = 1 Alloc Success = 1 Autobind = 0 Autobind Suc= 0 Autobind Fail= 0 Rebind Cmd= 0 Rebind Attempt= 0 Rebind Succes= 0 Free Cmd = 0 Free Attempt = 0 Free Suc = 0 Bind Add = 0 Bind Replace = 0 Bind Test = 0 Bind Success = 0Package : Alloc = 0 Alloc Success = 0 Autobind = 0 Autobind Suc= 0 Autobind Fail= 0 Rebind Cmd= 0 Rebind Attempt= 0 Rebind Succes= 0 Free Cmd = 0 Free Attempt = 0 Free Suc = 0 Bind Add = 0 Bind Replace = 0 Bind Test = 0 Bind Success = 0 Sysid=SYSG, DB2id=D23A, Date=mm/dd/yyyy, Time=08:43------------------------------------------------------------------------------------------------------------------------------------Auth Chk : Attempts = 0 Successes = 0 Using Cache = 0 Public = 0Plan : Alloc = 0 Alloc Success = 0 Autobind = 0 Autobind Suc= 0 Autobind Fail= 0 Rebind Cmd= 0 Rebind Attempt= 0 Rebind Succes= 0 Free Cmd = 0 Free Attempt = 0 Free Suc = 0 Bind Add = 0 Bind Replace = 0 Bind Test = 0 Bind Success = 0Package : Alloc = 0 Alloc Success = 0 Autobind = 0 Autobind Suc= 0 Autobind Fail= 0 Rebind Cmd= 0 Rebind Attempt= 0 Rebind Succes= 0 Free Cmd = 0 Free Attempt = 0 Free Suc = 0 Bind Add = 0 Bind Replace = 0 Bind Test = 0 Bind Success = 0 Sysid=SYSG, DB2id=D23A, Date=mm/dd/yyyy, Time=09:12------------------------------------------------------------------------------------------------------------------------------------Auth Chk : Attempts = 3 Successes = 3 Using Cache = 0 Public = 0Plan : Alloc = 1 Alloc Success = 1 Autobind = 0 Autobind Suc= 0 Autobind Fail= 0 Rebind Cmd= 0 Rebind Attempt= 0 Rebind Succes= 0 Free Cmd = 0 Free Attempt = 0 Free Suc = 0 Bind Add = 0 Bind Replace = 0 Bind Test = 0 Bind Success = 0Package : Alloc = 1 Alloc Success = 1 Autobind = 0 Autobind Suc= 0 Autobind Fail= 0 Rebind Cmd= 0 Rebind Attempt= 0 Rebind Succes= 0 Free Cmd = 0 Free Attempt = 0 Free Suc = 0 Bind Add = 0 Bind Replace = 0 Bind Test = 0 Bind Success = 0

FIGURE 62. Bind Activity Report




IntroductionThis report displays statistics about the Distributed Data Facility (DDF), including information about communication activity between DB2 subsystems.

The DDF enables an application program connected to one DB2 subsystem to access data residing on another DB2 subsystem in which a DDF is active.

This report is used to examine the DDF activity for a given DB2 subsystem. The report information can reveal the potential response problems that are due to the distributed environment.

Default DDnameO2RSDDF

Default TitleStatistics Distributed Activity





Data Elements









Cold Start Connections

Number of cold start connections with all remote locations (two-phase commit protocol only). (QDSTCSTR)

Warm Start Connections

Number of warm start connections with all remote locations (two-phase commit protocol only). (QDSTWSTR)

Resync Connections Attempted

Number of resynchronization connections attempted with all remote locations (two-phase commit protocol only). (QDSTRSAT)

Resync Connections Failed

Number of resynchronization connections that failed with all remote locations (two-phase commit protocol only). (QDSTRSAT-QDSTRSSU)

Conversations Dealloc - ZPARM Reached

Number of conversations deallocated because the DSNZPARM limit for maximum connected threads (active + inactive) was reached. (QDSTQCRT)

DBAT’s Queued - ZPARM Reached

Number of times that a DBAT was queued because the DSNZPARM limit for maximum active remote threads was reached. (QDSTQDBT)

Current Inactive DBAT’s

Number of current inactive DBAT’s. (QDSTQCIT)

Maximum Inactive DBAT’s

Maximum number of current inactive DBAT’s that existed (high water mark). (QDSTQMIT)

Current Active DBAT’s

Number of current active DBAT’s (snapshot). Applies only to DB2 Version 4 and above. (QDSTCNAT)

Maximum Active DBAT’s

Maximum number of active DBAT’s (high water mark). Applies only to DB2 Version 4 and above. (QDSTHWAT)

Maximum DBAT’s

Maximum number of active and inactive DBAT’s that existed (high water mark). Applies only to DB2 Version 4 and above. (QDSTHWDT)

Remote Location The DDF location name of the remote site associated with the subsequent block of data. (QLSTLOCN)

Conversations Queued

The number of conversation requests queued by DDF waiting for allocation. (QLSTCNVQ)

Message Buffer Rows

The number of rows in the message buffer if block fetch is being used. (QLSTBROW)

Block Mode Switches

Number of times a switch was made for continuous block mode to limited block mode. (QLSTCCBLB)

Binds for Remote

The number of SQL statements that were bound for remote access. (QLSTBRND)

Remote Coordinated Commits

The number of commit operations performed with the remote location as coordinator. (QLSTCPTR)

Remote Coordinated Rollbacks

The number of rollback operations performed with the remote location as coordinator. (QLSTRBTR)



Remote Coordinated Indoubts

The number of threads that became indoubt with the remote location as coordinator. (QLSTINDT)

Transactions Sent/Received

The number of transactions sent to or received from the remote site. (QLSTTRNS/QLSTTRNR)

Conversations Sent/Received

The number of conversations sent to or received from the remote site. (QLSTCNVS/QLSTCNVR)

Statements Sent/Received

The number of SQL statements sent to or received from the remote site. (QLSTSQLS/QLSTSQLR)


The number of commit requests sent to or received from the remote site. (QLSTCOMS/QLSTCOMR)

Aborts Sent/Received

The number of abort requests sent to or received from the remote site. (QLSTABRS/QLSTABRR)

Rows Sent/Received

The number of rows sent to or received from the remote site. (QLSTROWS/QLSTROWR)

Messages Sent/Received

The number of messages sent to or received from the remote site. (QLSTMSGS/QLSTMSGR)

Bytes Sent/Received

The number of bytes sent to or received from the remote site. (QLSTBYTS/QLSTBYTR)

Blocks Sent/Received

The number of blocks transmitted to or received from the remote site. (QLSTBTBF/QLACBRBF)

2-Phase Commits:

Prepares Sent/Received

The number of prepare requests sent to the participant, or received from the coordinator. Used only for 2-phase commit. (QLSTPRSE/QLSTPRRC)

Last Agents Sent/Received

The number of last agent requests sent to the coordinator, or received from the initiator. Used only for 2-phase commit. (QLSTLASE/QLSTLARC)


The number of committed requests sent to the participant, or received from the coordinator. Used only for 2-phase commit. (QLSTCRSE/QLSTCRRC)

Backouts Sent/Received

The number of backout requests sent to the participant, or received from the coordinator. Used only for 2-phase commit. (QLSTBKSE/QLSTBKRC)

Forgets Sent/Received

The number of forget requests sent to the coordinator, or received from the participant. Used only for 2-phase commit. (QLSTRRSE/QLSTRRRC)

CommitResps Sent/Received

The number of request commit responses sent to the coordinator, or received from the participant. Used only for 2-phase commit. (QLSTVYSE/QLSTVYRC)

BackoutResps Sent/Received

The number of backout responses sent to the coordinator, or received from the participant. Used only for 2-phase commit. (QLSTVNSE/QLSTVNRC)

Historical R


eports349

Distributed D

ata Facility (DD

F) Activity

Omegamon II for DB2 V540 Statistics DDF Activity Page 1Run Date=mm/dd/yyyy Grouped by DB2id Run Time=19:29:23 DB2id=A410------------------------------------------------------------------------------------------------------------------------------------Cold Start Connections = 0 Resync Connections Attempted = 0 Current Inactive DBAT’s = 2Warm Start Connections = 0 Resync Connections Failed = 0 Maximum Inactive DBAT’s = 5 Conversations Dealloc - ZPARM Reached = 1 Current Active DBAT’s = 1 DBAT’s Queued - ZPARM Reached = 0 Maximum Active DBAT’s = 5 Maximum DBAT’s = 10 Remote Location = B310 Conversations Queued = 0 Message Buffer Rows = 17 Remote Coordinated Commits = 0 Block Mode Switches = 0 Remote Coordinated Rollbacks = 0 Binds for Remote = 0 Remote Coordinated Indoubts = 0 Transactions Conversations Statements Commits Aborts Rows Messages Bytes Blocks ------------ ------------- ---------- ----------- ---------- ---------- ---------- ------------ ------------ SENT 1 1 2 1 0 0 3 1497 0 RECEIVED 0 0 0 0 0 17 3 5258 1 2-PHASE COMMIT: Prepares Last Agents Commits Backouts Forgets CommitResps BackoutResps ---------- ----------- ---------- ---------- ---------- ------------ ------------ SENT 0 0 0 0 0 0 0 RECEIVED 0 0 0 0 0 0 0 Remote Location = DRDA REMOTE LOCS Conversations Queued = 0 Message Buffer Rows = 34 Remote Coordinated Commits = 0 Block Mode Switches = 0 Remote Coordinated Rollbacks = 0 Binds for Remote = 0 Remote Coordinated Indoubts = 0 Transactions Conversations Statements Commits Aborts Rows Messages Bytes Blocks ------------ ------------- ---------- ----------- ---------- ---------- ---------- ------------ ------------ SENT 0 0 0 0 0 0 2 164 0 RECEIVED 1 1 0 1 0 34 2 149 0 2-PHASE COMMIT: Prepares Last Agents Commits Backouts Forgets CommitResps BackoutResps ---------- ----------- ---------- ---------- ---------- ------------ ------------ SENT 0 0 0 0 0 0 0 RECEIVED 0 0 0 0 0 0 0

FIGURE 63. Statistics Distributed Activity Report

Open/Close Activity


Open/Close Activity

IntroductionThis report displays statistics about database open and close activity, such as the number of opens and closes of datasets, and deferred close activity.

Default DDnameO2RSOCA

Default TitleStatistics Open/Close Activity






Open/Close Activity

Data Elements







Open Datasets The number of datasets open at the time the statistics record was written by DB2. This is a snapshot value. (QTDSOPN)

Not-in-use Datasets

The number of open pagesets that are not in use which are not physically closed. (QTSLWDD)

Not-in-use DS Accessed

The number of times that a physical open was not required due to deferred close. (QTREOPN)

DS Converted to Read-Only

Number of infrequently updated datasets converted from a read-write to a read-only state (pseudo-close). The SYSLGRNG entry is closed at this time. (QTPCCT)

Max Open Datasets

The maximum number of datasets open concurrently at any given time. (QTMAXDS)

Max Not-in-use Datasets

The maximum number of pagesets that were not in use but not physically closed. (QTMAXPB)

Not-in-use DS Closed

Number of not-in-use datasets that were closed because the total number of open datasets reached the deferred close threshold. The deferred close threshold value is based on the smaller of the value of DSMAX or the MVS DD limit. (Formerly called DS Closed via Drain in Version 260.) (QTDSDRN)

Open/C

lose Activity

352O

ME

GA

MO

N II for D

B2 H


uide, Version 540

FIG

UR

E 64.

Statistics O

pen

/Clo

se Activity R

epo

rt

Omegamon II for DB2 V540 Statistics Open/Close Activity Page 1Run Date=mm/dd/yyyy Grouped by None Run Time=10:28:34 Sysid=SYSG, DB2id=D31A, Date=mm/dd/yyyy, Time=07:46------------------------------------------------------------------------------------------------------------------------------------Open Datasets = 46 Not-in-use Datasets = 46 Not-in-use DS Accessed = 217 DS Converted to Read-Only = 0Max Open Datasets = 46 Max Not-in-use Datasets = 46 Not-in-use DS Closed = 0 Sysid=SYSG, DB2id=D31A, Date=mm/dd/yyyy, Time=08:15------------------------------------------------------------------------------------------------------------------------------------Open Datasets = 46 Not-in-use Datasets = 46 Not-in-use DS Accessed = 29 DS Converted to Read-Only = 26Max Open Datasets = 46 Max Not-in-use Datasets = 46 Not-in-use DS Closed = 0 Sysid=SYSG, DB2id=D31A, Date=mm/dd/yyyy, Time=08:26------------------------------------------------------------------------------------------------------------------------------------Open Datasets = 46 Not-in-use Datasets = 46 Not-in-use DS Accessed = 16 DS Converted to Read-Only = 0Max Open Datasets = 46 Max Not-in-use Datasets = 46 Not-in-use DS Closed = 0 Sysid=SYSG, DB2id=D31A, Date=mm/dd/yyyy, Time=08:45------------------------------------------------------------------------------------------------------------------------------------Open Datasets = 46 Not-in-use Datasets = 46 Not-in-use DS Accessed = 31 DS Converted to Read-Only = 0Max Open Datasets = 46 Max Not-in-use Datasets = 46 Not-in-use DS Closed = 0 Sysid=SYSG, DB2id=D31A, Date=mm/dd/yyyy, Time=09:15------------------------------------------------------------------------------------------------------------------------------------Open Datasets = 46 Not-in-use Datasets = 46 Not-in-use DS Accessed = 0 DS Converted to Read-Only = 0Max Open Datasets = 46 Max Not-in-use Datasets = 46 Not-in-use DS Closed = 0

Historical Reporter Audit Reports 353

Historical ReporterAudit Reports

IntroductionAudit reports contain data collected from DB2 audit trace records. The information in these reports is useful to DB2 system administrators, security administrators, and EDP auditors.

Chapter ContentsAuthorization Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354Authorization Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357Audited DDL (Data Definition Language) Access . . . . . . . . . . . . . . . . . . . . . . . . . . . 360Audited DML (Data Manipulation Language) Access . . . . . . . . . . . . . . . . . . . . . . . . 363DML (Data Manipulation Language) Statements at Bind . . . . . . . . . . . . . . . . . . . . . 366Authorization ID Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369Utility Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372Audit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

14

Authorization Failures



IntroductionThis report displays DB2 authorization failures per thread. This report identifies each user who attempted to access a DB2 object and failed due to lack of authorization. The information displayed can help auditors determine whether the authorization failures were due to multiple users' attempts to access the object(s) or were due to attempts by a single user.

Default DDnameO2RUCL1

Default TitleAuthorization Failures


Group By ElementsNone

Order By ElementsDB2ID, TIME, PLANNAME, CONNID, CORRID, SYSID, GROUP, MEMBER

Select ElementsDB2ID, PLANNAME, CONNID, CORRID, SYSID, GROUP, MEMBER

Data Elements

Timestamp The date and time at which the operation took place. (QWHSSTCK)

Sysid The MVS system ID. (ZWHMVSID)




Planname The name of the plan executed. (QWHCPLAN)




Corrid The correlation identifier. Actual values depend upon the type of connection. (QWHCCV)


Original Authid The original authorization ID passed from an external security facility such as RACF. If no security is used, this field is not applicable. (QWHCOPID)

Authid Checked The authorization ID passed to DB2 from other subsystems. (QW0140UR)

Object Type The type of object the DB2 program or command is executing against. (ZW0140OB)

Privilege The type of action attempted against DB2, such as a command, SQL call, or utility. (ZW0140PR)

Source Creator The name of the source table creator. (QW0140SC)

Source Table The name of the table involved in the DB2 operation. (QW0140SN)

Target Creator The name of the target table creator. (QW0140TC)

Target Table The name of the table involved in the DB2 operation. A value is displayed for this field only when the operation involves more than one table. (QW0140TN)

SQL TEXT The SQL statement the process has issued. (QW0140TX)




Batch job JES job name.

CICS External security signon ID, operator ID, terminal ID, system authorization ID, or a constant (character string).

IMS Signon ID or IMS logical terminal ID.

TSO TSO ID.


356O

ME

GA

MO

N II for D

B2 H


uide, Version 540

FIG

UR

E 65.

Au

tho

rization

Failu

res Rep

ort

Omegamon II for DB2 V540 Authorization Failures Page 1Run Date=mm/dd/yyy Run Time=12:57:13 Timestamp=1995-04-24-11.13.51.838455Sysid=SYSG, DB2id=D31A, Planname=DSNESPCS, Connid=TSO, Corrid=STO210B, Authid=STO210B, Original Authid=STO210B------------------------------------------------------------------------------------------------------------------------------------Authid Checked = STO210B Object Type = TBL/VIEW Privilege = SELECTSource Creator = UKSHIP Source Table = ACCOUNT_MANAGERS Target Creator = Target Table =SQL TEXT = SELECT * FROM UKSHIP.ACCOUNT_MANAGERS Timestamp=1995-04-24-11.14.41.241673Sysid=SYSG, DB2id=D31A, Planname=DSNESPCS, Connid=TSO, Corrid=STO210B, Authid=STO210B, Original Authid=STO210B------------------------------------------------------------------------------------------------------------------------------------Authid Checked = STO210B Object Type = USERAUTH Privilege = SYSADMSource Creator = Source Table = Target Creator = STO210B Target Table =SQL TEXT = GRANT SYSADM TO JWAYG


Authorization Control


IntroductionThis report displays information about users who have been granted access to DB2 objects and about users whose authorization to access DB2 objects, has been revoked.

In order to access a DB2 object, the user must be granted authority by the creator or someone who has the GRANT privilege. The user's access authority could be revoked when the user transfers to another department or terminates employment, or when the object moves from a test DB2 subsystem to a production DB2 subsystem.

This report provides an audit trail of GRANT and REVOKE statements per user. The report information shows who has granted or revoked authority to others.


Default TitleAuthorization Control



Order By ElementsDB2ID, TIME, PLANNAME, CONNID, CORRID, AUTHID, ORIGINAL_AUTHID, SYSID, GROUP, MEMBER

Select ElementsDB2ID, DATE, PLANNAME, CONNID, CORRID, AUTHID, ORIGINAL_AUTHID, SYSID, GROUP, MEMBER



Data Elements









Authid The primary authorization identifier. Actual values depend on the specific DB2 installation connection type. (QWHCAID)

Original Authid The original authorization identifier passed from an external security facility such as RACF. If no security is used, this field is not applicable. (QWHCOPID)

Revoker/Grantor The user who revokes or grants another user's DB2 object authorization. (QW0141OR)

Request Type The type of authorization control request. Possible values are G (Grant) or R (Revoke). (QW0141AC)

Object The type of object that the DB2 program or command is executing against. (ZW0141OB)

Reason Granted The reason authorization to execute a command has been granted. (ZW0141RE)

Return Code The code returned by DB2 to give the status of the SQL grant or revoke call. Values range from 0 to 99. Refer to the appropriate DB2 messages and code documentation for more information. (QW0141CO)

SQL TEXT The SQL statement that performs the revoke or grant. (QW0141TX)




Historical R

eporter Audit R

eports359

Authorization C

ontrol

OMEGAMON II for DB2 V540 Authorization Control Page 1Run Date=mm/dd/yyy Grouped by None Run Time=12:55:50 Timestamp=1992-07-13-17.49.23.286937Sysid=SYSG, DB2id=D22A, Planname=DSNESPRR, Connid=TSO, Corrid=USER06, Authid=USER06, Original Authid=USER06------------------------------------------------------------------------------------------------------------------------------------Revoker/Grantor = USER06 Request Type = REVOKE Object = TBL/VIEW Reason Granted = UNKNOWN Return Code = -556SQL TEXT = REVOKE SELECT ON TABLE CANDLE.H2STATS FROM USER06B Timestamp=1992-07-13-17.50.50.421756Sysid=SYSG, DB2id=D22A, Planname=DSNESPRR, Connid=TSO, Corrid=USER06, Authid=USER06, Original Authid=USER06------------------------------------------------------------------------------------------------------------------------------------Revoker/Grantor = USER06 Request Type = GRANT Object = TBL/VIEW Reason Granted = SYSADM Return Code = 0SQL TEXT = GRANT SELECT ON TABLE CANDLE.H2STATS TO USER06B Timestamp=1992-07-13-17.50.50.452931Sysid=SYSG, DB2id=D22A, Planname=DSNESPRR, Connid=TSO, Corrid=USER06, Authid=USER06, Original Authid=USER06------------------------------------------------------------------------------------------------------------------------------------Revoker/Grantor = USER06 Request Type = GRANT Object = TBL/VIEW Reason Granted = SYSADM Return Code = 0SQL TEXT = GRANT UPDATE ON TABLE CANDLE.H2STATS TO USER06B Timestamp=1992-07-13-17.52.13.788854Sysid=SYSG, DB2id=D22A, Planname=DSNESPRR, Connid=TSO, Corrid=USER06, Authid=USER06, Original Authid=USER06------------------------------------------------------------------------------------------------------------------------------------Revoker/Grantor = USER06 Request Type = REVOKE Object = UNKNOWN Reason Granted = UNKNOWN Return Code = 0SQL TEXT = REVOKE SYSADM FROM USER06B Timestamp=1992-07-13-17.52.14.023502Sysid=SYSG, DB2id=D22A, Planname=DSNESPRR, Connid=TSO, Corrid=USER06, Authid=USER06, Original Authid=USER06------------------------------------------------------------------------------------------------------------------------------------Revoker/Grantor = USER06 Request Type = REVOKE Object = TBL/VIEW Reason Granted = UNKNOWN Return Code = 0SQL TEXT = REVOKE SELECT ON TABLE CANDLE.H2STATS FROM USER06B

FIGURE 66. Authorization Control Report

Audited DDL (Data Definition Language) Access



IntroductionThis report displays information about DB2 tables that have been created, altered, or dropped. The report includes only those tables marked as auditable.

This report is used to identify tables whose statuses have changed, and who changed them. The report information provides an audit trail, by user, of tables whose statuses have changed as a result of any Data Definition Language (DDL) statement.


Default TitleAudited DDL Access

Data SourceIFCID 142. You must also supply IFCID 105 and 107 record data if you want to convert databases and pageset IDs to names.



Select ElementsDB2ID, DATE, PLANNAME, CONNID, CORRID, AUTHID, ORIGINAL_AUTHID, SYSID, GROUP, MEMBER

Data Elements


Sysid The MVS system ID. This field is blank if the data is extracted from a GTF dataset. (ZWHMVSID)








Corrid The correlation identifier. Actual values depend on the type of connection. (QWHCCV)



Operation The type of DDL statement. (ZW0142AC)

Owner The owner of the table. (QW0142OW)

Creator The creator of the table. (QW0142CR)

Database The name of the database involved in the DDL statement. This field contains blanks if IFCID 105 and 107 record data is not provided. (ZW0142DB)

Table The name of the table involved in the DDL statement. (QW0142TN)

OBID The internal IBM representation of the object for which DDL was performed. (QW0142OB)

SQL TEXT The DDL SQL statement. (QW0142TX)




Audited D

DL

(Data D

efinition Language) A

ccess

362O

ME

GA

MO

N II for D

B2 H


uide, Version 540

OMEGAMON II for DB2 V540 Audited DDL Access Page 1Run Date=mm/dd/yyy Grouped by None Run Time=12:56:43 Timestamp=1992-07-13-18.22.43.809060Sysid=SYSG, DB2id=D22A, Planname=DSNESPRR, Connid=TSO, Corrid=USER06, Authid=USER06, Original Authid=USER06------------------------------------------------------------------------------------------------------------------------------------Operation = CREATE Owner = USER06 Creator = USER06 Database = PAVDBASE Table = PAVTBLA OBID = 3SQL TEXT = CREATE TABLE PAVTBLA (A INTEGER,B INTEGER,C INTEGER) AUDIT ALL IN PAVDBASE.PAVTS Timestamp=1992-07-13-18.23.00.929205Sysid=SYSG, DB2id=D22A, Planname=DSNESPRR, Connid=TSO, Corrid=USER06, Authid=USER06, Original Authid=USER06------------------------------------------------------------------------------------------------------------------------------------Operation = CREATE Owner = USER06 Creator = USER06 Database = PAVDBASE Table = PAVTBLB OBID = 6SQL TEXT = CREATE TABLE PAVTBLB (A INTEGER,B INTEGER,C INTEGER) AUDIT ALL IN PAVDBASE.PAVTS Timestamp=1992-07-13-18.23.49.019843Sysid=SYSG, DB2id=D22A, Planname=DSNESPRR, Connid=TSO, Corrid=USER06, Authid=USER06, Original Authid=USER06------------------------------------------------------------------------------------------------------------------------------------Operation = DROP Owner = USER06 Creator = USER06 Database = PAVDBASE Table = PAVTBLB OBID = 6SQL TEXT = DROP TABLE PAVTBLB Timestamp=1992-07-13-18.24.05.916127Sysid=SYSG, DB2id=D22A, Planname=DSNESPRR, Connid=TSO, Corrid=USER06, Authid=USER06, Original Authid=USER06------------------------------------------------------------------------------------------------------------------------------------Operation = ALTER Owner = CANDLE Creator = USER06 Database = H2DBASE Table = H2ACCT OBID = 11SQL TEXT = ALTER TABLE CANDLE.H2ACCT AUDIT NONE Timestamp=1992-07-13-18.24.30.724430Sysid=SYSG, DB2id=D22A, Planname=DSNESPRR, Connid=TSO, Corrid=USER06, Authid=USER06, Original Authid=USER06------------------------------------------------------------------------------------------------------------------------------------Operation = ALTER Owner = CANDLE Creator = USER06 Database = H2DBASE Table = H2ACCT OBID = 11SQL TEXT = ALTER TABLE CANDLE.H2ACCT AUDIT ALL

FIGURE 67. Audited DDL Access Report


Audited DML (Data Manipulation Language) Access


IntroductionThis report displays information about a table that has been read and/or changed within a unit of recovery for the first time.

A unit of recovery defines all the work done on behalf of a user or transaction before a commit is made. Once committed, all changes to the table will become permanent. This will affect only those tables marked as auditable. A table is defined to be auditable either during table creation or by altering the table attribute.

This report shows, by user, the read and write activity of all tables within a unit of recovery. The report information provides an audit trail of tables that have been read or updated, as well as identifying the users of the tables.


Default TitleAudited DML Access




Select ElementsDB2ID, PLANNAME, CONNID, CORRID, AUTHID, ORIGINAL_AUTHID, SYSID, GROUP, MEMBER

Data Elements



DB2id The DB2 subsystem ID. (QWHSSSID)










Operation The type of DML access (READ or WRITE). (ZW0143OP)

URID The log relative byte address of the unit of recovery. This field contains zeros if the record is for read access. (QW0143UR)

Database The name of the database containing the auditable table. (ZW0143DB)

Pageset The name of the pageset containing the auditable table. (QW0143PS)

Table OBID The internal IBM representation of the table for which DML was performed. (QW0143OB)




Historical R

eporter Audit R

eports365

Audited D

ML

(Data M

anipulation Language) Access

OMEGAMON II for DB2 V540 Audited DML Access Page 1Run Date=mm/dd/yyy Grouped by None Run Time=12:57:20 Timestamp=1992-07-15-15.57.07.560077Sysid=SYSG, DB2id=D22A, Planname=DSNESPCS, Connid=TSO, Corrid=USER06, Authid=USER06, Original Authid=USER06------------------------------------------------------------------------------------------------------------------------------------Operation = READ URID = 000000000000 Database = H2DBASE Pageset = H2TSSTAT Table OBID = 3 Timestamp=1992-07-15-15.58.22.843424Sysid=SYSG, DB2id=D22A, Planname=DSNESPCS, Connid=TSO, Corrid=USER06, Authid=USER06, Original Authid=USER06------------------------------------------------------------------------------------------------------------------------------------Operation = READ URID = 000000000000 Database = H2DBASE Pageset = H2TSSTAT Table OBID = 3 Timestamp=1992-07-15-17.00.43.000521Sysid=SYSG, DB2id=D22A, Planname=DSNUTIL, Connid=UTILITY, Corrid=USER06AA, Authid=USER06, Original Authid=USER06------------------------------------------------------------------------------------------------------------------------------------Operation = READ URID = 0000450CC5D8 Database = H2DBASE Pageset = H2TSACCT Table OBID = 11 Timestamp=1992-07-15-17.00.58.795138Sysid=SYSG, DB2id=D22A, Planname=DSNUTIL, Connid=UTILITY, Corrid=USER06AA, Authid=USER06, Original Authid=USER06------------------------------------------------------------------------------------------------------------------------------------Operation = WRITE URID = 0000450CCECB Database = H2DBASE Pageset = H2TSACCT Table OBID = 11 Timestamp=1992-07-15-17.03.58.891425Sysid=SYSG, DB2id=D22A, Planname=DSNUTIL, Connid=UTILITY, Corrid=USER06AA, Authid=USER06, Original Authid=USER06------------------------------------------------------------------------------------------------------------------------------------Operation = READ URID = 0000450CEC66 Database = H2DBASE Pageset = H2TSACCT Table OBID = 11 Timestamp=1992-07-15-17.03.59.297288Sysid=SYSG, DB2id=D22A, Planname=DSNUTIL, Connid=UTILITY, Corrid=USER06AA, Authid=USER06, Original Authid=USER06------------------------------------------------------------------------------------------------------------------------------------Operation = WRITE URID = 0000450CEC66 Database = H2DBASE Pageset = H2TSACCT Table OBID = 11 Timestamp=1992-07-15-17.10.45.330608Sysid=SYSG, DB2id=D22A, Planname=DSNESPCS, Connid=TSO, Corrid=USER06, Authid=USER06, Original Authid=USER06------------------------------------------------------------------------------------------------------------------------------------Operation = READ URID = 000000000000 Database = H2DBASE Pageset = H2TSACCT Table OBID = 11

FIGURE 68. Audited DML Access

DML (Data Manipulation Language) Statements at Bind



IntroductionThis report displays the Data Manipulation Language (DML) statements that caused a bind to occur.

A bind takes the SQL statements from a program, formulates the access paths to the required resources, and stores the access paths in a plan. The DBRM is displayed when the bind that occurred was due to static SQL. The program name is displayed when the bind occurred due to dynamic SQL.

This report is used to monitor when and how often binds occur. The report information can reveal an excessive number of binds for static plans or can help to profile the dynamic SQL usage.


Default TitleDML Statements at Bind



Order By ElementsDB2ID, TIME, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, AUTHID, ORIGINAL_AUTHID, SYSID, GROUP, MEMBER

Select ElementsDB2ID, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, AUTHID, ORIGINAL_AUTHID, SYSID, GROUP, MEMBER

Data Elements



DB2id The DB2 subsystem ID. (QWHSSSID)








Authid The primary authorization identifier. Actual values depend on the specific DB2 installation the type of connection. (QWHCAID)


Program/DBRM The program or Database Request Module that performs the dynamic or static bind. (QW0145PN)

Statement Type The type of DML statement issued. (QW0145ST)

Statement # The number of the SQL statement within the plan. (QW0145SN)

Timestamp The hexadecimal dump of a program's DB2 timestamp at precompile time. (QW0145TS)

Return Code The SQL return code resulting from the bind process. Refer to the DB2 message and codes documentation for more information. (QW0145SC)

DBID/OBID List The list of objects referenced by this operation. (ZW0145DB)

Stmt Isolation The isolation level of the statement being bound. (QW0145IS)

Possible values are as follows:

SQL TEXT The SQL text associated with the bind process. (QW0145TX)




RR Repeatable read. (QW0145IS=QW0145RR)

CS Cursor stability. (QW0145IS=QW0145CS)

UR Uncommitted read. (QW0145IS=QW0145UR)

DM

L (D

ata Manipulation Language) S

tatements at B

ind

368O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 DML Statements at Bind Page 1Run Date=mm/dd/yyy Run Time=17:45:05 Timestamp=1995-04-24-17.20.42.194573Sysid=SYSG, DB2id=D41B, Planname=DSNESPCS, Connid=TSO, Corrid=STO210B, Authid=STO210B, Original Authid=STO210B------------------------------------------------------------------------------------------------------------------------------------Program/DBRM = DSNESM68 Statement Type = INSERT Statement # = 71 Timestamp = x'149EEA901A79FE48' Return Code = 0DBID/OBID List = 0004/008E Stmt Isolation = CSSQL TEXT = INSERT INTO TJMWBP0 SELECT * FROM DSN8230.EMP Timestamp=1995-04-24-17.34.37.670676Sysid=SYSG, DB2id=D41B, Planname=DSNESPCS, Connid=TSO, Corrid=STO210B, Authid=STO210B, Original Authid=STO210B------------------------------------------------------------------------------------------------------------------------------------Program/DBRM = DSNESM68 Statement Type = SEL-QUER Statement # = 71 Timestamp = x'149EEA901A79FE48' Return Code = 0DBID/OBID List = 0004/008E Stmt Isolation = URSQL TEXT = SELECT * FROM TJMWBP0 WHERE LASTNAME LIKE 'S%'

FIGURE 69. DML Statements at Bind Report


Authorization ID Changes


IntroductionThis report displays information about an authorization ID that has been changed for a thread. Authids can be changed by a SET CURRENT SQLID command, a CICS or IMS signon, or an IMS, CICS, or TSO IDENTIFY request.

This report is used to detect authorization failures when the authid is changed for a thread. The report information provides an audit trail of authid changes.


Default TitleAuthorization ID Changes

Data SourceIFCIDs 55, 83, 87, and 169




Data Elements













Operation The type of authorization ID change.� IDENTIFY (IFCID 83)� INBOUND (QW0169T4 = I)� OUTBOUND (QW0169TY = 0)� SETSQLID (IFCID 55)� SIGNON (IFCID 87)

Completion The result of the operation. (QW0055ST, QW0087AD, or QW0083AD)� FAIL � SUCCESS� EXITFAIL - failed; access denied by authorization exit� SECSFAIL - failed; access denied by security system� SYSADM - successful due to SYSADM authority

Original Authid The original authid set prior to IDENTIFY, SIGNON, or SET CURRENT SQLID processing. (QW0087OP, QW0083OP, QW0055OI, or QW0169AU)

New Authid The new authorization ID as changed by SET CURRENT SQLID request, or by authorization exit processing at IDENTIFY and SIGNON operations, or by communications database AUTHID translation if using distributed DB2 and the AUTHID translation function. (QW0087Q7, QW0083QDM QW0055NI, or QW0169NE)




Historical R

eporter Audit R

eports371

Authorization ID

Changes

OMEGAMON II for DB2 V540 Authorization ID Changes Page 1Run Date=mm/dd/yyy Grouped by None Run Time=12:58:44 Timestamp=1992-07-13-09.51.19.410427Sysid=SYSG, DB2id=D23A, Planname=*COMMAND, Connid=D23A, Corrid=D23A, Authid=SYSOPR, Original Authid=SYSOPR------------------------------------------------------------------------------------------------------------------------------------Operation = IDENTIFY Completion = SUCCESS Original Authid = TDO209B New Authid = TDO209B Timestamp=1992-07-13-17.39.03.436553Sysid=SYSG, DB2id=D23A, Planname=*COMMAND, Connid=D23A, Corrid=D23A, Authid=SYSOPR, Original Authid=SYSOPR------------------------------------------------------------------------------------------------------------------------------------Operation = IDENTIFY Completion = SUCCESS Original Authid = TDO206 New Authid = TDO206 Timestamp=1992-07-13-18.33.07.254023Sysid=SYSG, DB2id=D23A, Planname=KTE, Connid=DB2CALL, Corrid=TDDB16, Authid=TDDB16, Original Authid=TDDB16------------------------------------------------------------------------------------------------------------------------------------Operation = SETSQLID Completion = SYSADM Original Authid = TDDB16 New Authid = TDDB16A Timestamp=1992-07-13-18.37.28.386957Sysid=SYSG, DB2id=D23A, Planname=*COMMAND, Connid=D23A, Corrid=D23A, Authid=SYSOPR, Original Authid=SYSOPR------------------------------------------------------------------------------------------------------------------------------------Operation = IDENTIFY Completion = SUCCESS Original Authid = TDO206 New Authid = TDO206 Timestamp=1992-07-13-21.07.24.777827Sysid=SYSG, DB2id=D23A, Planname=KTE, Connid=DB2CALL, Corrid=TDDB16, Authid=TDDB16, Original Authid=TDDB16------------------------------------------------------------------------------------------------------------------------------------Operation = SETSQLID Completion = SUCCESS Original Authid = TDDB16A New Authid = TDDB16A Timestamp=1992-07-13-21.13.44.674262Sysid=SYSG, DB2id=D23A, Planname=KTE, Connid=DB2CALL, Corrid=TDDB16, Authid=TDDB16, Original Authid=TDDB16------------------------------------------------------------------------------------------------------------------------------------Operation = SETSQLID Completion = SYSADM Original Authid = TDDB16 New Authid = TDDB16A Timestamp=1992-07-13-21.28.12.358114Sysid=SYSG, DB2id=D23A, Planname=DSNESPRR, Connid=TSO, Corrid=USER08, Authid=USER08A, Original Authid=USER08ANetwork ID=USCACO01, LU Name=O2D22GA, Unique ID=A43B5A5171DF, Requesting Location=D23B------------------------------------------------------------------------------------------------------------------------------------Operation = INBOUND Completion = Original Authid = USER08A New Authid = USER08A Resp Loc = D23B

FIGURE 70. Authorization ID Changes Report

Utility Access


Utility Access

Introduction This report displays information about the DB2 objects that are affected by DB2 utility jobs.

This report is used to monitor the occurrence of utility jobs. The report information shows when each utility job was executed and what DB2 objects it affected.


Default TitleUtility Access

Data SourceIFCID 23, 24, 25. IFCIDs 105 and 107 are required to convert database pageset IDs to names.


Order By ElementsDB2ID, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, AUTHID, ORIGINAL_AUTHID, SYSID, GROUP, MEMBER

Select ElementsDB2ID, DATE, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, AUTHID, ORIGINAL_AUTHID, SYSID, GROUP, MEMBER


Utility Access

Data Elements







Authid The primary authorization identifier. (QWHCAID)


Utility The name of the utility currently executing. (QW0023NM, QWOO24NM, or QW0025NM)

Phase The utility phase ID, representing one of the several steps a utility job normally goes through before completion. (QW0023PH, QW00024PH, OR QW0025PH)

ID The user-specified ID of the utility being run. (QW0023ID, QW0024ID, or QW25ID)

# Processed The number of pages, records, or objects processed during the phase. (QW0023DN, QW0024DN, or QW0025DN)

Database The name of the database the utility is running against. (ZW0023DB, ZW0024DB, or ZW0025DB)

If IFCID 105 and 107 record data is not available then this data is the internal ID of the database the utility is running against. (QW0023DB, QW0024DB, or QW0025DB)

Pageset The name of the pageset the utility is running against. (ZW0023OB, ZW0024OB, or ZW0025OB). If IFCID 105 and 107 record data is not available then this data is the internal DB2 ID of the pageset the utility is running against. (QW0023OB, QW0024OB, or QW0025OB)




Utility A

ccess

374O

ME

GA

MO

N II for D

B2 H


uide, Version 540

OMEGAMON II for DB2 V540 Utility Access Page 1Run Date=mm/dd/yyy?? Grouped by None Run Time=13:00:10 Timestamp=1992-07-13-18.14.09.897336Sysid=SYSG, DB2id=D23A, Planname=DSNUTIL, Connid=UTILITY, Corrid=USER06CC, Authid=USER06B, Original Authid=USER06B-------------------------------------------------------------------------------------------------Utility = STOSPACE Phase = UTILINIT ID = TEMP3 # Processed = 0 Timestamp=1992-07-13-18.14.09.969306Sysid=SYSG, DB2id=D23A, Planname=DSNUTIL, Connid=UTILITY, Corrid=USER06CC, Authid=USER06B, Original Authid=USER06B-------------------------------------------------------------------------------------------------Utility = STOSPACE Phase = STOSPACE ID = TEMP3 # Processed = 0 Timestamp=1992-07-13-18.15.34.630353Sysid=SYSG, DB2id=D23A, Planname=DSNUTIL, Connid=UTILITY, Corrid=USER06CC, Authid=USER06B, Original Authid=USER06B-------------------------------------------------------------------------------------------------Utility = STOSPACE Phase = UTILTERM ID = TEMP3 # Processed = 62 Timestamp=1992-07-15-17.00.42.347818Sysid=SYSG, DB2id=D23A, Planname=DSNUTIL, Connid=UTILITY, Corrid=USER06AA, Authid=USER06, Original Authid=USER06-------------------------------------------------------------------------------------------------Utility = LOAD Phase = UTILINIT ID = LOAD1 # Processed = 0 Timestamp=1992-07-15-17.00.58.112874Sysid=SYSG, DB2id=D23A, Planname=DSNUTIL, Connid=UTILITY, Corrid=USER06AA, Authid=USER06, Original Authid=USER06-------------------------------------------------------------------------------------------------Utility = LOAD Phase = RELOAD ID = LOAD1 # Processed = 0 Database = H2DBASE Pageset = H2TSACCT Timestamp=1992-07-15-17.02.45.080932Sysid=SYSG, DB2id=D23A, Planname=DSNUTIL, Connid=UTILITY, Corrid=USER06AA, Authid=USER06, Original Authid=USER06------------------------------------------------------------------------------------------------Utility = LOAD Phase = SORT ID = LOAD1 # Processed = 4926 Database = H2DBASE Pageset = H2TSACCT Timestamp=1992-07-15-17.02.52.155326Sysid=SYSG, DB2id=D23A, Planname=DSNUTIL, Connid=UTILITY, Corrid=USER06AA, Authid=USER06, Original Authid=USER06-------------------------------------------------------------------------------------------------Utility = LOAD Phase = BUILD ID = LOAD1 # Processed = 4709 Database = H2DBASE Pageset = H2TSACCT

FIGURE 71. Utility Access Report


Audit Summary

Audit Summary

IntroductionThis report displays, for each user, information such as the number of authorization failures, count of Data Definition Language (DDL) and Data Manipulation Language (DML) SQL statements executed, and utility access.

Use this report to check whether certain counts are higher than normal. The information displayed can indicate a potential problem. If any of the counts are too high, you may want to examine the appropriate audit detail reports.

Since this report is always grouped by AUTHID and ORIGAUTHID, these elements are not valid groupby or orderby specifications for the Audit Summary report.

Default DDnameO2RUSUM

Default TitleAudit Summary

Data Source23-25, 55, 83, 87, 169, 140-145

Group By ElementsPLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, DB2ID, HOUR, DAY, SYSID, GROUP, MEMBER



Audit Summary


Data Elements

Start Date The beginning date for the period covered by this entry. (ZWHSDATE)

Hour The hour of the period covered by this entry. (ZWHSHOUR)





Authid The primary authorization identifier. Actual values depend upon the specific DB2 installation and the type of connection. (QWHCAID)

OrigAuth The original authorization ID passed from an external security facility such as RACF. If no security is used, this field is not applicable. (QWHCOPID)

Auth Failures The number of authorization failures.

Auth Control The number of Grant and Revoke statements.

DDL Access The number of Data Definition Language SQL statements executed.

DML Access The number of Data Manipulation Language SQL statements executed.

DML at Bind The number of Data Manipulation Language SQL statements executed that caused a bind to occur.

Authid Change The number of Authid changes made.

Utility Access The number of utility jobs executed.

Historical R

eporter Audit R

eports377

Audit S

umm

ary

OMEGAMON II for DB2 V540 Audit Summary Page 1Run Date=mm/dd/yyy Grouped by Hour, PlanName Run Time=13:06:21 Start Date=mm/dd/yyy, Hour=17Sysid=SYSG, Planname=DEFAULT----------------------------------------------------------------------------------------------------------------------------------Authid OrigAuth Auth Failures Auth Control DDL Access DML Access DML at Bind Authid Change Utility Access-------- -------- ------------- ------------- ------------- ------------- ------------- ------------- --------------USER09 USER09 581 0 0 0 0 0 0 ------------- ------------- ------------- ------------- ------------- ------------- -------------- 581 0 0 0 0 0 0 Start Date=mm/dd/yyy, Hour=17Sysid=SYSG, Planname=DSBIND----------------------------------------------------------------------------------------------------------------------------------Authid OrigAuth Auth Failures Auth Control DDL Access DML Access DML at Bind Authid Change Utility Access-------- -------- ------------- ------------- ------------- ------------- ------------- ------------- --------------USER06 USER06 0 0 0 0 14 0 0 ------------- ------------- ------------- ------------- ------------- ------------- -------------- 0 0 0 0 14 0 0 Start Date=mm/dd/yyy, Hour=17Sysid=SYSG, Planname=DSNESPRR----------------------------------------------------------------------------------------------------------------------------------Authid OrigAuth Auth Failures Auth Control DDL Access DML Access DML at Bind Authid Change Utility Access-------- -------- ------------- ------------- ------------- ------------- ------------- ------------- --------------USER06 USER06 0 6 0 2 1 0 0USER06B USER06B 0 0 0 1 0 0 0 ------------- ------------- ------------- ------------- ------------- ------------- -------------- 0 6 0 3 1 0 0 Start Date=mm/dd/yyy, Hour=18Sysid=SYSG, Planname=*COMMAND----------------------------------------------------------------------------------------------------------------------------------Authid OrigAuth Auth Failures Auth Control DDL Access DML Access DML at Bind Authid Change Utility Access-------- -------- ------------- ------------- ------------- ------------- ------------- ------------- --------------SYSOPR SYSOPR 0 0 0 0 0 73 0 ------------- ------------- ------------- ------------- ------------- ------------- -------------- 0 0 0 0 0 73 0

FIGURE 72. Audit Summary Report

Audit Summary


Historical Reporter DSNZPARM Reports 379

Historical ReporterDSNZPARM Reports

IntroductionThis chapter describes the DSNZPARM Reports.

Chapter ContentsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380System Installation Parameters (DSNZPARM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381

15

Overview


Overview

IntroductionThe DSNZPARM report displays the current settings of the DB2 installation (configuration) parameters for a particular DB2 subsystem.




IntroductionThis report displays the DB2 installation parameters defined in the DSNZPARM module. These parameters are set at installation time to establish execution time values for the DB2 subsystem, such as pool sizes, logging and locking parameters, maximum batch/online threads, authorization settings, naming conventions, and usage of trace functions. In addition to the value of each parameter, this report displays the initialization macro and parameter name as used in DSNZPARM.

Since this report presents the state of DSNZPARM parameters at a specified time (DB2 initialization time), it does not necessarily apply to the entire specified time interval. If any DSNZPARM parameter has changed during the course of the specified time interval, multiple reports are produced. Each report (two pages in length) displays one complete set of DSNZPARM parameters that were used for DB2 initialization.

This report is used to provide the user with a detailed list of the current DSNZPARM parameter values, or the DSNZPARM parameter values at the selected time. The report shows you when the parameters values have changed.

Default DDname O2RZPRM

Default TitleSystem Installation Parameters


Group By ElementsNot applicable

Order By ElementsNot applicable

Select ElementsDB2ID, SYSID, GROUP, MEMBER



Data Elements

Title Line:

DB2ID The DB2 subsystem name.

Assembled The date on which this module was assembled. (QWP4DATE)

Group The name of the data sharing group. Applies only to DB2 Version 4 and above. (QWHADSGN)

Member The member name within a data sharing group. Applies only to DB2 Version 4 and above. (QWHAMEMN)

In use DB2 timestamp of the statistics record. (QWHSSTCK)

Thread Parameters:

Maximum Concurrent Threads

The maximum number of concurrent allied threads (DBATs), including inactive threads. (QWP1CT)

Maximum TSO Users

The maximum number of foreground (TSO) threads. (QWP1IDF)

Maximum Batch Connections

The maximum number of background (TSO batch) threads. (QWP1IDB)

Maximum Connected DBATs

The total number of active and inactive database access threads that can be connected to DB2 concurrently. (QWP1RMT)

Logging Parameters:

Logging Mode Indicates whether dual active logs are being used. (ZWP2DUAL)

Maximum Input Tape Units

Maximum number of tape units that can be allocated to read archive log tape volumes concurrently. (QWP2MRTU)

Deallocate Time Time before an unused archive tape volume will be deallocated. Time specified may be in (minutes,seconds) or NOLIMIT. When the time is set to (1440,00), NOLIMIT will be displayed. (QWP2DMIN,QWP2DSEC)

Output Buffer The size of the archive log output buffer. (QWP2OBPS)

Input Buffer The size of the archive log input buffer. (QWP2IBPS)

Write Threshold The log write threshold. (QWP2WRTH)

Checkpoint Frequency

The checkpoint frequency for records. (QWP1LOGL)

Archiving Parameters

Archiving Mode Indicates whether dual archive logs are being used. (ZWP2ADL)

Volumes in BSDS

The number of log archive volume entries that can be contained in the BSDS. (QWP2ARCL)



Catalog Volumes The high-level qualifier of catalog/directory datasets. (CATALOG)

RACF Protect Indicates whether archive log datasets are to be RACF-protected. (PROTECT)

Mount WTOR Indicates whether the operator receives messages regarding archive log tape mount requests. (ZWP3WTOR)

Device Type 1 The device type or unit name to be allocated for storing the first copy of the archive log datasets. Applies only to DB2 Version 4 and above. (QWP3UNT1)

Device Type 2 The device type or the unit name to be allocated for storing the second copy of the archive log datasets. If dual archive mode is in use and this parameter is not specified, both archive copies will use the Device Type 1 unit parameter. Applies only to DB2 Version 4 and above. (QWP3UNT2)

Space Allocation Unit

The allocation size parameters for archive log datasets. (ZWP3CLTK)

Primary Space Allocation

The primary space allocation for archive log datasets. (QWP3RISP)

Secondary Space Allocation

The secondary space allocation for archive log datasets. (QWP3SECS)

Blocksize The block size for archive log datasets. (QWP3BKSZ)

Retention The retention period for archive logs. (QWP3RETN)

Mass Storage Volume Group 1

The MSS group name for allocation of archive log datasets. (QWP3MVS1)

Mass Storage Volume Group 2

The MSS group name for allocation of a second copy of the archive log datasets. (QWP3MVS2)

Archive Log 1 DSN Prefix

The MSS group name for allocation of archive log datasets. (QWP3REF1)

Archive Log 2 DSN Prefix

The MSS group name for allocation of a second copy of archive log datasets. (QWP3REF2)

Compact Data Indicates whether data written to logs should be compacted. (QWP3COMP)

Max Quiesce Time

The maximum amount of time DB2 will wait for a systemwide quiesce point for ARCHIVE LOG MODE(QUIESCE) command. (QWP3MQP)

Timestamp in Name

Indicates whether the timestamp is to be placed in the archive log dataset name. (QWP3DTM)

Authorization Parameters

Authorization Checking

Indicates whether DB2 authorization checking is active. (QWP4AUTH)

System Administrator 1

The authorization ID of the primary system administrator. (QWP4SADM)



System Administrator 2

The authorization ID of an alternate system administrator. (QWP4ADM2)

System Operator 1

The authorization ID of the primary system operator. (QWP4OPR1)

System Operator 2

The authorization ID of an alternate system operator. (QWP4OPR2)

Default ID The default authorization ID for unidentified DB2 users. (QWP4DFID)

Package Owner Authorization

For a non-DB2 requester executing a package at a DB2 server and using a three-part name to hop to a third site, YES specifies that the package owner will be the authority used, NO specifies that the ID that executes the package will be the authority used. This applies only to DB2 Version 3.

For DB2 Version 4, YES specifies that the ID used for static SQL is the package owner, and for dynamic SQL, it is the process runner. NO specifies that the authid of the process runner is used for all statements. (QWP4HOP)

Plan Authorization Cache Size

The size of the authorization cache that is used if CACHESIZE is not specified on the bind plan subcommand. If set to zero, no authorization cache is used. Applies only to DB2 Version 4 and above. (QWP4AUCA)

Bind New Package

The level of authority required when adding a new package or a new version of an existing package to a collection. Applies only to DB2 Version 4 and above. (QWP4BNVA)

Dataset and Database Parameters

Highlevel Dataset Qualifier

The high-level qualifier for catalog/directory datasets. (QWP6CATN)

Maximum Datasets Open

The maximum number of open datasets. (QWP4DSMX)

HSM Auto Recall Indicates whether HSM automatic recall is enabled. (QWP4HRCL)

Auto Recall Wait The maximum wait time for HSM automatic recall. (QWP4HRDC)

Checkpoints to Pseudo-Close

Number of consecutive checkpoints that a dataset or partition must go through since it was last updated before being selected for pseudo-close, that is, change state from read-write to read-only. (QWP1FREQ)

Elapsed Time to Pseudo-Close

Amount of time in minutes that must elapse since a dataset or partition was last updated before it can be selected for pseudo-close. (QWP1TMR)

Default Index Type

The default index type used if the TYPE option is omitted from a CREATE INDEX statement. Applies only to DB2 Version 4 and above. (QWP4DXTP)

Checkpoints to Level ID Update

Number of consecutive checkpoints between updates to the Level ID of a pageset or partition. Setting this parameter to zero disables down level detection. Applies only to DB2 Version 4 and above. (QWP1DFRQ)

Database Restart/Defer

The action to be taken on autostart list. (QWP7STRT)



Restart/Defer List:

A list of databases or tablespaces to be automatically restarted or deferred. If all databases/tablespaces are to be restarted or deferred, this field will display All. (ZQWP8DBSP)

IRLM Parameters:

IRLM Catalogued Procedure

The name of the IRLM catalogued procedure or started task. (QWP4IPRC)

IRLM Subsystem Name

The IRLM subsystem ID. (QWP4ISID)

Auto Start IRLM Indicates whether to start IRLM automatically. (QWP4IAU)

Auto Start Wait The autostart wait time. (QWP4ISWT)

Timeout Interval The timeout interval or maximum lock wait time. (QWP4OUT)

Utility Timeout Number of resource timeout intervals that a utility will wait for a lock or for claims to be released. (QWP4UTO)

Maximum Locks Per Tablespace

The maximum number of locks per tablespace. (QWP4LKTS)

Maximum Locks Per User

The maximum number of locks per user or application. (QWP4KLUS)

U Lock for Repeatable Read

Specifies whether repeatable read cursors will use page level update (U) locks, instead of S locks to access a table, returning to S locks as the cursor moves to the next page. Applies only to DB2 Version 4 and above. (QWP4RRU)

Pool Sizes:

EDM Pool The size of the EDM pool. (QWP4EDPL)

Sort Pool The size in K bytes of the sort pool. (QWP4SPOL)

RID Pool The maximum size in K bytes of the RID pool. If set to zero, access path selections that require the RID pool will not be used, including list prefetch and hybrid joins. (QWP4RMAX)

Minimum RID Lists

The least number of RID lists allowed for a RID map. (QWP4RMIN)

Governor (RLF) Parameters:

Auto Start Indicates whether the resource limit facility is started automatically at DB2 initialization. (QWP1RLFR)

Authorization ID The authorization ID of the RLF table administrator. (QWP1RLFA)

Table Suffix The suffix of the RLF table name used. (QWP1RLFT)

Action If Error The action taken if the governor encounters an error when accessing the RLF table, or when no entry is found in the table. (QWP1RLFR)

DDF Parameters:

DDF Start Option The DDF startup option selected. (QWP9STRT)



Action If RLST Error

The RLF option for distributed access threads, if there is no entry in the resource limit specification table (RLST). (QWP9RLER, QWP9RLFN)

Resynchronization Interval

Time interval in minutes during which indoubt logical units of work involving this DB2 subsystem and partner logical units are processed. (QWP9RYC)

Commit Status Status of a DDF thread after it commits or rolls back and holds no database locks or cursors. (QWP9CMST)

Idle Thread Timeout

The time in seconds that an active server thread is allowed to remain dormant before it is cancelled. A value of zero disables timeout for server threads. This does not apply to inactive or indoubt threads. Applies only to DB2 Version 4 and above. (QWP9TTO)

Trace Parameters:

Global Trace Classes

The global traces that should be started automatically at DB2 initialization. (QWP1TRST)

Statistics Trace Classes

The classes of statistics traces that should be included in automatic trace startup. (QWP1SMFS)

Accounting Trace Classes

The classes of accounting traces that should be included in automatic trace startup. (QPR1SMFA)

Audit Trace Classes

The classes of audit traces that should be included in automatic trace startup. (QPR1AUDT)

Monitor Trace Classes

The classes of monitor traces that should be included in automatic trace startup. (QWP1MON)

Trace Table Size The size of the in-core trace table. (QWP1TRSZ)

Statistics Interval Time

The statistics time interval for which the data in this row has been collected. (QWP1STIM)

Monitor Buffer Size

The size of the memory buffer space to be used by active monitor traces. (QWP1MONS)

DDCS Parameters:

Active DD Control

Indicates whether the DDL registration is to be activated. (QWP4SIT)

Control All Applications

Indicates whether to allow only registered applications. (QWP4REGD)

Require Full Names

Indicates whether full name qualification is required. (QWP4REGQ)

Unregistered Default

The action to be taken for unregistered applications. (QWP4REGU)

Registration Owner

Owner of Application Registration Table (ART) and Object Registration Table (ORT). (QWP4REGC)

Registration Database

The database containing ART and ORT. (QWP4REGN)



Appl Registration Table

The name of the ART. (QWP4REGA)

Object Registration Table

The name of the ORT. (QWP4EGO)

ART/ORT Escape Character

DDCS escape character for an ART or ORT search. This character is shown in both display and hexadecimal formats. (QWP4ESC)

Data Sharing Parameters: Data sharing parameters apply only to DB2 Version 4 and above.

Data Sharing Specifies whether or not DB2 data sharing is enabled. (QWPADSHR)

Group Name The name of the DB2 data sharing group. N/A is displayed if data sharing is not enabled. (QWPAGRPN)

Member Name The name of a member within the data sharing group. N/A is displayed if data sharing is not enabled. (QWPAMBRN)

Stored Procedure Parameters: Stored procedures parameters apply only to DB2 Version 4 and above.

MVS Procedure Name

The name of the MVS JCL procedure used to start the DB2 stored procedures address space. (QWP1SPPN)

Max Abends The number of times a stored procedure is allowed to terminate abnormally. (QWP1SPAB)

Timeout Value The number of seconds to wait for an SQL CALL statement to be assigned for execution in the DB2 stored procedures address space. A value of zero disables timeout for SQL CALL statements. (QWP1SPTO)

Miscellaneous Parameters:

Decimal Divide Option

The decimal divide option. (QWP4DIV3)

WTO Routing WTO route codes for DB2 messages. (QWP4SMRC)

Site Type Indicates whether this site is LOCAL or RECOVERY. This is needed for RECOVERY purposes. (QWP4SIT)

Change Data Capture

Indicates whether change data capture is enabled. (QWP4CDC)

Enable Data Propagation

Indicates whether to use data propagator (DPROP) to propagate SQL changes made to tables defined with data capture changes. (QWP4ENF)



3990-3 Sequential Cache

Indicates whether to use sequential mode to read cached data from a 3390-3 device. (QWP4SCAC)

Possible values for Version 3 are as follows:

YES Use sequential.

NO Bypass.

Possible values for Version 4 are as follows:

Bypass Same as NO in DB2 Version 3.

SEQ Same as YES in DB2 Version 3.

Automatic Rebind

Indicates whether plans or packages are automatically rebound. (QWP4ABN)

Automatic Rebind Explain

Indicates whether Explain processing is enabled during automatic rebind. (QWP4ABX)

Historical R

eporter DS

NZPA

RM

Reports

389

System

Installation Parameters (D

SN

ZPAR

M)

FIG

UR

E 73.

(Part 1 o

f 4). System

Installatio

n P

arameters R

epo

rt

Omegamon II for DB2 V&REL. System Installation Parameters Page 1Run Date=&PANDAT4Y. Run Time=16:03:06 Group=TDDB241G Member=D411 DB2ID=D411 Assembled: mm/dd/yyy In Use: mm/dd/yyy, 15:55:59 Thread Parameters Value Macro Parameter-------------------------- ----------------------------------- -------- ---------Maximum Concurrent Threads 50 DSN6SYSP CTHREADMaximum TSO Users 40 DSN6SYSP IDFOREMaximum Batch Connections 10 DSN6SYSP IDBACKMaximum Active DBATs 500 DSN6SYSP MAXDBATMaximum Connected DBATs 10000 DSN6SYSP CONDBAT Logging Parameters--------------------Logging Mode Dual DSN6LOGP TWOACTVMaximum Input Tape Units 2 DSN6LOGP MAXRTUDeallocate Time 70 minute(s) 20 seconds DSN6LOGP DEALLCTOutput Buffer 400K DSN6LOGP OUTBUFFInput Buffer 28K DSN6LOGP INBUFFWrite Threshold 20 DSN6LOGP WRTHRSHCheckpoint Frequency 1000 records DSN6SYSP LOGLOAD Archiving Parameters---------------------------Archiving Mode Dual DSN6LOGP TWOARCHVolumes in BSDS 500 DSN6LOGP MAXARCHCatalog Volumes Yes DSN6ARVP CATALOGRACF Protect No DSN6ARVP PROTECTMount WTOR Yes DSN6ARVP ARCWTORDevice Type 1 TSODA DSN6ARVP UNITDevice Type 2 TSODA DSN6ARVP UNIT2Space Allocation Unit Block DSN6ARVP ALCUNITPrimary Space Allocation 500 DSN6ARVP PRIQTYSecondary Space Allocation 60 DSN6ARVP SECQTYBlocksize 8192 DSN6ARVP BLKSIZERetention 60 days DSN6ARVP ARCRETNMass Storage Volume Group 1 DSN6ARVP MSVGPMass Storage Volume Group 2 DSN6ARVP MSVGP2Archive Log 1 DSN Prefix TDDB241A.ARCHLOG1 DSN6ARVP ARCPFX1Archive Log 2 DSN Prefix TDDB241A.ARCHLOG2 DSN6ARVP ARCPFX2Compact Data No DSN6ARVP COMPACTMax Quiesce Time 5 seconds DSN6ARVP QUIESCETimestamp in Name Yes DSN6ARVP TSTAMP

System


SN

ZPAR

M)

390O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 System Installation Parameters Page 2Run Date=mm/dd/yyy Run Time=16:03:06 Authorization Parameters------------------------Authorization Checking Yes DSN6SPRM AUTHSystem Administrator 1 TDO214 DSN6SPRM SYSADMSystem Administrator 2 TDO209 DSN6SPRM SYSADM2System Operator 1 TDO209 DSN6SPRM SYSOPRSystem Operator 2 TDO210 DSN6SPRM SYSOPR2Default ID IBMUSER DSN6SPRM DEFLTIDPackage Owner Authorization No DSN6SPRM HOPAUTHPlan Authorization Cache Size 1024 DSN6SPRM AUTHCACHBind New Package BINDADD DSN6SPRM BINDNV Dataset & Database Parameters Value Macro Parameter----------------------------- ----------------------------------- -------- ---------Highlevel Dataset Qualifier TDDB241A DSN6SPRM CATALOGMaximum Datasets Open 200 DSN6SPRM DSMAXHSM Auto Recall Yes DSN6SPRM RECALLAuto Recall Wait 120 seconds DSN6SPRM RECALLDCheckpoints to Pseudo-Close 5 DSN6SYSP PCLOSENElapsed Time to Pseudo-Close 10 minute(s) DSN6SYSP PCLOSETDefault Index Type 2 DSN6SPRM DEFIXTPCheckpoints to Level ID Update 5 DSN6SYSP DLDFREQDatabase Restart/Defer RESTART DSN6SPRM n/aRestart/Defer List: ALL IRLM Parameters--------------------------IRLM Cataloged Procedure D41IRLM DSN6SPRM IRLMPRCIRLM Subsystem Name MRLM DSN6SPRM IRLMSIDAuto Start IRLM Yes DSN6SPRM IRLMAUTAuto Start Wait 300 seconds DSN6SPRM IRLMSWTTimeout Interval 180 seconds DSN6SPRM IRLMRWTUtility Timeout 6 DSN6SPRM UTIMOUTMaximum Locks Per Tablespace 1000 DSN6SPRM NUMLKTSMaximum Locks Per User 10000 DSN6SPRM NUMLKUSU Lock for Repeatable Read No DSN6SPRM RRULOCK

FIGURE 74. (Part 2 of 4) System Installation Parameters Report

Historical R

eporter DS

NZPA

RM

Reports

391

System


SN

ZPAR

M)

Omegamon II for DB2 V540 System Installation Parameters Page 3Run Date=mm/dd/yyy Run Time=16:03:06 Pool Sizes-------------EDM Pool 6000K DSN6SPRM EDMPOOLSort Pool 4000K DSN6SPRM SRTPOOLRID Pool 4384K DSN6SPRM MAXRBLKMinimum RID Lists 1 DSN6SPRM MINRBLK Governor (RLF) Parameters-------------------------Auto Start No DSN6SYSP RLFAuthorization ID SYSIBM DSN6SYSP RLFAUTHTable Suffix 01 DSN6SYSP RLFTBLAction If Error NOLIMIT DSN6SYSP RLFERR DDF Parameters------------------------DDF Start Option AUTO DSN6FAC DDFAction If RLST Error NORUN DSN6FAC RLFERRDResynchronization Interval 2 DSN6FAC RESYNCCommit Status INACTIVE DSN6FAC CMTSTATIdle Thread Timeout 15 DSN6FAC IDTHTOIN Trace Parameters------------------------Global Trace Classes NO DSN6SYSP TRACSTRStatistics Trace Classes 01,03,04 DSN6SYSP SMFSTATAccounting Trace Classes 01,02,03 DSN6SYSP SMFACCTAudit Trace Classes NO DSN6SYSP AUDITSTMonitor Trace Classes NO DSN6SYSP MONTrace Table Size 1K DSN6SYSP TRACTBLStatistics Interval Time 30 DSN6SYSP STATIMEMonitor Buffer Size 1000K DSN6SYSP MONSIZE DDCS Parameters Value Macro Parameter------------------------- ----------------------------------- -------- ---------Activate DD Control No DSN6SPRM RGFINSTLControl All Applications No DSN6SPRM RGFDEDPLRequire Full Names Yes DSN6SPRM RGFFULLQUnregistered Default ACCEPT DSN6SPRM RGFDEFLTRegistration Owner DSNRGCOL DSN6SPRM RGFCOLIDRegistration Database DSNRGFDB DSN6SPRM RGFDBNAMAppl Registration Table DSN_REGISTER_APPL DSN6SPRM RGFNMPRTObject Registration Table DSN_REGISTER_OBJT DSN6SPRM RGFNMORTART/ORT Escape Character (X’40’) DSN6SPRM RGFESCP


System


SN

ZPAR

M)

392O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 System Installation Parameters Page 4Run Date - mm/dd/yyy Run Time - 16:03:06

Data Sharing Parameters--------------------------Data Sharing Yes DSN6GRP DSHAREGroup Name TDDB241G DSN6GRP GRPNAMEMember Name D411 DSN6GRP MEMBNAME

Stored Procedure Parameters---------------------------MVS Procedure Name D411SPAS DSN6SYSP STORPROCMaximum Abend Count 0 DSN6SYSP STORMXABTimeout Value 180 DSN6SYSP STORTIME

Miscellaneous Parameters---------------------------Decimal Divide Option No DSN6SPRM DECDIV3WTO Routing 01 DSN6SYSP ROUTCDESite Type LOCAL DSN6SPRM SITETYPChange Data Capture No DSN6SPRM CHGDCEnable Data Propagation No DSN6SPRM EDPROP3990-3 Sequential Cache BYPASS DSN6SPRM SEQCACHAutomatic Rebind Yes DSN6SPRM ABINDAutomatic Rebind Explain Yes DSN6SPRM ABEXP


Historical Reporter Performance Reports 393

Historical ReporterPerformance Reports

IntroductionThis chapter describes the Performance Reports.

Chapter ContentsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394Application Trace Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395Application Trace Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400Application SQL Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414Application Event Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422Application Buffer Pool Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430Application Buffer Pool I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433System Buffer Pool Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438System Buffer Pool I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442EDM Pool I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446Lock Suspension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449Global Lock Suspensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454Lock Contention. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459P-Lock Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467System Event Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472Negative Application SQL Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476

16

Overview


Overview

IntroductionPerformance reports require DB2 performance trace records generated by DB2. Each of these records has an ID, known as an IFCID, which represents a traceable event in DB2.

IFC source fields that begin with “QW” refer to IBM DSECT maps and are documented online in the IBM dataset DSNSAMP(DSNWMSGS).

The 105 and 107 records are needed to convert the DBID and PSID decimal representation of the database and pageset names to readable names on the report. If these records are not provided as input, the decimal representations of DBID and PSID cannot be converted, and the decimal number will be printed on the report instead. Furthermore, the DB2 START TRACE PERF command must contain TDATA (CPU,COR) if IN DB2 CPU TIME is to be inserted in field QWHUCPU and displayed in the Historical Performance reports. For more information, refer to the section titled “Complete configuration of the classic interface” in the OMEGAMON II for DB2 Configuration and Customization Guide.




IntroductionThis report displays applications that executed during the specified date and time.

This report can be used:

� to determine thread activity

� to determine resource usage of units of work and programs within a thread

� to locate threads that need further analysis due to poor performance in relation to other threads

Default DDname O2RPATS

Default TitleApplication Trace Summary

Data SourceIFCIDs 6–9, 15–18, 21, 58–71, 73, 74, 84–89, 95, 96

IFCIDs 68–71, 73, and 84–89, if you specify the select elements UOWSTART or PGMSTART.

If records are not matched with their corresponding pair, they will be dropped; that is, the reported information may be incomplete.

Group By ElementsTHREAD, UNIT_OF_WORK, PROGRAM

Specify only one of these per report.

DEFAULT: UNIT_OF_WORK

Order By Elements DB2ID, TIME, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, AUTHID, ORIGAUTH, SYSID, MEMBER, GROUP

Select Elements DB2ID, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, AUTHID, ORIGAUTH, IFCID, THREADSTART, UOWSTART, PGMSTART, SYSID, MEMBER, GROUP



Data Elements




Planname The plan name of the application. (QWHCPLAN)

Connid The connection identifier of the application. (QWHCCN)

Corrid The correlation identifier of the application. (QWHCCV)

Authid The authorization identifier of the application. (QWHCAID)

Original Authid The original authorization identifier of the application. (QWHCOPID)

Start Date The date that the application thread, unit of work, or program (depending on the groupby specification) began execution. (QWHSSTCK)

Start Time The time that the application thread, unit of work, or program (depending on the groupby specification) began execution. (QWHSSTCK)

Program Name The name of the application program invoked. If the groupby specification is either by unit of work or thread, then the value of this field will be the name of the first program invoked. (QW00nnPN from the Begin SQL Statement record)

SQL The number of SQL calls issued. (number of IFCIDs 59, 60, 61, 62, 64, 65)

In-DB2 Time The amount of time that elapsed while executing in DB2. (END.QWHSSTCK-START.QWHSSTCK sum)

In-DB2 CPU The amount of CPU time that accumulated while executing in DB2. (END.QWHUCPU-START.QWHUCPU sum)

Sorts The number of sorts performed. (number of IFCID 95s)

Sort Time The amount of time that elapsed while executing sorts. (IFCID END.QWHSSTCK - IFCID START.QWHSSTCK sum)

Locks The number of locks acquired. (number of IFCID 21s where QW0021FC = QW0021LO)

Rows The number of rows processed. (QW0058RP sum)

Pages The number of pages scanned. (QW0058PS sum)

Sync I/O Req The number of synchronous I/O (read or write) requests processed. (QW0006/7 or QW0008/9 record pairs sum)

Sync I/O Time The total elapsed time of all synchronous I/O (read or write) requests processed. (IFCID 7/9.QWHSSTCK - IFCID 6/8.QWHSSTCK sum)

Unit of Work Totals

The sum of all work performed by programs within the unit of work. This line is printed only if Group by PROGRAM is specified.

Thread Totals The sum of all work performed by units of work within the same thread. This line is printed only if you do not group by thread.

Historical R

eporter Performance R

eports397

Application Trace S

umm

ary

FIG

UR

E 77.

Ap

plicatio

n Trace —

Su

mm

ary (Gro

up

by TH

RE

AD

) Rep

ort

OMEGAMON II for DB2 V540 Application Trace Summary Page 1Run Date=mm/dd/yy Grouped by Thread Run Time=12.43.07 DB2Id=D22B, Planname=ACTMAINT, Connid=CICS1, Corrid=PTACT1, Authid=TDO306, Original Authid=TDO306---------------------------------------------------------------------------------------------------------------------------------- Sync SyncStart Date Start Time Program Name SQL In-DB2 Time In-DB2 CPU Sorts Sort Time Locks Rows Pages I/O Req I/O Time---------- --------------- ------------ ------ ------------ ---------- ----- ---------- -------- -------- ------- ------- ---------mm/dd/yy 13:32:52.980023 O2PGM010 79 00:00:06.330 00:00.066 0 00:00:00.0 94 1004 24 0 00:00.000 DB2Id=D22B, Planname=ACTMAINT, Connid=CICS1, Corrid=PTACT1, Authid=TDO306, Original Authid=TDO306---------------------------------------------------------------------------------------------------------------------------------- Sync SyncStart Date Start Time Program Name SQL In-DB2 Time In-DB2 CPU Sorts Sort Time Locks Rows Pages I/O Req I/O Time---------- --------------- ------------ ------ ------------ ---------- ----- ---------- -------- -------- ------- ------- ---------mm/dd/yy 14:32:52.980023 O2PGM010 79 00:00:06.330 00:00.066 0 00:00:00.0 94 1004 224 0 00:00.000

Application Trace S

umm

ary

398O

ME

GA

MO

N II for D

B2 H


uide, Version 540

OMEGAMON II for DB2 V540 Application Trace Summary Page 1Run Date=mm/dd/yy Grouped By Unit of Work Run Time=12.43.07 DB2Id=D22B, Planname=ACTMAINT, Connid=CICS1, Corrid=PTACT1, Authid=TDO306, Original Authid=TDO306---------------------------------------------------------------------------------------------------------------------------------- Sync SyncStart Date Start Time Program Name SQL In-DB2 Time In-DB2 CPU Sorts Sort Time Locks Rows Pages I/O Req I/O Time---------- --------------- ------------ ------ ------------ ---------- ----- ---------- -------- -------- ------- ------- ---------mm/dd/yy 13:32:52.980023 O2PGM010 30 00:00:02.305 00:00.022 0 00:00:00.0 37 402 10 0 00:00.000 13:52:52.980023 O2PGM010 49 00:00:04.025 00:00.044 0 00:00:00.0 57 602 14 0 00:00.000 ====== ============ ========== ===== ========== ======== ======== ======= ======= ========= Thread Totals 79 00:00:06.330 00:00.066 0 00:00:00.0 94 1004 24 0 00:00.000 DB2Id=D22B, Planname=ACTMAINT, Connid=CICS1, Corrid=PTACT1, Authid=TDO306, Original Authid=TDO306---------------------------------------------------------------------------------------------------------------------------------- Sync SyncStart Date Start Time Program Name SQL In-DB2 Time In-DB2 CPU Sorts Sort Time Locks Rows Pages I/O Req I/O Time---------- --------------- ------------ ------ ------------ ---------- ----- ---------- -------- -------- ------- ------- ---------mm/dd/yy 14:32:52.980023 O2PGM010 30 00:00:02.305 00:00.022 0 00:00:00.0 37 402 10 0 00:00.000 14:52:52.980023 O2PGM010 49 00:00:04.025 00:00.044 0 00:00:00.0 57 602 14 0 00:00.000 ====== ============ ========== ===== ========== ======== ======== ======= ======= ========= Thread Totals 79 00:00:06.330 00:00.066 0 00:00:00.0 94 1004 24 0 00:00.000

FIGURE 78. Application Trace-Summary (Group by UNIT_OF_WORK Report

Historical R


eports399

Application Trace S

umm

ary

OMEGAMON II for DB2 V540 Application Trace Summary Page 1Run Date=mm/dd/yy Grouped By Program Run Time=12.43.07 DB2Id=D22B, Planname=ACTMAINT, Connid=CICS1, Corrid=PTACT1, Authid=TDO306, Original Authid=TDO306---------------------------------------------------------------------------------------------------------------------------------- Sync SyncStart Date Start Time Program Name SQL In-DB2 Time In-DB2 CPU Sorts Sort Time Locks Rows Pages I/O Req I/O Time---------- -------------- ----------- ------ ------------ ---------- ----- ---------- -------- -------- ------- ------- ---------mm/dd/yy 13:32:52.980023 O2PGM010 18 00:00:01.260 00:00.014 0 00:00:00.0 22 252 6 0 00:00.000 13:36:31.065123 O2PGM015 12 00:00:01.045 00:00.008 0 00:00:00.0 15 150 4 0 00:00.000 ====== ============ ========== ===== ========== ======== ======== ======= ======= ========= Unit of Work Totals 30 00:00:02.305 00:00.022 0 00:00:00.0 37 402 10 0 00:00.000 Sync SyncStart Date Start Time Program Name SQL In-DB2 Time In-DB2 CPU Sorts Sort Time Locks Rows Pages I/O Req I/O Time---------- --------------- ------------ ------ ------------ ---------- ----- ---------- -------- -------- ------- ------- ---------mm/dd/yy 13:52:52.980023 O2PGM010 29 00:00:01.270 00:00.026 0 00:00:00.0 37 352 8 0 00:00.000 13:56:31.065123 O2PGM015 20 00:00:01.055 00:00.018 0 00:00:00.0 20 250 6 0 00:00.000 ====== ============ ========== ===== ========== ======== ======== ======= ======= ========= Unit of Work Totals 49 00:00:02.325 00:00.044 0 00:00:00.0 57 602 14 0 00:00.000 ====== ============ ========== ===== ========== ======== ======== ======= ======= ========= Thread Totals 79 00:00:04.330 00:00.066 0 00:00:00.0 94 1004 24 0 00:00.000 DB2Id=D22B, Planname=ACTMAINT, Connid=CICS1, Corrid=PTACT1, Authid=TDO306, Original Authid=TDO306------------------------------------------------------------------------------------------------------------------------------------ Sync SyncStart Date Start Time Program Name SQL In-DB2 Time In-DB2 CPU Sorts Sort Time Locks Rows Pages I/O Req I/O Time---------- --------------- ------------ ------ ------------ ---------- ----- ---------- -------- -------- ------- ------- ---------mm/dd/yy 14:32:52.980023 O2PGM010 18 00:00:01.260 00:00.014 0 00:00:00.0 22 252 6 0 00:00.000 14:36:31.065123 O2PGM015 12 00:00:01.045 00:00.008 0 00:00:00.0 15 150 4 0 00:00.000 ====== ============ ========== ===== ========== ======== ======== ======= ======= ========= Unit of Work Totals 30 00:00:02.305 00:00.022 0 00:00:00.0 37 402 10 0 00:00.000 Sync SyncStart Date Start Time Program Name SQL In-DB2 Time In-DB2 CPU Sorts Sort Time Locks Rows Pages I/O Req I/O Time---------- --------------- ------------ ------ ------------ ---------- ----- ---------- -------- -------- ------- ------- ---------mm/dd/yy 14:52:52.980023 O2PGM010 29 00:00:01.270 00:00.026 0 00:00:00.0 37 352 8 0 00:00.000 14:56:31.065123 O2PGM015 20 00:00:01.055 00:00.018 0 00:00:00.0 20 250 6 0 00:00.000 ====== ============ ========== ===== ========== ======== ======== ======= ======= ========= Unit of Work Totals 49 00:00:02.325 00:00.044 0 00:00:00.0 57 602 14 0 00:00.000 ====== ============ ========== ===== ========== ======== ======== ======= ======= ========= Thread Totals 79 00:00:04.330 00:00.066 0 00:00:00.0 94 1004 24 0 00:00.000

FIGURE 79. Application Trace-Summary (Group by PROGRAM) Report

Application Trace Detail



IntroductionThis report displays application resource use at the program, unit of work, or thread level, depending on the groupby option selected. Output is organized into the following categories:

� SQL summary information� sort summary information� scan summary information� lock summary information� I/O summary information� stored procedure summary information� parallel processing summary information

This report can be used to determine the following:

� resource usage of SQL statements within an application� locking, I/O, sort, and scan activity within an application� exploitation of query parallelism within an application� usage of stored procedures by an application

Default DDname O2RPATD

Default Title Application Trace Detail

Data Source IFCIDs 6–10, 15–18, 21, 44, 45, 53, 54, 58–71, 73, 74, 84 –89, 95, 96, 221, 222, 231, 233

IFCIDs 105 and 107 to convert database and pageset IDs


Group By ElementsTHREAD, UNIT_OF_WORK, PROGRAM, SYSID

Only specify one of these per report.

DEFAULT: UNIT_OF_WORK



Order By ElementsDB2ID, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, AUTHID, ORIGAUTH, TIME, SYSID, MEMBER, GROUP

Select Elements DB2ID, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, AUTHID, ORIGAUTH, IFCID, THREADSTART, UOWSTART, PGMSTART, SYSID, MEMBER, GROUP



Data Elements

Title Line:

Start Time The date and time (timestamp) that the application thread, unit of work, or program (depending on the groupby specification) began execution. (QWHSSTCK of the first IFCID record for (1) the first unit of work in the thread if grouped by thread, (2) the current unit of work if grouped by unit of work, or (3) the current program activity if grouped by program.)









Package The application program name invoked by the application. If packages are being used, the program name may be replaced by the package name in the form location.collection.program. If the groupby specification is by unit of work or thread, then the value of this field will be the first program name invoked. (QW00nnLN/PC/PN from Begin SQL or Begin SORT statement record)

SQL Summary

SQL Call The SQL statement type issued. (Derived from the IFCID number and statement type (QW00nnST))

Statement# The statement number of the SQL statement that was generated by the DB2 precompiler. (QW00nnSN from IFCIDs 53, 58–61, or 64–66)

Count The number of times that this SQL statement was executed. (Number of same IFCIDs (BEGIN SQL type: 59–61 or 64–66) with the same statement number. (QW00nnSN))

HiSQLcode The highest SQL code encountered when this statement was executed (Max of SQLcode subfield of SQLCA in IFCID 53 or 58).

In-DB2 Time The amount of time that elapsed while executing in DB2 to process these SQL statements. (SSSS.THT)

(END.QWHSSTCK-START.QWHSSTCK sum)

In-DB2 CPU The amount of CPU time that elapsed while executing in DB2 to process these SQL statements. (SSSS.THT)

(END.QWHUCPU-START.QWHUCPU sum)

Average Time The average amount of time that elapsed while executing in DB2 per SQL statement. (SSSS.THT)

(END.QWHSSTCK-START.QWHSSTCK sum/count)



Avg CPU The average amount of CPU time used while executing in DB2 to process an SQL statement. (SSSS.THT)

(END.QWHUCPU-START.QWHUCPU sum/count)

Locks The number of locks requested while processing an SQL statement. (QW0021FC = type lock)

Rows The number of rows processed while executing an SQL statement. (QW0058RP)

Pages The number of pages processed while executing an SQL statement. (QW0058RP)

Stored Procedure Call Summary

Name The name of the stored procedure. Applies only to DB2 Version 4 and above. (QW0233PR)

Call Count The number of calls to this stored procedure. (Count of IFCID 233 pairs.) Applies only to DB2 Version 4 and above.

Avg Time in Procedure

The elapsed time is calculated as the time difference between the entry IFCID 233 for the named procedure and the exit IFCID 233. The average is calculated by summing these differences and dividing by the number of IFCID 233 pairs. (Average of difference between ENTRY.QWHSSTCK and EXIT.QWHSSTCK.) Applies only to DB2 Version 4 and above.

# SQL Calls The total number of SQL calls made from this procedure. (A count of the number of begin SQL-type IFCIDs, 59-61 or 64-69, encountered between the entry IFCID 233 record and the exit). Applies only to DB2 Version 4 and above.

Total In-DB2 CPU Time

The sum of the In-DB2 CPU time for all SQL statements between IFCID 233 pairs for this stored procedure. Applies only to DB2 Version 4 and above.

Avg In-DB2 CPU Time

The Total In-DB2 CPU time divided by the Call Count. Applies only to DB2 Version 4 and above.

Locks The sum of the number of locks for all SQL statements between IFCID 233 pairs for this stored procedure. Applies only to DB2 Version 4 and above.

Rows The sum of the number of rows processed for all SQL statements between IFCID 233 pairs for this stored procedure. Applies only to DB2 Version 4 and above.

Pages The sum of the number of pages scanned for all SQL statements between IFCID 233 pairs for this stored procedure. Applies only to DB2 Version 4 and above.

Sorts The number of sorts executed while the stored procedure is in control. (Count of number of IFCID 95 records between 233 pairs.) Applies only to DB2 Version 4 and above.

Sort Time This is calculated from the total time spent in sorts while executing this stored procedure. The total time is divided by the Call Count to derive the Average Sort Time. Applies only to DB2 Version 4 and above.

Sort Summary:



SQL Call The SQL statement causing sort processing to be invoked. (from the last preceding unpaired Begin SQL IFCID).

Statement# The SQL statement number causing sort processing to be invoked. (QW00nnSN from the last preceding BEGIN SQL IFCID).

Type The type of sort performed. (QW0096TS, of the outermost sort if there are nested sorts).

Possible sort types:

ESA ESA sort using hardware sort assist instructions.

ESAT Combination ESA tag sort.

GRP Groupby sort.

REG Regular sort (not ESA, groupby, tag, or RID list sort). Applies only to DB2 Version 3.

TAG Tag sort. Applies only to DB2 Version 3.

Count The number of times that the SQL statement invoked a sort. (number IFCID 95).

#Part The number of times that the sort used partitioning. (QW0096SC, QW0096PO).

Sort Time The amount of elapsed time spent in sort processing. (END.QWHSSTCK-START.QWHSSTCK, of outermost sort if nested sorts).

Records The total number of records sorted. (QW0096NR sum).

Reads The number of records retrieved from a workfile during sort processing. (QW0096RD sum).

Inserts The number or records inserted into a workfile during sort processing. (QW0096IN sum).

Deletes The number or rows deleted due to merging records, for the evaluation of column functions with groupby. (QW0096RL sum).

WFiles The number of workfiles used during sort processing. (QW0096WF sum).

Runs The number of initial runs needed to perform the sort. Applies only to DB2 Version 3. (QW0096IR sum)

InitWF The number of initial runs needed to perform the sort. Applies only to DB2 Version 4 and above. (QW0096IR sum)

Merges The number of merge passes needed to perform the sort. (QW0096MP sum)

Cols The average number of sort columns. (QP0096SSC sum)

Keys The average number of sort keys. (QW0096SK)

Scan Summary:

Database The name of the database on which the scan was performed if IFCIDs 105/107 are available, or the database identifier number if IFCIDs 105/107 are not available. (QW0015DB/QW0016DB/QW0017DB)



Pageset The name of the pageset (tablespace) on which the scan was performed if IFCIDs 105/107 are available, or the pageset identifier number if IFCIDs 105/107 are not available. (QW0015PS/QW0016PS/QW0017PS)

Scan Count The number of scans of this type performed. (the number of IFCIDs (15, 16, or 17) with matching QW00nnDB and QW00nnPS)

Scan Type The type of scan performed. (type of IFCID: 15, 16, or 17)Possible scan types are as follows:� index� insert� seq(uential)

Data Type The type of data being scanned. (QW0018ID)Possible data types are as follows:� data (data pageset)� index (index pageset)� work (workfile pageset)

Rows Processed The number of rows processed by the data manager. (QW0018RP)

Rows Looked The number of rows examined by the data manager. (QW0018LA)

Rows Qual/DM The number of rows qualified by the data manager. (QW0018DQ)

Rows Qual/RD The number of rows qualified by RDS. (QW0018RQ)

Rows Updated The number of rows updated. (QW0018UP)

Rows Inserted The number of rows inserted. (QW0018IN)

Rows Deleted The number of rows deleted. This value is accumulated only when the rows deleted value is not -1. (QW0018DE)

Mass Del Req The number of mass delete requests made. This value is accumulated when the rows deleted value is -1. (QW0018DE)

Pages Scanned The total number of pages scanned by the data manager. (QW0018PS)

Pages Scan/Ref The total number of pages scanned due to enforcement of defined referential integrity constraints. (QW0018PR)

Rows Del/Ref he number of rows deleted due to enforcement of defined referential integrity constraints. (QW0018DR)

Lock Summary:

Type The lock type acquired. There will be one entry for every lock type acquired. (QW0021KT)

Possible lock types are as follows:



DPAG Data page locking.DTBS Database locking.PSET Pageset locking.DSET Dataset locking (partition).SKCT Skeleton cursor table locking.IPAG Index page locking.PDSO Pageset or dataset open locking.UTDA Utility I/O damage assessment.PSPI Pageset piece locks.SDBA Start/stop lock on DBA table.UGPT Getpage retry during abort.DESP 32K desperation pool lock.SREC SYSLGRNG recording lock.UTSE Utility serialization locking.MDEL Mass delete lock.TABL Table locking.HASH Hash anchor lock.SKPT Skeleton package table locking.COLL Collection lock.BIND Autobind/remote bind lock.ALBP Alter bufferpool lock.CDRN CS-Read drain lock.RDRN RR-Read drain lock.WDRN Write drain lock.UNDT Undetermined lock type.ROW Row.IEOF Index EOF.GRBP Group BP start/stop.PITR Index manager tree P-lock.PPSP Pageset/partition P-lock.PPAG Page P-lock.PCDB DDF CDB P-lock.PBPC Group BP castout P-lock.PPSC Pageset/partition castout P-lock.PRLF RLF P-lock.PDBD DBD P-lock.CDIR Catmaint convert directory.CCAT Catmaint convert catalog.CMIG Catmaint migration.DBEX DB exception lpl/grecp.UTID Utility Uid lock.UTEX Utility exclusive execution.RSTR SCA restart/redo access.DBUX DB exception update lock.RDBD Repair DBD text/diagnose.



Level The level of the lock. (QW0021ST)

Possible lock levels are as follows:

ANY Change or unlock functions may use this lock level.IS Intent share lock on tablespace.IX Intent exclusive lock on tablespace.NSU Non-shared update lock.S Shared lock on page or tablespace.SIX Share with intent exclusive lock on tablespace.U Update lock on page or tablespace.US Unprotected shared lock.X Exclusive lock on page or tablespace.

Resource Identifiers

The resource held by the lock. The content of this field depends on the type of lock that was requested. Only the information that applies to the type of resource being locked is shown. For example, for a database lock only the database identifier is displayed. For a data page lock, the database and pageset identifier is shown; each individual page lock is not listed. (QW0021RN - see the following list for subfields used)

Possible fields are as follows:

COLL The collection ID of the requested resource. This applies only to skeleton package table and collection lock types. (QW0021RN)

DB The database of the requested resource. (QW0021KD)

PART The partition number of the requested resource. (QW0021K2)

PKG The package name of the requested resource. This name is decompressed from the resource name, along with the collection ID (displayed with COLL label), and concatenated with a consistency token. This applies only to skeleton package table lock types. (QW0021RN)

PLAN The plan name of the requested resource. This applies only to skeleton cursor table lock types. (QW0021KD, QW0021KP, and QW0021KR)

PS The pageset of the requested resource. (QW0021KP)

TABLE The table of the requested resource. (QW0021KB)

Bufferpool The bufferpool name of the requested resource. (QW0021KD/QW0021KP for L-locks, QW0021P1 for P-Locks). P-Locks apply only to DB2 Version 4 and above.

UTID For utility UID lock, the utility ID of the requested resource. (First 16 bytes of QW0021RN)

Acquires The number of locks acquired for the specified type, level, and resource. (number of IFCID 21s with QW0021FC = QW0021LO)



Suspends The number of locks acquired for the specified type, level, and resource which resulted in a suspension of the application. (number of IFCID 21s with matching IFCID 44/45 record pairs)

Resumes The number of locks acquired for the specified type, level, and resource which resulted in a suspension of the application and a normal resume. (number of IFCID 21s with matching IFCID 44/45 record pairs where QW0045R = N)

Avg ElapTime/Susp

The average elapsed time for each suspend that was resumed normally. Locks that resulted in a timeout or deadlock will not be counted in this figure to avoid skewing the value to meaninglessness. (END.QWHSSTCK-BEGIN.QWHSSTCK from matching IFCID 44/45 record pairs divided by number of matching IFCID 44/45 record pairs where QW0045R = N)

Timeouts The number of locks acquired for the specified type, level, and resource which resulted in a suspension of the application and a subsequent timeout. (Number of IFCID 21s with matching IFCID 44/45 record pairs where QW0045R = T)

Deadlocks The number of locks acquired for the specified type, level, and resource which resulted in a suspension of the application and a subsequent deadlock. (number of IFCID 21s with matching IFCID 44/45 pairs where QW0045R = T)

(LockTotals by Type)

For each lock type (first column), a totals line is printed after all detail lines for the lock type. This line shows the total number of locks acquired and the total number of lock suspensions, resumes, timeouts, and/or deadlocks that occurred, as well as the average elapsed time for each lock suspension that was resumed normally.

Buffer Pool I/O Summary:

Database Database name (if IFCIDs 105/107 are available) or database identifier number (if IFCIDs 105/107 are not available). (QW0006DB/QW0008DB/QW0010DB)

Pageset The name of the pageset (tablespace) on which the scan was performed (if IFCIDs 105/107 are available) or the pageset identifier number (if IFCIDs 105/107 are not available). (QW0015PS/QW0016PS/QW0017PS)

BP Buffer pool identifier where pages are kept in storage. (QW0006BP/QW0008BP/QW0010BP)

GetPage Requests:

# Req The number of getpage requests. (QW0198GP)

NoRead The number of no-read getpage requests. (QW0198N)

Hit The percentage of buffer pool hits. (QW0198H)

Seq The percentage of getpage requests for a sequential access. (QW0198RN)

Rand The percentage of getpage requests for a random access. (QW0198RN)

List The percentage of getpage requests for a RID list access. (QW0198RL)



Release Requests:

#Req The number of page release requests. (QW0198RP)

Std The percentage of requests for a standard release. (QW0198SR)

Dest The percentage of requests for a destructive release. (QW0198DR)

MRU The percentage of requests to mark the buffer for MRU disposition. (QW0198MR)

# Set Writes The number of set write intent page requests. (QW0198SW)

Synchronous:

#Read The number of synchronous read requests. (QW0006F = R)

#Write The number of synchronous write requests. (QW0008)

Asynchronous:

#Read The number of asynchronous read requests. (QW0006F = S, L, or D)

SeqP The percentage of asynchronous read requests that were sequential prefetch. (QW0006F = S)

LstP The percentage of asynchronous read requests that were for list prefetch. (QW0006F = L)

DynP The percentage of asynchronous read requests that were for dynamic prefetch. (QW0006F = D)

Parallel Processing Summary

Stmt # The SQL statement number. Applies only to DB2 Version 4 and above. (QW0221QN/QW0222QN/QW0231QN)

Query Block# The query block number. Applies only to DB2 Version 4 and above. (QW0221QN/QW0222QN/QW0231QN)

Group # The parallel group number. Applies only to DB2 Version 4 and above. (QW0221GN/QW0222GN/QW0231GN)

Task # The sequence number of the child task in the parallel group. For a parent task the value of ‘P’ is shown. Applies only to DB2 Version 4 and above. (QW0231TQ or sequential number if 231 record not available)

Average Task Elapsed Time

The average amount of elapsed time for the task. Applies only to DB2 Version 4 and above. (END.QWHSSTCK-BEGIN.QWHSSTC for the parent task, QW0222SE-QW0222SS for the child)

Average Task CPU Time

The average amount of CPU time used by this task. Applies only to DB2 Version 4 and above. (END.QWHUCPU-BEGIN.QWHUCPU for the parent task, QW0231TX for the child)

Rows Processed The number of rows processed by this task. Applies only to DB2 Version 4 and above. (QW0222PR for parent task, QW0222SR for child where QW0222FM = 0 or 1)

Rows Produced The number of rows produced by this task. Applies only to DB2 Version 4 and above. (QW0222PR for parent task, QW0222SR for child where QW0222FM = 2 or 3)



Rows/WorkFile The number of rows in the work file. Applies only to DB2 Version 4 and above. (QW0222PR for parent task, QW0222SR for child where QW0222FM = 5)

Rows Consumed The number of rows consumed by the child task. Applies only to DB2 Version 4 and above. (QW0222OR for child task only, where QW0222FM = 2,3, or 4)

Task Suspends For a parent task this is the number of time the task was suspended waiting for a child. For a child task it is the number of time the child was suspended waiting for the parent. Applies only to DB2 Version 4 and above. (QW0222CS for parent tasks, QW0222C for child tasks QW0222FM = 2, 3, 4, or 5)

Locks Acquired The number of locks acquired by the task. Applies only to DB2 Version 4 and above. (Count of IFCID 21 records for each task, where QW0021FC=x’02’)

Pages Processed The number of pages processed by this task. Applies only to DB2 Version 4 and above. (QW0058PS for the parent task, sum of QW0018PS for child tasks)

Historical R


eports411

Application Trace D

etail

Omegamon II for DB2 V540 Application Trace Detail Page 1Run Date=mm/dd/yy Grouped by Program Run Time=15:49:50 Timestamp=1995-05-05-14.16.20.996304, Group=TDDB241G, Member=D411Sysid=SYSG, DB2id=D411, Planname=DSNESPCS, Connid=TSO, Corrid=STO210, Authid=STO210, Original Authid=STO210, Program=DSNESM68---------------------------------------------------------------------------------------------------------------------------------- SQL SUMMARY SQL Call Stmt # Count In-DB2 Time In-DB2 CPU Average Time Avg CPU Time Locks Rows Pages ------------------ ------ ----- --------------- ------------ --------------- ------------ -------- ------- -------- Prepare Cursor 71 1 00:00:01.870278 00:00.000000 00:00:01.870278 00:00.000000 10 17 34 Fetch 125 43 00:00:00.255920 00:00.000000 00:00:00.005951 00:00.000000 0 42 3 Open Cursor 131 1 00:00:03.026060 00:00.000000 00:00:03.026060 00:00.000000 6 42 49 Close Cursor 137 1 00:00:00.000436 00:00.000000 00:00:00.000436 00:00.000000 0 0 0 ===== =============== ============ =============== ============ ======== ======= ======== SQL Totals: 46 00:00:05.152694 00:00.000000 00:00:00.112015 00:00.000000 16 101 86 STORED PROCEDURE CALL SUMMARY Call Avg Time in # SQL Total In-DB2 Avg In-DB2 Name Count Procedure Calls CPU Time CPU Time Locks Rows Pages Sorts Sort Time -------- ----- -------------- ----- ------------ ------------ -------- ------- -------- ------- ------------ JMWPROC1 2 00:00:02:41857 12 00:03.740556 00:01.870278 10 17 34 1 00:00:00.228 JMWPROC2 5 00:00:06:57361 14 00:20.617275 00:04.123455 41 12 79 0 00:00:00.000 SORT SUMMARY SQL Call Statement# Type Count #Part Sort Time Records Reads Inserts Deletes WFiles InitWF Merges Cols Keys -------------- ---------- ---- ----- ----- ------------ --------- --------- --------- --------- ------ ------ ------ ---- ---- OPEN CURSOR 131 ESAT 2 0 00:00:00.456 42 690 690 0 2 1 0 25 5

FIGURE 80. (Part 1 of 3) Application Trace Detail (Group by Program)

Application Trace D

etail

412O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 Application Trace Detail Page 2Run Date=mm/dd/yy Grouped by Program Run Time=15:49:50 Timestamp=1995-05-05-14.16.20.996304, Group=TDDB241G, Member=D411Sysid=SYSG, DB2id=D411, Planname=DSNESPCS, Connid=TSO, Corrid=STO210, Authid=STO210, Original Authid=STO210, Program=DSNESM68---------------------------------------------------------------------------------------------------------------------------------- SCAN SUMMARY Scan Scan Data Rows Rows Rows Rows Rows Rows Rows Mass Pages Pages Pages Database Pageset Count Type Type Processed Looked Qual/DM Qual/RD Updated Inserted Deleted Del Req Scanned Scan/Ref Del/Ref -------- -------- ----- ------ ----- --------- ------- ------- ------- -------- -------- -------- ------- ------- -------- ------- DSNDB06 SYSDBASE 5 Index Index 5 5 3 0 0 0 0 0 12 0 0 Data 2 2 0 0 0 0 0 0 2 0 0 DSNDB07 DSN4K01 1 Insert Work 0 0 0 0 42 0 0 0 3 0 0 1 Seq Work 42 42 42 42 0 0 0 0 3 0 0 DSN8D31A DSN8S31E 1 Seq Data 42 42 42 42 0 0 0 0 24 0 0 ===== ====== ===== ========= ======= ======= ======= ======== ======== ======== ======= ======= ======== ======= Scan Totals: 5 Index Index 5 5 3 0 0 0 0 0 12 0 0 Data 2 2 0 0 0 0 0 0 2 0 0 1 Insert Work 0 0 0 0 42 0 0 0 3 0 0 2 Seq Work 42 42 42 42 0 0 0 0 3 0 0 Data 42 42 42 42 0 0 0 0 24 0 0 LOCK SUMMARY Resource Identifier(s) Type Level Acquires Avoids Suspends Resumes Avg ElapTime/Susp Timeouts Deadlocks ------------------------------------------ ---- ----- -------- ------ -------- ------- ----------------- --------- --------- n/a ALL ANY 0 0 0 0 n/a 0 0 IPAG S 3 0 0 0 n/a 0 0 S 1 0 0 0 n/a 0 0 S 1 0 0 0 n/a 0 0 PSET IS 1 0 0 0 n/a 0 0 DPAG S 3 0 0 0 n/a 0 0 DTBS S 1 0 0 0 n/a 0 0 PSET IX 1 0 0 0 n/a 0 0 DTBS S 1 0 0 0 n/a 0 0 DPAG ANY 0 34 0 0 n/a 0 0 DSET IS 4 0 0 0 n/a 0 0 ======== ====== ======== ======= ================= ========= ========= Lock Totals: 16 34 0 0 n/a 0 0


Historical R


eports413

Application Trace D

etail

Omegamon II for DB2 V540 Application Trace Detail Page 3Run Date=mm/dd/yy Grouped by Program Run Time=15:49:50 Timestamp=1995-05-05-14.16.20.996304, Group=TDDB241G, Member=D411Sysid=SYSG, DB2id=D411, Planname=DSNESPCS, Connid=TSO, Corrid=STO210, Authid=STO210, Original Authid=STO210, Program=DSNESM68---------------------------------------------------------------------------------------------------------------------------------- BUFFER POOL I/O SUMMARY -Synchronous Read- ----Synchronous Write--- --------Asynchronous Read (Prefetch)------- -----Total I/O---- Database Pageset BP # Req AvgTime # Req AvgTime PgFlt # Req Pg/Rq AvgTime Fail SeqP LstP DynP # Req AvgTime -------- -------- ---- ------- ---------- ------- ---------- ----- ------- ----- --------- ---- ---- ---- ---- ------- ---------- DSNDB07 DSN4K01 0 1 000.072844 0 n/a 0% 1 8 00.045262 0% 100% 0% 0% 2 000.059053 DSN8D31A DSN8S31E 1 8 000.044856 0 n/a 0% 9 6 00.033228 0% 100% 0% 0% 17 000.038700 ======= ========== ======= ========== ===== ======= ===== ========= ==== ==== ==== ==== ======= ========== I/O Totals: 9 000.047965 0 n/a 0% 10 6 00.034432 0% 100% 0% 0% 19 000.040842 PARALLEL PROCESSING SUMMARY Query Group Task Average Task Average Task Rows Rows Rows / Rows Task Locks Pages Stmt # Block# # # Count Elapsed Time CPU Time Processed Produced WorkFile Consumed Suspends Acquired Processed ------ ------ ----- ---- ----- --------------- ------------ --------- -------- -------- -------- -------- -------- --------- 131 1 1 P 1 00:00:01.870278 00:00.000231 6696 - - - 10 7 66 1 1 00:00:02.235678 00:00.000123 3453 - - - 93 3 34 2 1 00:00:02.235678 00:00.000123 3243 - - - 1 3 32 2 P 1 00:00:01.769278 00:00.000334 1233 - - - 1 2 12 1 1 00:00:01.845345 00:00.000366 1234 - - - 2 6 12 2 1 00:00:01.845345 00:00.000366 3565 - - - 3 16 35 3 P 1 00:00:03.872348 00:00.000675 - 324 - 213 4 22 32 1 1 00:00:03.754278 00:00.000678 - 455 - 123 5 13 45 2 1 00:00:03.754278 00:00.000678 - 435 - 3 6 3 43 2 1 P 1 00:00:01.342575 00:00.000345 - 457 - 23 77 3 45 1 1 00:00:01.456258 00:00.000346 - 234 - 456 77 45 23 2 1 00:00:01.456258 00:00.000346 - 234 - 6788 76 275 123 3 1 00:00:01.234276 00:00.000457 - 456 - 234 3 23 45 138 1 1 P 23 00:00:04.234676 00:01.023434 - - 234 123 2 13 12 1 23 00:00:04.546788 00:01.023423 - - 345 354 6 34 35 2 23 00:00:04.546788 00:01.023423 - - 456 567 6 54 56


Application SQL Trace



IntroductionThis report displays the SQL activity that occurred for each thread that was active within the reporting period. No grouping is allowed.

You can specify filtering specifications. For example, use only records with an authid of TDO209; use only IFCIDs 0006, 0007, 0009, and 0010; use only those records for the thread that started on mm/dd/yy at 08:16:02.345678.

Default DDnameO2RPSQL

Default TitleApplication SQL Trace

Data SourceIFCIDs 22, 58-71, 73, 74, 84-89, 221, 222, 224, 233, 237



Order By ElementsNone

Select ElementsDB2ID, AUTHID, ORIGAUTH, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, IFCID, THREADSTART, UOWSTART, PGMSTART, SYSID, MEMBER, GROUP



Data Element

Following the thread identifiers is a trace of SQL calls issued during execution of the thread.

Timestamp The date and time (timestamp) that the thread began. (QWHSSTCK)









Event Time The time that the SQL statement began processing.

ProgName The application program name from which the SQL call was issued.

SQL Call The SQL statement type issued. (Derived from the IFCID number and statement type (QW00nnST))

Note: For Fetch SQL statements, the number of consecutive fetches executed before the next SQL statement type is printed in parentheses.

Stmt # The statement number of the SQL statement that was generated by the DB2 precompiler. (QW00nnSN from IFCIDs 53, 58–61, or 64–66)

Performance Trace Information

In-DB2 Time The amount of time that elapsed while executing in DB2 to process this SQL statement. (SSSS.THT)(END IFCID.QWHSSTCK-START IFCID.QWHSSTCK)

In-DB2 CPU The amount of CPU time used to process this SQL statement. (SSSS.THT)(END IFCID.QWHUCPU-START IFCID.QWHUCPU)

Curs The cursor name for this SQL activity, when applicable. (QW00nnCN from IFCIDs 59–61, or 64–66)

SQLcode SQL return code from the SQLCA. (ZW0058SQ)

Module Product signature or module that detected the error (in case of an error). (ZW0058SM)

ErrCodes Error codes from the SQLCA. (ZW0058SE)

WarnCodes Warning codes from the SQLCA.



For each SQL statement, a summary of any scan processing performed for the statement is printed, which includes the following fields:

Data Type The type of data pageset scanned. (QW0058ID)

Possible data types are as follows:

Data Data pageset.Index Index pageset.Work Workfile pageset.

Rows Process The number of rows processed by the data manager. (QW0058RP)





Rows Insertd The number of rows inserted. (QW0058IN)



Pages Scanned The total number of pages scanned by the data manager. (QW0058PS)


Rows Del/Ref The number of rows deleted due to enforcement of defined referential integrity constraints. (QW0058DR)

Type=Entry A stored procedure has been entered. Applies only to DB2 Version 4 and above. (QW0233EX=QW0233E)

Type=Exit A stored procedure has completed execution. Applies only to DB2 Version 4 and above. (QW0233EX=QW0233X)

ProcedureName Name of the stored procedure. Applies only to DB2 Version 4 and above. (QW0233PR)

SQLCA The formatted SQLCA provided on exit from the stored procedure. Applies only to DB2 Version 4 and above. (QW0233SQ)



Opts The options specified for this SQL statement. (QW0063OT)

Possible option values are as follows:

Apost Indicates apostrophes used for strings rather than quotes in COBOL or COBOL 2 SQL statements.

ApostSQL Indicates apostrophes used for strings rather than quotes in dynamic SQL statements.

Comma Indicates commas used for decimal points rather than periods.

Quote Indicates quotes used for strings rather than apostrophes in COBOL or COBOL 2 SQL statements.

QuoteSQL Indicates quotes used for strings rather than apostrophes in dynamic SQL statements.

HostLang The host language used for the SQL statement. (QW0063OT or QW0063HL)

Possible languages are as follows:� Assembler� C� COBOL� COBOL II� Dynamic SQL.� FORTRAN� PL/I

Text The SQL statement text. The text is truncated after 5000 bytes. (QW0063ST)

Plan The plan name for this SQL statement. (QW0022PN)

Cost The estimated cost for execution of this SQL statement. (QW0022OS)

DBID The database identifier. This value is translated to the database name, if possible, from the IFCID 105 and 107 records (if present). (QW0022DD)

OBID The record object identifier. (QW0022OB)

Table The Table name. (QW0022TN)

Index The Access Index name. (QW0022AN)

MatchCols The number of match columns for this table. (QW0022NM)

Note: This field is moved up a line in the display, for version 270, because it is part of the header fields for the mini-plan, not part of the mini-plan itself.

ColPtr If access type is Index Scan (I), then this field is the pointer to match column, PVBMATCH (else value is zero). (QW0022LR)

TBA If table is to be added, then this field is the index in TBA array of table (else value is zero for extra plans, if needed for Group-By or Order-By after a join). (QW0022BX)

IDX If access type is Index Scan (I), then this field is the index in IDX array (else value is zero). (QW0022ID)



PDA If access method is a type 2 join (1st table), then this field is the index in PDA array of join predicate (else value is zero). (QW0022DX)

Next This is a pointer value to the next mini-plan in the list for this SQL statement (a zero value indicates no more mini-plans). (QW0022TR)

AccMeth Indicates the access method for the mini-plan, which may be either 1st Table (accessed), Nested Loop (join), Merge Scan (join), or Hybrid (join). (QW0022OD)

AccType Indicates the access type for the table. The general access type is displayed as Table Space Scan or Index Scan followed by the detail access type code in parentheses. (QW0022YP)

NewJoin This field indicates sort flags for the “new” table in a join function. (QW0022AG)

Possible flag values are as follows:

Predicate Indicates sort key is Join Predicate (SORTN_JOIN in Plan table).

Order By Indicates sort key is Order-By list (SORTN_ORDERBY in Plan table).

Group By Indicates sort key is Group-By list (SORTN_GROUPBY in Plan table).

No Dups Indicates sort should eliminate duplicates.

Unique Indicates sort key is Set Function Unique column (SORTN_UNIQU in Plan table).

Prefetch Indicates prefetch (prefetch in the Plan table).

Result Indicates sort on result for Order-By.

ComJoin This field indicates flags for the Composite table in a join function. (QW0022A2)

Possible flag values are as follows:

Predicate Indicates sort key is Join Predicate (SORTC_JOIN in Plan table).

Order By Indicates sort key is Order-By list (SORTN_ORDERBY in Plan table).

Group By Indicates sort key is Group-By list (SORTN_GROUPBY in Plan table).

No Dups Indicates sort should eliminate duplicates.

Unique Indicates sort key is Set Function Unique column (SORTC_UNIQU in Plan table).

AccDegree This field indicates the degree of parallelism requested to access the new table. (QW0022P1)

AccPGrp This field indicates the parallel group identifier for accessing the new table. (QW0022P2)

JoinDegree This field indicates the degree of parallelism requested to join the new table. (QW0022P3)



JoinPGrp This field indicates the parallel group identifier for joining the new table. (QW0022P4)

PQueryRLFDisabled

Indicates whether the RLF has disabled query parallelism. (QW0022RP)


None Query parallelism has not been disabled by the RLF. (QW0022RP=X’00’)

Query I/O Query I/O parallelism has been disabled by the RLF. (QW0022RP=X’01’)

QueryCPU Query CPU parallelism has been disabled by the RLF. (QW0022RP=X’02’)

All All query parallelism has been disabled by the RLR. (QW0022RP=X’03’)

N/A Query parallelism is not applicable for this statement. (QW0022RP=X’FF’)

PageRangeScan Possible values are YES or NO. Applies only to DB2 Version 4 and above. (QW0022DT=X’40’)

MergeJoinCo Number of merge join columns. Applies only to DB2 Version 4 and above. (QW0022JC)

JoinType Indicates the type of join. Applies only to DB2 Version 4 and above. (QW0022JT)


Left Left outer join. (QW0022JT=’L’)Outer Full outer join. (QW0022JT=’F’)Inner Inner join. (QW0022JT=’blank’)None No join. (QW0022JT=’X’00’)

SortNewGrpID The group ID of the parallel group used for sorting the new table. Applies only to DB2 Version 4 and above. (QW0022P6)

SortCompGrpID The group ID of the composite parallel group used for sorting. Applies only to DB2 Version 4 and above. (QW0022P7)

ParallelMode Indicates whether CPU or Query I/O parallelism is being used, or neither is being used. Applies only to DB2 Version 4 and above. (QW0022PM)


CPU CPU parallelism. (QW0022PM=’C’)I/O Query I/O parallelism. (QW0022PM=’I’)None No parallelism. (QW0022PM=’X’00’)

Query# Query number. Applies only to DB2 Version 4 and above. (QW0022QN)

QueryBlk# Query block number. Applies only to DB2 Version 4 and above. (QW0022QB)

Plan# Plan number. Applies only to DB2 Version 4 and above. (QW0022PL)

TableCreator Table creator. Applies only to DB2 Version 4 and above. (QW0022CR)



IndexCreator Index creator. Applies only to DB2 Version 4 and above. (QW0022AC)

IndexOnly Possible values are as follows: (QW0022IO)

Yes Index only access. (QW0022IO=Yes)

No Not index only. (QW0022IO=No)

TblspcLockMode Indicates the tablespace lock mode. Applies only to DB2 Version 4 and above. (QW0022LM)

Timestamp Timestamp. Applies only to DB2 Version 4 and above. (QW0022TS)

Consistency Consistency token. Applies only to DB2 Version 4 and above. (QW0022CT)

CollectionId Collection ID. Applies only to DB2 Version 4 and above. (QW0022CT)

Table Corr Name Table correlation name. Applies only to DB2 Version 4 and above. (QW0022CN)

Member Data sharing group member name. Applies only to DB2 Version 4 and above. (QW0022GM)

Historical R


eports421

Application S

QL

Trace

Omegamon II for DB2 V540 Application SQL Trace Page 4Run Date=mm/dd/yy Run Time=15:53:05 Timestamp=1995-05-05-14.16.19.228686Sysid=SYSG, DB2id=D31A, Planname=DSNESPCS, Connid=TSO, Corrid=STO210, Authid=STO210, Original Authid=STO210----------------------------------------------------------------------------------------------------------------------------------Event Time ProgName SQL Call Stmt # Performance Trace Information--------------- -------- -------------- ------ -------------------------------------------------------------------------------------14:16:20.996304 DSNESM68 Prepare Cursor 71 InDB2-Time=00:00:01.870278 InDB2-CPU=00:00.000000 Curs=C1 Loc=D31A Coll=DSNESPCS SQLCA: SQLcode=0 Module=DSN ErrCodes=0,0,0,-1,0,0,0 WarnCodes=” “ Data Rows Rows Rows Rows Rows Rows Rows Mass Pages Pages Rows Type Process Looked Qual/DM Qual/RD Updated Insertd Deleted DelReq Scanned Scn/Ref Del/Ref ----- ------- ------- ------- ------- ------- ------- ------- ------ ------- ------- ------- Index 14 14 4 0 0 0 0 0 30 0 0 Data 3 3 0 0 0 0 0 0 4 0 014:16:21.085425 DSNESM68 Statement Text 71 Opts=Apost,Period,ApostSQL HostLang=SQL Text: SELECT * FROM DSN8310.EMP ORDER BY LASTNAME14:16:22.592411 DSNESM68 Mini-Plan 71 Plan=DSNESPCS Cost=84.54 DBID=DSN8D31A OBID=00014 Table=EMP Index= MatchCols=0 ColPtr=00000000 TBA=1 IDX=0 PDA=0 Next=7E792068 AccMeth=1st Table AccType=Table Space Scan (R) NewJoin=None, Prefetch ComJoin=None DBID=16448 OBID=00000 Table= Index= MatchCols=0 ColPtr=00000000 TBA=0 IDX=0 PDA=0 Next=00000000 AccMeth=1st Table AccType=Index Scan () NewJoin=None ComJoin=Order By PQueryRLFDisabled=QueryI/O PageRangeScan=No MergeJoinCol=2 JoinType=None SortNewGrpID=0 SortCompGrpID=0 ParallelMode=None Query#=0 QueryBlk#=0 Plan#=0 TableCreator=xxxxxxxx IndexCreator=xxxxxxxx IndexOnly=No TblspcLockMode=xxx TableCorrName= Member= Consistency=149EEA901A79FE48 CollectionID=DSNESPCS Timestamp=AB064F2C932AA00414:16:22.871314 DSNESM68 Open Cursor 131 InDB2-Time=00:00:03.026060 InDB2-CPU=00:00.000000 Curs=C1 Loc=D31A Coll=DSNESPCS SQLCA: SQLcode=0 Module=DSN ErrCodes=0,0,0,-1,0,0,0 WarnCodes=” “ Data Rows Rows Rows Rows Rows Rows Rows Mass Pages Pages Rows Type Process Looked Qual/DM Qual/RD Updated Insertd Deleted DelReq Scanned Scn/Ref Del/Ref ----- ------- ------- ------- ------- ------- ------- ------- ------ ------- ------- ------- Data 42 42 42 42 0 0 0 0 46 0 0 Work 0 0 0 0 0 42 0 0 3 0 014:16:22.871327 DSNESM68 Stored Proc 131 Type=Entry ProcedureName=JMWPROC1 InDB2-Time=00:00:03.032601 InDB2-CPU=00:00.00000014:16:25.903928 DSNESM68 Stored Proc 131 Type=Exit ProcedureName=JMWPROC1 InDB2-Time=00:00:03.032601 InDB2-CPU=00:00.000000 SQLCA: SQLcode=0 Module=DSN ErrCodes=0,0,0,-1,0,0,0 WarnCodes=” “

FIGURE 83. Application SQL Trace Report

Application Event Trace



IntroductionThis report displays the contents of performance trace records for each thread active within the reporting period. It provides detailed information about events that have occurred for a specific application.

For record pairs, such as begin and end I/O, matching will be done, and pertinent information such as elapsed and CPU times will be provided with the end record data.

No grouping is allowed, but you can specify filtering specifications. For example, select only those records with an authid of TDO209; select only IFCIDs 6, 7, 9, and 10; or select only those records for the thread that started at mm/dd/yy at 08:16:02.345678.

Default DDnameO2RPAET

Default TitleApplication Event Trace

Data SourceIFCIDs 73 (CREATE THREAD) and 74 (TERMINATE THREAD) plus whatever IFCIDs are specified in selection criteria. These may include:

IFCIDs 6–10, 15–18, 21, 22, 44, 45, 53, 54, 58–71, 73, 74, 84–89, 95, 96, 221, 222, 231, 233, 251, and 259


IFCIDs 68–71, 73, 74, 84–89, if you specify SELECT UOWSTART or PGMSTART



If you specify TIME, the first record of the thread will be ordered by time and the rest of the records will be ordered by timestamp within the thread.

Select ElementsDB2ID, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, AUTHID, ORIGAUTH, IFCID, THREADSTART, UOWSTART, PGMSTART, DBID, PSID, SYSID, MEMBER, GROUP



Data Elements

If it is a distributed thread, distributed header information also will be included.

Following the thread identifiers is a trace of all events occurring during execution of the thread. For each performance trace record, the following items are reported:

At this point in the report, the performance trace information displayed will depend on the record’s IFCID. The following describes some of the fields that may be displayed.

In general, all NON-SERVICEABILITY fields within the particular record being reported will be displayed. Certain displays will be omitted if the field contains no significant information (blank or zero) and the field is not part of a tabular format display. Tabular format displays may be omitted, as a whole, if all of the fields that would be reported contain no significant information (blank or zero).

Start Time The date and time (timestamp) that the application thread began execution. (QWHSSTCK of first IFCID record for first Unit of Work in thread)









Event Time The time that the event occurred. (QWHSSTCK)

IFCID The IFCID of the performance trace record being reported. (QWHSIID)

Event Type The name of the event that occurred. For SQL calls, this is the SQL statement type issued. (Derived from IFCID # and statement type (QW00nnST))

Performance Trace Information

Stmt The statement number of the SQL statement that was generated by the DB2 precompiler. (QW00nnSN from IFCIDs 53, 58–61, or 64–66)

Program The application program name that generated the event, either directly or indirectly. Package name qualifiers for the program are displayed in the form location.collectionid.packageid, and the label will be changed to Pkg. (QW00nnPN from IFCIDs 53, 58–61, or 64–66)

ElapTime The total elapsed time between start and end of the event reported (for example, the SQL statement). This information is reported for event-end record types.(END.QWHSSTCK-START.QWHSSTCK as MM:SS.THTTH)



For a lock operation record the following data may be reported:

DB The name of the database on which the operation reported by this record was performed (if IFCIDs 105/107 are available) or the database identifier number (if IFCIDs 105/107 are not available). (QW00nnDB)

PS The name of the pageset (tablespace) on which the operation reported by this record was performed (if IFCIDs 105/107 are available) or the pageset identifier number (if IFCIDs 105/107 are not available). (QW00nnPS)

Recid The record identifier number for the table on which the operation reported by this record was performed. (QW00nnOB)

Lock Information:

Type The lock type acquired. There will be one entry for every lock type acquired. (QW0021KT)

Possible lock types are:



For a lock suspension, the following information is displayed:

For a lock resume, the following information is displayed::dt.Reason

Level The level of the lock. (QW0021ST)

Possible lock levels are as follows:

ANY Change or unlock functions may use this lock level.IS Intent share lock on tablespace.IX Intent exclusive lock on tablespace.NSU Nonshared update lock.S Shared lock on page or tablespace.SIX Share with intent exclusive lock on tablespace.U Update lock on page or tablespace.US Unprotected shared lock.X Exclusive lock on page or tablespace.

Resource The resource held by the lock. The content of this field depends on the type of lock that was requested. Only the information that applies to the type of resource being locked is shown. For example, for a database lock, only the database identifier is displayed; while for a data page lock, the database and pageset identifier is displayed; each individual page lock is not listed. (QW0021RN - see the following list for subfields used)

Possible fields are as follows:

COLL The collection ID of the requested resource. This applies only to skeleton package table and collection lock types. (QW0021RN)

DB The database of the requested resource. (QW0021KD)

PART The partition number of the requested resource. (QW0021K2)

PKG The package name of the requested resource. This name is decompressed from the resource name, along with the collection ID (displayed with COLL label), and concatenated with a consistency token. This applies only to skeleton package table lock types. (QW0021RN)

PLAN The plan name of the requested resource. This applies only to skeleton cursor table lock types. (QW0021KD, QW0021KP, and QW0021KR)

PS The pageset of the requested resource. (QW0021KP)

TABLE The table of the requested resource. (QW0021KB)

Reason The reason for the suspension. (QW0044WS)

Reason The reason for the resume. (QW0045R)



I/O Request Information:

For an I/O operation, the following additional data is reported:

Scan or SQL Information:

For a scan end or SQL end record, the following tabular data may be reported:

Pool Buffer pool identifier where pages are kept in storage. (QW00nnBP)

Type Indicates whether the I/O was synchronous or asynchronous. An asynchronous read (prefetch) indicates the type of prefetch (sequential, list, or dynamic).

#PF Number of page faults anticipated (for write request only). (QW00nnPI)

#Pgs Number of pages read or written. (QW00nnNP)

RC The Media Manager return code from the I/O request. (QW00nnMM)

Data Type The type of data being scanned. (QW0018ID)

Possible data types are as follows:

Data Data pageset.Index Index pageset.Work Workfile pageset.

Rows Process The number of rows processed by the data manager. (QW0018RP)





Rows Insertd The number of rows inserted. (QW0018IN)



Pages Scan’d The total number of pages scanned by the data manager. (QW0018PS)


Rows Del/Ref The number of rows deleted due to enforcement of defined referential integrity constraints. (QW0018DR)



Sort Information:

For a sort end record the following data may be reported:

Type The type of sort performed. (QW0096TS (of the outermost sort, if there are nested sorts). Possible sort types are as follows:

ESA ESA sort using hardware sort assist instructions.

ESAT Combination ESA tag sort.

GRP Groupby sort.

REG Regular sort (not ESA, groupby, tag, or RID list sort).

TAG Tag sort.

Sort Time The amount of elapsed time spent in sort processing. (END.QWHSSTCK-START.QWHSSTCK)

Records The total number of records sorted. (QW0096NR sum)

Reads The number of records retrieved from a workfile during sort processing. (QW0096RD sum)

Inserts The number or records inserted into a workfile during sort processing. (QW0096IN sum)

WFiles The number of workfiles used during sort processing. (QW0096WF sum)

Historical R


eports429

Application E

vent Trace

Omegamon II for DB2 V540 Application Event Trace Page 1Run Date=mm/dd/yy Run Time=15:54:04 Timestamp=1995-05-05-14.00.40.583211 ACE=069BFB48Sysid=SYSG, DB2id=D31A, Planname=DSNESPCS, Connid=TSO, Corrid=STO210, Authid=STO210, Original Authid=STO210---------------------------------------------------------------------------------------------------------------------------------- Event Time IFCID & Event Type Performance Trace Information--------------- ------------------------- ------------------------------------------------------------------------------------------14:00:40.583211 -96 DB2 Unit-of-Work Mark * * * generated by Omegamon II for DB2 (for internal use) * * *14:00:40.583211 72 Create Thread Start ElapTime=00:00.100145 Plan=DSNESPCS IDRopt=DSNESPCS ConnType=NO14:00:40.622122 21 Detail Lock Request Type=SKCT Plan=DSNESPCS Func=Lock ReqType=Unconditional,Acquire,Group,Result RsrcHash=00001620 State=S Dur=Plan ExtReqType=000000 IRLM: RetCode=0 Subcodes=00000000 RetToken=069014C4 OwnWU=000000FB069BFB48 ReqWU=006600FB00000000 DB2token=00A2800000A25FC014:00:40.682517 112 Allied Thread Plan Attributes TargetPlan=DSNESPCS IsoLevel=CS Acquire=Use Release=Commit14:00:40.683356 73 Create Thread End ElapTime=00:00.100145 Plan=DSNESPCS IDRopt=DSNESPCS ConnType=NO RetCode=0 RsnCode=0 Wt=1 QLen=014:00:44.433784 44 Lock Suspend/Id Call ElapTime=00:00.041323 Type=ALL Resource=ALL Func=Change ReqType=Unconditional,Acquire,Group,CountBy RsrcHash=00000000 State=ANY Dur=Manual+1 SuspRsn=LC RsmRsn=N14:00:44.475108 45 Lock Suspend/Id Resume ElapTime=00:00.041323 Type=ALL Resource=ALL Func=Change ReqType=Unconditional,Acquire,Group,CountBy RsrcHash=00000000 State=ANY Dur=Manual+1 SuspRsn=LC RsmRsn=N14:00:44.475593 21 Detail Lock Request Type=ALL Resource=ALL Func=Change ReqType=Unconditional,Acquire,Group,CountBy RsrcHash=00000000 State=ANY Dur=Manual+1 ExtReqType=000000 IRLM: RetCode=0 Subcodes=00000000 RetToken=00000000 OwnWU=000000FB069BFB48 ReqWU=006600FB00000000 DB2token=00A2800000A25FC0

FIGURE 84. Application Trace (Events) Report




IntroductionThis report details the logical (page) access to bufferpools from an application point of view.


� determining volume and type of activity for DB2 pagesets

� determining I/O performance for DB2 pagesets

� determining trends in volume or performance related to I/O activity

Data SourcePerformance Class(4), IFCID 6/7, 8/9, 198

IFCIDs 105 and 107 to convert database and pageset ID’s




Select ElementsDB2ID, IFCID, DBID, PSID, BPID, SYSID, MEMBER, GROUP

Data Elements

Start Date The date that the application began execution. (QWHSSTCK)

Hour The beginning hour that the application began execution. (ZWHSHOUR)



Database Database name (if IFCID’s 105/107 are available), or database identifier number (if IFCID’s 105/107 are not available).(QW0006DB/QW0008DB/QW0198DB –> QW0105DB or QW0107DB –> QW0105DN or QW0107DN)



Pageset Pageset (that is, tablespace) name (if IFCID’s 105/107 are available), or pageset identifier number (if IFCID’s 105/107 are not available).(QW0006OB/QW0008OB/QW0198OB –> QW0105OB or QW0107OB –> QW0105TN or QW0107TN)


GetPage Requests:

# Req Total number of getpage requests. (QW0198FC= G count)

NoRead Total number of getpage requests that specified the noread option. (QW0198PS= N count)

Hit Percentage of getpage requests that encountered a page hit in the bufferpool. (QW0198PS= H count/total getpage # req)

Seq Percentage of getpage requests that specified an access type of sequential access. (QW0198AT= S count/total getpage # req)

Rand Percentage of getpage requests that specified an access type of random access. (QW0198AT= R count/total getpage # req)

List Percentage of getpage requests that specified an access type of RID list access. (QW0198AT= L count/total getpage # req)

Release Requests:

# Req Total number of page release requests. (QW0198FC= R count)

Std Percentage of release requests that specified a request option of standard release. (QW0198AT= N count/total release # req)

Dest Percentage of release requests that specified a request option of destructive release. (QW0198AT= D count/total release # req)

MRU Percentage of release requests that specified a request option of MRU scheme release. (QW0198AT= M count/total release # req)

# Set Writes Total number of set write intent requests. (QW0198FC= S count)

Synchronous:

# Read Total number of synchronous read I/O requests. (6/7 pair count,QW0006F= R)

# Write Total number of synchronous write I/O requests. (8/9 pair count)

Asynchronous:

# Read Total number of asynchronous read I/O requests. QW0007AC (ACE of requestor) is used to order the record with the requesting thread, rather than the system ACE used to perform the request. (6/7 pair count,QW0006F= S, L, or D)

SeqP Percentage of asynchronous read requests that specified Sequential Prefetch processing. (QW0006F= S count/total asynch # read)

LstP Percentage of asynchronous read requests that specified List Prefetch processing. (QW0006F= L count/total asynch # read)

DynP Percentage of asynchronous read requests that specified Dynamic Prefetch processing. (QW0006F= D count/total asynch # read)

Application B

uffer Pool Access

432O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 Application Buffer Pool Access Page=1Report Date=mm/dd/yy By Hour Report Time=12.43.07 Start Date=mm/dd/yy, Hour=07---------------------------------------------------------------------------------------------------------------------------------- --------GetPage Requests---------- ---Release Requests--- # Set --Synchronous-- -----Asynchronous----- Database Pageset BP # Req NoRead Hit Seq Rand List # Req Std Dest MRU Writes # Read # Write # Read SeqP LstP DynP -------- -------- ---- ------- ------ ---- ---- ---- ---- ------- ---- ---- ---- ------- ------- ------- ------- ---- ---- ---- DSNDB01 SCT02 0 60 0 100% 0% 0% 0% 10 7% 13% 0% 0 60 0 60 0% 0% 0% DSNDB01 SYSUTIL 0 16 0 100% 0% 0% 0% 2 3% 8% 0% 0 16 0 16 0% 0% 0% DSNDB01 SYSLGRNG 0 35 0 100% 0% 0% 0% 0 0% 0% 0% 0 35 0 35 0% 0% 0% DSNDB06 DSNAPH01 2 669 4 100% 75% 10% 15% 101 2% 3% 0% 0 643 5 643 75% 10% 15% DSNDB06 DSNDTX01 9 9 0 100% 0% 0% 0% 2 1% 1% 0% 0 9 0 9 0% 0% 0% DSNDB04 SUKTSPT1 32K 220 7 100% 100% 0% 0% 1 1% 0% 0% 0 212 0 212 100% 0% 0% DSN8D22A XEMP2 32K1 98 7 100% 100% 0% 0% 102 21% 70% 0% 0 90 0 90 100% 0% 0%

FIGURE 85. Application Buffer Pool Access (Group by HOUR Report)




IntroductionThis report displays information about I/O activity that occurred within the DB2 buffer pools.


� determining the volume and type of activity for a specific application or person

� characterizing the I/O performance for a specific application, plan, AUTHID, connection, or person

� identifying trends in volume or performance related to I/O activity

Default DDnameO2RPABP

Default TitleApplication Buffer Pool I/O

Data SourcePerformance Class (4): IFCID pairs 6/7, 8/9, 10/9

IFCIDs 105 and 107 to convert database and pageset IDs.

IFCIDs 73, and 74, if you specify Group by thread or Select threadstart

IFCIDs 68, 69, 70, 71, 73, 74, 84, 85, 86, 87, 88, and 89, if you specify Group By UNIT_OF_WORK or PROGRAM, or Select UOWSTART or PGMSTART


Group by ElementsDB2ID, AUTHID, ORIGAUTH, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, HOUR, DAY, THREAD, UNIT_OF_WORK, PROGRAM, SYSID, MEMBER, GROUP

Order by ElementsDB2ID, AUTHID, ORIGAUTH, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, TIME, SYSID, MEMBER, GROUP



Select ElementsDB2ID, AUTHID, ORIGAUTH, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, IFCID, CLASS, SUBJECT, THREADSTART, UOWSTART, PGMSTART, DATABASE, PAGESET, SYSID, MEMBER, GROUP



Data Elements







Database Database name (if IFCIDs 105/107 are available) or database identifier number (if IFCIDs 105/107 are not available). (QW0006DB/QW0008DB/QW0010DB)

Pageset Pageset (tablespace) name (if IFCIDs 105/107 are available) or pageset identifier number (if IFCIDs 105/107 are not available). (QW0006OB/QW0008OB/QW0010OB)


Synchronous Read

# Req Total number of synchronous read I/O requests. (6/7 record pairs, QW0006F = R)

AvgTime Average elapsed time for synchronous read I/O requests. (6/7 pairs, QW0006F = R, QWHSSTCK)

Synchronous Write

# Req Total number of synchronous write I/O requests. (8/9 record pairs)

AvgTime Average elapsed time for synchronous write I/O requests. (8/9 record pairs, QWHSSTCK)

PgFlt Percentage of pages having synchronous writes performed that required paging before I/O could be performed. (QW0008PI)

Asynchronous Read (Prefetch)

# Req Total number of asynchronous read I/O requests. QW0007AC (ACE of requestor) is used to order the record with the requesting thread, rather than the system ACE used to perform the request. (6/7 record pairs, QW0006F = S, L, or D)

Pg/Req Average number of pages per asynchronous read request issued. (QW0007NP - average of all requests where QW0007NP is not zero)

AvgTime Average elapsed time for asynchronous read I/O requests. (6/7 record pairs, QW0006F = S, L, or D, QWHSSTCK)

Fail Percentage of asynchronous read requests resulting in no pages read. (QW0007NP = 0)



SeqP Percentage of asynchronous read requests that specified sequential prefetch processing. (QW0006F = S)

LstP Percentage of asynchronous read requests that specified list prefetch processing. (QW0006F = L)

DynP Percentage of asynchronous read requests that specified dynamic prefetch processing. (QW0006F = D)

Total I/O

# Req Total number of synchronous read, synchronous write, and asynchronous read I/O requests. (6/7, 8/9 record pairs)

AvgTime Average elapsed time for each I/O request. (6/7, 8/9 record pairs, QWHSSTCK)

Historical R


eports437

Application B

uffer Pool I/O

OMEGAMON FOR DB2 V540 APPLICATION BUFFER POOL IO PAGE=1REPORT DATE=mm/dd/yy BY HOUR, AUTHID, PLANNAME, CONNID, CORRID REPORT TIME=12.43.07 Start Date=mm/dd/yy, Hour=12, Authid=TDO209, Planname=DSNESPRR, Connid=TSO, Corrid=TDO209B---------------------------------------------------------------------------------------------------------------------------------- --Synchronous Read- ----Synchronous Write--- ---------Asynchronous Read (Prefetch)-------- -----Total I/O----Database Pageset BP # Req AvgTime # Req AvgTime PgFlt # Req Pg/Req AvgTime Fail SeqP LstP DynP # Req AvgTime-------- -------- ---- ------- ----------- ------- ---------- ----- ------- ------ ---------- ---- ---- ---- ---- ------- ----------H2DBASE H2TSACCT 0 643 0.123456 5 0.431875 0% 26 4 0.122446 0% 75% 10% 15% 674 0.131636H2DBASE H2TSPARM 0 643 0.123456 5 0.431875 0% 26 4 0.122446 0% 75% 10% 15% 674 0.131636H2DBASE H2TSSTAT 32K 643 0.123456 5 0.431875 0% 26 4 0.122446 0% 75% 10% 15% 674 0.131636 Start Date=mm/dd/yy, Hour=12, Authid=TDO210, Planname=DSNESPRR, Connid=TSO, Corrid=TDO210------------------------------------------------------------------------------------------------------------------------------------ --Synchronous Read- ----Synchronous Write--- ---------Asynchronous Read (Prefetch)-------- -----Total I/O----Database Pageset BP # Req AvgTime # Req AvgTime PgFlt # Req Pg/Req AvgTime Fail SeqP LstP DynP # Req AvgTime-------- -------- ---- ------- ----------- ------- ---------- ----- ------- ------ ---------- ---- ---- ---- ---- ------- ----------DSN8D22A XEMP1 2 643 0.123456 5 0.431875 0% 26 4 0.122446 0% 75% 10% 15% 674 0.131636DSN8D22A XPROJ1 32K9 643 0.123456 5 0.431875 0% 26 4 0.122446 0% 75% 10% 15% 674 0.131636 Start Date=mm/dd/yy, Hour=13, Authid=TDO209, Planname=DSNESPRR, Connid=TSO, Corrid=TDO209------------------------------------------------------------------------------------------------------------------------------------ --Synchronous Read- ----Synchronous Write--- ---------Asynchronous Read (Prefetch)-------- -----Total I/O----Database Pageset BP # Req AvgTime # Req AvgTime PgFlt # Req Pg/Req AvgTime Fail SeqP LstP DynP # Req AvgTime-------- -------- ---- ------- ----------- ------- ---------- ----- ------- ------ ---------- ---- ---- ---- ---- ------- ----------H2DBASE H2TSACCT 32K 643 0.123456 5 0.431875 0% 26 4 0.122446 0% 75% 10% 15% 674 0.131636H2DBASE H2TSPARM 0 643 0.123456 5 0.431875 0% 26 4 0.122446 0% 75% 10% 15% 674 0.131636H2DBASE H2TSSTAT 1 643 0.123456 5 0.431875 0% 26 4 0.122446 0% 75% 10% 15% 674 0.131636 Start Date=mm/dd/yy, Hour=13, Authid=TDO210, Planname=DSNESPRR, Connid=TSO, Corrid=TDO210------------------------------------------------------------------------------------------------------------------------------------ --Synchronous Read- ----Synchronous Write--- ---------Asynchronous Read (Prefetch)-------- -----Total I/O----Database Pageset BP # Req AvgTime # Req AvgTime PgFlt # Req Pg/Req AvgTime Fail SeqP LstP DynP # Req AvgTime-------- -------- ---- ------- ----------- ------- ---------- ----- ------- ------ ---------- ---- ---- ---- ---- ------- ----------DSN8D22A XEMP1 2 643 0.123456 5 0.431875 0% 26 4 0.122446 0% 75% 10% 15% 674 0.131636DSN8D22A XPROJ1 32K9 643 0.123456 5 0.431875 0% 26 4 0.122446 0% 75% 10% 15% 674 0.131636

FIGURE 86. Application Buffer Pool Report (Group by HOUR, AUTHID, PLANNAME, CONNID, CORRID)




IntroductionThis report details the logical (page) accesses to DB2 bufferpools from a system point of view.


� determining volume and type of activity for a DB2 pagesets

� determining I/O performance for DB2 pagesets

� determining trends in volume or performance related to I/O activity

Data SourcePerformance Class(4), IFCID’s 6–10, and 198

IFCID’s 105 and 107 to convert database and pageset ID’s




Select ElementsDB2ID, IFCID, DBID, PSID, BPID, SYSID, MEMBER, GROUP



Data Elements





Database Database name (if IFCID’s 105/107 are available), or database identifier number (if IFCID’s 105/107 are not available). (QW0006DB/QW0008DB/QW0010DB/QW0198DB –> QW0105DB or QW0107DB –> QW0105DN or QW0107DN)

Pageset Pageset (that is, tablespace) name (if IFCID’s 105/107 are available), or pageset identifier number (if IFCID’s 105/107 are not available). (QW0006OB/QW0008OB/QW0010OB/QW0198OB –> QW0105OB or QW0107OB –> QW0105TN or QW0107TN)

BP Buffer pool identifier where pages are kept in storage. (QW0006BP/QW0008BP/QW0010BP/QW0198BP)

GetPage Requests:

# Req Total number of getpage requests. (QW0198FC= G count)

NoRd Total number of getpage requests that specified the noread option. (QW0198PS= N count)

Hit Percentage of getpage requests that encountered a page hit in the bufferpool. (QW0198PS= H count/total getpage # req)

Seq Percentage of getpage requests that specified an access type of sequential access. (QW0198AT= S count/total getpage # req)

Rand Percentage of getpage requests that specified an access type of random access. (QW0198AT= R count/total getpage # req)

List Percentage of getpage requests that specified an access type of RID list access. (QW0198AT= L count/total getpage # req)

Release Requests:

# Req Total number of page release requests. (QW0198FC= R count)

Std Percentage of release requests that specified a request option of standard release. (QW0198AT= N count/total release # req)

Dest Percentage of release requests that specified a request option of destructive release. (QW0198AT= D count/total release # req)

MRU Percentage of release requests that specified a request option of MRU scheme release. (QW0198AT= M count/total release # req)

# Set Writes Total number of set write intent requests. (QW0198FC= S count)



Synchronous:

# Read Total number of synchronous read I/O requests. (6/7 pair count,QW0006F= R)

# Wrt Total number of synchronous write I/O requests. (8/9 pair count)

Asynchronous:

# Read Total number of asynchronous read I/O requests. QW0007AC (ACE of requestor) is used to order the record with the requesting thread, rather than the system ACE used to perform the request. (6/7 pair count,QW0006F= S, L, or D)

SeqP Percentage of asynchronous read requests that specified Sequential Prefetch processing. (QW0006F= S count/total asynch # read)

LstP Percentage of asynchronous read requests that specified List Prefetch processing. (QW0006F= L count/total asynch # read)

DynP Percentage of asynchronous read requests that specified Dynamic Prefetch processing. (QW0006F= D count/total asynch # read)

# Write Total number of asynchronous write I/O requests. (10/9 pair count)

Historical R


eports441

System

Buffer Pool A

ccess

Omegamon II for DB2 V540 System Buffer Pool Access Page=1Report Date=mm/dd/yy By Hour Report Time=12.43.07 Start Date=mm/dd/yy, Hour=07---------------------------------------------------------------------------------------------------------------------------------- -------GetPage Requests--------- ---Release Requests--- # Set -Synchronous- ---------Asynchronous--------- Database Pageset BP # Req NoRd Hit Seq Rand List # Req Std Dest MRU Writes # Read # Wrt # Read SeqP LstP DynP # Write -------- -------- ---- ------- ---- ---- ---- ---- ---- ------- ---- ---- ---- ------- ------- ----- ------- ---- ---- ---- ------- DSNDB01 SCT02 0 60 0 100% 0% 0% 0% 10 7% 13% 0% 0 60 0 60 0% 0% 0% 10 DSNDB01 SYSUTIL 0 16 0 100% 0% 0% 0% 2 3% 8% 0% 0 16 0 16 0% 0% 0% 2 DSNDB01 SYSLGRNG 0 35 0 100% 0% 0% 0% 0 0% 0% 0% 0 35 0 35 0% 0% 0% 0 DSNDB06 DSNAPH01 2 669 4 100% 75% 10% 15% 101 2% 3% 0% 0 643 5 643 75% 10% 15% 101 DSNDB06 DSNDTX01 9 9 0 100% 0% 0% 0% 2 1% 1% 0% 0 9 0 9 0% 0% 0% 2 DSNDB04 SUKTSPT1 32K 220 7 100% 100% 0% 0% 1 1% 0% 0% 0 212 0 212 100% 0% 0% 1 DSN8D22A XEMP2 32K1 98 7 100% 100% 0% 0% 102 21% 70% 0% 0 90 0 90 100% 0% 0% 102

FIGURE 87. System Buffer Pool Access Report (Group by HOUR)

System Buffer Pool I/O



IntroductionThis report displays information about I/O activity that occurred within the DB2 buffer pools.


� determining the volume and type of activity for DB2 pagesets

� characterizing the I/O performance for DB2 pagesets


Default DDnameO2RPSBP

Default TitleSystem Buffer Pool I/O

Data SourcePerformance Class (4), IFCIDs 6–10

IFCID 105 and 107 to convert database and pageset IDs



Select ElementsDB2ID, IFCID, DBID, PSID, SYSID, MEMBER, GROUP




Data Elements


Hour The beginning hour that the application began execution.

Database Database name (if IFCIDs 105/107 are available), or database identifier number (if IFCIDs 105/107 are not available). (QW0006DB/QW0008DB/QW0010DB)

Pageset Pageset (tablespace) name (if IFCIDs 105/107 are available), or pageset identifier number (if IFCIDs 105/107 are not available). (QW0006OB/QW0008OB/QW0010OB)


Synchronous Read:

# Req Total number of synchronous read I/O requests. (6/7 record pairs, QW0006F = R)

AvgTime Average elapsed time for synchronous read I/O requests. (6/7 pairs, QW0006F = R, QWHSSTCK)

Synchronous Write

# Req Total number of synchronous write I/O requests. (8/9 record pairs)

AvgTime Average elapsed time for synchronous write I/O requests. (8/9 pairs, QWHSSTCK)

Asynchronous Read (Prefetch):

# Req Total number of asynchronous read I/O requests. QW0007AC (ACE of requestor) is used to order the record with the requesting thread, rather than the system ACE used to perform the request. (6/7 record pairs, QW0006F = S, L, or D)

Pg/Rq Average number of pages per read request issued. (QW007NP/#REQ)

AvgTime Average elapsed time for asynchronous read I/O requests. (6/7 pairs, QW0006F = S, L, or D, QWHSSTCK)

Fail Percentage of asynchronous read requests resulting in no pages read. (QW0007NP)

SeqP Percentage of asynchronous read requests that specified sequential prefetch processing. (QW0006F = S)

LstP Percentage of asynchronous read requests that specified list prefetch processing. (QW0006F = L)

DynP Percentage of asynchronous read requests that specified dynamic prefetch processing. (QW0006F = D)

Asynchronous Write:

# Req Total number of asynchronous write I/O requests. (10/9 pairs)

Pg/Rq Average number of pages per write request issued. (QW0010WR)



AvgTime Average elapsed time for asynchronous write I/O requests. (10/9 pairs, QWHSSTCK)

Write PFlt Percentage of pages for all writes performed that required paging before I/O could be performed. (QW0010PI)

Historical R


eports445

System

Buffer Pool I/O

Omegamon II for DB2 V540 System Buffer Pool I/O Page 1 Run Date=mm/dd/yy Grouped by Hour Run Time=14:29:20 Start Date=mm/dd/yy, Hour=14 Sysid=SYSG ---------------------------------------------------------------------------------------------------------------------------------- -----Read---Synchronous---Write---- --------Asynchronous Read (Prefetch)------- --Asynchronous Write-- Write Database Pageset BP # Req AvgTime # Req AvgTime # Req Pg/Rq AvgTime Fail SeqP LstP DynP # Req Pg/Rq AvgTime PFlt -------- -------- ---- ------- --------- ------- --------- ------- ----- --------- ---- ---- ---- ---- ------- ----- --------- ---- CANDLE H2IXAUD1 0 2 00.027110 0 n/a 0 0 n/a 0% 0% 0% 0% 0 0 n/a 0% CANDLE H2IXAUD2 0 2 00.022650 0 n/a 0 0 n/a 0% 0% 0% 0% 0 0 n/a 0% CANDLE H2IXAUD3 0 2 00.037273 0 n/a 0 0 n/a 0% 0% 0% 0% 0 0 n/a 0% CANDLE H2IXAUD4 0 2 00.025397 0 n/a 0 0 n/a 0% 0% 0% 0% 0 0 n/a 0% CANDLE H2IXAUD6 0 2 00.040554 0 n/a 0 0 n/a 0% 0% 0% 0% 0 0 n/a 0% CANDLE H2IXAUD7 0 2 00.024132 0 n/a 0 0 n/a 0% 0% 0% 0% 0 0 n/a 0% CANDLE H2TSAUD 0 1 00.115169 0 n/a 0 0 n/a 0% 0% 0% 0% 0 0 n/a 0% DPSS08 IPSSTST1 0 0 n/a 0 n/a 0 0 n/a 0% 0% 0% 0% 1 1 00.018607 100% DPSS08 SPSSTEST 0 0 n/a 1 00.017870 0 0 n/a 0% 0% 0% 0% 1 3 00.019772 75% DSNDB01 DBD01 0 1 00.126689 1 00.039123 0 0 n/a 0% 0% 0% 0% 2 2 00.062923 66% DSNDB01 DSNLUX01 0 1 00.561749 0 n/a 0 0 n/a 0% 0% 0% 0% 1 1 00.096036 0% DSNDB01 DSNLUX02 0 1 00.044255 0 n/a 0 0 n/a 0% 0% 0% 0% 0 0 n/a 0% DSNDB01 SYSLGRNG 0 173 00.033119 0 n/a 0 0 n/a 0% 0% 0% 0% 4 1 00.116429 16% DSNDB01 SYSUTILX 0 4 00.348021 1 00.020588 1 14 00.048274 0% 0% 0% 100% 1 2 00.214438 0% DSNDB06 DSNADH01 0 3 00.035206 0 n/a 0 0 n/a 0% 0% 0% 0% 1 1 00.215255 100% DSNDB06 DSNAGH01 0 3 00.011502 0 n/a 0 0 n/a 0% 0% 0% 0% 0 0 n/a 0% DSNDB06 DSNAPH01 0 2 00.024336 0 n/a 0 0 n/a 0% 0% 0% 0% 1 1 00.020331 100% DSNDB06 DSNAPX01 0 0 n/a 0 n/a 0 0 n/a 0% 0% 0% 0% 1 1 00.035567 100% DSNDB06 DSNATX01 0 0 n/a 0 n/a 0 0 n/a 0% 0% 0% 0% 1 6 00.195359 100% DSNDB06 DSNATX02 0 5 00.031380 0 n/a 0 0 n/a 0% 0% 0% 0% 3 2 00.121871 50% DSNDB06 DSNAUH01 0 3 00.030395 0 n/a 0 0 n/a 0% 0% 0% 0% 0 0 n/a 0% DSNDB06 DSNDCX01 0 0 n/a 0 n/a 0 0 n/a 0% 0% 0% 0% 3 2 00.095232 100% DSNDB06 DSNDDH01 0 1 00.113449 0 n/a 0 0 n/a 0% 0% 0% 0% 1 1 00.071429 100% DSNDB06 DSNDSX01 0 5 00.051304 0 n/a 0 0 n/a 0% 0% 0% 0% 1 6 00.216007 66% DSNDB06 DSNDTX01 0 4 00.023037 0 n/a 0 0 n/a 0% 0% 0% 0% 2 3 00.164123 83% DSNDB06 DSNDXX02 0 3 00.091493 0 n/a 0 0 n/a 0% 0% 0% 0% 1 6 00.234913 83% DSNDB06 DSNKAX02 0 5 00.030939 0 n/a 0 0 n/a 0% 0% 0% 0% 0 0 n/a 0% DSNDB06 DSNUCH01 0 1 00.022360 0 n/a 0 0 n/a 0% 0% 0% 0% 1 1 00.060204 0% DSNDB06 DSNUCX01 0 2 00.008763 0 n/a 0 0 n/a 0% 0% 0% 0% 1 1 00.088495 0% DSNDB06 SYSCOPY 0 3 00.036797 1 00.031357 0 0 n/a 0% 0% 0% 0% 1 1 00.025339 0% DSNDB06 SYSDBASE 0 84 00.046349 1 00.033596 78 30 00.066956 0% 100% 0% 0% 2 1 00.214619 33% DSNDB06 SYSDBAUT 0 2 00.038112 1 00.028843 0 0 n/a 0% 0% 0% 0% 1 1 00.028682 0% DSNDB06 SYSPLAN 0 1 00.023194 1 00.027335 0 0 n/a 0% 0% 0% 0% 1 4 00.207089 80% DSNDB06 SYSUSER 0 4 00.042307 0 n/a 0 0 n/a 0% 0% 0% 0% 0 0 n/a 0% DSN8D31A DSN8S31E 1 8 00.044856 0 n/a 9 6 00.033228 0% 100% 0% 0% 0 0 n/a 0%

FIGURE 88. System Buffer Pool IO Report (Group by Hour)

EDM Pool I/O


EDM Pool I/O

IntroductionThis report displays information about I/O activity that occurred within the DB2 EDM pools.


� determining the volume or type of activity for a specific plan name, AUTHID, or connection type

� characterizing I/O performance


Default DDnameO2RPEDM

Default TitleEDM Pool I/O Activity

Data SourcePerformance Class (4), IFCIDs 23, 30

IFCIDs 105 and 107 to convert database IDs

IFCIDs 73, and 74, if you specify Group by THREAD or Select THREADSTART

IFCIDs 68, 69, 70, 71, 73, 74, 84, 85, 86, 87, 88, and 89, if you specify Group By UNIT_OF_WORK or PROGRAM, or Select UOWSTART or PGMSTART


Group By ElementsDB2ID, AUTHID, ORIGAUTH, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, HOUR, DAY, THREAD, UNIT_OF_WORK, PROGRAM, SYSID

Order By Elements

DB2ID, AUTHID, ORIGAUTH, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, TIME, SYSID, MEMBER, GROUP

Select ElementsDB2ID, AUTHID, ORIGAUTH, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, IFCID, THREADSTART, UOWSTART, PGMSTART, SYSID, MEMBER, GROUP


EDM Pool I/O

Data Elements

Start Time The date that the application began execution. (QWHSSTCK)









Type Type of object requested from the EDM pool. All EDM pool activity within an individual entry will be ordered by type, and the type identifier will not be printed until it changes. For example, all CT Header requests printed or all CT Directory request printed. (QW0029ID, QW0029RN/QW0029KN)

Possible types are as follows:� DB descriptor� cursor table: CT header, CT directory, or CT RDS section� package table: PT header, PT directory, or PT RDS section

Database/Plan/Package Identifier

The value in this column depends upon the Type element. If Type is DB Descriptor, the value will be the database name (if IFCIDs 105/107 are available) or database identifier number (if IFCIDs 105/107 are not available). Otherwise, the value will be the plan name for the cursor table that you request, or the location.collection.package identifier for the PT being requested. (QW0029DB, or QW0029PL, or QW0029LN.QW0029CI.QW0029PI)

Note: Since this element is derived from the program name, it can be only 8 bytes.

# Requests The number of times during this group’s interval that this TYPE/ID combination was requested.

# Data Mgr Calls The total number of calls to the data manager required to satisfy the requests. (QW0030DC, QW0030CC, QW0030GC)

Elapsed Time The total amount of time it took to satisfy all the requests (mm:ss.tht). (30.QWHSSTCK-29.QWHSSTCK)

ElapTime/Request

The average amount of time it took to satisfy one EDM pool request (mm:ss.tht).

Avg Sect Len The average section length (bytes) of the EDM pool object requested. (QW0029DL, QW0029CL, QW0029GL)

ED

M Pool I/O

448O

ME

GA

MO

N II for D

B2 H


uide, Version 540

OMEGAMON II for DB2 V540 EDM Pool I/O Activity Page 1Run Date=mm/dd/yy By Thread Run Time=12.43.07 Start Time: 1990-12-01.08:16:01.345678DB2Id=D22B, Planname=DSNESPRR, Connid=TSO, Corrid=TDO209AB, Authid=TDO209, Original Authid=TDO209AB---------------------------------------------------------------------------------------------------------------------------------- # # Data Elapsed ElapTime AvgType Database, Plan, or Package Identifier Requests Mgr Calls Time /Request Sect Len------------- -------------------------------------------- -------- --------- ----------- ----------- --------CT-Header DSNESPRR 2 2 00:00.21000 00:00.10500 1900.00CT-Header H2200PLN 2 2 00:00.21104 00:00.10552 1900.00CT-Directory DSNESPRR 2 2 00:00.00030 00:00.00015 200.00DB Descriptor DBSUK000 1 2 00:00.72000 00:00.36000 6214.00 DBSUK001 18 36 00:03.70872 00:00.10302 4564.00 Start Time: 1990-12-01.08:17:01.723101DB2Id=D22B, Planname=DSNESPRR, Connid=TSO, Corrid=TDO209AB, Authid=TDO209, Original Authid=TDO209AB---------------------------------------------------------------------------------------------------------------------------------- # # Data Elapsed ElapTime AvgType Database, Plan, or Package Identifier Requests Mgr Calls Time /Request Sect Len------------- -------------------------------------------- -------- --------- ----------- ----------- --------CT-Header DSNACTRP 4 4 00:00.00360 00:00.00090 435.00CT-Directory DSNACTRP 4 4 00:00.08008 00:00.02002 234.00CT-RDS Section DSNACTRP 1 2 00:00.24200 00:00.24200 5345.00PT-Header CHICAGO.PAYDEPT.PAYCR010 4 4 00:00.00360 00:00.00090 435.00PT-Directory CHICAGO.PAYDEPT.PAYCR010 4 4 00:00.08008 00:00.02002 234.00PT-RDS Section CHICAGO.PAYDEPT.PAYCR010 1 2 00:00.24200 00:00.24200 5345.00

FIGURE 89. EDM Pool Performance Report (Group by THREAD)


Lock Suspension

Lock Suspension

Introduction This report displays a summary of lock suspensions that have occurred.

This report can be used to determine the following:

� frequency and type of lock suspensions that are occurring

� average amount of time that elapses for lock suspensions

� specific resources (such as pagesets, plans) that are having frequent and lengthy lock suspensions

Default DDNameO2RPLKS

Default TitleLock Suspension



IFCID 21 to obtain lock resource name information for change lock functions

IFCIDs 73 and 74, if you specify Group By THREAD or Select THREADSTART

IFCIDs 68–71, 73, 74, 84–, and 89, if you specify Group By UNIT_OF_WORK or PROGRAM, or Select UOWSTART or PGMSTART


Group By ElementsDB2ID, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, AUTHID, ORIGAUTH, HOUR, DAY, THREAD, UNIT_OF_WORK, PROGRAM, SYSID, MEMBER, GROUP


Lock Suspension


Select ElementsDB2ID, AUTHID, ORIGAUTH, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, IFCID, THREADSTART, UOWSTART, PGMSTART, DBID, PSID, SYSID, MEMBER, GROUP

Data Elements





Resource Name Name of the resource for which the lock suspension occurred. The contents of this field depend on the Lock Type. For most locks the database and/or pageset names will make up the resource name. For more information on the resource name displayed, see the description of Lock Type. (QW0044LK)

The following subresource names may be displayed:

DB= Database name (if IFCIDs 105/107 are available), or database identifier number (if IFCIDs 105/107 are not available). (QW0044KD)

Coll= Collection identifier for collection lock suspensions. (QW0044RN - first 8 bytes)

Pkg= Package name, made up of the collection ID, program name, and consistency token, for SPT (skeleton package table) lock suspensions. (QW0044RN)

Note: The collection ID and program name must be decompressed from 6-bit codes as described in the IFCID 21 record DSECT.

Plan= Plan name for SKCT lock suspensions. (QW0044RN - first 8 bytes)

PS= Pageset (tablespace) name (if IFCIDs 105/107 are available), or pageset identifier number (if IFCIDs 105/107 are not available). (QW0044KP)

BP= The bufferpool name of the requested resource. (QW0021KD/QW0021KP for L-locks, QW0021P1 for P-locks)

UTID= The utility ID of the requested resource for utility UID lock. (First 16 bytes of QW0021RN)

Part= The partition number. (QW0044K2 or QW0044P4)

Lock Type The type of lock requested. This field will determine the contents of the resource name. (QW0044KT)



Lock Suspension


Local Suspends The number of local resource suspensions that occurred because the lock was already held by someone else. (QW0044WS)

Global Suspends The count of 44/45 IFCID pairs where QW0044G1=1 (lock is global) and QW0045SR=QW0045W5 (intersystem communication required).

Lock Suspension


Normal Resumes The number of local resource suspensions that were normally resumed, that is, did not result in timeout or deadlock. (QW0045R = N)

Normal Elapsed Time

The average amount of time that elapsed for local and global resource suspensions that resumed normally. (QWHSSTCK)

# Timeout The number of suspensions that resulted in a timeout. (QW0045R = T)

Timeout Elapsed Time

The average amount of time that elapsed for suspensions that resulted in timeouts. (QWHSSTCK)

# Deadlock The number of suspensions that resulted in deadlock. (QW0045R = D)

Deadlock Elapsed Time

The average amount of time that elapsed for suspensions that resulted in deadlock. (QWHSSTCK)

Other Suspends The number of suspensions that were not local resource suspensions. (QW0044KT)

Possible reasons for suspension are as follows:� global resource contention� intersystem communication� IRLM latch contention� IRLM queued request� local resource contention� notify message sent� local storage cannot be extended� RH to PTB communication request

Other Elapsed Time

The average amount of time that elapsed for other suspensions that were normally resumed. (QWHSSTCK)

Historical R


eports453

Lock S

uspension

Omegamon II for DB2 V540 Lock Suspension Page 1Date=mm/dd/yy Grouped by Sysid, DB2id, PlanName, Connid, Corrid, Authid Run Time=19:18:18 Sysid=SP13, DB2id=D411, Planname=, Connid=D411, Corrid=010.PM2PCP01, Authid=SYSOPR---------------------------------------------------------------------------------------------------------------------------------- Lock Local Global --Normal Resumes-- -----Timeouts----- -----Deadlocks---- --Other Suspends--Resource Name Type Suspends Suspends Count Elapsed Time Count Elapsed Time Count Elapsed Time Count Elapsed Time------------------------------ ---- -------- -------- ----- ------------ ----- ------------ ----- ------------ ----- ------------DB= DPAG 0 4 0 n/a 0 n/a 0 n/a 5 00:01.545259n/a ALL 0 0 0 n/a 0 n/a 0 n/a 9 00:04.798333Sysid=SP13, DB2id=D411, Planname=, Connid=D411, Corrid=020.TLPLKP1D, Authid=SYSOPR---------------------------------------------------------------------------------------------------------------------------------- Lock Local Global --Normal Resumes-- -----Timeouts----- -----Deadlocks---- --Other Suspends--Resource Name Type Suspends Suspends Count Elapsed Time Count Elapsed Time Count Elapsed Time Count Elapsed Time------------------------------ ---- -------- -------- ----- ------------ ----- ------------ ----- ------------ ----- ------------BP=0 PBPC 0 1 0 n/a 0 n/a 0 n/a 1 00:16.314817DB= DPAG 0 1 0 n/a 0 n/a 0 n/a 1 00:00.007262Sysid=SP13, DB2id=D411, Planname=DSNESPCS, Connid=TSO, Corrid=JWAYG2, Authid=JWAYG2---------------------------------------------------------------------------------------------------------------------------------- Lock Local Global --Normal Resumes-- -----Timeouts----- -----Deadlocks---- --Other Suspends--Resource Name Type Suspends Suspends Count Elapsed Time Count Elapsed Time Count Elapsed Time Count Elapsed Time------------------------------- ---- -------- -------- ----- ------------ ----- ------------ ----- ------------ ----- ------------DB= DPAG 0 6 0 n/a 0 n/a 0 n/a 6 00:07.504147n/a ALL 0 0 0 n/a 0 n/a 0 n/a 3 00:00.212810DB= PS= BP=0 PPSC 0 3 0 n/a 0 n/a 0 n/a 3 00:16.710442 PPSP 0 4 0 n/a 0 n/a 0 n/a 4 00:07.025822 PPAG 0 1 0 n/a 0 n/a 0 n/a 1 00:17.132123DB=DSN8D41A PS=DSN8S41E DSET 0 4 0 n/a 0 n/a 0 n/a 4 00:07.609823

FIGURE 90. Lock Suspension Report (Group by SYSID, DB2ID, Planname, Connid, Corrid, Authid)




IntroductionThis report provides a summary of global lock suspensions that occurred in a data sharing environment.

Data sharing environments are supported only in DB2 Version 4.

Data SourcePerformance trace IFCID 44 and 45.



IFCIDs 73 and 74, if groupby is THREAD or select is THREADSTART

IFCIDs 68–71, 73, 74, and 84–89, if groupby is UNIT_OF_WORK or PROGRAM or select is UOWSTART or PGMSTART.


Group By ElementsDB2ID, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, AUTHID, ORIGAUTH, HOUR, DAY, THREAD, UNIT_OF_WORK, PROGRAM, SYSID, MEMBER, GROUP


Select ElementsDB2ID, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, AUTHID, ORIGAUTH, THREADSTART, UOWSTART, PGMSTART, DBID, PSID, SYSID, MEMBER, GROUP



Data Elements

Resource Name Name of the resource for which the global lock suspension occurred. The contents of this field depend on the Lock Type. For most locks the database and/or pageset names will make up the resource name. For more information on the resource name displayed, see the description of Lock Type. (QW0044LK)

The following subresource names may be displayed:

DB= Database name (if IFCIDs 105/107 are available), or database identifier number (if IFCIDs 105/107 are not available). (QW0044KD)

Coll= Collection identifier for collection lock suspensions. (QW0044RN - first 8 bytes)

Pkg= Package name, made up of the collection ID, program name, and consistency token, for SPT (skeleton package table) lock suspensions. (QW0044RN)

Note: The collection ID and program name must be decompressed from 6-bit codes as described in the IFCID 21 record DSECT.

Plan= Plan name for SKCT lock suspensions. (QW0044RN - first 8 bytes)

PS= Pageset (tablespace) name (if IFCIDs 105/107 are available), or pageset identifier number (if IFCIDs 105/107 are not available). (QW0044KP)

BP= The bufferpool name of the requested resource. (QW0021KD/QW0021KP for L-locks, QW0021P1 for P-locks)

UTID= The utility ID of the requested resource for utility UID lock. (First 16 bytes of QW0021RN)

Part= The partition number. (QW0044K2 or QW0044P4)

Lock Type The type of lock requested. This field will determine the contents of the resource name. (QW0044KT)




Local Deadlock Count

The count of 44/45 pairs where the global lock flag is not set in the 44 record (QW0044GF has bit QW0044G1 unset) and the resume reason is deadlock. (QW0045R = ‘D’)

Local Timeout Count

The count of 44/45 pairs where the global lock flag is not set in the 44 record (QW0044GF has bit QW0044G1 unset) and the resume reason is timeout. (QW0045R = ‘T’)

Local Suspend Count

The count of 44/45 pairs where the global lock flag is not set in the 44 record. (QW0044GF has bit QW0044G1 unset)

Local Suspend Elap Time

The total elapsed time calculated for each 44/45 pair where the global lock flag is not set in the 44 record. (QW0044GF has bit QW0044G1 unset)

To XES The count of 44/45 pairs where the lock request was escalated to XES. (QW0044F3 has bit QW0044YI set)

Global Suspend Count

The count of 44/45 pairs where the global lock flag is set in the 44 record. (QW0044GF has bit QW0044G1 set)

Message Sending Count

The count of 44/45 pairs where the suspend reason is that an intersystem message was sent. (QW0044WS = QW0044W7)

Elapsed Time The sum of time calculated from the difference between the storeclock values in the header of 44/45 pairs included in the corresponding count.

XES Contention Count

The count of 44/45 pairs where:� the global lock flag is set in the 44 record (QW0044WS has bit

QW0044IS set)� the suspend reason has the intersystem communication bit set

(QW0045SR has bit QW0045W5 set)� the XES contention bit of the extent of global contention field is set

(QW0045XR has bit QW0045X3 set)

IRLM Gbl Contention Count



(QW0045SR has bit QW0045W5 set).� the IRLM global resource contention bit of the extent of global

contention field is set (QW0045XR has bit QW0045X4 set)

False Contention Count



(QW0045SR has bit QW0045W5 set)� neither the XES contention bit nor the IRLM global resource

contention bit of the extent of global contention field is set (QW0045XR has neither bit QW0045X3 nor QW0045X4 set)

Global L

ock Suspensions

458O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 Global Lock Suspension Page 1Date=mm/dd/yy Group by Sysid, DB2id, PlanName, Connid, Corrid, Authid Run Time=16:43:18 Sysid=SP13, DB2id=D411, Planname=, Connid=D411, Corrid=010.PM2PCP01, Authid=SYSOPR---------------------------------------------------------------------------------------------------------------------------------- ---Total--- -----Local----- Prop -------------- Global Contention -------------- Lock Dead- Time- --Suspensions-- Glbl To --Msg Sending-- ------XES------ -----IRLM------ -----False-----Resource Name Type Locks Outs Count Elap Time Susps XES Count Elap Time Count Elap Time Count Elap Time Count Elap Time---------------------- ---- ----- ----- ----- --------- ----- ----- ----- --------- ----- --------- ----- --------- ----- ---------DB= DPAG 0 0 0 n/a 4 4 1 00:00.000 0 n/a 4 00:01.000 0 n/an/a ALL 0 0 0 n/a 0 6 0 n/a 0 n/a 6 00:07.000 0 n/aSysid=SP13, DB2id=D411, Planname=, Connid=D411, Corrid=020.TLPLKP1D, Authid=SYSOPR---------------------------------------------------------------------------------------------------------------------------------- ---Total--- -----Local----- Prop -------------- Global Contention -------------- Lock Dead- Time- --Suspensions-- Glbl To --Msg Sending-- ------XES------ -----IRLM------ -----False-----Resource Name Type Locks Outs Count Elap Time Susps XES Count Elap Time Count Elap Time Count Elap Time Count Elap Time---------------------- ---- ----- ----- ----- --------- ----- ----- ----- --------- ----- --------- ----- --------- ----- ---------BP=0 PBPC 0 0 0 n/a 1 1 0 n/a 1 00:16.000 0 n/a 0 n/aDB= DPAG 0 0 0 n/a 1 1 0 n/a 0 n/a 1 00:00.000 0 n/aSysid=SP13, DB2id=D411, Planname=DSNESPCS, Connid=TSO, Corrid=JWAYG2, Authid=JWAYG2---------------------------------------------------------------------------------------------------------------------------------- ---Total--- -----Local----- Prop -------------- Global Contention -------------- Lock Dead- Time- --Suspensions-- Glbl To --Msg Sending-- ------XES------ -----IRLM------ -----False-----Resource Name Type Locks Outs Count Elap Time Susps XES Count Elap Time Count Elap Time Count Elap Time Count Elap Time---------------------- ---- ----- ----- ----- --------- ----- ----- ----- --------- ----- --------- ----- --------- ----- ---------DB= DPAG 0 0 0 n/a 6 6 0 n/a 0 n/a 6 00:07.000 0 n/an/a ALL 0 0 0 n/a 0 3 0 n/a 0 n/a 3 00:00.000 0 n/aDB= PS= BP=0 PPSC 0 0 0 n/a 3 3 0 n/a 3 00:16.000 0 n/a 0 n/a PPSP 0 0 0 n/a 4 4 0 n/a 0 n/a 4 00:07.000 0 n/a PPAG 0 0 0 n/a 1 1 0 n/a 0 n/a 1 00:17.000 0 n/aDB=DSN8D41A PS=DSN8S41E DSET 0 0 0 n/a 4 4 0 n/a 4 00:07.000 0 n/a 0 n/a ROW 1 0 0 n/a 2 2 0 n/a 0 n/a 1 00:00.000 1 10:32.000

FIGURE 91. Global Lock Suspension (Group by SYSID, DB2ID, Planname, Connid, Corrid, Authid)


Lock Contention

Lock Contention

IntroductionThis report displays all timeouts and deadlocks that have occurred.


� determining the frequency and type of lock contentions that are occurring

� identifying the specific resources (such as pagesets, plans) that are having lock contention problems

Default DDnameO2RPLKC

Default TitleLock Contention

Data SourcePerformance Class (6), IFCIDs 44, 45, 54, 172, 196, 213, 214



1FCIDs 73 and 74, if you specify Select THREADSTART

IFCIDs 68–71, 73, 74, and 84–89, if you specify Select UOWSTART or PGMSTART




Select ElementsDB2ID, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, AUTHID, ORIGAUTH, IFCID, THREADSTART, UOWSTART, PGMSTART, DBID, PSID, ELAPTIME, BPID, SYSID, MEMBER, GROUP

Lock Contention


Data ElementsEvent Time The time the lock request was made. If this information is not available (no

IFCID 44/213), then this will be the time that the deadlock/timeout occurred. (45/214 or 54, QWHSSTCK)

Elapsed Time The amount of time that elapsed between the lock request and the deadlock/timeout. (44/45 or 213/214 pairs, QWHSSTCK)

Result The reason the lock was not acquired: either TIMEOUT or DEADLOCK. (QW0045R)

Resource The resource in contention. The information presented here depends upon the type of resource that was requested. Only information that applies to the type of resource being locked is shown. For example, for a database lock, only the database id is shown; while for a data page lock, the database id, pageset id, and page number are displayed.

Possible resources are as follows:

DB The database of the requested resource. (QW0044KD/QW0213DB)

PS The pageset of the requested resource. (QW0044KP/QW0213PS)

PART The partition number of the requested resource. (QW0044K2/QW0213PT)

BP The bufferpool name of the requested resource. P-Locks apply only to DB2 Version 4. (QW0021KD/QW0021KP for L-locks, QW0021P1 for P-locks)

UTID For utility UID lock this is the utility ID of the requested resource. (First 16 bytes of QW0021RN)

Page The hexadecimal page number of the locked resource. (QW0044K1)

SubPage The hexadecimal sub-page number of the resource locked with an Index Page Lock. (QW0044K2)

Anchor The hexadecimal value of anchor ID for a resource locked with an Hash Anchor Lock. (QW0044K2)

RID The hexadecimal value of the record ID for a Row Lock. (QW0044K2)

Table The table name, or table record OBID of the table locked by a Table or Mass Delete Lock. (QW0044KP)

Type The type of lock requested. This field will always be present and will dictate what additional information will be presented. (QW0044KT/QW00213KT)



Lock Contention


HOLDER This section identifies a unit of work (user) holding a lock on the indicated resource (causing a block in the case of a timeout).

Plan The plan name for the user being identified. (QW0054PN or QW0172HP or QW0172WP or QW0196HP)

Lock Contention


Connid The connection id of the user being identified. (QW0054CN or QW0172HN or QW0172WN or QW0196HN)

Corrid The correlation id of the user being identified. (QW0054CV or QW0172HR or QW0172WR or QW0196HR)

OwnWU The holder’s owning work unit. This field is only non-blank if an IFCID 172 or 196 record is present for this event. (QW0172HO or QW0196HO)

State Indicates the state of the lock held. Possible values are: IS, IX, S, U, S, SIX, X, X’01’, X’07’. (QW0054ST or QW0172HS or QW0172WS or QW0196HS or QW0196WS or QW0172HS or QW0172WS)

DBMSid The holder’s DBMS identifier. This field is present only for deadlock events and is only non-blank if an IFCID 172 record is present for this event. Applies only to DB2 Version 3. (QW0172HI)

Member The holder’s DB2 member name. This value is present only for deadlock and timeout. Applies only to DB2 Version 4. (QW0172HI/QW0172WI/QW0196HI)

LUWid The holder’s Logical Unit-of-Work identifier. This field is only present (non-blank) if an IFCID 172 or 196 record is present for this event. It is set to ‘*’ if the lock holder is not a DBAT. (QW0172HL or QW0196HL)

Duration Indicates the requested duration of the lock. (QW0044DR or QW0172HD or QW0172WD or QW0196HD or QW0196WD)

Possible values are as follows:� allocation� commit� commit+1� manual� manual+1� plan

Type The holder’s contention type. This field is only present for timeout events. Possible values are ACE or RURE. (QW0054TC or QW0196HA)


Lock Contention

Waiter This section identifies a unit of work (user) waiting for a lock on the indicated resource. In the case of a timeout, this may be a priority waiter (causing a block) or the “victim” of the timeout.

Plan The plan name for the user being identified. (QWHCPLAN or QW0172HP or QW0172WP or QW0196HP)

Connid The connection id of the user being identified. (QWHCCN or QW0172HN or QW0172WN or QW0196HN)

Corrid The correlation id of the user being identified. (QWHCCV or QW0172HR or QW0172WR or QW0196HR)

State Indicates the state of the lock held. Possible values are: IS, IX, S, U, S, SIX, X, X’01’, X’07’ (QW0044ST or QW0213ST or QW0172HS or QW0172WS or QW0196HS or QW0196WS or QW0172HS, QW0172WS)

Conditional/Unconditional

The waiter’s (victim’s) request flag. This field is only present for timeout events and indicates whether the request for the lock was conditional or unconditional. (QW0196CU)

Worth The waiter’s DB2 assigned worth value. This field is only present for deadlock events and is only non-zero if an IFCID 172 record is present for this event. The value is an integer from 0 to 255. (QW0172WA)

OwnWU The waiter’s owning work unit. This field is only present (non-blank) if an IFCID 172 or 196 record is present for this event. (QW0172WO or QW0196WO)

DBMSid The holder’s DBMS identifier. This field is only present for deadlock events and is only non-blank if an IFCID 172 record is present for this event. Applies only to DB2 Version 3. (QW0172WI)

Member The waiter’s DB2 member name. This value is present only for deadlock and timeout. Applies only to DB2 Version 4. (QW0172HI/QW0172WI/QW0196HI)

LUWid The waiter’s Logical Unit-of-Work identifier. This field is only present (non-blank) if an IFCID 172 record is present for this event. It is set to ‘*’ if the lock waiter is not a DBAT. (QW0172WL)

Lock Contention




ReqWU The waiter’s requesting work unit. This field is only present for deadlock events and is only non-blank if an IFCID 172 record is present for this event. (QW0172WW)

Type The waiter’s contention type. This field is only present for timeout events. Possible values are ACE or RURE. (QW0054TC or QW0196HA)

Interval The timeout interval in DSNZPARM. This is the value of the DSNZPARM parameter IRLMRWT when the timeout occurred. (QW0196TI)

Count The timeout counter for this thread. Applies only to DB2 Version 4. (QW0196TC)



ReqWU The waiter’s requesting work unit. This field is only present for deadlock events and is only non-blank if an IFCID 172 record is present for this event. (QW0172WW)

Type The waiter’s contention type. This field is only present for timeout events. Possible values are ACE or RURE. (QW0054TC or QW0196HA)

Interval The timeout interval in DSNZPARM. This is the value of the DSNZPARM parameter IRLMRWT when the timeout occurred. (QW0196TI)

Count The timeout counter for this thread. Applies only to DB2 Version 4. (QW0196TC)

Historical R


eports465

Lock C

ontention

Omegamon II for DB2 V540 Lock Contention Page 1Date=mm/dd/yy Run Time=07:08:29 Event Time=1995-06-15-15.25.27.500151 Sysid=SP13 DB2id=D411 Result=Timeout Resource: Type = DSET DBID = PAVDB1 PSID = PAVPTS Partition = x’0001’ Waiter: Plan = DSNESPRR Connid = TSO Corrid = CLVIL ReqType = Unconditional State = X Duration = Commit OwnWU = 005400BA07B0BA18 Timeout: Count = 1 Interval = 600 Holder: Plan = DSNESPCS Connid = TSO Corrid = VHERN LUWid = R13D411(AB385DEC8EC30001) State = IS Type = 01 Duration = Commit OwnWU = 005400B707B0B738 Member = D411 Holder: Plan = DSNESPCS Connid = TSO Corrid = VHERN LUWid = R13D411(AB385F2A88F30001) State = IX Type = 01 Duration = Commit OwnWU = 005400BE07B0BE68 Member = D411Event Time=1995-06-16-07.11.45.741750 Sysid=SYSG DB2id=D310 Elapsed Time=02:00.945027 Result=Timeout Resource: Type = IPAG DBID = RBDBPKD1 PSID = RB00NSI1 Page = x’000658’ SubPage = x’00’ Waiter: Plan = DSNESPCS Connid = TSO Corrid = HSTDBAM Authid = HSTDBAM State = S Duration = Manual ReqType = Unconditional,Acquire,Single,Result Holder: Plan = SSCDB2 Connid = DB2CALL Corrid = SQLCONN Authid = HSTDB13 State = ANY Type = ACE Additional detail for this Timeout follows: Resource: Type = IPAG DBID = RBDBPKD1 PSID = RB00NSI1 Page = x’000658’ SubPage = x’00’ Waiter: Plan = DSNESPCS Connid = TSO Corrid = HSTDBAM ReqType = Unconditional State = S Duration = Manual OwnWU = 0000006623F266F8 Holder: Plan = SSCDB2 Connid = DB2CALL Corrid = SQLCONN LUWid = * State = X Type = ACE Duration = Commit OwnWU = 0000006B23F26B78

FIGURE 92. (Part 1 of 2) Lock Contention Report

Lock Contention

466O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon for DB2 V540 DB2 Lock Contention Page=1Report Date=mm/dd/yy Report Time=12.43.07 Event Time=1993-02-22-00.15.20.243000 Elapsed Time=010.421387 Type=Lock Result=DEADLOCK Resource: Type = DPAG DB=SUKDBD00 PS=SUKTS003 Page=000002 Holder: Plan = DSNESPRR Connid = TSO Corrid = TDO206 Authid = TDO206 State = X OwnWU = DSNESPRR Member = LUWid = TDO206 Duration = Commit Waiter: Plan = DSNESPCS Connid = TSO Corrid = TDO206D Authid = TDO206D State = X Worth = 111 OwnWU = DSNESPRR Member = LUWid = TDO206 Duration = Commit ReqWU = TDO206 Resource: Type = DPAG DB=SUKDBD01 PS=SUKTS013 Page=000001 Holder: Plan = DSNESPRR Connid = TSO Corrid = TDO206D Authid = TDO206D State = X OwnWU = DSNESPRR Member = LUWid = TDO206 Duration = Commit Waiter: Plan = DSNESPRR Connid = TSO Corrid = TDO206 Authid = TDO206 State = S Worth = 111 OwnWU = DSNESPRR Member = LUWid = TDO206 Duration = Commit ReqWU = TDO206 Event Time=1993-02-22-00.29.11.694200 Elapsed Time=005.123456 Type=Drain Result=TIMEOUT Resource: Type = PSET DB=SUKDBD00 PS=SUKTS000 Waiter: Plan = DSNESPCS Connid = TSO Corrid = TDO206D Authid = TDO206D State = X Conditional OwnWU = DSNESPCS Member = Duration = Commit Intvl = 180 TCount = 1 Holder: Plan = DSNESPRR Connid = TSO Corrid = TDO206 Authid = TDO206 State = S OwnWU = DSNESPRR Member = LUWid = TDO206 Duration = Commit Type = ACE Intvl = 180 TCount = 1 Waiter: Plan = DSNESPCS Connid = TSO Corrid = TDO206A Authid = TDO206A State = S OwnWU = DSNESPCS Member = LUWid = TDO206 Duration = Commit Type = ACE Intvl = 180 TCount = 1 Holder: Plan = DSNESPRR Connid = TSO Corrid = TDO206B Authid = TDO206B State = S OwnWU = DSNESPRR Member = LUWid = TDO206B Duration = Allocation Type = RURE Intvl = 180 TCount = 1

FIGURE 93. (Part 2 of 2) Lock Contention Report


P-Lock Detail

P-Lock Detail

Introduction This report displays information related to pageset P-lock and page P-lock activity for an object or set of objects in a data sharing environment. It also provides, in chronological order, a list of global locking events on a resource. This allows you to investigate intersystem locking problems.

Use this report to investigate, on a group-wide basis, locking problems identified by the contention or suspension reports.

Data sharing environments are supported only in DB2 Version 4.

Data SourcesIFCID 251, 259

Note: If you do not want information about page-level P-lock detail to appear on this report, select only IFCID 251.


Group By ElementsNone.

This report will be grouped by data sharing group name.

Order By ElementsDB2ID, DBID, PSID, SYSID, MEMBER, GROUP

Select ElementsDB2ID, DBID, PSID, SYSID, MEMBER, GROUP

Data Elements

Start Time The date and time of the first IFCID record (251 or 259) encountered for this resource.

Time The time taken from the store clock value in the IFC record header. In the data sharing environment this is the sysplex timer value. (QWHSSTCK)

Type The type of the P-lock. (QW0251TT/QW0259TT)

It may have one of the following values:

PPSP Pageset/partition P-lock. (QW0251TT)

PPAG Page P-lock. (QW0259TT)

P-Lock Detail


Request This is the IRLM function code which is used to request the creation of, or change to, a lock. (QW0251IF/QW0259IF)

It may have one of the following values:

Lock The creation of a lock is requested. (QW0251IF=QW0251IL, or QW0259IF=QW0259IL)

Unlock The deletion of a lock is requested. (QW0251IF=QW0251IU, or QW0259IF=QW0259IU)

Change A change in lock state is requested. (QW0251IF=QW0251IC, or QW0259IF=QW0259IC)

ChngPX A change in lock state is requested. This change has been initiated by driving the data sharing group member’s P-lock exit. (QW0251IF=QW0251IPC or QW0259IF=QW0259IP)

Event The event causing the P-lock activity. This is provided for page (type PPAG) P-lock activity only. (QW0259EV)


ChngL A change to a page latch event. (QW0259EV=QW0259EC)

GetP A getpage event. (QW0259EV=QW0259EG)

Latch A latch event. (QW0259EV=QW0259EL)

PLock A P-lock exit. (QW0259EV=QW0259EP)

SetWr Set write intent. (QW0259EV=QW0259ES)

Steal Page steal. (QW0259EV=QW0259ET)

Write Page write. (QW0259EV=QW0259EW)

Relative Page The relative page number associated with the lock request. This is provided for page P-locks (type PPAG) activity only. (QW0259KQ)

Page Type The type of page associated with the lock request. This is provided for page P-locks (type PPAG) activity only. (QW0259OB)


Data Data page. (QW0259OB=QW0259OD)

Hdr Header page. (QW0259OB=QW0259OH)

Indx Index page. (QW0259OB=QW0259OI)

Spce Space map page. (QW0259OB=QW0259OS)

Requesting Member

The member issuing the P-lock request. This is the name of the data sharing group member which wrote the IFI record. (QWHAMEMN)


P-Lock Detail

Request State The requested state of the P-lock for lock or change requests. It may take one of the values shown below. Note that for a request type ChngPX the request state is the state requested by the other member if there is a lock conflict. If there is no conflict then the requested state for a ChngPX request is shown as a dash (-). (QW0251ST/QW0259ST)

None. This is the value for an unlock request (QW0251ST=QW0251S0, QW0259ST=QW0259S0).

IS. Intent shared. (QW0251ST=QW0251S2)

IX. Intent exclusive. (QW0251ST=QW0251S3)

S. Shared. (QW0251ST=QW0251S4, QW0259ST=QW0259S4)

SIX. Shared, intent exclusive. (QW0251ST=QW0251S6)

NSU. Non-shared update. (QW0251ST=QW0251S7)

X. Exclusive. (QW0251ST=QW0251S8, QW0259ST=QW0259S8)

Deny. Request was denied. (QW0251ST=QW0251FF, QW0259ST=QW0259FF)

Prev State The previously held P-lock state. (QW0251OS/QW0259PS)


None. This is the value for an unlock request. (QW0251OS=QW0251S0, QW0259PS=QW0259S0)

IS. Intent shared. (QW0251OS=QW0251S2)

IX. Intent exclusive. (QW0251OS=QW0251S3)

S. Shared. (QW0251OS=QW0251S4, QW0259PS=QW0259S4)

SIX. Shared, intent exclusive. (QW0251OS=QW0251S6)

NSU. Non-shared update. (QW0251OS=QW0251S7)

X. Exclusive. (QW0251OS=QW0251S8, QW0259PS=QW0259S8)

Deny. Request was denied. (QW0251OS=QW0251FF, QW0259PS=QW0259FF)

Prev Cache State The previously held P-lock cached state. This value is present for pageset or partition P-locks (type PPSP) only. (QW0251OC)

Possible values are those listed under “Prev State” above.

New State The newly held P-lock state. (QW0251NS/QW0259NS)


New Cache State The newly held P-lock cached state. This value is present for pageset or partition P-locks (type PPSP) only. (QW0251NC)


Conflict With The data sharing group member which is in conflict with this request. The value is shown for rejected lock or change requests. It is also shown for ChngPX type requests where there is a conflict with this member’s currently held P-lock state. (QW0251DB/QW0259DB)

P-Lock D

etail

470O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 P-Lock Detail Page 1Run Date=mm/dd/yy Run Time=15:53:05 Start Time: 1995-06-12.09:52:23.400139Group=D41G Type=IndexSpace DB=DSB8D41A PS=XEMP1 Part=x’02’ BP=0---------------------------------------------------------------------------------------------------------------------------------- Prev New Relative Page Requesting Request Prev Cache New Cache ConflictTime Type Request Event Page Type Member State State State State State With--------------- ---- -------- ------ --------- ----- ---------- ------- ------ ------ ------ ------ -------------------09:52:23.400139 PPSP Lock D412 X S S S S09:52:30.642926 PPSP Lock D412 IX S S SIX SIX09:52:30.652250 PPAG Lock Latch x’000003’ Index D412 X None X09:54:27.118521 PPAG Unlock Write x’000003’ Index D412 None X None09:54:50.654365 PPAG Lock Latch x’000003’ Index D411 S None S09:55:43.831877 PPAG Lock Latch x’000003’ Index D411 X S X09:55:43.844332 PPSP Lock D411 X IS IS IS IS09:55:44.241647 PPSP ChangePX D412 IX SIX SIX IX IX D41109:56:00.386009 PPSP Lock D411 IX IS IS IX IX10:00:39.586244 PPAG Unlock Write x’000003’ Index D411 None X None10:04:07.369262 PPAG Lock Latch x’000003’ Index D412 S None S10:04:07.871925 PPAG Lock Latch x’000003’ Index D412 X S X10:05:06.308850 PPAG ChangePX PLockX x’000003’ Index D412 S X S D41110:05:22.591396 PPAG Lock Latch x’000003’ Index D411 S None S10:13:49.556760 PPSP Lock D411 SIX IX IX IX IX10:14:02.766442 PPSP Change D411 IS IX IX IS IS10:15:37.708310 PPAG Unlock Steal x’000003’ Index D411 None S None10:27:08.753090 PPAG Lock Latch x’000003’ Index D412 X S X10:27:18.135925 PPAG Unlock Write x’000003’ Index D412 None X None10:27:37.626353 PPAG Lock Latch x’000003’ Index D411 S None S10:28:44.599265 PPAG Lock Latch x’000003’ Index D411 X S X10:28:44.613411 PPAG Lock D411 X IS IS IS IS10:28:44.633002 PPSP ChangePX D412 - IX IX IX IX10:29:00.947469 PPSP Lock D411 IX IS IS IX IX10:31:25.103890 PPAG Unlock Write x’000003’ Index D411 None X None10:39:13.495244 PPAG Lock Latch x’000003’ Index D411 S None S10:39:13.651427 PPAG Lock Latch x’000003’ Index D411 X S X10:39:14.328320 PPAG Unlock Write x’000003’ Index D411 None X None10:39:32.075222 PPSP Lock D412 SIX IX IX IX IX10:39:32.415622 PPSP Change D412 IS IX IX IS IS10:51:49.760345 PPSP Lock D411 SIX IX IX SIX SIX10:51:50.073103 PPSP ChangePX D412 - IS S S S10:52:05.943335 PPSP Change D411 S SIX SIX S S

FIGURE 94. (Part 1 of 2) Data Sharing P-Lock Detail

Historical R


eports471

P-Lock D

etail

Omegamon II for DB2 V540 P-Lock Detail Page 2Run Date=mm/dd/yy Run Time=15:53:05 Start Time: 1995-06-12.09:52:30.762519Type=TableSpace DB=DSB8D41A PS=DSN8S41E Part=x’02’ BP=0---------------------------------------------------------------------------------------------------------------------------------- Prev New Relative Page Requesting Request Prev Cache New Cache ConflictTime Type Request Event Page Type Member State State State State State With--------------- ---- -------- ------ --------- ----- ---------- ------- ------ ------ ------ ------ ------------------09:52:30.762519 PPSP Lock D412 X S S S S09:52:39.029529 PPSP Lock D412 IX S S SIX SIX09:53:30.047590 PPAG Lock Latch x’000002’ Data D412 X None X09:54:27.116617 PPAG Unlock Write x’000002’ Data D412 None X None09:56:34.923130 PPSP Lock D411 X IS IS IS IS09:56:34.976397 PPSP ChangePX D412 IX SIX SIX IX IX D41109:56:50.728764 PPSP Lock D411 IX IS IS IX IX10:00:30.272446 PPAG Lock Latch x’000002’ Data D411 X None X10:00:39.584455 PPAG Unlock Write x’000002’ Data D411 None X None10:04:07.888648 PPAG Lock Latch x’000002’ Data D412 X None X10:13:29.521353 PPSP Lock D411 SIX IX IX IX IX10:13:29.630843 PPAG Lock Latch x’000000’ Hdr D411 SIX IX IX IX IX10:13:29.882995 PPAG Unlock Write x’000000’ Hdr D411 None X None10:13:45.989383 PPSP Change D411 IS IX IX IS IS10:21:25.067884 PPAG Unlock Write x’000002’ Data D412 None X None10:24:47.667155 PPAG Lock Latch x’000001’ Spce D412 S None S10:24:47.668308 PPAG Unlock Steal x’000001’ Spce D412 None S None10:27:08.755169 PPAG Lock Latch x’000002’ Data D412 X None X10:27:18.134198 PPAG Unlock Write x’000002’ Data D412 None X None10:29:26.159994 PPSP Lock D411 X IS IS IS IS10:29:26.349527 PPSP ChangePX D412 - IX IX IX IX10:29:42.836052 PPSP Lock D411 IX IS IS IX IX10:31:24.006245 PPAG Lock Latch x’000002’ Data D411 X None X10:31:25.101944 PPAG Unlock Write x’000002’ Data D411 None X None10:39:10.635050 PPSP Lock D412 SIX IX IX IX IX10:39:10.842307 PPAG Lock Latch x’000000’ Hdr D412 X None X10:39:11.113893 PPAG Unlock Write x’000000’ Hdr D411 None X None10:39:13.313970 PPSP Change D412 IS IX IX IS IS10:39:13.653448 PPAG Lock Latch x’000002’ Data D411 X None X10:39:14.325391 PPAG Unlock Write x’000002’ Data D411 None X None10:50:58.417698 PPSP Lock D411 SIX IX IX SIX SIX10:50:59.776866 PPSP ChangePX D412 - IS S S S10:51:15.204206 PPSP Change D411 S SIX SIX S S

FIGURE 95. (Part 2 of 2) Data Sharing P-Lock Detail

System Event Trace


System Event Trace

IntroductionThis report displays the contents of performance trace records. This report is used to get detailed information about events that occurred and the relationships between those events.

For record pairs, such as begin and end I/O, matching will be done, and pertinent information such as elapsed and CPU times will be provided with the end-record data. For DBIDs and PSIDs, if IFCIDs 105 and 107 are available, names will be displayed; otherwise only IDs will be displayed.

No grouping or ordering is allowed. You can specify filtering specifications. For example, select only those records with an authid of TDO209, or select only IFCIDs 6, 7, 9, and 10.

Default DDnameO2RPSET

Default TitleSystem Event Trace

Data SourceWhatever IFCIDs are specified in the selection criteria.



Select ElementsDB2ID, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, AUTHID, ORIGAUTH, IFCID, DBID, PSID, SYSID, MEMBER, GROUP

Data ElementsDistributed header information for each performance trace record includes the following items:

Event Time The time that the event occurred. (QWHSSTCK)

IFCID The IFCID of the performance trace record being reported. (QWHSIID)

Event Type The name of the event that occurred. For SQL calls, this is the SQL statement type issued. (Derived from IFCID # and statement type (QW00nnST))


System Event Trace

Performance Trace Information:

At this point in the report, the performance trace information displayed will depend on the record’s IFCID. The following describes some of the fields that may be displayed.

In general, all NON-SERVICEABILITY fields within the particular record being reported will be displayed. Certain displays will be omitted if the field contains no significant information (blank or zero) and the field is not part of a tabular format display. Tabular format displays may be omitted, as a whole, if all of the fields that would be reported contain no significant information (blank or zero).

ACE The Agent Control Element of the thread that was used when this trace record was written. (QWHSACE)



Plan The plan name of the application. (QWHCPLAN)



DB The name of the database on which the operation reported by this record was performed (if IFCIDs 105/107 are available) or the database identifier number (if IFCIDs 105/107 are not available). (QW00nnDB)

PS The name of the pageset (tablespace) on which the operation reported by this record was performed (if IFCIDs 105/107 are available) or the pageset identifier number (if IFCIDs 105/107 are not available). (QW00nnPS)

Recid The record identifier number for the table on which the operation reported by this record was performed. (QW00nnOB)

Index Index pageset. (QW00nnIB)

Predicate: SQL predicates evaluated by Data Manager (stage 1 only). (QW00nnTP)

I/O Request Information

For an I/O operation, the following additional data is reported:

Pool Buffer pool identifier where pages are kept in storage. (QW00nnBP)

Request I/O request type. (QW0006F)

#Pgs Number of pages read or written. (QW00nnNP)

1stPg First page number to be read, in hexadecimal. (QW006PN)

ReqACE The agent control element of the record that initiated the I/O. (QW0007AC)

ElapTime The time taken to perform the I/O. (07.QWHSSTCK - 06.QWHSSTCK)

RC The Media Manager return code from the I/O request. (QW00nnMM)

System Event Trace


Scan or SQL Information

For a scan end or SQL end record, the following tabular data may be reported:

Data Type The type of data being scanned. (QW0018ID) Possible data types are as follows:

Index Index pageset.

Data Data pageset.

Rows Process

The number of rows processed by the data manager. (QW0018RP)

Rows Looked

The number of rows examined by the data manager. (QW0018LA)

Rows Qual/DM

The number of rows qualified by the data manager. (QW0018DQ)

Rows Qual/RD

The number of rows qualified by RDS. (QW0018RQ)

Rows Updated

The number of rows updated. (QW0018UP)

Rows Insertd

The number of rows inserted. (QW0018IN)

Rows Deleted

The number of rows deleted. This value is accumulated only when the rows deleted value is not -1. (QW0018DE)

Mass Del Req

The number of mass delete requests made. This value is accumulated when the rows deleted value is -1. (QW0018DE)

Pages Scan’d

The total number of pages scanned by the data manager. (QW0018PS)

Pages Scn/Ref

The total number of pages scanned due to enforcement of defined referential integrity constraints. (QW0018PR)

Rows Del/Ref

The number of rows deleted due to enforcement of defined referential integrity constraints. (QW0018DR)

Historical R


eports475

System

Event Trace

Omegamon II for DB2 V540 System Event Trace Page 6Run Date=mm/dd/yy Run Time=16:34:52 Trace Data for: mm/dd/yy Sysid=SYSG DB2id=D31AEvent Time IFCID & Event Type Performance Trace Information--------------- ------------------------ -----------------------------------------------------------------------------------------14:00:12.038336 48 SRB Exec Unit End ACE=069BFA28 ElapTime=00:00.070473 R0=7D895030 R1=7D895938 R15=0000000014:00:12.203160 21 Detail Lock Request Plan= Connid=D31A Corrid=020.CLSTAT01 Authid=SYSOPR OrigAuth=SYSOPR ACE=069BFA28 Type=ALL Resource=ALL Func=Unlock ReqType=Unconditional,Acquire,Group,CountBy RsrcHash=00000000 State=ANY Dur=Plan ExtReqType=000000 IRLM: RetCode=12 Subcodes=40000000 RetToken=00000000 OwnWU=000000FA069BFA28 ReqWU=006600FA00000000 DB2token=00A2800000A25FC014:00:12.239070 94 TCB Or SRB Resumed ACE=07556008 ElapTime=00:00.271771 RetCode=0 TODclock=AB064B8DF506FE0114:00:12.239728 93 Suspend Called ACE=07556008 ElapTime=16:07.189886 ROB=00440030 00000000 00000000 00000000 07556068 00000000 |..................-.....| +18 07556008 00000000 00000000 083150F6 00000000 00000000 |..-...........&6........|14:00:30.107673 100 Pool Storage Get/Free Start ACE=0792DD60 ElapTime=00:00.019584 Type=GETMAIN Cond=RC Class=0C ReqBytes=96 Pool=SHBS FOR LOCAL V-POOLS14:00:30.127257 101 Pool Storage Get/Free End ACE=0792DD60 ElapTime=00:00.019584 RetCode=014:00:30.129262 82 Identify Start ACE=069BFA28 ElapTime=00:00.022013 SSOB=0006AB54 PSWkey=80 AMGS=075665A8 SSIfunc=41 SSIFlags=Problem,31-bit,Normal08:16:03.401728 273 ** Unknown ** +000 050C0275 00401995 05051215 000000A0 | n | +010 0000E2E8 E2C7C4F3 F1C1F3F1 03764312 | SYSGD31A31 | +020 AB06341B C72F4E04 C4F3F1C1 40404040 | G + D31A | +030 40404040 40404040 00000002 03A0 | |

FIGURE 96. System Event Trace Report

Negative Application SQL Codes



IntroductionThis report displays the SQL statements that returned a negative SQL code. To customize this report, you can specify filtering specifications. For example, use only records with an authid of TDO209.

Default DDnameO2RPNEG

Default TitleNegative Application SQL Codes

Data SourceIFCIDs



Select ElementsDB2ID, AUTHID, PLANNAME, CONNID, CORRID, SYSID, MEMBER, GROUP

Data Elements

Mvsid The identifier of the MVS system. (ZWHMVSID)

Db2id The DB2 subsystem name. (QWHSSSID)



Plan The plan name of the application. (QWHCPLAN)






Following the thread identifiers is a trace of SQL calls issued during execution of the thread.

Performance Trace Information:

Pgmname The application program name from which the SQL call was issued. For DB2 2.3, the package name qualifiers for the program will be displayed after the CPU time. (QW00nnPN from IFCIDs 53, 58–61, or 64–66)

Stmt# The statement number of the SQL statement that was generated by the DB2 precompiler. (QW00nnSN from IFCIDs 53, 58–61, or 64–66)

SQLcode SQL return code from the SQLCA. (SQLCODE)

Module Product signature or module that detected the error (in case of an error). (SQLERRP)

ErrCodes Error codes from the SQLCA. (SQLERRD)

MsgTkns Message codes from the SQLCA. (SQLERRM)

Negative A

pplication SQ

L C

odes

478O

ME

GA

MO

N II for D

B2 H


uide, Version 540

Omegamon II for DB2 V540 Negative Application SQL Codes Page 1Run Date=mm/dd/yy Run Time=07:53:08 ODB2id=D42D, Authid=CANDL2, Planname=DSNESPRR, Corrid=CANDL2----------------------------------------------------------------------------------------------------------------------------------Mvsid: Db2id: D42D Pgmname: DSNESM68 Authid: CANDL2 Group: D42GRPPlan: DSNESPRR Stmt#: 0119 Connid: TSO Corrid: CANDL2 Member: D42DSQLcode: -151 Module: DSNXOOP ErrCodes: FFFFFE70,00000000,0,-1.0,00000000,00000000MsgTkns: “CANDL.CANDL1.F1”, Mvsid: Db2id: D42D Pgmname: DSNESM68 Authid: CANDL2 Group: D42GRPPlan: DSNESPRR Stmt#: 0119 Connid: TSO Corrid: CANDL2 Member: D42DSQLcode: -151 Module: DSNXOOP ErrCodes: FFFFFE70,00000000,0,-1.0,00000000,00000000MsgTkns: “CANDL.CANDL1.F1”, Mvsid: Db2id: D42D Pgmname: DSNESM68 Authid: CANDL2 Group: D42GRPPlan: DSNESPRR Stmt#: 0119 Connid: TSO Corrid: CANDL2 Member: D42DSQLcode: -151 Module: DSNXOOP ErrCodes: FFFFFE70,00000000,0,-1.0,00000000,00000000MsgTkns: “CANDL.CANDL1.F1”, Mvsid: Db2id: D42D Pgmname: DSNESM68 Authid: CANDL2 Group: D42GRPPlan: DSNESPRR Stmt#: 0119 Connid: TSO Corrid: CANDL2 Member: D42DSQLcode: -151 Module: DSNXOOP ErrCodes: FFFFFE70,00000000,0,-1.0,00000000,00000000MsgTkns: “CANDL.CANDL1.F1”, Mvsid: Db2id: D42D Pgmname: DSNESM68 Authid: CANDL2 Group: D42GRPPlan: DSNESPRR Stmt#: 0119 Connid: TSO Corrid: CANDL2 Member: D42DSQLcode: -151 Module: DSNXOOP ErrCodes: FFFFFE70,00000000,0,-1.0,00000000,00000000MsgTkns: “CANDL.CANDL1.F1”, Mvsid: Db2id: D42D Pgmname: DSNESM68 Authid: CANDL2 Group: D42GRPPlan: DSNESPRR Stmt#: 0119 Connid: TSO Corrid: CANDL2 Member: D42DSQLcode: -122 Module: DSNXOGB ErrCodes: FFFFFF9C,00000000,0,-1.0,00000000,00000000 Mvsid: Db2id: D42D Pgmname: DSNESM68 Authid: CANDL2 Group: D42GRPPlan: DSNESPRR Stmt#: 0119 Connid: TSO Corrid: CANDL2 Member: D42DSQLcode: -122 Module: DSNXOGB ErrCodes: FFFFFF9C,00000000,0,-1.0,00000000,00000000 Mvsid: Db2id: D42D Pgmname: DSNESM68 Authid: CANDL2 Group: D42GRPPlan: DSNESPRR Stmt#: 0119 Connid: TSO Corrid: CANDL2 Member: D42DSQLcode: -122 Module: DSNXOGB ErrCodes: FFFFFF9C,00000000,0,-1.0,00000000,00000000&vellip. Mvsid: Db2id: D42D Pgmname: DSNESM68 Authid: CANDL2 Group: D42GRPPlan: DSNESPRR Stmt#: 0119 Connid: TSO Corrid: CANDL2 Member: D42DSQLcode: -122 Module: DSNXOGB ErrCodes: FFFFFF9C,00000000,0,-1.0,00000000,00000000 GROUP TOTALS: 30 statements GRAND TOTALS: 30 statements

FIGURE 97. Negative Application SQL Coded Report

Input Reports 479

Input Reports

IntroductionThis chapter describes the Input Reports.

Chapter ContentsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480Input Record Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481Input Record Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484Input Record Dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486

17

Overview


Overview

IntroductionThe input reports display information about the records found in the input files.

Input Reports 481

Input Record Summary


IntroductionThis report provides a summary of the number and types of input records found in all of the input files, as well as the date-time ranges of those records, by DB2 subsystem.

This report is used to investigate input file contents.

Default DDnameO2RIPS

Default TitleInput Record Summary

Data SourceReporter input file



Select ElementsDB2ID, PLANNAME, CONNID, CORRID, CONTYPE, CORRNAME, AUTHID, ORIGAUTHID, IFCID, SYSID, GROUP, MEMBER



Data Elements

Record Type Summary:

RType The OMEGAMON record type being summarized.

Possible field values are as follows:

0000 Control record.

0017 DSNZPARM record.

0048 Statistical detail record.

0064 Audit/accounting detail record.

0065 Accounting summary record.

0096 Performance unit-of-work record.

0097 Performance trace record.

0098 Program change record.

Count The number of times the record type occurred during the specified time.

IFCID Summary:

IFCID The IBM IFCID record type being summarized

The number of times the IFCID type occurred during the specified time.Count

Systems:



Start The beginning timestamp for the period covered by this accounting row. It reflects either the time the thread was created or the time of DB2 signon processing that caused DB2 to externalize the accounting data. (QWHSSTCK)

End The ending timestamp for the period covered by this accounting row. It either reflects the time thread terminated or the time of DB2 signon processing that caused DB2 to externalize the accounting data. (ZWHESTCK)

Total Records

The total number of records read by the specified system for the specified period.

Input Reports

483

Input Record S

umm

ary

FIG

UR

E 98.

Inp

ut R

ecord

Su

mm

ary

Omegamon II for DB2 V540 Input Record Summary Page 1Run Date=mm/dd/yyy Run Time=16:55:05 Record Type Summary: RType Count RType Count RType Count----- -------- ----- --------- ----- ---------0097 8372 IFCID Summary: IFCID Count IFCID Count IFCID Count----- -------- ----- --------- ----- ---------0001 73 0002 73 00030018 3662 0023 1 00250107 78 0140 18 01410234 2 Sysid = SYSG DB2id = D31A Start = mm/dd/yy 06:46:52.922320 End =mm/dd/yy 16:55:19.751866 Total Records = 8170Sysid = SYSG DB2id = D31A Start = mm/dd/yy 06:46:52.922320 End =mm/dd/yy 16:55:19.751866 Total Records = 8170Sysid = SYSG DB2id = D31A Start = mm/dd/yy 06:46:52.922320 End =mm/dd/yy 16:55:19.751866 Total Records = 8170Sysid = SYSG DB2id = D31A Start = mm/dd/yy 06:46:52.922320 End =mm/dd/yy 16:55:19.751866 Total Records = 8170

Input Record Trace


Input Record Trace

IntroductionThis report displays a 1- or 2-line summary of each of the input records found in all of the input files. It also provides a summary of the number and types of input records found in all of the input files, as well as the date-time ranges of those records by DB2 subsystem.


Default DDnameO2RIPRT

Default TitleInput Record Trace

Data SourceAny IFCIDs specified in selection criteria.




Data ElementsNone

Input Reports

485

Input Record Trace

Omegamon II for DB2 V540 Input Record Trace Page 1Run Date=mm/dd/yy Run Time=15:53:37 Event Time IFCID & Event Type Performance Trace Information--------------- ------------------------------------------------------------------------------------------------------------------13:27:41.877637 1 System Statistics ACE=082A6B88 DB2id=D41B Sysid=SP13 Date=mm/dd/yy RecLen=175613:27:41.891827 2 Database Statistics ACE=082A6B88 DB2id=D41B Sysid=SP13 Date=mm/dd/yy RecLen=91213:27:41.893068 106 DSNZPARM System Parameters Plan= Connid=D41B Corrid=016.WVSMT 01 Authid=SYSOPR OrigAuth=SYSOPR Netid= LUname=(ABDD504B7E78) Commit#=1 Reqloc=D41B ACE=082A6B88 DB2id=D41B Sysid=SP13 Date=mm/dd/yy RecLen=183913:27:41.897462 202 Dynamic System Parameters ACE=082A6B88 DB2id=D41B Sysid=SP13 Date=mm/dd/yy RecLen=33613:27:49.704337 3 Accounting Record Plan=-COMMAND Connid=DB2CALL Corrid=D41BSPAS Authid=D41BSPA OrigAuth= Netid= LUname=R13D41B(ABDD50A8B710) Commit#=1 Reqloc=D41B ACE=08105008 DB2id=D41B Sysid=SP13 Date=mm/dd/yy RecLen=92413:56:06.670037 1 System Statistics ACE=082A6B88 DB2id=D41B Sysid=SP13 Date=mm/dd/yy RecLen=175613:56:06.671784 2 Database Statistics ACE=082A6B88 DB2id=D41B Sysid=SP13 Date=mm/dd/yy RecLen=91213:56:06.683147 202 Dynamic System Parameters ACE=082A6B88 DB2id=D41B Sysid=SP13 Date=mm/dd/yy RecLen=33613:56:06.690120 105 DBID/OBID Database/Tablespc Map ACE=08105178 DB2id=D41B Sysid=SP13 Date=mm/dd/yy RecLen=376

FIGURE 99. Input Record Trace

Input Record Dump


Input Record Dump

IntroductionThis report displays a full hexadecimal and character dump of the input records found in all of the input files. It also provides a summary of the number and types of input records found in all of the input files, as well as the date-time ranges of those records by DB2 subsystem.


Default DDnameO2RIPRD

Default TitleInput Record Hex Dump

Data SourceAny IFCIDs specified in selection criteria.




Data ElementsNone

Input Reports

487

Input Record D

ump

Omegamon II for DB2 V&REL. Input Record Hex Dump Page 1Run Date=mm/dd/yy Run Time=15:53:37 Event Time IFCID & Event Type Performance Trace Information----------------------------------------------------------------------------------------------------------------------------------07:54:29.541704 44 Lock Suspend/Id Call Plan=DSNESPCS Connid=TSO Corrid=PADBA2 Authid=PADBA2 OrigAuth=PADBA2 Netid= LUname=R13D411(ABD6AEF1739B) Commit#=0 Reqloc= ACE=07F5A488 DB2id=D411 Sysid= Date=mm/dd/yy RecLen=358 Data = 07ED7564 00000013 00000000 00000000 00000000 00000000 |........................| +0018 00000000 00000000 00000000 00000000 0208FE00 92C9E280 |....................kIS.| +0030 D0C00000 0000 |......|07:54:29.556427 45 Lock Suspend/Id Resume Plan=DSNESPCS Connid=TSO Corrid=PADBA2 Authid=PADBA2 OrigAuth=PADBA2 Netid= LUname=R13D411(ABD6AEF1739B) Commit#=0 Reqloc= ACE=07F5A488 DB2id=D411 Sysid= Date=mm/dd/yy RecLen=307 Data = D508F0 |N.0|07:56:33.940808 63 SQL Statement Text Plan=DSNESPCS Connid=TSO Corrid=PADBA2 Authid=PADBA2 OrigAuth=PADBA2 Netid= LUname=R13D411(ABD6AFE07323) Commit#=0 Reqloc= ACE=07F5A488 DB2id=D411 Sysid= Date=mm/dd/yy RecLen=380 Data = 0400004A 40404040 E2C5E340 C3E4D9D9 C5D5E340 C4C5C7D9 |... SET CURRENT DEGR| +0018 C5C5407E 407DC1D5 E87D4040 40404040 40404040 40404040 |EE = ‘ANY’ | +0030 40404040 40404040 40404040 40404040 40404040 40404040 | | +0048 40404040 | |07:56:34.082088 63 SQL Statement Text Plan=DSNESPCS Connid=TSO Corrid=PADBA2 Authid=PADBA2 OrigAuth=PADBA2 Netid= LUname=R13D411(ABD6AFE07323) Commit#=0 Reqloc= ACE=07F5A488 DB2id=D411 Sysid= Date=mm/dd/yy RecLen=380 Data = 0400004A 40404040 E2C5D3C5 C3E340D4 C1E74DE3 C5E7E35D |... SELECT MAX(TEXT)| +0018 40C6D9D6 D4404040 404040D7 C1D5E9C1 4BD7C1E5 D7E3C240 | FROM PADBA.PAVPTB | +0030 40404040 40404040 40404040 40404040 40404040 40404040 | | +0048 40404040 | |

FIGURE 100. Input Record Dump

Input Record Dump


489

Accessing OMEGAMON II Messagesand the Data Dictionary

IntroductionThis appendix provides information on accessing OMEGAMON II messages and the data dictionary.

Appendix ContentsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490

A

Overview


Overview

IntroductionThe Historical Main Menu provides access to the data dictionary and all OMEGAMON II messages. The messages are those that may appear during your OMEGAMON II realtime or historical sessions. The data dictionary contains descriptions of all OMEGAMON II table column names. Both documents are provided in online and printable formats. To access these documents, select DICTIONARY or MESSAGES from the Historical Main Menu (see Figure 2 on page 37).

Printing online documentsThe online document files for the data dictionary and for OMEGAMON II messages are displayed in ISPF browse mode. This enables you to search for a particular message or table column name.

To print copies of either document:

� Press F4/16 from the OMEGAMON II menu or from the Historical Main menu.

Result: The Print JCL Options panel appears.

Print JCLmOptions panelThe Print JCL Options panel enables you to print the data dictionary or OMEGAMON II messages.

FIGURE 101. Print JCL Options Panel

Candle -------------------- PRINT JCL OPTIONS -------------- OMEGAMON II for DB2 COMMAND ===> Press ENTER to create job and edit it. Enter SUBMIT to create job and automatically submit it. Confirm/modify the information below: Save jcl in dsn ===> TEST.PRINT(PRINT) Dsn qualifier ===> TD0101 Generic unit ===> SYSDA Sysout class ===> A Printer type ===> 0 0=Any 1=38xx JOB statement information: ===> //TD0101 JOB (ACCOUNT),NAME ===> //* ===> //* ===> //*

491

Overview

Set Dataset High-Level Qualifier panelIf your dataset high-level qualifier has not already been set in the ISPF dialog, the Set Dataset High Level Qualifier panel (Figure 102 on page 491) appears the first time you choose either DICTIONARY or MESSAGES from the Historical Main Menu (see Figure 2 on page 37).

FIGURE 102. Set Dataset High-Level Qualifier Panel

Enter the name of the dataset high-level qualifier needed to access the files containing the data dictionary tables and the OMEGAMON II messages. If this panel appears and you are not sure of your dataset high-level qualifier, see your database administrator.

Once you set the high-level qualifier, this panel will not appear again. Any time you select DICTIONARY or MESSAGES, you will go directly to the online file.

Candle ----------- Set Dataset High Level Qualifier -------- OMEGAMON II for DB2 COMMAND ===> Dataset does not exist...: .O2MSGS Modify the dataset high level qualifier for your installation: Dsn qualifier ===>

Enter END command to return to Historical main menu

Overview


493

Guidelines for Sizing VSAM Datasets

IntroductionThis appendix provides guidelines for sizing VSAM datasets.

Appendix ContentsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494

B

Overview


Overview

IntroductionYou can store collected, extracted, and summarized data in VSAM datasets. This method requires that you define and initialize your datasets to store DB2 data.

OMEGAMON II generates sample JCL in rhilev.RKD2SAM(HCRTcccc) to do this at customization time. In addition, rhilev.RKD2SAM(ACRTcccc) contains sample JCL that you can use to define and initialize the datasets.

Note: You must have chosen VSAM as the storage type you want to use.

TableThe following table provides guidelines for sizing your VSAM datasets, based on average record size.

Table 17. VSAM Dataset Allocation Guidelines

Record Type Record Length

Avg.* No. of Rec./CI

3380 Device 3390 Device

No. of CI/Cyl.

Avg. No. of

Rec./Cyl.

No. of CI/Cyl.

Avg. No. of

Rec./Cyl.

STATISTICS 1338 4 174 532 208 635

Buffer Pool 184 29 174 3870 208 4619

Group Buffer Pool 124 43 174 5743 208 6855

Package 256 21 174 2782 208 3320

DDF 184 29 174 3870 208 4619

† Average Record 2218 2 174 321 208 383

ACCOUNTING 1208 4 174 590 208 704

Buffer Pool 80 67 174 8902 208 10625


Package 256 21 174 2782 208 3320

DDF 248 21 174 2872 208 3427

† Average Record 1180 3 174 379 208 452

ACCOUNTING SUMMARY

1510 4 174 472 208 563

Buffer Pool 80 67 174 8902 208 10625


Package 256 21 174 2782 208 3320

DDF 264 20 174 2698 208 3220

† Average Record 2182 2 174 326 208 390

495

Overview

DSNZPARM 4202 1 174 169 208 202

Audit Fail 430 12 174 1656 208 1977

Audit Control 380 14 174 1874 208 2237

Audit DDL 406 13 174 1754 208 2093

Audit DML 146 36 174 4878 208 5822

Audit Bind 514 10 174 1385 208 1654

Audit ChangeID 398 13 174 1789 208 2136

Audit Utility 154 35 174 4624 208 5519

† The average record is calculated using the values from a main section (Accounting/Statistics) with values from 2 buffer pool and 2 package sections.

* Assuming 30% data compression ratio.

Table 17. VSAM Dataset Allocation Guidelines (continued)

Record Type Record Length

Avg.* No. of Rec./CI

3380 Device 3390 Device

No. of CI/Cyl.

Avg. No. of

Rec./Cyl.

No. of CI/Cyl.

Avg. No. of

Rec./Cyl.

Overview


497

Symbols<&nopage>types of reports

see report categories 144

Aaccounting class traces 107, 124Accounting Lock Activity report (statistics) 319, 321Accounting report (accounting) 190, 199accounting report type

report subjects for 147accounting reports 106, 123

Buffer Pool Activity 216Detail 232, 235Distributed Data Facility Activity 186, 225, 230Global Lock Activity 193, 243, 246Group Buffer Pool Activity 184, 220, 224Lock Activity 191, 239, 242overview 181, 215Package Detail 188, 198, 280, 284Parallel Task Activity 251, 253Resource Limit Activity 247, 250Scan Activity 254, 257Sort Activity 258, 260SQL Activity 195, 261, 266Summary 268, 271Termination Summary 272, 274Time Summary 275, 279

action codesfor report panels 120

Adobe portable document format 19application buffer pool access

performance 430Application Buffer Pool Access report 431application buffer pool access report

sample report, performance 431Application Buffer Pool I/O report 436application buffer pool I/O report

performance 433sample report, performance 436

application event tracesample report, performance 428

application event trace reportperformance 422

Application SQL Trace report 420application SQL trace report

performance 414

sample report, performance 420Application Trace Detail report 410application trace detail report


Application Trace Events report 428application trace summary report 396


application tracesdata extraction 56

audit report typereport subjects for 148

audit reports 109, 126Authorization Control 357, 359Authorization Failures 354Authorization ID Changes 369, 371DDL Access 360, 362DML Access 363, 365DML Statements at Bind 366, 368overview 205, 353, 379, 393summary 375, 376utility access 372, 373

Audit Summary report 376audit summary report

audit 375sample report, audit 376

Authorization Control report (audit) 357, 359Authorization Failures report (audit) 354Authorization ID Changes report (audit) 369, 371

Bbatch

data extraction 54Bind Activity report (statistics) 342, 345breaks, control 115Buffer Pool Activity report (accounting) 182, 216Buffer Pool Activity report (statistics) 202, 288, 294

CCandle Web site 23categories for reports 144CI display command 35collectors

41Command Activity report (statistics) 301, 304

Index


Common Interfaceonline data collector 40

control breaks 115CPU Time Summary report (statistics) 203, 305,

307creating historical reports 104, 112customizing

report options 114

Ddata extraction 54, 58

application traces 56data source 55keyword descriptions 68setting options (keywords) 59setting options, customization panels 58storage destination 58, 87submitting job for 58wildcard characters 67

data summarizationkeyword descriptions 92overview 86setting options, customization panels 87setting options, keywords 89source data 87submitting job 88wildcard characters 99

data, sourcefor OMEGAMON II for DB2 reporter 104, 112

datasetsrhilev.RKD2PAR(COPT) 42rhilev.RKD2SAM 57

datasets, sourcespecifying for reports 116

date, setting for reports 118DB2 load utility 32DB2 tables

reporting methods using 33specifying for reports 116storing data 32using insert mode 32using load mode 32

DDL Access report (audit) 360, 362ddnames 141Detail report (accounting) 232, 235Detail report (statistics) 308, 310Distributed Data Facility Activity report

(accounting) 186, 225, 230Distributed Data Facility Activity report

(statistics) 346, 349DML Access report (audit) 363, 365DML Statements at Bind report (audit) 366, 368DSNZPARM report type

report subjects for 148DSNZPARM reports

overview 380system installation parameters 381

DSNZPARM Reports panel 108, 128

EEDM Pool Activity report (statistics) 316, 318EDM Pool I/O report 447EDM pool I/O report

performance 446errors specification 168extraction, data 54extractor

see data extraction

Ffilter specification 155

accounting field values 158accounting fields 156field values 157performance field values 158performance fields 156

filtering options 117

GGDDM 131GDDM Presentation Graphics Facility (PGF) 131Global Lock Activity report (accounting) 193, 194,

243, 246Global Lock Activity report (statistics) 322, 325Global Lock Suspension report 457global lock suspension report


Graphical Data Display Manager (GDDM) 131graphical reports 131Group Buffer Pool Activity report (accounting) 184,

220, 224Group Buffer Pool Activity report (statistics) 296,

300group by options 115groupby specification 159GTF data

extractor 57

Hhistorical components

overview 30historical features

illustration 28Historical Main Menu 37

499

accessing 37historical reports

accounting 106, 123Accounting data(accounting) 190, 199Accounting Lock Activity (statistics) 319, 321action codes 120audit 109, 126

utility access 372audit, summary 375Authorization Control (audit) 357, 359Authorization Failures (audit) 354Authorization ID Changes (audit) 369, 371Bind Activity (statistics) 342, 345Buffer Pool Activity (accounting) 182, 216Buffer Pool Activity (statistics) 202, 288, 294canceling options 114COBOL, C reporting 176Command Activity (statistics) 301, 304CPU Time Summary (statistics) 203, 305, 307creating 104, 112date and time options 118DDL Access (audit) 360, 362Detail (accounting) 232, 235Detail (statistics) 308, 310Distributed Data Facility Activity (accounting) 186,

225, 230Distributed Data Facility Activity (statistics) 346,

349DML Access (audit) 363, 365DML Statements at Bind (audit) 366, 368DSNZPARM 108, 128, 381EDM Pool Activity (statistics) 316, 318filtering options 117Global Lock Activity (accounting) 193, 194, 243,

246Global Lock Activity (statistics) 322, 325graphical 131Group Buffer Pool Activity (accounting) 184, 220,

224Group Buffer Pool Activity (statistics) 296, 300headings for 135input 130input record dump 486input record summary 480input record trace 484Lock Activity (accounting) 191, 192, 239, 242Log Activity (statistics) 326, 329Open/Close Activity (statistics) 350, 352Package Detail (accounting) 188, 198, 280, 284Parallel Task Activity (accounting) 251, 253performance 128

application buffer pool access 430

application buffer pool I/O 433application event trace 422application SQL trace 414application trace detail 400application trace summary 395EDM pool I/O 446lock contention 459negative application SQL codes 476p-lock detail 467system buffer pool access 438system buffer pool I/O 442system event trace 472

QMF 177report panels, using 120Resource Limit Activity (accounting) 247, 250return codes 135SAS 175saving options 114Scan Activity (accounting) 254, 257see report request languagesetting options 115Sort Activity (accounting) 258, 260source datasets, specifying 116source DB2 tables, specifying 116SQL Activity (accounting) 195, 196, 197, 261,

266SQL Activity (statistics) 330, 334statistics 106, 121

global lock suspension 454lock suspension 449

Subsystem Activity (statistics) 336, 338Summary (accounting) 268, 271Summary (statistics) 339, 341system installation parameters 381Termination Summary (accounting) 272, 274Time Summary (accounting) 275, 279traces, accounting class 107, 124types of 104, 105, 112, 119

IIFCID accounting reports

accounting 190, 199Global Lock Activity 194Lock Activity 192SQL Activity 196, 197

IFCID-based reports 103, 176accounting 181accounting reports

Buffer Pool Activity 182DSNZPARM reports 205

overview 206statistics reports


overview 201Input Record Summary 480input report type

report subjects for 151input reports 130, 480

record dump 486record summary 480record trace 484

insert mode 32ISPF Primary Options Menu 37

KKD2SPF CLIST 37keywords

data extraction 59, 68data summarization 89, 92online data collection 44

Lload mode 32load utility, DB2 32Lock Activity report (accounting) 191, 192, 239,

242Lock Contention report 464lock contention report


Lock Suspension report 452lock suspension report


Log Activity report (statistics) 326, 329log data 32

Mmary 37multiple collectors

prerequisites 41

Nnative QMF 177negative application SQL codes

performance 476Negative Application SQL Codes report 477negtive application SQL codes report

sample report, performance 477

Oonline data collection

keyword descriptions 44setting options, customization panels 42setting options, keywords 42

wildcard characters 51Open/Close Activity report (statistics) 350, 352options

setting data extraction options 58options for OMEGAMON II for DB2 reporter

setting 114options, setting

data summarization 87data summarization keywords 89online data collection 42online data collection (keywords) 42

order by options 115orderby specification 161output specification 162

PPackage Detail report (accounting) 188, 198, 280,

284panel

Historical Main Menu 37Statistics Reports 121

Parallel Task Activity report (accounting) 251, 253PDF files, adding annotations 20performance report types

report subjects for 149performance reports 128

application buffer pool access 430sample report 431

application buffer pool I/O 433sample report 436

application event trace 422sample report 428

application SQL trace 414, 420application trace detail 400

sample report 410application trace summary 395application trace summary sample report 396EDM pool I/O 446

sample report 447global lock suspension 454

sample report 457lock contention 459

sample report 464lock suspension 449

sample report 452negative application SQL codes 476, 477overview 394p-lock detail 467

sample report 469system buffer pool access 438

sample report 440system buffer pool I/O 442

501

sample report 444system event trace 472

sample report 474PGF 131P-Lock Detail report 469p-lock detail report


printing problems 19

QQMF reports 177

Rrecord dump report

input 486record summary report

input 480record trace report

input 484relative time, setting for reports 118report categories 144report request language

accounting reports 147audit reports 148ddnames 141DSNZPARM reports 148errors specification 168filter specification 155format of request 143groupby specification 159input reports 151orderby specification 161output specification 162overview 140performance reports 149sample JCL 141selection specification 155SET GLOBAL statement 143statistics reports 145time specification 152title specification 166values specification 162

report specificationerrors 168filter 155groupby 159orderby specification 160output 162report categories 144report subjects 144selection 155

time 152title 166values 162

report subjects 144report types

accounting 147audit 148DSNZPARM 148input 151performance 149statistics 145

reporting methodsoverview 36using DB2 tables 33using VSAM datasets 35

reportssee historical reportingstatistics 201, 287

Resource Limit Activity report (accounting) 247, 250return codes

OMEGAMON II for DB2 reporter 135rhilev.RKANSAS 175rhilev.RKD2PAR(COPT) 42rhilev.RKD2SAM(KO2JGTFS) 57rhilev.TKANSAMP 176

Ssample report 373, 376SAS reports 175, 176Scan Activity report (accounting) 254, 257selection criteria 117selection specification 155

accounting field values 158accounting fields 156field values 157performance field values 158performance fields 156

Set Dataset High-Level Qualifier panel 491SET GLOBAL statement 143setting options

data extraction 59data summarization 87, 89online data collection (customization panels) 42

setting report options 114date and time 118source datasets 116source DB2 tables 116

sizing guidelinesVSAM datasets 494

SMF dataextractor 56

Sort Activity report (accounting) 258, 260source data


for OMEGAMON II for DB2 reporter 104, 112source datasets

specifying 116source DB2 tables

specifying for reports 116SQL Activity report (accounting) 195, 196, 197,

261, 266SQL Activity report (statistics) 330, 334START TRACE command 56statistics report type 145statistics reports 106, 121

Accounting Lock Activity 319, 321Bind Activity 342, 345Buffer Pool Activity 202, 288, 294Command Activity 301, 304CPU Time Summary 203, 305, 307Detail 308, 310Distributed Data Facility Activity 346, 349EDM Pool Activity 316, 318Global Lock Activity 322, 325Group Buffer Pool Activity 296, 300Log Activity 326, 329Open/Close Acitivty 352Open/Close Activity 350overview 287SQL Activity 330, 334Subsystem Activity 336, 338Summary 339, 341

Statistics Reports panel 121storage

DB2 tables 32subjects for reports

see report subjectsSubsystem Activity report (statistics) 336, 338summarizer

see data summarizationSummary report (accounting) 268, 271Summary report (statistics) 339, 341switch-and-archive facility 34

CI display command 35System Buffer Pool Access report 440system buffer pool access report


system buffer pool I/Osample report, performance 444

System Buffer Pool I/O report 444system buffer pool I/O report

performance 442system event trace

sample report, performance 474System Event Trace report 474system event trace report

performance 472system installation parameters report

DSNZPARM 381

TTermination Summary report (accounting) 272, 274time specification 152Time Summary report (accounting) 275, 279time, setting for reports 118title specification 166traces, accounting class 107, 124

Uutility access report

audit 372sample report, audit 373

Utitlity Access report 373

Vvalues specification 162variable replacement 34VSAM datasets 494

allocation guidelines 494CI display command 35preparing datasets 494reporting methods using 35resource usage 35sizing guidelines 494switch-and-archive facility 34

WWeb site, Candle 23wildcard characters

with report options 117

historical reporting guide -...

Documents