DB2 Thread Status Values

This topic contains a list of all possible values for the status of a DB2® thread. This field is displayed on thread summary and thread detail panels as Status, DB2 Status, or Thread Status.

The following list shows all possible values for the status of a DB2 thread:

NOT-AVAIL
The thread is not available
IN-ABORT
The thread is in abort processing.
IN-ACCEL
The thread is executing on IBM® DB2 Analytics Accelerator for z/OS®.
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 plan name.)
IN-COMMIT
The thread is in Commit processing (applies only to threads that originate from an attachment that does not use 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 call's request.
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 DB2 DISPLAY THREAD=D status.
IN-TRIGGER
The thread is currently running in a trigger.
IN-USER-FUNC
The thread is currently running a user-defined function.
NOT-IN-DB2
The thread is not currently executing in DB2.
SP/UDF-INACT
The thread is trying but not able to run in a stored procedure or user-defined function.
SWAPPED-OUT
The thread is not currently executing 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 being done under a thread other than this one (for example, sequential or List Prefetch).
WAIT-ASYNCWR
The thread is currently waiting for completion of Write I/O that is being done under a thread other than this one (for example, Deferred Writes).
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-GLBLOCK
The thread is currently waiting for either:
  • Inter-system communication within the data sharing group to determine if there is lock contention.
  • A lock held by another subsystem in the data sharing group.
WAIT-LOCK
The thread is waiting for a lock.
WAIT-MSGSEND
The thread is waiting because of inter-system message sending contention.
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 a dataset, DFHSM recall of a dataset, SYSLGRNG update or define/extend/delete of a dataset, rollback, and Commit phase 2 for read only threads.
WAIT-SP-STOP
The thread is queued waiting for a stopped stored procedure.
WAIT-TERM-TH
The thread is queued and waiting for thread termination as a result of allied task termination. This status corresponds to DB2 DISPLAY THREAD=QD status.
UTIL-STOP
The DB2 utility was started but not completed because of abnormal termination.

The following status are only available when class 2/3 traces are on:

Start of changeWAIT-ACCELEnd of change
Start of changeThe thread is currently waiting for claimers to be released after acquiring drain lock.End of change
WAIT-CLAIMER
The thread is currently waiting for claimers to be released after acquiring drain lock.
Start of changeWAIT-CL3LOCKEnd of change
Start of changeThe thread is currently waiting for the completion of an identify call to the IRLM.End of change
WAIT-COMMIT
The thread is waiting for the FORCE-AT-COMMIT event to finish.
WAIT-DRNLOCK
The thread is currently waiting to acquire drain lock.
Start of changeWAIT LOBEnd of change
Start of changeThe thread is currently waiting for TCP/IP to materialize a LOB.End of change
Start of changeWAIT-LOCKLATEnd of change
Start of changeThe thread is waiting for a LOCK-I/O-LATCH.End of change
Start of changeWAIT-LOCKPIPEnd of change
Start of changeThe thread is currently waiting for a PIPE suspend.End of change
Start of changeWAIT-LOCKPQSEnd of change
Start of changeThe thread is currently suspended for parallel task synchronization.End of change
WAIT-LOGQSCE
The thread is currently suspended because of an ARCHIVE LOG MODE(QUIESCE) command.
WAIT-PGLATCH
The thread is currently waiting for page latch.
Start of changeWAIT-SP-SCHDEnd of change
The thread is waiting for a TCB to become available in the stored procedures address space to schedule a stored procedure.
Start of changeWAIT-SWITCHEnd of change
Start of changeThe thread is currently waiting for the completion of a synchronous execution switch.End of change
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.


Feedback