Managing Predecessor Dependencies › Predecessor Dependencies

Predecessor Dependencies

Many jobs can run simultaneously in an Application. Predecessor dependencies describe the relationships between jobs in an Application. By default, a job runs after all its predecessors complete successfully. A job that waits for other jobs to complete is in the PREDWAIT state.

Example: Dependencies between jobs in an Application

Every day, jobs A, B, C, and D run. On Fridays, job E runs. On the last workday of the month, job F also runs.

The following illustration displays the run frequency of all the jobs.

The server submits a job after all of the job's predecessors complete successfully. In this Application, the jobs run in the following order:

• Job B and job C run after job A completes successfully
• Job D runs after job B and job C complete successfully
• Job E runs on Fridays after job D completes successfully
• On the last workday of the month, there are two possibilities:
  • If the last workday of the month is a Friday, job F runs after job E completes successfully
  • If the last workday of the month is not a Friday, job F runs after job D completes successfully

More information:

Abandon Predecessor Dependencies at a Specified Time