|
|
|
|
|
Basic Scheduling parameters specify on what dates the mission is a candidate for activation.
The New Day procedure determines if the balancing mission is a candidate for execution on a specific date. If a balancing mission is a candidate for execution on a specific date, the balancing mission is placed in the Active Balancing file.
Each balancing mission in the Active Balancing file has an original scheduling date associated with it. This is the date on that data should be balanced according to the Basic Scheduling parameters. This date is not necessarily the same as the current calendar date or the current installation working date.
Note: Basic Scheduling parameters may be ignored by the Control-M/Analyzer New Day procedure, depending on the mode of operation.
Table 277 Basic Scheduling Parameters
Parameter |
Description |
|---|---|
DAYS |
Days of the month to activate the balancing mission. |
WDAYS |
Days of the week to activate the balancing mission – Sunday, Monday, and so on. |
MONTHS |
Months to activate the balancing mission. |
CONFCAL |
Name of a user-defined calendar for confirming schedule dates. |
DATES |
Specific dates in the year to activate the balancing mission – day and month. |
RETRO |
A flag that specifies whether the balancing mission should be ordered for possible execution after its original scheduling date has passed. |
MAXWAIT |
Number of days that the balancing mission should wait to be executed after its original scheduling date has passed and before the mission is disregarded. |
MINIMUM |
Minimum number of free tracks required for the library defined in parameter PDS under that the balancing mission is ordered. |
PDS |
Name of a partitioned data set (library) to be checked for minimum free space. |
Parent Topic |