How to resolve file status 35

I have misinterpreted the error message. After looking it up I image your suggestion may be accurate, since it does not seem to be a variable length record. CICS Guy, my appologies, you were also on the right track. Dick, I was thinking that but I just couldn't see why anybody would specify carriage control on a byte line Just what I was thinking Posted: Mon Aug 27, pm.

There was after advance in that program. Comment List. Related Discussions. Resources Support. CyberRes Academy. Partner Portal.

Contact us. Privacy Policy Terms of Use. 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. Sequentially accessed files only. Indicates a sequence error. 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. 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.

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.

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.

This condition indicates that an attempt has been made to write beyond the externally defined boundaries of a sequential file.

Trying to open a file that does not exist. A conflict has been detected between the actual 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 Key length or position, duplicates or sparse parameters.

The Recording Mode is Variable or Fixed or not defined the same as when the file was created. For files with variable-length records the minimum and maximum record lengths for the actual file may not match the minimum and maximum record lengths used by the program. Files in sequential access mode.

A boundary violation exists. Micro Focus For line sequential files this refers to the physical size of the record, that is after space removal, tab compression and null insertion. In this case, the physical size of the new record is allowed to be smaller than that of the record being replaced. Root Cause: You are trying to open a file in a particular mode that is not allowed for that file. Fix: Check the file attribute in the actual file, the file attributes defined in the FD section of the program, the record length in your DCB Parameter and the record mode, etc.

Root Cause: If you try to sequentially read a file even when the end of the record is reached. Fix: Check the password which is given for VSAM file or whether you are authorized to access the file or not? This might happen when a previous Job did not close the file so VSAM has to verify the integrity of the file. Fix: Before building the alternate index AIX and path, you need to load the cluster. During the processing of a VSAM file, some system error occurs and it is subsequently unusable how to fix this issue?