Data Definition Language (DDL) Reference Manual

DDL Messages
Data Definition Language (DDL) Reference Manual—529431-004
A-30
Cause. A The DDL compiler name containing a hyphen (-) might duplicate a
FORTRAN name.
Effect. When generating FORTRAN source code, the DDL compiler might use
another identifier with the same FORTRAN name but a different DDL name.
Recovery. Avoid using a hyphen in a name for a FORTRAN object.
Cause. A definition, record, or element name has more than 30 ASCII characters.
Effect. The DDL compiler rejects the object.
Recovery. Shorten the name and recompile.
Cause. A constant is used as a value, but the constant data type is not consistent with
the data type of the object receiving the value.
Effect. The DDL compiler rejects the object.
Recovery. Check the data type and use a constant whose value is a number for a
numeric type or a string for an alphanumeric type, then recompile the object.
Cause. The product version specified in the TOKEN-MAP statement does not match
bit fields stored in the same byte.
Effect. The DDL compiler rejects the TOKEN-MAP object.
Recovery. Specify the same product version for bit fields that share the same byte. If
a bit field extends across two bytes, specify the same product version for bit fields that
share the same word.
Cause. A COBOL level-number increment in a COBLEVEL command is equal to or
less than 0.
Effect. The DDL compiler does not change the increment.
Recovery. Correct the error and recompile if you want to.
***ERROR*** Identifier too long
***ERROR*** Improper type of Constant for this usage
***ERROR*** Inconsistent VERSION within byte- bit-field-name
***WARNING*** Increment is not a legal positive int- value
not changed