Threads Summary Excluding Idle Threads
This panel shows an overview of the activity of all active threads (excluding idle threads) that are connected to DB2.
________________ ZALLT VTM O2 V540.#P DC11 S 07/01/16 14:22:24 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
+ ---------- -------- ----- ------------ ------ ------ ------ ------------
+ 08-04:12 KO2PLAN 00.0% NOT-IN-DB2 124 0 11 OMPEDA5S
+ 08-03:08 KO2PLAN 00.0% NOT-IN-DB2 0 0 0 OMPEDA5S
+ 07-13:35 KO2PLAN 00.0% NOT-IN-DB2 158 0 19 SZ91DM31
+ 07-13:34 KO2PLAN 00.0% NOT-IN-DB2 0 0 0 SZ91DM31
+ 00:00:57.2 KO2PLAN 00.0% IN-SQL-CALL 0 0 0 OMPEHZ7S
+ 00:00:57.1 KO2PLAN 00.0% NOT-IN-DB2 104 0 7 OMPEHZ7S
+ 00:00:56.8 KO2PLAN 00.0% NOT-IN-DB2 0 0 0 OMPEHZ8S
+ 00:00:56.7 KO2PLAN 00.0% NOT-IN-DB2 104 0 7 OMPEHZ8S
+ 00:00:54.8 KO2PLAN 00.0% NOT-IN-DB2 104 0 7 OMPEHZAS
+ 00:00:21.3 KO2PLAN 00.0% NOT-IN-DB2 0 0 0 OMPEHZ7S
+ 00:00:20.7 KO2PLAN 00.0% NOT-IN-DB2 0 0 0 OMPEHZ8S
=============================================================================== Each row provides information about an individual thread. Each column provides information about thread elapsed time, Db2 and MVS resource consumption, and DB2 activity.
Highlighting
The following table shows
the fields that might be highlighted in the panel above to indicate
that an exception that is related to this field exceeded its threshold
value:
| Field | Exception | Reason |
|---|---|---|
| Elapsed | ETIM | This thread has reached the Elapsed Time threshold value. |
| CPU | TCPU | The thread address space has excessive CPU utilization. |
| GetPg | GETP | The Getpage to Read I/O ratio indicates poor read efficiency. |
| Update | PGUP | The rate for system page updates is high. |
| Commit | COMT | The ratio of Commits to Updates indicates a low Commit frequency. |
Navigation
For additional
information about:
- the IMS connection, move the cursor to the IMS ID line and press F11 (Zoom). IMS releases V10, 11, 12, 13, 14, and 15 are supported.
- A particular thread, move the cursor to the thread information line and press F11 (Zoom). .
- Related topics, select one of the options on the top of the panel.
- Other topics, use the PF keys.
Fields
- 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 in parallel processing or if it invoked autonomous procedures, one of the following identifiers is displayed after the elapsed time:
- *
- This thread is a parallel task that is initiated on behalf of another (originating) thread to process a query request in parallel.
- O
- This thread is the originating thread that invoked autonomous procedures.
- P
- This thread is the parent or the originating thread of the parallel tasks that are created to process a query request in parallel. Activity performed for this (originating) thread is reflected under the parallel tasks.
- X
- This thread is a parallel task that is initiated on behalf of another (originating) thread on another DB2 for sysplex parallelism.
- Planname or Package
- The Db2 plan name (or package name) of the active thread. If you selected option T from the Realtime Main Menu, this panel shows the information by plan. If you selected option U, this panel shows the information by package.
- CPU (if monitoring a local DB2 subsystem, or data sharing group with XCF component activated for remote CPU)
- The CPU rate (percent) associated with the thread.
For non-CICS threads, this is the CPU rate of the address space from which the thread originates.
- Db2 (if monitoring a data sharing group or remote DB2 subsystem while XCF component is not activated for remote CPU)
- The Db2 subsystem name of the data sharing group member that is currently monitored.
- Status
- The current Db2 status of the thread.
- GetPg
- The number of thread Getpage requests. Getpage requests
are logical Read requests that might not actually result in physical
I/O if the requested page is currently in the buffer pool.
DB2 resets the Getpage count at Create Thread and Signon. If Signon is not driven, the Getpage count is cumulative.
- 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. DB2 resets the page update count at Create Thread and Signon. If Signon is not driven, the page update count is cumulative.
- Commit
- The number of times the thread successfully completed
Commit processing.
Db2 resets the Commit count at Create Thread and Signon. If Signon is not driven, the count is cumulative.
- CORRID/JOBN
- This field is customizable
by means of user mod TKANSAM(KO2MOD02) and shows
either:
- CORRID
- The correlation ID of the thread.
- JOBN
- The jobname of the thread.