Determines a date range (Start Date - End Date) when the job or folder can be ordered or the Rule-based Calendar (RBC) can be used. During the period that the job or folder is outside the active range (non active), it is not eligible to be ordered, if the relationship between Job Scheduling definitions and Rule Based Calendars is set to AND (Default: OR).
If the relationship is set to OR, the job is eligible to be ordered depending on the RBC criteria.
You can use the Active parameters to define either of the following:
EXAMPLE: A job that uses an Every Day calendar should not be ordered on October 25th and 26th. The Start Date and End Date should be:
The Job is not ordered on October 25th and 26th
You can use this parameter with multiple copies of a job or folder definition to create date ranges during which the job or folder definition is run with alternate values, to eliminate the necessity of making last-minute changes to a job processing definition for a fixed period of time. In all other Control-M components, ensure that the Active Start Date is less than or equal to the Active End Date. No matter which component you use to define the Active period, you can leave either the Start date or the End date blank. If only a start date is specified, the job can be scheduled on or after that date. If only an end date is specified, the job can be scheduled on or before that date.
When you define an Inactive period, the end date identifies the last date of the earlier active period (active-period1). The start date identifies the first date of the later active period (active-period2). Therefore, the end date must be less than the start date.
Additional information |
Description |
---|---|
Usage |
Optional |
Format |
Drop-down list. Define one or both of the following sub-parameters: |
Variable Name |
None |
Alternate names for the Active Start Date parameters |
|
Alternate names for the Active End Date parameters |
|
Alternate formats for the Active Start Date parameters |
|
Control‑M/EM Utilities |
String for date. According to site standard (ddmmyyyy, mmddyyyy, yyyymmdd). EXAMPLE: <ACTIVE_FROM="15032017"/> |
Control‑M for z/OS |
6-integer string for date. According to site standard (ddmmyy, mmddyy, yymmdd). |
Alternate formats for the Active End Date parameters |
|
Control‑M/EM Utilities |
String for date. According to site standard (ddmmyyyy, mmddyyyy, yyyymmdd). EXAMPLE: <ACTIVE_TILL="15032017"/> |
Control‑M for z/OS |
6-integer string for date. According to site standard (ddmmyy, mmddyy, yymmdd). Default: blank. |
Parent Topic |