Display thread output

These steps are part of the larger task of displaying threads. When you complete the steps for displaying threads, return to the main task.

Use the Display Thread output window to view the current status of one or more threads, as specified in the Display Thread window.

To view and manipulate threads:

  1. Click the Refresh push button to ensure you are viewing the most recent status.

  2. From the Active and inactive threads table you can right-click on a selected thread and select additional tasks from the pop-up menu:

  3. From the Indoubt threads table (or for versions later than Version 5 the Postponed and Indoubt threads) you can right-click on a selected thread and select an appropriate utility:

  4. Click Close to close the window.

Related information

About the display:

If you selected to view all threads in the Display Thread window, the display thread output is divided into two tables. The top of the window shows the active and inactive threads by Token. The bottom half of the window shows the indoubt and for versions of DB2 for OS/390 later than Version 5, it shows postponed threads by Authorization identifier. The output actually appears as a series of DSNV... messages.

A status area at the bottom of the window contains informational messages relating to your thread output. If, for example, you wanted to view the indoubt threads, you see the following message if there are no existing indoubt threads: 

DSNV420I - subsystem name NO INDOUBT THREADS FOUND
Information that is returned in this output area reflects a dynamic status. When the information is displayed, it is possible that the status has changed. The information is consistent only within one address space and is not necessarily consistent across all address spaces displayed.

For active and inactive threads, the columns of the report are:

Token
A 1- to 5-character number representing the thread token assigned by DB2 to the thread. For threads with a status value of N, this value is 0.
Auth id
The authorization ID associated with a signed-on connection. If not signed-on, this column is blank.
State
The thread state is active or inactive for this table.
Name
A 1- to 8-character variable representing the connection name used to establish the thread. For threads using application-directed access from a non-DB2 requester, the name is the constant SERVER. Name can be blank if the thread of the originating task is running on the same DB2.
Status
A 1- or 2-character connection status code with the following values:

D
Thread is in the process of termination.
DI
Thread is disconnected from an execution unit; no TCB is associated with the DB2 thread (valid only when 'connection name'=RRSAF).
N
Thread is in either IDENTIFY or SIGNON status.
PT
Parallel task thread established.
QD
Thread is queued for termination.
QT
CREATE THREAD request queued.
RA
Distributed thread is performing a remote access on behalf of a request from another location.
RD
Distributed thread is performing a remote access on behalf of a request from another location; thread is performing an operation that invoked DCE services.
RN
Distributed thread is performing a remote access on behalf of a request from another location. The request accesses data at another (DB2) location, so the thread was suspended because DB2 must first connect to the partner location (establish DB2 system conversations with the partner).
RQ
Distributed thread is performing a remote access on behalf of a request from another location. The thread is suspended because the maximum number of active database access threads ( MAX REMOTE ACTIVE value of the DSN6SYSP macro as displayed in the subsystem parameters window) was reached.
SP
Thread is executing within a stored procedure.
SW
Thread is waiting for a stored procedure to be scheduled.
T
Allied, nondistributed thread was established.
TN
Allied thread was distributed to access data at another DB2 location, but it was suspended because DB2 must first connect to the partner location (establish DB2 system conversations with the partner).
TR
Allied thread was distributed to access data at another location.
A
The Active column. An asterisk means the thread is active within DB2. If VTAM has control of the conversation (if DB2 transferred control of the thread to VTAM for that conversation), there is a V in this column. A W indicates that DB2 has suspended processing on this conversation until VTAM notifies DB2 that the VTAM event is complete. The column is otherwise blank.
Req-cnt
A wraparound counter to show the number of DB2 requests.
Correlation id
A 1- to 12-character variable representing the recovery correlation-ID associated with the thread. A correlation ID is an identifier associated with a specific thread.
Plan name
A 1- to 8-character variable representing the plan name associated with the thread. For threads using application-directed access from a non-DB2 requester, this column displays the constant DISTSERV.
Location
The location name of the remote system. DB2 does not receive a location name from requesters that are not DB2 for OS/390 subsystems. Information about a requester that is not a DB2 for OS/390 subsystem is the requester's LUNAME or IP address. The LUNAME is in the form <LULA> and the IP address is in the form nnn.nnn.nnn.nnn.
ASID
Address space identifier.

For indoubt threads, the columns of the report are:

Auth ID
The authorization ID associated with a signed-on connection. If not signed-on, this field is blank.
Coordinator
The name of the two-phase commit coordinator.
Status
The status of the thread. Possible values are:
ABORTED - A canceled thread
ABORTED-H
INDOUBT
COMMITTED - A committed thread
COMMITTED-H
Reset
Indicates whether information in the report must be purged with the command -RESET INDOUBT (DB2).
URID
A unit of recovery identifier. This uniquely identifies a unit of work.