Runtime errors will have this format:
9D,xx
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:
9D,01 Read error on dictionary file
An error occurred while reading the XFD file; this probably means the XFD is corrupt. Recompile with -Fx to re-create the dictionary.
9D,02 Corrupt dictionary file
The dictionary file for one of your COBOL files is corrupt and cannot be read. Recompile with -Fx to re-create the dictionary.
9D,03 Dictionary (.xfd) file not found
The dictionary file for one of your COBOL files cannot be located. Be sure you have specified the correct directory via your XFD-DIRECTORY runtime configuration file variable. You may need to recompile with -Fx to create the dictionary.
9D,04 Too many fields in the key
There are more than 16 fields in a key. Check your key definitions and re-structure the key that is illegal, then recompile with -Fx.
9D,11 ODBC connection missing needed functionality
Because ODBC has so many implementations, we require certain minimal functionality. This includes: the ability to list columns, list primary keys, list existing tables, and support Level 1 SQL. Your ODBC driver lacks one or more of these capabilities.
9D,12 ODBC library function returned an unexpected error
One of the ODBC library functions returned an error that was not expected.
9D,13 Illegal size or type of data for variable xxx
An elementary data item in your FD was larger than 255 bytes, or there is no ODBC type that matches the current data type.
9D,14 More than one table with the same name
When tables were listed, more than one table was found with the same name.
9D,15 ODBC driver missing needed types
The driver doesn't support the data types needed for Acu4GL for ODBC.