Distributed Thread Detail (VTAM and TCP/IP Connections)
This panel provides information about VTAM® APPC threads, TCP/IP threads,
or RRSAF threads of an individual distributed thread. For VTAM APPC and TCP/IP conversations,
it additionally includes statistics about the distributed activity
of the thread.
VTAM APPC threads
The thread subtype determines the data that is displayed with the RSUM minor command.
This panel provides information
about VTAM APPC conversations.
________________ ZTDIST VTM O2 V540./C DB11 08/28/13 1:20:48 2
> Help PF1 Back PF3
>
> THREAD INFORMATION: Enter a selection letter on the top line.
> A-THREAD DETAIL B-LOCK COUNTS C-LOCK WAITS D-LOCKS OWNED E-GLOBAL LOCKS
> F-CURRENT SQL G-SQL COUNTS *-DISTRIBUTED I-BUFFER POOL J-GROUP BP
> K-PACKAGES L-RES LIMIT M-PARALLEL TASKS N-UTILITY O-OBJECTS
> P-CANCEL THREAD Q-DB2 CONSOLE R-DSN ACTIVITY S-APPL TRACE T-ENCLAVE
> U-LONG NAMES V-DB2 CON SRV W-ACCEL ACTIVITY
===============================================================================
> DISTRIBUTED THREAD DETAIL
PLAN
+ Thread: Plan=DSNESPRR Connid=TSO Corrid=HONG Authid=HONG
+ Attach: TSO Userid=HONG Region asid= 151
+ Dist : Type=DISTRIBUTED ALLIED, Luwid=DEIBMIPS.IPSAQB11.CBE010B90BCE=3620
+ Location : PMODBE1
rsum
+ Distributed VTAM APPC Conversations
+
+ VTAM VTAM Last VTAM Last VTAM Time Since Conv VTAM
+ Luname Modename APPC Req APPC Qual Last Req Status Session ID
+ -------- -------- --------- --------- ---------- ---------- ----------------
+ IPSASE11 IBMRDB UNKNOWN DATAFLU 06:23:48.6 NOT-ACTIVE C0CF1A6BA8F5ECEF
+ IPSARA21 IBMRDB UNKNOWN DATAFLU 06:23:48.8 NOT-ACTIVE E4CF19C081F5ABA1
+ IPSASB31 IBMRDB UNKNOWN DATAFLU 06:23:48.5 IN-VTAM E8CF19C083FB5F9E
+
+ Distributed SQL Statistics
+
+ Remote Location Name = PMODBE1
+ Remote Location Luname = IPSASE11
+
+ Protocol Used = SYSTEM Conversations Queued = 0
+ Conv Deallocated = 0
+ Indoubt/Remote = 0
+ Dist Local Elapsed = 06:23:48.809
+
+ SQL Row Message Byte Commit Abort Conv Blocks
+ ------- ------- ------- -------- ------- ------- ------- -------
+ Sent 2 0 5 1202 0 0 0 0
+ Recv 0 1 5 988 0 0 0 1
+
+ Remote Location Name = PMODA21
+ Remote Location Luname = IPSARA21
+
+ Protocol Used = SYSTEM Conversations Queued = 0
+ Conv Deallocated = 0
+ Indoubt/Remote = 0
+ Dist Local Elapsed = 00:00:00.126
+
+ SQL Row Message Byte Commit Abort Conv Blocks
+ ------- ------- ------- -------- ------- ------- ------- -------
+ Sent 2 0 5 1193 0 0 0 0
+ Recv 0 1 5 954 0 0 0 1
+
+ Remote Location Name = PMODB31
+ Remote Location Luname = IPSASB31
+
+ Protocol Used = SYSTEM Conversations Queued = 0
+ Conv Deallocated = 0
+ Indoubt/Remote = 0
+ Dist Local Elapsed = 00:00:00.311
+
+ SQL Row Message Byte Commit Abort Conv Blocks
+ ------- ------- ------- -------- ------- ------- ------- -------
+ Sent 3 0 7 1777 0 0 0 0
+ Recv 0 1 6 1154 0 0 0 1
+
+ Remote Location Name = ALL LOCATIONS
+
+ Protocol Used = SYSTEM Conversations Queued = 0
+ Conv Deallocated = 0
+ Indoubt/Remote = 0
+ Dist Local Elapsed = 00:00:00.552
+
+ SQL Row Message Byte Commit Abort Conv Blocks
+ ------- ------- ------- -------- ------- ------- ------- -------
+ Sent 7 0 17 4172 0 0 0 0
+ Recv 0 3 16 3096 0 0 0 3
=============================================================================== Fields
Distributed VTAM APPC Conversations
The
following fields are displayed when the thread has a distributed relationship
with a remote Db2 subsystem.
One line of output is displayed for each active conversation.
- VTAM Luname
- The VTAM logical unit name of the remote Db2 subsystem that is the partner on this VTAM APPC conversation.
- VTAM Modename
- The VTAM logmode in use by the APPC conversation. For database access threads, the logmode name exists and originates on the MVS system of the remote requester.
- Last VTAM APPC Req
- The most recent VTAM APPC request that was issued on the conversation.
- Last VTAM APPC Qual
- The most recent VTAM APPC qualifier that was issued on the conversation.
- Time Since Last Req
- The elapsed time since the last APPC command was issued on the conversation.
- Conv Status
- The status of the conversation.
- WAIT-VTAM
- The conversation is suspended and waiting for a VTAM response.
- IN-VTAM
- The conversation is active within VTAM.
- NOT-ACTIVE
- The conversation is inactive-neither waiting for a VTAM response nor active in VTAM.
- VTAM Session ID
- The VTAM session identifier in use by the conversation.
Distributed SQL statistics
The
following group of fields occurs for each remote DB2 location with which the thread has communicated,
either as a requester or a server. Each sent/received field generates
two rows of output; the top row is the sent value, and the bottom
row is the received value.
- Remote Location Name
- The name of a remote location with which the local DB2 has communicated.
- Remote Location Luname
- The logical unit name of the location
specified in the
Remote Location Name
field. This field is not displayed for distributed TCP/IP threads. - Protocol Used
- The type of distributed protocol being used. The values are SYSTEM, APPLICATION, or BOTH, depending on whether system directed access, application directed access, or both are being used.
- Conversations Queued
- The number of conversation requests queued by DDF waiting for allocation.
- Conv Deallocated
- The number of conversations deallocated.
- Indoubt/Remote
- The number of threads that went indoubt with the remote location as coordinator.
- Dist Local Elapsed
- The time the thread has spent waiting for a response to a remote SQL request (includes remote Db2 processing time, VTAM processing time, and network time). The time is calculated from the point of thread creation (or Db2 signon if the thread is reused). This field is displayed only for distributed allied threads.
- SQL Sent/Recv
- The number of SQL calls sent to and from the remote location since thread creation or Db2 signon.
- Row Sent/Recv
- The number of rows sent to and from the remote location since thread creation or Db2 signon.
- Message Sent/Recv
- The number of VTAM messages sent to and from the remote location since thread creation or DB2 signon.
- Byte Sent/Recv
- The number of bytes sent to and from the remote location since thread creation or Db2 signon.
- Commit Sent/Recv
- The number of Commits sent to and from the remote location since thread creation or Db2 signon.
- Abort Sent/Recv
- The number of aborts sent to and from the remote location since thread creation or Db2 signon.
- Conv Sent/Recv
- The number of conversations sent to and from the remote location since thread creation or Db2 signon.
- Blocks Sent/Recv
- The number of blocks sent and received using block fetch.
Distributed TCP/IP threads
This
panel provides information about TCP/IP conversations.
________________ ZTDIST VTM O2 V540./C DB11 08/28/13 1:14:57 2
> Help PF1 Back PF3
>
> THREAD INFORMATION: Enter a selection letter on the top line.
> A-THREAD DETAIL B-LOCK COUNTS C-LOCK WAITS D-LOCKS OWNED E-GLOBAL LOCKS
> F-CURRENT SQL G-SQL COUNTS *-DISTRIBUTED I-BUFFER POOL J-GROUP BP
> K-PACKAGES L-RES LIMIT M-PARALLEL TASKS N-UTILITY O-OBJECTS
> P-CANCEL THREAD Q-DB2 CONSOLE R-DSN ACTIVITY S-APPL TRACE T-ENCLAVE
> U-LONG NAMES V-DB2 CON SRV W-ACCEL ACTIVITY
===============================================================================
> DISTRIBUTED THREAD DETAIL
PLAN
+ Thread: Plan=DISTSERV Connid=SERVER Corrid=db2bp.exe Authid=HONG
+ Dist : Type=DATABASE ACCESS, Luwid=G941543B.KB08.130827231306=3670
+ Location : ::FFFF:9.65.84.59
+ Host Name:sig-9-65-84-59.mts.ibm.com
rsum
+ Distributed TCP/IP Data
+Location Port Ctbuser Srvclsnam Prod ID
+--------------------------------------- ------ -------- ---------- --------
+::FFFF:9.65.84.59 11511 hong NT SQL09050
+
+ End User ID :
+ hong
+
+ Transaction Name :
+ db2bp.exe
+
+ Workstation Name :
+ IBM-67119346B51
+
+ Account Loc Name :
+ N/P
+
+ Account Suffix :
+ N/P
+
+ Account String :
+ N/P
+
+ Distributed SQL Statistics
+
+ Remote Location Name = ::FFFF:9.65.84.59
+
+ Protocol Used = SYSTEM Conversations Queued = 0
+ Conv Deallocated = 0
+ Indoubt/Remote = 0
+
+ SQL Row Message Byte Commit Abort Conv Blocks
+ ------- ------- ------- -------- ------- ------- ------- -------
+ Sent 0 815 21 474788 0 0 0 14
+ Recv 17 0 21 2302 0 0 1 0
===============================================================================
Fields
Distributed TCP/IP Data: The following fields are displayed when the thread has a distributed relationship with a remote DB2 subsystem. One line of output is displayed for each active conversation. TCP/IP activity is grouped by remote TCP/IP locations.The following fields are shown for each remote location with which this thread has communicated, as either a remote requestor (if a distributed allied thread) or server (if a database access thread).- Location
- The IP address in dotted decimal notation.
- PORT
- The IP port number used in the connection.
- Ctbuser
- The binder's AuthID.
- Srvclsnam
- The service class name as taken from the Accounting Record MVS Account Code and DDF Information Data Section (QMDA).
- Prod ID
- The Product ID parameter having the form PPPVVRRM, where PPP is the Product, VV is the Version, RR is the Release, and M is the Modification.
- IP Addr
- The IP address in Hexadecimal notation.
- Workstation name
- The end user's workstation name.
- Account Loc Name
- The Db2 LOCATION name for the Db2 system that created the QMDAINFO values if QMDALOCN is truncated.
- Account Suffix
- One of the following items apply:
- The MVS accounting string that is associated with the MVS address space of the Db2 SQL application.
- The account suffix. The maximum length of this field is 200 bytes. This environment variable is the user-supplied portion (suffix) of the accounting string.
- Account String
- The extended accounting string area.
- If QMDAASTR is defined by QMDAINFO, this area contains all the remaining bytes beyond position 142 for QMDAACCT.
- If QMDAASTR is defined by QMDASQLI, this area contains all the remaining bytes beyond position 200 for QMDASUFX.
- Otherwise, this area contains all bytes beyond position 247 for QMDAASTR.
- Transaction name
- The name of the transaction.
- TCP/IP Userid
- The TCP/IP user ID.
Distributed RRSAF threads
This panel provides information about RRSAF
conversations.
________________ ZTDIST VTM O2 V540./I SE11 07/10/13 14:38:16 2
> Help PF1 Back PF3
>
> THREAD INFORMATION: Enter a selection letter on the top line.
> A-THREAD DETAIL B-LOCK COUNTS C-LOCK WAITS D-LOCKS OWNED E-GLOBAL LOCKS
> F-CURRENT SQL G-SQL COUNTS *-DISTRIBUTED I-BUFFER POOL J-GROUP BP
> K-PACKAGES L-RES LIMIT M-PARALLEL TASKS N-UTILITY O-OBJECTS
> P-CANCEL THREAD Q-DB2 CONSOLE R-DSN ACTIVITY S-APPL TRACE T-ENCLAVE
> U-LONG NAMES V-DB2 CON SRV W-ACCEL ACTIVITY
===============================================================================
> DISTRIBUTED THREAD DETAIL
PLAN
+ Thread: Plan=RRSFSE11 Connid=RRSAF Corrid=A00000000000 Authid=HONG
+ Attach: RRSAF JOB Name=HONGRSAF JOB Asid= 56
+ Package: RRSFSE11 Collection=RRSFSE11
+ Luwid=DEIBMIPS.IPSASE11.CBA37B8A05D4=15
rsum
+ Distributed RRSAF Data
+ Location Port Ctbuser Srvclsnam Prod ID
+ --------------------------------------- ------ -------- ---------- --------
+ N/A N/A HONG N/A N/A
+
+
+
+ End User ID :
+ LU-LONG-USER-ID-THAT-IS-UP-TO-128-BYTES-AND-IT-IS-SET-IN-THE-MIDDLE-OF-THI
+ S-PROGRAM-USING-SET-CLIENT-INFO-CALL
+
+ Transaction Name :
+ LP-LONG-APPLICATION-NAME-THAT-IS-UP-TO-255-BYTES-THIS-IS-SET-IN-THE-MIDDLE
+ -OF-THE-PROGRAM-USING-SET-CLIENT-INFO-CALL
+
+ Workstation Name :
+ LW-LONG-WORKSTATION-NAME-THAT-IS-UP-TO-255-BYTES-THIS-IS-SET-IN-THE-MIDDLE
+ -OF-THE-PROGRAM-USING-SET-CLIENT-INFO-CALL
+
+ Account Loc Name :
+ N/P
+
+ Account Suffix :
+ WHICH-IS-A-FREE-FORMAT-ACCOUNT-INFORMATION-IT-IS-SET-IN-THE-MIDDLE-OF-THE-
+ PROGRAM-USING-SET-CLIENT-INFO-CALL
+
+ Account String :
+ N/P
=============================================================================== Distributed RRSAF Data: The Resource Recovery Services attachment facility (RRSAF) is a Db2 attachment facility that relies on a z/OS® component called Resource Recovery Services (z/OS RRS). z/OS RRS provides system-wide services for coordinating two-phase commit operations across z/OS subsystems.
RRSAF information is
limited to the following fields:
- Ctbuser
- The binder's AuthID.
- Workstation name
- The end user's workstation name. Db2 applications which use the RRSAF interface can invoke the DB2 DSNRLI function SET_CLIENT_ID to pass this value.
- UserID
- The end user's User ID. Db2 applications which use the RRSAF interface can invoke the DB2 DSNRLI function SET_CLIENT_ID to pass this value.
- Transaction name
- The name of the transaction. Db2 applications which use the RRSAF interface can invoke the DB2 DSNRLI function SET_CLIENT_ID to pass this value.
Navigation
For additional
information about
- related topics, select one of the options at the top of the panel.
- other topics, use the PF keys.
Fields
Thread identifier: This information identifies the thread to which
the information in this panel applies.
- Plan
- The Db2 plan name of the active thread.
- Connid
- The Db2 connection identifier of the active thread.
- Corrid
- The Db2 correlation identifier of the active thread. If the correlation is not set, N/A is displayed.
- Authid
- The Db2 authorization identifier of the active thread.
- Attach
- Depending on the type of connection, the appropriate information is displayed.
Package identifier: This information identifies the package to
which the information in this panel applies.
Distributed
thread identifier: The following fields are displayed when the
thread has a distributed relationship with a remote DB2 subsystem.
- Type
- The distributed thread type:
- Distributed Allied
- A requesting thread that has issued an SQL call to a remote DB2 location.
- Database Access
- A responding thread that is serving a remote DB2 location by responding to an SQL call.
- Location
- The remote location name.
- Luwid
- Logical unit of work indicator for the distributed thread. It
has the following format (separated by periods):network-name.originating-VTAM-luname.unique-identifier=token
- network-name
- The network name
- originating-VTAM-luname
- The originating VTAM LUNAME
- unique-identifier
- The unique identifier
- token
- You can use the token instead of luwid in any DB2 command that accepts luwid as input.