Data Definition Language (DDL) Reference Manual

DDL Messages
Data Definition Language (DDL) Reference Manual—529431-004
A-63
Cause. An odd-length string definition contains an OCCURS clause that cannot be
translated to pTAL or TAL. When generating pTAL or TAL source for a string, the DDL
compiler usually emits a struct for the string field. Because this particular string is an
odd length, the DDL compiler would have to add a filler to word-align the struct.
Effect. The DDL compiler does not write the definition to the pTAL or TAL source file.
Recovery. Change the DDL definition so make the definition even length. Recompile
the definition.
Cause. A record or definition is too large to fit in the symbol table.
Effect. The DDL compiler closes the dictionary and source code files and stops
processing.
Recovery. Reduce the complexity of the data structure by defining the object in
multiple DEFINITION or RECORD statements, and recompile the object.
Cause. You requested TACL output for an object, but the object does not conform to
TACL rules.
Effect. A message follows describing the TACL error. The DDL compiler does not
write the object to the TACL source file.
Recovery. Correct the error and recompile.
Cause. The name of a definition or token map exceeds the limit of 31 ASCII
characters pTAL or TAL allows for these names.
Effect. The DDL compiler does not write the definition or token map to the pTAL or
TAL source file.
Recovery. Shorten the name, recompile the definition or token map, and request
output to the pTAL or TAL source file.
***ERROR*** Structure alignment in TAL is incompatible with
DDL- element-name
***FATAL ERROR*** Symbol table is full
***WARNING*** TACL OUTPUT DIAGNOSTICS:
***ERROR*** TAL DEF or TOKEN MAP name too long