Sample Schemas
Data Definition Language (DDL) Reference Manual — 426798-002
B- 8
DDL Commands to Create an SPI Schema
For this example, the DDL definitions that are not part of the standard SPI definition file
are contained in the file ASSNDDL. Note that when you write a subsystem, the file
name of the file containing the subsystem’s DDL definitions should have this format:
ssssDDL
In the format,
ssss
is a code to identify the subsystem. In the preceding example, 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 DDL compiles the source code in file ASSNDDL, it adds the definitions in this file
to the dictionary and generates three source-code files:
DDL does not generate FORTRAN source code for SPI objects.
DDL Commands to Create an SPI Schema
The following commands create a DDL dictionary from the DDL source file containing
standard SPI definitions (ZSPIDEF.ZSPIDDL) and from the file ASSNDDL containing
subsystem-specific definitions:
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.
? ERRORS 1
? DICT !
? COMMENTS
? SOURCE ZSPIDEF.ZSPIDDL
? SETSECTION
? COBOL ASSNCOB !
? TAL ASSNTAL !
? TACL ASSNTACL !
? SOURCE ASSNDDL (ASSN-DEFS)
? SETSECTION CONSTANTS
? SOURCE ASSNDDL (ASSN-TOKEN-INFO)
? SETSECTION
? SOURCE ASSNDDL (ASSN-BUFFER)
On current default volume
Assure default DDL sectioning
COBOL source for subsystem
TAL source for subsystem
TACL source for subsystem
Definitions specific to
subsystem
Token-related definitions
Buffer structure for
subsystem
VSTB02.vsd