TSO Thread Summary
This panel provides an overview of the activity of all foreground TSO threads connected to Db2.
Each row provides information about an individual thread, including information about thread response time, DB2 and MVS™ resource consumption, and Db2 activity.
________________ ZTSOT VTM O2 V550.#P DA41 S 11/05/13 12:13:55 2
> Help PF1 Back PF3 Up PF7 Down PF8 Sort PF10 Zoom PF11
> T.B
> Thread Activity: Enter a selection letter on the top line.
> A-All-Idle *-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
===============================================================================
> TSO Thread Summary
THDT
+ *
+ Elapsed Planname CPU Status GetPg Update Commit Userid
+ ---------- -------- ----- ------------ ------ ------ ------ --------
+ 00:10:17.2 ADB 00.0% SWAPPED-OUT 0 0 1 MIS
+ 00:10:06.0 DSNESPRR 00.0% SWAPPED-OUT 16 0 2 MIS
===============================================================================
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 number of updates since the last successful commit is high. |
Navigation
For additional
information about
- a particular thread, move the cursor to the thread information line and press F11 (Zoom).
- A different Db2 subsystem, data sharing group, or member of a data sharing group, enter the name of a Db2 subsystem, group, or member in the topmost row and press Enter.
- 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 a data sharing group with XCF component activated for remote CPU)
- The CPU rate (percent) that is associated with the thread. Database access threads run in MVS SRB mode. The displayed rate is SRB time (no TCB time).
- 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.
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. 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.
If a QMF thread user exits from a query panel to other than the home panel, tablespace locks defined with DEALLOCATE(COMMIT) will be retained until Commit is effected. This is also true of SPUFI users who do not specify AUTOCOMMIT, or who specify DEFER on completion of a transaction.
- Userid
- The TSO user ID of the active thread user.