Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

what is the file status code 03

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
ksivapradeep

New User


Joined: 30 Jul 2004
Posts: 95

PostPosted: Thu Dec 16, 2004 12:40 pm    Post subject: what is the file status code 03
Reply with quote

hi all,

what is the file status code 03?


regards,
siva pradeep
Back to top
View user's profile Send private message

ovreddy

Active User


Joined: 06 Dec 2004
Posts: 211
Location: Keane Inc., Minneapolis USA.

PostPosted: Thu Dec 16, 2004 1:31 pm    Post subject: File Status code and Meaning...
Reply with quote

Hi siva,

As I know this is a great list of file status keys. 03 is not a valid file status key. Even If it exists it is vendor specific.

Bye,
Reddy.


1 & 2 Description

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

00 Successful completion
02 Indexed files only. Possible causes:
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 duplicates are allowed.
04 The length of the record being processed does not conform to the fixed file attributes for that file.
05 The referenced optional file is not present at the time the OPEN statement is executed.
06 Attempted to write to a file that has been opened for input.
07 Sequential files only. For an OPEN or CLOSE statement with the REEL/UNIT phrase the referenced file is a non-reel/unit medium.
08 Attempted to read from a file opened for output.
09 No room in directory or directory does not exist.
10 No next logical record exists. You have reached the end of the file.
12 Attempted to open a file that is already open.
13 File not found.
14 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.
Too many files open simultaneously (Micro Focus).
15 Too many indexed files open (Micro Focus).
16 Too many device files open (Micro Focus).
17 Record error: probably zero length (Micro Focus).
18 Read part record error: EOF before EOR or file open in wrong mode (Micro Focus).
19 Rewrite error: open mode or access mode wrong (Micro Focus).
20 Device or resource busy (Micro Focus).
21 Sequentially accessed files only. Indicates a sequence error. The ascending key requirements 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.
22 Indexed and relative files only. Indicates a duplicate key condition. Attempt has been made 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.
23 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.
24 Relative and indexed files only. Indicates a boundary violation. Possible causes:
Attempting to write beyond the externally defined boundaries of a file
Attempting a sequential WRITE operation has been tried on a relative file, but the number of significant digits in the relative record number is larger than the size of the relative key data item described for the file.
30 The I/O statement was unsuccessfully executed as the result of a boundary violation for a sequential file or as the result of an I/O error, such as a data check parity error, or a transmission error.
32 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 (RTS) message by Micro Focus).
34 The I/O statement failed because of a boundary violation. This condition indicates that an attempt has been made to write beyond the externally defined boundaries of a sequential file.
35 An OPEN operation with the I-O, INPUT, or EXTEND phrases has been tried on a non-OPTIONAL file that is not present.
37 An OPEN operation has been tried on a file which does not support the open mode specified in the OPEN statement.
38 An OPEN operation has been tried on a file previously closed with a lock.
39 A conflict has been detected between the fixed file attributes and the attributes specified for the file in the program.
This is usually caused by a conflict with record-length, key-length, key-position or file organization.
Other possible causes are:
1. Alternate indexes are incorrectly defined.
2. The Recording Mode is Variable or Fixed or not defined the same as when the file was created..
41 An OPEN operation has been tried on file already opened.
42 A CLOSE operation has been tried on file already closed.
43 Files in sequential access mode. The last I/O statement executed for the file, before the execution of a DELETE or REWRITE statement, was not a READ statement.
44 A boundary violation exists. Possible causes:
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
Attempting to REWRITE a record to a file and the record is not the same size as the record being replaced.
46 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.
47 A READ or START operation has been tried on a file not opened INPUT or I-O.
48 A WRITE operation has been 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.
49 A DELETE or REWRITE operation has been tried on a file that is not opened I-O.

Extended File Status Keys
(Next) (Previous) (Table-of-Contents)
The first character of the file-status-key is known as status-key-1. If status-key-1 is equal to 9 then status-key-2 is a binary value as defined in the following table.

Status-key-2
Decimal Status-key-2
Hex Description

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

000 00 No further information.
001 01 Insufficient buffer space. Could also indicate an out of memory situation.
002 02 File not open when access tried.
003 03 Serial mode error.
004 04 Illegal file name.
005 05 Illegal device specification.
006 06 Attempt to write to a file opened for input.
007 07 Disk space exhausted.
008 08 Attempt to input from a file opened for output.
009 09 No room in directory or directory does not exist.
010 0A File name not supplied.
012 0C Attempt to open a file that is already open.
013 0D File not found.
014 0E Too many files open simultaneously.
015 0F Too many indexed files open.
016 10 Too many device files open.
017 11 Record error, probable cause is zero record length.
018 12 Read partial record error: EOF before EOR or file open in wrong mode.
This can also be cause when a physical line sequential file (ASCII/Text) is being read as a sequential file and the directive SEQUENTIAL(LINE) is not set (Micro Focus).
019 13 Rewrite error: open mode or access mode wrong.
020 14 Device or resource busy.
021 15 File is a directory.
022 16 Illegal or impossible access mode for OPEN.
023 17 Illegal or impossible access mode for CLOSE.
024 18 Disk I/O error.
025 19 Operating system data error.
026 1A Block I/O error.
027 1B Device not available.
028 1C No space on device.
029 1D Attempt to delete open file.
030 1E File system is read only.
031 1F Not owner of file.
032 20 Too many indexed files, or no such process.
033 21 Physical I/O error.
034 22 Incorrect mode or file descriptor.
035 23 Attempt to access a file with incorrect permission.
036 24 File already exists.
037 25 File access denied.
038 26 Disk not compatible.
039 27 File not compatible.
040 28 Language initialization not set up correctly.
041 29 Corrupt index file.
042 2A Attempt to write on broken pipe.
043 2B File information missing for indexed file.
045 2C Attempt to open an NLS file using an incompatible program.
047 2D Indexed structure overflow. (Could indicate that you have reached the maximum number of duplicate keys.)
065 41 File locked.
066 42 Attempt to add duplicate record key to indexed file.
067 43 Indexed file not open.
068 44 Record locked.
069 45 Illegal argument to ISAM module.
070 46 Too many indexed files open.
071 47 Bad indexed file format.
072 48 End of indexed file.
073 49 No record found in indexed file.
074 4A No current record in indexed file.
075 4B Indexed data file name too long.
076 4C Internal ISAM module failure.
077 4D Illegal key description in indexed file.
081 51 Key already exists in indexed file.
092 5C A PUT for update or an ERASE was issued without a previous GET for update.
100 64 Invalid file operation.
101 65 Illegal operation on an indexed file.
102 66 Sequential file with non-integral number of records.
104 68 Null file name used in a file operation.
105 69 Memory allocation error.
124 7C Connection to remote system is failing (Micro Focus)
125 7D Connection to remote system file server is failing (Micro Focus)
129 81 Attempt to access record zero of relative file.
135 87 File must not exist.
138 8A File closed with lock - cannot be opened.
139 8B Record length or key data inconsistency.
141 8D File already open - cannot be opened.
142 8E File not open - cannot be closed.
143 8F REWRITE/DELETE in sequential mode not preceded by successful READ.
146 92 No current record defined for sequential read.
147 93 Wrong open mode or access mode for READ/START.
148 94 Wrong open mode or access mode for WRITE.
149 95 Wrong open mode or access mode for REWRITE/ DELETE.
150 96 Program abandoned at user request.
151 97 Random read on sequential file.
152 98 REWRITE on file not opened I-O.
158 9E Attempt to REWRITE to a line-sequential file.
159 9F Malformed line sequential-file.
161 A1 File header not found.
173 AD Called program not found.
180 B4 End-of-file marker error.
182 B6 Console input or console output open in wrong direction.
183 B7 Attempt to open line sequential file for I-O.
188 BC File name too large.
193 C1 Error in variable length count.
194 C2 File size too large.
195 C3 DELETE/REWRITE not preceded by a READ.
196 C4 Record number too large in relative or indexed file.
210 D2 File is closed with lock.
213 D5 Too many locks.
218 DA Malformed MULTIPLE REEL/UNIT file.
219 DB Operating system shared file limit exceeded.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts splitting a file abdulrafi DFSORT/ICETOOL 2 Fri Mar 24, 2017 11:51 am
No new posts Receive a file using PCOMM macro Harald.v.K IBM Tools 0 Thu Mar 23, 2017 6:50 pm
No new posts Export flat file data into excel sheet murali.andaluri DFSORT/ICETOOL 2 Mon Mar 20, 2017 5:39 pm
No new posts Formatting VB File Learncoholic DFSORT/ICETOOL 3 Mon Mar 20, 2017 12:29 pm
No new posts Updating a VSAM file with DISP=OLD sheersh JCL & VSAM 8 Tue Mar 14, 2017 6:14 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us