Scheduler shows predecessor as "Not Scheduled" and "Satisfied NO"
search cancel

Scheduler shows predecessor as "Not Scheduled" and "Satisfied NO"

book

Article ID: 197300

calendar_today

Updated On:

Products

Scheduler Job Management

Issue/Introduction


JOBX  has criteria:  JOBA-01 40 SCHDA OR JOBB-01 40 SCHDB

Both schedule SCHDA and SCHDB have Auto Select NO which means that the schedules are not brought into the active workload during Autoscan.  These schedules run when needed, and are brought into the workload only via the RUN command. 

Issue:  JOBA in SCHDA completed, but JOBX does not run.  JOBX's predecessors status shows:

Command  Type     Name / Current Status                      Satisfied 
-------- ------ -------------------------------------------- ---------
________ JOB      JOBB 01 40 SCHDB                            NO   
                   Not Scheduled                                                
________ JOB      JOBA 01 40 SCHDA                             YES  
                   Completed       J0006190 RC=00000                            
 


 

Cause

Working as designed when the predecessor schedule is Auto Select NO.

 

Resolution

If the goal is for JOBX to run when either JOBA-01 40 SCHDA, or JOBB-01 40 SCHDB completes, then use the true -OR- operator on the criteria statement.

Example: JOBA-01 40 SCHDA -OR- JOBB-01 40 SCHDB

Reference:  Scheduler Job Management Online Reference Guide section 8 Criteria Language  The OR vs -OR- Operators

Scheduler Bookshelves