LUTYPE6.2 (APPC)
The general term used for the LUTYPE6.2 protocol is Advanced Program-to-Program Communication (APPC). In addition to enabling data communication between transaction-processing systems, the APPC architecture defines subsets that enable device-level products (APPC terminals) to communicate with host-level products and also with each other.
You can use APPC sessions for CICS®-to-CICS communication and for communication between CICS and other APPC systems or terminals.
Here is an overview of some of the principal characteristics of the APPC architecture.
Protocol boundary
The APPC protocol boundary is a generic interface between transactions and the SNA network. It is defined by formatted functions, called verbs, and protocols for using the verbs. Details of this SNA protocol boundary are given in the Systems Network Architecture publication Transaction Programmer's Reference Manual for LU Type 6.2.
CICS provides a command-level language that maps to the protocol boundary and enables you to write application programs that hold APPC conversations. Alternatively, you can use the Common Programming Interface Communications (CPI Communications) of the Systems Application Architecture® (SAA) environment.
- Mapped
- In mapped conversations, the data passed to and received from the APPC application program interface is user data. The user is not concerned with the internal data formats demanded by the architecture.
- Basic
- In basic conversations, the data passed to and received from the APPC application program interface is prefixed with a header, called a GDS header. The user is responsible for building and interpreting this header. Basic conversations are used principally for communication with device-level products that do not support mapped conversations, and which possibly do not have an application programming interface open to the user.
Synchronization levels
The APPC architecture provides three levels of synchronization. In CICS, these levels are known as Levels 0, 1, and 2. In SNA terms, these correspond to NONE, CONFIRM, and SYNCPOINT, as follows:
- Level 0 (NONE)
- This level is for use when communicating with systems or devices that do not support synchronization points, or when no synchronization is required.
- Level 1 (CONFIRM)
- This level allows conversing transactions to exchange private synchronization requests. CICS built-in synchronization does not occur at this level.
- Level 2 (SYNCPOINT)
- This level is the equivalent of full CICS syncpointing, including rollback. Level 1 synchronization requests can also be used.
EXEC CICS commands and CPI Communications support all three levels.
Program initialization parameter data
When a transaction initiates a remote transaction connected by an APPC session, it can send data to be received by the attached transaction. This data, called program initialization parameters (PIP), is formatted into one or more variable-length subfields according to the SNA architected rules. CPI Communications does not support PIP.
LU services manager
Multisession APPC connections use the LU services manager, the software component responsible for negotiating session binds, session activation and deactivation, resynchronization, and error handling. It requires two special sessions with the remote LU; these are called the SNASVCMG sessions. When these sessions are bound, the two sides of the LU-LU connection can communicate with each other, even if the connection is 'not available for allocation' for users.
A single-session APPC connection has no SNASVCMG sessions. For this reason, its function is limited. It cannot, for example, support level-2 synchronization.
Class of service
The CICS implementation of APPC includes support for “class of service” selection.
- Alternate routing: virtual routes for a given COS can be assigned to different physical paths (explicit routes).
- Mixed traffic: different kinds of traffic can be assigned to the same virtual route and, by selecting appropriate transmission priorities, undue session interference can be prevented.
- Trunking: explicit routes can use parallel links between specific nodes.
In particular, sessions can take different virtual routes, and thus use different physical links; or, the sessions can be of high or low priority to suit the traffic carried on them.
In CICS, APPC sessions are specified in groups called modesets, each of which is assigned a modename. The modename must be the name of a z/OS® Communications Server SNA LOGMODE entry (also called a modegroup), which can specify the class of service required for the session group. For more information, see ACF/Communications Server LOGMODE table entries for CICS.
Limited resources
For efficient use of some network resources (for example, switched lines), SNA allows for such resources to be defined in the network as limited resources. When a session is bound, SNA indicates to CICS whether the bind is over a limited resource. When a task using a session across a limited resource frees the session, CICS unbinds that session if no other task requires it.
Both single- and multi-session connections can use limited resources. For a multi-session connection, CICS does not unbind LU service-manager sessions until all modegroups in the connection have performed initial "change number of sessions" (CNOS) exchange. When CICS unbinds a session, CICS tries to balance the contention winners and losers. This balancing might result in CICS resetting an unbound session to be neither a winner or a loser.