Selecting the protocol
CICS® provides three different protocols that support distributed transaction processing. These protocols define the rules under which two transactions can communicate with each other.
- APPC (advanced program-to-program communication, sometimes referred to as LUTYPE6.2)
- MRO (multiregion operation)
- LUTYPE6.1 (logical unit type 6.1).
Both APPC and LUTYPE6.1 are protocols defined by SNA. They are therefore more widely available for communicating with non-CICS systems. LUTYPE6.1 is the predecessor of APPC; so you should, if possible, avoid using LUTYPE6.1 for new applications. However, some new applications may still need to use LUTYPE6.1 to communicate with existing LUTYPE6.1 applications.
To help you migrate applications from LUTYPE6.1 to APPC, CICS provides a migration path. For more information on this, see Migration of LUTYPE6.1 applications to APPC links.
Choosing between MRO and APPC can be quite simple. The options depend on the configuration of your CICS complex and on the nature of the conversation partner. MRO does not support communication with a partner in a non-CICS system. Further, it supports communication between transactions running in CICS systems in different MVS™ images only if the MVS images are in the same MVS sysplex, and are joined by cross-system coupling facility (XCF) links; the MVS images must be at IBM® MVS/ESA release level 5.1, or later. (For full details of the hardware and software requirements for XCF/MRO, see Installation requirements for XCF/MRO.)
For communication with a partner in another CICS system, where the CICS systems are either in the same MVS image, or in the same MVS/ESA 5.1 (or later) sysplex, you can use either the MRO or the APPC protocol. There are good performance reasons for using MRO. But if there is any possibility that the distributed transactions will need to communicate with partners in other operating systems, it is better to use APPC so that the transaction remains unchanged.
APPC application programs will not run under MRO. Even if both partners are in the same MVS image, CICS will not use MRO facilities but will send conversation data through the communications controller. That involves some z/OS® Communications Server overhead. So you must decide whether your application programs are to converse using APPC or MRO and code them accordingly.
Table 1 points out the main differences between the MRO and APPC protocols.
| MRO | APPC |
|---|---|
| Function is realized without using a telecommunication access method. | Depends on z/OS Communications Server or similar. |
| Non-standard architecture. | SNA architecture. |
| CICS-to-CICS links only. | Links to non-CICS systems possible. |
| Communicates within single MVS image, or (using XCF/MRO) between MVS images in same sysplex. | Communicates across multiple MVS images or other operating systems. |
| Sync level 2 forced for the conversation. | Sync level 0, 1, or 2 can be selected. |
| Program initialization parameter (PIP) data not supported. | PIP data supported. |
| Data transmission not deferred. | Deferred data transmission. |
| Partner transaction may be identified in data. | Partner transaction defined by program command. |
| Performance overhead over a single application. | Even greater performance overhead over a single application. |
| RECEIVE can be issued only in receive state. | RECEIVE causes conversation turnaround when issued in send state on mapped conversations. |
| No ISSUE SIGNAL command. | ISSUE SIGNAL command available. |
| WAIT command has no function. | WAIT command causes transmission of deferred data. |