Thread Lock/Claim/Drain Activity
This panel provides a summary of lock related activity for an individual thread.
________________ ZTLOCT VTM O2 V540.#P DA41 11/04/13 9:10:16 2
> Help PF1 Back PF3
> THREAD INFORMATION: Enter a selection letter on the top line.
> A-THREAD DETAIL *-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 W-ACCEL ACTIVITY
===============================================================================
> THREAD LOCK/CLAIM/DRAIN ACTIVITY
PLAN
+ Thread: Plan=ADB Connid=TSO Corrid=MIS Authid=MIS
+ Attach: TSO Userid=MIS Region asid= 224
+ Package: ADB2GET Collection=ADBL
+ Luwid=DEIBMIPS.IPSATA41.CC3659CD8774=796
loct
+ Lock Requests = 2 Deadlocks Detected = 0
+ Unlock Requests = 1 Timeouts Detected = 0
+ Query Requests = 0 Suspends - Lock Only = 0
+ Change Requests = 0 Suspends - Latch Only = 0
+ Other IRLM Requests = 0 Suspends - Other = 0
+ Escalations to Shared = 0 Escalations to Exclusive = 0
+ Maximum Page/Row Locks = 0
+
+ Claim Requests = 0 Claims Failed = 0
+ Drain Requests = 0 Drains Failed = 0
===============================================================================
Highlighting
OMEGAMON® XE for DB2 PE highlights some fields in this panel to
draw your attention to their current status:
Field | Exception | Reason |
---|---|---|
Plan | Any | Same as the other thread detail panels. |
Navigation
For additional information about
- related topics, select one of the options on the top of the panel.
- other topics, use the PF keys.
Fields
Thread identifier: This information identifies the thread to which
the information in this panel applies.
- Plan
- The Db2 plan name of the active thread.
- Connid
- The Db2 connection identifier of the active thread.
- Corrid
- The Db2 correlation identifier of the active thread. If the correlation is not set, N/A is displayed.
- Authid
- The Db2 authorization identifier of the active thread.
- Attach
- Depending on the type of connection, the appropriate information is displayed.
- 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.
- Entry
- 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.
- Db2
- The Db2 subsystem identifier.
- MVS
- The MVS system identifier.
- ORIGAUTH
- The original (primary) Db2 authorization identifier of the thread. This field displays only when the original identifier is different from the Authid.
Package identifier: This information identifies the package to
which the information in this panel applies.
Distributed thread identifier: The following
fields are displayed if the thread has a distributed relationship with a remote Db2 subsystem.
- Type
- The distributed thread type.
- Distributed Allied
- A requesting thread; one that has issued an SQL call to a remote Db2 location.
- Database Access
- A responding thread; one that is serving a remote Db2 location by responding to an SQL call.
- Db2=
- The Db2 subsystem ID, indicating the member of the data sharing group of this thread.
- Luwid
- This value consists of two parts: the logical unit of work ID (luw-id) and a
token. The token can be used in place of the luw-id in any Db2
command that accepts luw-id as input. Format:
luw-id=token
The luw-id consists of the network name, the originating VTAM® LUNAME, and a unique identifier (separated by periods). Thus, the Luwid field displays data like in the following example:
USCACO01.O2D22A.A1FE8E04B9D4=8
- 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.
Lock count information:
- Lock Requests
- Requests to Internal Resource Lock Manager (IRLM) to obtain a lock on a resource.
- Deadlocks Detected
- The number of deadlocks detected.
- Unlock Requests
- Requests to IRLM to unlock a resource.
- Timeouts Detected
- The number of times that the suspension of a unit of work lasted longer than the IRLM timeout value.
- Query Requests
- Requests to IRLM to query a lock.
- Suspends - Lock Only
- Suspensions of a unit of work because a lock could not be obtained.
- Change Requests
- Requests to IRLM to change a lock.
- Suspends - Latch Only
- Db2 internal latch suspensions.
- Other IRLM Requests
- Requests to IRLM to perform a function other than those listed before.
- Suspends - Other
- Suspensions caused by something other than locks and latches.
- Escalations to Shared
- Occasions when the allowable number of locks per tablespace was exceeded, causing a page (IS) lock to escalate to a shared (S) lock.
- Escalations to Exclusive
- Occasions when the allowable number of locks per tablespace was exceeded, causing a page (IX) lock to escalate to an exclusive (X) lock.
- Maximum Page/Row Locks
- The maximum number of page or row locks held concurrently. This count cannot exceed the value of the NUMLKUS (locks per user) installation parameter.
- Claim Requests
- The number of claim requests.
- Claims Failed
- The number of unsuccessful claim requests.
- Drain Requests
- The number of drain requests.
- Drains Failed
- The number of unsuccessful drain requests.