|
|
|
|
| Table 36. Status Key Values and Meanings |
High-
Order
Digit |
Meaning
|
Low-
Order
Digit |
Meaning
|
|---|
0
 X
X
X
|
Successful
Completion
X
X
X
|
0 |
No further information |
2
|
This file status value only applies to
indexed files with alternate keys that
allow duplicates.
The input-output statement was
successfully executed, but a duplicate key
was detected. For a READ statement the
key value for the current key of reference
was equal to the value of the same key in
the next record within the current key of
reference. For a REWRITE or WRITE
statement, the record just written created
a duplicate key value for at least one
alternate record key for which duplicates
are allowed. |
4
|
A READ statement was successfully
executed, but the length of the record
being processed did not conform to the
fixed file attributes for that file. |
5
X
X
X |
An OPEN statement is successfully executed
but the referenced optional file is not
present at the time the OPEN statement is
executed. The file has been created if
X the open mode is I-O or EXTEND. This does
X not apply to OS/390 and VM VSAM sequential
X files. |
7
|
For a CLOSE statement with the NO REWIND,
REEL/UNIT, or FOR REMOVAL phrase or for an
OPEN statement with the NO REWIND phrase,
the referenced file was on a non-reel/unit
medium. |
1
|
At end
condition
|
0
|
A sequential READ statement was attempted
and no next logical record existed in the
file because the end of the file had been
reached, or the first READ was attempted
on an optional input file that was not
present. |
4
|
A sequential READ statement was attempted
for a relative file and the number of
significant digits in the relative record
number was larger than the size of the
relative key data item described for the
file. |
2
|
Invalid key
condition
|
1
|
A sequence error exists for a sequentially
accessed indexed file. The prime record
key value has been changed by the program
between the successful execution of a READ
statement and the execution of the next
REWRITE statement for that file, or the
ascending requirements for successive
record key values were violated.
Under OS/2 for Btrieve indexed files, file
status 21 is not applicable. You can
create records sequentially in any key
order. |
2
|
An attempt was made to write a record that
would create a duplicate key in a relative
file; or an attempt was made to write or
rewrite a record that would create a
duplicate prime record key or a duplicate
alternate record key without the
DUPLICATES phrase in an indexed file. |
3
|
An attempt was made to randomly access a
record that does not exist in the file, or
a START or random READ statement was
attempted on an optional input file that
was not present. |
4
|
An attempt was made to write beyond the
externally defined boundaries of a
relative or indexed file. Or, a
sequential WRITE statement was attempted
for a relative file and the number of
significant digits in the relative record
number was larger than the size of the
relative key data item described for the
file. |
3
X
X
X |
Permanent
error
condition
X
X
X |
0 |
No further information |
4
|
A permanent error exists because of a
boundary violation; an attempt was made to
write beyond the externally-defined
boundaries of a sequential file. |
5
|
An OPEN statement with the INPUT, I-O, or
EXTEND phrase was attempted on a
non-optional file that was not present. |
7
|
An OPEN statement was attempted on a file
that would not support the open mode
specified in the OPEN statement. Possible
violations are:
1. The EXTEND or OUTPUT phrase was
specified but the file would not
support write operations.
2. The I-O phrase was specified but the
file would not support the input and
output operations permitted.
3. The INPUT phrase was specified but the
file would not support read
operations. |
8
|
An OPEN statement was attempted on a file
previously closed with lock. |
9
X
X
X |
The OPEN statement was unsuccessful
because a conflict was detected between
the fixed file attributes and the
attributes specified for that file in the
program. These attributes include the
organization of the file (sequential,
relative, or indexed), the prime record
key, the alternate record keys, the code
set, the maximum record size, the record
type (fixed or variable), and the blocking
factor.
X Under AIX, OS/2, and Windows, file status
X 39 is not supported for line sequential
X files or Btrieve files. |
4
|
Logic error
condition
|
1
|
An OPEN statement was attempted for a file
in the open mode. |
2
|
A CLOSE statement was attempted for a file
not in the open mode. |
3
|
For a mass storage file in the sequential
access mode, the last input-output
statement executed for the associated file
prior to the execution of a REWRITE
statement was not a successfully executed
READ statement.
For relative and indexed files in the
sequential access mode, the last
input-output statement executed for the
file prior to the execution of a DELETE or
REWRITE statement was not a successfully
executed READ statement. |
4
|
A boundary violation exists because an
attempt was made to rewrite a record to a
file and the record was not the same size
as the record being replaced, or an
attempt was made to write or rewrite a
record that was larger than the largest or
smaller than the smallest record allowed
by the RECORD IS VARYING clause of the
associated file-name. |
6
|
A sequential READ statement was attempted
on a file open in the input or I-O mode
and no valid next record had been
established because:
1. The preceding READ statement was
unsuccessful but did not cause an at
end condition
2. The preceding READ statement caused an
at end condition. |
7
|
The execution of a READ statement was
attempted on a file not open in the input
or I-O mode. |
8
|
The execution of a WRITE statement was
attempted on a file not open in the I-O,
output, or extend mode. |
9
|
The execution of a DELETE or REWRITE
statement was attempted on a file not open
in the I-O mode. |
9
|
Implementor-
defined
condition
|
0 |
No further information. |
1
|
For VSAM only on OS/390 and VM: Password
failure.
Under AIX, OS/2, and Windows:
Authorization failure. |
| 2 |
Logic error. |
3
|
For all files, except QSAM: Resource not
available. |
4
|
For VSAM under OS/390 and VM with CMPR2
compiler-option only: No file position
indicator for sequential request.
Under AIX, OS/2, and Windows: Concurrent
open error. |
5
|
For all files, except QSAM: Invalid or
incomplete file information. |
6
|
For VSAM file under OS/390 and VM: An
OPEN statement with the OUTPUT or EXTEND
phrase was attempted for an optional file,
but no DD statement was specified for the
file.
For QSAM file under OS/390 and VM: An
OPEN statement with the OUTPUT or EXTEND
phrase was attempted for an optional file,
but no DD statement was specified for the
file and the CBLQDA(OFF) run-time option
was specified.
Under AIX, OS/2, and Windows: File system
not available. |
7
|
For VSAM only under OS/390 and VM: OPEN
statement execution successful: File
integrity verified.
Under AIX, OS/2, and Windows: Errors
related to remote file access. |
8
|
Under AIX, OS/2, and Windows: Open failed
due to locked file. |
9
|
Under AIX, OS/2, and Windows: Record
access failed due to locked record. |
Adobe, the Adobe logo, Acrobat, the Acrobat logo, and Acrobat Reader are registered trademarks
of Adobe Systems incorporated.
