Data Definition Language (DDL) Reference Manual

Sample Schemas
Data Definition Language (DDL) Reference Manual—529431-004
B-8
DDL Commands to Create an SPI Schema
DDL Commands to Create an SPI Schema
Example B-1 on page B-8 creates a dictionary from the DDL source file containing
standard SPI definitions (ZSPIDEF.ZSPIDDL) and from the file ASSNDDL containing
subsystem-specific definitions.
The SETSECTION commands in Example B-1 on page B-8 divide the host-language
source files into sections as recommended in the Distributed Name Service (DNS)
Management Programming Manual.
Selected ZSPIDDL Statements
The DDL statements from the file ZSPIDEF.ZSPIDDL in Example B-2 on page B-9 are
either used by the DDL statements in the file ASSNDDL or used in examples in this
manual. They are included here for documentation only. Do not copy these statements
individually—use the command SOURCE ZSPIDEF.ZSPIDDL to compile the entire set
of standard DDL statements into your dictionary as shown in the preceding set of DDL
commands.
Example B-1. Creating an SPI Schema
?ERRORS 1
?DICT !
?COMMENTS
?SOURCE ZSIPDEF.ZSPIDDL
On current default volume
?SETSECTION
Assure default DDL sectioning
?COBOL ASSNCOB !
COBOL source for subsystem
?TAL ASSNTAL !
TAL source for subsystem
?TACL ASSNTACL !
TACL source for subsystem
?SOURCE ASSNDDL (ASSN-DEFS)
Definitions specific to subsystem
?SETSECTION CONSTANTS
?SOURCE ASSNDDL (ASSN-TOKEN-INFO)
Token-related definitions
?SETSECTION
?SOURCE ASSNDDL (ASSN-BUFFER)
Buffer structure for subsystem
Note. Certain ZSPIDDL definitions cause the DDL compiler to issue warning messages when
it generates host-language source code. For example, the definition of ZSPI-DDL-BYTE
causes the DDL compiler to issue a warning when it generates COBOL source code. Because
COBOL does not recognize the BINARY 8 data type, the DDL compiler translates this
definition to PIC X(1). For data type translations that cause the DDL compiler to issue
warnings, see Appendix C, DDL Data Translation
.