When a job is submitted by a VM user to MVS, CMEM places a job order for that job in the Control‑M Active Jobs File. Control‑M treats the job as a regular job.

Note:If the job is submitted with parameter TYPRUN=HOLD in the JOB statement, Control‑M releases the job for execution when all scheduling requirements are fulfilled.

When the job finishes execution, execution analysis is performed as usual. If the job order contains post-processing instructions, they are carried out in the same manner as for a regular job.

CMEM can be ordered to add or delete a prerequisite condition when the VM-generated job is displayed on the MVS internal reader, or when the VM-generated job finishes execution in the MVS environment.

For example, CMEM can be ordered to add prerequisite condition SEND-NOW-FILE1 when the MVS system displays a job named VMJOB1. The SEND-NOW-FILE1 prerequisite condition can cause Control‑M to submit a job that causes an MVS file named FILE1 to be sent to VM.

The addition or deletion of prerequisite conditions in this manner does not interfere in any way with the execution of the VM-generated job, nor does Control‑M analyze execution results for the job.

CMEM can be ordered to monitor the execution of a VM-generated job with regard to dataset creation, deletion or access.

For example, CMEM can be ordered to add prerequisite condition FILE1-CREATED when a VM-generated job creates a file named FILE1 in the MVS system. Prerequisite condition FILE1-CREATED can trigger a job that sends a user notification back to VM (the following topics describe the various techniques).

For more information, see the CMEM chapter in the Control‑M for z/OS User Guide.