Handling On Spool Jobs

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 (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 performs the following actions:

  • 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 On Spool Job Scheduling Definition Considerations

  The forced job appears in the Active Environment screen with status WAIT SCHEDULE ON SPOOL.

• 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, to release it, if required.
  • If the external job is waiting for execution in HELD state, that is, if the job arrives on spool with TYPRUN=HOLD, Control-M releases it for execution.
  • Otherwise, Control-M verifies that the job is still in the spool (waiting for execution, executing or ended) before deciding to perform post-processing.
• Control-M waits for the job to finish execution, reads its SYSOUT, analyzes the execution results and performs all the post-processing actions defined in the job scheduling definition.

Note: Control-M can only handle NJE jobs as On Spool jobs when they originate on the same NJE node as that on which Control-M is running.