A customer of CA Technologies discovered that JCL errors were costing them time and money. Common errors went unnoticed, causing expensive reruns. A recurring common error, such as 'DATA SET NOT FOUND,' caused jobs to ABEND after execution of the first several steps. The systems programmer had to analyze the JCL to locate the source of the problem and correct it, and the job had to be rerun.
The customer purchased CA JCLCheck and established a standard to scan their production JCL in batch, using CA JCLCheck to flag errors and check for nonzero return codes. CA JCLCheck improved efficiency right away, here's how.
The night operator, Joe, discovered that the initial production of JOBR was going to ABEND, as indicated by the error messages listed on CA JCLCheck Report 6 - Error Messages.
The error messages read:
CAY6186E MISSING GDG NUMBER CAY6072E CONTINUATION STATEMENT REFERENCES A NONEXISTENT DATA SET CAY6033W OVERRIDES OUT OF ORDER
Joe compared other reports generated by CA JCLCheck to the problems indicated by the error messages to find the solution.
He read Report 1 - Listing of Jobstream JCL to see the JCL exactly as it was submitted for the job. He read Report 2 - Listing of Merged JCL to see the entire JCL for the job including procedure library statements. Joe compared these reports and determined that the submitted JCL was incomplete without the GDG reference. He compared the cataloged GDG with the GDG being referenced in the job stream JCL. If the submitted JCL referenced the cataloged data set, the GDG reference was valid.
Next, Joe determined from Report 2 - Listing of Merged JCL that the data set existed in a PDS that was entered in the JCL. Using one of the CA JCLCheck ISPF panels, Joe added the PDS that contained the member called by JOBR.
Finally, he discovered that the overrides were out of order because one had been deleted for a previous run and had not been reinstated for future runs. Joe inserted the override into the job stream JCL for JOBR and resubmitted the JCL.
The evening's production continued without ABENDs. When the shift ended, the correction to the JCL was noted and production ran as if a problem never occurred.
|
Copyright © 2014 CA.
All rights reserved.
|
|