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

Glossary
Safeguard Management Programming Manual—422086-028
Glossary-11
object
made no explicit assignment to that field after calling the SSNULL procedure to
initialize the structure.
object. In SPI, an entity subject to independent reference and control by a subsystem; for
example, the disk file $DATA or the data communications line $X2502. An object
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-name template. A name that stands for more than one object. The name includes
wild-card characters such as * and ?. TMF and some data communications
subsystems accept object names of this form.
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. The 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-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, C #define directives, COBOL level-01 variables, or TACL text
variables. (In some cases, as with the data communications subsystems, object-type
numbers are shared by several subsystems.) The object-type number is a header
token in commands and responses. See object type.
owner. For 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. For 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.
For a token or other definition, the subsystem that provided the definition. For 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