Created On: 7 June 2010
Problem:
When working with COBOL files that are defined as Heap Files using the Filetype"14" directive, a close on the file would sometimes result in a bad file status such as a 9/013 "File not Found" error being returned.
There is a problem with the logic in the File Handler for the CLOSE statement handling of Heapfiles where the return-code was being checked prior to the actual close operation being performed. This means that if there was a bad status code from a previous operation in the File Handler then the error would actually be reported for the close because the status code area was not cleared out. So the close wasn't really failing, it was just been reported as bad because there was another operation that actually failed.
There is a problem with the logic in the File Handler for the CLOSE statement handling of Heapfiles where the return-code was being checked prior to the actual close operation being performed. This means that if there was a bad status code from a previous operation in the File Handler then the error would actually be reported for the close because the status code area was not cleared out. So the close wasn't really failing, it was just been reported as bad because there was another operation that actually failed.
Resolution:
This problem has been fixed in Net Express 5.1 Wrappack 4 Hotfix 5 and above.
Incident #2448545
Old KB# 31153
