Db2 Thread Detail Long Names

Use these attributes to view detailed information about long names for a specific thread.

Accounting Info The z/OS accounting string that is associated with the Db2 SQL application's z/OS address space. (Field name: NMDAACCT). The information comes from the ACCT= parameter on the job statement.
  • If the ACCT= parameter is blank, the information on the EXEC statement is used.
  • TSO logon accounting information is present only if there is a value in the account field on the TSO Logon panel.
  • z/OS allows multiple fields to be supplied in the accounting string. When multiple fields are present in the accounting string, Db2 delimits these fields with an X'FF' value.
The following example shows three z/OS accounting fields ACCT=(X,Y,Z). In this example, Db2 creates a 5-byte string of "XDYDZ" where "D" represents the X'FF' delimiter. This field is not the same as the CICS accounting token. If QMDACTYP is SASS (connection type=CICS), and ACCOUNTREC is UOW or TASK in the DB2CONN or DB2ENTRY resource definitions, the CICS token is available in QWHCTOKN.
Accounting String The accounting string. (Field name: NMDAASTR).
  • For local Db2 threads, the format of the accounting string is shown in QMDAINFO.
  • For database access threads, the accounting string contains the accounting string sent by the requester.
  • The QMDAPRID value identifies which product produced the accounting string.
    • If the requester is Db2, the accounting string is defined in QMDAINFO.
    • If QMDAPTYP is DSN, QMDAINFO defines the format.
    • If QMDAPTYP is SQL, JCC, or QSQ, QMDASQLI defines the format.
    • If QMDAPTYP is HTP or HTS, QMDAREST defines the format.
    • If QMDAPTYP is DFH, QMDACICS defines the format.
    • Otherwise, the format is undefined.

Accounting Suffix The accounting suffix. (Field name: NMDASUFX). The maximum length of this field is 200 bytes. This field is the user-supplied portion (suffix) of the accounting string. An example is "DEFAULT_DRDA". A value of zero in QMDASFLN indicates there is no account suffix.

ACE Address The agent control element (ACE) of the thread that was used when this record was written. (Field name: NTHACE). An ACE is an identifier that is unique to a given thread for the life of the thread. Using the ACE values, it is possible to separate out trace records from concurrent unrelated threads. When a thread is terminated, the ACE value is freed and can be used later by a subsequent thread. There are times when an ACE value in the data indicates that the function performed under the ACE in NTHACE is actually being performed on behalf of another ACE, as indicated by the ACE value in the data section. An example of this is when a sequential prefetch read is done by a Db2 service task on behalf of a thread.

Authorization ID The initial primary authorization ID. (Field name: NTHAUTH).
  • For TSO: The logon ID.
  • For batch: The user ID on the job statement.
  • For RRSAF:
    If the following conditions are true, RRSAF uses the value in ACEEUSRI as the initial primary authorization ID:
    • The system authorization facility (SAF) and a security product, such as RACF, is used.
    • There is an ACEE associated with the job step TCB or with the AXSB.
    • The first 7 characters of the job step user ID match the first 7 characters of the value in ACEEUSRI.

    If any of the above conditions are not true, then the initial primary authorization ID is the value in ASXBUSER.

  • For IMS (message-driven regions): SIGNON-ID, LTERM, ASXBUSR, OR PSB NAME.
  • For IMS (control regions): USER-ID on job statement, or RACF, started procedure entry if RACF is used.
  • For CICS: USERID, OPID, GROUP, SIGN, or TERM, or TX, as specified in the DB2ENTRY resource definition.
  • For z/OS OPERATOR commands and Db2 system internal agents: = 'SYSOPR'.
  • For a distributed application server (AS):
    • If the application requester (AR) is a Db2 system, this is the same value that was assigned at the AR.
    • If the application requester is not a Db2 system, this is the user ID that was used to make the initial connection with the application server.
The user ID is obtained in one of the following ways:
  • Passed by the requester in the allocate conversation flow (FMH5).
  • Passed by the requester in the DRDA security flow.
  • Derived by the server from the RACF passticket.
  • Provided by the requester in the DRDA security flow.

Authorization id The primary authorization ID from a connection or signon. (Field name: NWHCAID). For z/OS operator commands and Db2 system internal agents, the value is SYSOPR. Secondary authorization IDs might be the RACF groups associated with this primary authorization ID. The SQL ID is initially set to this primary authorization ID. The connection authorization exit and the signon authorization exit can change the primary authorization ID so that it is not the same as the original primary authorization ID (QWHCOPID). Distributed authorization ID translation can also change the primary authorization ID. If QWHCAID_OFF is not 0, this value is truncated.

Connection ID The connection name. Not valid on end of memory and reflects the z/OS home ASID connection name. (Field name: NTHCONN).
  • For batch: 'BATCH'
  • For TSO: 'TSO'
  • For QMF: 'DB2CALL'
  • For UTILITY: 'UTILITY'
  • For DB2 INTERNAL: Db2 subsystem ID
  • For IMS: IMS-ID
  • For CICS: CICS-ID
  • For RRSAF: RRSAF
For distributed database access threads:
  • For threads from a Db2 requester, this field contains the connection name of the thread at the requesting location.
  • For threads using the DRDA protocol from a non-Db2 requester, this field contains the constant 'SERVER'.
Correlation ID The correlation ID value. (Field name: NTHCORR).
  • For batch: JOBNAME
  • For TSO: LOGON-ID
  • For IMS/VS: PST#.PSBNAME
  • For CICS: CONNECTION_TYPE.THREAD_TYPE.THREAD_#.TRAN-ID
  • For RRSAF: CORRELATION-ID value from signon function
  • For threads from a Db2 requester, this field contains the CORRELATION-ID name of the thread at the requesting location.
  • For threads using the DRDA protocol from a non-Db2 requester, this field contains the first 12 characters in the DDM external name (EXTNAM) parameter of the DDM EXCSAT command received as part of the SQL CONNECT.

Correlation Token The correlation token. (Field name: NWHCCTKN).

Data Sharing Group The data sharing group name.

DB2 Subsystem The Db2 subsystem ID.

DB2 Version The Db2 version.

DSG Member Name The data sharing group (DSG) member name.

End User ID The user ID of the workstation end user. (Field name: NWHCEUID). This user ID can be different from the authorization ID used to connect to Db2. This field contains blanks if the client did not supply this information.

Filler The pad field. (Field name: FILLER01).

Interval Start The start time of this interval.

Logical Unit of work ID The logical unit of work ID (LUWID) as defined for the LU 6.2 interface. (Field name: NTHLUW). The LUWID uniquely identifies the thread within the network, and consists of the following:
A fully qualified network name (QWHSLUNM)
The fully qualified network name is a maximum 16-bytes in length, consisting of two 8-character fields, QWHSNID and QWHSLUNM, that together uniquely identify a client system. The LUWID remains the same on IMS, CICS, and RRSAF thread reuse. Second part of network name (see QWHSLWID).
An LUW instance number (QWHSLUUV)
The instance number is displayed as 12 hex characters. When concatenated with the fully qualified network name, it uniquely identifies a distributed thread.
Note: Though this field might appear to be a timestamp, it is not to be processed as one. For more information. See the -DISPLAY THREAD command in the Command Reference.
An LUW sequence number
The LUW sequence number identifies the last COMMIT scope in which the logical unit participated. This number is incremented whenever a thread commits or is rolled back.

MVS System ID The MVS identifier.

Original Appl UserID The original application user ID. (Field name: NWHCOAUD).

Original Operator Id The initial primary authorization ID. (Field name: NWHCOPID).
  • For TSO: The logon ID.
  • For batch: The user ID on the job statement.
  • For RRSAF:
    If the following conditions are true, RRSAF uses the value in ACEEUSRI as the initial primary authorization ID:
    • The system authorization facility (SAF) and a security product, such as RACF, is used.
    • There is an ACEE associated with the job step TCB or with the AXSB.
    • The first 7 characters of the job step user ID match the first 7 characters of the value in ACEEUSRI.

    If any of the above conditions are not true, then the initial primary authorization ID is the value in ASXBUSER.

  • For IMS (message-driven regions): SIGNON-ID, LTERM, ASXBUSR, OR PSB NAME.
  • For IMS (control regions): USER-ID on job statement, or RACF, started procedure entry if RACF is used.
  • For CICS: USERID, OPID, GROUP, SIGN, or TERM, or TX, as specified in the DB2ENTRY resource definition.
  • For z/OS OPERATOR commands and Db2 system internal agents: = 'SYSOPR'.
  • For a distributed application server (AS):
    • If the application requester (AR) is a Db2 system, this is the same value that was assigned at the AR.
    • If the application requester is not a Db2 system, this is the user ID that was used to make the initial connection with the application server.
The user ID is obtained in one of the following ways:
  • Passed by the requester in the allocate conversation flow (FMH5).
  • Passed by the requester in the DRDA security flow.
  • Derived by the server from the RACF passticket.
  • Provided by the requester in the DRDA security flow.

Originating System The managed system name of the agent. Valid format is alphanumeric, with a maximum of 32 characters; example, DB91:SYS1:DB2.

Plan Name The plan name. (Field name: NTHPLAN). It is blank for Db2 command thread; otherwise:
  • For SPUFI with cursor stability: 'DSNESPCS'.
  • For SPUFI with repeatable read: 'DSNESPRR'.
  • For TSO: The application plan name.
  • For IMS: The application plan name. IMS and CICS commands have a blank plan name.
  • For CICS: The application plan name. IMS and CICS commands have a blank plan name.
  • For RRSAF, create thread with the collection parameter: '?RRSAF '.
  • For QMF: 'DSQPLAN'.
  • For Distributed Database Access threads:
    • For threads using the DRDA protocol from a requester, this field contains the plan name being executed at the requesting location.
    • For threads using the DRDA protocol from a non-Db2 requester or from a Db2 2.3 requester, this field contains the constant 'DISTSERV'.
  • For binding: 'DSNBIND' (system plan)
  • For utility: 'DSNUTIL ' (system plan)
  • For authorization: 'ACT' + X'0000000000' (system plan)
  • For unallocated threads and miscellaneous Db2 system service tasks: 'BCT' + X'0000000000' (system plan)
  • For startup: 'STARTCT' + X'00' (system plan)

Role Name The role name that is associated with the authorization ID. (Field name: NWHCROLE).

Thread End Time The ending store clock value. (Field name: NTHETIME). You can use this field with the field NTHSTIME (beginning store clock value) to determine the elapsed time of an application. See comments on NTHSTIME for more information.

Thread Start Time Beginning store clock value (STCK) for the period covered by this accounting record. (Field name: NTHSTIME). You can determine the elapsed time of the application by subtracting this field from QWACESC (ending store clock value). Threads that do not terminate (such as CICS primed threads and IMS wait-for-input message regions) can have an ending clock value that includes the time the thread was inactive and waiting to perform work.

Thread Type The connecting system type code (in hexadecimal). This field can have a null value. (Field name: NTHATYPE). For example, this field contains a null value for some utilities.

Transaction Name The transaction or application name that the end user is running. (Field name: NWHCEUTX). This identifies the application that is currently running, not the product that is used to run the application. This field contains blanks if the client did not supply this information.

Trusted Context The trusted context name. (Field name: NWHCTCXT).

Workstation Name The end user's workstation name. (Field name: NWHCEUWN). This field contains blanks if the client did not supply this information.