This topic lists the Acu4GL error messages that could occur during execution of your program. The topic Compiler Errors provides information on compile-time errors and also provides several methods for retrieving runtime errors.
An explanation and a recommended recovery procedure follow each message.
Runtime errors will have this format:
The 9D indicates a file system error and is reported in your FILE STATUS variable. The xx is a secondary error code. These are the secondary errors reported directly from Acu4GL:
An error occurred while reading the XFD file; this probably means the XFD is corrupt. Recompile with -Fx to re-create the dictionary.
The dictionary file for one of your COBOL files is corrupt and cannot be read. Recompile with -Fx to re-create the dictionary.
The dictionary file for one of your COBOL files cannot be located. Be sure you have specified the correct directory via your XFD_PREFIX runtime configuration file variable. You may need to recompile with-Fx to create the dictionary.
There are more than 16 fields in a key. Check your key definitions and restructure the key that is illegal, and then recompile with -Fx.
01 - mismatch found but exact cause unknown (this status is returned by the host file system)
02 - mismatch found in file's maximum record size
03 - mismatch found in file's minimum record size
04 - mismatch found in the number of keys in the file
05 - mismatch found in primary key description
06 - mismatch found in first alternate key description
07 - mismatch found in second alternate key description
The list continues in this manner for each alternate key.
One of the DB2 library functions returned an error that was not expected.
An elementary data item in your FD was larger than 255 bytes, or there is no DB2 type that matches the current data type.
When tables were listed, more than one table was found with the same name. Consider whether or not setting the USER_PATH configuration variable will resolve the issue. This variable will enable tables with identical names, but with different ownership (located in a different schema) to be found and accessed.