IBM Workload Scheduler for z/OS: flexible run cycles
germanagrossi 2700045401 Visits (5268)
Starting from IBM Workload Scheduler for z/OS 9.1 the new object run cycle group can be defined to have more flexible run cylces and reduce the need of manually generated periods.
It consists of a sets of several run cycles defined as database objects independent from applications.
So a run cycle group can be used by more than one application and that an application can use a mix of its own run cycles and of one or more run cycle groups.
It can be referenced in the application description with the possibility to specify the offset (positive and negative) or inside a rule like a classic period .
It is possible to can group run cycles in subsets so that the negative run cycles can be applied only to the positive ones belonging to the same set.
User wants to schedule an application every day of the month except the last day of the month. But you also want the application scheduled on the last day of the year .
RC1: Type=R FDR=3: EVERY DAY(DAY) MONTH
RC2: Type=E FDR=3: ONLY(LAST) DAY(DAY) MONTH
RC3: Type=R FDR=3: ONLY(LAST) DAY(DAY) YEAR
RC2 'cancels' the last day of each month generated by RC1 AND also the only date generated by RC3. User cannot schedule the application on Dec 31st, RC2 always cancels that specific date since Dec 31st is a "last day of the month".
If implemented as "subsets":
SET1 RC1: Type=R FDR=3: EVERY DAY(DAY) MONTH
SET1 RC2: Type=E FDR=3: ONLY(LAST) DAY(DAY) MONTH
SET2 RC3: Type=R FDR=3: ONLY(LAST) DAY(DAY) YEAR
SET1 generates every day of month except the last day of month
SET2 generates last day of year.
The result is the union of dates generated by subsets SET1 and SET2
Run cycle groups allow the use of a logical AND between individual run cycles in the group. This is achieved with the addition of two new run cycle types:
A Rule-based run cycle. Select days when the application is to be run
if they belong to all A types of the set of run cycles.
D Exclusion rule-based run cycle. Select days when the application is
NOT to be run if they belong to all D types of the set of run cycles.
A run cycle called WEEKLY that corresponds to the last work day of the week, and a second one called MONTHLY for the first day of the month. To schedule an applications on the first day of the month if it is also the last work day of the week, user can define two AND run cycles
WEEKLY: Type=A FDR=3: ONLY(LAST) DAY(WORKDAY) WEEK
MONTHLY: Type=A FDR=3: ONLY(FIRST) DAY(DAY) MONTH
The result list of dates will be the intersection of the run cycles .
If subset are defined , the intersection is applied only within the subset.
The run cycle groups can be defined using ISPF panels, IBM Dynamic Workload Console and Batch Loader Interfaces
In the long term plan (LTP) run cycle group is interpreted as non-cyclic periods with open intervals (no end dates) where the generated days are used as start dates for the intervals and where every interval starting from a generated day finishes at the next generated day. To ensure the proper operation of the run cycle group, the last interval should extend beyond the LTP end-date, so that it is closed by this date.