How run cycles use periods

To have HCL Workload Automation for Z automatically schedule an operation, create a run cycle in the application, job, or group definition.

When you create run cycles using the SEMESTER period, for example, you can use either rules or offsets:

Run cycles that use rules

 First Day in Semester
 Last Sunday in Semester
 Seventh Sunday in Semester    (This may result in an error)
 Last Day in Semester

These are the equivalent selections using offsets:

Run cycles that use offsets

 Semester, offset 1         First day in semester
 Semester, offset 105       Last Sunday in semester (for the semester
                               beginning on 26 August 1996)
 Semester, offset 38        Seventh Sunday in semester (for the
                               semester beginning on 18 January 1994)
 Semester, offset -1        Last day in semester
Notice that using offsets is more difficult and makes run cycles harder to maintain.
Note:
  1. The start (origin) of each period is offset 1: there is no offset 0.
  2. You cannot specify rules or offsets that select a day outside the interval. If the free-day rule causes a selected day to be shifted outside the interval, however, HCL Workload Automation for Z schedules the occurrence and issues a warning message.
  3. If you omit the end date from the interval, the interval extends to the beginning of the next interval, so an offset of -1 (Last Day in Semester) selects the day before the next semester.
  4. If you add occurrences to the current plan using ETT (event-triggered tracking), and you want external dependencies to be resolved as though the added occurrence had a fixed input arrival time, create a noncyclic period ETTRCY1 with an interval origin of 71/12/31, 31 December 2071. Run cycles that specify this special period are never scheduled in the long-term plan, but dependencies are resolved using the input arrival time on the run cycle, instead of the actual input arrival time, which is the time when the occurrence is added. See Adding occurrences by event-triggered tracking for more information.
  5. If you add occurrences to the current plan using ETT (event-triggered tracking), and you want to set its deadline by adding an offset to the actual input arrival time, then create a noncyclic period ETTRCY2 with an interval origin of 71/12/31, 31 December 2071. Then, for your ETT application, create a run cycle that specifies this offset period: an input arrival time of 00.00 and, as the deadline, the day and time you want the offset to be added to the actual input arrival time. These run cycles are never scheduled in the long-term plan, but when the occurrence is added to the plan, the occurrence deadline is calculated as the actual input arrival time plus the run cycle deadline. See Adding occurrences by event-triggered tracking for more information.