Run cycle
A run cycle specifies the days that a job stream is scheduled
to run. Each run cycle is defined for a specific job stream and cannot
be used by other job streams. You can specify the following types
of run cycle:
simple- A specific set of user-defined days when a job stream is run.
- daily
- A run cycle that specifies that the job stream runs according to a day frequency and type that you set. For example, it might run daily, every three days, or just on working days.
- weekly
- A run cycle that specifies the days of the week when a job stream is run. For example, a job stream can be run every Monday, Wednesday, and Friday using a weekly run cycle.
- monthly
- A run cycle that specifies that the job stream runs according
to a monthly day or date that you set. For example, it might run every
1st and 2nd day of the month, or every 1st Monday and 2nd Tuesday
of the month. It can also run, for example, every
1st and 2nd day of the month every two months.
- yearly
- A run cycle that specifies that a job stream runs, for example,
yearly. It can also run, for example, every three
years.
- exclusive
- A run cycle that specifies the days and times when a job stream cannot be run. Exclusive run cycles take precedence over inclusive run cycles.
- inclusive
- A run cycle that specifies the days and times when a job stream is scheduled to run. Exclusive run cycles take precedence over inclusive run cycles.
- offset-based
- A run cycle that uses a combination of user-defined periods and offsets. For example, an offset of 3 in a period of 15 days is the third day from the beginning of the period. It is more practical to use offset-based run cycles when the cycle is based on cyclic periods. This term is used only in HCL Workload Automation for Z, but the concept applies also to the distributed product.
- rule-based
- A run cycle that uses rules based on lists of ordinal numbers, types of days, and common calendar intervals (or period names in HCL Workload Automation for Z). For example, the last Thursday of every month. Rule-based run cycles are based on conventional periods, such as calendar months, weeks of the year, and days of the week. In HCL Workload Automation for Z, run cycles can also be based on periods that you define, such as a semester. This term is used only in HCL Workload Automation for Z, but the concept applies also to the distributed product. You can also specify a rule to establish when a job stream runs if it falls on a free day.