12.07.2015 Views

Contact Technical Support

Contact Technical Support

Contact Technical Support

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

CASS MessagesCASS701E — xxxxx SRAM CLOSE CALL ERRReason:A close call was issued before any records were retrieved by calling SRTGETR.This will be issued only if the application was linked with interface modulesfrom Release 5.1 or prior.Action:Relink the program to obtain a later version of the CA-SRAM modules to correctthe problem.CASS801E — xxxxx CA-SRAM I/O ERR - FILL PHASECCB=xxxxxx,SEEK=xxxxxxxxxxxxReason:An I/O error has occurred during the fill phase. The associated CCB address andthe last seek argument are displayed. CA-SRAM I/O errors are most oftencaused by hardware errors or by accidentally overlaying the CA-SRAM work filewith another output file from the same program or from another partition.Action:Attempt to rerun the job using a different DASD volume if the problem points toa hardware error; otherwise, correct the JCL.CASS802E — xxxxx CA-SRAM I/O ERR - MERGE PHASECCB=xxxxxx,SEEK=xxxxxxxxxxxxReason:An I/O error has occurred during the merge phase. The associated CCB addressand the last seek argument are displayed. CA-SRAM I/O errors are most oftencaused by hardware errors or by accidentally overlaying the CA-SRAM work filewith another output file from the same program or from another partition.Action:Rerun the job using a different DASD volume if the problem points to ahardware error; otherwise, correct the JCL.CAS Messages 7–13

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!