Sybase: Runtime Errors
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. Recreate the XFD file.
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 ACUCOBOL-GT stored procedures
not found
or
ACUCOBOL-GT lock table missing
The installation of Acu4GL for Sybase creates a number of stored procedures and tables. At least one of these was not found.
9D,12 A column of a key is of data type TEXT or IMAGE, which is illegal
Columns that are part of an index may not be of type TEXT or type IMAGE. Check your key definition.
9D,13 Internal error
Multiple records were found with the same index (this is a Sybase error).
9D,14 DB library function returned an unexpected errordbinit
(Sybase) failed. An error message from Sybase will be displayed on the terminal.
9D,16 Trying to rename a table across databases
RENAME works only within the same database.
9D,17 Cache error (internal error)
The internal process cache has been corrupted. Please contact Acucorp Technical Support.
9D,18 Primary Key error
This means there was an error when creating the primary key for a secondary table.
9D,19 Table Size Error
The table is larger than Sybase will accept, either in the number of columns or in the number of bytes in the row. Use the SECONDARY_TABLE directive to get around this.
9D,20 (no message associated with this error)
This error tells you that you are trying to do something with a FAST_ACCESS table that is not allowed. See the FAST_ACCESS portion of section Configuration Variables to learn the restrictions for tables opened this way.