Determining the success or failure of a job
These parameters specify how IBM Tivoli Workload Scheduler for z/OS determines the next status of an operation when the job or started-task ends. When the failing job has been obtained by restarting an operation at Step or Job level (see Restart and Cleanup function) and the failure is determined by the EQQCLEAN step ending with RC>=8 (and causing all subsequent steps to FLUSH), then the operation status is always set to Error, overriding any completion checking logic implemented. For jobs using non-centralized scripts and running on fault-tolerant workstations, see the RCCONDSUC keyword of the JOBREC statement described in the Scheduling End-to-end with Fault Tolerance Capabilities manual.
| Statement | Keywords | Description |
|---|---|---|
| EWTROPTS | RETCODE | Create job-end (3P) event with highest or last return code |
| STEPEVENTS | Specifies when IBM Tivoli Workload Scheduler for z/OS creates events for ending job-steps | |
| JCCOPTS | Job completion checker actions | |
| NOERROR | LIST | Error codes that are not errors |
| JTOPTS | NOERROR | Error codes that are not errors |
| HIGHRC | Highest return code that is not an error | |
| ERRRES | Reset operation status to A (arriving) for these error codes |
These job options in operation details override statement values:
- ERROR TRACKING
- HIGHEST RETURNCODE
IBM Tivoli Workload Scheduler for z/OS processes the options in this order when a job or started task ends:
- EWTROPTS RETCODE - create job-end event.
- JCC - the event is passed to JCC if it is active. The JCC can
set a new value for the return code. After JCC processing, the event
passes to the controller.
The event reaches the event queue at the controller.
- Return code 0 - Operation status set to C. Or continue checking.
- ERROR TRACKING - If operation details specify no error tracking, the operation status is set to C. Or continue checking.
- NOERROR - If the return code matches a NOERROR entry, the operation
status is set to C. Or continue checking.
IBM Tivoli Workload Scheduler for z/OS checks all NOERROR statements and the NOERROR keyword of JTOPTS for a matching entry.
- HIGHRC - If the return code is less than or equal to HIGHRC, the
operation status is set to C. Or continue checking.
IBM Tivoli Workload Scheduler for z/OS first uses the HIGHRC value in the operation details. If blank, JTOPTS HIGHRC is used.
- ERRRES - If the return code matches an ERRRES entry, the operation status is set to A.
If no match has occurred, the operation status is set to E. Recovery processing can then occur.