Data Definition Language (DDL) Reference Manual

DDL Compiler Commands
Data Definition Language (DDL) Reference Manual529431-004
9-65
FORTRAN
Unless the command FORTRANUNDERSCORE on page 9-66 is in effect, the DDL
compiler discards any hyphens in a DDL name before writing the name to FORTRAN
source code.
FORTRAN does not support unsigned numbers. If you specify an unsigned number,
the DDL compiler translates it to a FORTRAN signed integer.
FORTRAN does not accept FILLER fields greater than 255 single-byte characters. the
DDL compiler can add filler characters to ensure that structures start on word
boundaries; if such padding generates more than 255 filler characters, the DDL
compiler breaks them into smaller fields before writing the FORTRAN source code.
The DDL compiler performs all of the syntax checks listed under the FORCHECK
command before writing source output. If the compiler finds a syntax error, it does not
write the source output for the DDL object with the error; it does write source output for
a DDL object if only a warning is issued.
The DDL compiler ignores the RENAMES clause when generating FORTRAN source
output.
In Example 9-29 on page 9-65, the DDL compiler retrieves the definition of the record
CUSTOMER from the open dictionary, translates it to FORTRAN source code, and
writes it to the file \DALLAS.$DATA.SALES.FORSRC. 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. FORTRAN does not recognize the UPSHIFT clause, but is included as a
comment.
Note. The DDL compiler translates objects named A-B and AB to data structures that have the
same name in FORTRAN (unless FORTRANUNDERSCORE has been specified).
Example 9-29. FORTRAN Command (page 1 of 2)
DDL Input
?DICT
?FORTRAN \dallas.$data.sales.forsrc
OUTPUT RECORD customer.