V 4.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

Product documentation


Abstract

This document updates the IBM ® Tivoli® OMEGAMON XE for DB2® Performance Expert on z/OS and IBM Tivoli OMEGAMON XE for DB2 Performance Monitor on z/OS: Monitoring Performance from the OMEGAMON Classic Interface manual, SC18-9988-02, for Version 4.1.0.

Content

  • Update 1: Modification to Classic Interface Near-Term Thread History Filter Options panel in PK38741 (February 2007)
  • Update 2: Revised near-term history WRITEOPTION(VSAM,SEQ) option, new NTAINTERVAL option in PK38096 (June 2007)
  • Update 3: Added TCP/IP information on Thread History Distributed Activity panel (May 2007)
  • Update 4: Added near-term history data grouped by correlation ID (May 2007)
  • Update 5: Revised formulas for Average Thread Footprint and Maximum Number of Threads for the DBM1 Virtual Storage Below 2 GB panel in PK49139 (August 2007)
  • Update 6: Additional fields on DSNZPARM IRLM Parameters panel in PK64503 (June 2008)
  • Update 7: Revised termination status information for Thread History Summary and Thread History Detail panels, in PK92602 (September 2009).
  • Update 8: Revised information about "Suspends - False Contention" on Thread Global Lock Activity and Thread History Global Lock Activity panels in PK75515 (January 2010)
  • Update 9: Revised meaning of Scope field and Status field on REDIRECT MONITORING TO ANOTHER DB2 panel, in PM09518 (June 2010)
  • Update 10: Field updates for PACKAGE DETAIL (ZPKD) and THREAD HISTORY PACKAGE DETAIL (ZHTPKD), in PM17596 (November 2010)
  • Update 11: Field update for the Locks/Claims Owned by a Thread (ZLOCKO) panel, in PM28794 fix (February 2011)
  • Update 12: Field update for the DSNZPARM Thread Parameters (ZPSYS) panel, in PM24529 fix (March 2011)
  • Update 13: Field description updates in Chapter 5, Chapter 6, and Chapter 15, in PM29092 fix (May 2011)
  • Update 14: Panel and field description updates in Chapter 7, in PM02978 fix (June 2011)
  • Update 15: Updates in chapter 3 "Summary, section "Summary of DB2 Activities", several sections in chapter 5, "Thread activity", chapter 6, "Locking Conflicts, and chapter 15, "Near-term history information" (August 2012)


Update 1: Modification to Classic Interface Near-Term Thread History Filter Options panel in PK38741 (February 2007)

The Near-Term Thread History Filter Options panel and its description now clarify the filter options at thread summary (interval) and at thread detail display levels, as follows:

Near-Term Thread History Filter Options

Use this panel to specify the reporting period for which you want to view near-term thread history information, the intervals into which the report is divided, and filter options that restrict the data that is displayed on subsequent thread history panels.




Navigation

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



Fields

Information about available data:

Time of oldest available record
    Displays the earliest time that thread data was collected to active data sets. Displays N/A if no thread data is collected.
    This is either the time stamp of the first IFCID 3 record or, if detail is not being collected, the oldest near-term thread summary record.


Time of latest record
    Displays the most recent time that thread data was collected to active data sets. Displays N/A if no thread data is collected.
    This is either the time stamp of the last IFCID 3 record or, if detail is not being collected, the last near-term thread summary record.


Total number of records
    Displays the number of thread records (IFCID 3) that are collected to active data sets. Displays 0 if no detail thread records are collected.

Filter options limiting the time: Specify an absolute or relative time range of at most 24 hours for the reporting period for which you want to view near-term thread history information. The specified time range should be within the range of collected data.

START-DATE/TIME
    Specify an absolute start date and time. START-DATE/TIME and RELATIVE-START are mutually exclusive.
    You can specify the date and time in U.S., European, or ISO format.
    DATE
    • mm/dd/yyyy (U.S.)
    • dd.mm.yyyy (European)
    • yyyy-mm-dd (ISO)
    TIME
    • hh:mm (U.S.)
    • hh.mm (European, ISO)

END-DATE/TIME
    Specify an absolute end date and time. END-DATE/TIME and RELATIVE-END are mutually exclusive.
    You can specify the date and time in U.S., European, or ISO format.
    DATE
    • mm/dd/yyyy (U.S.)
    • dd.mm.yyyy (European)
    • yyyy-mm-dd (ISO)
    TIME
    • hh:mm (U.S.)
    • hh.mm (European, ISO)


RELATIVE-START
    Specify a start time relative to the current time, as the number of minutes or hours before the current time. The default value is one hour. RELATIVE-START and START-DATE/TIME are mutually exclusive.

RELATIVE-END
    Specify an end time relative to the specified start time, as the number of minutes or hours after START-DATE/TIME or RELATIVE-START. RELATIVE-END and END-DATE/TIME are mutually exclusive.

REPORT-INTERVAL
    Specify a report interval by which the report period is partitioned, from 5 to 60 minutes, in five minute increments. The value must be some multiple of the Near-Term History Data Collector summary record write frequency.

Filter options to be used at interval display level: You can use these options to filter near-term history data at thread summary (interval) display level.

PLAN
    You can specify up to five plan names that you want to be displayed on subsequent thread history panels. You can enter multiple values including wildcards. You can compare values using the equal (=) or not equal (^=, <>) comparison operators. Use the equal operator to OR multiple values. Use the not equal operator to AND multiple values.

AUTHID
    You can specify up to five authorization ids that you want to be displayed on subsequent thread history panels. You can enter multiple values including wildcards. You can compare values using the equal (=) or not equal (^=, <>) comparison operators. Use the equal operator to OR multiple values. Use the not equal operator to AND multiple values.

CONNID
    You can specify up to five connection ids that you want to be displayed on subsequent thread history panels. You can enter multiple values including wildcards. You can compare values using the equal (=) or not equal (^=, <>) comparison operators. Use the equal operator to OR multiple values. Use the not equal operator to AND multiple values.

CONNTYPE
    You can specify up to five connection types that you want to be displayed on subsequent thread history panels.
    TSO
        TSO foreground and background (QWHCTSO)
    CALLATCH
        DB2 call attach (QWHCDB2C)
    CICS
        CICS attach (QWHCCICS)
    DLI
        DL/I batch (QWHCDLIB)
    IMSBPP
        IMS attach BMP (QWHCIMSB)
    IMSMPP
        IMS attach MPP (QWHCIMSM)
    IMSCTRL
        IMS control region (QWHCICTL)
    IMSBMP
        IMS transaction BMP (QWHCTBMP)
    IMS
        All IMS threads including DL/I batch (QWHCDLIB +QWHCIMSB + QWHCIMSM + QWHCICTL + QWHCTBMP)
    SYSDIR
        System directed access (data base access threads) (QWHCDUW)
    APPLDIR
        Application directed access (data base access threads) (QWHCRUW)
    DIST
        Data base access threads (System-directed and Application-directed) (QWHCDUW + QWHCRUW)
    BATCH
        DB2 call attach (QWHCDB2C)

Filter options to be used only at thread detail display level: You can use these options to filter near-term history data at thread detail display level.

PACKAGE
    You can specify up to five package ids that you want to be displayed on subsequent thread history panels. You can enter multiple values including wildcards. You can compare values using the equal (=) or not equal (^=, <>) comparison operators. Use the equal operator to OR multiple values. Use the not equal operator to AND multiple values.

CORRID
    You can specify up to five correlation ids that you want to be displayed on subsequent thread history panels. You can enter multiple values including wildcards. You can compare values using the equal (=) or not equal (^=, <>) comparison operators. Use the equal operator to OR multiple values. Use the not equal operator to AND multiple values.

GETPAGES
    Specify the minimum number of Getpage requests that you want to be displayed on subsequent thread history panels. You can compare values using the equal (=) or not equal (^=, <>) comparison operators. Use the equal operator to OR multiple values. Use the not equal operator to AND multiple values.

DEADLK/TIMEOUT
    Specify the minimum number of deadlocks and lock timeouts that you want to be displayed on subsequent thread history panels. You can compare values using the equal (=) or not equal (^=, <>) comparison operators. Use the equal operator to OR multiple values. Use the not equal operator to AND multiple values.

LOCK-ESCAL
    Specify the minimum number of lock escalations that you want to be displayed on subsequent thread history panels. You can compare values using the equal (=) or not equal (^=, <>) comparison operators. Use the equal operator to OR multiple values. Use the not equal operator to AND multiple values.

COMMIT
    Specify the minimum number of commits that you want to be displayed on subsequent thread history panels. You can compare values using the equal (=) or not equal (^=, <>) comparison operators. Use the equal operator to OR multiple values. Use the not equal operator to AND multiple values.

DB2-CPU-TIME
    Specify the minimum amount of DB2 processor time that you want to be displayed on subsequent thread history panels. You can compare values using the equal (=) or not equal (^=, <>) comparison operators. Use the equal operator to OR multiple values. Use the not equal operator to AND multiple values.

DB2-ELAP-TIME
    Specify the minimum amount of DB2 elapsed timethat you want to be displayed on subsequent thread history panels. You can compare values using the equal (=) or not equal (^=, <>) comparison operators. Use the equal operator to OR multiple values. Use the not equal operator to AND multiple values.

IO-ELAP-TIME
    Specify the minimum amount of I/O elapsed time that you want to be displayed on subsequent thread history panels. You can compare values using the equal (=) or not equal (^=, <>) comparison operators. Use the equal operator to OR multiple values. Use the not equal operator to AND multiple values.

The Near-Term Thread History Filter Options - Confirmation panel shows the reporting and filtering options that you have specified on the Near-Term Thread History Filter Options panel.


Update 2: Revised near-term history WRITEOPTION(VSAM,SEQ) option, new NTAINTERVAL option in PK38096 (June 2007)

Information regarding near-term history data collection to sequential data sets (WRITEOPTION(VSAM,SEQ)) has been revised. Archiving of VSAM data sets is no longer supported.

The new near-term history data collection options keyword NTAINTERVAL lets you control the subinterval by which near-term thread history data is shown in the Thread History By Subinterval panel. Installations with huge numbers of executed threads per minute can adjust the subinterval to obtain an adequate level of information detail.

Attachments KO2CICH15.PDF and KO2CICH22.PDF contain updates of chapters 15 and 22 of the Classic Interface manual that reflects these changes.


Update 3: Added TCP/IP information on Thread History Distributed Activity panel (May 2007)

The Thread History Distributed Activity panel now shows TCP/IP information about distributed threads, similar to information already available by means of the realtime component of OMEGAMON XE for DB2 PE.

Attachment KO2CICH15.PDF contains updates of chapter 15 of the Classic Interface manual that reflects these changes.


Update 4: Added near-term history data grouped by correlation ID (May 2007)


Near-term thread history data can now be grouped by correlation identifier, in addition to the existing grouping options. The new Thread History By Correlation ID panel is accessible from the Thread History By Report Interval panel.

Attachment KO2CICH15.PDF contains updates of chapter 15 of the Classic Interface manual that reflects these changes.

Update 5: Revised formulas for Average Thread Footprint and Maximum Number of Threads for the DBM1 Virtual Storage Below 2 GB panel in PK49139 (August 2007)

Attachment KO2CICH07.PDF contains updates of chapter 7 of the Classic Interface manual that reflects these changes (page 257).


Update 6: Additional fields on DSNZPARM IRLM Parameters panel in PK64503 (June 2008)


Wait Time Local Deadlock (QWP5DLOK)
Time (in seconds or milliseconds) of the local deadlock
detection cycle. Values between 1 and 5 are seconds and values
between 100 and 5000 are milliseconds. The initial value is
retrieved from the IRLMPROC DEADLOK parameter. This value can
be changed dynamically with the MODIFY
irlmproc,SET,DEADLOCK=nnnn command.

Local Cycles Per Global (QWP5DCYC)
The number of local deadlock cycles that must expire before the
IRLM performs global deadlock detection processing. This value
is retrieved from the IRLMPROC DEADLOK parameter. In a data
sharing environment, IRLM synchronizes all DEADLOK values in
the group to the values specified on the most recent IRLM to
join the group. The DEADLOK values can be changed by starting a
member with the required values.

CF Lock Table Hash Entries (QWP5HASH)
The number of lock table entries (LTE) that IRLM has allocated
in the XCF LOCK structure. The initial value is calculated by
the IRLM based on IRLMPROC parameters and the XCF LOCK
structure size. This value can be changed dynamically with the
MODIFY irlmproc,SET,LTE=nnnn command. For more information, see
DB2 Data Sharing: Planning and Administration and "CF Pending
Hash Entries".

IRLM Maximum CSA Allowed (QWP5MCSA)
The maximum amount of common service area (CSA) and extended
CSA (ECSA) that the IRLM for this DB2 uses for its lock control
block structure. This value is retrieved from the IRLMPROC
MAXCSA parameter.

CF Pending Hash Entries (QWP5PHSH)
The number of LOCK HASH entries (LTE) that this IRLM can use on
the next connect to the XCF LOCK structure. This value is set
by MODIFY irlmproc,SET,LTE=nnnn command and exists until the
next time the IRLM connects to the XCF LOCK structure or a
subsequent MODIFY irlmproc,SET,LTE=nnnn command is issued. For
more information, see DB2 Data Sharing: Planning and
Administration and "CF Lock Table Hash Entries".

PC Yes Specified (QWP5PCY)
Indicates whether the IRLM is to use the cross-address-space
program call. This value is retrieved from the IRLMPROC PC
parameter.

CF Lock Table List Entries (QWP5RLE)
The number of entries (RLE) in the list of update locks that
are currently held in the XCF LOCK structure. This list is
sometimes called the "modify lock list" or "record list table".
The initial value is calculated by the IRLM based on IRLMPROC
parameters and the XCF LOCK structure size. This value can be
changed dynamically with the MODIFY irlmproc,SET,LTE=nnnn
command or a XCF LOCK structure resizing. For more information,
see DB2 Data Sharing: Planning and Administration and "CF Lock
Table Hash Entries".

Current Timeout Interval (QWP5TVAL)
The initial value is retrieved from the Timeout Interval
(IRLMRWT). The current value can be changed dynamically with
the MODIFY irlmproc,SET,TIMEOUT=nnnn,subsystem-name command.



Update 7: Revised termination status information for Thread History Summary and Thread History Detail panels, in PK92602 (September 2009).

Thread History Summary termination status: The status that indicates the reason for the thread termination.

READS IFI READ request

RESIGN Same user signed on with same authentification
identifier.

NEWUSE User signon

DDFINA The distributed thread went inactive.

DEALLO Thread termination.

COMMIT RRSAF thread specified accounting interval = COMMIT

EOT/TE End of task, application terminated normally.

EOT/AB End of task, application terminated abnormally.

EOM/AB End of memory, application terminated abnormally.

RES/IN Resolve indoubt processing.

FORCE Stop forced, MVS cancelled DB2 or MVS forced DB2.

IEOT/T End of task, application terminated normally and is
indoubt.

IEOT/A End of task, application terminated abnormally and is
indoubt.

IEOM/A End of memory, application terminated abnormally and
is indoubt.

IFORCE Stop forced, MVS cancelled DB2 or MVS forced DB2, and
the thread is indoubt.

STALE Staleness Threshold exceeded for DDF or RRSAF thread

LIMIT DDF ROLLUP threshold limit exceeded.

STORAG Internal DB2 storage threshold was reached for DDF or
RRSAF thread.

INACT Distributed database access thread termination.


Thread History Detail termination status: The status that indicates the reason for the thread
termination:
* READS
* RESIGNON
* NEWUSER
* DDFINACT
* DEALLOC
* COMMIT
* EOT/TERM
* EOT/ABND
* EOM/ABND
* RES/INDT
* FORCE
* IEOT/TRM
* IEOT/ABN
* IEOM/ABN
* IFORCE
* STALE
* LIMIT
* STORAGE
* INACT


Update 8: Revised information about "Suspends - False Contention" on Thread Global Lock Activity and Thread History Global Lock Activity panels in PK75515 (January 2010)

Suspends - False (and Conv)
Summation of false contentions and sync-to-async heuristic conversions.

XES detects hash class contention when two different locks on
different resources hash to the same entry in the coupling
facility lock table. The requester is suspended until it is
determined that no real lock contention exists.

Sync-to-async heuristic conversions are done when the XES
determines that it is more efficient to drive the request
asynchronously to the coupling facility.


Update 9: Revised meaning of Scope field and Status field on REDIRECT MONITORING TO ANOTHER DB2 panel, in PM09518 (June 2010)

Scope The scope for the command prefix. Possible values are:

S The indicated DB2 subsystem is a single subsystem that
is not a member of a data sharing group.

M The indicated DB2 subsystem is a member of a data
sharing group.


Status The following statuses might be displayed:

Active DB2 subsystem is active.

Not Active
DB2 subsystem is not active.

Update 10: Field updates for PACKAGE DETAIL (ZPKD) and THREAD HISTORY PACKAGE DETAIL (ZHTPKD), in PM17596 (November 2010)

The following information was modified:


- Chapter 5. Thread Activity

Navigation hint:

  1. Open the table of contents
  2. Click Chapter 5. Thread Activity
  3. Click 'Threads Summary Excluding Idle Threads'
  4. Click 'Thread Package Summary'
  5. Click 'Package Detail ' (ZPKD)

The following field description has been modified:
Stored Procedure Schedule Wait
Waits for an available TCB to schedule a stored procedure.
This Wait is not supported in DB2 V9.1 or later.

The following field description of has been added:
User-defined Function Schedule Wait

Waits for an available TCB to schedule user-defined functions. Current Wait Time is not available for this entry. This Wait is not supported in DB2 V9.1 or later.

- Chapter 15. Near-term History Information

Navigation hint:

  1. Open the table of contents
  2. Click Chapter 15. Near-term History Information
  3. Click 'Thread History Package Detail' ( ZHTPKD)

The following field description has been added:
Stored Procedure Schedule Wait
Waits for an available TCB to schedule a stored procedure.
This Wait is not supported in DB2 V9.1 or later.


Update 11: Field update for the Locks/Claims Owned by a Thread (ZLOCKO) panel, in PM28794 fix (February 2011)

The following information was modified:

- Chapter 6. Locking Conflicts -> Locks/Claims Owned by a Thread (ZLOCKO) panel
The following field description has been updated:

ISOLATION Option
The ISOLATION option specified when the plan is bound. The isolation parameter allows you to control the data consistency in the pages that the plan accesses. It has an effect on the number of page or row locks held concurrently by an application. The available options are:

  • Cursor Stability (CS)
    Causes a page lock acquired for read processing to be released when the application subsequently accesses data contained on another data page. (Page locks acquired as a result of update activity are always retained until commit.)
  • Read Stability (RS)
    Is similar to Repeatable Read but this isolation option allows to insert new rows or update rows that did not satisfy the original search condition of the application.
  • Repeatable Read (RR)
    Causes all application locks obtained for read processing to be retained until application commit time.
  • RR with X-lock
    Means Repeatable Read with X-lock.
  • RS with X-lock
    Means Read Stability with X-lock.
  • Uncommitted Read (UR)
    Causes data to be read without acquiring locks. This can result in accessing data that has been updated but not yet committed. It applies only to read-only operations: SELECT, SELECT INTO, or FETCH from a read-only result table. Use this isolation level only when:
    - Data consistency is not necessary or inconsistencies already exist
    - Errors cannot occur with its use, such as with a reference table that is rarely updated


Update 12: Field update for the DSNZPARM Thread Parameters (ZPSYS) panel, in PM24529 fix (March 2011)

The following information was modified:


- Chapter 7. Resource Managers and Other DB2 Subsystem Information -> DSNZPARM Thread Parameters (ZPSYS) panel

The following field description has been added:

Enable Use Of DB2 Sort (DB2 Version 8 or later)
Specifies if the DB2 Sort feature is enabled or disabled:
YES - DB2 Sort is enabled.
NO - DB2 Sort is disabled.


Update 13: Field description updates in Chapter 5, Chapter 6, and Chapter 15, in PM29092 fix (May 2011)

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 Thread Package Summary (ZPKG):



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 Package Detail (ZPKD) :



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

-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 Thread History Package Summary (ZHTPKG):



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 Thread History Package Detail (ZHTPKD):






Update 14: Panel and Field description updates in Chapter 7, in PM02978 fix
(June 2011)

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.

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

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

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

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

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

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

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

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

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

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

JOBNAME
The job name 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).

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

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

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

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

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

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

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

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

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

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

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

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 15: Updates in chapter 3 "Summary, section "Summary of DB2 Activities", several sections in chapter 5, "Thread activity", chapter 6, "Locking Conflicts, and chapter 15, "Near-term history information" (August 2012)

Chapter 3, Summary, subsection Summary of DB2 Activity

Connections
The number of active connections originating from the connection type. For Distributed, it is the count of remote DB2 connections in which the DB2 subsystem being monitored has active DB2-to-DB2 system conversations.
For remote DB2 subsystems and in Data Sharing Group mode, this field is marked as not available (N/A).

Threads
The number of active threads that are originating from the connection type. This number includes active parallel task threads that are initiated by threads that are originating from the connection type. For Distributed, it is the number of active database access threads that are active on the DB2
subsystem being monitored.

CPU
The total CPU rate (percent) attributable to the connection type. For non-CICS connection types, this value is the total CPU rate of all address spaces within the connection type with active threads. For CICS connections, this value is the total CPU rate attributable to all active threads originating from CICS connections. For more information about CPU use, see "Analyzing DB2 CPU Usage".

Chapter 5, Thread activity, subsection "All Threads Connected to DB2"

CORRID/JOBN
You can customize this field by using user mod TKANSAM(KO2MOD02). This field shows either one of the following parameters:
CORRID
The correlation ID of the thread.
JOBN
The jobname of the thread.
For remote DB2 subsystems, the correlation ID is displayed instead of the job name.

Chapter 5, Thread activity, subsection "Background Thread Summary"

For additional information about

  • summary information about individual threads that originate from a particular background job, place the cursor on 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 originate 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, subsection "CICS Thread Summary"

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

Jobname | Corrid
You can customize this field by using user mod TKANSAM(KO2MOD02). This field shows one of the following parameters:
Jobname
The jobname of the connected CICS region (by default).
For remote threads, this field shows the correlation ID up to 8 characters.
Corrid
The correlation ID of the CICS thread if OMPEOPTS member in RKD2PAR has the following setting: CICSCORR=YES.

Chapter 5, Thread activity, subsection "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".

Threads
The total number of threads connected from the IMS subsystem.
This value excludes data of parallel task threads that are initiated by another thread that is originating from the IMS connection.

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, subsections "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, subsections "Triggers 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 "All Threads Connected to DB2, in the following subsections:
Thread Detail
SQL Call Being Executed
Current SQL Counts
Distributed Thread Detail (VTAM and TCP/IP connections)
Thread Buffer Pool Activity
Thread Group Buffer Pool Activity
Thread Package Summary
Thread Resource Limit Statistics
Current Parallel Task Summary
Utility Detail Information
Objects Used By Thread
Cancel Thread
Data Sets Used by Thread
Enclave Detail Information
Long Names

and Chapter 6, Locking Conflicts, in the following subsections:
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 subsections:
Thread History Detail
Thread History Lock Waits
Thread History Lock/Claim/Drain Activity
Thread History SQL Counts
Thread History Dynamic SQL Calls
Thread History Buffer Pool Activity
Thread History Resource Limit Statistics
Thread History Distributed Activity
Thread History Package Summary
Thread History Package Detail
Thread History Sort and Scan Activity
Thread History Group Buffer Pool Activity
Thread History Parallel Task
Thread History Global Lock Activity

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

Related information

Classic Interface Version 4.1.0

KO2CICH07.PDFKO2CICH15.PDF KO2CICH22.PDF

Publication number

SC18-9988-02

Original publication date

2008/8/26

Product Alias/Synonym

DB2PE

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

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

Software version:

4.1.0

Operating system(s):

z/OS

Software edition:

All Editions

Reference #:

7010061

Modified date:

2012-08-22

Translate my page

Machine Translation

Content navigation