The difference may be in locating the acufh.dll. A value of binary zeroes is returned for the file status when a filetype(21) file cannot be opened because acufh.dll is not found. As it currently works, this is not a fatal error and the program continues, returning the invalid status of binary zeroes. A status of two ascii zeroes would indicate success, but two binary zeroes indicate nothing. There is RPI 608828 for this issue, that is, when acufh.dll is not found the program continues as if there were no error other than returning the invalid status of binary zeroes. (Note: filetype(21), that is RM files, are accessed through acufh.dll, which must be loadable for I/O on RM files with Visual COBOL.)
↧