Display thread -- Fields and controls
Active
Displays only active threads. This is the default. An active allied
thread is connected to DB2 via TSO, BATCH, IMS, CICS or CAF. An active database access thread is connected via VTAM to another system and is performing work on behalf of that system. If, during command processing, an active thread becomes indoubt, it can appear twice--once as active and once as indoubt.
The information produced by active threads can be useful for debugging purposes,
especially messages DSNV403I and DSNV404I.
Inactive
Displays only inactive threads. An inactive thread is a database access
thread that is connected via VTAM to another system and is idle, waiting for a new unit of work to begin
from that system.
Indoubt
Displays only indoubt threads. An indoubt thread is a participant in a
two-phase commit protocol that completed the first phase of commit,
and then lost communication with the commit coordinator, and does not
know whether to commit or roll back the updates that were made.
The indoubt thread information displayed includes threads for which
DB2 has a coordinator role, a participant role, or both coordinator and participant roles.
The commit coordinator for an allied thread is either a transaction
manager (for example, IMS or CICS) or OS/390 RRS for threads that use RRSAF.
The commit coordinator for a database access thread is a requester at a
remote system.
Indoubt threads hold locks on all resources that were updated.