CONVERSATIONS SUMMARY report

Figure 1 is an example of the APPCDATA CONVERSATIONS SUMMARY report.

 Summary 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
  Number of conversations:        2

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

  TP name: APOLLO
  TP_ID: 06186D300000001A
  LU name: Z0A6AP04
  Work Unit ID: A0000005
  Number of conversations:        1

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

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

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

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

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

  TP name: TRACYB
  TP_ID: 06186FF000000023
  LU name: Z0A6AP02
  Work Unit ID:  N/A
  Number of conversations:        0

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

  TP name: *UNKNOWN*
  TP_ID: 0618715000000024
  LU name: Z0A6AP04
  Work Unit ID:  N/A
  Number of conversations:        0

Address Space ID

Information about the conversations for TPs in a particular address space follows the Address Space ID heading. The ASID is displayed as four hexadecimal digits after this heading. When the report displays information about conversations for TPs in all address spaces, the ASIDs appear in increasing numeric order.

Scheduler Name

The scheduler name is the name of the transaction scheduler that received and scheduled the work for the transaction program. If the scheduler was the APPC/MVS transaction scheduler, ASCH appears in this field. If a different scheduler was involved, a name representing that scheduler appears. When no TPs are running in an address space, N/A appears under the scheduler name.

TP Name

A TP is part of a distributed application that communicates with another program, also a TP. The communication between TPs is called a conversation. Conversations are started by a TP that issues an allocate call. A TP can converse with more than one other TP. The TP whose point-of-view is being considered is called the local TP. A 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 a local TP starts all conversations, its name is not available and this report displays *UNKNOWN*. If a partner TP starts a conversation with the local TP, the local TP name becomes available from the allocate call and is displayed in this report.

TP_ID

A TP_ID is a token that identifies a specific TP instance. A TP instance is created for an inbound conversation or by a request to allocate an outbound conversation from something other than a TP. A TP instance differs from a TP in that the TP is a program using communication functions and a TP instance is the actual processing of those functions in MVS™.

LU Name

An LU is a system interface to a SNA network. An LU on your system through which a local TP communicates is a local LU. LUs for partner TPs are partner LUs. Sessions, which allow program-to-program communication, are established between a local LU and partner LUs.

Work Unit ID

A work unit ID is an identifier for a TP that is assigned by the scheduler. This ID will appear on externals of the scheduler, such as a console display, to identify the work unit associated with this TP instance. If no work unit ID was used for the conversation, this value will be N/A.

Number of Conversations

A TP can converse with one or more partner TPs. There is no limit to the number of conversations other than the limit imposed by the number of available sessions.