V 5.1.0: Update to the Monitoring Performance from the OMEGAMON Classic Interface manual of IBM Tivoli OMEGAMON XE for DB2 Performance Expert on z/OS and IBM Tivoli OMEGAMON XE for DB2 Performance Monitor on z/OS

Manual


Abstract

This document updates the IBM ® Tivoli® OMEGAMON for DB2® Performance Expert on z/OS and IBM Tivoli OMEGAMON XE for DB2 Performance Monitor on z/OS, Version 5.1.0: Monitoring Performance from the OMEGAMON Classic Interface manual, SH12-6924-01.

Content

  • Update 1 - (May 2011):
    • Field description updates in Chapter 5, Chapter 6, and Chapter 15, in PM29092 fix
    • New panel and field description in Chapter 8. Application Trace Facility (ATF), "Specify Application Trace"
  • Update 2 - (June 2011) - Panel and field description updates in Chapter 7 in PM02978 fix
  • Update 3 - (June 2011) - Update of panel layout: Specify Application Trace (ZATRQ)
  • Update 4 - (August 2011) - Panel and field description updates in Chapter 5 in PM42983 fix
  • Update 5 - (September 2011) - Field description updates in Chapter 5, Chapter 9, and Chapter 15 in PM22223 fix.
  • Update 6 - (December 2011) Chapter 15, Thread Lock Waits, Addition to definition term Resource, in PM50050
  • Update 7 - (February 2012) Update of panel Thread History Lock Waits (ZHTWAIT) in PM44351/PM46935
  • Update 8 - (June 2012) - New object types in Chapter 10. Object Analysis
  • Update 9 - (August 2012) -Updates in Chapter 5. Thread Activity, Chapter 6, Locking Conflicts, and Chapter 15, Near-term history information in PM67040
  • Update 10 - (September 2012) - In the following chapters, the lock types "BPPS" and "SPRC" are added to the list of lock types: Chapter 6. Locking Conflicts, Chapter 8. Application Trace Facility (ATF), Chpater 15. Near-term History information, and Chapter 19. Lock Types and lock levels in PM57463
  • Update 11 - (October 2012) - In Chapter 12, "Address Space Information", the section "Local System Queue Area" is added in PM48517,
  • Update 12 - PM71363 - (November 2012) - New fields are added to the following sections of Chapter 7. Resource Managers and Other DB2 Subsystem Information, "Resource Managers and Other DB2 Subsystem Information menu":
    "Address Space Summary" (ZJ225), "Thread Information" (ZJ225B), and "Shared and Common Storage" ZJ225C.
  • Update 13 - PM75968 - (November 2012) - The panel and field description of the following chapter and section is updated:
    Chapter 6. Locking Conflicts, "Locking Conflicts panel"
  • Update 14 - PM72933 - (January 2013) - The new lock types BMBA and DGTT are added to the appropriate chapters in the documentation.
  • Update 15 - PM84768 - (July 2013) - Chapter 15. Near-term history information, section EDM Pool Statistics Summary by Report Interval, and Chapter 4, Exceptions, section Exception Messages

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


Update 15 - PM84768 - (July 2013) - Chapter 15. Near-term history information, section EDM Pool Statistics Summary by Report Interval, and Chapter 4. Exceptions, section Exception Messages

In chapter 15. Near-term history information, section EDM Pool Statistics Summary by Report Interval, the following definition description is updated like this:

Pages in Use %
The percentage of the pages in the EDM pool that are used during a given interval.
This field is displayed for DB2 version 9.1 and below.
If DB2 version 8.1 or higher is monitored, this field is calculated without DBD pages.

In chapter 4. Exceptions, section Exception Messages, the following definition description for EDM pool utilization (EDMU) is updated like this:

EDMU

EDMU is a member of the DB2 system (SY) exception group. The default threshold for EDMU is 90% of the pool size. The threshold can be any value between 1% and 100%. If the ratio of the pool in use to total pool size exceeds this threshold, OMEGAMON XE for DB2 PE displayes an exception message.

EDMU provides information about EDM pool utilization.

DB2 uses the environmental descriptor management (EDM) pool to manage and contain the following features:

  • Database descriptors (DBDs)
  • Cursor tables (CTs)
  • Skeleton cursor tables (SKCTs)
  • Package tables (PTs)
  • Skeleton package tables (SKPTs)
  • Dynamic SQL caches (DSCs)

The size of each pool is defined by its individual installation parameter.

To compute the EDM-in-use-ratio for DB2 version 8.1 and 9.1, OMEGAMON XE for DB2 PE totals the EDM pages in use by package tables and cursor tables and devides this number by the total EDM pool size. This value does not include DBDs, SKCTs, SKPTs, or DSCs.

To compute the EDM-in-use-ratio for DB2 10.1 and higher, OMEGAMON XE for DB2 PE totals the EDM pages in use by database descriptors (DBDs) and divides this number by the total DBD pool size.

Update 14 - PM72933 - (January 2013) - The lock types BMBA and DGTT are added to the appropriate chapters in the documentation.

In Chapter 6. Locking Conflicts, the following lock types are added to the Resource field:

BMBA BMC_MBAO or BMC_MBAR
DGTT URID=unit of recovery ID

In Chapter 8. Application Trace Facility (ATF), under Application Trace Event Detail, the following Event Tokens are added:

BMBA Buffer manager SCA MBA L-lock.
DGTT DGTT URID lock

In Chapter 15. Near-term history information, under Thread History Lock Waits for Resource, the following lock types are added to the Resource field:

BMBA Buffer manager SCA MBA L-lock
BMC_MBAO or BMC_MBAR
DGTT DGTT URID lock
URID=unit of recovery ID

In Chapter 19. Lock types and lock levels, in the Lock types table, the following lock types are added:


Lock type Description Explanation
BMBA Buffer Manager Buffer Manager gets this lock whenever BM needs to read, insert, or update a MBA record in SCA.
DGTT DGTT URID lock This lock is acquired to protect segments that belong to a Declared Global Temporary Table.

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

Update 13 - PM75968 - (November 2012) - The panel and field description of the following chapter and section is updated:

Chapter 6. Locking Conflicts, "Locking Conflicts panel"

This panel shows existing DB2 locking contentions and deadlocks. It provides
information about the owners and waiters currently involved in locking conflicts.
A locking conflict exists when a DB2 thread owning a resource causes another DB2
thread to wait. In general, when DB2 cannot satisfy a request for the resource, the
requester will be suspended.
A suspended lock resource always has an owning thread. Multiple threads may be
waiting for the same resource. It may also have one or more global owners that
have global interest in the resource.
When S mode is used in data sharing environment, lock resources that are waited
by a local thread will be displayed. All global owners and all local threads that are
involved in this locking conflict are displayed.
When G mode is used in data sharing environment, lock resources that are waited
by a local or remote thread will be displayed. All the global owners and all local
and remote threads that are involved in the locking conflict are displayed.
The plan names of all threads for which the elapsed time exception has tripped are
highlighted. For more information about current thread exceptions, type E.A on the
top line of the panel to display the Exception Messages for Thread Exceptions
panel.

For more information about lock resources, see "Lock Types and Lock Levels".

The following field description in this section is updated:

Resource
Identifies the resource that is currently locked by the lock owner, or the
lock resource causing the lock to be suspended. The resource varies
depending upon the type of lock held.
Note: DB=database name can be represented as a DBID=identifier, which
is the decimal identifier of the database. PSID=identifier can be represented
as PSID=identifier, which is the decimal identifier of the table space. HEX
values are displayed for lock resources if the resource is owned by a thread
on a remote LPAR, and no OMPE task is available from that LPAR, or XCF
is not set up correctly. If the owner is a thread running on some other
member of the data sharing group, the DB2 subsystem name is displayed.

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

Update 12 - PM71363 - (November 2012) - New fields are added to the following sections of Chapter 7. Resource Managers and Other DB2 Subsystem Information, "Resource Managers and Other DB2 Subsystem Information menu":

"Address Space Summary" (ZJ225), "Thread Information" (ZJ225B), and "Shared and Common Storage" ZJ225C:

Chap7_ZJ225_ZJ225B_ZJ225C.pdfChap7_ZJ225_ZJ225B_ZJ225C.pdf

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

Update 11 - (October 2012) - In Chapter 12, "Address Space Information", the section "Local System Queue Area" is added in PM48517,

This panel shows the amount of local system queue area (LSQA) storage that is currently allocated and the amount of storage that is available to be used above and below the 16M line in the specified address space.

This panel requires special authorization because its use causes additional system overhead to collect the necessary data. Type /PWD on the top line of the panel, enter a valid password when requested, then press Enter. Thereafter, OMEGAMON XE for DB2 PE displays the requested information.

Navigation
For additional information about:

  • related topics, select one of the options at the top of the panel.
  • other topics, use the PF keys.

Fields

$DB2MSTR
The name of the job that is running in this address space. (In this case, $DB2MSTR.)

ASID
The address space identification number.

Collected at
The time at which OMEGAMON XE for DB2 Performance Expert collected the information for this LSQA summary.

Allocated
The size of the storage which is currently in use.

Percent Allocated
The percentage of allocated memory versus the whole amount of memory (Allocated / Available * 100).

Available
The overall available LSQA storage. This includes the allocated LSQA/SWA that is available and the storage that is available for the private use of the user.

Largest Available
The largest available contiguous storage area.

Available For User Pvt
The eligible LSQA storage that is available for the private usage of the user.

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

Update 10 - (September 2012)
In the following chapters, the lock types "BPPS" and "SPRC" are added to the list of lock types: Chapter 6. Locking Conflicts, Chapter 8. Application Trace Facility (ATF), Chpater 15. Near-term History information, and Chapter 19. Lock Types and lock levels in PM57463


Chapter 6. Locking Conflicts, section "Locking Conflicts panel"

The following lock types are added to the list of resources:

BPPS
BP=buffer pool ID, DB=database name, PS=pageset name

SPRC
SYS_PITR

Chapter 8. Application Trace Facility, section "Application Trace Event Detail"

The following event tokens are added to the list of event tokens:

BPPS
A buffer manager pageset P-lock.

SPRC
Sys Level PIT Recovery lock

Chapter 15. Near-term history information, section "Thread History Lock Waits"

The following lock types are added to the list of lock types:

BPPS Buffer manager pageset RR P-lock

  • BP=buffer pool ID
  • DB=database name
  • PS=pageset name

SPRC Sys Level PIT Recovery lock
SYS_PITR

Chapter 19. Lock types and lock levels, section "Lock types"

The following lock types are added to the list of lock types:

BPPS Buffer Manager Pageset P-lock A buffer manager pageset RR P-lock
.... .... ....
SPRC Sys Level PIT Recovery lock A Point In Time recovery lock

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

Update 9 - (August 2012)
Updates in Chapter 5. Thread Activity, Chapter 6, Locking Conflicts, and Chapter 15, Near-term history information in PM67040

Chapter 5, Thread Activity, section Threads Summary Excluding Idle Threads

JOBN
The jobname of the thread.
For remote DB2 subsystems, the correlation ID is displayed instead of the job name.

Chapter 5, Thread Activity, section Background Thread Summary

For additional information about one of the following items, perform the corresponding action:

  • Summary information about individual threads that originated from a particular background job, place the cursor to the line that contains that job and press F11 (Zoom). The information might not be displayed if individual threads do not work the address space of the background job, for example, if threads work inside of a DB2 address space.

Active Threads
The number of active threads that originated from the background connection.
This value excludes parallel task threads that are initiated by another thread that is originating from the background connection.

Jobname
The name of the connected batch job or utility.
For remote DB2 subsystems, the correlation ID is displayed instead of the job name.

Chapter 5, Thread Activity, section CICS Thread Summary

Jobname
The job name of the connected CICS region.
For remote threads, this fields displays the correlation ID up to 8 characters.

Active Threads
The number of active threads originating from the CICS connection. This value includes outstanding Create Thread requests not yet satisfied by DB2.
This value excludes threads originating from the CICS connection that are waiting for reuse.

Commit Rate/Sec
The number of DB2 Commits per second originating from the CICS connection.
The Commit rate is computed by determining the number of commits that occurred since the previous OMEGAMON cycle divided by the elapsed time since the previous cycle.

RO Commit Rate/Sec
The number of DB2 read-only Commits per second originating from the CICS connection.
This rate is computed by determining the number of read-only Commits that occurred since the previous OMEGAMON cycle divided by the elapsed time since the previous cycle.

Note: The following fields do not include data of parallel task threads that is initiated by another thread that is originating from the CICS connection:
  • Total CPU
  • DB2 CPU
  • Pct. of THRDMAX
  • Active Threads

Chapter 5, Thread Activity, section IMS Thread Summary

CPU%
The total CPU rate (percent) of IMS regions within the IMS subsystem that have active threads to DB2.
This value excludes data of parallel task threads that are initiated by another thread that is originating from the IMS connection. For more information about CPU use, see "Analyzing DB2 CPU Usage".

Jobid
The name of the dependent or control region in which the thread is active.
For remote DB2 subsystems, the correlation ID is displayed instead of the name of the dependent or control region.

Chapter 5, Thread Activity, section Enclave Thread Summary

Jobname
The name of the active job.
For Distributed threads, this column might contain other identifying data, such as an executable program name. For remote DB2 subsystems, the correlation ID is displayed instead of the job name.

Chapter 5, Thread Activity, sectionTriggers Thread Summary

Jobname
The name of the job that is executing the trigger.
For remote DB2 subsystems, the correlation ID is displayed instead of the job name.

Chapter 5, Thread Activity, section Threads Summary Excluding Idle Threads, in the following subsections:
Thread Detail
Thread Lock/Claim/Drain Activity
Thread Global Lock Activity
Current SQL Counts
Distributed Thread Detail (VTAM and TCP/IP Connections)
Thread Buffer Pool Activity
Thread Group Buffer Pool Activity
Thread Package Summary
Package Detail
Thread Resource Limit Statistics
Current Parallel Task Summary
Utility Detail Information
Objects Used By Thread
SQL Call Being Executed
Cancel Thread
Data Sets Used by Thread
Enclave Detail Information
Long Names
Chapter 6, Locking Conflicts, in the following sections:
Locks/Claims Owned by a Thread
Thread Lock/Claim/Drain Activity
Locks/Claims Causing a Thread to Wait
Thread Global Lock Activity

Attachment identifier: Depending on the type of connection, the appropriate information is displayed. If distributed thread detail is displayed, attach information is displayed only if the thread is a distributed allied thread (not for distributed database access threads).

Connection Type

Batch
The MVS jobname and ASID.
Note: For threads from remote DB2, the MVS job name is N/A.

CICS
The CICS jobname, task name, task number, terminal ID, and thread type. The thread type is:
Pool The thread in use is a pool thread.
Enty The thread in use is a nonprotected entry thread.
Prot The thread in use is a protected thread. Protected threads are defined in an RCT entry definition using the THRDS operand.

IMS
The IMS region number, transaction name, region name, and terminal ID (LTERM).

RRSAF
The MVS job name and ASID.
Note: For threads from remote DB2, the MVS job name is N/A.

System
The originating DB2 job name and the resource manager that is the
source of the thread. An additional line below the Attach line
identifies the user thread, if any, being served by the system
thread.

TSO
The TSO user ID and region ASID.

Utility
No additional information.

Chapter 15, Near-term History Information, in the following sections:
Thread History Detail
Thread History Global Lock Activity
Thread History Buffer Pool Activity
Thread History Package Detail
Thread History Group Buffer Pool Activity
Thread History Lock Waits
Thread History Lock/Claim/Drain Activity
Thread History SQL Counts
Thread History Dynamic SQL Calls
Thread History Resource Limit Statistics
Thread History Distributed Activity
Thread History Package Summary
Thread History Sort and Scan Activity
Thread History Parallel Task

Attachment identifier:

Connection Type
The connection type is displayed in the first field:

APPLDIR
Application directed access (data base access threads)

BATCH
Other DB2 batch threads

CALLATCH
DB2 call attach

CICS
CICS attach

DLI
DL/I batch

IMSBMP
IMS attach BMP

IMSMPP
IMS attach MPP

IMSCTRL
IMS control region

IMSBMPB
IMS transaction BMP

RRSAF
Recoverable Resource Manager Services Attachment Facility

SYSDIR
System directed access (data base access threads)

TSO
TSO foreground and background

Utility
Utility thread

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

Update 8 - (June 2012)
New object types in Chapter 10. Object Analysis


The following object types are added to the list of object types in the sections Database Allocations, Spacename Allocations, and Dataset allocations in chapter 10. Object Analysis:

IXCL - A clone of an index
LBTS - A LOB tablespace
TSCL - A clone of an universal tablespace
TSPG - A partition by growth universal tablespace
TSPR - A partition by range universal tablespace
XMTS - An XML table space

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

Update 7 - (March 2012)
Update of chapter Thread History Lock Waits (ZHTWAIT) in PM44351/PM46935

ko2ci00265_v510.pdfko2ci00265_v510.pdf

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

Update 6 - (December 2011):
Chapter 15, Thread Lock Waits, Addition to definition term Resource, in PM50050

If the name of the resource is not available, N/A and the reason why the resource name is not available is displayed. One of the following reasons might be the cause:

Notify IRLM function
Anything to do with lock state, duration, etc. is invalid.
Query IRLM function
Anything to do with lock state, duration, etc. is invalid.
Change with non zero token
Change a non zero value indicates the lock to free. The values of resource and type are not valid.
Unlock with non zero token
Unlock a non zero value indicates the lock to free. The values of resource and type are not valid.
Lock with non zero token
Token should be zero on Lock.
Reason for the suspend=XX
Is displayed if none of the above reasons is found. See QW0044WS for possible XX values.

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

Update 5 (September 2011):
Field description updates in Chapter 5, Chapter 9, and Chapter 15 in PM22223 fix.

The following subsections were modified:

In chapter 5: Thread Activity


In chapter 9: Distributed Data Facility
  • Distributed Data Facility Statistics
DistributedDataFacilityStatistics.pdfDistributedDataFacilityStatistics.pdf

In chapter 15: Near-term History Information
  • Thread History Distributed Activity
Near-termHistory_ThreadHistoryDistributedActivity.pdfNear-termHistory_ThreadHistoryDistributedActivity.pdf

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

Update 4 (August 2011 - for Version 5.1.0):
Panel and field description updates in Chapter 5 in PM42983 fix

The following information was modified in Chapter 5 "Thread Activity":

  • CICS Thread Summary (ZCICST)
  • CICS RCT Summary (ZCICSTR)
  • CICS RCT Detail (ZCICTRD)

Chap_5_update_ZCICST_ZCICSTR_ZCICTRD.pdf

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

Update 3 (June 2011 - for Version 5.1.0):
Update of panel layout: Specify Application Trace (ZATRQ)

The following information was modified:
Section "Specify Application Trace" in "Application Trace Facility Menu" of Chapter 8 "Application Trace Facility (ATF)":
Chap_8_Appl_Trace_Facility_(ZATRQ).pdf

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

Update 2 (June 2011 - for Version 5.1.0):
Panel and field description updates in Chapter 7 in PM02978 fix

The following information was modified.
-----------------------------------------------------------------------------------------

- Chapter 7. Resource Managers and Other DB2 Subsystem Information

The following description of the Active Trace Detail section was modified:

Active Trace Detail
This panel shows DB2 trace activity at a detailed (IFCID) level. With this information
you can determine how much overhead was incurred in the traces.



Navigation
For additional information about other topics, use the PF keys.

Fields
Trace Qualifications:

Number
The internal DB2 trace number assigned to the trace.

Type The trace type.

Destination
The destinations that are assigned to the trace on this line.

ASID Specifies the address space for which trace data is collected (DB2 V10).

Class The active trace class(es) on this trace.

Rmids
The resource manager IDs (Rmids) specified when the trace was started. If
the trace was qualified with no Rmids, this field contains an asterisk (*).

Tdata The trace headers that are in use by this trace entry.

Plan The plan name qualifying the trace. If the trace was not qualified with a
Plan, this field contains an asterisk (*).

Location
The location name qualifying the remote trace. If the trace was not qualified
with a location, this field contains an asterisk (*).

Authid
The authorization identifier (Authid) qualifying the trace. If the trace was not
qualified with an authorization identifier, this field contains an asterisk (*).

Wrkstn
The workstation name (Wrkstn) qualifying the trace. If the trace was not
qualified with a workstation name, this field contains an asterisk (*) (DB2 V9 and above).

Connid
The connection name (Connid) qualifying the trace. If the trace was not
qualified with a connection name, this field contains an asterisk (*) (DB2 V9 and above).

Appname
The application name (Appname) qualifying the trace. If the trace was not
qualified with an application name, this field contains an asterisk (*) (DB2 V9 and above).

Corrid The correlation name (Corrid) qualifying the trace. If the trace was not
qualified with a correlation name, this field contains an asterisk (*) (DB2 V9
and above).

Userid
The user name (Userid) qualifying the trace. If the trace was not qualified
with a user name, this field contains an asterisk (*) (DB2 V9 and above).

Pkgloc
The location name of the package (Pkgloc) qualifying the trace. If the trace
was not qualified with the location name of the package, this field contains
an asterisk (*) (DB2 V9 and above).

Pkgcol
The collection name of the package (Pkgcol) qualifying the trace. If the
trace was not qualified with the collection name of the package, this field
contains an asterisk (*) (DB2 V9 and above).

Pkgprog
The DBRM or program name (Pkgprog) qualifying the trace. If the trace
was not qualified with a DBRM or program name, this field contains an
asterisk (*) (DB2 V9 and above).

Role The connection role name qualifying the trace. If the trace was not qualified
with a connection role name, this field contains an asterisk (*) (DB2 V9 and above).

Audit Policy Names (AUDTPLCY)
Specifies a list of up to eight audit policy names (AUDTPLCY) for which
trace information is gathered (DB2 V10).

Miscellaneous trace information: The following fields are displayed if the Trace
Destination field contains an OPx destination.

JOBNAME
The jobname that started the trace.

ASID The address space ID of the job that started the trace.

PLANNAME
The plan name of the thread that is using the OPx destination.

AUTHID
The authorization identifier of the thread that started the trace. For active
trace requests in use by OMEGAMON XE for DB2 PE, the authorization ID
is that of the O2CI address space, not the authorization ID of the user
issuing the start trace request.

CONNID
The connection ID of the thread that is using the OPx destination.

CORRID
The correlation ID of the thread that is using the OPx destination.

BUFSIZE
The buffer size value that was used when the trace was started.

Exclude Trace Qualifications:

XPlan The exclude filtering for the plan name (XPlan). If the trace was not
qualified with an XPlan , this field contains NONE (DB2 V9 and above).

XLoc The exclude filtering for the location name (XLoc) qualifying the remote
trace. If the trace was not qualified with an XLoc, this field contains NONE
(DB2 V9 and above).

XAuthid
The exclude filtering for authorization identifier (Xauthid). If the trace was
not qualified with an XAuthid, this field contains NONE (DB2 V9 and above).

XWrkstn
The exclude filtering for workstation name (XWrkstn). If the trace was not
qualified with an XWrkstn, this field contains NONE (DB2 V9 and above).

XConnid
The exclude filtering for connection name (XConnid). If the trace was not
qualified with an XConnid, this field contains NONE (DB2 V9 and above).

XAppname
The exclude filtering for application name (XAppname). If the trace was not
qualified with an XAppname, this field contains NONE (DB2 V9 and above).

XCorrid
The exclude filtering for correlation name (XCorrid). If the trace was not
qualified with an XCorrid, this field contains NONE (DB2 V9 and above).

XUserid
The exclude filtering for user name (XUserid). If the trace was not qualified
with an XUserid, this field contains NONE (DB2 V9 and above).

XPkgloc
The exclude filtering for the location name of the package (XPkgloc). If the
trace was not qualified with an XPkgloc, this field contains NONE (DB2 V9 and above).

XPkgcol
The exclude filtering for the collection name of the package (XPkgcol). If the
trace was not qualified with an XPkgcol, this field contains NONE (DB2 V9 and above).

XPkgprog
The exclude filtering for DBRM or program name (XPkgprog). If the trace
was not qualified with a XPkgprog, this field contains NONE (DB2 V9 and above).

XRole The exclude filtering for connection role name (XRole). If the trace was not
qualified with a XRole, this field contains NONE (DB2 V9 and above).

IFCID information:

Total IFCIDs Active
The total number of trace IFCIDs activated by the trace entry.

IFCID The number of an active IFCID.

IFCID Description
The description of the IFCID on this line.

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


Update 1 (May 2011 - for Version 5.1.0):
Field description updates in Chapter 5, Chapter 6, and Chapter 15, in PM29092 fix

The following information was modified.
-----------------------------------------------------------------------------------------

-Chapter 5. Thread Activity

The following description of the Package identifier section is modified:

Package
The DB2 package name of the active thread. Up to 18 characters of the package name are returned.

The information is updated in the following subsections of "Threads Summary Excluding Idle Threads" in "Chapter 5, Thread Activity":

  • Thread Detail (ZTDTL)
  • Thread Lock/Claim/Drain Activity (ZTLOCT)
  • Thread Global Lock Activity (ZTGLOC)
  • SQL Call Being Executed (ZSQL)
  • Current SQL Counts (ZTSCNT)
  • Distributed Thread Detail (VTAM and TCP/IP Connections) (ZTDIST)
  • Thread Buffer Pool Activity (ZBUF)
  • Thread Group Buffer Pool Activity (ZTGBUF)
  • Thread Package Summary (ZPKG) and the subsection "Package Detail" (ZPKD)
  • Thread Resource Limit Statistics (ZRLMS)
  • Current Parallel Task Summary (ZTASK)
  • Utility Detail Information (ZUTID)
  • Objects Used By Thread (ZUTID)
  • Data Sets Used by Thread (ZIIO)
  • Enclave Detail Information (ZENCLD)
  • Long Names (ZLNAM)


The following description of the Package/DBRM information is updated in section "Thread Package Summary (ZPKG)" of Chapter 5, Thread Activity":

Package/DBRM
The name of the program for which data is reported. Up to 18 characters of
the package name are returned. An asterisk (*) is displayed after the
program name of the last executed program.

Here is an update of the current panel for V510:

________________ ZPKG VTM O2 V510./C SN12 04/05/11 10:07:49 2
> Help PF1 Back PF3 Up PF7 Down PF8 Zoom PF11

> THREAD INFORMATION: Enter a selection letter on the top line.

> A-THREAD DETAIL B-LOCK COUNTS C-LOCK WAITS D-LOCKS OWNED E-GLOBAL LOCKS
> F-CURRENT SQL G-SQL COUNTS H-DISTRIBUTED I-BUFFER POOL J-GROUP BP
> *-PACKAGES L-RES LIMIT M-PARALLEL TASKS N-UTILITY O-OBJECTS
> P-CANCEL THREAD Q-DB2 CONSOLE R-DSN ACTIVITY S-APPL TRACE T-ENCLAVE
> U-LONG NAMES
===============================================================================
> THREAD PACKAGE SUMMARY
PLAN
+ Thread: Plan=DSNESPCS Connid=TSO Corrid=MIS Authid=MIS
+ Attach: TSO Userid=MIS Region asid= 529
+ Package: DSNESM68 Collection=DSNESPCS
+ Luwid=DEIBMIPS.IPSATN12.C79376EB3F60=705
pkl
+ Package List: Location Collection Package
+ ---------------- ------------------ ------------------
+ * DSNESPCS DSNESM68
+ * DSNTIAP DSNTIAP
pkg
+
+ SQL In-DB2 In-DB2 In-DB2
+ Package/DBRM Requests Elapsed Time CPU Time Waits Wait Time
+ ------------------ ---------- ------------ ------------ -------- ------------
+ DSNESM68 * 159 00:06:39.744 00:00:00.651 3447 00:05:55.553
===============================================================================

The following description of the Package information is updated in subsection "Package Detail (ZPKD)" of section "Thread Package Summary (ZPKG)" in Chapter 5, Thread Activity:

Program
The program name for which data is reported. Up to 18 characters of the
package name are returned.

Here is an update of the current panel for V510:

________________ ZPKD VTM O2 V510./C SN12 03/25/11 13:59:40 2
> Help PF1 Back PF3 Up PF7 Down PF8
===============================================================================
> PACKAGE DETAIL
PLAN
+ Thread: Plan=RUNSPNA9 Connid=DB2CALL Corrid=MISRSP9 Authid=MIS
+ Attach: BATCH JOB Name=MISRSP9 JOB Asid= 55
+ Package: SPNAT9_NEWNAME_TES Collection=MIS
+ Luwid=DEIBMIPS.IPSATN12.C785E64DF6BB=2263
pkd SPNAT9_NEWNAME_TES:MIS:PMODBN1
+ Program = SPNAT9_NEWNAME_TES
+ Type = PACKAGE-STORPROC Location = PMODBN1
+ Token = 18EE5F5E1C189E3E Collection = MIS
+ Version = V1
+
+ SQL Request Count = 1
+
+ In-DB2 Times Total Current
+ ------------------------------ ------------ ------------
+ Elapsed Time 00:00:00.000 00:00:00.000
+ CPU Time 00:00:00.000 00:00:00.000
+
+ Waits Count Total Current
+ ------------------------------ ---------- ------------ ------------
+ Synchronous I/O Wait 0 00:00:00.000 00:00:00.000
+ Asynchronous Read I/O Wait 0 00:00:00.000 00:00:00.000
+ Asynchronous Write I/O Wait 0 00:00:00.000 00:00:00.000
+ Local Lock/Latch Wait 90381 00:00:00.683 00:00:00.000
+ Page Latch Wait 0 00:00:00.000 00:00:00.000
+ Drain Lock Wait 0 00:00:00.000 00:00:00.000
+ Drain of Claims Wait 0 00:00:00.000 00:00:00.000
+ Global Parent L-lock Wait 0 00:00:00.000 00:00:00.000
+ Global Child L-lock Wait 0 00:00:00.000 00:00:00.000
+ Global Other L-lock Wait 0 00:00:00.000 00:00:00.000
+ Global Pageset/Partition P-locks 0 00:00:00.000 00:00:00.000
+ Global Page P-lock Wait 0 00:00:00.000 00:00:00.000
+ Global Other P-lock Wait 0 00:00:00.000 00:00:00.000
+ Inter-System Message Send Wait 0 00:00:00.000 00:00:00.000
+ DB2 Service Task Wait 0 00:00:00.000 00:00:00.000
+ Archive Log Mode(Quiesce) Wait 0 00:00:00.000 00:00:00.000
+ Archive Read from Tape Wait 0 00:00:00.000 00:00:00.000
===============================================================================

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

-Chapter 6. Locking Conflicts


The following description of the Package identifier section is modified:

Package
The DB2 package name of the active thread. Up to 18 characters of the package name are returned.

The information is updated in "Chapter 6, Locking Conflicts", section:

  • Locks/Claims Owned by a Thread (ZLOCKO)
  • Thread Lock/Claim/Drain Activity
  • Locks/Claims Causing a Thread to Wait
  • Thread Global Lock Activity

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

-Chapter 15. Near-term history information


The following description is updated in section "Thread History Global Lock Activity (ZHTGLOC)" of Chapter 15. Near-term history information":

The Package identifier section is replaced by the Time identifier section:

Time identifier:
Start The start date and time of this thread execution.
End The end date and time of this thread execution.

The following description of the Time identifier is added to section "Thread History Group Buffer Pool Activity (ZHTGBUF)" of Chapter 15. Near-term history information":

Time identifier:
Start The start date and time of this thread execution.
End The end date and time of this thread execution.


The following description of the Package/DBRM summary is updated in section "Thread History Package Summary (ZHTPKG)" of Chapter 15. Near-term history information":

Package/DBRM
The name of the program for which data is reported. Up to 18 characters of
the package name are returned. An asterisk (*) is displayed after the
program name of the last executed program.

Here is an update of the current panel for V510:

________________ ZHTPKG VTM O2 V510./C SN12 03/25/11 14:11:03 2
> Help PF1 Back PF3 Up PF7 Down PF8 Zoom PF11

> THREAD HISTORY: Enter a selection letter on the top line.

> A-THREAD DETAIL B-LOCK COUNTS C-LOCK WAITS D-GLOBAL LOCKS E-SORT/SCAN
> F-DYNAMIC SQL G-SQL COUNTS H-DISTRIBUTED I-BUFFER POOL J-GROUP BP
> *-PACKAGE SUMMARY L-RES LIMIT M-PARALLEL TASKS
===============================================================================
> THREAD HISTORY PACKAGE SUMMARY
HPLN
+ Thread: Plan=RUNSPNA9 Connid=DB2CALL Corrid=MISRSP9 Authid=MIS
+ Attach: CALLATCH DB2=SN12 MVS=PMO4
+ Time : Start=03/24/2011 15:40:28.190377 End=03/24/2011 15:41:01.548079
+ Luwid=DEIBMIPS.IPSATN12.C784BBE202EE
pkg
+
+ SQL In-DB2 In-DB2 In-DB2
+ Package/DBRM Requests Elapsed Time CPU Time Waits Wait Time
+ ------------------ ---------- ------------ ------------ -------- ------------
+ SPNAT9_NEWNAME_TES 1 00:00:33.022 00:00:25.579 0 00:00:00.000
+ RUNSPNA9 1 00:00:00.334 00:00:00.001 1 00:00:00.000
===============================================================================


The following description of the Package information is updated in section "Thread History Package Detail (ZHTPKD)" of Chapter 15. Near-term history information":

Program
The program name for which data is reported. Up to 18 characters of the
package name are returned.

Here is an update of the current panel for V510:

________________ ZHTPKD VTM O2 V510./C SN12 03/25/11 14:11:16 2
> Help PF1 Back PF3 Up PF7 Down PF8
===============================================================================
> THREAD HISTORY PACKAGE DETAIL
HPLN
+ Thread: Plan=RUNSPNA9 Connid=DB2CALL Corrid=MISRSP9 Authid=MIS
+ Attach: CALLATCH DB2=SN12 MVS=PMO4
+ Time : Start=03/24/2011 15:40:28.190377 End=03/24/2011 15:41:01.548079
+ Luwid=DEIBMIPS.IPSATN12.C784BBE202EE
pkd SPNAT9_NEWNAME_TES:MIS:PMODBN1
+ Program = SPNAT9_NEWNAME_TES
+ Type = PACKAGE Location = PMODBN1
+ Token = 18EE5F5E1C189E3E Collection = MIS
+
+ SQL Request Count = 1
+
+ In-DB2 Times Total
+ ------------------------------ ------------
+ Elapsed Time 00:00:33.022
+ CPU Time 00:00:25.579
+
+ Waits Count Total
+ ------------------------------ ---------- ------------
+ Synchronous I/O Wait 0 00:00:00.000
+ Asynchronous Read I/O Wait 0 00:00:00.000
+ Asynchronous Write I/O Wait 0 00:00:00.000
+ Local Lock/Latch Wait 0 00:00:00.000
+ Page Latch Wait 0 00:00:00.000
+ Drain Lock Wait 0 00:00:00.000
+ Drain of Claims Wait 0 00:00:00.000
+ Global Lock Wait 0 00:00:00.000
+ Inter-System Message Send Wait 0 00:00:00.000
+ DB2 Service Task Wait 0 00:00:00.000
+ Archive Log Mode(Quiesce) Wait 0 00:00:00.000
+ Archive Read from Tape Wait 0 00:00:00.000
+ ------------------------------ ---------- ------------
+ 0 00:00:00.000
===============================================================================


New panel and field description in Chapter 8. Application Trace Facility (ATF), "Specify Application Trace":

The following information was modified.

Chap_8_Specify Application Trace(ZATRQ).pdf



Related information

URL or Document Number
Information Management
Tivoli Software Information

Publication number

SH12-6924-01

Copyright date

2005, 2011

Original publication date

2011/3/8

Product Alias/Synonym

OMEGAMON XE for DB2 PE
OMEGAMON XE for DB2 PM

Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 Tools for z/OS
IBM Tivoli OMEGAMON XE for DB2 PE / PM / BPA

Software version:

5.1.0

Operating system(s):

z/OS

Software edition:

All Editions

Reference #:

7020388

Modified date:

2013-07-15

Translate my page

Machine Translation

Content navigation