Configuration of a sysplex on LPAR and Non-LPAR systems

Figure 1 shows the connections required to connect two processors, one of which runs two MVS™ images on PR/SM™. It also illustrates redundant sysplex couple data sets, channels, signaling paths, and Sysplex Timers.

In this configuration, a failure on any one channel, path, ESCD, or sysplex couple data set does not bring down the sysplex. In case of a failure, MVS can use a different sysplex couple data set, channel, path, ESCD, or Sysplex Timer to maintain sysplex operation.

The figure shows channel to channel connections through ESCDs.
A channel on each LPAR in CPC1 is connected to the primary couple data set and a second channel is connected to the alternate couple data set. A channel on CPC2 is connected to the primary couple data set and a second channel is connected to the alternate couple data set. Both data sets are shared by all three systems.
A Sysplex Timer is needed to synchronize timestamps between the two processors.
A coupling facility can be used in this configuration.

Figure 1. Configuration of a Sysplex on LPAR and Non-LPAR Systems

Note: If you have PR/SM installed with the ESCON® Multiple Image Facility (EMIF), you can share ESCON channels among logical partitions. For information about EMIF and shared channel paths, see PR/SM Planning Guide and z/OS HCD Planning.