Job Dependencies
Each OpCon job can depend on one or more OpCon jobs. These dependencies help to maintain the workflow. Dependencies can be internal to one schedule, defined across schedules, and defined across schedule dates.
The following information applies to defining job dependencies:
Predecessor Schedule Name: Defines the name of the schedule containing the Predecessor Job. The dependent schedule can be the same as the schedule Name, or any other single- or multi-instance schedule or subschedule.
Predecessor Job Name: Defines the name of the dependent job that the Successor Job depends on. In most cases, the Predecessor Job Name must be different than the Job Name. If a job needs to be dependent on itself across days, set the Offset to an value other than zero. In this case, the dependent Job Name can be the same as the Job Name.
If a job depends on a multi-instance job, the dependency applies to all instances of the dependent job that exist when the job processes.
Predecessor Instance Name: Defines the name of the schedule instance to be used for the Predecessor Job.
The Instance Name drop-down will only be available for Multi-Instance Schedules. The * (asterisk) option represents all instances.
Dependency Type: Defines the type of job dependency. Refer to the Dependency Types table.
Options: Defines the options that are set for the defined dependency. Refer to the Dependency Options Details table.
Successor Frequency Name: Defines the name of the frequency if the job dependency is defined for a specific frequency.
- Leave the frequency blank to associate the job dependency at the job level and always include the dependency for the job.
- Select a frequency name to associate the job dependency only when the job runs with the associated frequency.
Successor Instance Name: Defines the name of the schedule instance for the job.
Dependency Type | Description |
---|---|
After | The job waits until the dependent job completes.
|
Conflict | The job cannot start if the dependent job is running.
If Job A is set up with a conflict dependency on Job B, then Job B should also be set up with a Conflict dependency on Job A. |
Exclude | The job removes the dependent job from the Daily schedule during the Schedule Build process.
|
Requires | The job waits until the dependent job exists in the Daily tables and completes.
|
Dependency Option | Description |
---|---|
Check All Days (C) |
|
Failed |
|
Finished OK |
|
Ignore Exit Code (E) |
|
Job Name Like (L) |
If the characters "JobA" are defined for the dependent job, "JobA12," "JobAspecial," and "JobAbc" would be checked for a Conflict dependency. |
Offset |
|