...
We recommend using order jobs, i.e. one or more jobs in a job chain with multiple orders rather than multiple standalone jobs, (i.e. jobs being that are started individually).
Overview
The advantages of order jobs are that these jobs and job chains:
- are independent of parameter values - only "What the job itself does" is implemented;
- are more generic, meaning that "What a job achieves" is determined by the order parameters;
- can be easily deployed between different environments, e.g. dev, test, prod
- can be more easily changed or modified, if required;
- can take account of dependencies between jobs and
- can handle errors more flexibly.
...
Your might encounter the situation when jobs differ in their parameterisationparameterization. When such jobs are executed in job chains and are started by orders containing different parameters then it is possible to configure a small number of order jobs to run in multiple job chains.
In this situation:
- If if you had to modify a job script, then you just have to apply this to one job.
- If, if instead , you had created a job for each set of parameters then code maintenance would create some considerabe a considerable overhead.
Error Handling
Error handling in job chains is more flexible than with standalone jobs. There are several ways how to react when jobs in job chains terminate with an error:
- End end the job chain
- Start start another job in the job chain
- Repeat repeat the job that terminated in error
Suspend suspend the order
Different methods of error handling can be specified for each node in a job chain. Whenever the job at the current job chain node termnates terminates with an error then the order will either be forwarded to the node configured in the error state, will be suspended or will be restared restarted (setback).
A standalone job can be configured to re-run after the job has terminated with an error or to stop immediately. It cannot be restarted automatically until it has been manually unstopped.
...