Distributed Name Service (DNS) Management Operations Manual

Glossary
Glossary–12 31258 Tandem Computers Incorporated
subsystem-object type. The owner.subsystem number.subsystem-object type number
grouping always provides a unique identifier for the subsystem-object type that is
independent of the subsystem-object type name assigned by a particular user.
Developers of management applications should always use the owner.subsystem
number.subsystem-object type number grouping to refer internally to the subsystem-
object type; DNS provides a programmatic command for translating the grouping to
the type name, and vice versa. This approach assures portability for management
applications without concern for subsystem-object type name conflicts. Subsystem-
object type number in DNS has the same meaning as object-type number in other DSM
products. See object-type number.
subsystem owner. A value identifying the company that supplies a particular
subsystem. It consists of a name of up to eight characters, blank-filled on the right.
The owner for all subsystems supplied by Tandem is TANDEMb/b/. The subsystem
owner, the subsystem number, and the subsystem version number make up the
subsystem ID that uniquely identifies the subsystem.
Subsystem Programmatic Interface (SPI). A common, message-based interface that can be
used to build and decode messages used for communication between requesters and
servers—for instance, in a management application. It includes procedures to build
and decode specially formatted messages (as described under the SPI message
definition); definition files in TAL, COBOL85, TACL, and C for inclusion in programs,
macros, and routines using the interface procedures; and definition files in DDL for
programmers writing their own subsystems. See also SPI message.
subsystem version number. A 16-bit integer representing the software release version of
a subsystem. The subsystem version number is a field of the subsystem ID. If its
value is null (zero), the subsystem ID refers to any and all versions of the subsystem.
See version number.
support activities. Activities, as defined by the Tandem operations management model,
that provide technical support for operations activities in a production environment.
For DSM, support activities include customizing DSM applications, writing filters for
EMS events, defining a DNS database, and implementing a fully automated
operations-management environment.
system name. The identifier of an individual system, or a node in an EXPAND
network.
Systems Network Architecture (SNA). The IBM-developed architecture that serves as a
means of linking IBM products in a network environment.
TACL. See Tandem Advanced Command Language.
Tandem Advanced Command Language (TACL). The Tandem product that is both the
standard Guardian 90 command interpreter and and a language consisting of
functions, macros, and routines that allows you to build your own commands.
TMF. See Transaction Monitoring Facility.
Transaction Monitoring Facility. The Tandem software product that provides transaction
protection, database consistency, and database recovery.