Skip to main content

I have a mf cobol program that reads items from an indexed rm file. The filetype is set to 21. trying to open a file for output gives a file status error of 93. 

Reading the file works find but opening for output gives a 21. 

I have a mf cobol program that reads items from an indexed rm file. The filetype is set to 21. trying to open a file for output gives a file status error of 93. 

Reading the file works find but opening for output gives a 21. 

Hello,

I can do an open output without an issue with filetype(21) from an MF COBOL program. I am running Visual COBOL 2.3 Update 1. What version are you running?

Regards,

I have a mf cobol program that reads items from an indexed rm file. The filetype is set to 21. trying to open a file for output gives a file status error of 93. 

Reading the file works find but opening for output gives a 21. 

I am running version Micro Focus Visual COBOL 2.3 Version 2.3.02187.

If I use a different file, I can write to the file however I am opening (and closing) a file for input in one procedure then opening for output in another procedure. That is where the status 93 occurs.

I have a mf cobol program that reads items from an indexed rm file. The filetype is set to 21. trying to open a file for output gives a file status error of 93. 

Reading the file works find but opening for output gives a 21. 

It sounds to me like the file isn't being closed after the original open input which would cause the open output to fail. Please trace through your code and make sure that the close statement for that file is being done properly. Since open output requires exclusive access to the file the file cannot be open by the same or any other process at the time the open output occurs.

I have a mf cobol program that reads items from an indexed rm file. The filetype is set to 21. trying to open a file for output gives a file status error of 93. 

Reading the file works find but opening for output gives a 21. 

I thought of that and ran through the code a few times. The close is being called. Oddly enough it is working now....

Terms & ConditionsAccessibility statement