U11-626 shows job completed after steps flushed due to nonzero return code
Article ID: 55032
Updated On:
Products
Issue/Introduction
When a job receives a non zero return codes and causes steps to flush, the CA 11 message U11-626 says the job completed successfully. Why?
Environment
Resolution
CA 11 only considers a system or user abend as an unsuccessful termination of a job. Since condition codes may be used in different ways, CA 11 normally will ignore condition codes and will assume a job completes successfully as long as no step abended.
CA 11 can be set up to check condition codes returned at step termination and can determine if a job should be set for restart by using the GBLHIRC config parameter or updating the HIRTCD field in the CMT. The defaults are zero which indicate that CA 11 is to NOT do condition code checking.
When HIRTCD or GBLHIRC is set to a nonzero value, CA 11 checks the return code of each step in the job and considers the job to have failed (abended) if any step returns a condition code equal to or greater than the specified value. If using the Auto Setup feature, then Auto Setup is invoked when the job terminates and sets the job for restart.
CA 11 does not stop processing of the job when an unacceptable condition code is encountered; the job processes until it reaches completion or abends.
Note:
If an installation has implemented a scheduling system such as CA 7 or Scheduler which also performs return code processing, it is important to synchronize the handling of return codes between CA 11 and the scheduling system. In other words, CA 11 and the scheduling system must agree on what constitutes a job or step return code which results in a restart for a job.
Feedback
