DSNV401I DISPLAY THREAD REPORT FOLLOWS -

Explanation

This message marks the beginning of multiple lines of information in response to a DISPLAY THREAD command. Some lines in the output have their own message numbers or alphanumeric identifiers to assist with identification.

The output from the command consists of one or more (but not all) of the following sections:

Member-specific information (DSNV473I, DSNV747I, DSNV475I, DSNV476I, DSNV503I)

If you specify the SCOPE(GROUP) option, the output includes member-specific information before the thread-specific information for that member.

Depending on the DISPLAY THREAD options and the threads that are found, the output includes one or more of the following lines. Each line is followed by thread-specific information for the specified type of thread on that member:

  DSNV473I ACTIVE THREADS FOUND FOR MEMBER: text
  DSNV474I INDOUBT THREADS FOUND FOR MEMBER: text
  DSNV475I INACTIVE THREADS FOUND FOR MEMBER: text
  DSNV476I POSTPONED ABORT THREADS FOUND FOR MEMBER: text
  DSNV503I SYSTEM THREADS FOUND FOR MEMBER: text
text
Member name for which thread information is being displayed.

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.
Start of changeDISCONNEnd of change
Start of changeThe DBAT is disconnecting.End of change
Start of changeDISCN-NCEnd of change
Start of changeThe disconnected DBAT is being reused for a new connection, or is waiting to complete authorization.End of change
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.

Start of changeThis value is accompanied by a token value of 0.End of change

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.
Start of changeRDEnd of change
Start of changeThe 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.End of change
Start of changeRHEnd of change
Start of changeThe 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
End of change
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.

Start of changeRPEnd of change
Start of changeThe 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.End of change
RQ
The DBAT is processing a request from a remote location, and it is suspended for one of the following reasons:

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.

Start of changeFor threads with a connection status value of DA or N, this value is 0.End of change

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.

Information about indoubt and postponed threads (DSNV406I and DSNV431I)

The DISPLAY THREAD command reports the same type of information about indoubt and postponed threads.

Information about indoubt threads begins with a DSNV406I message. 

DSNV406I - INDOUBT THREADS -
COORDINATOR               STATUS     RESET URID         AUTHID
text                      text       txt   hex          text
DISPLAY INDOUBT REPORT COMPLETE

Information about postponed abort threads begins with a DSNV431I message. 

DSNV431I - POSTPONED ABORT THREADS -
COORDINATOR               STATUS     RESET URID         AUTHID
text                      text       txt   hex          text
DISPLAY POSTPONED ABORT REPORT COMPLETE

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

COORDINATOR text
The name of the two-phase commit coordinator. The value depends on the type of thread, as follows:
Allied threads
The coordinator name is one of the following values:
  • The IMS connection name
  • The CICS connection name
  • RRS (for Resource Recovery Services attachment facility connected threads)
  • The location name of the local Db2 subsystem.

Additional information is displayed for IMS and CICS connections and for RRS.

Database access threads (DBATs)
The coordinator name is one of the following values:
  • location:luname, where location is the relational database name for the coordinator and luname is the SNA LU name for the coordinator.
  • location:port, where location is the relational database name for the coordinator and port is the TCP/IP port number for two-phase commit resynchronization for the coordinator.
  • <luname>:luname, where luname is the SNA LU name for the coordinator.
  • nnn.nnn.nnn.nnn:port , where nnn.nnn.nnn.nnn is the IP address for the coordinator and port is the TCP/IP port number for two-phase commit resynchronization for the coordinator.

If the thread is distributed, additional information is displayed.

STATUS text
The status of the thread.

If the status of a thread for a logical unit of work at a participant is INDOUBT, COMMITTED-H, or ABORTED-H, and the coordinator is a Db2 location that has not cold started, the lack of any information about the thread in a DISPLAY THREAD(INDOUBT) report indicates that the decision at the coordinator was to abort the logical unit of work.

This field can have one of the following values:

ABORT-P
A postponed abort unit of recovery. Objects for which this unit of recovery has backout work pending are inaccessible (restart-pending status) until the abort is completed (for example, by means of the RECOVER POSTPONED command).
ABORT-PSTRT
A postponed abort unit of recovery that is currently undergoing RECOVER POSTPONED processing or automatic Db2 backout processing (requested by restarting with system parameter LBACKOUT = AUTO).
ABORTED
A coordinator status that indicates that Db2 has one or more downstream participants that are using the Presumed Nothing (PN) protocol and might be indoubt. The thread is included in the DISPLAY THREAD output until all downstream PN participants complete indoubt resolution. The detail line V450 lists the downstream participants that have pending resolution. Database locks that were held for the thread are released.

If a participant resolved the indoubt thread with a heuristic decision, and the decision was COMMIT, detail line V452 is displayed. This detail line contains the name of the participant and the heuristic decision that it made. Because the coordinator aborted and the participant committed, this situation indicates heuristic damage. Information about the thread is displayed until it is deleted with the RESET INDOUBT command. The database administrators at all involved locations need to know that heuristic damage occurred and at which location.

ABORTED-H
An indoubt thread that was heuristically resolved with the RECOVER INDOUBT command. Information about the thread is displayed is displayed until the coordinator is informed of the heuristic decision. Additional detail lines might be included in the report.
COMMITTED
A thread that is committed. This status is displayed when Db2 is the coordinator and has downstream participants that might be indoubt. Information about the thread is included in the DISPLAY THREAD output until all downstream participants complete indoubt resolution. Detail line V450 lists the downstream participants that have pending resolution. Database locks that were held for the thread are released.

If a participant resolved the indoubt thread with a heuristic decision, and the decision was ABORT (rollback), detail line V453 is displayed. This detail line contains the name of the participant and the heuristic decision that it made. Because the coordinator committed and the participant aborted, this situation indicates heuristic damage. Information about the thread is displayed until it is deleted with the RESET INDOUBT command. The database administrators at all involved locations need to know that heuristic damage occurred and at which location.

COMMITTED-H
An indoubt thread that was heuristically resolved with the RECOVER INDOUBT command. Information about the thread is displayed until the coordinator is informed of the heuristic decision, and all downstream participants, if any, complete indoubt resolution. Additional detail lines might be included in the report to identify downstream participants that have pending resolution.
INDOUBT
A thread that is indoubt. Information about the thread is displayed until all indoubt resolution responsibilities are complete. Additional detail lines might be included in the report.
RESET txt
If this column contains YES, the thread must be removed from the indoubt display. If necessary, use the RESET INDOUBT command to purge a thread. If this column is empty, the thread does not need to be removed.
URID hex
An RBA of the Db2 recovery log. This point is the beginning of recovery logging for this thread.
AUTHID text
The primary authorization ID that is associated with the thread.

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

V429: Information about stored procedures

If a thread is running a stored procedure, the output includes the following information about the stored procedure.

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
  V429 CALLING PROCEDURE=text, LOAD MODULE=text, 
       PROC=text, ASID=hex, WLM_ENV=text
PROCEDURE text
The name of the stored procedure.
LOAD MODULE text
The MVS™ load module that is associated with the stored procedure. This value is empty until the load module name is determined.
PROC text
The name of the JCL PROC that is used to start the address space where the stored procedure is running. This field is empty until the stored procedure is assigned to a specific stored procedure address space.
ASID hex
The MVS address space ID (ASID) of the address space where the stored procedure is running. This field contains the value 0000 until the stored procedure is assigned to a specific stored procedure address space.
WLM_ENV text
The name of the WLM application environment where the stored procedure is running.

V436: Information about SQL statements

If you specify a detail report and a thread is processing an SQL statement, the output includes the following information about the SQL statement and the program that contains the statement.

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
  V436-PGM=text, SEC=num, STMNT=num, THREAD-INFO=text
PGM text
The collection ID and associated package or DBRM member. This information is provided in the following format: 
collection.package

If the SQL statement that is being executed is not associated with a package, collection is not applicable and is indicated by an asterisk (*).

SEC num
The SQL section number that is associated with the package or DBRM.
STMT num
The SQL statement number that is associated with the package or DBRM.
THREAD-INFO text
Information about the thread.
thread-information is a colon-delimited list that contains the following segments. An asterisk (*) in any segment indicates that the information is not available.
  • The primary authorization ID that is associated with the thread.
  • The name of the user's workstation.
  • The ID of the user.
  • The name of the application.
  • The statement type for the previously executed statement: dynamic or static.
  • The statement identifier for the previously executed statement, if available. The statement identifier can be used to identify the particular SQL statement. For static statements, the statement identifier correlates to the STMT_ID column in the SYSIBM.SYSPACKSTMT table. For dynamic statements, the statement identifier correlates to the STMT_ID column in the DSN_STATEMENT_CACHE_TABLE table. That statement might not have contributed to the current failure.
  • The name of the role that is associated with the thread.
  • The correlation token that can be used to correlate work at the remote system with work performed at the Db2 subsystem. The correlation token, if available, is enclosed in '<' and '>' characters, and contains three components, separated by periods:
    • A 3 to 39 character IP address.
    • A 1 to 8 character port address.
    • A 12 character unique identifier.

V437: Information about the user and application

If the client system is able to provide specific information about the user that is associated with this thread, this information is included in the output. If the information is not provided by the client system, the relevant fields contain an asterisk (*).

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text
  V437-WORKSTATION=text 
       USERID=text
       APPLICATION NAME=text
WORKSTATION text
The workstation name
USERID text
The user ID
APPLICATION NAME text
The name of the client application

V440: Information about threads that are managed by an XA transaction manager

If the thread is related to a global transaction that is coordinated by an XID, the output includes XID information. The DISPLAY THREAD command must include the TYPE(ACTIVE) and DETAIL options, or the TYPE (INDOUBT) option for this information to be included.

Line V440 indicates that the thread is managed by an XA transaction manager, such as WebSphere® Application Server, which identifies the transaction with an xid value. The XID is provided to allow correlation with the XA transaction manager. Db2 uses both the logical unit of work identifier, luwid, and the XA transaction identifier, xid, to coordinate and recover transactions. Db2 is a participant in an XA transaction that is executing on behalf of an XA transaction manager.

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
  V440-XID=hex
XID hex
The XID is provided in its hexadecimal representation and consists of the following elements:
  • A 4-byte format ID.
  • A 4-byte global transaction identifier length (the gtrid_length field).
  • A 4-byte branch qualifier length (bqual_length).
  • Variable-length data that is composed of at most two contiguous components: A global transaction identifier length (gtrid_length), and a branch qualifier length (bqual_length). The gtrid_length element specifies the number of bytes (1-64) that constitute the gtrid, starting at the first byte of the data element. The bqual-length element specifies the number of bytes (up to 64) that constitute bqual, starting at the first byte after gtrid.

V441: User accounting information

If the client system is able to provide user accounting information for the thread, this information is included in the output. The DISPLAY THREAD command must include the DETAIL option and either the TYPE(ACTIVE), TYPE(INACTIVE), or TYPE(INDOUBT) option for this information to be included.

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
  V441-ACCOUNTING=text
ACCOUNTING text
The client end-user accounting information. This information is provided if the appropriate information is provided by the client system, and if Db2 recognizes the format of the information.

V442: Information about correlation tokens

If the client system is able to provide a correlation token that can be used to correlate work at the remote system with work that is performed at the Db2 subsystem, this information is included in the output.

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
  V442-CRTKN=text
CRTKN text
The correlation token, which is made up of three components separated by periods:
ip-address.port-address.unique-id
ip-address
The IP address is 3 to 39 characters in length.
port-address
The port address is 1 to 8 characters in length.
unique-id
The ID is 12 characters in length.

V444: Information about distributed threads (for active, inactive, stored procedure, and system threads)

If any threads were distributed to other locations, the output includes the logical unit of work identifier for each distributed thread.

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text
          text
  V444-text=num ACCESSING DATA AT 
   text-address..number
text=num ACCESSING DATA AT
Information to identify the distributed thread as follows:
text
The global logical unit of work ID (LUWID).
num
The local token that identifies the thread. This token can be used in place of the LUWID in any Db2 command that accepts LUWID as input.
If the thread becomes indoubt, a new token is assigned for the indoubt thread.
text-address..number
The remote DBMS at which data is being accessed.
text
The partner location name.
address
The partner LU name for an SNA connection, or the dotted decimal IP address for a TCP/IP connection (nnn.nnn.nnn.nnn).
number
An SQL port number. This token is included only if the second token is an IP address.

V445: Information about database access threads

The output includes the following information about database access threads:

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text
          text
  V445-text=num ACCESSING DATA FOR
   text
text=num
Information to identify a distributed database access thread (DBAT) as follows:
text
The global logical unit of work ID (LUWID).
num
The local token that identifies the thread. This token can be used in place of the LUWID in any Db2 command that accepts LUWID as input.
If the thread becomes indoubt, a new token is assigned for the indoubt thread.
ACCESSING DATA FOR text
The network address of the remote location. This value can be blank.
  • If the connection with the requester is through SNA, this field contains the relational database name of the requester or the VTAM® LU name of the requester, a dash (-) delimiter, and the LU name of the requester.
  • If the connection with the requester is through TCP/IP, this field contains the IP address of the requester.

V447 and V448: Information about conversations

The output contains conversation information for active and inactive threads. Conversation information is displayed for a distributed database access thread (DBAT), distributed inactive connection, or distributed allied thread when a detail report is specified. Information is displayed for each conversation that is associated with the thread or connection. The report lists detailed information regarding the connection. 

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text
          text
  V447--INDEX SESSID           A ST TIME
  V448--(txt) text             t tx timestamp
INDEX (text)
The index value from the location information in the V445 output line. This value provides correlation of the conversation detail information to the associated location.
SESSID text
The session identifier. The session identifier is either a pair of TCP/IP port numbers or a VTAM-defined session instance identifier.
TCP/IP connections
The local Db2 TCP/IP port number followed by the TCP/IP port number for the partner. The two port numbers are separated by a colon. For example: 5001:28191.
SNA partners
The VTAM-defined session instance identifier of the session on which the conversation is running. The field contains zeros if the session identifier is not applicable.

VTAM might not supply the entire session ID (SID) to Db2. The first two digits of the SID might be incorrect, in which case the SID, as presented in this message, is not acceptable in VTAM commands. If this occurs, use the VTAM DISPLAY NET,ID=db2-luname,SCOPE=ACT command to obtain the full SID. The DISPLAY NET command lists all sessions for the Db2 logical unit. Review the DISPLAY NET report for the complete session ID.

A text
A single alphabetic character that indicates activity. This field can contain one of the following values:
N
The conversation is active in the network.
W
The conversation is suspended in Db2 while it waits for the network notification that the function is complete.
Blank
All other cases.
ST text
The status of the conversation. This information is presented as two characters and can contain the following values:
First character
A
Conversation is in allocation.
C
Session limits are being negotiated with the partner (CNOS) prior to conversation allocation.
D
Conversation is in deallocation.
R
Receiving.
  • At the requesting site, this value indicates that the conversation is receiving a response from a request.
  • At the server site, this value indicates that the conversation is receiving or waiting for a request.
S
Sending.
  • At the requesting site, this value indicates that the conversation can send requests to the server.
  • At the server site, this value indicates that the conversation is sending or preparing to send a response.
X
Exchanging log name information with the partner before conversation allocation to determine if the partner supports protected conversations. If the thread remains in this status for an extended period of time, the Db2 service task that exchanges log names might be busy processing other requests. The Db2 DISPLAY LOCATION command (DISPLAY LOCATION(*) DETAIL) shows you conversation activity for this (RESYNC) service task.
Blank
All other cases.
Second character
1
Unprotected conversation using system-directed access is active.
2
Unprotected conversation using application-directed access is active.
3
Protected conversation using system-directed access is active.
4
Protected conversation using application-directed access is active.
5
A distributed thread is processing a secondary connection in support of an application that uses package-based continuous block fetch.
Blank
All other cases.
TIME timestamp
The timestamp (yydddhhmmssth), in local time, of the last message that was sent or received on the conversation. The timestamp consists of the following segments:
yy
Two-digit indicator for the year.
ddd
Three-digit indicator for the day of the year.
hhmmssth
Indicator for the time of the day.

V449: Information about IMS and CICS connections and RRS

When the coordinator is an IMS or CICS connection or is RRS, the output includes the following additional information about the coordinator.

COORDINATOR               STATUS     RESET URID         AUTHID
text                      text       txt   hex          text
  V449-HAS NID=text AND ID=text
NID text
The network ID that is assigned by IMS or CICS, or, if the connection type is RRSAF, the RRS unit of recovery ID.
ID text
The correlation ID that is assigned by IMS or CICS, or, if the connection type is RRSAF, the correlation ID that is assigned by the connected application.

V450: Information about downstream participants that might be indoubt

If you specify TYPE(INDOUBT) in the DISPLAY THREAD command, the output also includes the following information about any downstream participants that might be indoubt. The indoubt participants that are listed in the output might be the result of an abnormal termination of this Db2 subsystem. The LUWID of the indoubt thread is displayed in the COORDINATOR field prior to this message.

COORDINATOR               STATUS     RESET URID         AUTHID
text                      text       txt   hex          text
  V450-HAS PARTICIPANT INDOUBT AT 
   text-address..number
HAS PARTICIPANT INDOUBT AT text address number
The name of a remote DBMS at which data is being accessed or where a thread is indoubt.
  • text is the partner location name.
  • address is the partner LU name for an SNA connection, or the dotted decimal IP address for a TCP/IP connection (nnn.nnn.nnn.nnn).
  • number is a resynchronization port number. This token is included only if the second token is an IP address.

V451: Information about incomplete resolution of indoubt threads

Line V451 indicates that an indoubt thread was manually resolved with the RECOVER INDOUBT command, but indoubt resolution with the coordinator is not complete. The thread remains indoubt. The LUWID of the indoubt thread is displayed in the COORDINATOR field prior to this message. 

COORDINATOR               STATUS     RESET URID         AUTHID
text                      text       txt   hex          text
  V451-RESYNC WITH COORDINATOR STILL PENDING

You must specify TYPE(INDOUBT) in the DISPLAY THREAD command for this information to be displayed.

V452: Information about heuristic commit decisions

Line V452 indicates that a decision was made at the participant to force the indoubt thread to commit without waiting for automatic resynchronization to be performed. The LUWID of the indoubt thread is displayed in the COORDINATOR field prior to this message.

COORDINATOR               STATUS     RESET URID         AUTHID
text                      text       txt   hex          text
  V452-HEURISTIC COMMIT BY PARTICIPANT AT LOCATION text
HEURISTIC COMMIT BY PARTICIPANT AT LOCATION text
The location (relational database name) where the HEURISTIC COMMIT was performed.

You must specify TYPE(INDOUBT) in the DISPLAY THREAD command for this information to be displayed.

This information is displayed until Db2 resolves the indoubt status with the coordinator. If the coordinator decision is the same as the heuristic decision of the partner, the detail line is no longer displayed.

V453: Information about heuristic abort decisions

Line V453 indicates that a decision was made at the participant to force the indoubt thread to abort without waiting for automatic resynchronization to be performed. The LUWID of the indoubt thread that was forced to abort is displayed in the COORDINATOR field prior to this message.

COORDINATOR               STATUS     RESET URID         AUTHID
text                      text       txt   hex          text
  V453-HEURISTIC ABORT BY PARTICIPANT AT LOCATION text
HEURISTIC ABORT BY PARTICIPANT AT LOCATION text
The location (relational database name) where the HEURISTIC ABORT was performed.

You must specify TYPE(INDOUBT) in the DISPLAY THREAD command for this information to be displayed.

This information is displayed until Db2 resolves the indoubt status with the coordinator. If the coordinator decision is the same as the heuristic decision of the partner, this detail line is no longer displayed.

If the coordinator status is COMMITTED and the heuristic decision of the participant is ABORT, the message continues to be displayed until it is deleted with the RESET INDOUBT command. The database administrators at all involved locations need to know that heuristic damage occurred and at which location.

V457: Information about resync protocol errors with participants

Line V457 indicates that a protocol error was detected during attempted automatic indoubt resolution with the participant. Manual resolution of an indoubt thread at the participant location might be required. The LUWID of the thread that might require manual resolution is displayed in the COORDINATOR field prior to this message.

COORDINATOR               STATUS     RESET URID         AUTHID
text                      text       txt   hex          text
  V457-RESYNC PROTOCOL ERROR WITH PARTICIPANT text
RESYNC PROTOCOL ERROR WITH PARTICIPANT text
The location where manual resolution might be needed. The location is either the relational database name or the logical unit name (LU name) of the participant.

You must specify TYPE(INDOUBT) in the DISPLAY THREAD command for this information to be displayed.

V458: Connection information for indoubt threads

If you specify TYPE(INDOUBT) in the DISPLAY THREAD command, the output contains the following connection information : 

COORDINATOR               STATUS     RESET URID         AUTHID
text                      text       txt   hex          text
  V458-CONNECTION-NAME text CORRELATION-ID text
CONNECTION-NAMEtext
The connection name that is assigned by the coordinator if the coordinator is another Db2 subsystem. The field contains the constant SERVER if the coordinator is not a Db2 subsystem.
CORRELATION-ID text
The correlation ID that is assigned by the coordinator if the coordinator is another Db2 subsystem. The field contains the first 12 characters of the EXTNAME parameter of the EXCSAT command that is sent by the coordinator if the coordinator is not a Db2 subsystem.

V459: Information about syncpoint protocol errors with coordinators

Line V459 indicates that a protocol error was detected during sync point processing with the coordinator. Manual resolution of an indoubt thread at this location is required. The LUWID of the thread that requires manual resolution is displayed in the COORDINATOR field prior to this message.

COORDINATOR               STATUS     RESET URID         AUTHID
text                      text       txt   hex          text
   V459-SYNCPOINT PROTOCOL ERROR WITH COORDINATOR

You must specify TYPE(INDOUBT) in the DISPLAY THREAD command for this information to be displayed.

V460: Information about syncpoint protocol errors with participants

Line V460 indicates that a protocol error was detected during sync point processing with the participant. Manual resolution of an indoubt thread at the participant location might be required. The LUWID of the thread that might require manual resolution at the participant is displayed in the COORDINATOR field prior to this message.

COORDINATOR               STATUS     RESET URID         AUTHID
text                      text       txt   hex          text
    V460-SYNCPOINT PROTOCOL ERROR WITH PARTICIPANT text
SYNCPOINT PROTOCOL ERROR WITH PARTICIPANT text
The location where manual resolution might be needed. The location is either the relational database name or the logical unit name (LU name) of the participant.

You must specify TYPE(INDOUBT) in the DISPLAY THREAD command for this information to be displayed.

V461: Information about heuristic damage

Line V461 indicates that indoubt resolution with the coordinator completed. Heuristic damage was detected at this location because the heuristic decision that was made at this location is different than the decision that was made at the coordinator. The thread remains indoubt. The LUWID of the thread is displayed in the COORDINATOR field prior to this message. The STATUS field shows the heuristic decision that was made at this location.

This message is displayed until it is removed by a RESET INDOUBT command.

COORDINATOR               STATUS     RESET URID         AUTHID
text                      text       txt   hex          text
  V461-RESYNC WITH COORDINATOR SHOWS HEURISTIC DAMAGE

You must specify TYPE(INDOUBT) in the DISPLAY THREAD command for this information to be displayed.

V462: Information about cold starts by participants

Line V462 indicates that Db2 has coordinator responsibility for an indoubt thread at the participant, and the participant informed Db2 that it performed a cold start operation and lost all knowledge of indoubt threads. Heuristic damage might have occurred at the participant. The LUWID of the indoubt thread is displayed in the COORDINATOR field prior to this message.

Use the RESET INDOUBT command to purge this message from the indoubt report. The cold-starting participant might have been coordinating downstream participants that are now indoubt. The database administrator at these participants might need to know the status of the thread at the coordinator, so that correct heuristic decisions can be made. 

COORDINATOR               STATUS     RESET URID         AUTHID
text                      text       txt   hex          text
  462-COLD START BY PARTICIPANT AT LOCATION text
COLD START BY PARTICIPANT AT LOCATION text
The location (relational database name) where the cold start was performed.

You must specify TYPE(INDOUBT) in the DISPLAY THREAD command for this information to be displayed.

V463: Information about cold starts by coordinators

Line V463 indicates that one of the following situations occurred:

  • The coordinator for a thread that is indoubt at a Db2 subsystem was cold started and therefore lost all knowledge of indoubt threads.
  • The knowledge of the local system about the coordinator was cold started, for example, by the RESET INDOUBT FORCE command.

Manual resolution of an indoubt thread at this location is required. The LUWID of the thread for which manual resolution is required is displayed in the COORDINATOR field prior to this message. 

COORDINATOR               STATUS     RESET URID         AUTHID
text                      text       txt   hex          text
   V463-COORDINATOR HAS COLD STARTED

You must specify TYPE(INDOUBT) in the DISPLAY THREAD command for this information to be displayed.

V464: Information about resync protocol errors with coordinators

Line V464 indicates that a protocol error was detected during attempted automatic indoubt resolution with the coordinator. Manual resolution of an indoubt thread at this location is required. The LUWID of the thread that requires manual resolution is displayed in the COORDINATOR field prior to this message. 

COORDINATOR               STATUS     RESET URID         AUTHID
text                      text       txt   hex          text
   V464-RESYNC PROTOCOL ERROR WITH COORDINATOR

You must specify TYPE(INDOUBT) in the DISPLAY THREAD command for this information to be displayed.

V465: Information about threads that remain in the prepared state

Line V465 indicates that the thread was prepared for the specified period of time. Db2 is the participant in the logical unit of work. Db2 has completed the first phase of commit and is waiting for the commit or abort decision to be transmitted from the coordinator for the specified period of time. This message is not included in the output until the thread is in the prepared state for 60 seconds. The thread is identified by the line that precedes this message.

You must specify TYPE (ACTIVE) in the DISPLAY THREAD command for this information to be displayed.

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
   V465-THREAD HAS REMAINED IN A PREPARED STATE FOR timestamp
timestamp
The length of time that the thread was prepared, in the format hh:mm:ss (hours, minutes and seconds). The maximum number of reported hours is 65535, which is roughly 7.5 years. After this time period elapses, the count is reset to zero.
You can take the following actions to try to resolve this thread manually (that is, take heuristic action) if you need to release locks that are held by this thread:
  1. Use the CANCEL DDF THREAD command to force the thread from the prepared state to the indoubt state. When the thread is indoubt, it is displayed in the DISPLAY THREAD TYPE(INDOUBT) report.
  2. Determine the proper decision (commit or abort) by contacting the coordinator location, as shown in the display of indoubt threads.
  3. Use the RECOVER INDOUBT command to heuristically commit or abort the thread.

V466: Information about how long a thread was indoubt

Line V466 indicates that the thread entered the indoubt state at the specified time. Db2 is the participant in the logical unit of work, has completed the first phase of commit, and is waiting for the commit or abort decision to be transmitted from the coordinator. However, Db2 lost communications with the coordinator. The LUWID of the thread is displayed in the COORDINATOR field prior to this message. 

COORDINATOR               STATUS     RESET URID         AUTHID
text                      text       txt   hex          text
  V466-THREAD HAS BEEN INDOUBT FOR timestamp
THREAD HAS BEEN INDOUBT FOR timestamp
The length of time that the thread was indoubt, in the format hh:mm:ss (hours, minutes and seconds). The maximum number of reported hours is 65535, which is roughly 7.5 years. After this time period elapses, the count is reset to zero.

If necessary, you can release locks that are held by this thread by performing the following actions:

  1. Determine the proper decision (commit or abort) by contacting the coordinator location, as shown in the display of indoubt threads.
  2. Use the RECOVER INDOUBT command to heuristically commit or abort the thread.

You must specify TYPE(INDOUBT) in the DISPLAY THREAD command for this information to be displayed.

V467: Information about distributed threads (for indoubt and postponed threads)

For indoubt and postponed distributed threads, the output includes the following additional information.

COORDINATOR               STATUS     RESET URID         AUTHID
text                      text       txt   hex          text
  V467-HAS LUWID text=num
LUWID text num
The global logical unit of work ID and the local token that identifies the thread.

You must specify TYPE(INDOUBT) in the DISPLAY THREAD command for this information to be displayed.

V471: Information about available agents

Line V471 indicates that the agent is currently not associated with a remote location. In the following situations, the agent can be assigned to a process:

  • The completion of a queued receive request on a type 2 inactive thread.
  • A request that a new connection be established, after MAX REMOTE ACTIVE has been reached. 
NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
  V471-luwid=token
luwid=token
The global logical unit of work ID and the local token that identifies the agent.

V480 and V481: Information about the unit of recovery

When the DISPLAY THREAD command is issued with the RRSURID option, additional information is provided about the unit of recovery.

Information about the participant is provided in line V480 when the TYPE(ACTIVE) option is used.

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
  V480-DB2 IS PARTICIPANT FOR RRS URID=hex
URID hex
The Recoverable Resource Services (RRS) unit of recovery ID in which this thread participates.

Information about the coordinator is provided in line V481 when either the TYPE(ACTIVE) or the TYPE(INDOUBT) option is used.

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
  V481-DB2 IS COORDINATOR FOR RRS URID=hex
URID hex
The Recoverable Resource Services (RRS) unit of recovery ID for which this thread is coordinator.

When the V481 message is included in an INDOUBT thread report, the preceding lines indicate the status of the Db2 unit of recovery that contains the RRS unit of recovery. If manual recovery of the RRS unit of recovery is required, the outcome of the Db2 unit of recovery can determine whether to commit or rollback the RRS unit of recovery.

V482: WLM information

If you request a detail report and the thread is associated with a z/OS Workload Manager (WLM) enclave, the output includes an indication that WLM is currently applying its performance goals to the thread.

  V482 WLM-INFO=text
text
Information about the WLM characteristics that are associated with the thread. This field includes the values of the following identifiers when known, separated by colons:
  • The name of the service class.
  • The service class period number.
  • The importance level of the period.
  • The performance index of the service class period, scaled by 100. A value of 100 corresponds to a value of 1.0 in the corresponding RMF report.
An asterisk (*) indicates that the value is not known or is not applicable.

V485: Information about trusted contexts

If a thread is associated with a trusted context, the output includes the trusted context name, system authorization ID, and role.

This information is included when a non-detail report is specified.

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
  V485-TRUSTED CONTEXT=text,
       SYSTEM AUTHID=text, 
       ROLE=text
TRUSTED CONTEXT text
The trusted context name.
SYSTEM AUTHID text
The system authorization ID that is associated with the user in the trusted context.
ROLE text
The role that is associated with the user in the trusted context. If the role is not defined for the trusted context, this field contains an asterisk (*).

V490: Information about suspended threads

Line V490 indicates that a thread in your system is currently suspended. This message is informational only.

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
   V490- SUSPENDED timestamp smodule soffset smodptf-level
timestamp

The suspend date and time. The format is YYDDD-HH:MM:SS.HSEC.

smodule soffset and smodptf-level
These fields are for the use of IBM® Support.

When V490 is displayed

The V490 information is displayed only when you specify TYPE(SYSTEM) in the DISPLAY THREAD command.

V492: Information about storage

The V492 line is an informational message for use by IBM Support. 

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
  V492-LONG numK 64VLONG numK 64LONG numK

V501: Information about commands

Line V501 indicates that the system thread is currently executing the specified command. The thread is identified by the preceding lines of output.

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
V501-COMMAND EXECUTING:  text
text
The command that the thread is currently running.

V502: Information about Db2 exit routines

If a system thread is currently executing a Db2 exit routine that you specified, the output includes the following additional information about the thread. The thread is identified by the preceding lines of output.

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
V502-PLOCK ENGINE text EXIT, RMID=text,FCODE=texttext
text
The name of the Db2 exit routine that the thread is running.
RMID=text, FCODE=text text
These fields are for the use of IBM Support.
RMID=dec
Resource manager identifier (RMID).
FCODE=text
Feature code.
text
A text description, if available.

V504: Information about threads that are terminating

If a system thread is currently terminating another thread, the output includes the following additional information about the thread. The thread is identified by the preceding lines of output.

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
V504-TERMINATING CORRID=text, CONNID=text, HASID=text
CORRID=text
The specified correlation ID of the thread that is being terminated.
CONNID=text
The connection ID of the thread that is being terminated.
HASID=text
The home address space ID of the thread that is being terminated.

V505: Information about threads that are waiting

Line V505 indicates that a system thread is experiencing a long wait time for reading or writing data for the specified object. The thread is identified by the preceding lines of output.

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
V505-BM PROCESSING DBNAME=text, SPACE NAME= text, PART= num
DBNAME=text
The name of the database.
SPACE NAME= text
The name of the table space or index space.
PART= num
A number that identifies the partition. For non-partitioned data sets, no value is displayed.

More detailed information about the suspended thread is reported in line V490.

V507: Information about monitoring tasks

If the thread is currently an internal Db2 monitoring task, the output includes the following additional information about the thread.

V507-text MONITOR, INTERVALS=monintervals, STG=monstg, BOOSTS=monboosts, HEALTH=text
     REGION=num, AVAIL=num, CUSHION=num
text MONITOR
The type of monitoring task: active or inactive.
monintervals, monstg, monboosts, and text
These fields are for the use of IBM Support.
REGION num
The size of the region, as a number and unit of measurement.
AVAIL num
The amount of available storage, as a number and unit of measurement.
CUSHION num
The size of the storage cushion, as a number and unit of measurement. The storage cushion is a defined portion of total storage that is available for use, but whose use triggers alerts. The purpose of the alerts is to notify administrators of unexpected storage requirements and help them manage the condition.

You must specify TYPE(SYSTEM) in the DISPLAY THREAD command for this information to be displayed.

V520: Information about autonomous procedures

When a thread is processing an autonomous procedure, the output includes the following additional information about the thread.

NAME     ST A   REQ ID               AUTHID    PLAN      ASID TOKEN
text     t  t   num text             text      text      hex  num
  V520-AUTONOMOUS PROCEDURE INVOKED BY THREAD
       WITH TOKEN=num
TOKEN num
The token of the invoking thread for the autonomous procedure.

Information that indicates NOT FOUND situations

If no threads or connections of the requested type are found, one of the following messages is displayed.

DSNV419I NO CONNECTIONS FOUND
The DISPLAY THREAD TYPE(*), TYPE(ACTIVE) or TYPE(INACTIVE) command was unable to locate any connections within the subsystem.
NO CONNECTION FOUND FOR NAME=text
The DISPLAY THREAD TYPE(ACTIVE) or TYPE(INACTIVE) command was unable to locate any connections that are associated with the indicated connection name. This message is generated once for each connection name for which no connection was found.
NO THREADS FOUND FOR NAME=text
The DISPLAY THREAD TYPE(ACTIVE) or TYPE(INACTIVE) command was unable to locate any threads that are associated with the indicated connection name. This message is generated once for each connection name for which no threads were found.
NO SYSTEM THREADS FOUND
The DISPLAY THREAD command did not find any system threads that can be displayed.
NO SYSTEM THREADS FOUND FOR NAME= connection-name
The DISPLAY THREAD command did not find any system threads for the named connection.
DSNV420I NO INDOUBT THREADS FOUND
The DISPLAY THREAD command found no indoubt threads within the system. This message is generated when the command requests information about all (*) threads that are currently residing within an indoubt state (TYPE=INDOUBT) within the system, but no threads currently exist within this state.
csect NO INDOUBT THREADS FOUND FOR CONNECTION NAME=text
The DISPLAY THREAD TYPE(INDOUBT) command was unable to locate any indoubt threads that are associated with the indicated connection name. This message is generated once for each connection name for which no indoubt threads were found. If you do not specify a connection name, the command uses a default connection name.
NO POSTPONED THREADS FOUND FOR NAME=text
The DISPLAY THREAD command found no postponed abort URs for the named connection. This message is generated when the command requests information about threads for the given connection name that are currently residing within a postponed abort state, but no threads currently exist within this state.
DSNV434I csect NO POSTPONED ABORT THREADS FOUND
The DISPLAY THREAD TYPE(POSTPONED) command found no postponed abort threads.

Other information reported in the DISPLAY THREAD output

ARCHIVE LOG QUIESCE CURRENTLY ACTIVE
An ARCHIVE LOG MODE(QUIESCE) command is currently active. Updates against Db2 resources have been temporarily suspended, which might result in active threads being suspended until termination of the quiesce period.
SCOPE(GROUP) SUPPRESSED DURING RESTART AND SHUTDOWN
The DISPLAY THREAD command with the SCOPE(GROUP) option was issued during restart or shutdown. SCOPE(GROUP) is not supported during restart or shutdown. The command runs locally.
ONLY SYSTEM THREAD DATA AVAILABLE
The DISPLAY THREAD command was issued during restart or shutdown and specified a value for the TYPE option other than SYSTEM. This message indicates that only system thread information is available during restart and shutdown.

End of report markers

The DISPLAY THREAD output normally ends with message DSN9022I.

If the command is not able to complete the report, the output ends with message DSN9023I and one of the following explanations:

DSNV423I DISPLAY THREAD MESSAGE POOL SIZE EXCEEDED
The amount of CSA or ECSA virtual storage that is needed to generate DISPLAY THREAD output exceeded the maximum size of the message buffer pool.

This situation can happen when many threads exist in Db2, and the pattern-matching character '*' is used in a DISPLAY THREAD command, as shown in the following example:

-DISPLAY THREAD(*)

In this case, processing is terminated.

To correct the error, reduce the amount of CSA or ECSA virtual storage that is required for the DISPLAY THREAD command by performing one of the following actions:

  • Specify qualifiers, such as TYPE(INDOUBT), TYPE(ACTIVE), or TYPE(INACTIVE).
  • Specify specific connection-name, location-name, or luwid values.
MESSAGE LIMIT EXCEEDED. DISPLAY IS TRUNCATED.
The number of DISPLAY THREAD command messages exceeds the maximum number of permitted messages. The maximum number of messages is specified by the LIMIT option or the default value for the LIMIT option.
DISPLAY THREAD OUTPUT TO BE CONTINUED
DISPLAY THREAD command output directed to an MVS console must be continued in another group of messages. The continuation notice contains a unique command ID that is also displayed in the first line of the continuation.
DISPLAY THREAD OUTPUT TO BE CONTINUED (CMDID = command-id)

Compare the command ID values to confirm that the continuation is from the same report.

DISPLAY THREAD OUTPUT CONTINUED (CMDID = command-id)

Error messages

If the DISPLAY THREAD command fails, you receive one of the following messages:

csect-name DISPLAY THREADpkwname TERMINATED, DEFAULT UNAVAILABLE

The DISPLAY THREAD command statement did not contain all required parameters. Command processing terminates.

csect-name
The name of the control section that issued the message.
pkwname
The command primary keyword as entered by the requester.

One of the following items was not specified: connection-name, LOCATION, or LUWID.

Reenter the command with one of these parameters specified.

LOCATION OR LUWID KEYWORD INVALID WHEN DDF NOT STARTED
The DISPLAY THREAD TYPE(ACTIVE) command was issued with the keyword LOCATION or LUWID, but the distributed data facility (DDF) was not started. The LOCATION or LUWID keyword can be used only if DDF is in operation.

Command processing is complete.

INVALID PARAMETER WITH LUWID KEYWORD luwid-parameter

The DISPLAY THREAD TYPE(ACTIVE) or DISPLAY THREAD TYPE(INACTIVE) command was issued with the keyword LUWID and its required parameter list. However, one of the parameters was syntactically invalid as a logical unit of work identifier.

The command returns without processing.

Reenter the command with valid LUWID values.

SCOPE(GROUP) DISPLAY TERMINATED DUE TO IRLM TRUNCATION

The SCOPE(GROUP) keyword was specified, and IRLM truncated the responses gathered from other members. This error is a Db2 internal error.

The DISPLAY THREAD report is terminated and processing abnormally terminates.

Notify the system programmer and contact IBM Support to report the problem.

SCOPE(GROUP) DATA UNAVAILABLE

The SCOPE(GROUP) keyword was specified, and the IRLM NOTIFY to other members has returned a bad return code.

  SCOPE(GROUP) DATA UNAVAILABLE,
         IRLM RETURN CODE: retcode,
         IRLM REASON DATA: reason
retcode
Return code from IRLM on the Notify request.
reason
Reason code diagnostic information from IRLM on the Notify request.

System action

Processing continues.

Operator response

Review the information that is provided for each line of output and take any necessary action.