Examples for ADJUST CONDITIONS

ADJUST CONDITIONS Example 1

If a predecessor job is not scheduled, the requirement for the prerequisite conditions that the predecessor job would have normally placed in the IOA Conditions file is erased in the successor jobs.

Figure 143 ADJUST CONDITIONS Parameter Example 1

TBL ACCOUNTS_GROUP       CTM.PROD.SCHEDULE(TBL)

COMMAND ===>                                          SCROLL===> CRSR

+-------------------------------------------------------------------+

GROUP   ACCOUNTS_GROUP          MEMNAME  ACCOUNTS                     

OWNER   N04B                                                          

APPL                                                                 

DESC                                                                  

ADJUST CONDITIONS Y            TBL MAXWAIT 00   STAT CAL             

KEEP JOBS UNTIL REMOVED Y    KEEP AT LEAST 05 DAYS AFTER ENDED NOT OK

SET VAR                                                               

DOCMEM  ACCOUNTS    DOCLIB   CTM.PROD.DOC                            

=====================================================================

SCHEDULE RBC ALL_DAYS                                                 

DAYS    ALL                                                   DCAL    

                                                              AND/OR

WDAYS                                                         WCAL    

MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y

DATES                                                                 

CONFCAL          SHIFT       RETRO N MAXWAIT 00                       

SCHEDULE RBC ACTIVE FROM          UNTIL                               

=====================================================================

SCHEDULE RBC SUNDAYS                                                  

DAYS    01                                                    DCAL    

                                                              AND/OR

COMMANDS: EDIT, DOC, PLAN, JOBSTAT                           16.44.31

ADJUST CONDITIONS Example 2

Assume that a SMART Table Entity defines a chain of jobs, in the order
DAILY-1 —> DAILY-2 —> DAILY-3 —> WEEKLY-1 —> DAILY-4.

• The user wants the following:
  • Each of the DAILY jobs must run every day, in the order
    DAILY-1 —> DAILY-2 —> DAILY-3 —> DAILY-4.
  • The WEEKLY-1 job must run only on each Tuesday.
  • When WEEKLY-1 runs, it must run after DAILY-3 and before DAILY-4.
• DAILY-1, DAILY-2, DAILY-3, WEEKLY-1, and DAILY-4 contain IN and OUT conditions to ensure that they run in the required order.

Unless some step is taken, on the days when WEEKLY-1 does not run, DAILY-4 cannot be executed, because its IN condition causes it to wait for WEEKLY-1 to end.

If the ADJUST CONDITIONS parameter is set to D, WEEKLY-1 is ordered daily. Every day except Tuesday, its scheduling conditions prevent it running, and it is ordered as a PSEUDO job. Each Tuesday, it is ordered and executed normally. The logical job flow is maintained throughout.