Using error codes to set operations to ended-in-error

Depending on the application, you might consider that not all error codes represent true operation errors. That is, you do not want the operation representing the job or started task to be marked as ended-in-error for certain error codes. You can tell HCL Workload Automation for Z to ignore certain error codes, using the NOERROR statement. You specify a list of error codes that must not cause the operation to be marked as ended-in-error. If the operation ends with an error code that matches a NOERROR condition, the operation is treated as having ended normally.

A specific extended status code shows if an operation, with completed (C) as current status, ended with an error code matching a NOERROR entry.

An error code specified by the NOERROR initialization statement can apply to all computer workstation operations, or it can be specified to apply to only a subset of such operations or steps within those operations. If the completion code of the last step in the operation is used to set the error code, this is regarded as a job error code. This means that the stepname and procstepname parameters of the NOERROR statement cannot be used to establish a match with the specified code because HCL Workload Automation for Z does not have the relevant step information.

If the error code is numeric, after checking the NOERROR list, HCL Workload Automation for Z checks the error code against the HIGHRC keyword of the JTOPTS initialization statement. If HIGHRC has been specified at operation level, HCL Workload Automation for Z uses this value instead of the installation-defined HIGHRC. The operation is considered to have ended-in-error if the error code has a higher numeric value than the HIGHRC value specified. If the error code is numerically lower than or equal to the HIGHRC value, the operation is considered to have ended normally. In this case, the operation is marked as C, complete.

To use the NOERROR keyword for specific job or started-task steps, the event writer options, as specified in the EWTROPTS initialization statement, must be set as follows:
  • The STEPEVENTS keyword must specify either ALL or NZERO.
  • The RETCODE keyword must specify HIGHEST.

For more information about the NOERROR statement, see NOERROR; for more information about the NOERROR modify command, see Modifying the scheduler.