DB2 thread identification

A thread executing in DB2® on behalf of a CICS® transaction is identified by its correlation ID set by the CICS DB2 Attachment Facility. DB2 allows up to 12 bytes to be used for the correlation ID. In releases of CICS before CICS Transaction Server for OS/390®, Version 1 Release 2, only 8 bytes were used.

The format 12 byte correlation ID is made up as as eeeettttnnnn where eeee is either COMD, POOL or ENTR indicating whether it is a command, pool or DB2ENTRY thread; tttt is the transid, and nnnn is a unique number.

Note:
A correlation ID passed to DB2 can be changed only by the CICS Attachment Facility issuing a signon to DB2. If signon reuse occurs by a thread using a primary authorization ID which remains constant across multiple transactions (for example, by using AUTHID(name)) only one signon will occur. In this instance the tttt in the correlation ID does not match the running transaction ID. It is the ID of the transaction for which the initial signon occurred.

Related concepts
Problem determination for CICS DB2
Thread TCBs (task control blocks)
Wait types for CICS DB2
Messages for CICS DB2
Trace for CICS DB2
Dump for CICS DB2
Transaction abend codes for CICS DB2
Execution Diagnostic Facility (EDF) for CICS DB2
Handling deadlocks in the CICS DB2 environment
[[ Contents Previous Page | Next Page Index ]]