This example illustrates a sysplex of two systems whose signaling paths are defined both via the coupling facility and CTC devices. In this example, the group (named SYSAPP) is assigned to its own transport class, and all other COUPLExx defaults are taken. This ensures that message traffic for the members of the group NEWAPP is sent on its own dedicated signaling paths and does not compete with other multisystem applications.

Note that because more signaling paths are defined, the configuration in this example provides higher availability than the example shown in Example 4 — Defining signaling paths through the coupling facility.

In this scenario, the sysplex PLEXOF2D consists of two MVS™ systems (SYSA and SYSB) on two processors.

There is one group, NEWAPP, in the sysplex that requires special consideration. NEWAPP is assigned to its own transport class (TCNEW) in the COUPLExx parmlib member on each system in the sysplex.

Members of other groups on this system share signaling resources in the DEFAULT transport class.

Consider using this configuration when you plan to use an application for which you do not want other multisystem applications competing for signaling resources.