Restarting a CA 11 controlled job in a step subsequent to the abnormal terminated step involving condition code checks
Article ID: 69309
Updated On:
Products
Issue/Introduction
When a CA 11 controlled job abnormally terminates and is restarted in a step subsequent to the abnormal terminated step, it may be necessary to modify the last return code (LRTCD) of the step that terminated to prevent subsequent steps from flushing. This occurs because the successor step never processed through the JES control blocks and CA 11 is not able to make a determination about the status of the successor step. The LRTCD parm only need to be used if the restart step is a successor step that is dependent on the return code of the failed step.
Resolution
The example below illustrate JOBA abended in step5 and step6 is the preferred restart step. Normally, CA 11 would automatically select STEP5 for restart. However, to restart the job in STEP6, you must override the START step with STEP6 and code STEP5 as the abended step using the LRTCD keyword. By default, =0 is used to null the return code of the fail step. However, a non-zero value can be used, causing CA 11 to honor its return code for the successor step.
//U11RMS EXEC PGM=U11RMS,TYPRUN='R,STEP6,/RE=XXXXXX,LRTCD=STEPSTEP5'
Feedback
