Doesn't matter, as it isn't normal behaviour in ISAM as defined by the COBOL standards. Can you please recheck GnuCOBOL 3 dev (preferably from SVN with generating the missing parts according to HACKING) or from https://sourceforge.net/projects/open-cobol/files/gnu-cobol/nightly_snapshots/ ?
If it still has the same behaviour please retry after replacing VBISAM with the patched VBISAM source posted by Ron in [8910169768#423a]? (it will need a while until I find the time to update the "official" VBISAM but I'm quite sure that this version is fine).
Doesn't matter, as it isn't normal behaviour in ISAM as defined by the COBOL standards. Can you please recheck GnuCOBOL 3 dev (preferably from SVN with generating the missing parts according to HACKING) or from https://sourceforge.net/projects/open-cobol/files/gnu-cobol/nightly_snapshots/ ?
If it still has the same behaviour please retry after replacing VBISAM with the patched VBISAM source posted by Ron in [8910169768#423a]? (it will need a while until I find the time to update the "official" VBISAM but I'm quite sure that this version is fine).
Related
Discussion: Could you please let me know regarding where we can get VBISAM for RHEL 7