|
1 or 2 |
The extended attributes (EAs) for an existing
REGIONAL(1) file could not be located and no RECCOUNT or RECSIZE values
were given via the ENVIRONMENT or SET DD option. |
|
3 |
A positioning error occurred for a sequential
output file. |
|
4 |
TYPE (FIXED) was specified for a native file,
but the file size was not a multiple of RECSIZE. |
|
5 or 13 |
A positioning error occurred for a REGIONAL(1)
file. |
|
6 - 12 |
A positioning error occurred for an output file. |
|
21 - 23 |
AMTHD(DDM) was specified on the SET DD statement
for a file, but the DDM DDLs (DUBRUN and DUBLDM) could not be found
or accessed. |
|
24 |
Incorrect extended attribute on a DDM file. |
|
25 |
The ORGANIZATION option of the ENVIRONMENT attribute
conflicts with the type of data set (DDM or native). |
|
26 |
Conflicts exist with how the file is being used. |
|
27 |
A composite key was detected with a keyed-opening. |
|
28 - 30 |
A new DDM file could not be created. |
|
31 |
A positioning error occurred for a DDM file. |
|
35 |
AMTHD(BTRIEVE) was specified on the DD environment
variable but the BTRIEVE loadable component (BTRCALLS) could not be
found or could not be accessed on the system. |
|
36 |
Unexpected error occurred when opening a BTRIEVE
file. |
|
37 |
A new BTRIEVE file could not be created. |
|
38 |
A positioning error occurred for a BTRIEVE file. |
|
40 |
AMTHD(ISAM) was specified on the DD environment
variable but the ISAM non-multithreading loadable components (IBMWS20F
and IBMWS20G) or the ISAM multithreading loadable components (IBMWM20F
and IBMWM20G) could not be found or could not be accessed on the system. |
|
41 |
Unexpected error occurred when opening an ISAM
file. |
|
42 |
A new ISAM file could not be created. |
|
43 |
A positioning error occurred for an ISAM file. |
|
60 |
A file of invalid type is being opened. An
example of this is opening a VSAM file under z/OS UNIX System Services.
VSAM files are not supported under z/OS UNIX System Services. |
|
62 |
Query for file information failed for a VSAM
file under MVS batch. |
|
63 |
A non-VSAM file is being opened as a VSAM file
under MVS batch. |
|
64 |
A VSAM file is being opened with an invalid
type (that is, the file is not a KSDS, ESDS or RRDS file). |
|
65 |
A VSAM file is being opened in a non-MVS batch
environment. VSAM files are supported only under MVS batch. |
|
66 |
Open of a VSAM file failed. Subcode 2 gives
the feedback code. |
|
67 |
A VSAM file is being opened as a non-VSAM file
under MVS batch. |
|
68 |
An invalid VSAM file is being opened. |
|
69 |
Query for file information failed for a native
file under MVS batch. |
|
70 |
Positioning for a VSAM file failed. |
|
71 |
A VSAM file is being opened under a non-MVS
batch environment. |
|
72 |
An invalid PL/I file is being opened. |
|
73 |
The SFS library cannot be loaded. |
|
74 |
The DCE library cannot be loaded. |
|
75 |
A new SFS file could not be created. |
|
77 |
Positioning for an SFS file failed. |
|
78 |
Not enough storage below the line. |
|
80 |
There was an error processing an empty VSAM
file opened for update. Oncode 82 should have been issued. |