Loop detection and analysis

Batch daily planning programs (extend, replan, and trial) prevent you from creating current plans that would cause a dependency loop condition. This is achieved by checking each single network of the plan, that is each set of operations that are linked to each other by some dependencies. Before extending a current plan (PGM=EQQDNTOP), it is a good practice to run a trial plan to detect any dependency loop condition.

The scheduler checks for both normal and conditional dependencies. A step dependency determines a check at operation level.

If a loop condition is detected, batch daily planning programs stop creating the plan and start an analysis phase that produces:
  • A message with summary information about the loop in the EQQMLOG and EQQLOOP data sets
  • A list of messages in the EQQLOOP data set about:
    • The operations involved in the loop and their dependencies.
    • The dependencies that the batch daily planning programs suggest to remove, one at a time, to solve the loop.
    • The application descriptions sorted by the last update date and time in the application definition.