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

Glossary
SPI Programming Manual—427506-006
Glossary-7
object type
typically has a name and a type known to the controlling subsystem. In DDL, an item in
a dictionary. DDL assigns each object a unique object number for identification.
object type. A category of objects to which a specific object belongs: for example, a specific
disk file might have the object type FILE and a specific terminal the object type SU. A
subsystem identifies a set of object types for the objects it manages. The operator
interface to the subsystem might have keywords to identify the types. Correspondingly,
the programmatic interface would have object-type numbers suitable for passing to the
SPI SSINIT procedure. In DDL, one of the six types of dictionary objects: records,
DEFs, constants, token types, token codes, and token maps.
object-name template. An object name, provided in a command, which the subsystem
compares with the names of its objects to identify those to which the command should
be applied. Some subsystems allow wild-card characters in object-name templates.
object-name token. A parameter or response token that identifies, by name, a particular
object of a given object type. An object-name token is a kind of object-selector token.
See object-selector token
.
object-selector token. A token that identifies one or more specific objects to operate on, of
the object type given in the command. Typically, the value of such a token is either
some form of object name or an object number. An object-name token is a kind of
object-selector token. See object-name token
.
object-type number. A number that represents an object type managed by a subsystem.
Each subsystem with a token-oriented programmatic interface can have its own set of
object-type numbers, which are represented in DDL by constants and in programs by
TAL literals or defines, COBOL level-01 variables, or TACL text variables. (In some
cases, object-type numbers are shared by several subsystems.) The object-type
number is a header token in commands and responses. See object type
.
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 eight-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 further
information, see the
EMS Manual .