SPI Programming Manual (G06.24+, H06.03+, J06.03+)

Summary of DDL for SPI
SPI Programming Manual—427506-006
B-7
DDL Data Translation
This notation is not DDL code, but is a shortened notation designed to give the
information needed. For instance, the example above reflects this TOKEN-CODE
statement in the definition file ZSPIDEF.ZSPIDDL:
TOKEN-CODE zspi-tkn-context VALUE IS zspi-tnm-context
TOKEN-TYPE IS zspi-typ-bytestring.
DDL Data Translation
The DDL compiler can translate any DEF statement into data-declaration source code
in TAL, C, COBOL, or TACL. The only restriction is that not all data types are
supported in all four languages. Whenever a declared data type is not supported in a
particular language, DDL attempts to translate the data type into a declaration of a
compatible data type. For example, DDL structures described with PIC X or PIC 9
clauses are translated into STRING BYTE types in TAL; a structure described as PIC
S9(4) COMP is translated into a TAL or TACL INT data type or a COBOL NATIVE-2
data type.
When no compatible data type is available, DDL translates the data type into a
character-string declaration. For example, a structure described as TYPE FLOAT,
which is the REAL data type in TAL, is translated into PIC X(4) in COBOL.
For additional examples of DDL DEF source and the resulting output in TAL, C,
COBOL, and TACL, see the information about DDL data translation in the
Data
Definition Language (DDL) Reference Manual .