Two types of errors can be reported by the return codes of n1, n2, n3, and n4--non-VSAM file errors and VSAM file errors. The error is described by n2 and n4. For VSAM file errors, n4 is always equal to 28. The error is described by n1, n2, and n3. A general return code is given by n4 for both non-VSAM and VSAM errors. All return codes are decimal values.
n4 Return Codes:
|
n4 |
Reason |
Action |
|---|---|---|
|
4 |
End-of-file |
Call Product Support. |
|
8 |
Open error or file is not open |
Look for JCL errors or for the use of improper files. |
|
12 |
An I/O error has occurred |
Find cause for I/O error. |
|
16 |
Request not recognized |
Call Product Support. |
|
20 |
File was already opened |
Call Product Support. |
|
24 |
Parameter list error |
Call Product Support. |
|
28 |
VSAM error n1=R15 return code from VSAM n2=low order byte from R0 GENCB/MODCB type of error n3=VSAM feedback byte error in I/O request |
Use n1, n2, and n3 to check for possible user errors. If there are no user errors, call Product Support. |
|
32 |
Insufficient storage |
Increase storage for job step. |
|
36 |
SYNAD error occurred |
Call Product Support. |
|
40 |
BPAM FIND error n1=R15 n2=R0 |
Use n1 and n2 (as described in Data Management Macro Instructions) to check for errors. |
|
44 |
BPAM STOW error n1=R15 n2=0 |
Use n1 and n2 (as described in Data Management Macro Instructions) to check for errors. |
n2 Return Codes:
|
n2 |
Reason |
Action |
|---|---|---|
|
0 |
n4=8, use of unopened file n4=24, parameter list error |
Call Product Support. Call Product Support. |
|
1 |
JCL/label overrode parm list |
Remove DCB information from JCL and ensure that the correct files are referenced. |
|
2 |
Parm list overrode JCL/label |
Remove DCB information from JCL and ensure that the correct files are referenced. |
|
3 |
Unrecognized request |
Call Product Support. |
|
4 |
z/OS or OS/390 x13 ABEND trapped at open |
Fix cause for x13 ABEND. |
|
5 |
Tried to update seq. file |
Call Product Support. |
|
6 |
VSAM write at other than load |
Call Product Support. |
|
7 |
SOS table could not expand |
Call Product Support. |
|
8 |
z/OS or OS/390 DCB open failed |
Call Product Support. |
|
9 |
SOS table buffer pointer lost |
Call Product Support. |
|
10 |
SOS table file CB not built |
Call Product Support. |
|
11 |
z/OS or OS/390 DD statement Missing |
Supply missing DD statement. |
|
12 |
VSAM ACB open failed |
Call Product Support. |
|
13 |
Record format invalid |
Call Product Support. |
|
14 |
Macro format invalid |
Call Product Support. |
|
15 |
Record length not numeric |
Call Product Support. |
|
16 |
Record length too large |
Call Product Support. |
|
17 |
Block size not numeric |
Call Product Support. |
|
18 |
Block size too large |
Call Product Support. |
|
19 |
Invalid VSE/ESA sysname table |
Assemble a valid sysname table. |
|
20 |
VSE/ESA sysname table entry missing |
Assemble a sysname table with an entry for the missing one. |
|
21 |
VSE/ESA LU number too large |
Use an LU number within range. |
|
22 |
VSE/ESA sysname is not numeric or is misspelled |
Correct to a valid sysname. |
|
23 |
VSE/ESA sysname blank |
Do not use blank sysname. |
|
24 |
VSE/ESA LU not assigned |
Call Product Support. |
|
25 |
VSE/ESA DTF prototype missing |
Call Product Support. |
|
26 |
VSE/ESA logic module missing |
Generate missing logic module. |
|
27 |
VSE/ESA CCW mismatch |
Call Product Support. |
|
28 |
File is not a PDS |
Allocate file to a PDS. |
|
Copyright © 2014 CA.
All rights reserved.
|
|