Common Communications Interface › z/OS Parallel Sysplex Configurations

z/OS Parallel Sysplex Configurations

If you operate z/OS in a parallel sysplex configuration, CAICCI can take advantage of XCF and XES hardware to provide high performance messaging between members of the sysplex. Use XCF or XES to achieve high-bandwidth connections between z/OS systems in a sysplex, without the need for a network protocol such as TCP/IP or VTAM.

XCF and XES also support numerous fault tolerance features, enabling communications to continue even following what otherwise can be a disastrous hardware error. Together, these features result in faster, more reliable communications. They are especially recommended for those environments with large application workloads.

XCF provides efficient, high‑bandwidth communications using a technique that is known as XCF signaling. With XCF, you can configure coupling facility paths or CTC connections for cross-system communications. The CAICCI message traffic is directed over an XCF signaling path according to how you configure XCF and CAICCI. XCF requires appropriate hardware and software definitions.

XES enables CAICCI to manage structures in a hardware device that is known as a coupling facility for messaging. Like XCF, XES provides high bandwidth. A series of coupling facility operations implements it. XES requires an appropriate coupling facility hardware and software configuration.

If the sysplex does not include a coupling facility, or when adequate coupling facility resources for CAICCI do not exist, use XCF. If adequate coupling facility resources are available for CAICCI, you can use the XES protocol to exploit the coupling facility structures, yielding important performance benefits.

Use PROTSEC to specify XCF and XES type links as secure connections. The parameters that are passed to PROTSEC specify secure links over XCF or XES protocols. You can specify either parameter or both parameters in either order as shown in the following examples:

PROTSEC(XCF,XES)

PROTSEC(XES,XCF)

PROTSEC(XCF)

PROTSEC(XES)

Note: PROTSEC does not actually enable the flow of encrypted data; PROTSEC internally flags the XCF/XES link as a secure link.

Note: For more information about setting up XCF or XES, see IBM z/OS MVS Setting Up a Sysplex and z/OS MVS Programming Sysplex Services Guide.