The file status in GnuCOBOL is COBOL 202x based, with extensions where necessary. The settings you mention is an ACUCOBOL setting, if I'm not wrong this is directly taken care by the file handlers directly so an EXTFH interface would have take care of it, too.
For GnuCOBOL we already have the accepted [feature-requests:#348] but no one has adjusted GnuCOBOL's filio to handle anything like this yet.
As you use EXTFH in any case I suggest to write a little C routine that calls libcob's EXTFH and translates the status codes (this may not be accurate in every case, but may be enough for you). You'd then adjust the setting to use the C routine instead of libcob and A_EXTFH_FUNC to your C routine.
The first thing to do is to come up with the mapping (you may want to get the 202x CD 1 to check the standard codes) and the second thing is to write the C routine (relative easy, you may have someone with little C knowledge to write it).
Nice to hear it works.
The file status in GnuCOBOL is COBOL 202x based, with extensions where necessary. The settings you mention is an ACUCOBOL setting, if I'm not wrong this is directly taken care by the file handlers directly so an EXTFH interface would have take care of it, too.
For GnuCOBOL we already have the accepted [feature-requests:#348] but no one has adjusted GnuCOBOL's filio to handle anything like this yet.
As you use EXTFH in any case I suggest to write a little C routine that calls libcob's EXTFH and translates the status codes (this may not be accurate in every case, but may be enough for you). You'd then adjust the setting to use the C routine instead of libcob and
A_EXTFH_FUNCto your C routine.The first thing to do is to come up with the mapping (you may want to get the 202x CD 1 to check the standard codes) and the second thing is to write the C routine (relative easy, you may have someone with little C knowledge to write it).
Simon
Related
Wish List: #348