First 17 steps check different datasets for emptiness. If empty, gives a return code of 200.
Next 5 steps sends an email to customer if the first 5 steps issues other than return code 200.
Next 12 steps abend the job if the rest of 12 steps gives return code OTHER than 200.
Now, the job that ran yesterday was abended with a JCL error in step JS080 because the dataset used in step JS080 was not found. We had to restart the job from JS090. This caused an abend in step JS230 since the COND code referred here is of JS060 which was skipeed because we restarted the job from JS090.
I would like to know how to adjust this JCL to avoid such an inconvenience.
Joined: 23 Nov 2006 Posts: 19270 Location: Inside the Matrix
Only knowing what was originally posted, my suggestion would be to eliminate the "empty" testing and setting codition code(s).
Depending on content or "empty", jcl can be program-created on the fly to submit the required job(s)/step(s) thru the internal reader and the restart issues will go away. The code that creates the jcl would also be able to "restart-in-the-middle". Only needed processes would be submitted eliminating the COND issues.