HP DDL D40, Справочное руководство

Страница: 335 / 576

DDL Compiler Commands
Data Definition Language (DDL) Reference Manual — 426798-002
9 -105
TAL Command
°
Appends ^WLN to every SPI TOKEN-MAP name
°
Appends ^KEY to every primary-key name and alternate-key name
As a result, the maximum length for the name of a DDL group definition, record,
token map, or key that is to be written to pTAL or TAL is 27 ASCII characters, not
the standard DDL name length of 30 characters.
•
The pTAL or TAL source code for a definition or record compiled with the
CFIELDALIGN_MATCHED2 command contains the fillers added by DDL as
specified by the alignment algorithm in effect when the definition or record was
compiled.
•
For the data types that DDL generates for pTAL or TAL source code, see Table C-6
on page C-12.
•
The DDL compiler performs all of the syntax checks listed under the TALCHECK
command before writing the pTAL or TAL source output. If DDL finds a syntax
error, it does not write the source output for the object with the error; it does write
source output for an object if only a warning is issued.
•
The lower bound for pTAL or TAL arrays can be set with the TALBOUND
command.
TAL Command Example
In the following example, DDL opens the dictionary, opens and then clears the file
\DALLAS.$DATA.SALES.TALSRC, retrieves the record CUSTOMER from the open
dictionary, translates it into pTAL or TAL source code, and then writes it to the open
pTAL or TAL source file. For the definition of the CUSTOMER record, see the sample
database schema in
Appendix B, Sample Schemas .
47> DDL
!?DICT
!?TAL \dallas.$data.sales.talsrc !
!OUTPUT RECORD customer.
?SECTION CUSTOMER
?PAGE
STRUCT CUSTOMER^DEF (*);
BEGIN
STRUCT CUSTNUM;
BEGIN STRING BYTE [1:4]; END;
STRUCT CUSTNAME;
BEGIN
STRUCT LAST^NAME;
BEGIN STRING BYTE [1:12]; END;
!Upshift
STRUCT FIRST^NAME;
BEGIN STRING BYTE [1:8]; END;
!Upshift
STRUCT MIDINIT;
BEGIN STRING BYTE [1:2]; END;
!Upshift