|
|
|
|
|
Normally you would want to decollate report output as soon as it is created. To handle the output produced by the batch jobs, a report decollating mission for the job must be placed on the Active Missions file. Your decision on how to schedule a report decollating mission to the Active Missions file will depend on your current production control system (if you have one) and your preferences for scheduling.
Note: Control-M for z/OS has full integration with Control-D and can schedule the report decollating mission as soon as the job ends.
The Basic Scheduling parameters of a report decollating mission specify on which days and/or dates you want to schedule the report decollating mission to the Active Missions file for potential execution. report decollating missions must be scheduled to the Active Missions file before they can execute and process the relevant report output. A copy of the report decollating mission is placed on the Active Missions file by a special scheduling program called by the New Day procedure (CTDNDAY). Temporary changes can be made to the report decollating mission without affecting the master definition in the report decollating missions library.
The options and methods available for scheduling the report decollating missions are detailed in Scheduling Parameters later in this phase.
Parent Topic |