SPI Common Extensions Manual
Glossary
SPI Common Extensions Manual—427508-001
Glossary-8
owner
owner. In the case of a disk file, the user or program that created the file, or a user or
program to whom the creator has given the file with the FUP GIVE command. In the
case of a process, the user or program that created the process or, if the PROGID
option was specified in the FUP SECURE command for the code file, the user or
program that owns the code file. In the case of a token or other definition, the
subsystem that provided the definition. In the case of a subsystem, the company or
organization that provides the subsystem, or the 8-character string identifying that
company.
parameter token. In control and inquiry, a token that provides parameter information for a
command. Most tokens in the SPI message for a command are parameter tokens.
Depending on the subsystem, they can include attribute tokens, object-selector or
object-name tokens, and subsystem-control tokens. Compare with syntax token. In
event management, a token representing a parameter passed by an application to an
event-message filter. Such tokens are kept in a parameter buffer. For more information,
see the
EMS Manual
.
pass-through error. An error originally reported by one subsystem or system component
but included in a response record produced by another subsystem. Typically, a
subsystem passes an error from a second subsystem only if that error prevented the
first subsystem from performing a command successfully. A pass-through error is
expressed as an error list that is nested within another error list. See nested error list.
position descriptor. A four-word block of information that indicates a position within an SPI
buffer. A position descriptor is used as a parameter to some of the special operations
for SSGET and SSPUT.
positioning operation. An operation that gets, sets, or changes the current position in an
SPI buffer, or that creates in the buffer a construct (such as a list) that provides a
scope for retrieval of data.
predefined value. A commonly used value that is given a symbolic name in an SPI
definition file.
private token type. A token type defined by and specific to a particular subsystem. A
private token type is built from standard SPI token data types although it might have
additional semantic connotations for the subsystem. For example, a subsystem might
define a token type that looks to SPI like an integer but that implies to the subsystem a
range of values smaller than an integer type allows. See token type.
procedural interface. A means for obtaining services through procedure calls; also, the set
of procedures through which services are obtained. For instance, an application has a
procedural interface to SPI. That interface consists of the procedures SSINIT,
SSNULL, SSPUT, SSPUTTKN, SSGET, SSGETTKN, SSMOVE, and SSMOVETKN.
programmatic command. A command issued by a program rather than by a human
operator.