The fields in the third section of the Job Scheduling Definition screen correspond to the Job Scheduling Definition Runtime Scheduling parameters.
===========================================================================
IN
CONTROL
RESOURCE
PIPE
FROM TIME + DAYS UNTIL TIME + DAYS
DUE OUT TIME + DAYS PRIORITY SAC CONFIRM
TIME ZONE:
===========================================================================
Note: The PIPE parameter is only displayed if MAINVIEW Batch Optimizer (MVBO) is installed at your site.
The Runtime Scheduling parameters define runtime criteria that must be satisfied before the job can be submitted. You have already seen the IN parameter and CONFIRM parameters. Table 6 explains several of the Runtime Scheduling parameters.
Table 6 Runtime Scheduling Parameters
Parameter |
Explanation |
---|---|
CONTROL |
Control Resource. Each Control resource specification consists of two values: Resource name and the type of control required. Valid values for the type of control are:
For example, this parameter can be used to specify that exclusive control of a particular file is required. Control-M does not submit the job until it has exclusive control of that file. |
RESOURCE |
Quantitative Resource. Each Quantitative resource specification consists of two values: Resource name and the quantity required. For example, this parameter can be used to specify that two tape drives are required by the job. Control-M does not submit that job until two tape drives are available and reserved for that job. |
TIME |
TIME FROM indicates the earliest time that Control-M can submit the job. If specified, the job is not submitted before this time of the scheduling day. TIME UNTIL indicates the latest time by which a job can be submitted. If Control-M is unable to submit the job before this time (for example, if a required resource is not available before the UNTIL time), the job is not submitted. Either value or both, or neither, can be specified. No value means that a time factor is irrelevant for job submission. |
Note: It is possible to specify the FROM/TO offset in days in addition to the FROM/TO time. For details, see the Control-M for z/OS User Guide. |
|
PRIORITY |
Job priority. If two or more jobs awaiting submission are competing for resources, this value enables Control-M to determine which job to submit, based on priority. Alphabetic or numeric values can be specified, where Critical path priority can be indicated by specifying an asterisk (*) before the priority value (for example, *5). A critical path job always takes precedence over a non-critical path job. |
You had previously determined the following submission criteria for the job:
Define the criteria as follows:
When you define post-processing parameters, you will see that when the job ends OK this same IN condition is added, but with a date of ODAT.
Two resources can be specified on a single line. Once you specify the quantity of the first resource, the cursor automatically tabs over to the RESOURCE-NAME field for the second resource.
Once you have filled in two resources on the resource line, an additional resource line is opened to enable you to specify more resources.
This section of the job scheduling definition appears as shown below:
===========================================================================
IN IDJOB3-ENDED-OK PREV
CONTROL
RESOURCE IDTAPE-DRIVE 0001 IDCPOWER 0005
PIPE
FROM TIME 2300 + DAYS UNTIL TIME 0400 + DAYS
DUE OUT TIME + DAYS PRIORITY *5 SAC CONFIRM
TIME ZONE:
===========================================================================
Parent Topic |