Reason:
The indicated file function could not be performed with the specified file.
Action:
See :tref refid=A6001T. to determine the reason the error occurred and the appropriate action. If you receive a return code combination of 0,24,0,8, contact CA Product Support.
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 a 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 value
|
n4 |
Reason |
Action |
|---|---|---|
|
4 |
End-of-file |
Call CA 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 CA Product Support. |
|
20 |
File was already opened |
Call CA Product Support. |
|
24 |
Parameter list error |
Call CA 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 CA Product Support. |
|
32 |
Insufficient storage |
Increase storage for job step. |
|
36 |
SYNAD error occurred n1=byte 1 of DECB n1=byte 2 of DECB n1=byte 3 of DECB |
Call CA 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 |
Reason |
Action |
|
0 |
n4=8, use of unopened file n4=24, parameter list error |
Call CA Product Support. Call CA 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 CA Product Support. |
|
4 |
OS x13 ABEND trapped at open |
Fix cause for x13 ABEND. |
|
5 |
Tried to update seq. file |
Call CA Product Support. |
|
6 |
VSAM write at other than load |
Call CA Product Support. |
|
7 |
SOS table could not expand |
Call CA Product Support. |
|
8 |
OS DCB open failed |
Call CA Product Support. |
|
9 |
SOS table buffer pointer lost |
Call CA Product Support. |
|
10 |
SOS table file CB not built |
Call CA Product Support. |
|
11 |
OS DD statement Missing |
Supply missing DD statement. |
|
12 |
VSAM ACB open failed |
Call CA Product Support. |
|
13 |
Record format invalid |
Call CA Product Support. |
|
14 |
Macro format invalid |
Call CA Product Support. |
|
15 |
Record length not numeric |
Call CA Product Support. |
|
16 |
Record length too large |
Call CA Product Support. |
|
17 |
Block size not numeric |
Call CA Product Support. |
|
18 |
Block size too large |
Call CA Product Support. |
|
19 |
Invalid DOS sysname table |
Assemble a valid sysname table. |
|
20 |
DOS sysname table entry missing |
Assemble a sysname table with an entry for the missing one. |
|
21 |
DOS LU number too large |
Use an LU number within range. |
|
22 |
DOS sysname is not numeric or is misspelled |
Correct to a valid sysname. |
|
23 |
DOS sysname blank |
Do not use blank sysname. |
|
24 |
DOS LU not assigned |
Call CA Product Support. |
|
25 |
DOS DTF prototype missing |
Call CA Product Support. |
|
26 |
DOS logic module missing |
Generate missing logic module. |
|
27 |
DOS CCW mismatch |
Call CA Product Support. |
|
28 |
File is not a PDS |
Allocate file to a PDS. |
|
Copyright © 2013 CA.
All rights reserved.
|
|