DSM/Tape Catalog Management Programming Manual

SPI Programming Considerations

DSM/Tape Catalog Management Programming Manual—520481-003

3-3

Object Types and Object Names

Objects within SPI are entities subject to independent reference and control by a

subsystem. An object typically has a name (object name) and a type (object type). An

object type is a category of objects to which a specific object belongs. The DSM/TC

subsystem has its own set of object types. (They are 16-bit integers.)

The ZSPI-TKN-OBJECT-TYPE header token is included in all commands and

responses, and it contains the type of object operated on by the command.

In the DSM/TC subsystem, object types are represented by names having the form:

object

identifies the object type.

Tokens

A token is made up of two parts: an identifying code (a token code or a token map,

represented in programs by an appropriate name) and a value. For control and inquiry,

a token normally represents a parameter to a command, an item of information in a

response, or control information for SPI (or the subsystem).

Simple Tokens

A simple token is made up of a token code and a value of the type indicated in the

token code. Token codes that represent simple tokens are 32-bit integers. They have

names of the form:

subsys

is a 4-character abbreviation for a subsystem. For NonStop Kernel subsystems,

the first character is always Z.

name

identifies the token code.

For a table of all the token codes defined by the DSM/TC subsystem, see Section 4,

Common Definitions.

ZMCS-OBJ-object

Note. This manual uses a shortened form for the object-type names in the text and headings

(for example, POOL, CONSOLE, and so on). In programs, however, you must pass the full

name of the command to SSINIT (for example, ZMCS-OBJ-POOL, ZMCS-OBJ-CONSOLE,

and so on). For a complete description of all object-types supported by the DSM/TC

subsystem, see Section 5, Commands and Responses

subsys-TKN-name