Runtime errors will have this format:
9D,xxxx
The 9D indicates a file system error and is reported in your FILE STATUS variable. The xx is a secondary, database-specific error code. These are the secondary errors reported directly from Acu4GL for Oracle:
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 configuration variable. You may need to recompile with -Fx to create the dictionary.
9D,04 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. Note that this error may be caused by inappropriate application of a directive. Check all directives, and call Acucorp Technical Support if you have questions.
9D,05 Too many fields in the key (more than 16 for Oracle)
Check your key definitions and redefine the key that is illegal, then
recompile with
-Fx.
9D,06 Mismatched dictionary file
The dictionary file (.xfd) for one of your files conflicts with the COBOL description of the file FD. The "xx" indicates a tertiary error code that is defined by the host file system. You can determine the exact nature of the mismatch by referring to the host system's error values.
The tertiary error code may have any of these values:
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.
9D,08 Attempt to use multiple users
An attempt was made to change the login name during processing. Check your login name.
There are additional 9D secondary error numbers. These are Oracle error codes. You can determine the meanings of Oracle database error codes by referring to the Oracle documentation.
The prepare portion is aged out of cache. Re-enter the code while invalidating the prepare portion.