Distributed Name Service (DNS) Management Operations Manual

Initializing and Starting DNS Configurations
DNS Management and Operations
31258 Tandem Computers Incorporated 3–5
Figure 3-1. Using DNSCOM to Initialize DNS
54> DNSCOM
DNSCOM - T9635D00 - (15DEC91) SYSTEM \ANKARA
COPYRIGHT TANDEM COMPUTERS INCORPORATED 1987, 1991
DNSCOM_ SELECT DNSCONF $ENGIN2.DNS.CONFIG
WARNING 1063 - DNS Configuration has not been Initialized -
Configuration File is $ENGIN2.DNS.CONFIG
DNSCOM_ SELECT DEFINITION ON
DNSCOM_ VOLUME $ENGIN2.DNS
DNSCOM_ RESET DNSFILE *
DNSCOM_ ASSUME DNS
Default Name Type is DNS
DNSCOM_ SET MAXDOMAINS 50
DNSCOM_ SET MAXMANAGERS 100
DNSCOM_ SET MAXNAMES 2000
DNSCOM_ SET MAXTYPES 200
DNSCOM_ SET SECURITY "AAOO"
DNSCOM_ SET DNSOWNER DNS.MGR
DNSCOM_ ASSUME DNSPROCESS
Default Name Type is DNSPROCESS
DNSCOM_ SET DNS-MANAGER PRIORITY 150
DNSCOM_ SET DNS-MANAGER CPUS (4,5)
DNSCOM_ SET DNS-MANAGER SWAPVOL $DATA2
DNSCOM_ SET DNS-MANAGER PROCESSNAME $RDNS
DNSCOM_ SET DNS-EXPORTER PROCESSNAME $RDNX
DNSCOM_ SET DNS-EXPORTER PRIORITY 120
DNSCOM_ SET DNS-EXPORTER CPUS (5,4)
DNSCOM_ SET DNS-EXPORTER SWAPVOL $DATA2
DNSCOM_ INITIALIZE DNS
DNS Configuration File \ANKARA.$ENGIN2.DNS.CONFIG Initialized
DNSCOM_ START DNS
Name Manager \ANKARA.$RDNS Started
Name Manager \ANKARA.$RDNX Opened
DNSCOM_ OBEYVOL $ISV.ZDNS
DNSCOM_ OBEY LOAD
11
9
8
7
6
5
4
3
2
10
1
032
• • •
• • •
6. The next step involves commands that assign attribute values to the name
manager and exporter processes. These commands require the keyword
DNSPROCESS as part of each entry. If you would like to eliminate the need for
repeatedly entering this keyword, enter the ASSUME command and specify
DNSPROCESS as the default object.