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

Glossary
Safeguard Management Programming Manual—422086-028
Glossary-14
sensitive command
sensitive command. A command that can be issued only by a restricted set of users, such
as the super group, because the subsystem restricts access to the command. For data
communications subsystems, the sensitive commands are those that can change the
state or configuration of objects. So for these subsystems, the sensitive commands are
also action commands. See also nonsensitive command.
server version. The software release version of the server to which a requester using SPI
(such as a management application) is sending a command. If the server version is
older than the maximum field version in a request, the server rejects the request. SPI
puts the maximum field version into the command buffer; the server puts its own
version into each response buffer. See maximum field version.
session. The period during which two entities can exchange data. For a management
application, the period during which an application can issue commands to a
subsystem. For a command interpreter, the period during which a user can issue
commands to the command interpreter.
short read. An operation in which the application reads fewer bytes than are available in a
message. For SPI, the term implies that the number of bytes requested by the
application is less than the number of used bytes in the SPI buffer or that the
application furnished a buffer too small to contain the response data produced by the
subsystem.
simple token. A token consisting of a token code and a value that is either a single
elementary field, such as an integer or a character string, or a fixed (nonextensible)
structure. See also extensible structured token.
snapshot file. A file containing all response data for a command. It is used to ensure a
consistent response in cases where data—for instance, statistics—might change
between one reply message and the next. Subsystems for NonStop servers do not use
snapshot files, but subsystems you write can do so.
special operation. An operation, such as a control operation or an operation that gets
information from the buffer (rather than the header), performed by the SSGET or the
SSPUT procedure. Special operations include obtaining the length or number of
occurrences of a token, changing the current position, clearing the last-error
information, or deleting a token from the buffer. A program directs SSGET or SSPUT to
perform a special operation by passing to the procedure one of a set of special SPI
token codes. These special token codes do not represent tokens in the buffer but
simply direct SSGET or SSPUT to perform the indicated operations.
SPI. Abbreviation for Subsystem Programmatic Interface
.
SPI buffer. A sequence of memory locations used for a message produced by the SPI
procedures.
SPI control code. A special token code, passed to one of the SPI procedures, that directs
SPI to perform a specified action on the buffer (such as a positioning operation). The
ZSPI-TKN-DATAFLUSH, ZSPI-TKN-DELETE, and ZSPI-TKN-CLEARERR token