CONVERSATIONS DETAIL report

For each TP in an address space, the CONVERSATIONS DETAIL report duplicates the summary report. In addition, the report displays the following topics for each conversation:
  • Conversation ID
  • Conversation correlator
  • Partner TP name
  • Attach user ID
  • Conversation type
  • Sync level
  • Unit of recovery identifier (URID)
  • Logical unit of work identifier (LUWID)
  • Resource manager name
  • Attached by partner TP
  • Allocated to partner LU
  • LOGON mode
  • Current state
  • Time of day
The following is an example of the APPCDATA CONVERSATIONS DETAIL report:
 Detail Report for CONVERSATIONS
 -------------------------------
 Address space ID (ASID): '0022'X
 Scheduler name: ASCH

  TP name: TBDRIVER
  TP_ID: 0618691000000017
  LU name: Z0A6AP04
  Work Unit ID: A0000003

   Conversation ID: 0618F3F800000018 Correlator: 0618F3F800000018
   Partner TP name: TBDRIVER
   Attach user ID: DBUTLER
   Conversation type: BASIC     Sync level: SYNCPT
   URID : AD49C2737EEFC0000000000401020000
   LUWID: USIBMZ0.Z0A4AP03 C26D566FB104 0001
   Resource Manager Name  : ATB.USIBMZ0.Z0A6AP04.IBM
   Attached by  Partner LU: USIBMZ0.Z0A4AP03  Logon mode: TRANPAR
   Current state: SYNCPT DEALLOCATE

   Conversation ID: 0618F86000000019 Correlator: 0618F86000000019
   Partner TP name: TBDRIVER
   Attach user ID: DBUTLER
   Conversation type: BASIC     Sync level: SYNCPT
   URID : AD49C2737EEFC0000000000401020000
   LUWID: USIBMZ0.Z0A4AP03 C26D566FB104 0001
   Resource Manager Name  : ATB.USIBMZ0.Z0A6AP04.IBM
   Allocated to Partner LU: USIBMZ0.Z0A4AP03  Logon mode: TRANPAR
   Current state: DEFER RECEIVE

 Address space ID (ASID): '0023'X
 Scheduler name: ASCH

  TP name: APOLLO
  TP_ID: 06186D300000001A
  LU name: Z0A6AP04
  Work Unit ID: A0000005

   Conversation ID: 061905980000001C Correlator: 0000000000000000
   Partner TP name: APOLLO
   Attach user ID: DBUTLER
   Conversation type: BASIC     Sync level: NONE
   URID :  N/A
   LUWID:  N/A
   Resource Manager Name  :  N/A
   Attached by  Partner LU: USIBMZ0.Z0A6AP04  Logon mode: TRANPAR
   Current state: RECEIVE
   Waiting for data       TOD: 08/08/1996 18:19:57.410602

 Detail Report for CONVERSATIONS
 -------------------------------
 Address space ID (ASID): '0022'X
 Scheduler name: ASCH

  TP name: TBDRIVER
  TP_ID: 0618691000000017
  LU name: Z0A6AP04
  Work Unit ID: A0000003

   Conversation ID: 0618F3F800000018 Correlator: 0618F3F800000018
   Partner TP name: TBDRIVER
   Attach user ID: DBUTLER
   Conversation type: BASIC     Sync level: SYNCPT
   URID : AD49C2737EEFC0000000000401020000
   LUWID: USIBMZ0.Z0A4AP03 C26D566FB104 0001
   Resource Manager Name  : ATB.USIBMZ0.Z0A6AP04.IBM
   Attached by  Partner LU: USIBMZ0.Z0A4AP03  Logon mode: TRANPAR
   Current state: SYNCPT DEALLOCATE

   Conversation ID: 0618F86000000019 Correlator: 0618F86000000019
   Partner TP name: TBDRIVER
   Attach user ID: DBUTLER
   Conversation type: BASIC     Sync level: SYNCPT
   URID : AD49C2737EEFC0000000000401020000
   LUWID: USIBMZ0.Z0A4AP03 C26D566FB104 0001
   Resource Manager Name  : ATB.USIBMZ0.Z0A6AP04.IBM
   Allocated to Partner LU: USIBMZ0.Z0A4AP03  Logon mode: TRANPAR
   Current state: DEFER RECEIVE

 Address space ID (ASID): '0023'X
 Scheduler name: ASCH

  TP name: APOLLO
  TP_ID: 06186D300000001A
  LU name: Z0A6AP04
  Work Unit ID: A0000005

   Conversation ID: 061905980000001C Correlator: 0000000000000000
   Partner TP name: APOLLO
   Attach user ID: DBUTLER
   Conversation type: BASIC     Sync level: NONE
   URID :  N/A
   LUWID:  N/A
   Resource Manager Name  :  N/A
   Attached by  Partner LU: USIBMZ0.Z0A6AP04  Logon mode: TRANPAR
   Current state: RECEIVE
   Waiting for data       TOD: 08/08/1996 18:19:57.410602

 Address space ID (ASID): '0025'X
 Scheduler name:  N/A

  TP name: *UNKNOWN*
  TP_ID: 06186BD000000019
  LU name: Z0A6AP04
  Work Unit ID:  N/A

   Conversation ID: 061901300000001B Correlator: 0000000000000000
   Partner TP name: APOLLO
   Attach user ID: DBUTLER
   Conversation type: BASIC     Sync level: NONE
   URID :  N/A
   LUWID:  N/A
   Resource Manager Name  :  N/A
   Allocated to Partner LU: USIBMZ0.Z0A6AP04  Logon mode: TRANPAR
   Current state: SEND

 Address space ID (ASID): '0026'X
 Scheduler name:  N/A

  TP name: *UNKNOWN*
  TP_ID: 06186E900000001B
  LU name: Z0A6AP04
  Work Unit ID:  N/A

   Conversation ID: 06190A000000001D Correlator: 06190A000000001D
   Partner TP name: MARINER
   Attach user ID: DBUTLER
   Conversation type: BASIC     Sync level: SYNCPT
   URID : AD49C3B27EEFC2800000000501020000
   LUWID: USIBMZ0.Z0A6AP04 C3B2F7069180 0001
   Resource Manager Name  : ATB.USIBMZ0.Z0A6AP04.IBM
   Allocated to Partner LU: USIBMZ0.Z0A6AP04  Logon mode: TRANPAR
   Current state: SEND

 Address space ID (ASID): '0027'X
 Scheduler name:  N/A

  TP name: TRACYB
  TP_ID: 06186FF000000023
  LU name: Z0A6AP02
  Work Unit ID:  N/A
  No conversations to be processed.

 Address space ID (ASID): '0028'X
 Scheduler name:  N/A

  TP name: *UNKNOWN*
  TP_ID: 0618715000000024

  LU name: Z0A6AP04
  Work Unit ID:  N/A
  No conversations to be processed.
Conversation ID
The conversation ID is an identifier that is supplied and maintained by the system. It is sometimes called a resource ID. When a TP successfully allocates a conversation, the system returns a conversation ID that uniquely identifies that conversation. Transaction programs specify that ID whenever they issue a call to each other.
Conversation Correlator
A conversation correlator is used to help restore protected resources to a consistent state following the failure of an LU, session, or conversation.

The conversation correlator is supplied and maintained by the LU. If no conversation correlator was used, this value will be zeros.

Partner TP Name
The name of the partner TP. A partner TP is a program with which another TP, called a local TP, has a conversation. A TP whose point-of-view is being considered is the local TP. The TP with which the local TP is conversing is called a partner TP. The partner TP can be on the same system as the local TP, or on a remote system. The name of the TP that starts a conversation is usually not known because the allocate call specifies only the name of the TP to be attached. When the local TP starts a conversation with a partner TP, the partner TP name is known and is displayed in this report. When a partner TP starts the conversation, its name is not known and *UNKNOWN* is displayed in this report.
Attach User ID
The attach user ID is the userid that was passed to the partner LU to indicate where an attached TP was running. If the conversation was started by the local TP, the userid displayed is the ID under which the partner TP was running. If the conversation was started by the partner TP, the user ID displayed is the ID under which the local TP was running.
Conversation Type
A TP can carry on two types of conversations:
Mapped
A conversation that allows the exchange of arbitrary data records. A mapped conversation call conceals from the application program the logical-record data-stream format required in a basic conversation.
Basic
A conversation that contains logical records that include 2-byte fields (LL). The LLs specify the amount of data to follow before the next LL.

Basic conversations are generally used by LU service programs that provide user services.

When the conversation type is not known, *UNKNOWN* is displayed.

Sync Level
Sync level is the level of synchronization between programs in a distributed transaction. APPC/MVS supports the following levels of synchronization:
None
There is no synchronization of activities in a distributed transaction.
Confirm
Allows a TP to use the confirm call to synchronize activities with a partner TP.
Syncpt
Allows a TP to perform sync point processing on this conversation. The TP and its partner can issue Commit and Backout calls, and recognize returned parameter values relating to resource recovery processing.

When the sync level is not known, *UNKNOWN* is displayed.

URID
The identifier for a unit of recovery. A unit of recovery represents part of a TP's processing for a protected conversation. If the conversation is not a protected conversation, the report displays N⁄A for this field.
LUWID
A logical unit of work ID is an identifier for the processing a program performs from one sync point to the next. If the conversation is not a protected conversation, the report displays N⁄A for this field.
Resource Manager Name
The name of the local LU, as it is known to RRS. If the LU is capable of processing protected conversations, APPC/MVS supplies this resource manager name when registering the LU with RRS. If the LU is not defined as capable of processing protected conversations, the report displays N⁄A for this field.
Attached by Partner LU
The name of the partner LU where the conversation originated. Conversations can be attached by the partner LU or allocated to the partner LU, depending on where a conversation originates. When a conversation was attached by a partner LU, the partner TP started the conversation and issued the allocate call to the local TP.

The partner LU name might be a network-qualified LU name; that is, the combined network ID and network LU name (two 1-8 byte Type A character strings, concatenated by a period: network_ID.network_LU_name). The partner LU name is network-qualified if the network ID is known; if not, only the network LU name appears in the report.

Allocated to Partner LU
The name of the partner LU where the conversation was received is displayed in this field. Conversations can be attached by the partner LU or allocated to the partner LU, depending on where a conversation originates. When a conversation was allocated to a partner LU, the local TP started the conversation and issued the allocate call to the partner TP.

The partner LU name might be a network-qualified LU name; that is, the combined network ID and network LU name (two 1-8 byte Type A character strings, concatenated by a period: network_ID.network_LU_name). The partner LU name is network-qualified if the network ID is known; if not, only the network LU name appears in the report.

Logon Mode
A logon mode defines a particular set of session characteristics for the conversation. The characteristics include the class of service to be used on the conversation and the synchronization level. Logon modes are defined by a system administrator for each partner LU with which the local LU communicates. There can be more than one logon mode defined for a single partner LU.
Current State
The current state is the state of the conversation at the time the dump was taken. Possible states are:
  • Reset
  • Initialize
  • Send
  • Receive
  • Send pending
  • Confirm
  • Confirm and send
  • Confirm and deallocate
  • Defer receive
  • Defer deallocate
  • Syncpt
  • Syncpt send
  • Syncpt deallocate
  • *UNKNOWN*
For certain states, a message might also appear. Possible messages are:
  • Waiting for data
  • Waiting for confirm
  • Data available to be received.
TOD (Time of Day)
The TOD field is displayed when the TP was in a wait state at the time of the dump. The time displayed is the time the program began the wait. A TP can be in a wait state after it requests data or after it issues a CONFIRM call. The TOD field displays the date and time in the format mm⁄dd⁄yyyy hour:minutes:seconds:microseconds.
Parent topic: APPCDATA CONVERSATIONS subcommand output