DB2 Lock Conflict Attributes
Use DB2 Lock Conflict Group attributes to create situations that monitor DB2 database lock conflicts.
Authorization ID The primary authorization ID from connection or sign-on, that identifies the execution privileges an application has to a DB2 object or service. Valid format is alphanumeric with a maximum of 8 characters; for example, TRAN5.
Authorization ID (Unicode) The primary authorization ID from connection or sign-on, that identifies the execution privileges an application has to a DB2 object or service. Valid format is alphanumeric with a maximum of 8 characters; for example, TRAN5.
Begin Time Beginning store clock value (STCK) for the period covered by this accounting record. You can determine the elapsed time of the application by subtracting this field from QWACESC (ending store clock value). Threads that do not terminate (such as CICS primed threads and ims wait-for-input message regions) can have an ending clock value that includes the time the thread was inactive and waiting to perform work.
DB2 Lock Conflict Attributes Identifies the connection of an application to a DB2 system.
Value | Description |
---|---|
BATCH | Batch job |
CICS | CICS attach |
DB2CALL | DB2 call facility |
DIST | Distributed |
IMS | IMS thread |
TSO/E | TSO/E foreground and background |
UTILITY | DB2 utility |
Connection Type The type of DB2 connection.
Value | Description |
---|---|
APPLCTN | Application directed access |
BATCH | Batch job |
CICS | CICS attach |
DB2CAF | DB2 call attach |
DLIBATCH | DL/I Batch |
IMS | IMS thread |
IMS BMP | IMS attach BMP |
IMS TBMP | IMS transaction BMP |
IMS CTL | IMS control region |
IMS MPP | IMS attach MPP |
SYSTEM | System directed access |
TSO/E | TSO/E foreground and background |
UNKNOWN | Unrecognizable connection type |
UTILITY | DB2 utility |
Correlation ID The correlation between an application and the connection to a DB2 system. Valid format is alphanumeric, with a maximum of 12 characters; for example, DLKEX212.
DB2 ID The name of a DB2 subsystem.
Display Elapsed Time The total amount of elapsed time since thread creation or DB2 sign-on.
IDNAME An internal attribute used for navigation, it contains either the Data Sharing Group Name or the DB2ID.
Valid format is alphanumeric with a maximum of 8 characters; for example TDDB242G.
Lock Elapsed Time The amount of time (in seconds) a waiter has been waiting for the resource.
Lock Level Identifies the lock resource usage.
Value | Description |
---|---|
IS | Intent share |
IX | Intent exclusive |
NSU | Non-shared Update |
S | Share |
SIX | Share intent exclusive |
U | Update |
UNS | Unprotected shared |
X | Exclusive |
Lock Resource The resource a lock owner currently has locked or the resource that caused DB2 to suspend a lock request. Valid format is alphanumeric, with a maximum of 50 characters; for example, DB=TBLBLK2 PS=PAGELK2.
Lock Status The status of a job holding or waiting on a lock: If the status is OWN with a DB2 subsystem name, the lock is owned by another DB2 subsystem in the Data Sharing Group (DSG); for example, if lock status is OWN-DB2A, the lock is owned by DB2 subsystem DB2A.
Lock Token Lock Token.
Lock Type The lock type of the lock request.
Lock type | Description |
---|---|
ACSC | The Accelerator Services commands (ACSC) lock. |
ALBP | The Alter buffer pool (ALBP) lock indicates a lock on a buffer pool during execution of an ALTER BUFFERPOOL command. |
BIND | The BIND lock indicates an autobind or remote bind lock. |
BMBA | The Buffer manager SCA MBA (BMBA) L-lock. The Buffer Manager (BM) gets this lock when it needs to read, insert, or update a multiple buffer pool (MBA) record in a Shared Communications Area (SCA). (BMC_MBAO or BMC_MBAR) |
BPPS | The Buffer Manager Pageset (BPPS) RR (repeatable
read) P-lock:
|
CCAT | The CATMAINT convert catalog (CCAT) lock is acquired when catalog conversion is performed. |
CDBL | The Compress dictionary build (CDBL) lock. |
CDIR | The CATMAINT convert directory (CDIR) lock is acquired when directory conversion is performed. |
CDRN | The Cursor Stability drain (CDRN) lock is acquired to drain
all CS read access to an object:
|
CMDS | The DB2® Command Serialization (CMDS) lock. |
CMIG | The CATMAINT migration (CMIG) lock is acquired when catalog migration is performed. |
COLL | The Collection (COLL) lock |
DBDL | The DBD load (DBDL) lock is the database descriptor load lock. |
DBEX | The Database exception (DBEX) lock indicates a lock on a "Logical
page list" (LPL) or "Group buffer pool recovery pending" (GRECP) database
exception status. This lock is only used in a data sharing environment. |
DBXU | The DB exception update lock is used for updating the database exception status. |
DGTT | The DGTT URID lock is acquired to protect segments that belong to a Declared Global Temporary Table (DGTT). These segments are deallocated during Commit 1 by logging them and serializing them using the Unit of Recovery ID (URID) lock. |
DPAG | The DB2 page (DPAG) lock
in a tablespace. When programs read data or update data, they acquire
a page lock containing the data.
|
DSET | The partitioned lock. A partitioned tablespace contains one or more partitions (up to 64). It is created when you create a table space using the SQL CREATE TABLESPACE statement with the NUMPARTS parameter. Only one table can be stored on a partitioned tablespace. Each partition contains one part of a table. The partitioned lock only locks the partition with the data that is referenced.
|
DTBS | The Database lock indicates a lock on the database.
|
GRBP | The Group buffer pool (GRBP) start/stop lock. BP=buffer pool ID |
HASH | The Hash anchor (HASH) lock.
|
HPSP | The Header Page (HP) Bucket or Stored Procedure (SP) Command lock. |
IEOF | The Index end of file (IEOF) lock is acquired at the index
end of file.
|
IPAG | The Index page (IPAG) lock in an index space. When application
programs read or update data, they acquire a lock on the page containing
the index when indexing is used.
|
IXKY | The Index key (IXKY) lock. |
LBLK | The Large object (LOB) lock. |
LPLR | The Logical page list recovery (LPLR) lock. |
MDEL | The Mass delete (MDEL) lock is acquired when doing a mass delete
from a table (for example, when you DELETE FROM a table) within a
segmented tablespace. It is used to prevent another user from reusing freed segments before a delete operation is committed.
|
PALK | The Partition lock.
|
PBPC | The Group BP level castout (PBPC) P-lock. A physical lock acquired when a castout of a group buffer pool occurs. Castout is the process of writing pages in the group buffer pool out to DASD. This lock is only used in a data sharing environment. |
PCDB | The DDF CDB P-lock. A Distributed Data Facility communication database physical lock. This lock is only used in a data sharing environment. |
PDBD | The DBD P-lock is a database descriptor physical lock. This lock is only used in a data sharing environment. |
PDSO | The Pageset or partitioned pageset open lock. If the data set supporting the tablespace that is referenced by the application is not opened, the program will acquire a lock to open the data set. The data set will stay open if CLOSE=NO is defined in the SQL statement creating the tablespace.
|
PITR | The Index manager tree (PITR) is a physical lock (P-lock). This lock is only used in a data sharing environment.
|
PPAG | The Page P-lock is a physical lock on a page. This lock is only used in a data sharing environment. |
PPSC | The Pageset/partition level castout physical lock (P-lock). This lock is only used in a data sharing environment. |
PPSP | The Pageset/partition physical lock (P-lock). This lock is only used in a data sharing environment. |
PRLF | The Resource Limit Facility (RLF) physical lock (P-lock). This lock is only used in a data sharing environment. |
PSET | The Pageset (PSET) lock can be a tablespace or indexspace. A pageset containing DB2 tables is a tablespace. A pageset containing DB2 index structure is an indexspace. A pageset can be simple or partitioned. This lock type is for the simple pageset only.
|
PSPI | The Pageset piece (PSPI) lock. A pageset is a collection of pageset pieces. Each pageset piece is a separate VSAM data set. A simple pageset contains from 1 to 32 pieces. Each piece of a simple pageset is limited to 2 GB. Whenever a simple pageset piece reaches this size, another piece is allocated and the pageset grows. This is a lock on the expanded pageset piece. |
RDBD | The Repair DBD (RDBD) lock is acquired when REPAIR DBD REBUILD is running (test/ diagnose). |
RDRN | The Repeatable Read drain (RDRN) lock is acquired to drain
all RR access to an object.
|
RGDA | The Retry Getpage During Abort (RGDA) lock. |
ROW | The Row lock indicates a lock on a row. |
RSTR | The Shared Communications Area (SCA) restart (RSTR) lock indicates
a lock on SCA access for restart/redo information. (BMC-RSTP) |
SDBA | The Start/stop lock on DBA (SDBA) table indicates a lock on
the table, tablespace, or database when a CREATE/DROP is processed
against these objects.
|
SENV | The System environment (SYSENV) serialization lock. |
SKCT | The Skeleton cursor table (SKCT) lock indicates a lock on the
application plan. PLAN=plan name |
SKPT | The Skeleton package table (SKPT) lock indicates a lock on the application package. |
SPRC | The System level point in time (PIT) recovery
lock. SYS_PITR |
SREC | The Log range lock. DB2 writes a record in the log range tablespace (SYSLGRNG) every time a tablespace is opened and updated, and updates SYSLGRNG whenever that tablespace is closed. The record contains the opening and/or closing log RBA (relative byte address) for the tablespace. When DB2 writes to SYSLGRNG, the program acquires a lock on the tablespace with updates.
|
TABL | The Table (TABL) lock on the table which resides in a segmented
tablespace.
|
UIDA | The Util I/O Damage Assessment lock. |
UNDT | The Undetermined (UNDT) lock indicates that this lock cannot
be determined because it is not part of the other listed lock types. Resource ID (in hexadecimal). |
UNKN | The Unknown (UNKN) lock indicates the resource does not exist. |
UTEX | The Utility exclusive execution (UTEX) lock. UTEXEC |
UTID | The Utility identifier (UTID) lock. UID=utility id |
UTOB | The Utility object (UTOB) lock.
|
UTSE | The Utility serialization (UTSE) lock is required when running
utility jobs. UTSERIAL |
WDRN | The Write drain (WDRN) lock is acquired to drain all write
access to an object.
|
XMLK | The XML lock. |
LUWID The logical unit of work ID (LUWID) for a thread.
MVS System An ID for the MVS System Management Facility (SMF). Valid format is alphanumeric with a maximum of 4 characters; for example SP11.
Originating System ID The managed system name of the agent. Valid format is alphanumeric, with a maximum of 32 characters; for example, DB91:SYS1:DB2.
Plan Name The name of an application plan that DB2 produces during the bind process and uses for processing SQL statements during execution. Valid format is alphanumeric with a maximum of 8 characters. For example PLANLCK2 is the name of an application plan. *SYSTEM* indicates DB2 subsystem-generated threads that own or are waiting on a lock.
Resource Name 1 (Unicode) The resource name of type defined by type code.
Resource Name 2 (Unicode) The resource name of type defined by type code.
Resource Name 3 The resource name of type defined by type code.
Resource Name 4 The resource name of type defined by type code.
Resource Type 1 This value indicates what is contained in Resource Name 1.
Value | Description |
---|---|
BP | Buffer Pool |
CO | Collection name |
DB Hash | Database |
HC | Class |
PL | Plan name |
UT | Utility ID |
Resource Type 2 This value indicates what is contained in Resource Name 2.
Value | Description |
---|---|
PK | Package |
PS | Page Set (Table space) |
Resource Type 3 This value indicates what is contained in Resource Name 3.
Resource Type 4 This value indicates what is contained in Resource Name 4.
Value | Description |
---|---|
PT | Partition |
SUBSYS The IRLM subsystem name.
Thread Status The current status of a thread.
- Status
- Description
- IN-ABORT
- The thread is in abort processing.
- IN-ACCEL
- The thread is executing in accelerator.
- IN-AUTO-PROC
- The thread is processing an autonomous procedure.
- IN-BIND-DYNM
- The thread is in dynamic bind processing.
- IN-BIND-STAT
- The thread is in static bind processing.
- IN-COMMAND
- Command threads display this status when they are active in DB2 and executing within the DB2 command processor. (This type of thread always has a blank.)
- IN-COMMIT
- The thread is in commit processing. It applies only to threads that originate from an attachment that does not use a two-phase commit protocol.
- IN-COMT-PHS1
- The thread is in commit phase 1 processing.
- IN-COMT-PHS2
- The thread is in commit phase 2 processing.
- IN-CRTE-THRD
- The thread is in create thread processing.
- IN-DB2
- The thread is executing in DB2. A more descriptive status could not be determined.
- INDOUBT
- The thread is in doubt.
- IN-SIGNON
- The thread is in signon processing. This status applies only to threads originating from CICS or IMS attachments.
- IN-SQL-CALL
- The thread is processing an SQL call.
- IN-SQL-SORT
- The thread is executing an SQL call and is doing the sort processing required to satisfy the request of the call.
- IN-STOR-PROC
- The thread is currently running in a stored procedure.
- IN-TERM-THRD
- The thread is in termination as a result of allied task termination. This status corresponds to the DB2 DISPLAY THREAD=D.
- IN-TRIGGER
- The thread is currently running in a trigger.
- IN-USER-FUNC
- The thread is currently running a user-defined function.
- NOT-AVAIL
- The thread is not available
- NOT-IN-DB2
- The thread is currently not running in DB2.
- SP/UDF-INACT
- The thread is trying to but cannot run in a stored procedure or user-defined function.
- SWAPPED-OUT
- The thread is currently not running in DB2. The thread originating address space is swapped out.
- WAIT-ARCHIVE
- The thread is waiting for an archive log tape mount necessary during thread abort processing.
- WAIT-ARCREAD
- The thread is currently waiting for read of archive log from tape.
- WAIT-ASYNCRD
- The thread is currently waiting for completion of a read I/O that is done under a thread other than this one (such as sequential or list prefetch).
- WAIT-ASYNCWR
- The thread is currently waiting for completion of write I/O that is done under a thread other than this one (such as deferred writes).
- WAIT-CLAIMER
- The thread is currently waiting for claimers to be released after acquiring DRAIN lock.
- WAIT-CONVLIM
- The distributed thread is in a synchronous wait because the conversation limit has been reached for its designated logmode.
- WAIT-CTHREAD
- The thread is queued in create thread processing because DB2 reached the CTHREAD value. This status corresponds to DB2 DISPLAY THREAD=QD status.
- WAIT-DRNLOCK
- The thread is currently waiting to acquire DRAIN lock.
- WAIT-GLBLOCK
- The thread is currently waiting for one of the following:
- A lock held by another subsystem in the data sharing group.
- intersystem communication within the data sharing group to determine if there is lock contention.
- WAIT-LOCK
- The thread is waiting for a lock
- WAIT-LOGQSCE
- The thread is currently suspended because of an ARCHIVE LOG MODE(QUIESCE) command.
- WAIT-MSGSEND
- The thread is currently waiting because of intersystem message sending contention.
- WAIT-PGLATCH
- The thread is currently waiting for page latch.
- WAIT-REMREQ
- The database access thread is in a synchronous wait (waiting for a response or a request from the originating DB2 subsystem).
- WAIT-REMSQL
- The distributed allied thread is in a synchronous wait (waiting for a response from the remote DB2 subsystem being accessed).
- WAIT-REUSE
- The thread is not currently in use and is waiting to be reused. This status applies only to CICS and IMS threads.
- WAIT-SERVICE
- The thread is currently waiting for completion of a DB2 service. Types of DB2 services include open/close of data set, DFHSM recall of a data set, SYSLGRNG update, or define/extend/delete of a data set, rollback, and commit phase 2 for read only threads.
- WAIT-SP-STOP
- The thread is queued waiting for a stopped stored procedure.
- WAIT-SPSCHD
- The thread is waiting for a TCB to become available in the stored procedures address space to schedule a stored procedure.
- WAIT-SYNC-IO
- The thread is currently waiting for completion of a synchronous
Read I/O or Write I/O. Note: This status can indicate that a DB2 resource is not large enough. You can use the OMEGAMON XE for DB2 PE resource manager or object analysis displays to further isolate the problem.
- WAIT-TERM-TH
- The thread is queued and waiting for thread termination as a result of allied task termination. This status corresponds to the DB2 DISPLAY THREAD=QD status.
- UTIL-STOP
- The DB2 utility was started but not completed because of abnormal termination.
Thread Token The thread token uniquely identifies a specific thread.
Thread Type The type of thread.
Type | Description |
---|---|
A-LIST | Allied-distributed thread starts at one server location; processes at another. |
ALLIED | Thread starts and processes at one server location. |
DBACCESS | Database access thread, requested by an allied-distributed thread. |
UNKNOWN | Unknown. |
Time Stamp Represents the end of data collection or the end of an interval, and is the local time where the system is running.
- M = Month
- D = Day
- Y = Year
- H = Hour
- M = Minute
- S = Second
Uniqueness Value The instance number: When concatenated with the fully qualified network name, it uniquely identifies a distributed thread (DB2 field name: QWHSLUUV).
Uniqueness Value2 The instance number: When concatenated with the fully qualified network name, it uniquely identifies a distributed thread (DB2 field name: the last 2 bytes of QWHSLUUV).