Workload balancing in a sysplex

In a sysplex, you can use MRO and XCF/MRO links to create a CICSplex consisting of sets of functionally equivalent terminal-owning regions (TORs) and application-owning regions (AORs).

You can use these products and functions to perform workload balancing:
  • The z/OS® Communications Server generic resource function
  • Dynamic transaction routing
  • Dynamic routing of DPL requests
  • CICSPlex® System Manager (CICSPlex SM)
  • The z/OS Workload Manager (WLM)

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 terminal user who wants to start a session with a CICSplex that has several terminal-owning regions uses the generic resource name in the logon request. Using the generic resource name, z/OS Communications Server can select one of the CICS TORs to be the target for that session. For this mechanism to operate, the TORs must all register to z/OS Communications Server under the same generic resource name. z/OS Communications Server can perform workload balancing of the terminal sessions across the available terminal-owning regions.

The terminal-owning regions can in turn perform workload balancing using dynamic transaction routing. Application-owning regions can route DPL requests dynamically. The CICSPlex SM product can help you to manage dynamic routing across a CICSplex.