SPI Programming Manual (G06.24+, H06.03+, J06.03+)

Glossary
SPI Programming Manual—427506-006
Glossary-10
sensitive command
the response record contain ZSPI-TKN-MORE-DATA, indicating that the response
record is incomplete.
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
extended SPI subsystems, the sensitive commands are those that can change the
state or configuration of objects; for these subsystems, the sensitive commands are
also action commands. Compare with nonsensitive command
.
server. An SPI server. A subsystem process that accepts SPI commands from
management applications.
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
.
short read. An operation in which the application reads fewer bytes than are available in a
message. In the context of SPI, the term implies that the number of bytes requested by
the application is fewer 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. Compare with extensible structured token
.
snapshot file. A file used by context-sensitive servers to record 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. NonStop
Kernel subsystems provided by HP 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. Subsystem Programmatic Interface.
SPI buffer. A block of memory where SPI procedures create and manipulate SPI
messages.
SPI definitions. See SPI standard definitions.