DSM/Tape Catalog Management Programming Manual

DSM/Tape Catalog Management Programming Manual—520481-003
3-1
3
SPI Programming Considerations
The Subsystem Programmatic Interface (SPI) is used to build and decode commands
and responses needed by the DSM/TC subsystem to communicate with management
applications. The messages containing the commands and responses are transported
by an application that communicates with the MEDIASRV process—not by SPI.
Command numbers and object-type numbers, denoted in programs by names from
HP’s definition files, are used to represent commands and object types. For example,
the ALTER command is denoted by the command number ZMCS-CMD-ALTER, and the
object type for audit trails is denoted by the object-type number ZMCS-OBJ-
DISKFILE.
Tokens are also denoted with characteristic names to represent parameters, results,
and event-message elements. Tokens take on values, in most cases numbers, file
names, and so on. For more information on tokens, see the SPI Programming Manual.
Definition Files
The tokens, values, and other data items necessary to use SPI to manage a DSM/TC
subsystem are contained in files with names of the form:
where xxxx represents a specific development language:
Topic Page
Definition Files
3-1
Syntax Elements 3-2
The Command Buffer, Building 3-7
A Command in Progress, Discontinuing 3-8
Response Buffers, Receiving and Decoding 3-8
Error Handling 3-9
Security 3-9
ZSPIxxxx
Subsystem Programmatic Interface definitions
ZMCSxxxx
Media catalog subsystem definitions
C
C
COB
COBOL
DDL
Data Definition Language, from which the other files are derived
PAS
Pascal
TACL
HP Tandem Advanced Command Language
TAL
Transaction Application Language