CONFIGURATION SUMMARY report

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

 Summary Report for CONFIGURATION
 --------------------------------

 Local LU name: Z0A6AP01 Status: Active
 Local LU Resource Manager Name : *NONE*
 Local LU Resource Manager Token: *NONE*
 Generic Resource Name:  MVSLU
 Number of partners:        0
 Number of partner/mode pairs:        0
 Number of URs:             0
 Total Expressions of Interest:        0

 Local LU name: Z0A6AP02 Status: Active
 Local LU Resource Manager Name : *NONE*
 Local LU Resource Manager Token: *NONE*
 Generic Resource Name:  *NONE*
 Number of partners:        0
 Number of partner/mode pairs:        0
 Number of URs:             0
 Total Expressions of Interest:        0

 Local LU name: Z0A6AP03 Status: Active
 Local LU Resource Manager Name : ATB.USIBMZ0.Z0A6AP03.IBM
 Local LU Resource Manager Token: 01000001020DC0000000000300000001
 Generic Resource Name:  MVSLU3
 Number of partners:        0
 Number of partner/mode pairs:        0
 Number of URs:             0
 Total Expressions of Interest:        0

 Local LU name: Z0A6AP04 Status: Active
 Local LU Resource Manager Name : ATB.USIBMZ0.Z0A6AP04.IBM
 Local LU Resource Manager Token: 01000001020DC0000000000200000001
 Generic Resource Name:  *NONE*
 Number of partners:        2
 Number of partner/mode pairs:        2
 Number of URs:             3
 Total Expressions of Interest:        4

Local LU Name

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

Status

The status of the local LU is one of the following:

Pending

The local LU was waiting to be connected to the Virtual Telecommunications Access Method (VTAM) network. Possible reasons for the wait are as follows:

• The LU name entered after the ACBNAME operand in the APPCPMxx parmlib member did not exactly match the LU name defined to VTAM in SYS1.VTAMLST.
• An APPC definition statement for the LU name was not in SYS1.VTAMLST.
• VTAM was not active.
• The transaction scheduler associated with the LU was not active.

Pending Active

The local LU was about to become active. (In the output from the DISPLAY APPC, LU command, this status is included under PENDING LUs.)

Active

The local LU was connected to the VTAM network.

In termination

The local LU was being disconnected from the VTAM network.

Pending Outbound Only

The local LU was about to become outbound only. (In the output from the DISPLAY APPC,LU command, this status is included under PENDING LUs.)

Outbound only

The local LU was only capable of processing outbound TPs.

Unknown

The local LU configuration was not known.

Local LU Resource Manager Name

The name of the local LU, as it is known to RRS. If the VTAM APPL definition statement for this LU defines it as 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 *NONE*.

Local LU Resource Manager Token

The token of the local LU, as it is known to RRS. If the VTAM APPL definition statement for this LU defines it as capable of processing protected conversations, and APPC/MVS successfully registers the LU, RRS returns this token for the LU to use. If the LU is not defined as capable of processing protected conversations, the report displays *NONE*.

Generic Resource Name

The VTAM generic resource name associated with the LU. The generic resource name identifies a group of LUs that provide the same function. This name is specified on the GRNAME parameter of the LUADD statement in an APPCPMxx parmlib member. If a generic resource name has not been specified in parmlib, the report displays *NONE*.

Number of Partners

The number of partner LUs with which the local LU established sessions.

A local LU can establish sessions with one or more partner LUs. Partners can be on the same system or on remote systems.

Number of Partner/Mode Pairs

A logon mode establishes the session characteristics between a local LU and a partner LU. Each logon mode establishes a specific type of session. The unique combination of partner LU and logon mode defines a partner/mode pair.

A local LU and its partner can have more than one logon mode. For example, when one partner of a local LU has two logon modes, there are two partner/mode pairs. When the local LU has another partner with three logon modes, there is a total of five partner/mode pairs for the local LU.

Number of URs

The number of units of recovery in which the LU has expressed interest with RRS. A unit of recovery represents part of a TP's processing for a protected conversation. Expressing interest in a unit of recovery enables the LU to process Commit and Backout calls from TPs that allocate protected conversations.

Total Expressions of Interest

The total number of expressions of interest that the LU has made with RRS.