Sysplex implementation

TSO users can access all repository data, regardless of the MVS system to which they log on. Data is maintained in a single repository, regardless of the MVS system on which the utility executes.

There can be only one master IPT server. All other IPT servers are considered slaves. The master IPT server initiates all required functions for the product. When creating the cpcxINI file for a sysplex, you must decide which of the following ways that you want the IPT servers to communicate.

• (recommended) Designate a master IPT server that always initiates all of the functions that are required for the BMC System Administration for IMS solution to run. If you use this method, BMC recommends that you always start the master IPT server first.

  • If the designated master IPT server starts successfully but later becomes unavailable, another CPC server (slave) becomes the master. When the designated master becomes available again, control is passed back to the designated master and the other CPC server returns to slave status.

  • If the designated master IPT server does not start, the other CPC servers wait for one hour before issuing an ABEND.

  During the installation process, a cpcxINI file was created in CPCSAMP (if you chose non-merged libraries for your installation) or IMSAMP (if you chose merged libraries for your installation). It contains the XSYS command that designates the master IPT server. For information about non-merged and merged installation libraries, see the installation guide. For information about the XSYS command, see the Master keyword in CPCINI keywords.

• If a master IPT server was not designated, the first active CPC becomes the master and initiates all required functions. If the master fails, another CPC becomes the master and takes over all required functions. If the first CPC IPT server becomes active again, it returns as a slave.