Distributed Name Service (DNS) Management Operations Manual

How to Define DNS Names
Building and Modifying the DNS Database
31258 Tandem Computers Incorporated 4–17
See Figure 4-8 for the following explanation. Before defining the composite object(s)
displayed in Figure 4-8, the system manager must have defined a composite type
called ATM and specified that all associated ATMs must consist of a Pathway
terminal, a SNAX/XF LU, and an HLS thread. These components are identified in the
definition of the composite type by the subsystem-object type names TERM IN
PATHWAY, LU IN SNAX, and SESSION IN SNAX/HLS, respectively.
Figure 4-8. Sample Composite Objects and Types
PATHWAY SNAX SNAXHLS
Components of the Composite
\B.$PM \B.ZNET \B.$HLS9
TERM-006
(Terminal)
$LINE4.#LU3
(Logical Unit)
#LINE4.LU3
(Session)
Composite Object
Composite NameATM-44
S8121-007
Once the composite type is defined, you can define any number of ATMs (composite
objects) that are instances of that composite type. In the example in Figure 4-8, the
commands for defining the composite type ATM are shown below. User input is
displayed in boldface type.
DNSCOM_ASSUME COMPOSITETYPE
DNSCOM_SET OWNER EZZCORP
DNSCOM_SET TYPENUM 1
DNSCOM_SET COMPONENTS TERM IN PATHWAY
DNSCOM_SET COMPONENTS LU IN SNAX
DNSCOM_SET COMPONENTS THREAD IN SNAXHLS
DNSCOM_SET DOMAIN BANK33
DNSCOM_ADD ATM
DNSCOM_