Basic Scheduling parameters specify on what dates the mission can be activated. These parameters are relevant only under certain implementation techniques. For more information see the INCONTROL for z/OS Administrator Guide.
Figure 59 Basic Scheduling Parameters
===========================================================================
DAYS DCAL
AND/OR
WDAYS WCAL
MONTHS 1- 2- 3- 4- 5- 6- 7- 8- 9- 10- 11- 12-
DATES
CONFCAL SHIFT RETRO N MAXWAIT 99
MINIMUM PDS
===========================================================================
Table 66 Basic Scheduling Parameters
Parameter |
Description |
---|---|
DAYS |
Days of the month to activate this mission. A maximum of two lines can be specified.
|
WDAYS |
Days of the week to activate the mission. A maximum of two lines may be specified.
|
MONTHS |
Months to activate the mission. |
DATES |
Specific dates in the year to activate the mission. |
===========================================================================
DAYS DCAL
AND/OR
WDAYS WCAL
MONTHS 1- 2- 3- 4- 5- 6- 7- 8- 9- 10- 11- 12-
DATES
CONFCAL SHIFT RETRO N MAXWAIT 99
MINIMUM PDS
===========================================================================
Table 67 Additional Basic Scheduling Parameters
Parameter |
Description |
---|---|
CONFCAL |
Name of a calendar used for mission activation confirmation. SHIFT indicates if and when a mission should be activated when it fails confirmation by the CONFCAL calendar. Valid values are:
|
RETRO |
Valid values are:
|
MAXWAIT |
Number of "extra chance" days to try to activate a mission if the original scheduling date of the mission has passed. |
MINIMUM |
Minimum number of free tracks in a PDS (partitioned data set) under which the mission is activated. The mission is activated if the number of free tracks is less than the minimum. |
PDS |
Name of partitioned data set (library) to be checked for free space. |
Parent Topic |