Distributed Name Service (DNS) Management Operations Manual

Glossary
31258 Tandem Computers Incorporated Glossary–11
Subsystem Control Facility (SCF). An interactive interface for configuring, controlling,
and collecting information from Tandem data communications subsystems.
Subsystem Control Point (SCP). The management process for all Tandem data-
communications subsystems. There can be several instances of this process.
Applications using SPI send all commands for data-communications subsystems to an
instance of this process, which in turn sends them on to the manager processes of the
target subsystems. The Subsystem Control Point also processes a few commands
itself. It provides security features, version compatibility, support for tracing, and
support for applications implemented as NonStop process pairs. See manager
process.
subsystem environment. The Tandem subsystems and customer applications that use an
SPI management interface to communicate with management applications and with
the DSM management services. See also operations environment.
subsystem ID (SSID). A data structure that uniquely identifies a subsystem (including
whether it is a Tandem subsystem or a subsystem you write). It consists of the name
of the owner of the subsystem (the company that provides it), a subsystem number
that denotes the subsystem within the scope of its owner, and a subsystem version
number. The subsystem ID is an argument to most of the SPI procedures.
subsystem name. The name that denotes a particular subsystem. An externalization of
the subsystem ID. Examples are PATHWAY, TMF, and AM3270.
subsystem number. An integer that identifies a subsystem within the context of its
owner. The subsystem owner, the subsystem number, and the subsystem version
number make up the subsystem ID that uniquely identifies a subsystem.
subsystem object. An object controlled by a Tandem-supplied, third-party, or user-
written subsystem.
subsystem-object name. The name used by a Tandem-supplied, user-written, or third
party subsystem, or by the Guardian 90 operating system, to refer to an object, for
instance, the PATHWAY name of a terminal or a SNAX name for a logical unit. For
example: TERM-006 UNDER \TS.$PM, $LINE4.#LU3 UNDER \NY.$SSCP, or
\CENTER.$BOOKS.PLANS.OUTLINE.
subsystem-object type. The classification of an object, as defined by a subsystem. All
members of an object type have the same attributes and management semantics. An
object can have a different object type in every subsystem that knows about the object.
In DNS, the subsystem-object type is a particular kind of attribute associated with a
subsystem-object name. It is a template that simplifies the definition of a subsystem-
object name by specifying the kind of object to which the name refers; it is an
externalization of the OWNER/SUBSYSTEM NUMBER/SUBSYSTEM-TYPE
NUMBER construct.
subsystem-object type name. In DNS, the name that identifies a subsystem-object type.
For example, LU, LU IN SNAX, or LINE IN AM6520.
subsystem-object type number. In DNS, an integer used to identify a subsystem-object
type, passed to the SSINIT procedure in commands that apply to an instances of this