IMS Thread Summary
This panel provides an overview of DB2 thread activity originating from connected IMS subsystems.
It provides information about a connection level about all IMS subsystems identified to Db2. This panel also presents information about individual IMS threads (such as thread elapsed time, Db2 and MVS resource consumption, and DB2 activity).
________________ ZIMST VTM O2 V540.#P SN11 S 11/05/13 12:35:16 2
> Help PF1 Back PF3 Up PF7 Down PF8 Sort PF10 Zoom PF11
> T.D
> Thread Activity: Enter a selection letter on the top line.
> A-All-Idle B-TSO C-CICS *-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
===============================================================================
> IMS Thread Summary
IMSA
+ IMS ID CPU% Connection Threads
+ -------- ---- ---------- -------
+ MA41 00.0 2 1
THDI
+ *
+ Elapsed Planname Jobid CPU Status GetPg Update Commit Connid
+ ---------- -------- -------- ---- ------------ ----- ------ ------ --------
+ 00:00:07.5 DSN8IP0 IMSA41M1 00.0 WAIT-LOCK 12 0 0 MA41
===============================================================================
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).The following IMS releases are supported:
- IMS V10
- IMS V11
- IMS V12
- IMS V13
- IMS V14
- IMS V15
- a particular thread, move the cursor to the thread 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
IMS connection information:
- IMS ID
- The name of the IMS subsystem connected to Db2. If the IMS subsystem is DL/I batch, OMEGAMON® XE for DB2 PE displays the characters DLIBATCH.
- CPU%
- The total CPU rate (percent) of IMS regions within the IMS subsystem that have active threads to DB2.
- Connection
- The total number of regions from the IMS subsystem connected to Db2 (dependent and control).
- Threads
- The total number of threads connected from the IMS subsystem.
IMS 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 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.
Because SQL calls might be interspersed with IMS DLI calls and other activity, this wall clock time value need not solely reflect Db2 processing.
- 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.
- Jobid
- The name of the dependent or control region in which the thread is active.
- CPU (if monitoring a Db2 subsystem or data sharing group member)
- The current CPU rate (percent) of the IMS
region in which the thread is active.
This might include non-DB2 TCB activity.
- 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 MODE is MULT is specified on the IMS TRANSACT macro which defines the transaction or a WFI region is used, multiple messages might be processed before a commit point is reached, and page locks and DEALLOCATE(COMMIT) tablespace and SKCT locks are released.
- Connid
- The Db2 connection identifier of the active thread. The connection ID is the same as the IMS ID. It is used to relate an individual thread to the IMS system specified by the IMS ID under IMS Connection Information above.