File status code 34 in cobol

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. Other possible causes are: Alternate indexes are incorrectly defined. The Recording Mode is Variable or Fixed or not defined the same as when the file was created.

OPEN statement execution successful: File integrity verified. Share this: Twitter Facebook. Like this: Like Loading Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:. Email required Address never made public. Name required. Follow Following. IBM Mainframe tutorials. Quite often, to reach larger markets or provide a higher level of service to existing customers it requires the newer Internet technologies to work in a complementary manner with existing corporate mainframe systems.

We specialize in preparing applications and the associated data that are currently residing on a single platform to be distributed across a variety of platforms. Preparing the application programs will require the transfer of source members that will be compiled and deployed on the target platform. The data will need to be transferred between the systems and may need to be converted and validated at various stages within the process.

SimoTime has the technology, services and experience to assist in the application and data management tasks involved with doing business in a multi-system environment. Table of Contents. File Status Code Overview. Primary File Status. Extended File Status, nnn-xx. Software Agreement and Disclaimer.

Current Server or Internet Access. Internet Access Required. Glossary of Terms. Comments or Feedback. Company Overview. Status Key Description by Group. Successful Completion or non-terminal condition that may be acceptable to continue processing. Refer to the section for Status-Key-1 being equal to "0" for additional information based on Status-Key End of File , attempting to read beyond the end of the file.

Refer to the section for Status-Key-1 being equal to "1" for additional information based on Status-Key Invalid Key , an attemprt to access a file failed because the requested key is not available for processing.

The error may be caused by an invalid key or the sequence of processing for a valid key. Refer to the section for Status-Key-1 being equal to "2" for additional information based on Status-Key Permanent Error , usually caused by a limit in the logical processing or a difference in the logical file definitions and the physical file.

Refer to the section for Status-Key-1 being equal to "3" for additional information based on Status-Key Logic Error , a program is attempting a file access function in an improper sequence or beyond the capabilities of the physical file functions. Refer to the section for Status-Key-1 being equal to "4" for additional information based on Status-Key Implementor Defined , Many vendors take advantage of the x"00' to x'FF' or binary value.

Therefore, the file status-key-2 may not always be a numeric value that is easy to display. Refer to the section for Status-Key-1 being equal to "9" for additional information based on Status-Key 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.

The length of the record being processed does not conform to the fixed file attributes for that file. Sequential files only.

File not found. Also, check to see if the path to the file concerned exists Micro Focus. 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.

One of two possibilities: 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. You have reached the end of the file. 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. Indicates a sequence error.