Basic Scheduling Parameters for job scheduling definitions

Each Basic Scheduling parameter is described in this chapter. However, the interrelationships between some of these parameters are described briefly below.

DAYS, DCAL, WDAYS, WCAL

These parameters are all optional.

The DAYS parameter identifies days of the month on which the job must be scheduled, such as first day of the month, third working day of the month. Several formats are available for specifying DAYS values.

The WDAYS parameter identifies days of the week on which the job must be scheduled, such as the first day of the week, the second day of each week, and so on. Several formats are available for specifying WDAYS values.

A calendar name can be specified in the DCAL and/or WCAL fields. A calendar specifies days of the year on which a rule can be scheduled, known as working days. For more information on calendars and the IOA Calendar facility, see IOA Calendar Facility.

When both the DAYS and DCAL parameters are specified, they work as a complementary unit, as described in DAYS: Basic Scheduling Parameter. Similarly, when both WDAYS and WCAL are specified, they also work as a complementary unit, as described in WDAYS: Basic Scheduling Parameter.

When values for both DAYS (/DCAL) and WDAYS (/WCAL) are specified in the same job scheduling definition, the resulting schedule is determined by the value specified in field AND/OR.

CONFCAL and SHIFT

A calendar specified in CONFCAL is not used for job scheduling, but is used instead for validating a scheduled date. Only jobs that have satisfied all other specified basic scheduling criteria are checked against the CONFCAL calendar. If the day is a working day in the CONFCAL calendar, the job is scheduled on that day. Otherwise, the job is either shifted to (scheduled on) another day according to the value entered in the SHIFT parameter, or the job is not scheduled (if no SHIFT value has been specified).

CONFCAL calendars are especially useful for handling holidays and other scheduling exceptions.

Defining a Schedule – Internal Scheduling Logic

When defining tables which handle jobs to be scheduled individually, it is useful to understand the IOA Scheduling facility logic, which determines whether to order a job on a specific day. This logic is described below.

1. ACTIVE FROM and UNTIL parameters are checked first. If the current date falls outside the time range specified, no further checking is performed.
2. DAYS and DCAL parameters are checked independently and a first tentative scheduling decision is created.
3. WDAYS and WCAL parameters are checked independently and a second tentative scheduling decision is created.
4. A third tentative scheduling decision is created based on the above two decisions and the AND/OR value linking them.

   (If DAYS and/or DCAL are not specified, this third temporary scheduling decision is identical to the second scheduling decision. If WDAYS and/or WCAL are not specified, this third scheduling decision is identical to the first scheduling decision.

5. If CONFCAL and/or SHIFT are specified, this third scheduling decision is adjusted according to the CONFCAL and SHIFT criteria.
6. This third scheduling decision (as adjusted) becomes the final scheduling decision. The IOA Scheduling facility determines whether to schedule a job based on this final scheduling decision.

Scheduling Jobs in SMART Tables

The following scheduling algorithm applies to SMART Tables:

1. Before jobs in a SMART Table can be scheduled, the SMART Table itself must be eligible for scheduling (that is, at least one of the rule-based calendars of basic scheduling criteria in the SMART Table Entity has been satisfied).
2. If (and only if) the SMART Table is eligible for scheduling, each job scheduling definition in the table is individually checked for possible scheduling.
3. For each job scheduling definition:
   • Rule-based calendars in the job scheduling definition are checked sequentially beginning with the first calendar. The SCHEDULE RBC ACTIVE FROM and UNTIL parameters are checked first. If the current date falls outside the time range specified, no further checking is performed.

     If the criteria of a rule-based calendar is satisfied, no further checks are performed on the remaining calendars. The criteria belonging to the satisfied calendar are used in the scheduling algorithm.

   • The RELATIONSHIP parameter (AND/OR) is checked.
     • If a rule-based calendar is satisfied and the defined relationship is OR, the satisfied rule-based calendar is sufficient and the job is scheduled according to criteria of this calendar. No further checks are performed.
     • If no rule-based calendar is satisfied and the defined relationship is AND (that is, the job requires that the rule-based calendar be satisfied), the job is not scheduled if it is in a SMART Table. If it is in a non-SMART table it is scheduled according to the job scheduling definition.
     • If a rule-based calendar is satisfied and the defined relationship is AND, or if no rule-based calendar was satisfied and the defined relationship is OR, the basic scheduling criteria of the job must be satisfied (that is, the algorithm continues with the next step).
   • The basic scheduling criteria of the job are checked.
     • If the basic scheduling criteria of the job are not satisfied, the job is not scheduled.
     • If the basic scheduling criteria of the job are satisfied, the job is scheduled.

The basic scheduling criteria of the job, not the rule-based calendar criteria, are used for scheduling. This is a concern only if there are conflicting MAXWAIT values in the rule-based calendar criteria and the basic scheduling criteria of the job. In this case, the MAXWAIT value from the basic scheduling criteria of the job is used.

Figure 141 SMART Table Scheduling Flowchart