Handling Unscheduled Conditions

The handling of Unscheduled Conditions, as defined above, is more complex because it concerns the issue of normal dependency versus "Maybe" dependency:

• Normal Dependency

  A successor job is always dependent on the predecessor job, regardless of whether the predecessor job is scheduled.

  With this type of dependency, using the example cited above, successor Job-B must not be submitted because predecessor Job-A was not scheduled and executed.

  In this case, the dependency must not be ignored. The unscheduled prerequisite condition is not added manually.

• "Maybe" Dependency

  A successor job is dependent on the predecessor job only if the predecessor job is scheduled that day. If the predecessor job is not scheduled that day, the successor job can still be submitted, provided that other runtime scheduling criteria are satisfied.

  In this case, the predecessor job is referred to as a Maybe job.

  With this type of dependency, using the example cited above, successor job Job-B must be submitted, provided all other runtime scheduling criteria are satisfied, because predecessor job Job-A was not scheduled.

  In this case, the dependency must be ignored or bypassed. Methods for ignoring Maybe dependencies are described below.