Workload routing in a sysplex

In an MVS™ sysplex, you can create a CICSplex consisting of sets of functionally equivalent CICS® terminal-owning regions (TORs) and application-owning regions (AORs). If the FEPI back end system is a TOR in such a CICSplex, you can use the z/OS® Communications Server generic resource function to perform workload routing across the available TORs.

A z/OS Communications Server application program such as CICS can be known to z/OS Communications Server by a generic resource name, as well as by the specific network name defined on its z/OS Communications Server APPL definition statement. A number of CICS regions can use the same generic resource name.

A FEPI application, which starts a session with a CICSplex that has several terminal-owning regions, names a target that you have defined as the generic resource name of the TORs. Using the generic resource name, z/OS Communications Server is able to select one of the CICS TORs to be the target for that session. For this mechanism to operate, the TORs must all be registered to z/OS Communications Server with the same generic resource name. z/OS Communications Server is able to perform dynamic workload routing of the terminal sessions across the available TORs.

For information about defining FEPI targets as z/OS Communications Server generic resource names, see the APPLLIST option of the FEPI INSTALL TARGETLIST system programming command. For further information about z/OS Communications Server generic resources, see Configuring z/OS Communications Server generic resources.