Data Definition Language (DDL) Reference Manual

Sample Schemas
Data Definition Language (DDL) Reference Manual—529431-004
B-7
Sample SPI Schema
You do not generate COBOL, pTAL, TAL, or TACL source code for the standard SPI
definitions; HP supplies the COBOL, pTAL, TAL, or TACL source code in these files:
For this example, the DDL definitions that are not part of the standard SPI definition file
are contained in the file ASSNDDL. When you write a subsystem, the file name of the
file containing the subsystem’s DDL definitions must have this format:
ssssDDL
In the format, ssss is a code to identify the subsystem. In Figure B-1 on page B-2, the
subsystem code happens to be ASSN.
The file ASSNDDL contains the source code to define four simple tokens and one
extensible structured token. It contains all the DDL statements needed to define the
token types, token codes, and the token map. It also contains the DDL statements to
define the subsystem ID and the SPI message buffer.
When the DDL compiler compiles the source code in file ASSNDDL, it adds the
definitions in this file to the dictionary and generates three source code files:
The DDL compiler does not generate FORTRAN source code for SPI objects.
Topics:
•
DDL Commands to Create an SPI Schema on page B-8
•
Selected ZSPIDDL Statements on page B-8
•
ASSNDDL Statements on page B-10
Language File
COBOL ZSPIDEF.ZSPICOB
pTAL or TAL ZSPIDEF.ZSPITAL
TACL ZSPIDEF.ZSPITACL
File Description
ASSNCOB A COBOL source file that contains COBOL data descriptions for the DDL
statements in ASSNDDL.
ASSNTAL A pTAL or TAL source file that contains pTAL or TAL data definitions for the
DDL statements in ASSNDDL.
ASSNTACL A TACL source file that contains TACL data definitions for the DDL
statements in ASSNDDL.