Thread History Global Lock Activity

This panel provides information about global locking activity for an individual thread.

 
________________ ZHTGLOC  VTM     O2       V550.#P SE12 11/06/13 13:51:22   2 
> Help PF1               Back PF3               Up PF7                 Down PF8
                                                                               
>          THREAD HISTORY:  Enter a selection letter on the top line.          
                                                                               
> A-THREAD DETAIL   B-LOCK COUNTS  C-LOCK WAITS     *-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 GLOBAL LOCK 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                                         
 gloc                                                                          
+ P-lock Lock Requests        =     312  S Lock Requests           =     870
+ P-lock Unlock Requests      =      36  S Unlock Requests         =     347
+ P-lock Change Requests      =     145  S Change Requests         =     163
+ Suspends - IRLM Global Cont =       0   Total L-lock Requests       =    3290
+ Suspends -S Global Cont  =       0  S L-lock Req Percentage   =   34.4%
+ Suspends - False (and Conv) =     273   Incompatible Retained Locks =       0
+ Notify Messages Sent        =     103   Total Number False Content. =       0
===============================================================================

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.
Attach information is displayed only if the thread is a distributed allied thread (not for distributed database access threads).
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.
Time identifier:
Start
The start date and time of this thread execution.
End
The end date and time of this thread execution.
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.

Global lock information: