Data Definition Language (DDL) Reference Manual

DDL Compiler Commands
Data Definition Language (DDL) Reference Manual—529431-004
9-103
TACL
The DDL compiler translates each DDL object (except constants) to one or more TACL
structures; the DDL compiler translates constants to TACL text variables.
For the data types that the DDL compiler generates for TACL source code, see
Table C-5 on page C-9.
When translating a definition or record, the DDL compiler generates a TACL structure
corresponding to the data type of each field or group of fields in the definition or record,
unless the field or group is defined with a TACL clause.
If a field definition or a field or group description includes a TACL clause, the DDL
compiler generates a TACL structure with the high-level TACL data type specified in
the TACL clause.
The DDL compiler performs these checks before generating TACL source code:
•
Checks whether a definition or record contains a data type not supported by TACL;
if so, the DDL compiler issues a warning.
•
Checks whether a definition, record, or token map generates a TACL structure with
more than 5,000 bytes; if so, the DDL compiler issues an error message and does
not generate the object.
•
Checks whether a CONSTANT generates a TACL text variable with a value
greater than 130 ASCII characters, including any tildes (~) emitted by the DDL
compiler; if so, the DDL compiler issues an error message and does not generate
the object.
In Example 9-53 on page 9-104, the DDL compiler retrieves the record CUSTOMER
from the open dictionary, translates it to TACL source code, and writes the source
code to the file \DALLAS.$DATA.SALES.TACLSRC. If this file already exists, the DDL
compiler appends the entry for CUSTOMER to the file. For the definition of the
CUSTOMER record, see the sample database schema in Appendix B, Sample
Schemas.