Using SA z/OS Subplexes

You can divide your real sysplexes into several logical SA z/OS subplexes (an example is shown in Figure 1). To do this you must define a specific XCF group suffix and a specific group policy object for each subplex. Each SA z/OS subplex must have its own automation manager. In each subplex there must also be only one shared automation manager takeover file and one shared schedule override file.

With SA z/OS subplexes you can run automation on systems of sysplexes in the same way as on single systems. This is required if you do not have shared DASDs for all your systems in the sysplex.

The group ID must be defined in an HSA parmlib member or INGXINIT for NetView.

To allow automation agents within the same physical sysplex, but to communicate via XCF rather than NetView Gateways within different SA z/OS subplexes, optionally an extended XCF Communication Group can be defined as well. For more details, see Defining Extended XCF Communication Groups.