Welcome vamsivaliveti.edu1
All very good questions.
1) From on-line help,
Deferred. Another instance of this job was running when this instance was ready to launch, and the concurrency option for the job was set to Defer. This job instance runs after the previous instance completes.
Defer until Normal. Runs the job only after the previous instance of the job completes with a Completed Normally status. If the previous instance does not complete normally, this job will not run.
Defer until completion. Runs the job only after the previous instance completes regardless of the final status of the previous job.
At the job-level, job definition -> Options tab
For example, if a repeating job is defined with deferred until normal, the job will wait until the previous instance completes normally before it starts
2) If job A is scheduled daily, then there is no need to the status to completed normally in order for Job A to run the next day. Note, a problem will occur when Job A for whatever reason runs over to the next production day (for example, if Job A starts at 11:57pm then completes abnormally at 12:13am the next day). So if the concurrency option is set to deferred until normal, then you will have to manually mark Job A as completed normally. You can also create a job event that automatically sets the job to completed normally whenever it fails.
3)See response #2. When a job fails:
- if the problem is resolved from the backend/application server, then you can manually set the job to completed normally
- if the problem is correctable by re-running a job, then re-run job until normal completion
- if no corrective action is needed and failure is expected, then you can create a job event that automatically sets the job to completed normally whenever it fails
BR,
Derrick Au
