Safeguard Management Programming Manual (G06.29+, H06.08+, J06.03+)

Elements of SPI Messages

Safeguard Management Programming Manual—422086-028

4-7

Other Tokens

The Safeguard subsystem uses other tokens as command parameters, results in

responses, and elements of event messages and error lists.

Simple Tokens

Simple tokens—tokens whose values are single fields or fixed structures—are

identified by token codes. The token codes for the simple tokens used by the

Safeguard subsystem are represented by symbolic names in the form ZSFG-TKN-

name, where name identifies the token code. For example, the token code ZSFG-TKN-

PASSWORD identifies a simple token that contains a password.

Token Types

The token types used by the Safeguard subsystem are represented by symbolic

names in the form ZSPI-TYP-name, where name identifies the token type. For

example, the token type ZSPI-TYP-CHAR8 represents a string of eight ASCII

characters. The Safeguard subsystem does not define any private token types. That is,

no token types have names of the form ZSFG-TYP-name.

Throughout this manual, when a simple token is described, its token type is given.

Predefined Value Names

The predefined values used by the Safeguard subsystem are represented by symbolic

names in the form ZSFG-VAL-name, where name identifies the predefined value. For

example, the predefined value ZSFG-VAL-BUFLEN represents the recommended

buffer length.

Extensible Structured Tokens

Extensible structured tokens—tokens whose values are extensible structures—are

identified by token maps. The token maps for the extensible structured tokens used by

the Safeguard subsystem are represented by symbolic names in the form ZSFG-MAP-

name, where name identifies the token map. For example, the token map ZSFG-MAP-

ACCESS identifies an extensible structured token that contains an access control list

entry.

The ADD and ALTER commands contain extensible structured tokens. The responses

to the Safeguard commands INFO and STATUS can also contain extensible structured

tokens.

Extensible structured tokens do not appear in any event message or error list issued

by the Safeguard subsystem. Throughout this manual, when an extensible structured

token is described, its DDL definition, including the definitions and types of all fields, is

also given.