Job On Spool

The job must have the following characteristics:

• The job must be submitted with TYPRUN=HOLD to delay its execution and permit Control-M to determine when to run the job.

  Note:

  For users who have the Thruput Manager product installed, a conflict might occur between it and the Control-M On Spool processing.

  Thruput Manager intercepts JES JCL Interpretation processing, and temporarily changes the job's status.   If the Control-M Submittor task requests the job's status while it is being processed by Thruput Manager, it receives a response indicating that the Job is not HELD. As a result, the job is set to status WAIT EXECUTION, and Control-M does not try to release it. In this event, you may see messages from Thruput Manager (for example, DTM1459I) and from the Control-M Submittor (for example, SUB13AI) with the same time-stamp. This indicates that both tasks were processing the job at the same time.

  BMC recommends that the vendor of the Thruput Manager product be contacted to determine if a fix for this problem (to not change the job’s status) has been issued.

  In any case, the JOB card of the On Spool Job must be coded with TYPRUN=JCLHOLD, rather than TYPRUN=HOLD, to cause both Thuput Manager and the JCL Interpreter to process the job only after it has been released by Control-M.

• The MSGCLASS sysout of the job:
  • for JES3 users: must be equal to the Control-M SYSOUT held class
  • for JES2 users: can be any held SYSOUT class

This enables Control-M to read the job sysout and perform post-processing according to the job scheduling definition.