V 5.1.1: Update of the manual "Monitoring Performance from the OMEGAMON Classic Interface" 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 contains updates of the manual "Monitoring Performance from the OMEGAMON Classic Interface", SH12-6966-00, of the products "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.1.

Content

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

  • Update 2- PM66261 - (October 2012) - Updates in Chapter 5. Thread Activity, Chapter 6, Locking Conflicts, and Chapter 15, Near-term history information.
  • Update 3 - PM68650 - (November 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), Chapter 15. Near-term History information, and Chapter 19. Lock Types and lock levels.
  • Update 4 - 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 5 - PM71108 - (November 2012) - The field description of the following chapters is updated:
    • Chapter 5. Thread Activity, "Threads Summary Excluding Idle Threads", "Current SQL Counts"
    • Chapter 5. Thread Activity, "Threads Summary Excluding Idle Threads", "Distributed Thread Detail (VTAM and TCP/IP Connections)"
    • Chapter 7. Resource Managers and Other DB2 Subsystem Information, "Buffer Manager Information"
    • Chapter 7. Resource Managers and Other DB2 Subsystem Information, "Buffer Pool Detail"
    • Chapter 7. Resource Managers and Other DB2 Subsystem Information, "Group Buffer Pool Detail"
    • Chapter 7. Resource Managers and Other DB2 Subsystem Information, "EDM Pool Information"
    • Chapter 7. Resource Managers and Other DB2 Subsystem Information, "SQL/RID Pool/Parallelism/Stored Procedure Information"
    • Chapter 9. Distributed Data Facility, "Distributed Data Facility Statistics"
    • Chapter 15. Near-term history information, "Buffer Pool Statistics Summary by Report Interval" ,"Buffer Pool Statistics Detail"
    • Chapter 15. Near-term history information, "Distributed Data Facility Statistics Summary by Report Interval" ,"Distributed Data Facility Statistics Detail"
    • Chapter 15. Near-term history information, "Group Buffer Pool Statistics Summary by Report Interval" ,"Group Buffer Pool Statistics Detail"
    • Chapter 15. Near-term history information, "EDM Pool Statistics Summary by Report Interval" ,"EDM Pool Statistics Detail"
    • Chapter 15. Near-term history information, "SQL Statistics Summary by Report Interval" ,"SQL/RID Pool/I/O Parallelism Statistics Detail"
    • Chapter 15. Near-term history information, "Thread History Distributed Activity"
    • Chapter 15. Near-term history information, "Thread History SQL Counts"
  • Update 6 - PM75968 - (November 2012) - The panel and field description of the following chapter and section is updated:
    Chapter 6. Locking Conflicts, "Locking Conflicts panel"
  • Update 7 - PM72933 - (Januar 2013) - The lock types BMBA and DGTT are added to the appropriate chapters in the documentation
  • Update 8 - PM81181 - (March 2013) - For redirecting the monitoring to another DB2, the new status "Unsupported" is added.
  • Update 9 - PM80739 - (April 2013) - Support for the Integrated DB2 Analytics Accelerator
  • Update 10 - 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 11 - PM57463 (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

__________________________________________________________________________________

Update 11 - PM57463 - (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

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 10 - 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 9 - PM80739 - (April 2013) - Support for the Integrated DB2 Analytics Accelerator
  • In the panel Threads Summary Excluding Idle Threads (ZALLT), the new thread status "IN-ACCEL" is added.


    ________________ ZALLT VTM O2 V511./C DA31 S 03/25/13 16:44:16 2
    > Help PF1 Back PF3 Up PF7 Down PF8 Sort PF10 Zoom PF11
    > T.A
    > Thread Activity: Enter a selection letter on the top line.

    > *-All-Idle B-TSO C-CICS D-IMS E-Background F-Dist Allied
    > G-Dist DBAC H-Util I-Inact J-Filter K-Functions L-Stored Proc
    > M-Triggers N-Sysplex O-Enclaves P-Worksta Q-All+Idle
    ===============================================================================
    > Threads Summary Excluding Idle Threads
    THDA
    + *
    + Elapsed Planname CPU Status GetPg Update Commit CORRID/JOBN
    + ---------- -------- ----- ------------ ------ ------ ------ ------------
    + 02-21:46 KO2PLAN 00.0% NOT-IN-DB2 0 0 0 D822DM1S
    + 02-01:23 KO2PLAN 00.0% NOT-IN-DB2 0 0 0 SN14DM1S
    + 02-01:22 KO2PLAN 00.0% NOT-IN-DB2 0 0 0 SN14DM1S
    + 00:26:07.7 KO2PLAN 00.0% NOT-IN-DB2 0 0 0 DA31DM1S
    + 00:26:07.0 KO2PLAN 00.0% NOT-IN-DB2 74 0 7 DA31DM1S
    + 00:25:35.9 KO2PLAN 00.0% NOT-IN-DB2 0 0 0 DA31DM1S
    + 00:00:13.4 WAYNEPLN 00.0% IN-ACCEL 149 0 0 DA31DIST
    ===============================================================================

  • In the panel Thread Accelerator Detail (ZTACEL), the new option "W" provides details about using the thread acclerator. Option "W" is available after you zoomed into one of the threads by pressing F11 (Zoom) from most of the panels that are included in Chapter 5. Thread Activity. You can also display the IN-ACCEL status by using option "A-THREAD DETAIL".

    ________________ ZTACEL VTM O2 V511./C DA31 03/25/13 16:45:59 2
    > Help PF1 Back PF3

    > 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
    > K-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 *-ACCEL ACTIVITY
    ===============================================================================
    > THREAD ACCELERATOR DETAIL
    PLAN
    + Thread: Plan=WAYNEPLN Connid=RRSAF Corrid=W031008CF728 Authid=WDRI
    + Attach: RRSAF JOB Name=WDRIRLTB JOB Asid= 49
    + Package: INDI5 Collection=WEDLOCKCOL
    + Dist : Type=DISTRIBUTED ALLIED, Luwid=DEIBMIPS.IPSASA31.CB1D1F55BB7C=29255
    + Location : VMNPS52
    acel
    + Accelerator Data for this thread follows
    + Number of accelerators accessed: 1
    +
    + Name:VMNPS52
    + CPU Times Elapsed Times
    + ------------- -------------
    + In DB2 00:00:00.014 00:00:14.179
    + Accelerator 00:00:00.002 00:00:13.927
    + Accumulated wait 00:00:00.000
    + Counters
    + --------
    + Connects: 2 Requests: 4
    + Timeouts: 0 Failures: 0
    +
    + Data Transfer
    + -------------
    + Sent Received
    + -------- --------
    + Bytes: 6242 3679800
    + Messages: 22 24
    + Blocks: 0 2
    + Rows: 0 10104
    ===============================================================================
  • In the panel Resource Managers and Other DB2 Subsystem Information (ZRMMENU), the new option "N" - ACCELERATOR is available. You can display a list of the available accelerators by selecting option N. You can sort the list of accelerators by each of the fields.

    ________________ ZRMMENU VTM O2 V511./C DA31 03/28/13 16:18:06 2
    > Help PF1 Back PF3
    > R.

    > Enter a selection letter on the top line.
    ===============================================================================
    > RESOURCE MANAGERS AND OTHER DB2 SUBSYSTEM INFORMATION

    _ A BUFFER MANAGER ......... Buffer Manager Information
    _ B LOG MANAGER ............ DB2 Log Manager Information
    _ C EDM POOL ............... EDM Pool Information
    _ D BIND STATISTICS ........ Bind Statistics
    _ E SUBSYSTEM MANAGER ...... DB2 Subsystem Support Manager Statistics
    _ F ACTIVE TRACES .......... Current Trace Activity
    _ G START-UP OPTIONS........ IRLM and Stored Procedures Start-Up Options
    _ H DSNZPARM ............... DB2 Installation Parameters
    _ I LOCK/CLAIM/DRAIN........ Lock Manager/Claim/Drain Statistics
    _ J SQL/RID POOL/PARALLEL... SQL/RID Pool/Parallelism/Stored Proc. Information
    _ K OPEN/CLOSE STATISTICS... Dataset Open and Close Statistics
    _ L DB2 COMMANDS ........... DB2 Command Statistics
    _ M DB2 Storage ........... Storage Management Pool Summary
    _ N ACCELERATOR ............ Accelerator Information

    ===============================================================================
  • The panel Accelerator Summary (ZACST) shows a list of acclerators that are available in the current DB2 subsystem. By zooming into an individual accelerator, the panel Accelerator Statistics Detail (ZACSD) is displayed. It shows detailed statistics information about the selected accelerator.

    ________________ ZACST VTM O2 V511./C DA31 03/25/13 16:47:55 2
    > Help PF1 Back PF3 Up PF7 Down PF8 Sort PF10 Zoom PF11
    ===============================================================================
    > Accelerator Summary

    ACST
    + Number of accelerators defined: 2
    +
    +
    + Name State Requests Active Max Actv
    + -------- -------- -------- -------- --------
    + VMNPS52 ONLINE 59 0 4
    + VMNPS54 ONLINE 0 0 1

__________________________________________________________________________________

Update 8 - PM81181 - (March 2013) For redirecting the monitoring to another DB2, the new status "Unsupported" is added.

In Chapter 3. Summary, subchapter "Redirect Monitoring to Another DB2", the new status "Unsupported" is added to the list of statuses.

Unsupported
DB2 lower than version 8 or higher than version 10 is not supported.

__________________________________________________________________________________


Update 7 - PM72933 - (Januar 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 6 - PM75968 - (November 2012) - The panel and field description of the following chapter and section is updated:

- Chapter 6. Locking Conflicts, "Locking Conflicts panel"
Chap6_Locking Conflicts panel.pdf


__________________________________________________________________________________

Update 5 - PM71108 - (November 2012) - The field description of the following chapters is updated. New fields are added and existing fields are removed or updated:

- Chapter 5. Thread Activity, "Threads Summary Excluding Idle Threads", "Current SQL Counts"
Chap5_Current SQL Counts.pdf


- Chapter 5. Thread Activity, "Threads Summary Excluding Idle Threads", "Distributed Thread Detail (VTAM and TCP/IP Connections)"

The following fields are only supported for DB2 V8 and 9:
Block Mode Switches
The number of times a switch was made from continuous block mode to limited block mode. (Supported for DB2 version 8 and 9).
Message Buffer Rows
The number of rows in the message buffer if block fetch is being used. (Supported for DB2 version 8 and 9).
Bind Remote Access
The number of SQL statements that were bound for remote access. (Supported for DB2 version 8 and 9).


- Chapter 7. Resource Managers and Other DB2 Subsystem Information, "Buffer Manager Information"

Field description of HP Size is removed from the description.


- Chapter 7. Resource Managers and Other DB2 Subsystem Information, "Buffer Pool Detail"
The following field is only supported for DB2 version 9 and above:
Getpage Failed - Cond SeqReq
The number of conditional sequential getpage requests which failed because the page is not in the buffer pool. (Supported for DB2 9 and above.)

The following field is only supported for DB2 version 8:
Write Engine Not Available
The number of Writes that were deferred because DB2 reached its maximum number of concurrent Writes. (Supported for DB2 version 8.)


- Chapter 7. Resource Managers and Other DB2 Subsystem Information, "Group Buffer Pool Detail"
Chap7_Group Buffer Pool Detail.pdf


- Chapter 7. Resource Managers and Other DB2 Subsystem Information, "EDM Pool Information"

The following field is only supported for DB2 version 8:
Failures due to EDM Pool Full
Failures that occurred because the EDM pool was full. (Supported for DB2 version 8.)

The following fields are only supported for DB2 version 9 and above:
Failures due to RDS Pool Full
Failures that occurred because the RDS pool was full. (Supported for DB2 version 9 and above.)
Failures due to SKEL Pool Full
Failures that occurred because the SKEL pool was full. (Supported for DB2 version 9 and above.)
Number of Statements
The number of statements in the EDM pool. (Supported for DB2 version 9 and above.)


- Chapter 7. Resource Managers and Other DB2 Subsystem Information, "SQL/RID Pool/Parallelism/Stored Procedure Information"

The following fields have been renamed:
Planned Degree Executed-> Planned Degree Count
Number of parallel groups that were executed at the planned parallel degree.
Reduced Degree Executed-> Reduced Degree Count
Number of parallel groups that were processed to a degree less than the planned degree because of a storage shortage or buffer pool contention.

The following field is only supported for DB2 V8 and 9:
Seq (No ESA Enclave)
Number of parallel groups that were executed in sequential mode because MVS/ESA enclave services were unavailable. (Supported for DB2 version 8 and 9.)


- Chapter 9. Distributed Data Facility, "Distributed Data Facility Statistics"

The following fields are only supported for DB2 V8 and 9:
Binds for Remote Access
The number of SQL statements bound for remote access. (Supported for DB2 version 8 and 9.)
Message Buffer Rows
The number of rows in the message buffer block if block fetch is being used. (Supported for DB2 version 8 and 9.)
Block Mode Switches
The number of times a switch was made from continuous block mode to limited block mode. (Supported for DB2 version 8 and 9.)


- Chapter 15. Near-term history information, "Buffer Pool Statistics Summary by Report Interval" ,"Buffer Pool Statistics Detail"

The following field is only supported for DB2 version 9 and above:
Getpage Failed - Cond SeqReq
The number of conditional sequential getpage requests that failed because the page is not in the buffer pool. (Supported for DB2 version 9 and above.)

The following field is only supported for DB2 V8:
Write Engine Not Available
Writes that were deferred because DB2 reached its maximum number of concurrent Writes. (Supported for DB2 version 8.)


- Chapter 15. Near-term history information, "Distributed Data Facility Statistics Summary by Report Interval" ,"Distributed Data Facility Statistics Detail"

The following fields are only supported for DB2 V8 and 9:
Binds for Remote Access
Number of SQL statements bound for remote access. (Supported for DB2 version 8 and 9.)
Message Buffer Rows
Number of rows in the message buffer if block fetch is being used. (Supported for DB2 version 8 and 9.)
Block Mode Switches
Number of times a switch was made from continuous block mode to limited block mode. (Supported for DB2 version 8 and 9.)


- Chapter 15. Near-term history information, "Group Buffer Pool Statistics Summary by Report Interval" ,"Group Buffer Pool Statistics Detail"
Chap15_Group Buffer Pool Statistics Detail.pdf


- Chapter 15. Near-term history information, "EDM Pool Statistics Summary by Report Interval" ,"EDM Pool Statistics Detail"
Chap15_EDM Pool Statistics Detail.pdfChap15_EDM Pool Statistics Detail.pdf


- Chapter 15. Near-term history information, "SQL Statistics Summary by Report Interval" ,"SQL/RID Pool/I/O Parallelism Statistics Detail"

The following fields have been renamed:
Planned Degree Executed-> Planned Degree Count
Number of parallel groups that were executed at the planned parallel degree.
Reduced Degree Executed-> Reduced Degree Count
Number of parallel groups that were processed to a degree less than the planned degree because of a storage shortage or buffer pool contention.

The following field is only supported for DB2 V8 and 9:
Seq (No ESA Enclave)
Number of parallel groups that were executed in sequential mode because MVS/ESA enclave services were unavailable. (Supported for DB2 version 8 and 9.)


- Chapter 15. Near-term history information, "Thread History Distributed Activity"

The following fields are only supported for DB2 V8 and 9:
Block Mode Switches
The number of times a switch was made from continuous block mode to limited block mode. (Supported for DB2 version 8 and 9.)
Message Buffer Rows
The number of rows in the message buffer if block fetch is being used. (Supported for DB2 version 8 and 9.)
Bind Remote Access
The number of SQL statements bound for remote access. (Supported for DB2 version 8 and 9.)


- Chapter 15. Near-term history information, "Thread History SQL Counts"
Chap15_Thread History SQL Counts.pdf



__________________________________________________________________________________



Update 4 - 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 3 - PM68650 - (November 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), Chapter 15. Near-term History information, and Chapter 19. Lock Types and lock levels.


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 2 - (October 2012) - Updates in Chapter 5. Thread Activity, Chapter 6, Locking Conflicts, and Chapter 15, Near-term history information in PM66 261.

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, 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
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 1 - (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.

Publication number

SH12-6966-00

Copyright date

2005, 2012

Original publication date

2012/6/15

Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 Tools for z/OS

Software version:

5.1.1

Operating system(s):

z/OS

Reference #:

7036049

Modified date:

2014-01-21

Translate my page

Machine Translation

Content navigation