The following points relate to component definition:
The job name specified in the ON JOBARRIV statement in this rule must match the name of the job to be monitored. It can be a full job name, or it can be a mask if a group of jobs is to be monitored.
The job scheduling definition must be forced by the first DO FORCEJOB statement in the CMEM rule.
The MEMNAME value in the job scheduling definition must match the name of the external job. A mask can be specified in the MEMNAME field if the same job scheduling definition is used for more than one job.
Appropriate runtime scheduling criteria for the job must be defined in the job scheduling definition. This enables Control-M to control when the job should be run, that is, its execution.
Desired post-processing actions must be defined in the job scheduling definition.
On Spool jobs are handled as follows:
When the job arrival event occurs, Control-M forces the requested table or job.
If the MEMNAME value in the requested table or job does not match the name of the arriving job, the table or job is forced and processed regularly by Control-M, which presumes that a job is submitted when its runtime scheduling criteria are met, and so on.
If the MEMNAME value in the requested table or job matches the name of the arriving job, the job becomes an On Spool job and Control-M
replaces the MEMNAME mask, if a mask was specified in MEMNAME, with the name of the arriving job
assigns the job ID of the job that triggered the event to the forced job
forces the job
For details and exceptions see the discussion of On Spool job scheduling definition considerations in the Control-M for z/OS User Guide.
The forced job appears in the Active Environment screen with WAIT SCHEDULE ON SPOOL as its status.
Control-M starts processing the forced job when all runtime scheduling criteria defined in the job scheduling definition are satisfied. If there are no runtime scheduling criteria in the job scheduling definition, Control-M starts processing the job immediately.
Control-M looks for the job in the spool and releases it, if required.
If the external job is waiting for execution in HELD state, that is, if the job arrives on spool with the TYPRUN parameter set to HOLD, Control-M releases it for execution.
Otherwise, Control-M verifies that the job is still in the spool, and is waiting for execution, executing, or ended, before performing postprocessing.
Control-M waits for the job to finish execution, reads its SYSOUT, analyzes the execution results, and performs all the postprocessing actions defined in the job scheduling definition.
By default, Control-M can only handle On Spool jobs that originate on the same NJE node on which Control-M is running.
