DB2 Query Monitor User's Guide.pdf

8/9/2019 DB2 Query Monitor User's Guide.pdf

1/70

DB2 Query Monitor for OS/390

Users Guide

Version 1 Release 1

SC27-0968-00


2/70


3/70

DB2 Query Monitor for OS/390

Users Guide

Version 1 Release 1

SC27-0968-00


4/70

Note!Before using this information and the product it supports, be sure to read the general information under notices.

First Edition (December 2000)

This edition applies to Version 1 Release 1 Modification Level 0, program number 5655E67, and to all subsequentreleases and modifications until otherwise indicated in new editions. Make sure you are using the correct edition forthe level of the product. Order Publications through your IBM representative or the IBM branch office serving yourlocality.

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in anyway it believes appropriate without incurring any obligation to you.

Copyright International Business Machines Corporation 2000. All rights reserved.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.


5/70

ContentsChapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . 1Product Description. . . . . . . . . . . . . . . . . . . . . . . . 1Highlights . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Performance and Security . . . . . . . . . . . . . . . . . . . . . 1

Performance . . . . . . . . . . . . . . . . . . . . . . . . . 1Security . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Hardware and Software Requirements. . . . . . . . . . . . . . . . . 2DB2 Version . . . . . . . . . . . . . . . . . . . . . . . . . 2ISPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2DASD Datasets . . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 2. Tailoring Query Monitor Files . . . . . . . . . . . . . . . 3Creating Table Spaces . . . . . . . . . . . . . . . . . . . . . . 3Bind the DB2/QM Plans . . . . . . . . . . . . . . . . . . . . . . 3Defining JCL for a DB2/QM Subsystem . . . . . . . . . . . . . . . . 3Defining Parameters Passed to the DB2/QM Subsystem . . . . . . . . . . 3

MONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . 4SUBSYS . . . . . . . . . . . . . . . . . . . . . . . . . . 4INTERVAL . . . . . . . . . . . . . . . . . . . . . . . . . . 4PLANS . . . . . . . . . . . . . . . . . . . . . . . . . . . 4DBRMS . . . . . . . . . . . . . . . . . . . . . . . . . . . 5SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5AUTHID . . . . . . . . . . . . . . . . . . . . . . . . . . . 5EXPROF . . . . . . . . . . . . . . . . . . . . . . . . . . 6EXCEPTIONS . . . . . . . . . . . . . . . . . . . . . . . . 6

Starting a DB2/QM Subsystem . . . . . . . . . . . . . . . . . . . 6As a started task. . . . . . . . . . . . . . . . . . . . . . . . 6As a job . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Stopping a DB2/QM Subsystem . . . . . . . . . . . . . . . . . . . 6As a started task. . . . . . . . . . . . . . . . . . . . . . . . 6As a job . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Defining Interval Processing . . . . . . . . . . . . . . . . . . . . 7

Chapter 3. Configuring DB2 Query Monitor . . . . . . . . . . . . . . 9Configuring Subsystem and DB2 Query Monitor Information. . . . . . . . . 9

Defining the CQMCNTFL Control File . . . . . . . . . . . . . . . . 9Invoking QM . . . . . . . . . . . . . . . . . . . . . . . . . 9Starting the Configuration Dialog . . . . . . . . . . . . . . . . . . 9

GDG Base Model DSN . . . . . . . . . . . . . . . . . . . . 10DB2 Control Dataset . . . . . . . . . . . . . . . . . . . . . 10DB2 Subsystem ID . . . . . . . . . . . . . . . . . . . . . 10Command Selection Values . . . . . . . . . . . . . . . . . . 10

Configure Subsystem Information . . . . . . . . . . . . . . . . . 10Configure DB2 Query Monitor-Specific Information . . . . . . . . . . . 1112

Chapter 4. Verifying Installation . . . . . . . . . . . . . . . . . . 13Verifying Installation . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 5. Query Monitor Space Calculations . . . . . . . . . . . . 15Partitions and Intervals in Query Monitor . . . . . . . . . . . . . . . 15

Sizing the THRDS11 Partitioned Table Space and Partitioning Indexspace 15Create Tablespace Threads . . . . . . . . . . . . . . . . . . . 16Create Index CQM.THREADS_V11_IX . . . . . . . . . . . . . . . 16

Copyright IBM Corp. 2000 iii


6/70

Sizing the BUFFPL11 Partitioned Table Space . . . . . . . . . . . . . 16Create Tablespace BUFFPL11 . . . . . . . . . . . . . . . . . . 16Create Index CQM.BUFFERPOOLS_V11_IX . . . . . . . . . . . . . 16

Sizing the DBRMS11 Partitioned Table Space . . . . . . . . . . . . . 17Create Tablespace DBRMS11 . . . . . . . . . . . . . . . . . . 17Create Index CQM.DBRMS_V11_IX . . . . . . . . . . . . . . . . 17

Sizing the STMTS11 Partitioned Table Space. . . . . . . . . . . . . . 17

Create Tablespace STMTS11 . . . . . . . . . . . . . . . . . . 18Create Index CQM.STATEMENTS_V11_IX . . . . . . . . . . . . . 18

Adding Data Partitions . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 6. Getting Started . . . . . . . . . . . . . . . . . . . . 21Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Functions and Concepts . . . . . . . . . . . . . . . . . . . . 21DB2 QM Subsystems . . . . . . . . . . . . . . . . . . . . 21TSO/ISPF Facility . . . . . . . . . . . . . . . . . . . . . . 21Intervals . . . . . . . . . . . . . . . . . . . . . . . . . 21Navigation Commands and Actions . . . . . . . . . . . . . . . 21

Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Monitoring Profile . . . . . . . . . . . . . . . . . . . . . . . 23

Agents . . . . . . . . . . . . . . . . . . . . . . . . . . 23Application Profile . . . . . . . . . . . . . . . . . . . . . . . 23Exception Profile . . . . . . . . . . . . . . . . . . . . . . . 23

Exceptions . . . . . . . . . . . . . . . . . . . . . . . . 23Thresholds . . . . . . . . . . . . . . . . . . . . . . . . 23

Starting IBM DB2 Query Monitor . . . . . . . . . . . . . . . . . . 24Selection Menu. . . . . . . . . . . . . . . . . . . . . . . . 241. View Current Activity . . . . . . . . . . . . . . . . . . . . . 242. View Past Activity . . . . . . . . . . . . . . . . . . . . . . 243. Work with Monitoring Agents . . . . . . . . . . . . . . . . . . 244. View DB2 Command Activity . . . . . . . . . . . . . . . . . . 245. Work with Profiles . . . . . . . . . . . . . . . . . . . . . . 25S. Setup . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 7. Viewing Current Activity . . . . . . . . . . . . . . . . 271. View Current Activity . . . . . . . . . . . . . . . . . . . . . . 27

Function . . . . . . . . . . . . . . . . . . . . . . . . . . 27Display Threads . . . . . . . . . . . . . . . . . . . . . . 27

Features . . . . . . . . . . . . . . . . . . . . . . . . . . 27Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Valid Commands Entered in the Option Field . . . . . . . . . . . . 28Valid Line Commands . . . . . . . . . . . . . . . . . . . . 28

Chapter 8. Viewing Historical Activity . . . . . . . . . . . . . . . . 332. View Past Activity . . . . . . . . . . . . . . . . . . . . . . . 33

Function . . . . . . . . . . . . . . . . . . . . . . . . . . 33Features . . . . . . . . . . . . . . . . . . . . . . . . . . 33Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Valid Line Commands . . . . . . . . . . . . . . . . . . . . 33Interval Thread Activity . . . . . . . . . . . . . . . . . . . . 33

Chapter 9. Monitoring Subsystems . . . . . . . . . . . . . . . . . 353. Work with Monitoring Agents . . . . . . . . . . . . . . . . . . . 35

Function . . . . . . . . . . . . . . . . . . . . . . . . . . 35Features . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

iv DB2 Query Monitor for OS/390: Users Guide


7/70

Valid Line Commands . . . . . . . . . . . . . . . . . . . . 35

Chapter 10. Viewing DB2/QM Command Activity . . . . . . . . . . . 374. View DB2 Command Activity . . . . . . . . . . . . . . . . . . . 37


Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Chapter 11. Defining Selection Criteria . . . . . . . . . . . . . . . 395. Work with Profiles . . . . . . . . . . . . . . . . . . . . . . . 39


Monitoring Profiles . . . . . . . . . . . . . . . . . . . . . 39Application Profiles . . . . . . . . . . . . . . . . . . . . . 41Exception Profiles . . . . . . . . . . . . . . . . . . . . . . 43

Chapter 12. Setup . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 13. Common Tasks . . . . . . . . . . . . . . . . . . . 49

Chapter 14. DB2/QM Memory Usage Statistics . . . . . . . . . . . . 51Displaying Activity . . . . . . . . . . . . . . . . . . . . . . . . 51

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Output . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 15. DB2 Query Monitor Operator Commands . . . . . . . . . 53Valid Commands . . . . . . . . . . . . . . . . . . . . . . . . 53

DISPLAY DATASPACES . . . . . . . . . . . . . . . . . . . . 53INTERVAL . . . . . . . . . . . . . . . . . . . . . . . . . 53

Appendix. Notices . . . . . . . . . . . . . . . . . . . . . . . 55Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Contents v


8/70

vi DB2 Query Monitor for OS/390: Users Guide


9/70

Chapter 1. Introduction

Product DescriptionIBM DB2 Query Monitor for OS/390 provides real-time and historical views intoquery activity throughout your DB2 subsystems. Monitoring agents that can bestarted and stopped dynamically use menu-driven criteria to watch up to 64 DB2subsystems. With Query Monitor you can pinpoint activity that is important to yourbusiness. This enables you to spot potential problems and take steps to resolvethese problems quickly.

One true advantage of Query Monitor is that you can choose what data is gatheredduring monitoring, specify when it will be gathered, and identify about whom datawill be gathered.

When thresholds are crossed, activity is flagged for investigation and possibletermination. At intervals set by you, real-time activity is saved from memory to diskand optionally, from disk to database.

HighlightsWith Query Monitor, you can:v Spot trouble in real-time before it causes significant waste of DB2 resourcesv Locate problem queries as they executev Identify users and locations issuing problem queriesv Set thresholds that automate early warnings and corrective actionsv Terminate unwanted queriesv Clear up processes that are blocking DB2 availabilityv Maintain high availability

Performance and Security

PerformanceIBM DB2 Query Monitor uses dataspace storage to record SQL statistical data. Aninstallation may limit the amount of data stored by defining monitoring selectioncriteria via Monitoring Profiles. The DB2/QM Monitoring Agents do not gatherstatistics on threads that do not match the specified selection criteria. Furthermore,an installation may limit DB2/QMs use of dataspace storage by defining limits onthe sizes of the individual dataspaces.

Monitoring Agent code is optimized to ensure that the least possible overhead is

introduced. Since the monitoring agent code works solely with memory structures,DB2/QM does not invoke OS/390 services that introduce delays and waits. Aseparate task outside of monitoring agent processing offloads data from the variousdataspaces into external DB2 tables.

SecurityThe installation of DB2/QM requires you to have DBADMIN authority, at a minimum.

Since IBM DB2 Query Monitor displays results of executed SQL queries, it does notcompromise the integrity of the underlying DB2 subsystems it monitors. Any DB2

Copyright IBM Corp. 2000 1


10/70

commands DB2/QM issues on behalf of its users flow through the standard DB2interfaces and are subject to the installations DB2 security policies.

Hardware and Software Requirements

DB2 VersionQuery Monitor (QM) requires an installation of DB2, version 5 or later.

ISPFISPF, version 4, is required for Query Monitor.

DASD DatasetsQuery Monitors libraries can reside on 3380 or 3390 DASD. The total spacerequired for the target library is 79 3390 tracks. The total space required for thedistribution library is 220 3390 tracks.

Query Monitor requires the following dataset:

DATASET MEMBERS DIRBLKS TRACKS

SCQMLOAD 50 46 39

SCQMPENU 91 20 16

SCQMMENU 11 5 5

SCQMSAMP 5 5 8

SCQMDBRM 12 15 6

SCQMSLIB 1 2 2

SCQMCLST 2 2 2

2 DB2 Query Monitor for OS/390: Users Guide


11/70

Chapter 2. Tailoring Query Monitor Files

To install Query Monitor you must tailor specific DB2 Query Monitor files for yoursystem.

Creating Table SpacesTailor and run the member CQM#DDL from the SCQMSAMP library to create thetablespaces required for DB2/QM interval processing. IBM recommends placingthese tablespaces in a separate bufferpool and storage group. For information onsize requirements for these tablespaces, refer to Chapter 5.Define the DB2/QM tablespaces only in the DB2 subsystem that will store DB2/QMinterval data.

Bind the DB2/QM PlansTailor and run the job CQM#BIND from the SCQMSAMP library to bind the DB2/QMplans.

Defining JCL for a DB2/QM SubsystemA DB2/QM subsystem may run as a started task or as a job under the control ofJES. If you wish to run DB2/QM as a started task, the JCL must reside in acatalogued procedure library. Tailor the following statements to define JCL for aDB2/QM subsystem. The member CQMPROC of the SCQMSAMP library containsa copy of this JCL.//CQMPROC PROC HILEVEL=CQM.V1R1,//CQMPROC EXEC PGM=CQMMAIN.//PARM=(SUBSYS(TEST),// MONITOR(DSN)// PLANS(1500),// DBRMS(5000),// SQL(300000),// INTERVAL(60))//STEPLIB DD DSN=&HILEVEL..SCQMLOAD,DISP=SHR//SYSUDUMP DD SYSOUT=*,

For a description of the parameters passed to CQMMAIN, see DefiningParameters Passed to the DB2/QM Subsystem, below.

Defining Parameters Passed to the DB2/QM SubsystemThe CQMMAIN program uses the following parameters to define the DB2/QMsubsystem name, the monitored DB2 subsystems, the length of the recordinginterval, and the pool sizes that contain the DB2/QM measurement blocks.

Code these parameters on the PARM keyword of the EXEC statement or placethem in a 80 bytes parameter file allocated to the CQMPARMS DD.

When using CQMPARMS parameter file, DB2/QM ignores the parameters coded onthe EXEC statement. Use a hyphen to continue lines in the CQMPARMS parameterfile and do not code line numbers.



12/70

MONITORSyntax:

MONITOR(db2_subsys1,profile_name1,db2_subsys2,profile_name2.)

The MONITOR parameter is a given instance that DB2/QM records SQLperformance data for, defined for the DB2 subsystems. A given DB2/QM subsystemcan monitor up to 64 DB2 subsystems.Example:MONITOR(R51A,R51APROF,R51B,R51BPROF)

The above example instructs DB2/QM to start monitoring agents for DB2subsystems R51A and R51B at startup. The parameter also instructs the monitoringagents for DB2 subsystems R51A and R51B to use monitoring profiles R51APROFand R51BPROF, respectively

SUBSYSSyntax:

SUBSYS(db2qm_subsystem_name)

The SUBSYS parameter defines the DB2/QM subsystem name. A DB2/QMsubsystem does not correspond to an OS/390 subsystem. The name must be 1-4characters in length.Example:SUBSYS(DBQM)

INTERVALSyntax:

INTERVAL(recording_interval_length)

The INTERVAL parameter defines the length of the recording interval in minutes.The length of the recording interval can range from 1 to 86400 minutes.ExampleINTERVAL(30)

The above example defines a recording interval length of 30 minutes.

PLANSSyntax:

PLANS(size_of_plan_measurement_block_pool)

The PLANS parameter defines the size of the DB2/QM plan measurement blockpool. DB2/QM records data related to plan execution in plan measurement blocks.Define a plan measurement block pool size large enough to contain the maximumamount of plans executed within the recording interval.

Note: DB2/QM operation does not require this parameter. Only use this parameterto limit the amount of dataspace storage used by DB2/QM.



13/70

If DB2/QMs dataspace storage requirements exceed the limitations imposedby this parameter, SQL measurement data may be lost. Omitting thisparameter forces DB2/QM to set the limit to the amount of blocks that can fitinto a 2GB dataspace. The amount of control blocks, or nodes available, canbe determined by issuing an F DB2QM,DISPLAY DATASPACES commandafter startup.

DBRMSSyntax:

DBRMS(size_of_dbrm_measurement_block_pool)

The DBRMS parameter defines the size of the DB2/QM DBRM measurement blockpool. DB2/QM records data related to statement execution within a DBRM/Packagein DBRM measurement blocks. Define the DBRM measurement block pool sizelarge enough to contain the maximum amount of individual SQL statementsexecuted within a recording interval.

Note: DB2/QM operation does not require this parameter. Only use this parameter

to limit the amount of dataspace storage used by DB2/QM.

If DB2/QMs dataspace storage requirements exceed the limitations imposedby this parameter, SQL measurement data may be lost. Omitting thisparameter forces DB2/QM to set the limit to the amount of blocks that can fitinto a 2GB dataspace. The amount of control blocks, or nodes available, canbe determined by issuing an F DB2QM,DISPLAY DATASPACES commandafter startup.

SQLSyntax:

SQL(size_of_sql_image_pool)

The SQL parameter defines the size of the DB2/QM SQL image block pool.DB2/QM records SQL statement images in SQL image blocks. Define SQL imageblock pool size large enough to contain the maximum amount of statement imagescaptured within the recording interval. Each SQL image block contains 80characters of a given SQL image. DB2/QM can use multiple SQL image blocks torepresent up to 4096 bytes of a given SQL image.

Note: DB2/QM operation does not require this parameter. Only use this parameterto limit the amount of dataspace storage used by DB2/QM.

If DB2/QMs dataspace storage requirements exceed the limitations imposed

by this parameter, SQL measurement data may be lost. Omitting thisparameter forces DB2/QM to set the limit to the amount of blocks that can fitinto a 2GB dataspace. The amount of control blocks, or nodes available, canbe determined by issuing an F DB2QM,DISPLAY DATASPACES commandafter startup.

AUTHIDSyntax:

AUTHID(DB2 AUTHID)

Chapter 2. Tailoring Query Monitor Files 5


14/70

The AUTHID parameter defines the DB2 AUTHID that DB2/QM uses to establish aconnection to DB2 during interval processing.Example:AUTHID(DB2USER)

The above example identifies DB2USER as the DB2 Authid that DB2/QM will use toconnect to DB2 during interval processing.

EXPROFSyntax:

EXPROF(EXCEPTION_PROFILE_NAME)

The EXPROF parameter defines the name of the exception profile that DB2/QMloads at startup.Example:EXPROF(R51AEXPF)

The above example instructs DB2/QM to use the exception profile EXPRF1.

EXCEPTIONSSyntax:

EXCEPTIONS(EXCEPTION_SCAN_INTERVAL_LENGTH)

The EXCEPTIONS keyword defines the length of the exception scan interval inseconds. The default scan interval length is 30 seconds.Example:EXCEPTIONS(10)

The above example defines an exception scan interval length of 10 seconds.

Starting a DB2/QM Subsystem

As a started taskIssue the MVS START command to start the started procedure JCL.Example:START CQMPROC

As a jobSubmit the DB2/QM JCL from TSO or ISPF.Example://CQMJOB JOB, DB2QM,CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID//STEP1 EXEC CQMPROC

Stopping a DB2/QM Subsystem

As a started taskIssue the MVS STOP command to stop the DB2/QM started procedure.Example:P CQMPROC



15/70

As a jobIssue the MVS STOP command to stop the DB2/QM job. Follow the procedures forstopping a DB2/QM started task, above.

Note: The MVS CANCEL command can terminate a DB2/QM subsystem.

Avoid using the MVS FORCE command to terminate a DB2/QMsubsystem. Unpredictable results may occur otherwise, including thetermination of any monitored DB2 subsystems.

Defining Interval ProcessingThe installation of DB2/QM requires you to choose optimum values for the length oftime that DB2/QM holds related SQL performance data in memory. Too long of aninterval may degrade system performance due to DB2/QMs use of processorstorage and too small of an interval may cause DB2/QM to thrash writing data to itsrelated DB2 tables.

The INTERVAL, AUTHID, and MONITOR parameters relate directly to interval

processing. Definitions are required in the CQMCNTFL control file that define howDB2/QM attaches to DB2. DB2/QM uses the first DB2 subsystem listed in theMONITOR parameter to record its interval SQL performance data.1. Tailor member CQM@UDB2 in the SCQMSAMP library. This JCL unloads

DB2/QM interval data to history datasets.2. Tailor member CQM@LDB2. This JCL loads off-loaded DB2/QM interval data

into the HISTORY INTERVAL table.

The CQM@UDB2 member unloads all partitions of interval data that have not beenunloaded. Thus, a single run of this job can unload all data for a day. You can alsosubmit this job every time interval processing is started, on the hour. A GDG baseshould be created before running this job. Make sure you set the limit on the GDG

base large enough to hold all data you want to keep. For example, if you are goingto run this job once a day and you want to keep a month of data, set the limit to 30.

The CQM@LDB2 job takes the off-loaded dataset and loads it back into aHISTORY version of the DB2/QM tables. This data is not deleted from these tablesuntil the CQM@LDB2 job is re-run. This job loads data back into the HISTORYINTERVAL table. This job lets you load multiple unloaded datasets that areconcatenated into one run.

Some of the programs in the load library must run APF authorized. Include the loadlibrary (SCQMLOAD) as part of your authorized list.

Chapter 2. Tailoring Query Monitor Files 7


16/70


17/70


18/70

--------------------------Enter DB2 System Parameters-------------------------Command ==>

GDG Base Model DSN ==>DB2 Control Dataset ==>(Pre-allocated)

Enter DB2 Subsystem Info:

DB2 Subsystem ID ==> (1-4 Character Subsystem ID)

Valid command selection values are:1: ZPARM, BSDS, and Load Library Information2: DB2 Query Monitor Parameters

GDG Base Model DSNEnter the reference dataset to use for dataset creation processing.

DB2 Control DatasetThis field displays the dataset that is used as the control file.

DB2 Subsystem IDEnter the subsystem identifier (SSID) for the DB2 subsystem you want to configure.This is a four-character maximum field. You must run through the followingconfiguration steps and specify the appropriate SSID in this field for eachsubsystem against which you want to run DB2 Query Monitor.

Command Selection ValuesEnter a valid sub-selection code to display one of the lower level screens.

Valid values are:1. Information specific to a particular DB2 subsystem, including ZPARM, BSDS,

and load library information.2. Information specific to DB2 Query Monitor.

Configure Subsystem InformationChoose option 1 in the Option field. This option is for ZPARM, BSDS, and loadlibrary information. The following panel is displayed:



19/70

----------------- Update Parameters for DB2 Subsystem -----------------Command ==>Enter or Update Specific DB2 Parameters :

DB2 ZPARMs Member ==>DB2 Bootstrap DSN #01 ==>DB2 Bootstrap DSN #02 ==>DB2 Loadlib1 ==>DB2 Loadlib2 ==>DB2 Loadlib3 ==>DB2 Loadlib4 ==>DB2 Loadlib5 ==>

DB2 ZPARMs member

Enter the eight-character ZPARM load module member name generated for thisDB2 subsystem.

BSDS #1 & BSDS #2

Enter the full dataset names of the two boot strap datasets being used by this DB2subsystem.

DB2 Loadlib 1 through 5

Enter the names of the datasets that comprise the current loadlib concatenation forDB2. This concatenation is usually a subsystem-specific DSNEXIT library, the baseDSNEXIT library for the current DB2 version, and the base DSNLOAD library forthe current DB2 version. If necessary, two extra library spaces are provided.

Configure DB2 Query Monitor-Specific InformationChoose option 2 in the Option field. This option is for DB2 Query Monitor-specificinformation. The following panel is displayed:

Chapter 3. Configuring DB2 Query Monitor 11


20/70

----- DB2 Query Monitor - Update Parameters for DB2 SubsystemCommand ==>

Enter or Update Specific DB2 Parameters :Plan #1 Name ==>

Plan NameEnter the eight-character plan name for DB2 Query Monitor. This is the same planname used in member CQM#BIND in the SCQMSAMP library when you bound theplan for DB2 Query Monitor in the preceding steps.

Note: You must reconfigure subsystem information for each DB2 that recordsDB2/QM interval data.



21/70

Chapter 4. Verifying Installation

You should verify the installation of DB2 Query Monitor on your system by startingthe product.

Verifying Installation1. Start a DB2/QM subsystem to monitor a given DB2 subsystem. For information

on monitoring DB2 subsystems, see the MONITOR parameter in Chapter 2, Tailoring Query Monitor Files.

2. Issue the following query against the monitored DB2 subsystem using a toolsuch as DB2s SPUFI:SELECT * FROM SYSIBM.SYSDUMMY1;

3. Enter the DB2/QM ISPF Dialog. Enter option 1 from the DB2/QM PrimaryOption menu. You should see the thread you created by entering the query inStep #2.



22/70



23/70

Chapter 5. Query Monitor Space Calculations

DB2 objects (such as DATABASE and TABLESPACE) are built in DB2 during QMinstallation to store data collected by QM. The DDL to build these objects requiressome calculations for space prior to the creation of the objects.

In particular, the partition tablespace sizes for THRDS11, BUFFPL11, DBRMS11,and STMTS11 (threads, bufferpools, DBRMS, and statements) must be determined,based on certain estimates provided by the installer at install time. Coincidental tothese calculations are the space calculations necessary for the partitioned indexspaces that accompany each partitioned tablespace.

Following is a discussion of the sizing issues related to each of these tablespacesand accompanying index spaces. As with all DB2 objects, the accuracy of theestimates determines the degree to which the QM objects are successfully spacemanaged. As with all DB2 objects, these sizes can be altered as new information ismade available for space management. These objects require the same DBAadministration required by all DB2 objects for optimal management.

The following discussion and guidelines are intended as an installation starting pointin the space management of the QM objects to be created in the installation of theproduct.

Partitions and Intervals in Query MonitorFor each of the partitioned tablespaces, the installation instructions andaccompanying DDL provide for 24 partitions per tablespace. This is in line with theQM recommendation of setting interval size to 60 minutes, and reusing partitionsdaily.

These partitions are used in a wrap around fashion. QM writes to a partition for

an interval set at install time. When the end of an interval is reached and a newinterval begins, QM initializes the next partition and writes the new interval to thatpartition. When all partitions are full, QM writes the next interval of data to the firstpartition (effectively reusing that partition). If additional partitions are desired toextend wrap around time, the tablespace can be initially built with more partitions,or can be altered to add partitions. See Adding Data Partitions below for moreinformation on running QM with additional partitions.

The size of each partition in the create DDL is determined based on an estimate ofactivity that occurs during one interval. If the interval is set to 60 minutes, then theestimate is for activity within a 60 minute timeframe. If the interval is set tosomething other than 60 minutes, then the estimate should be based on expectedactivity during the selected interval duration.

Sizing the THRDS11 Partitioned Table Space and PartitioningIndexspace

There is one table in the THRDS11 (threads) tablespace, namedCQM.THREADS_V11. A row is stored in the CQM.THREADS_V11 table for eachoccurrence of a thread during the interval. You should allow for 900 bytes of dataper row when calculating space for this tablespace. You should try to place all datain the PRIQTY, with a SECQTY equal to at least 20% of the PRIQTY.



24/70

The PRIQTY of the partitioning index CQM.THREADS_V11_IX should be at least15% of the PRIQTY for the tablespace. The SECQTY of the partitioning indexshould be at least 5% of the PRIQTY for the tablespace. The minimum calculationfor PRIQTY and SECQTY in the CREATE TABLESPACE and CREATE INDEX DDLis: Let n equal the number of estimated threads per interval.Let ROUND be the process of rounding up to the nearest integer.

Create Tablespace ThreadsPRIQTY = ROUND((1000n)/1024) + 72SECQTY= ROUND((.2)(PRIQTY))

Create Index CQM.THREADS_V11_IXPRIQTY = ROUND((tablespace PRIQTY)(.15)) SECQTY= ROUND((tablespacePRIQTY)(.05))

Example: If the number of estimated threads per minute is 180, and the interval isset to 60 minutes, then the calculation for the THRDS11 tablespace is:

n = (180)(60) = 10800(1000)(10800) = 10800000ROUND(10800000/1024) = 1054710547+ 72 = 10619Tablespace PRIQTY 10619Tablespace SECQTY 2124Indexspace PRIQTY 1593Indexspace SECQTY 531

Sizing the BUFFPL11 Partitioned Table SpaceThere is one table in the BUFFPL11 (bufferpool) tablespace, namedCQM.BUFFERPOOLS_V11. A row is stored in the CQM.BUFFERPOOLS_V11 table

for each unique plan accessing a distinct bufferpool during that interval. If a planaccesses two bufferpools and is executed one or more times during the interval,there are two rows inserted into this table. If another plan accesses the same twobufferpools, accesses a third bufferpool, and is executed one or more times duringthe interval, there are an additional three rows inserted into the table. Data is rolledup by plan and bufferpool. You should allow for 120 bytes of data per row whencalculating space for this tablespace. You should try to place all data in thePRIQTY, with a SECQTY equal to at least 20% of the PRIQTY. The PRIQTY of thepartitioning index CQM.BUFFERPOOLS_V11_IX should be at least 20% of thePRIQTY for the tablespace. The SECQTY of the partitioning index should be atleast 10% of the PRIQTY for the tablespace. The minimum calculation for PRIQTYand SECQTY in the CREATE TABLESPACE and CREATE INDEX DDL is: Let nequal the number of estimated plan/bufferpool combinations per interval.

Let ROUND be the process of rounding up to the nearest integer.

Create Tablespace BUFFPL11PRIQTY = ROUND((120n)/1024) + 72SECQTY= ROUND((.2)(PRIQTY))

Create Index CQM.BUFFERPOOLS_V11_IXPRIQTY = ROUND((tablespace PRIQTY)(.2))SECQTY= ROUND((tablespace PRIQTY)(.1)) Example: If the number of estimatedplans to be executed in an interval is 90, each plan accesses two bufferpools, and



25/70

the interval is set to 60 minutes, then the calculation is: n = (90)(2)(60) = 10800(120)(10800) = 1296000ROUND(1296000/1024) = 12661266 + 72 = 1338Tablespace PRIQTY 1338Tablespace SECQTY 268Indexspace PRIQTY 268

Indexspace SECQTY 134

Sizing the DBRMS11 Partitioned Table SpaceThere is one table in the DBRMS11 tablespace, named CQM.DBRMS_V11. A row isstored in the CQM.DBRMS_V11 table for each combination of a unique DBRM andSQL statement executed during that interval. Data is rolled up by DBRM and SQLstatement. You should allow for 600 bytes of data per row when calculating spacefor this tablespace. You should try to place all data in the PRIQTY, with a SECQTYequal to at least 20% of the PRIQTY. The PRIQTY of the partitioning indexCQM.DBRMS_V11_IX should be at least 15% of the PRIQTY for the tablespace.The SECQTY of the partitioning index should be at least 5% of the PRIQTY for thetablespace. The minimum calculation for PRIQTY and SECQTY in the CREATETABLESPACE and CREATE INDEX DDL is: Let n equal the number of estimatedDBRM/SQL statement combinations per interval.Let ROUND be the process of rounding up to the nearest integer.

Create Tablespace DBRMS11PRIQTY = ROUND((600n)/1024) + 72SECQTY= ROUND((.2)(PRIQTY))

Create Index CQM.DBRMS_V11_IXPRIQTY = ROUND((tablespace PRIQTY)(.15))SECQTY= ROUND((tablespace PRIQTY)(.05)) Example: If the number of estimated

DBRMS to be executed in an interval is 50, and 20 executes three SQLSTATEMENTS each while the other 30 executes four SQL STATEMENTS each,and the interval is set to 60 minutes, then the calculation is: n = ((20)(3) +(30)(4))(60) = 10800(600)(10800) = 6480000ROUND(6480000/1024) = 63296329 + 72 = 6401Tablespace PRIQTY 6401Tablespace SECQTY 1281Indexspace PRIQTY 961Indexspace SECQTY 321

Sizing the STMTS11 Partitioned Table SpaceThere is one table in the STMTS11 (statements) tablespace, namedCQM.STATEMENTS_V11. A row is stored in the CQM.STATEMENTS_V11 table foreach combination of a unique DBRM and SQL statement executed during thatinterval. Data is rolled up by DBRM and SQL statement. You should allow for 125bytes of data per row when calculating space for this tablespace. You should try toplace all data in the PRIQTY, with a SECQTY equal to at least 20% of the PRIQTY.The PRIQTY of the partitioning index CQM.STATEMENTS_V11_IX should be atleast 20% of the PRIQTY for the tablespace. The SECQTY of the partitioning indexshould be at least 10% of the PRIQTY for the tablespace. The minimum calculationfor PRIQTY and SECQTY in the CREATE TABLESPACE and CREATE INDEX DDL

Chapter 5. Query Monitor Space Calculations 17


26/70

is: Let n equal the number of estimated DBRM/SQL statement combinations perinterval.Let ROUND be the process of rounding up to the nearest integer.

Create Tablespace STMTS11PRIQTY = ROUND((125n)/1024) + 72SECQTY= ROUND((.2)(PRIQTY))

Create Index CQM.STATEMENTS_V11_IXPRIQTY = ROUND((tablespace PRIQTY)(.2))SECQTY= ROUND((tablespace PRIQTY)(.1)) Example: If the number of estimatedDBRMS to be executed in an interval is 50, and 20 executes three SQLSTATEMENTS each while the other 30 executes four SQL STATEMENTS each,and the interval is set to 60 minutes, then the calculation is: n = ((20)(3) +(30)(4))(60) = 10800(125)(10800) = 1350000ROUND(1350000/1024) = 13191319 + 72 = 1391Tablespace PRIQTY 1391Tablespace SECQTY 279Indexspace PRIQTY 279Indexspace SECQTY 140

Adding Data PartitionsAlthough this documentation and accompanying installation DDL build the QMpartition tablespaces with 24 partitions, you can add additional partitions to the QMpartitioned tablespaces. The only limitation, other than DB2 limitations on partitionedtablespaces, is that all QM partitioned tablespaces must contain the same numberof partitions. The tablespaces THRDS11, DBRMS11, BUFFPL11, and STMTS11must all have the same number of partitions.

To install the QM objects with more (or less) than the 24 partitions, you mustchange the DDL that creates the tablespaces and partitioning indexes. The DDL isfound in the dataset SCQMSAMP, with a member name of CQM#DDL. To addpartitions 25, 26, 27, 28, 29, and 30 to the THRDS11 tablespace, make thefollowing changes to the CREATE TABLESPACE THREADS... DDL:

CREATE TABLESPACE THREADS IN CQMDB . . . PART 24 COMPRESS YES,PART 25 COMPRESS YES, PART 26 COMPRESS YES, PART 27 COMPRESSYES, PART 28 COMPRESS YES, PART 29 COMPRESS YES, PART 30COMPRESS YES) LOCKSIZE PAGE BUFFERPOOL BP4 CLOSE NO CCSIDEBCDIC; Remember that if you change the number of partitions in one of thepartitioned tablespaces, you must make the same change to use the same number

of partitions in all, including THRDS11, DBRMS11, BUFFPL11, and STMTS11. Ifyou change the number of partitions in a tablespace, you must also alter the DDLthat creates the partitioning index. For the above example in which the THRDS11tablespace was given six additional partitions (25, 26, 27, 28, 29, and 30), theCREATE TYPE 2 INDEX CQM.THREADS_V11_IX DDL needs to be altered asfollows:

CREATE TYPE2 INDEX CQM.THREADS_V11_IX ON CQM.THREADS_V11 . . .(PART 01 VALUES(01,2147483647) ,PART 02 VALUES(02,2147483647) ,PART 03VALUES(03,2147483647) ,PART 04 VALUES(04,2147483647) ,PART 05VALUES(05,2147483647) ,PART 06 VALUES(06,2147483647) ,PART 07



27/70

VALUES(07,2147483647) ,PART 08 VALUES(08,2147483647) ,PART 09VALUES(09,2147483647) ,PART 10 VALUES(10,2147483647) ,PART 11VALUES(11,2147483647) ,PART 12 VALUES(12,2147483647) ,PART 13VALUES(13,2147483647) ,PART 14 VALUES(14,2147483647) ,PART 15VALUES(15,2147483647) ,PART 16 VALUES(16,2147483647) ,PART 17VALUES(17,2147483647) ,PART 18 VALUES(18,2147483647) ,PART 19VALUES(19,2147483647) ,PART 20 VALUES(20,2147483647) ,PART 21

VALUES(21,2147483647) ,PART 22 VALUES(22,2147483647) ,PART 23VALUES(23,2147483647) ,PART 24 VALUES(24,2147483647) ,PART 25VALUES(25,2147483647) ,PART 26 VALUES(26,2147483647) ,PART 27VALUES(27,2147483647) ,PART 28 VALUES(28,2147483647) ,PART 29VALUES(29,2147483647) ,PART 30 VALUES(30,2147483647)) BUFFERPOOL BP4CLOSE NO;

Chapter 5. Query Monitor Space Calculations 19


28/70



29/70

Chapter 6. Getting Started

IBM DB2 Query Monitor for OS/390 allows you to monitor query, thread, bufferpool,and other DB2 resources.

OverviewIBM DB2 Query Monitor allows system administrators and/or DBAs to monitor DB2resource consumption and pinpoint inefficient or improperly coded SQL statements.IBM DB2 Query Monitor performs this task with minimal system overhead, andwithout running expensive DB2 traces.

IBM DB2 Query Monitor allows the user to view statistics about current andhistorical SQL activity. It also allows dynamic monitoring of DB2 subsystems. Usersmay define profiles that filter performance data at the monitoring- and displayinterface levels. Additionally, exception conditions can be set up to alert users whenspecific SQL related thresholds exceed defined limits.

Functions and ConceptsThis section describes functionality and concepts that are unique to IBM DB2 QueryMonitor.

DB2 QM SubsystemsA DB2 QM Subsystem records SQL performance statistics related to one or moreDB2 Subsystem. A DB2 QM Subsystem may run as a started task or job.

Each DB2 QM Subsystem can monitor and record SQL performance data for up to64 DB2 Subsystems; however, a given DB2 Subsystem cannot be monitored bymore than one DB2 QM Subsystem. Interval data for all DB2 Subsystems definedin a DB2 QM Subsystem is stored in one DB2.

TSO/ISPF FacilityThe TSO/ISPF facility of DB2 Query Monitor allows the end user to display DB2SQL performance data. This feature allows the end user to determine what impactcertain SQL processing has on DB2 resources. End users of the ISPF facility canview SQL performance data at the plan level and at the DBRM/Package statementlevel.

IntervalsIntervals are segments of time defined by the administrator, into which data isdivided once captured. When you view past SQL activity you are viewing data for adiscrete period in time.

Current interval data resides in memory; whereas, prior interval data resides in

partitioned table spaces.

Intervals are defined by the INTERVAL startup parameter. For further information onsetting Intervals refer to Chapter 2, Tailoring Query Monitor Files.

Navigation Commands and ActionsDB2 Query Monitor is a TSO/ISPF application that responds to standard TSO/ISPFcommands. This section describes additional IBM DB2 Query Monitor features thathave been developed to help you use and navigate through the application.



30/70


31/70

Monitoring ProfileThe Monitoring Profile defines what activity each monitoring agent will capture, suchas activity involving connections, users, plans, or DBRMs of a DB2 subsystem.

Agents Monitoring Agent refers to the interface that DB2 QM installs within a DB2subsystem to capture SQL performance data.

Application ProfileThe Application Profile defines what data will be displayed out of the data collected.

Each user can have his or her own profile.

Exception ProfileThe Exception Profile specifies acceptable limits of processing.

ExceptionsAn exception is a condition that occurs when a defined threshold has beenexceeded.

The Exception Profile specifies what threads are within acceptable limits. When athread is outside an acceptable limit, an exception is generated and displayed inred on the screen.

ThresholdsA threshold is a defined limit on SQL processing initiates an exception conditionwhen it has been exceeded.

Thresholds can be set in the Exception Profile panel.

Thresholds can be set up for:v Total SQL callsv Total Getpagesv Lock requestsv CPU timev Elapsed timev Application CPU timev Application elapsed time

Chapter 6. Getting Started 23


32/70

Starting IBM DB2 Query Monitor

Selection MenuThis is the Main Menu of IBM DB2 Query Monitor:

CQM$MAIN V1R1 ---------- IBM DB2 Query Monitor -----------------Option ===> __________________________________________________________________

DB2 QM Subsystem ID: User:

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

1. View Current Activity

2. View Past Activity

3. Work with Monitoring Agents

4. View DB2 Command Activity

5. Work with Profiles

S. Setup

X. Exit Query Monitor

Enter END command to return to ISPF.

1. View Current ActivityView Current Activity allows you to see performance data for the current interval.

Type 1 to display the View Current Activity panel.

2. View Past ActivityView Past Activity allows you to view performance data for previous intervals.

Type 2 display the View Past Activity panel.

3. Work with Monitoring AgentsWork with Monitoring Agents allows you to turn the monitoring agents on and off forspecific DB2 subsystems.

Type 3 to display the Work with Monitoring Agents panel.

4. View DB2 Command ActivityView DB2 Command Activity allows you to view DB2 commands that have beenexecuted.

Type 4 display the DB2 Commands Executed panel.



33/70

5. Work with ProfilesWork with Profiles allows you to determine what data gets collected, what data isdisplayed, and what data generates exceptions.

Type 5 to display the Work with Profiles panel.

S. Setup Use the Setup command to tailor DB2 parameters in the control file, which allowsDB2/QM interval processes to connect to DB2. See Chapter 12, Setup, for moreinformation.

Type S to display the Enter DB2 System Parameters panel.

Chapter 6. Getting Started 25


34/70



35/70

Chapter 7. Viewing Current Activity

With IBM DB2 Query Monitor, you can view current activity.

1. View Current ActivitySelect option 1, View Current Activity from the Selection panel to display the ThreadActivity panel:

CQM$DTHR V1R1 ------- DB2 QM Thread Activity ------Option ===> ________________________________________________ Scroll ===> PAGE------------------------------------------------------------------------- +>DB2 QM Subsystem: Current Interval Started:

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

Display Threads: I (Active/Interval) D (Detail/Summarize)

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

Cmd SSID Intv Plan Name Job Name DB2 CPU Time DB2 Elapsed SQL Calls

Valid Line Commands: (Sql detail, Instruction totals, Buffers, Delays, Locks)

FunctionThe Thread Activity panel shows SQL thread activity in the current interval.

Display Threads

Active/Interval: This setting allows the user to display threads that are currentlyactive in DB2 or threads that have been active sometime within the current interval.

Detail/Summarize: This setting allows the user to display the data about threadactivity on a detail level or to summarize by plan name.

Features

DataThe following columns are part of the Thread Activity panel:

1. SSID (DB2 Subsystem ID)2. Intv (Interval Indicator)3. Plan Name4. Job Name5. DB2 CPU Time



36/70

6. DB2 Elapsed7. SQL Calls8. X Exec9. Connectn (DB2 Connection Name)

10. APPL Elapsed11. APPL CPU12. Total Getpages13. Plan Name14. Token15. Accounting Token16. Requesting Site (IP address of client for distributed thread)17. NETID (Network ID)18. LUNAME19. AUTHID (DB2 Auth)20. Plan Start Time21. Plan End Time

Valid Commands Entered in the Option Field

INTV: This command displays the intervals panel, and works as a shortcut toOption 2 from the main menu.

PROF: This command displays the Application Profiles panel, and works as ashortcut to Option 5.2.

Panels that support line commands have explanatory text listing the validcommands. Type the first letter of the command, which is capitalized in theexplanation, to view this information.

Note: The commands available for the panel will be overlaid if you display the PFkeys.

Valid Line CommandsThe following line commands are valid on the Thread Activity panel.

If you enter invalid information for an option field (primary command), an errormessage is issued indicating that an invalid command has been entered and(typically), the extended error messages for the command will list the valid valuesfor the field.

SQL Detail: Type S to display the DB2 Query Monitor Plan Detail panel, whichshows activity for DBRMs and/or packages that execute under a plan.

Instruction Totals: Type I to display the Instruction counts panel, which showscounts by instruction type that execute under a given plan.

Buffers: Type B to display the Plan Bufferpool Statistics panel, which showsbufferpool statistics.

Delays: Type D to go to the Thread Delays panel, which shows statistics onevents that cause delays in the execution of plans or packages.



37/70

Locks: Type L to go to the Thread Locking Events panel, which shows lockstatistics.

SQL Detail: Type S to display the DB2 Query Monitor Detail panel. This paneldisplays activity for DBRMs and/or packages that execute under a plan.

This is the DB2 Query Monitor Plan Detail panel:

CQM$DPLN V1R1 -------- Query Monitor Plan Detail --------Option ===> ________________________________________________ Scroll ===> PAGE

Jobname: Plan: DB2 SSID: Plan Execution Count:

Totals or Averages: (Total of all executions/Average of each execution)-------------------------------------------------------------------------------

Cmd DBRM/PKG Collection ID DB2 CPU Time DB2 Elapsed SQL Calls

***************************** Bottom of Data **********************************

Valid Line Commands: (Sql detail, Buffers, Delays, Locks)

The following line commands are valid on the DB2 Query Monitor Detail panel:

Instruction totals:: Type Iin the line command field of the Thread Activity panel todisplay the SQL Instruction Counts panel. This panel displays counts by instructiontype that executes under a plan.

Chapter 7. Viewing Current Activity 29


38/70

This is the Instruction Counts panel:

CQM$STHR V1R1 ---------- SQL Instruction Counts ---------Option ===> ________________________________________________ Scroll ===> PAGE


Totals or Averages: (Total of all executions/Average of each execution)

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

Instruction Totals Instruction Totals Instruction Totals----------- ------ ----------- ------ ----------- ------

Valid Commands: (End)

The following line commands are valid on the SQL Instruction Counts panel:

Buffers: Type B in the line command field of the Thread Activity panel to displaythe Plan Bufferpool Statistics panel. This panel will display bufferpool statistics..

This is the Plan Bufferpool Statistics panel:

CQM$BTHR V1R1 ------- Plan Bufferpool Statistics -------Option ===> ________________________________________________ Scroll ===> PAGE

Jobname: Plan: DB2 SSID: Plan Execution Count:Totals or Averages: (Total of all executions/Average of each execution)

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

Bufferpool:Get Page RequestsBuffer Pages UpdatedSynchronous Pages ReadSynchronous Pages WrittenSequential Prefetch RequestsList Prefetch RequestsDynamic Prefetch RequestsSuccessful Hiperpool ReadsHiperpool Read FailuresSuccessful Hiperpool WritesUnsuccessful Hiperpool WritesAsync Pages ReadAsync Pages Read by Hiperpool

Valid Commands: (End)

The following line commands are valid on the Plan Bufferpool Statistics panel:



39/70

Delays: Type D to display the Thread Delays panel. This panel shows statistics onevents that cause delays in the execution of plans or packages.

This is the Thread Delays panel:

CQM$ETHR V1R1 -------------- Thread Delays -------------Option ===> ________________________________________________ Scroll ===> PAGE


Totals or Averages: (Total of all executions/Average of each execution)------------------------------------------------------------------------ +

Delay Event Event Count Delay TimeLock or Latch DelaysSynchronous I/O DelaysOther Read DelaysOther Write DelaysService Task Switch DelaysArchive Log Quiesce DelaysArchive Log Read DelaysDrain Lock DelaysClaim Release DelaysPage Latch DelaysStored Procedure DelaysNotify Message DelaysGlobal Contention DelaysValid Commands: (End)

The following line commands are valid on the Thread Delays panel:

Locks: Type L to display the Thread Locking Events panel. This panel shows lockstatistics.

This is the Thread Locking Events panel:

CQM$LTHR V1R1 ---------- Thread Locking Events ---------Option ===> ________________________________________________ Scroll ===> PAGE


Totals or Averages: (Total of all executions/Average of each execution)------------------------------------------------------------------------ +

Lock Event Event CountLock DeadlocksLock SuspensionsLock TimeoutsLatch SuspensionsOther SuspensionsLock RequestsUnlock RequestsQuery RequestsChange RequestsOther RequestsClaim RequestsClaim FailuresDrain RequestsValid Commands: (End)

Chapter 7. Viewing Current Activity 31


40/70



41/70

Chapter 8. Viewing Historical Activity

With IBM DB2 Query Monitor, you can view historical activity.

2. View Past ActivitySelect option 2, View Past Activity from the Selection panel to display the Intervalpanel:

CQM$INTV V1R1 --- DB2 QM Intervals ---Option ===> _____________________________ Scroll ===> PAGE

Valid Cmds: Select,Unload Data,Load history

-------------------------------------------------------------Cmd Avail Start Date Start Time End Date End Time Prtn

FunctionThe Interval panel allows you to view performance data for previous intervals. Thefirst panel you see is a list of intervals through which you can scroll. You can usethe three valid line commands, Select , Unload Data , and Load history to workwith specific intervals.

Features

DataThe following columns are part of the Interval panel:v Availv

Start Datev Start Timev End Datev End Timev Prtn (Partition)v Offloaded Dataset

Valid Line CommandsThe following Line Commands are valid on the Interval panel:

Line Command Description

SELECT Type S to go to the Interval Thread Activity panel, whichcontains the data for the interval line item you selected.

UNLOAD DATA Type U to unload data.

LOAD HISTORY Type L to load history.

Interval Thread ActivityThe Interval Thread Activity panel is similar to the Thread Activity panel, althoughthis panel shows data for prior intervals. Three additional commands are availableon this panel:



42/70

Command Description

NEXT This command displays the next interval. PF6 also performs this command.

PREV This command displays the previous interval. PF4 also performs thiscommand.

CURRENT Issued from an Interval Thread Activity panel, this command displays thecurrent Thread Activity panel.



43/70

Chapter 9. Monitoring Subsystems

With IBM DB2 Query Monitor, you can use agents to monitor DB2 subsystems.

3. Work with Monitoring AgentsSelect option 3, Work with Monitoring Agents , from the Selection panel to displaythe DB2 QM Monitoring panel:

CQM$DDB2 V1R1 ------- DB2 QM Monitoring ------Option ===> ________________________________ Scroll ===> PAGE

Valid Cmds: Activate, Deactivate---------------------------------------------------------------

Cmd Subsystem Active Monitored DB2 QM SSID Profile

FunctionThis panel allows you to turn monitoring agents on and off for specific DB2subsystems.

Features

DataData columns in this panel include:v

Subsystemv Activev Monitoredv DB2 QM SSID

Valid Line CommandsThe following line commands are valid for the Monitoring panel:

Activate: Type Ato activate monitoring for the current DB2 subsystem line item.

Deactivate: Type D to deactivate monitoring for the current DB2 subsystem lineitem.



44/70



45/70

Chapter 10. Viewing DB2/QM Command Activity

With IBM DB2 Query Monitor, you can view DB2 command activity.

4. View DB2 Command ActivitySelect option 4, View DB2 Command Activity, from the Selection panel to displaythe DB2 Commands Executed panel:

CQM$CDMD V1R1 ------- DB2 Commands Executed -------Option ===> _______________________________________________ Scroll ===> PAGE------------------------------------------------------------------------- >DB2 QM Subsystem: Current Interval Started:

-------------------------------------------------------------------------------Job Name Authid Timestamp Command Text

FunctionThe View DB2 Commands Executed panel allows you to view command activity.

Features

DataData columns in this panel include:v Job Namev Authidv Timestampv Command Text



46/70



47/70

Chapter 11. Defining Selection Criteria

With IBM DB2 Query Monitor, you tailor profiles to control what data is monitoredand displayed. You can also define thresholds via exception profiles that highlightSQL activity that is outside defined parameters.

5. Work with ProfilesSelect option 5, Work with Profiles , from the Selection menu to display the Profilepanel:

Select which type of profile you would like to view:

_ 1) Monitoring Profile - Determines what threads are

2) Application Profile - Determines what threads will

3) Exception Profile - Define thread thresholds for

Press Enter/PF3 to continue

FunctionUse the panels in the Profile option to set the criteria for what data is collected,what data is displayed, and what data generates exceptions.

FeaturesThe Profile panel is a menu that provides access to three types of profiles:v Monitoringv Applicationv Exception

Monitoring ProfilesThe Monitoring Profile acts as a filter to determine what activity each monitoringagent will capture.



48/70

This is the Monitoring Profiles panel:

CQM$PRFM V1R1 -------- Monitoring Profiles --------Option ==>___________________________________________________Scroll ==> PAGE-------------------------------------------------------------------------Cmd Profile Description Last User Upd Timestmp

***************************** Bottom of Data **********************************

Valid Line Commands: (Create, Update, Delete)

Function: The Monitoring Profiles panel allows you to create new monitoringprofiles, and to make changes to existing ones.

Features: Profile data is displayed and can be accessed through line commands.

Data: Data columns on this panel include:v Profilev Descriptionv Last Userv Upd Timestamp

Valid Line Commands: The following line commands are valid on the MonitoringProfiles panel:

Line Command Description

CREATE Type C to create a new profile. The Create Profile panel isdisplayed, followed by the Update panel where you finishcreating the new profile.

UPDATE Type U to update a profile.

DELETE Type D to delete a profile.

Create Profile: Type C to create a profile. Type the profile name and descriptionthen press Enter. A second window appears where you may select the type ofprofile to create (AUTHID, CONNECTN, JOB, PLAN, or SSID). Type C next to thedesired profile type, then press Enter to display the Update Detail window whereyou may complete the new profile.



49/70

CQM$PRFB V1R1 ---- Create Profile ----Option ===> _____________________________________________________

Profile Name __________Description _______________________________________

Press Enter/PF3 to create or Can to cancel

Update Profile: Type U to update a profile. At the Update Detail window, you maychange the specifics of the profile. A message is issued after you update the profileto indicate that it was successfully updated.

CQM$PRFT V1R1 --- Update ---Option ===> __________________________________ Scroll ===> PAGE

Description ________________________________________

Valid Cmds: Create,Update,Delete

-------------------------------------------------------------Cmd Type Inc/Exc Fltr Data QM Pln SQLOrd Interv Host V

***************************** Bottom of Data ****************

Delete: Type D to delete a profile. A message displays that prompts you to confirmyour decision, followed by a second message confirming the deletion was made.

Application ProfilesThe Application Profile serves as a filter to determine what data will be displayed onISPF, from the data that was collected. This is the default selection from the Workwith Profiles panel.

Chapter 11. Defining Selection Criteria 41


50/70


51/70


52/70

This is the Exception Profiles panel:

CQM$EXCP V1R1 ---------- Exception Profiles ----------Option ===> ________________________________________________ Scroll ===> PAGE-------------------------------------------------------------------------

Cmd Profile Description Last User Upd Timestmp

***************************** Bottom of Data **********************************

Valid Line Commands: (Create, Update, Delete)

Function: The Exception Profiles panel is where you manage exception profiles.

The Exception Profiles panel displays a list of current profiles to which you canmake changes.

Features: You can create, update and delete exception profiles from this panel.

Data: Data columns in this panel include:v Profilev Descriptionv Last Userv Updv Timestamp

Valid Line Commands: The following line commands are valid for the ExceptionProfile panel:



53/70

Create: Type C to create a new profile. The Create Profile window is displayed:

CQM$EXCC V1R1 ---- Create Profile ----Option ===> ______________________________________________

Profile Name ______________

Description _______________________________________

Total SQL Calls ____________Total Getpages ____________Lock Request ____________Lock Escalations ____________CPU Time __ : __ : __Elapsed Time __ : __ : __Application CPU Time __ : __ : __Application Elapsed Time __ : __ : __

Press Enter/PF3 to create or CAN to cancel

The Create Profile window is used to create a new exception profile.

Update: Type U to update an exception profile. The Update window is displayed:

CQM$EXCU V1R1 --- Update ---Option ===> ___________________________________________

Profile Name

Description

Total SQL CallsTotal GetpagesLock RequestLock Escalations

CPU Time __ : __ : __Elapsed Time __ : __ : __Application CPU Time __ : __ : __Application Elapsed Time __ : __ : __

Press Enter/PF3 to create or CAN to cancel

The Update panel is used to make changes to existing exception profiles.

Delete: Type D to delete an exception profile. A dialog box opens to confirm yourchoice, followed by a second dialog box confirming your decision.

Chapter 11. Defining Selection Criteria 45


54/70



55/70

Chapter 12. Setup

Use this option to identify the DB2 subsystem in which you want to work and theplan name to which you are binding. This is the S option at the IBM DB2 QueryMonitor Main Menu.

A sample panel is shown below.

--------------------------Enter DB2 System Parameters--------------------------Command ==>

DB2 Tools Load Library ==>GDG Base Model DSN ==>DB2 Control Dataset ==>(Pre-allocated)

Enter DB2 Subsystem Info:

DB2 Subsystem ID ==> (1-4 Character Subsystem ID)

Parameter List Selection ==> (Screen # 1-n)

Valid Parameter list selection values are:1: ZPARM, BSDS, and Load Library Information2: DB2 Query Monitor Parameters

Use Option #2 from the menu above to work with Query Monitor parameters. TheUpdate Parameters for DB2 Subsystem panel opens. At this panel you may specifythe plan name to display objects. A sample panel is shown below.



56/70

------DB2 Query Monitor - Update Parameters for DB2 SubsystemCommand ==>

Enter or Update Specific DB2 Parameters :

Plan #1 Name ==>



57/70

Chapter 13. Common Tasks

The following summarizes how to execute common IBM DB2 Query Monitor tasks:

Task Instructions

Display Thread Activity From the main panel, type 1 to select View Current Activity . The ThreadActivity panel is displayed.

Display Plan Activity From the Thread Detail or the Interval Thread Detail panel, type S on theCMD line. The Plan Detail panel is displayed.

Display DBRM Package Activity From the Plan Detail panel, type S on the CMD line. The DBRM Detailpanel is displayed.

Display SQL Instruction Text From the DBRM Detail panel, type S on the CMD line. The SQL InstructionText panel is displayed.

Display Bufferpool Statistics From the main panel, type 1 to select View Current Activity , then type B forBuffer. The Thread Bufferpool Statistics panel is displayed.

Display SQL Instruction Totals From the main panel, type 1 to select View Current Activity , then type I forInstruction counts. The SQL Instruction Counts panel displayed.

Display Lock Event Totals From the main panel, type 1 to select View Current Activity , then type L forLocks. The Thread Locking Events panel is displayed.

Display Accounting Class III Data From the Thread Activity or the Interval Thread Activity panel, type D. TheThread Delays panel is displayed.



58/70



59/70

Chapter 14. DB2/QM Memory Usage Statistics

DB2/QM records data about SQL activity for the current interval in a set ofdataspaces. Each dataspace contains a specific control block type. During an activeinterval, DB2/QM fetches control blocks from the dataspace control block pools asrequired. At the end of the interval processing DB2/QM returns the control segmentto the dataspace pools. DB2/QM subdivides these dataspaces into one megabytesegments. Each segment contains a number of control blocks. This number variesdepending on the size of the control blocks.

Displaying ActivityTo display activity within the DB2/QM dataspace pools, enter the DISPLAYDATASPACES command.

Refer to Chapter 15, DB2 Query Monitor Operator Commands, for moreinformation about the DISPLAY DATASPACES command.

SyntaxF db2qmtask,DISPLAY DATASPACES

OutputCQM3240I DB2 QM DATASPACE UDAGE DISPLAY:CQM3241I PLAN DATASPACE:CQM3242I NODE SIZE 5,968CQM3243I TOTAL NODES 358,225CQM3244I AVAILABLE NODES 358,224CQM3245I PERCENT UTILIZED 0.00%CQM3241I DBRM DATASPACECQM3242I NODE SIZE 580CQM3243I TOTAL NODES 3,698,929CQM3244I AVAILABLE NODES 3,698,911CQM3245I PERCENT UTILIZED 0.00%CQM3241I SQL DATASPACE:CQM3242I NODE SIZE 96CQM3243I TOTAL NODES 22,335,490CQM3244I AVAILABLE NODES 22,335,373CQM3245I PERCENT UTILIZED 0.00%CQM3241I HOSTV DATASPACE:CQM3242I NODE SIZE 96CQM3243I TOTAL NODES 22,335,490CQM3244I AVAILABLE NODES 22,335,490

CQM3245I PERCENT UTILIZED 0.00%

To determine space usage in a particular pool, subtract the available nodes fromthe total nodes, and then multiply by the node size. This will determine the amountof storage in use for control blocks in the given pool.

For example, in the above output the amount of space used by the SQL dataspacewould be 11,232 bytes. 1

(22,335,490 - 22,335,373) * 96 = 11,232



60/70

____________________________________

1 The actual space used may be anywhere from 11,232 bytes to one megabytebecause DB2/QM frees storage on a segment boundary.



61/70

Chapter 15. DB2 Query Monitor Operator Commands

Via the MVS MODIFY command, an operator may communicate directly with theDB2/QM task to display or control its operation. For more information on thiscommand, see the OS/390 System Commands Manual.

Valid CommandsThe valid DB2/QM operator commands are listed below.

DISPLAY DATASPACESThe DISPLAY DATASPACES command displays statistics related to DB2/QMsdataspace usage. For more information on this command, see Chapter 14, DB2/QM Memory Usage Statistics.

INTERVALUse the INTERVAL command to dynamically invoke DB2/QMs interval processor.

During normal operation, DB2/QM creates interval data when a recording intervalexpires or during DB2/QM shutdown.



62/70



63/70

Appendix. Notices

This information was developed for products and services offered in the U.S.A. IBMmay not offer the products, services, or features discussed in this document in othercountries. Consult your local IBM representative for information on the products andservices currently available in your area. Any reference to an IBM product, program,or service is not intended to state or imply that only that IBM product, program, orservice may be used. Any functionally equivalent product, program, or service thatdoes not infringe any IBM intellectual property right may be used instead. However,it is the users responsibility to evaluate and verify the operation of any non-IBMproduct, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give you anylicense to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive

Armonk, NY 10594-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSOR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIESOF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR APARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not apply toyou.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvements and/orchanges in the product(s) and/or the program(s) described in this publication at anytime without notice.

Any references in this publication to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of thoseWeb sites. The materials at those Web sites are not part of the materials for thisIBM product and use of those Web sites is as your own risk.

Licensees of this program who wish to have information about it for the purpose ofenabling: (i) the exchange of information between independently created programsand other programs (including this one) and (ii) the mutual use of the informationwhich has been exchanged, should contact:



64/70

IBM CorporationJ74/G4555 Bailey AvenueP.O. Box 49023San Jose, CA 95161-9023U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this information and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have been

estimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of thoseproducts, their published announcements or other publicly available sources. IBMhas not tested those products and cannot confirm the accuracy of performance,compatibility or any other claims related to non-IBM products. Questions on thecapabilities of non-IBM products should be addressed to the suppliers of thoseproducts.

All statements regarding IBMs future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBMs suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrates programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment to IBM,for the purposes of developing, using, marketing or distributing application programsconforming to the application programming interface for the operating platform forwhich the sample programs are written. These examples have not been thoroughlytested under all conditions. IBM, therefore, cannot guarantee or imply reliability,serviceability, or function of these programs.



65/70

If you are viewing this information softcopy, the photographs and color illustrationsmay not appear.

TrademarksThe following terms are trademarks of the IBM Corporation in the United States orother countries or both:

Advanced Peer-to-PeerNetworking

AIXAIX/6000CICSCICS/MVSCICS/VSEDATABASE 2DB2Distributed Relational

Database ArchitectureDRDADXT

GDDMIBMMVS/ESAMVS/XAOfficeVision/VMOS/2PL/IPROFSQMFSQL/DSVirtual Machine/Enterprise

Systems ArchitectureVM/XA

VSE/ESA

Other company, product, and service names, which may be denoted by a doubleasterisk (**), may be trademarks or service marks of others.

Appendix. Notices 57


66/70



67/70

Readers Comments Wed Like to Hear from You

DB2 Query Monitor for OS/390Users GuideVersion 1 Release 1

Publication No. SC27-0968-00

Overall, how satisfied are you with the information in this book?

Very Satisfied Satisfied Neutral Dissatisfied Very DissatisfiedOverall satisfaction h h h h h

How satisfied are you that the information in this book is:

Very Satisfied Satisfied Neutral Dissatisfied Very DissatisfiedAccurate h h h h hComplete h h h h hEasy to find h h h h hEasy to understand h h h h hWell organized h h h h hApplicable to your tasks h h h h h

Please tell us how we can improve this book:

Thank you for your responses. May we contact you? h Yes h No

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in anyway it believes appropriate without incurring any obligation to you.

Name Address

Company or Organization

Phone No.


68/70


69/70


70/70

File Number:Program Number: 5675E67

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

Documents

DB2 Query Monitor User's Guide.pdf