Search results for query: *

I think JIH has it.... we rebuild the file before, delay the batch file 10 seconds, and then run the program getting the error. I bet the network just hasn't let go of the file - causing the 37. That would also explain why it happens sometimes, and sometimes it doesn't... If that particular...

The errors are: Runtime error 8 file status 37 for file FILENAME. A 37 is "Specified OPEN mode is not supported". This error makes no sense knowing that you can re-start the program and all works fine. and Runtime error 8 file status 30 for file FILENAME. A 30 is "Permanent Error". This...

The file the error is for is already opened I-O. I thought it might be opening too many files I-O... there are 8 in this particular program, and 6 open input. The error is never for any of the other files opened I-O, and it's the 3rd file to be opened I-O. Does this give you any more ideas?

Sorry - Cobol is Microfocus Visual Cobol 3.6. Operating system is Windows XP. The batch file runs in a dos window. No INTs or GNTs. Not sure what they are - we don't use them. tks

We have several programs that are "bugging" out with silly errors that don't make sense. For example - we'll get a runtime error 8 file status 37 for a file, then restart the program (changing nothing) and it runs fine. Sometimes it happens, sometimes it doesn't. There is no file corruption...