V 4.2.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, SC19-2507-00, for Version 4.2.0.

Content

  • Update 1: Modification to Filter Options panel to filter active/inactive threads and to Profile Maintenance menu to change session profile, in PK90831 (August 2009)
  • Update 2: Modification to Thread History Summary panel and new Thread History Times Summary panel with time-based near-term history information from other panels in more convenient way, in PK95877 (September 2009).
  • Update 3: Modifications to Application Trace Facility (ATF) panels, in PK95875 (September 2009).
  • Update 4: Revised termination status information for Thread History Summary and Thread History Detail panels, in PK92602 (September 2009).
  • Update 5: Revised information about "Suspends - False Contention" on Thread Global Lock Activity and Thread History Global Lock Activity panels in PK75515 (January 2010)
  • Update 6: Revised DB2 Connect scope information about DB2C Master in Redirect Monitoring to Another DB2 and related panels in PK93918 (January 2010)
  • Update 7: Revised meaning of Scope field and Status field on REDIRECT MONITORING TO ANOTHER DB2 panel, in PM09518 (June 2010)
  • Update 8: Field updates for PACKAGE DETAIL (ZPKD) and THREAD HISTORY PACKAGE DETAIL (ZHTPKD), in PM17596 (November 2010)
  • Update 9: Field update for the Locks/Claims Owned by a Thread (ZLOCKO) panel, in PM31674 fix (February 2011)
  • Update 10: Field update for the DSNZPARM Thread Parameters (ZPSYS) panel, in PM24529 fix (March 2011)
  • Update 11: Field description updates in Chapter 5, Chapter 6, and Chapter 15, in PM29092 fix (May 2011)
  • Update 12: Panel and field description updates in Chapter 7 in PM02978 fix (June 2011)
  • Update 13: Chapter 5. "Thread Activity": Panel and field updates for CICS Thread Summary (ZCICST), CICS RCT Summary (ZCICSTR), and CICS RCT Detail in PM34737 (ZCICTRD) (August 2011)
  • Update 14: Chapter 15, Thread Lock Waits, Addition to definition term Resource, in PM50500 (December 2011)
  • Update 15: Update of topic Thread History Lock Waits in PM44351/PM46935 (February 2012)
  • Update 16: Updates in chapter 3: Summary of DB2 Activity, chapter 5: Thread Activity, chapter 6: Locking Conflicts, and chapter 15: Near-term History Information for PM67027 (August 2012)


Update 1: Modification to Filter Options panel to filter active/inactive threads and to Profile Maintenance menu to change session profile, in PK90831 (August 2009)

7.10 Filter Options For Thread Activity Displays

Use this panel to save filter criteria to a specified profile, to
activate a different profile, or to specify filter criteria that are to
be used in the thread activity panels for the remainder of the session.




Shortcut to specify filter criteria on thread activity panels

If you already know the available filter criteria, you can bypass the
Filter Options panel and enter the criteria directly on any thread
activity panel. The following example shows a partial Threads Summary
Excluding Idle Threads panel. The criteria (here: PLAN¬=KO2PLAN) is
entered on the "command line" following the (panel-specific) identifier
THDA. To remove the criteria, overtype them with space characters and
press Enter.

Note the status information about filtering and the profile in use.




Fields

Use the following fields to specify the filter criteria. For more
details like operators, wildcard characters, field types, and so on, use
online help F1 (Help).

PLAN The DB2 plan name of the active thread.

PACKAGE/DBRM
The DB2 package name or DBRM name of the active thread.

COLLECTION
The package collection identifier. This field is displayed only
if a package is being used.

AUTHID The DB2 thread authorization identifier of the active thread.

CONNID The DB2 connection identifier of the active thread.

CORRID The correlation identifier. If the application requestor is a
DB2 system, this is the same correlation ID assigned at the
requestor. If the application requestor is not DB2, this is the
name of the job, task, or process that is being serviced.

LOCATION The name of the location requesting information.

DB2STAT See "DB2 Thread Status" for definitions of all possible DB2
status values.

PARENTACE
parentace=0 eliminates child parallel tasks from the Thread
Activity displays.

GETPAGES The number of Getpage requests issued by the thread since
thread creation.

UPDATES The number of DB2 page updates made by the thread since thread
creation.

This value is incremented each time a row in a page is updated,
not just once for each page updated. DB2 might update pages
when it creates intermediate result tables because of a
qualified SELECT statement, even though SELECT statements are
generally thought of as read only operations. Pages that have
been updated are written asynchronously by DB2, according to
DB2's internal Deferred Write algorithm, not immediately after
update or commit.



DB2 resets the page update count at Create Thread and Signon.
If Signon is not driven, the page update count is cumulative.


COMMITS The number of times the thread successfully completed commit
processing. DB2 resets the commit count at thread create and
signon. If signon is not driven, the count is cumulative.

ELAPTIME The elapsed time since thread creation.

ELAPTIME/COMMIT
Average elapsed time between commits.

DB2TIME The total in-DB2 elapsed time in seconds for an active thread.

DB2TIME/COMMIT
Average in-DB2 elapsed time between commits.

WORKSTATION
The workstation identifier.

TRANSACTIONID
The transaction ID.

ENDUSERID
The end user ID.

PROCESSING-IN-DB2
Flag to filter active or inactive threads.Y filters
(suppresses) inactive threads; only active thread are shown. N
filters (suppresses) active threads; only inactive thread are
shown.



16.2 Profile Maintenance menu

This menu is the first menu for the Profile Maintenance Facility. From
this menu you can access panels to change the characteristics of
exceptions, change options for the current OMEGAMON XE for DB2 PE
session, save, delete, change, and list profiles, or add descriptions to
profiles.



16.17 Change Profile

Use this panel to change the currently used profile to a different one.



Because this panel contains options that can have a great effect on the
system, this panel might require special authorization. If OMEGAMON XE
for DB2 PE prompts you for authorization, first type /PWD on the top
line of the panel. Then type your password and press Enter.



Update 2: Modification to Thread History Summary panel and new Thread History Times Summary panel with time-based near-term history information from other panels in more convenient way, in PK95877 (September 2009).


17.22 Thread History Summary

This panel provides summary information about thread activity within a
report interval.




17.28 Thread History Times Summary

This panel provides time-based summary information of threads that
completed within a report interval.



Navigation

For additional information about
* a particular thread, move the cursor to the thread information line
and press F11 (Zoom).
* related topics, choose on of the options at the top of the panel.
* other topics, use the PF keys.



Fields

Report Interval
The timespan (to the nearest minute) of the report.

Start The start date and time of the interval currently displayed.

Report Filtered
This field shows YES if thread filter values were used to
create this display. Otherwise, NO is displayed.

End The end time of the interval currently displayed.

End Time The end time of the DB2 thread execution.

If this thread is involved with parallel processing, one of the
following parallel task identifiers is displayed after the end
time:

* Indicates that this thread is a parallel task
initiated on behalf of another (originating) thread to
process a query request in parallel.

P Indicates that this thread is the parent, or
originating thread, of the parallel tasks created to
process a query request in parallel. Activity
performed for this (originating) thread is reflected
under the parallel tasks.

Plan The DB2 plan name.

Authid The DB2 authorization identifier of the threads.

Elapsed Time
The total elapsed time for the thread.

CPU Time The amount of CP time used by the thread. This value reflects
MVS TCB time for non-database access threads and SRB time for
database access threads and parallel tasks. This time
represents CP time only and does not include zIIP time.

In-DB2 Elap Tm
The elapsed time spent in DB2. Accounting class 2 is required.
Displays N/A if accounting class 2 data is not available.

In-DB2 CPU Tm
The CPU time spent in DB2. Accounting class 2 is required.
Displays N/A if accounting class 2 data not available.

SQL The total number of DCL, DDL, and DML SQL calls issued by the
thread. COMMIT and ROLLBACK/ABORT are not included.

Getpag The number of Getpage requests issued.


Update 3: Modifications to Application Trace Facility (ATF) panels, in PK95875 (September 2009).

All Application Trace Facility (ATF) panels show the current state of an application trace, including a possible trace data set full condition.

The Specify Application Trace panel provides an option to specify the reuse of an already existing data set for trace data collection. Overtype the default APPEND by REUSE in the following panel.





U pdate 4: 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 5: 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 6: Revised DB2 Connect scope information about DB2C Master in Redirect Monitoring to Another DB2 and related panels in PK93918 (January 2010)

5.3 Redirect Monitoring to Another DB2

Use this panel to change the DB2 system you are monitoring or to
redirect OMEGAMON XE for DB2 PE to a restarted DB2 system.



Fields

Name The name of the DB2 subsystem.

Command Prefix
The name of the DB2 command prefix.

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.

M* The indicated DB2 subsystem is a member of a data
sharing group and controls the DB2 Connect monitoring
for the group (the subsystem is the current DB2C
Master).

When the PE Server subtask acting as DB2C Master
terminates, the value changes from M* to M and DB2
Connect data is no longer monitored.

If another PE Server subtask in the data sharing group
takes over DB2 Connect monitoring and becomes the new
DB2C Master:
* The value changes from M to M*.
* The name of the DB2 subsystem now acting as the new
DB2C Master is shown on the corresponding DB2
Connect panels.

Note: During the transition of the DB2C Master role
(which might take several minutes) DB2 Connect
data cannot be monitored, no DB2 subsystem is
marked as DB2C Master, and on corresponding DB2
Connect panels the name of the DB2C Master is
shown as N/A.


Update 7: 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.

M* The indicated DB2 subsystem is a member of a data
sharing group and controls the DB2 Connect monitoring
for the group (the subsystem is the current DB2
Connect group-scope monitoring master, abbreviated as
"DB2C Master").

When the PE Server subtask acting as DB2C Master
terminates, the value changes from M* to M and DB2
Connect data is no longer monitored.



If another PE Server subtask in the data sharing group
takes over DB2 Connect monitoring and becomes the new
DB2C Master:
* The value changes from M to M*.
* The name of the DB2 subsystem now acting as the new
DB2C Master is shown on the corresponding DB2
Connect panels.

Note: During the transition of the DB2C Master role
(which might take several minutes) DB2 Connect
data cannot be monitored, no DB2 subsystem is
marked as DB2C Master, and on corresponding DB2
Connect panels the name of the DB2C Master is
shown as N/A.


Status The following statuses might be displayed:

Active DB2 subsystem is active.

Not Active
DB2 subsystem is not active.


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

The following information has been 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 9: Field update for the Locks/Claims Owned by a Thread (ZLOCKO) panel, in PM31674 fix (February 2011)

The following information has been 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 10: Field update for the DSNZPARM Thread Parameters (ZPSYS) panel, in PM24529 fix (March 2011)

The following information has been 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 11: 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 12: 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 13: Chapter 5. "Thread Activity": Panel and field updates for CICS Thread Summary (ZCICST), CICS RCT Summary (ZCICSTR), and CICS RCT Detail (ZCICTRD) in PM34737 (August 2011)

The following information was modified:
-----------------------------------------------------------------------------------------
CICS Thread Summary (ZCICST)
The modified panel:

The modified field descriptions:
Fields:

CICS connection information:

CICS REL
The CICS release of the connected CICS region. The supported CICS releases are:
6.4.0 for CICS Transaction Server 3.1
6.5.0 for CICS Transaction Server 3.2
6.6.0 for CICS Transaction Server 4.1
6.7.0 for CICS Transaction Server 4.2

Jobname
The jobname of the connected CICS region.

Total CPU
The total CPU rate (percent) of the CICS region connected to DB2. This includes both TCB and SRB time. For more information about CPU use, see "Analyzing DB2 CPU Usage".

DB2 CPU
The total CPU rate (percent) that is attributable to active threads originating from the CICS connection. This value is a subset of the total CICS region CPU utilization. For more information about CPU use, see "Analyzing DB2 CPU Usage".

Pct. of THRDMAX
The percentage of THRDMAX (CICS maximum threads) that the current threads have reached.

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. This value excludes parallel task threads initiated on behalf of another thread originating from the CICS connection.

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.

CICS thread information:

Elapsed
The elapsed time since thread creation, or since DB2 signon if the thread is reused. When the elapsed time of the thread exceeds 24 hours, the format is dd-hh:mm. If this thread is involved with parallel processing, one of the following parallel task identifiers is displayed after the elapsed time:
* - Indicates that this thread is a parallel task initiated on behalf of another (originating) thread to process a query request in parallel.
X - Indicates that this thread is a parallel task initiated on behalf of another (originating) thread on another DB2 for sysplex parallelism.
P - Indicates that this thread is the parent, or originating thread, of the parallel tasks created to process a query request in parallel. Activity performed for this (originating) thread is reflected under the parallel tasks.

Planname
The DB2 plan name of the active thread.

CPU (if monitoring a DB2 subsystem or a data sharing group member)
The CPU rate (percent) attributable to the thread.
For more information about CPU use, see "Analyzing DB2 CPU Usage".

DB2 (if monitoring a data sharing group)
The name of the DB2 subsystem that is currently being monitored.

Status
The current DB2 status of the thread. For definitions of all possible status values, see "DB2 Thread Status".

GetPg The number of thread Getpage requests. This logical read request might not actually result in physical I/O if the requested page is currently in the buffer pool.

Update
The number of DB2 page updates made by the thread since thread creation. This value is incremented each time a row in a page is updated, not just once for each page updated. DB2 might update pages when it creates intermediate result tables because of a qualified SELECT statement, even though SELECT statements are generally thought of as read only operations. Pages that have been updated are written asynchronously by DB2, according to DB2's internal Deferred Write algorithm, not immediately after update or commit.

Commit
The number of times the thread successfully completed Commit processing.

Jobname | Corrid
This field is customizable by means of user mod TKANSAM(KO2MOD02) and shows either:
Jobname - The jobname of the connected CICS region (default).
Corrid - The correlation ID of the CICS thread if OMPEOPTS member in RKD2PAR has the following setting: CICSCORR=YES .


-----------------------------------------------------------------------
CICS RCT Summary (ZCICSTR)
The modified panel:

The modified field descriptions:
Fields:

CICS
The CICS jobname. If you enter a different jobname, the corresponding RCT summary information is displayed.

RELEASE
Identifies the release number of the CICS system:
6.4.0 for CICS Transaction Server 3.1
6.5.0 for CICS Transaction Server 3.2
6.6.0 for CICS Transaction Server 4.1
6.7.0 for CICS Transaction Server 4.2

DB2CONN Name
The RCT name in use by the CICS jobname.

Statistics Dest (SHDDEST)
The transient data destination used for the shutdown statistics when the attachment facility is stopped.

Error MSG DESTID 1, 2, and 3 (ERRDEST)
The identifier of the DFHDCT destination for unsolicited error messages. As many as three destination IDs can be assigned.

Attachment Standby Mode
The attachment standby mode for this CICS region. Possible values are: STANDBY, CEX2STRT, CEX2TERM, DB2MAINT, MSBACTIV, RESYNC, or N/A.

CICS Auth Name (SIGNID)
The authorization ID used when the attachment connects to DB2.

THRD Purge Time Interval
Specifies the length of the protected thread purge cycle in the format:
MINUTES : SECONDS.

Tasks on Ready Queue
The number of tasks that are on ready queue (waiting to be scheduled).

Maximum Threads (THRDMAX)
The maximum number of threads that can be created between CICS and DB2 within this RCT.

HWM Tasks on Ready Queue
The high-water mark (HWM) of tasks on ready queue.

Active MVS Subtasks
The number of MVS subtasks that are active.

Number of Free Connections
The number of free connections available.

HWM Active MVS Subtasks
The high-water mark (HWM) of MVS subtasks that are active.

Thread Error Action
The action that will be taken when thread is in error condition. Possible values: ABEND, N906D, N906, or N/A.

Connect Error Action
The action that will be taken when connection is failed. Possible values ABEND, SQLCODE, or N/A.

DB2ENTRY
The identifier of a classification of transactions within this CICS job. When there are multiple transactions with the same RCT definition, this field will display the ID of the first transaction.

PLANNAME
The name of the specific plan for which you want to display statistical information. Use this field to reduce the number of lines displayed at the bottom of the panel.

The following fields are displayed for each command, entry, and pool RCT definition that exists within the resource control table.

DB2ENTRY
The identifier of a classification of transactions within this CICS job. When there are multiple transactions with the same RCT definition, this field displays the ID of the first transaction.

Calls The number of DB2 calls generated by transactions that share an RCT definition since the attach facility was started.

Waits The number of DB2 waits experienced by transactions that share an RCT definition since the attach facility was started.

Aborts
The number of aborts experienced by transactions that share an RCT definition since the attach facility was started.

THRDA
The maximum number of active threads for this RCT entry.

THRDS
The number of MVS TCBs that will be attached (for use by the RCT definition) to the transactions when the attach facility is started.

TCB Time
The CPU time (in seconds) used by transactions originating from this RCT definition. This time represents CP time only and does not include zIIP time.

REUSE
The number of times CICS transactions using DB2ENTRY were able to reuse an already created DB2 thread.


-----------------------------------------------------------------------
CICS RCT Detail (ZCICTRD)
The modified panel:

The modified field descriptions:
Fields:

CICS
The CICS jobname.

RELEASE
Identifies the release number of the CICS system:
6.4.0 for CICS Transaction Server 3.1
6.5.0 for CICS Transaction Server 3.2
6.6.0 for CICS Transaction Server 4.1
6.7.0 for CICS Transaction Server 4.2

Transaction ID (TXID)
The transaction IDs of all CICS transactions that are defined in the RCT entry definition being viewed.

DB2ENTRY Name
The identifier of the transaction or transaction group being viewed.

Plan Name (PLAN)
The name of the plan assigned to the transactions.

Thread TCB Prty (DPMODE)
The MVS dispatching priority of thread TCBs relative to the CICS main TCB. Possible values: High or Low.

Plan Alloc Exit (PLNEXIT)
The name of the exit program that can dynamically allocate the planname for the transaction ID when the first SQL call is issued.

Rollbck on Deadlok (ROLBE)
Determines whether CICS issues a syncpoint rollback when the transaction experiences an Internal Resource Lock Manager (IRLM)-detected deadlock or timeout.
Yes - CICS will roll back all DB2 work and all CICS-protected resources to the last syncpoint.
No - CICS will roll back only the incomplete SQL call that was involved in the deadlock/timeout.

Thread Wait (TWAIT)
The action to take if no thread is available to execute a DB2-CICS transaction.
Pool - If all threads are in use, DB2 places this transaction in the pool; if all pool threads are in use, DB2 places this transaction in a queue.
Yes - If all threads are in use, the transaction waits until a thread is available.
No - If all threads are in use, the transaction abends.

DB2 Accounting Reason
The reason for DB2 Accounting. DB2 accounting is done by one of the following:
UOW - Account for each unit of work (UOW)
TASK - Account for each task
TXID - Account for each Transaction ID change
NONE - No accounting

AUTHID
The authorization identifier if used by transaction(s).

Thread Limit (THRDA)
The maximum number of active threads for this RCT entry.

Prot Thread Limit (THRDS)
The number of MVS TCBs that will be attached (for use by the RCT definition) to the transactions when the attach facility is started.

Authorization Opt. (AUTH)
The type of authorization ID required to execute the DB2 plan for transactions that are originating from the RCT definition. The possible values are:

Group - The group
OPID - A sign-on operator ID
SignID - A sign-on ID
Term - The terminal ID.
TxID - The transaction ID
Userid - The user's sign-on ID
xxxxxx - A character string
* - Indicates a null value

Statistics information:

Count of Calls
The number of DB2 calls generated by the transactions since the CICS-DB2 attach was started.

Current Free TCBs
The number of currently free task control blocks (TCBs) to be reconnected with threads. .

Count of Commits
The number of Commits completed since the attach facility was started.

Current Active TCBs
The number of currently active threads.

Count of Authorizations
The number of times authorization has been invoked for the threads defined to the transactions.

Current Total TCB Time
The CP time (in seconds) used by transactions originating from this RCT definition. This time represents CP time only and does not include zIIP time.

Count of Aborts
The number of aborts experienced by the transactions since the attach facility was started.

Current Active Threads
The number of transactions that are currently active in DB2 or are waiting for a thread (TWAIT=YES).
Count of RO Commits
The number of read-only Commits since the attach facility was started.

Highwater Active Thread
The high-water mark of active threads.

Count of Waits/Ovflw Pool
The number of times that all available threads for the entry were busy, and the transaction had to wait or be diverted to the pool (depending on the setting of Thread Wait).

Current Waits/Ovflw Pool
The number of transactions that are waiting for a thread, or that have overflowed into the pool.
Count of Tasks
The total number of tasks using this DB2ENTRY.

Current Protected Thread
The current protected thread count.

Count of Partial SignOns
The total count of sign-ons.

Highwater Protected Thread
The high-water mark of protected threads.

Count of Thread Terminates
The number of times a thread terminated.

Current ReadyQue Thread
The number of threads waiting to be executed.

Count of Thread Creates
The number of times a thread is created.

Highwater ReadyQue Thread
High-water mark of threads waiting to be executed.

Count of Thread Reuse
The number of times CICS transactions using the DB2ENTRY were able to reuse an already created DB2 thread.

Current User Request
The total count of user requests.

Count of Thread Limit Hits
The number of times the thread reuse limit is hit.

Highwater User Request
High-water mark of user requests.




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

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 15: Update of topic Thread History Lock Waits in PM44351/PM46935 (March 2012)

ko2ci00265_v420.pdfko2ci00265_v420.pdf


Update 16: Updates in chapter 3: Summary of DB2 Activity, chapter 5: Thread Activity, chapter 6: Locking Conflicts, and chapter 15: Near-term History Information for PM67027 (August 2012)

Chapter 3: Summary
Section: 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". For remote DB2 subsystems and in Data Sharing Group mode, this field is marked as not available (N/A).

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 task below:

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

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

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 job name.

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
Section: 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: Threads Summary Excluding Idle Threads, 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
Subsection: Package Detail
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
Log Names

and 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 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 HistoryGroup 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.2.0

Publication number

SC19-2507-00

Original publication date

2009/8/7

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

Operating system(s):

z/OS

Software edition:

All Editions

Reference #:

7016497

Modified date:

2012-08-24

Translate my page

Machine Translation

Content navigation