|
|
|
|
|
DAYS DCAL
AND/OR
WDAYS WCAL
MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y
DATES
CONFCAL SHIFT RETRO N MAXWAIT 00
MINIMUM PDS
What Places the Report Decollating Mission into the Active Missions File?
A report decollating mission must be placed in the Active Missions file in order to execute. The mechanism used to place a copy of the report decollating mission definitions in the Active Missions file is the New Day procedure (CTDNDAY).
The New Day procedure calls a special scheduling program that runs independently of the Control-D monitor (STC). The program can run at any time, even if the Control-D monitor is not active.
The scheduling program scans and analyzes your report decollating mission library, and determines which report decollating missions should be scheduled to the Active Missions file depending on the defined Basic Scheduling Parameters. You can also specify special parameters in the list of missions to be scheduled, which can override any specified scheduling criteria. For example, the FORCE parameter ignores Basic Scheduling parameters, and always places the report decollating mission in the Active Missions file.
Methods of Scheduling Report Decollating Missions
You can invoke the scheduling program under a variety of environments (see Figure 6). Below is a list of the possible invocation environments and a description of how they work. Some of the methods detailed do not require that any Basic Scheduling parameters be coded.
All users should use this method when testing report decollating mission definitions, or for any ad hoc type scheduling. You simply use the Online options ORDER or FORCE to specify which report decollating missions you want to place on the Active Missions file.
If the Control-M Production Control System is active at your site, you can (and should) use it to automatically schedule your report decollating missions. Use the CATEGORY field of the Control-M job scheduling definition to specify which report decollating mission Category should be scheduled Then, when the relevant batch job is scheduled by Control-M, the Control-D report decollating mission will automatically be scheduled to the Active Missions file. (Using this method, you would not need to define any Basic Scheduling parameters in the report decollating mission.)
You can run the scheduling program as a batch job, using procedure CTDRPDAY. The batch job will analyze the Basic Scheduling parameters of the specified report decollating missions, and schedule the relevant missions to the Active Missions file. (This method normally requires definition of Basic Scheduling parameters for each report decollating mission.) Using this method, you can invoke the scheduling program from an application batch job. This would normally be defined as the last step in the job that would schedule the report decollating mission for this job into the Active Missions file. (Using this method, you can use the FORCE parameter, and you would therefore not need to define any Basic Scheduling parameters.)
During the run of New Day procedure CTDNDAY, described in the Control-D and Control-V chapter of the INCONTROL for z/OS Administrator Guide, one of its phases is the execution of the scheduling program. During this phase, it analyzes a supplied list of report decollating missions, and determines which of them should be scheduled to the Active Missions file. (Using this method, you would normally define Basic Scheduling parameters for each report decollating mission, and would keep the report decollating mission list for CTDNDAY up-to-date.)
If you have a scheduling package, you probably want to avoid duplicating scheduling information in Control-D. You can use the scheduler to control the scheduling and execution of the report decollating missions. This can be accomplished using either of two main methods:
The first method is to pass a list of scheduled jobs for a specific day from the scheduling program to the Control-D New Day procedure. This would place the relevant report decollating missions into the Active Missions file. You want the report decollating mission to execute after the relevant batch jobs have created their report output, so you need to establish a trigger from the scheduler, on completion of the batch job. You can do this by adding a condition to Control-D that would trigger the report decollating mission. You would specify in the report decollating mission (through the IN parameter) that the report decollating mission should wait for the condition before executing. The conditions can be added to the report decollating missions by utility IOACND, which can be executed under various environments.
The second method is to use a user exit in the scheduler software to invoke an execution of the Control-D scheduling program whenever an appropriate job completes in the scheduler application. Since the scheduler knows the job has ended successfully, the report decollating mission is automatically placed in the Active Missions file and can start to execute immediately.
Using these methods, you do not need to define any Basic Scheduling parameters in the report decollating mission.
For users of the CA-7 scheduling software, a Control-D Interface is supplied. Documentation concerning the implementation of the interface can be found in member CA7DOC in the IOA SAMPLE library.
If you implement the CDAM Direct Write feature, you can schedule report decollating missions to the Active Missions file based on the creation of a CDAM file. Using this method, you must set EXIT to YES in the CDAM parameters of the batch job's JCL. We will discuss this technique further in Phase 6. Using this method, you do not need to define any Basic Scheduling parameters.
Figure 24 Graphic Overview of Scheduling Methods
Note: DAILY SUBSYSTEM in the above figure refers to the New Day procedure and the programs it calls.
Parent Topic |