Can you define a dependency for the job?

When managing the workload in the plan, you can control job processing using dependencies. Dependencies can be of the following types:

Normal

It is a relationship between two jobs or between a job and an application stating that one job or application, named successor, can run only when the other job or application, named predecessor, is completed. Normal dependencies can be internal or external:

Internal dependency

The relationship links jobs belonging to the same application.

External dependency

The relationship links:

Jobs belonging to different applications
A job to an application
An application to a job

For detailed information, see Specifying dependencies.

Conditional

It is a relationship between one job, named conditional successor, and one or more jobs or job steps, named conditional predecessors, stating that the conditional successor can run only when a specific combination of conditional predecessors status and return code values occurs.

For detailed information, see Conditioning the processing of operations.

Cross

It is a dependency of a local job from another job running in a different scheduling environment. It indicates that a local job cannot start until the remote job is completed. Cross dependencies helps you to integrate the workload running on different engines. They can be both HCL Workload Automation for Z engines (controller) and HCL Workload Automation engines (master domain manager).

For detailed information, see Defining and managing cross dependencies.