DSNV402I ACTIVE THREADS -

Explanation

This message marks the beginning of a section of output from the DISPLAY THREAD command, which is part of message DSNV401I.

Information about active, inactive, stored procedure, and system threads (DSNV402I, DSNV424I, and DSNV497I)

The DISPLAY THREAD command reports the same type of information about active, inactive, stored procedure, and system threads.

The TYPE(ACTIVE) and TYPE(PROC) options generate a DSNV402I message.

DSNV402I - ACTIVE THREADS -
NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
DISPLAY ACTIVE REPORT COMPLETE

The TYPE(INACTIVE) option generates a DSNV424I message.

DSNV424I - INACTIVE THREADS -
NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
DISPLAY INACTIVE REPORT COMPLETE

The TYPE(SYSTEM) option generates a DSNV497I message.

DSNV497I - SYSTEM THREADS -
DB2 db2-statestate-phase 
NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
DISPLAY SYSTEM THREAD REPORT COMPLETE

Each thread that meets the report criteria is listed on a separate line. Additional information might be provided for individual threads.

Db2 db2-statestate-phase

The state of Db2 as follows:

db2-state

The state of Db2. Possible values are STARTING, STOPPING, or ACTIVE.

state-phase

The phase of restart or shutdown, if available. If db2-state is ACTIVE, no phase information is provided.

NAME text

The connection name that was used to establish the thread.

If the connection status value is D, the connection name is either the connection name for the allied address space or the Db2 subsystem name.

For distributed database access threads, this field contains the following information:

requester-value

For threads that access the server from a Db2 for z/OS® requester, this value is the connection name of the thread at the requesting location.

SERVER

For threads that access the server from a non-Db2 for z/OS requester, no connection name is identified.

DISCONN

The DBAT is disconnecting.

DISCN-NC

The disconnected DBAT is being reused for a new connection, or is waiting to complete authorization.

blank

For threads where the originating task is running on the same Db2 subsystem, this value is blank.

When the connection name value is blank, the expected connection status value is PT.

ST t

A one- or two-letter code that indicates connection status. Possible values are:

AC

A thread is executing in an accelerator server. This status is displayed until accelerator processing concludes and returns control to Db2.

AT

A thread that processes an autonomous procedure.

D

The thread is in the process of termination as a result of the termination of the associated allied task. If this thread is also the last (or only) Db2 thread for the address space, the associated allied task is placed in a wait state.

For an active thread, this value can indicate possible problems with Db2. If the activity indicator value is *, use the information in message DSN3201I to identify and resolve any problems.

DA

The DBAT slot is currently not associated with a remote connection and is available to be assigned to a type 2 inactive thread.

This value is accompanied by a token value of 0.

DI

The thread is disconnected from an execution unit. No TCB is associated with the Db2 thread.

This value is possible is only when the connection name is RRSAF.

N

The thread is in either IDENTIFY or SIGNON status.

This value is accompanied by a token value of 0.

ND

The thread is in either IDENTIFY or SIGNON status, and the thread is currently not associated with any TCB.

PT

A parallel task thread was established (plan allocated).

QD

The thread is queued for termination as a result of the termination of the associated allied task. If this thread is also the last (or only) Db2 thread for the address space, the associated allied task is placed in a wait state.

For an active thread, this value can indicate possible problems with Db2. If the activity indicator value is *, use the information in message DSN3201I to identify and resolve any problems.

QT

The CREATE THREAD request was queued. The associated allied task is placed in a wait state.

R2

The inactive connection (sometimes called a type-2 inactive thread) is waiting for a the next request from its remote location. See "Inactive connections support" in How DBATs process remote connections.

RA

The DBAT is processing a request from a remote location. A DBAT with this status is a candidate for idle thread detection and termination based on the IDTHTOIN subsystem parameter setting.

RD

The DBAT is processing a request from a remote location and waiting for the next transaction. The DBAT is an active KEEPDYNAMIC-refreshable thread, and not a candidate for idle thread detection and termination. For more information, see Enabling KEEPDYNAMIC refresh for DBATs.

RH

The DBAT is processing a request from a remote location and waiting for the next transaction. The DBAT is being kept active due to resources being held past a commit or rollback. A DBAT with this status is a candidate for idle thread detection and termination based on the IDTHTOIN subsystem parameter setting. For more information, see IDLE THREAD TIMEOUT field (IDTHTOIN subsystem parameter). The possible resources being held are:

• Open WITH HOLD cursors
• Allocated declared global temporary tables
• Held lob locators
• Commit performed within a stored procedure which requires a two-phase commit/rollback from the client connection
• Active KEEPDYNAMIC packages but the client did not request KEEPDYNAMIC refresh

RK

The DBAT is processing a request from a remote location for an operation that invoked Kerberos services. This status is displayed until Kerberos services returns control to Db2.

RN

The DBAT is processing a request from a remote location, and the request accesses data at another Db2 location. The thread is suspended until Db2 connects to the partner location (establishes Db2 system conversations with the partner).

When another Db2 site is being contacted for the first time using system-directed access, Db2 must establish Db2 system conversations with the partner location. A request is presented to a Db2 DDF service task that establishes a system conversation. The thread is suspended until the request is processed. If the thread remains in this status for an extended period of time, the Db2 service task that establishes the system conversations might be busy processing other requests. The Db2 DISPLAY LOCATION command (DISPLAY LOCATION(*) DETAIL) shows conversation activity for this Db2 system conversation (SYSCON-O) service task.

RP

The DBAT is processing a request from a remote location and waiting for the next transaction. The thread is an active high-performance DBAT, and it is not a candidate for idle thread detection and termination. For more information, see Enabling high-performance DBATs.

RQ

The DBAT is processing a request from a remote location, and it is suspended for one of the following reasons:

• The maximum number of active DBATs specified by the MAXDBAT subsystem parameter was reached. See MAX REMOTE ACTIVE field (MAXDBAT subsystem parameter).
• The system profile monitoring threshold was reached. See Monitoring threads by using profile tables.

Database access agents (DBAAs) are queued until other DBAAs deallocate or go inactive, providing an available slot. The DBAA resumes when a slot becomes available, and the DBAA is next in the queue.

Consider increasing the value of the MAXDBAT subsystem parameter.

RX

The DBAT is processing an XA transaction for a request from another location.

SP

A thread is running within a stored procedure. This status value is displayed until the stored procedure terminates and returns control to Db2.

SW

A thread is waiting for a stored procedure to be scheduled. This status value is displayed until the stored procedure begins to run.

T

An allied, nondistributed thread was established (plan allocated).

TD

An allied thread was established (plan allocated), and the thread is currently not associated with any TCB.

TN

An allied thread was distributed to access data at another Db2 location, but it was suspended because Db2 was not connected to the partner location.

When another Db2 site is being contacted for the first time using system-directed access, Db2 must establish Db2 system conversations with the partner location. A request is presented to a Db2 DDF service task that establishes a system conversation. The thread is suspended until the request is processed. If the thread remains in this status for an extended period of time, the Db2 service task that establishes the system conversations might be busy processing other requests. The Db2 DISPLAY LOCATION command (DISPLAY LOCATION(*) DETAIL) shows conversation activity for this Db2 system conversation (SYSCON-O) service task.

TR

An allied thread was distributed to access data at another location.

A t

An indicator that the thread is active within Db2. t can have one of the following values:

*

The thread is active.

blank

The thread is inactive.

REQ num

A counter that shows the number of Db2 requests. This counter restarts at 1 when the count exceeds 32767 requests.

ID text

The recovery correlation ID that is associated with the thread.

For DBATs, this field contains one of the following values:

028.DBAA nn

This value indicates that the database access agent (DBAA) is performing connection processing, which consists of establishing the DBAA thread and validating and verifying the user's ID.

RACF® requests are serialized on one of the Db2 RACF service tasks. This serialization might increase the validation time when multiple DBAAs are being created concurrently.

This value is possible only while the thread is being created.

requester-value

For threads that use system-directed access or application-directed access from a Db2 requester, this value is the correlation ID of the thread at the requesting location.

This value is possible only after the thread has been created.

external-name

For threads that use application-directed access from a non-Db2 requester, this value is the first 12 characters in the DDM external name (EXTNAM) parameter of the DDM EXCSAT command that is received as part of the SQL CONNECT statement.

This value is possible only after the thread has been created.

AUTHID text

The authorization ID that is associated with a signed-on connection.

PLAN text

The plan name that is associated with the thread.

For DBATs, this field contains one of the following values:

DISTSERV

For threads that use application-directed access from a non-Db2 requester, no plan name is identified.

requester-value

For threads that use system-directed access or application-directed access from a Db2 requester, this value is the plan name that is being executed at the requesting location.

For RRSAF connected threads that did not specify a plan name at connect time, the value ?RRSAF is displayed.

If a thread was not established, this field is blank.

If this value is a system plan, see the information about system plans in message DSNT376I.

ASID hex

The address space ID (ASID) of the home address space. This value is a hexadecimal number of up to four characters.

TOKEN num

The thread token that is assigned to the thread.

For threads with a connection status value of DA or N, this value is 0.

If multiple threads have the same token, those threads are processing secondary connections in support of an application that uses package-based continuous block fetch.

The information about types of threads ends with a REPORT COMPLETE line.