Data Definition Language (DDL) Reference Manual

DDL Compiler Commands
Data Definition Language (DDL) Reference Manual—529431-004
9-62
FORCHECK
When FILLER 0 is specified, the structure of TEST1 in CASE1 differs from the
structure of TEST1 in CASE2. A COBOL program containing these data structures can
not successfully execute the preceding MOVE statement.
FORCHECK
The [NO]FORCHECK command performs [suppresses] FORTRAN syntax checks on
subsequent DDL object definitions without generating code.
Default: FORCHECK if a FORTRAN source code file is open, otherwise
NOFORCHECK
FORCHECK
performs the FORTRAN syntax checks as though FORTRAN source code were
being produced.
NOFORCHECK
suppresses FORTRAN syntax checks.
If a FORTRAN source code file is open, the compiler performs the FORTRAN checks
whether or not FORCHECK is set.
You can stop FORTRAN syntax checking with a NOFORCHECK command; you can
restart checking with a subsequent FORCHECK.
The DDL compiler does not make all the lengthy syntax tests that the FORTRAN
compiler makes. The DDL compiler tests the DDL statements to ensure that they follow
the rules specified by FORTRAN:
•
An elementary field must not be larger than 255 bytes.
•
An element must not be described as TYPE CHARACTER 8; this data type is not
supported in FORTRAN.
Caution. Mixing FILLER 1 and FILLER 0 can cause the DDL compiler to generate unusable
code. Using the preceding CASE1 as an example, if you add the definition to a dictionary while
FILLER 0 is in effect and later output the definition with FILLER 1 (the default) in effect, the
DDL compiler generates COBOL source code with two added fillers (one preceding TEST1
and the other within it, as in both of the CASE1 examples), causing the computational item to
begin in the middle of a word. This is incorrect for either FILLER option. Results are similar for
languages other than COBOL.
[NO]FORCHECK