A SMART Table Entity defines a chain of jobs with the following flow:
The user wants the following:
Each of the DAILY jobs must run every day, in the order DAILY1 —> DAILY2 —> DAILY3 —> DAILY4.
The WEEKLY1 job must run only on each Tuesday.
When WEEKLY1 runs, it must run after DAILY3 and before DAILY4.
DAILY1, DAILY2, DAILY3, WEEKLY1, and DAILY4 contain IN and OUT conditions to ensure that they run in the required order.
The ADJUST CONDITIONS parameter controls how an unscheduled WEEKLY1 job affects the job flow:
If ADJUST CONDITIONS is set to the default N (No), on the days when WEEKLY1 does not run, DAILY4 cannot be executed, because its IN condition causes it to wait for WEEKLY1 to end.
If ADJUST CONDITIONS is set to Y (Yes), when WEEKLY1 is not scheduled (every day except Tuesday), the IN condition of DAILY4 (the prerequisite from WEEKLY1) is erased. DAILY4 is added to the AJF without its dependency on the other jobs in the flow.
If ADJUST CONDITIONS is set to D (Dummy), WEEKLY1 is ordered daily. Every day except Tuesday, its scheduling criteria prevent it from running, and it is ordered as a DUMMY job. Each Tuesday, it is ordered and executed normally. The logical job flow is maintained throughout. This matches the user requirements.
If ADJUST CONDITIONS is set to B (Bridge), when WEEKLY1 is not scheduled (every day except Tuesday), the IN condition of DAILY4 (the prerequisite from WEEKLY1) is replaced by the IN CONDITION of WEEKLY1. The logical job flow is maintained, and DAILY4 is added to the AJF with a dependency on DAILY3. This matches the user requirements.
ADJUST CONDITIONS Example 2:
A SMART Table Entity defines a chain of jobs with the following flow:
The user wants the following:
On weekdays, the jobs must run in the following order: DAILY1 —> WEEKDAY2 —>DAILY4
On weekends, the jobs must run in the following order: DAILY1 —> WEEKEND2 —> WEEKEND3 —> DAILY4
All jobs contain IN and OUT conditions to ensure that they run in the required order.
WEEKDAY2 and WEEKEND2 have the same IN and OUT conditions, but different scheduling criteria.
WEEKDAY2 is scheduled to run only on working days (Monday-Friday).
WEEKEND2 and WEEKEND3 are scheduled to run only on weekends (Saturday and Sunday).
The ADJUST CONDITIONS parameter controls how the different days of the week affect the job flow:
If ADJUST CONDITIONS is set to the default N (No):
On working days (Monday-Friday), DAILY4 cannot be executed, because its IN condition causes it to wait for WEEKEND3 to end.
On weekend days, all scheduled jobs are executed in the required job flow. No adjustment is required.
If ADJUST CONDITIONS is set to Y (Yes):
On working days (Monday-Friday), the IN condition of DAILY4 (the prerequisite from WEEKEND3) is erased. DAILY4 is added to the AJF without its dependency on the other jobs in the flow.
On weekend days, all scheduled jobs are executed in the required job flow. No adjustment is required.
If ADJUST CONDITIONS is set to D (Dummy):
On working days (Monday-Friday), WEEKEND2 and WEEKEND3 are both ordered as DUMMY jobs. As a result, DAILY4 might inherit the prerequisite IN condition prematurely, before WEEKDAY2 has ended.
On weekend days, WEEKDAY2 is ordered as a DUMMY job. As a result, WEEKEND3 might inherit the prerequisite IN condition prematurely, before WEEKEND2 has ended.
If ADJUST CONDITIONS is set to B (Bridge):
On working days (Monday-Friday), when WEEKEND2 and WEEKEND3 are not scheduled, the IN condition of DAILY4 (the prerequisite from WEEKEND3) is replaced by the IN CONDITION of WEEKEND3. After this Bridge action, no other condition is missing. The logical job flow is maintained, and DAILY4 is added to the AJF with a dependency on WEEKDAY2. This matches the user requirements.
On weekend days, all scheduled jobs are executed in the required job flow. No adjustment is required.
