Mvs file status codes

File not closed by previous job. OPEN statement execution successful: File integrity verified. For more technical support, ask our Experts in our Mainframe Forum. Description of the Code. Successful completion. Not a valid File Status Key. 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.

Not a valid File Status Code. Attempted to read from a file opened for output. No room in directory or directory does not exist. Attempted to open a file that is already open. No next logical record at end. Relative files only. A sequential READ statement is attempted for the first time on an optional file that is not present.

Too many device files open. Record error: probably zero length. Rewrite error: open mode or access mode wrong Micro Focus only. Device or resource busy Micro Focus only. Too many Indexed files opened. An OPEN operation has been tried on a file previously closed with a lock. Attempt to randomly read a record that did not exist. Attempt to delete a record without reading it. Attempt to delete a record without opening the file in the I-O mode. Ask a Question on Forum.

Forums List. DB2 Tips. JCL Examples. MVS Tips. Interview Questions. Record not available, thereby new record written. Record found VSAM rec 1. Hence, record VSAM rec 1 rewritten. Back to top. Status Code 93 means resource not available. Since you didn't post actual code, all we can do is guess. Perhaps if you explain in more detail what you're doing, and show us code, we can make some suggestions.

Posted: Tue Nov 24, pm. I can imagine that probably in the coding that phenomenon was overlooked. For the rest i agree with the dino. Posted: Thu Nov 26, am.