S001 |
An I/O error ocurred. Check reason code for exact cause. Examples are trying to read beyond End of File, trying to write to an input file or a file length error. |
S002 |
Invalid I/O record, eg attempting to write a record that is longer than the maximum record length. |
S004 |
Error occured during OPEN. Eg Invalid DCB. |
S013 |
Error OPENing a dataset, eg PDS member does not exist, record length in program doesn’t match dataset’s record length. |
S0C1 |
Operation Exception. Check for subscript errors, missing DD card, file not opened. |
S0C4 |
Protection Exception/Storage Violation. Trying to access storage not available to the program. Can be caused by a subscripting error or reading/writing a file that isn’t open. |
S0C7 |
Program Check Exception – Data. Check for spaces in a packed decimal or numeric field. Check to see if record layouts or file layouts have been changed. |
Sx22 |
Job has been cancelled. The value of x will vary depending on the way the job was cancelled. S222 means job was cancelled by a user or operator without a dump. If a TSO session times out you will probably get an S522 abend code. |
S806 |
Unable Link or Load. The job was unable to find the specified load module. Check that the job is looking at the correct Load Libraries, specify a STEPLIB if required. |
S80A |
Not enough Virtual Sorage to satisfy a GETMAIN or FREEMAIN request. |
S822 |
Unable to obtain to obtain enough space to satisfy a REGION= request May need to change REGION statement in the JCL.. |
S878 |
Not enough storage available to satisfy a GETMAIN or FREEMAIN request.. Job was anable to allocate an area of memory of the correct size. Try Specifying or amending the ‘REGION=’ JCL statement. |
S913 |
You are trying to access a dataset which you are not authorized to use. |
Sx37 |
Unable to allocate enough storage for a dataset. You might need to increase the amount of primary and secondary space to be allocated for a dataset in the ‘SPACE=’ parameter, or you may have to move the dataset to a different DASD devive which has enought space to store the dataset. ‘x’ will vary, likely Abends are SB37, SD37 or SE37. |
U1020 |
I/O Logic error. Typical reasons are; trying to write to a file opened as input; Rewrite without a previous read. See the message IGZ020I for details of the exact reason. |
U1035 |
Inavlid OPEN/CLOSE. Check there is a DD statement for the file. See the message IGZ035I for more detailed information. |
|
|
001 |
I/O ERROR |
002 |
I/O INVALID RECORD |
004 |
OPEN ERROR |
008 |
I/O SYNAD ERROR |
013 |
OPEN ERROR |
028 |
PAGING I/O ERROR |
0CX |
PROGRAM CHECK EXCEPTIONS:
0C1 |
OPERATION |
0C4 |
PROTECTION / ADDRESSING |
0C5 |
ADDRESSING |
|
706 |
NON-EXECUTABLE PROGRAM |
804 |
INSUFFICIENT VIRTUAL STORAGE |
806 |
UNABLE TO LOAD (LINK ETC) PROGRAM |
80A |
INSUFFICIENT VIRTUAL STORAGE |
878 |
INSUFFICIENT VIRTUAL STORAGE |
737 |
I/O ERROR |
A14 |
I/O ERROR |
B37 |
The system allocated all the primary and secondary space it could, but it still could not write the output. |
D37 |
Primary disk space was exceeded and no secondary space has been specified, or it has been exhausted. |
E37 |
This often occurs when you try to add members to a PDS, and you get E37 ABEND. It occurs because the PDS Directory require more space for its members, than it was initially alloted. |
Be the first to comment