HP DDL D40 Reference Manual page 339

DDL Compiler Commands
NOTALCHECK
terminates the TALCHECK checking. If a pTAL or TAL source file is not open,
NOTALCHECK is the default.
TALCHECK Command Guidelines
The following points are guidelines for using the TALCHECK command:
If a pTAL or TAL source file is open, the compiler performs checks whether or not
TALCHECK is set.
You can stop pTAL or TAL syntax checking by specifying NOTALCHECK; you can
restart checking with a subsequent TALCHECK.
The DDL compiler does not perform the lengthy testing performed by the pTAL or
TAL compiler. The DDL compiler tests the DDL statements to ensure that they do
not violate the following rules of form specified by pTAL or TAL:
pTAL or TAL reserved words cannot be DDL names.
A constant value must not be greater than its defined limit.
A name cannot be longer than 31 ASCII characters, including suffixes (such as
^DEF, ^WLN, or ^KEY).
A REDEFINES clause cannot be at the level directly following that of a
definition or record.
TALCHECK Command Example
The following listing shows the error messages generated by the pTAL or TAL check
on a single RECORD statement:
?TALCHECK
RECORD location.
FILE IS "$data.sales.location" Key-
sequenced.
02 resident PIC X(15).
02 loc PIC X(3).
02 code PIC 999.
KEY IS resident.
END
Record LOCATION size is 21 bytes.
*** WARNING *** TAL OUTPUT DIAGNOSTICS:
*** ERROR *** Reserved word - RESIDENT
*** ERROR *** Reserved word - CODE
?NOTALCHECK
When TALCHECK is in effect, DDL issues the following message for each DDL object
that passes the syntax check:
TAL CHECK completed for name
Data Definition Language (DDL) Reference Manual—426798-002
Start syntax checking
Turn off checking
VST935.vsd
9 -109
TALCHECK Command