Wednesday 2 November 2011

VSAM FILE STATUS CODES

             VSAM   FILE - STATUS   CODES

********************************
STATUS 00 SUCCESSFUL COMPLETION                 
********************************
SUCCESSFUL COMPLETION

************************
STATUS 02 DUPLICATE KEY
************************
Indexed files only. Possible causes are:
For a READ statement, the key value for the current key is equal
to the value of that same key in the next record in the current
key of reference

For a WRITE or REWRITE statement, the record just written created
a duplicate key value for at least one alternate record key for
which alternates are allowed

******************************
STATUS 04 WRONG LENGTH RECORD
******************************
The length of the record being processed does not conform to the
fixed file attributes for the file

************************
STATUS 05 MISSING FILE
************************
The referenced optional file is not present at the time the 0PEN
statement is executed

******************************
STATUS 06 WRITE TO INPUT FILE
******************************
Attempted to write to a file that has been opened for input

************************************
STATUS 07 INVALID REEL-UNIT REQUEST
************************************
Sequential files only. For an OPEN or CLOSE statement with the
REEL/UNIT phrase the referenced file is a non-reel/unit medium

*****************************
STATUS 08 READ AN INPUT FILE
*****************************
Attempted to read from a file opened for output

***********************************
STATUS 09 DIRECTORY DOES NOT EXIST
***********************************
No room in directory or directory  does not exist

**********************
STATUS 10 END OF FILE
**********************
You have reached end of file.

****************************
STATUS 12 FILE ALREADY OPEN
****************************
Attempted to open a file that is already open

*************************
STATUS 13 FILE NOT FOUND
*************************
File not found

****************************************************************
STATUS 14 TOO MANY FILES OPEN or INVALID RELATIVE RECORD NUMBER
****************************************************************
Too many files open simultaneously (Micro Focus)

                        OR

Relative files only. The number of significant digits in the
relative record number is larger than the size of the relative key
data item described for that file

**************************************
STATUS 15 TOO MANY INDEXED FILES OPEN
**************************************
Too many indexed files open (Micro Focus)

*************************************
STATUS 16 TOO MANY DEVICE FILES OPEN
*************************************
Too many device files open (Micro Focus)

*****************************
STATUS 17 ZERO LENGTH RECORD
*****************************
Record error: probably zero length (Micro Focus)

*******************************************
STATUS 18 END OF FILE BEFORE END OF RECORD
*******************************************
Read part record error: EOF before EOR or file open in wrong mode
(Micro Focus)

************************
STATUS 19 REWRITE ERROR
************************
Rewrite error: open mode or access mode wrong
(Micro Focus)

**********************
STATUS 20 DEVICE BUSY
**********************
Device or resource busy (Micro Focus)

*************************
STATUS 21 SEQUENCE ERROR
*************************
Sequentially accessed files only. Indicates a sequence error. The
ascending key requirement of successive record key values has
been violated, or the prime record key value has been changed by a
COBOL program between successful execution of a READ statement
and execution of the next REWRITE statement for that file

************************
STATUS 22 DUPLICATE KEY
************************
Indexed and relative files only. Indicates a duplicate key
condition. Attempt has been to store a record that would
create a duplicate key in the  indexed or relative file OR a
duplicate alternate record key that  does not allow duplicates.

**************************
STATUS 23 NO RECORD FOUND
**************************
Indicates no record found.  An attempt has been made to access a
record identified by a key, and that record does not exist in the
file. Alternatively a START or READ operation has been tried on an
optional input file that is not present.

***********************************************************
STATUS 24 BOUNDARY VIOLATION OR INVALID RELATIVE RECORD NO
***********************************************************
Relative and indexed files only. Indicates a boundary violation.

Possible causes are:
Attempting to write beyond the externally defined boundaries
of a file

A sequential WRITE operation has been tried on a relative
file, but the number of significant digits in the relative
number is larger than the size of the relative key data item
described for the file.

*********************************************
STATUS 30 BOUNDARY VIOLATION OR PARITY CHECK
*********************************************
I/O failed for a sequential file because of a boundary violation
or data check parity error or a transmission error

********************************
STATUS 32 TOO MANY FILES OPENED
********************************
Too many Indexed files opened. This can also happen when a
sequential file is open for input and an  attempt is made to open
the same file for output.
(Run Time System CRTS) message by Micro Focus).

**********************
STATUS 34 I/O FAILURE
**********************
The I/O statement failed because of a boundary violation. This
condition indicates that an attempt was made to write beyond the
externally defined boundaries of a sequential file.

******************************************
STATUS 35 OPEN A FILE THAT DOES NOT EXIST
******************************************
An OPEN operation with the I-O, INPUT, or EXTEND phrases has
been tried on a non-OPTIONAL file that does not exist. May need to
map the COBOL file name to the physical file name.
(Micro Focus, refer to the ASSIGN(EXTERNAL) directive)

*****************************
STATUS 37 OPEN MODE INVALID
*****************************
An OPEN operation has been tried on a file which does not support
the open mode specified in the OPEN statement.

******************************************
STATUS 38 OPEN ATTEMPTED ON A LOCKED FILE
******************************************
An OPEN operation has been tried on a file previously closed with
a lock.

*****************************
STATUS 39 ATTRIBUTE CONFLICT
*****************************
A conflict has been detected between the actual file attributes
and the attributes specified for the file in the program.

*************************************************************
STATUS 40 CONFLICT WITH RECORD OR KEY LENGTH OR KEY POSITION
OR FILE ORGANIZATION
*************************************************************
This is usually caused by a conflict with record length,
key length or position or file organization.

Other possible causes are:
1. Alternate indexes are incorrectly defined...(Key length or
position, duplicates or sparse parameters).
2. The recording mode is variable or fixed or not defined the
same as when the file was created.

****************************
STATUS 41 FILE ALREADY OPEN
****************************
An OPEN operation was attempted on a file already opened.

******************************
STATUS 42 FILE ALREADY CLOSED
******************************
A CLOSE operation was attempted on a file already closed.

*****************************************
STATUS 43 INCOMPATIBLE DELETE OR REWRITE
*****************************************
Files in sequential access mode: The last I/O executed for the
file, before the execution of a DELETE or REWRITE statement,
was not a READ statement.

*****************************
STATUS 44 BOUNDARY VIOLATION
*****************************
A boundary violation occurred. Possible causes:
1. Attempting to WRITE or REWRITE a record that is larger
than the largest, or smaller than the smallest record
allowed by the RECORD IS VARYING clause of the associated
file.
2. Attempting to REWRITE a record to a file and the record is
not the same size as the record being replaced.

************************
STATUS 45 REWRITE ERROR
************************
An attempt has been made to REWRITE a record to a file, and the
record is not the same size as the record being replaced.
(Micro Focus) For line sequential files this refers to the
physical size of the record, after space removal, tab compression
and null insertion. In this case, the physical size of the new
record is allowed to be smaller than the record being replaced.

**************************************
STATUS 46 NEXT RECORD NOT ESTABLISHED
**************************************
A sequential READ operation has been tried on a file open in the
INPUT or I-O mode but no valid next record has been established.

********************************
STATUS 47 INVALID READ OT START
********************************
A READ or START operation has been tried on a file not opened
INPUT or I-O.

************************
STATUS 48 INVALID WRITE
************************
A WRITE operation was tried on a file not opened in the
OUTPUT, I-O, or EXTEND mode, or on a file open I-O in the
sequential access mode.

************************************
STATUS 49 INVALID DELETE OR REWRITE
************************************
A DELETE or REWRITE was attempted on a file not opened I-O.

***********************************
STATUS 9000 NO FURTHER INFORMATION
************************************
No further information

**************************************
STATUS 9001 INSUFFICIENT BUFFER SPACE
**************************************
Insufficient buffer space. Could also indicate an out of memory
situation.

**************************
STATUS 9002 FILE NOT OPEN
**************************
File not open when access tried.

******************************
STATUS 9003 SERIAL MODE ERROR
******************************
Serial mode error

******************************
STATUS 9004 ILLEGAL FILE NAME
******************************
Illegal file name. Micro Focus: the COBOL file name may not be
mapped to a fully qualified PC file name. Check the
ASSGN/(EXTERNAL) directive and possible environment variable
setting for the COBOL file name.

*****************************************
STATUS 9005 ILLEGAL DEVICE SPECIFICATION
******************************************
Illegal Device Specification

**********************************************
STATUS 9006 ATTEMPT TO WRITE TO AN INPUT FILE
***********************************************
Attempt to write to a file opened for input.

*********************************
STATUS 9007 DISK SPACE EXHAUSTED
*********************************
Disk space exhausted

*************************************************
STATUS 9008 ATTEMPT TO READ FROM AN OUTPUT FILE
*************************************************
Attempt to input from a file opened for output.

*************************************
STATUS 9009 DIRECTORY DOES NOT EXIST
*************************************
No room in directory or directory does not exist.

***********************************
STATUS 9010 FILE NAME NOT SUPPLIED
***********************************
File name not supplied.

*********************************
STATUS 9012 FILE IS ALREADY OPEN
*********************************
Attempt to open a file that is already open.

***************************
STATUS 9013 FILE NOT FOUND
***************************
File not found.

*********************************
STATUS 9014 TOO MANY FILES OPEN
*********************************
Too many files open simultaneously.

********************************
STATUS 9015 TOO MANY FILES OPEN
********************************
Too many indexed files open.

***************************************
STATUS 9016 TOO MANY DEVICE FILES OPEN
***************************************
Too many device files open.

*************************
STATUS 9017 RECORD ERROR
*************************
Record error. Probable cause is zero record length.

***************************************
STATUS 9018 READ PARTIAL RECORD ERROR.
***************************************
Read partial record error: EOF before EOR or file open in wrong
mode. This can also be caused when a physical line sequential
(ASCII/Text) is being read as a sequential file and the
directive SEQUENTIAL/LINE)is not set (Micro Focus).

***************************
STATUS 9019 REWRITE ERROR.
***************************
Rewrite error: open mode or access mode wrong.

***************************
STATUS 9020 RESOURCE BUSY.
***************************
Device or resource busy.

********************************
STATUS 9021 FILE IS A DIRECTORY
********************************
File is a directory.

********************************
STATUS 9022 ILLEGAL ACCESS MODE
********************************
Illegal or impossible access mode for open.

********************************
STATUS 9023 ILLEGAL ACCESS MODE
********************************
Illegal or impossible access mode for close.

***************************
STATUS 9024 DISK I/O ERROR
***************************
Disk I/O error: Attempting to read a LINE SEQUENTIAL file as a
SEQUENTIAL file (Micro Focus).

****************************************
STATUS 9025 OPERATING SYSTEM DATA ERROR
****************************************
Operating system data error.

********************************
STATUS 9026 DISK NOT COMPATIBLE
********************************
Disk not compatible.

***********************************
STATUS 9027 DEVICE NOT AVAILABLE
***********************************
Device not available.

*******************************
STATUS 9028 NO SPACE ON DEVICE
*******************************
No space on device.

*****************************************
STATUS 9029 ATTEMPT TO DELETE OPEN FILE
*****************************************
Attempt to delete open file.

*************************************
STATUS 9030 FILE SYSTEM IS READ ONLY
*************************************
File system is read only.

*******************************
STATUS 9031 NOT OWNER OF FILE
*******************************
Not owner of file.

****************************
STATUS 9032 NO SUCH PROCESS
****************************
Too many indexed files or no such process.

*********************************
STATUS 9033 PHYSICAL I/O ERROR
*********************************
Physical I/O error.

**********************************************
STATUS 9034 INCORRECT MODE OR FILE DESCRIPTOR
**********************************************
Incorrect mode or file descriptor.

*********************************
STATUS 9035 ACCESS NOT PERMITTED
*********************************
Attempt to access file with incorrect permission.

*******************************
STATUS 9036 FILE AREADY EXISTS
*******************************
File already exists.

*********************************
STATUS 9037 FILE ACCESS DENIED
*********************************
File access denied.

********************************
STATUS 9038 INCOMPATIBLE DISK
********************************
Disk not compatible.

********************************
STATUS 9039 FILE NOT COMPATIBLE
********************************
File not compatible.

**********************************************
STATUS 9040 LANGUAGE INITIALIZATION INCORRECT
**********************************************
Language initialization not set up correctly.

*********************************
STATUS 9041 CORRUPT INDEX FILE
*********************************
Corrupt Index File.

********************************************
STATUS 9042 ATTEMPT TO WRITE ON BROKEN PIPE
********************************************
Attempt to write on broken pipe.

**************************************
STATUS 9043 MISSING FILE INFORMATION
**************************************
File information missing for indexed file.
(Micro Focus) This could indicate the filename IDX is missing.

*******************************************
STATUS 9045 OPEN WITH INCOMPATIBLE PROGRAM
*******************************************
Attempt to open an NLS file using an incompatible program.

*****************************************
STATUS 9047 - INDEXED STRUCTURE OVERFLOW
*****************************************
Indexed structure overflow. (Could indicate that you have
reached the maximum number of duplicate keys.

**************************
STATUS 9065 - FILE LOCKED
**************************
File locked.

***********************************
STATUS 9066 - DUPLICATE RECORD KEY
***********************************
Attempt to add a duplicate key to indexexd file.

************************************
STATUS 9067 - INDEXED FILE NOT OPEN
************************************
Indexed file not open.

****************************
STATUS 9068 - RECORD LOCKED
****************************
Record locked.

*******************************
STATUS 9069 - ILLEGAL ARGUMENT
*******************************
Illegal argument to ISAM module.

**********************************
STATUS 9070 - TOO MANY FILES OPEN
**********************************
Too many indexed files open.

*************************
STATUS 9071 - BAD FORMAT
*************************
Bad indexed file format.

**************************
STATUS 9072 - END OF FILE
**************************
End of indexed File.

******************************
STATUS 9073 - NO RECORD FOUND
******************************
No record found in indexed file.

********************************
STATUS 9074 - NO CURRENT RECORD
********************************
No current record in indexed file.

**********************************************
STATUS 9075 - Indexed data file name too long
**********************************************
Indexed data file name too long.

*******************************
STATUS 9076 - INTERNAL FAILURE
*******************************
Internal ISAM module failure.

***************************************
STATUS 9077 - ILLEGAL KEY DESCRIPTION
***************************************
Illegal key description in indexed file.

*******************************************************
STATUS 9078 - INVALID KEY DESCRIPTION IN INDEXED FILE
*******************************************************
Invalid key description in indexed file.

*********************************
STATUS 9081 - KEY ALREADY EXISTS
*********************************
Key already exists in indexed file.

*****************************************************
STATUS 9092 - ATTEMPT TO UPDATE WITHOUT PREVIOUS GET
*****************************************************
A PUT for update or an ERASE was issued without a previous GET
for update.

*************************************
STATUS 9100 - INVALID FILE OPERATION
*************************************
Invalid file operation.

********************************
STATUS 9101 - ILLEGAL FILE OPERATION.
********************************
Illegal operation on an indexed file

*********************************************
STATUS 9102 - NON-INTEGRAL NUMBER OF RECORDS
*********************************************
Sequential file with non-integral number of records.

*****************************
STATUS 9104 - NULL FILE NAME
*****************************
Null file name used in a file operation.

**************************************
STATUS 9105 - MEMORY ALLOCATION ERROR
**************************************
Memory allocation erro

****************************************
STATUS 9124 - REMOTE CONNECTION FAILING
****************************************
Connection to remote system is failing.
(Micro Focus) This could indicate a File Name is mapped to use
Fileshare and the Fileshare Server has not been started.

**********************************
STATUS 9125 - FILE SERVER FAILING
**********************************
Connection to remote system file server is failing (Micro Focus).

*********************************************
STATUS 9129 - ATTEMPT TO ACCESS RECORD ZERO
*********************************************
Attempt to access record zero of relative file.

**********************************
STATUS 9135 - FILE MUST NOT EXIST
**********************************
File must not exist.

************************************
STATUS 9138 - FILE CLOSED WITH LOCK
************************************
File closed with lock - cannot be opened.

***********************************
STATUS 9139 - RECORD INCONSISTENCY
***********************************
Record length or key data inconsistency.

********************************
STATUS 9141 - FILE ALREADY OPEN
********************************
File already open - cannot be opened.

****************************
STATUS 9142 - FILE NOT OPEN
****************************
File not open - cannot be closed.

**************************************************
STATUS 9143 - REWRITE/DELETE NOT PRECEDED BY READ
**************************************************
REWRITE/DELETE in sequential mode not preceded by
successful READ.

********************************
STATUS 9146 - NO CURRENT RECORD
********************************
No current record defined for sequential read.

***************************************
STATUS 9147 - WRONG OPEN MODE FOR READ
***************************************
Wrong open mode or access mode for READ/START.

****************************************
STATUS 9148 - WRONG OPEN MODE FOR WRITE
****************************************
Wrong open mode or access mode for WRITE. This can be caused
by issuing a READ after the end-of-file has been reached
during sequential processing.

*******************************************
STATUS 9149 - WRONG OPEN MODE FOR REWRITE
*******************************************
Wrong open mode or access mode for REWRITE/DELETE.

********************************
STATUS 9150 - PROGRAM ABANDONED
********************************
Program abandoned at user request.

**********************************
STATUS 9151 - INVALID RANDOM READ
**********************************
Random read on sequenetial file.

******************************
STATUS 9152 - INVALID REWRITE
******************************
REWRITE on file not opened I/O.

******************************
STATUS 9158 - INVALID REWRITE
******************************
Attempt to REWRITE to a line-sequential file.

*****************************
STATUS 9159 - MALFORMED FILE
*****************************
Malformed line-sequential file.

**********************************
STATUS 9161 - MISSING FILE HEADER
**********************************
File header not found.

***************************************
STATUS 9173 - CALLED PROGRAM NOT FOUND
***************************************
Called program not found.

************************
STATUS 9180 - EOF ERROR
************************
End-of-file marker error.

***************************************
STATUS 9182 - INVALID CONSOLE FUNCTION
***************************************
Console input or console output open in wrong direction.

***************************
STATUS 9183 - INVALID OPEN
***************************
Attempt to open line sequential file for I-O.

**********************************
STATUS 9188 - FILE NAME TOO LARGE
**********************************
File name too large.

************************************
STATUS 9193 - VARIABLE LENGTH ERROR
************************************
Error in variable length count.

**********************************
STATUS 9194 - FILE SIZE TOO LARGE
**********************************
File size too large.

**************************************************
STATUS 9195 - DELETE/REWRITE NOT PRECEDED BY READ
**************************************************
DELETE/REWRITE not preceded by a READ.

***********************************************
STATUS 9196 - RELATIVE RECORD NUMBER TOO LARGE
***********************************************
Record number too large in relative or indexed file.

************************************
STATUS 9210 - FILE CLOSED WITH LOCK
************************************
File is closed with lock.

*****************************
STATUS 9213 - TOO MANY LOCKS
*****************************
Too many locks.

******************************
STATUS 9218 - REEL/UNIT ERROR
******************************
Malformed MULTIPLE REEL/UNIT File.

No comments:

Post a Comment