What's the difference between "static" and "dynamic" predecessors

Document ID : KB000049454
Last Modified Date : 14/02/2018
Show Technical Document Details

A new predecessor type of "static" was implemented in JMO r11.
All predecessor conditions implement prior to r11 are, by default, "dynamic."

From the Reference guide:
===================

Type

Indicates whether the predecessor is dynamic or static:

DYNAMIC
A dynamic predecessor is loaded into the tracking file only when the corresponding predecessor job or jobset is in the current-day workload.

STATIC
A static predecessor is loaded into the tracking file whether or not the corresponding predecessor job or jobset is in the current-day workload.

There are reasons for both to exist. Consider the follow example:

You have an "update" job and a "report" job.
The "update" job is a predecessor to the "report" job.

If the "report" job should run after the "update" job has run, when the "update" job is in the schedule, the predecessor type should be "dynamic."

If the "report" job should run after, but only if, the "update" job has run, the predecessor type should be "static."