Managing Predecessor Dependencies › Predecessor Dependencies › Inherited Dependencies

Inherited Dependencies

Jobs in an Application may have different run frequencies. When the server selects jobs for submission, it checks the relationships between jobs and determines whether jobs should inherit dependencies.

Example: Inherited Dependencies of a Job

There are three jobs in an Application. Job A releases job B, which releases job C. Job A and job C run daily, and job B runs only on Friday.

By default, jobs inherit the relationships of their predecessors. Job B runs only on Fridays. On the other days, the server selects job A and job C. Job C inherits the relationship between the unselected job B and job A. On these days, job C depends on job A, not on job B.

You can override job inheritance. Without job inheritance, job A and job C run independently if job B does not run.

The following table summarizes the predecessor dependencies on different days with and without inheritance:

More information:

Override Job Inheritance