Distributed Name Service (DNS) Management Operations Manual

Working With Different DNS Configurations
Using DNSCOM
6–8 31258 Tandem Computers Incorporated
In the following example, DNS attempts to open the process on \REMOTE specified
by DNS-MANAGER PROCESSNAME in \REMOTE.$DATA.MYDNS.DNSCONF:
ALTER DEFINE =_DNS_CONFIG, FILE \REMOTE.$DATA.DNSCONF
DNSCOM
DNSCOM - T9635D00 (15DEC91) SYSTEM \ABC
COPYRIGHT TANDEM COMPUTERS INCORPORATED 1987, 1991
Current Configuration File is \REMOTE.$DATA.MYDNS.DNSCONF
Using Other Configuration
Files With the OPEN
Command
DNS provides the flexibility of using a default configuration file or a configuration file
specified by you in a command line. If you choose to open a configuration with the
OPEN command and supply a specific name manager, DNS opens the configuration
associated to that name manager. This changes the current configuration file and
current name manager. See “Switching DNS Configurations” below for more
information on using different configuration files and name managers.
Switching DNS
Configurations
As introduced in Section 3, the current configuration file is a specified configuration
file or the default configuration file. By default, DNSCOM expects to deal with a
configuration that has $SYSTEM.SYSTEM.DNSCONF as the configuration file, $ZDNS
as the name manager, and $ZDNX as the name exporter.
The current configuration file and current name manager are linked. If you change the
current configuration file, the current name manager also changes to the name
manager associated with that configuration file. The same is true when you change
the current name manager.
To change the current name manager for a single command, you must include the at-
part in the DNSCOM command line.
If an at-part is specified after the object of the command, the command name
manager becomes the name manager specified in that at-part .
If no at-part is specified, the command name manager is the current name
manager.
For the following example commands, assume that the current name manager is
\BOSTON.$PDNS, that the current CMDSYS setting is null, and that DNSCOM is
running on \BOSTON.
In the following command, the name manager becomes \NEWYORK.$PDNS:
ALTER TERM22 AT \NEWYORK, REFERENT \NEWYORK.$LINE6.#LU22
In the following command, the name manager becomes \NEWYORK.$TDNS:
ALTER TERM22 AT \NEWYORK.$TDNS, REFERENT &
\NEWYORK.$LINE6.#LU22
In the following command, the name manager becomes \BOSTON.$TDNS:
ALTER TERM22 AT $TDNS, REFERENT \NEWYORK.$LINE6.#LU22
In the following command, the name manager becomes \BOSTON.$PDNS:
ALTER TERM22, REFERENT \NEWYORK.$LINE6.#LU22