DSM/Tape Catalog Management Programming Manual

SPI Programming Considerations
DSM/Tape Catalog Management Programming Manual—520481-003
3-2
Syntax Elements
For a particular category of definitions (in this case, ZSPI or ZMCS), the language-
specific files are generated from one file containing definitions expressed in HP’s Data
Definition Language. This file has a language code of DDL. Thus, the file ZMCSDDL is
the source file for the definitions files ZMCSC, ZMCSCOB, ZMCSPAS, ZMCSTACL, and
ZMCSTAL.
These files are commonly found on the operating-system software release volume in
the subvolume ZSPIDEF, but can be stored elsewhere by your system management.
Syntax Elements
The command and response syntax that makes up SPI messages for the DSM/TC
subsystem is described in these categories:
Commands
Commands are requests for action (by a subsystem) or requests for information (from
a subsystem), conveyed as interprocess messages from a management application to
a subsystem.
A command number is used to represent a particular command to a subsystem. The
DSM/TC subsystem has its own set of command numbers, which are 16-bit integers.
The command number is an SPI buffer header field in an SPI command and response
buffer. The ZSPI-TKN-COMMAND header token is included in all commands and
responses, and it contains a command itself.
Programs use names of this form to represent commands:
command
identifies a programmatic command.
Category Page
Commands
3-2
Object Types and Object Names 3-3
Tokens 3-3
The Command Buffer, Building 3-7
ZMCS-CMD-command
Note. This manual uses a shortened form for the command names in the text and headings
within Section 5, Commands and Responses (for example, ADD, ALTER, and so on). In
programs, however, you must pass the full name of the command to SSINIT (for example,
ZMCS-CMD-ADD, ZMCS-CMD-ALTER, and so on). For a complete description of all
commands supported by the DSM/TC subsystem, see Section 5, Commands and Responses.