Thanks, I think I'll just add the file status, ignore it and be done with
it.  These programs have been working for years and years, so I don't feel
the need to change them too much.

I try to stay away from the COBOL stuff as much as possible, but sometimes
I have to.

But everytime I get into one, I try to:

A) externalize the file descriptions with a copy dds,
B) change assign statements from DISK-xxx to DATABASE-xxx

these changes at least make it easier to deal with the next time I get into

Thanks for the help,


---------original message------------
Personally I'd try fix it ASAP.  To identify the files you could add the
File Status and a check on open then log all files that caused a 95.

If I recall correctly, using the file status and ignoring it, will probably
produce the "safest" results.

The reason it happens by the way is that ANSI rules were tightened between
the dialects used for the 38 and 400 versions.  As a result an error status
(95) had to be issued to ensure ANSI compliance.  I can't look it up, but
this may be one of the "features" that can be disabled by a compile time
option - have you checked?

Jon Paris

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.