Many users need to operate two or more Control‑M monitors simultaneously, for example, for production and test installations. Control‑M does not support two monitors that update the same production databases, such as the IOA Log file, Active Jobs file, and History Job file. Using the IOA QNAME specified in the IOAPARM member in the IOA.PARM library, an Enqueue Management mechanism prevents different Control‑M monitors from updating the same production databases.
To activate more than one Control‑M monitor in a single system, follow these steps:
The following prefixes must be different for the two environments when installing a new IOA environment:
Note: The BASEPREF parameter is shared when cloning one IOA environment to another. For more information, see Housekeeping.
Note: All editing required by the instructions below must be performed on members of the specified new Control‑M library. Do not modify members in the currently working Control‑M libraries.
The following names and prefixes must be different from the current Control‑M when performing the new Control‑M installation:
Parameters values for the Control‑M Event Manager (CMEM) must be different than those of the currently working Control‑M. Change the value of the CTM2SBS CMEM parameter and the data set names in the IOACPRM member in the IOA.PARM library.
Perform Step 5.2 – Copy Control-M started tasks to site library.
The job production parameters for each Control‑M system must be stored in different Scheduling libraries. Verify that the job production parameters (for example, when to run the job, required resources, and so on) are specified for the new Control‑M using the new Control‑M Scheduling library. This is important for a new Control‑M version, because it is critical that the job production parameters of the production Control‑M system are not affected by the installation of a new Control‑M.
For more information, see the Control‑M chapter in the INCONTROL for z/OS Administrator Guide.
Parent Topic |