Thread History Lock/Claim/Drain Activity

This panel provides lock/claim/drain statistics such as the number of requests to acquire a lock and the number of pages that were locked for a thread.


________________ ZHTLOCT  VTM     O2       V540.#P SE12 11/06/13 13:46:21   2  
> Help PF1               Back PF3               Up PF7                 Down PF8 
                                                                                
>          THREAD HISTORY:  Enter a selection letter on the top line.           
                                                                                
> A-THREAD DETAIL   *-LOCK COUNTS  C-LOCK WAITS     D-GLOBAL LOCKS  E-SORT/SCAN 
> F-DYNAMIC SQL     G-SQL COUNTS   H-DISTRIBUTED    I-BUFFER POOL   J-GROUP BP  
> K-PACKAGE SUMMARY L-RES LIMIT    M-PARALLEL TASKS                             
=============================================================================== 
>                  THREAD HISTORY LOCK/CLAIM/DRAIN ACTIVITY                     
 HPLN                                                                           
+ Thread:  Plan=DSNESPCS  Connid=TSO      Corrid=MIS          Authid=MIS        
+ Attach:  TSO            DB2=SE12        MVS=PMO4                              
+ Time  :  Start=11/06/2013 13:30:02.142363     End=11/06/2013 13:31:39.784388  
+ Luwid=DEIBMIPS.IPSATE12.CC39197D8375                                          
 loct                                                                           
+ Lock Requests          =       1645   Deadlocks Detected         =          0 
+ Unlock Requests        =        636   Timeouts Detected          =          0 
+ Query Requests         =         72   Suspends - Lock Only       =          0 
+ Change Requests        =        272   Suspends - Latch Only      =          1 
+ Other IRLM Requests    =          0   Suspends - Other           =          0 
+ Escalations to Shared  =          0   Escalations to Exclusive   =          0 
+ Maximum Page/Row Locks =          6                                           
+                                                                               
+ Claim Requests         =        867   Claims Failed              =          0 
+ Drain Requests         =         18   Drains Failed              =          0 
===============================================================================

Navigation

For additional information about

related topics, choose on of the options at the top of the panel.
other topics, use the PF keys.

Fields

Thread Identifier:

Plan: The Db2 plan name of the thread.
Connid: The Db2 connection identifier of the thread.
Corrid: The Db2 correlation identifier of the thread.
Authid: The Db2 authorization identifier of the thread.

Attachment identifier:

Connection Type

The connection type is displayed in the first field:

APPLDIR: Application directed access (database 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
TSO: TSO foreground and background
Utility: Utility thread

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.

Distributed thread identifier: The following fields are displayed when 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 server thread; one that has received and is serving an SQL request from a remote Db2 location.

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 such as the following:


USCACO01.O2D22A.A1FE8E04B9D4=8

Time identifier:

Start: The start date and time of this thread execution.
End: The end date and time of this thread execution.

Lock/Claim/Drain:

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: Occasions when suspension of a unit of work lasted longer than the IRLM timeout value.
Query Requests: Requests to IRLM to query a lock.
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 above.
Suspends - Other: Suspensions caused by something other than locks and latches.
Lock 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.
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 locks held concurrently during the thread's execution. This count cannot exceed the value of the NUMLKUS (locks per user) installation parameter.

Claim/Drain information:

Claim Requests: The number of requests for a claim on a resource.
Claims Failed: The number of unsuccessful claim requests.
Drain Requests: The number of requests for a drain of claims.
Drains Failed: The number of unsuccessful drain requests.