Error Handling

Introduction

The JobScheduler comes with a number of methods for error handling. These include:

• stop a job: running orders have to wait for the job to become available
• suspend an order: the order waits to be resumed later on
• setback an order: make an order repeatedly try to continue processing after a predefined time interval
• make an order leave a job chain
• make an order continue processing with a specific job node for error handling

Resources

Feature in Detail

• Page:
  How to handle errors

How To ... Articles

• Page:
  How to configure the handling of exit codes by jobs
• Page:
  How to emulate AutoSys max_exit_success exit codes
• Page:
  How to handle errors in a job chain made up from shell jobs
• Page:
  How to read stdout from a job and switch to a node depending on the occurrence of a specific string
• Page:
  How to reschedule a stopped job
• Page:
  How to stop a job in error
• Page:
  How to use Job Post-processing to handle Exit Codes
• Page:
  How to use setbacks to make a job retry in the event an error

Frequently Asked Questions

• Page:
  Can a job call database procedures or a successor job for error handling?
• Page:
  Can a job chain be manually restarted at any job node after an error?
• Page:
  Does JobScheduler handle SNMP traps?
• Page:
  How does JobScheduler get the exit code from a shell script?
• Page:
  Send Order Log per Email with a JobScheduler JITL-Job
• Page:
  What is the difference between "end" and "kill immediately"?
• Page:
  Will JobScheduler retain the order of execution when a batch job is delayed?

Examples in Detail

• Page:
  Example for control of the process flow of a job chain by exit codes
• Page:
  Job JobSchedulerSSHJob - Handling StdErr and ExitCode