The Control‑M Event Manager (CMEM) communicates with Control‑M through communication files. Communication can be implemented using the previously existing method (Step 7.4 – Allocate and/or format communication files (for non-Sysplex environments)) in any environment.

In a Sysplex environment, communication can also be implemented by the MVS System Logger Sysplex function (Step 7.5 – CMEM Sysplex configuration parameters (optional) and Step 7.6 – Build CMMPLEX parameter member (optional)).

However, all active CMEM and Control‑M monitors must use the same communication method.

The monitor-to-subsystem communication file CTM2SBS is required in both Sysplex and non-Sysplex environments (Step 7.3 – Allocate subsystem communication file).

The MVS System Logger option (Step 7.5 – CMEM Sysplex configuration parameters (optional)T and Step 7.6 – Build CMMPLEX parameter member (optional)) forces the Control‑M and CMEM monitors to not start or to terminate if a CMEM or Control‑M monitor is started in non-Sysplex environment or the MVS System Logger is not available.

For more information, see the Control‑M chapter in the INCONTROL for z/OS Administrator Guide, and CMEM considerations.