Distributed Name Service (DNS) Management Operations Manual

How to Define DNS Names
Building and Modifying the DNS Database
4–14 31258 Tandem Computers Incorporated
Managers usually manage only one subsystem. For example, a Pathmon process
manages Pathway, and $SSCP manages SNAX/XF.
The example below shows how to add a subsystem manager. User input is displayed
in boldface type; system output is displayed in regular type.
DNSCOM_SET SSMANAGER SUBSYSTEMS SNAX
DNSCOM_ADD SSMANAGER $SSCP
SSMANAGER \BLUE.SSCP Added
DNSCOM_
Examples of subsystem manager name are the following Guardian 90 process or disk
file names:
\NY.$PM
\SFO.$HLS9
\LA.$SYSTEM.SYSTEM.FUP
Manager names can be expanded using the specifications from the NAMESYS and
NAMEVOL basic commands, discussed in Section 7.
Defining Composite Type
Names
As defined in Section 2, a composite is an object controlled by two or more subsystems
and cannot be defined until you define its associated composite type. The composite
type definition specifies the subsystem-object types that must be included in every
instance of this type (the composite objects).
Essentially, the composite type definition provides a template for defining any
instance of that composite type; it establishes the required components for composite
objects.
When you add a composite type definition, you specify the following:
The composite type name
A list of subsystem-object types (SSTYPEs).
An owner (usually your company name).
A type number. The type number must be unique among type numbers defined
by the owner.
Finally, you can specify the default domain for composites of this type.
Figure 4-6 displays the name dependencies and relationships of composite type name
definitions.