Distributed Name Service (DNS) Management Operations Manual

Working With Different DNS Configurations
Using DNSCOM
31258 Tandem Computers Incorporated 6–9
To avoid having to include the name of the name manager each time that DNSCOM is
run, as well as to handle the case where the desired configuration is not in the running
state, DNSCOM looks for DEFINE =_DNS_CONFIG. If this define mapping statement
is present, the default configuration for that execution of DNSCOM becomes the one
whose configuration file is mapped by =_DNS_CONFIG. (DNSCOM reads the
configuration file to learn the names for the name manager and name exporter
processes.)
If you usually use the same DNS configuration, you may want to place the following
line in your TACLCSTM file so you automatically receive the same DNS configuration
by default. This default can be overridden by including the name of a name manager
on the command line.
ADD DEFINE =_DNS_CONFIG, FILE config file
A system manager can similarly change the default DNS configuration for all users on
a system by defining =_DNS_CONFIG in the TACLLOCL file. For more information
on TACL files, refer to the Guardian 90 Operating System User's Guide and the Tandem
Advanced Command Language (TACL) Reference Manual, Volumes 1 and 2.
In addition, the DNSCOM OPEN and SELECT commands let you switch between
DNS configurations. The following examples show switching the configuration with
the OPEN and SELECT commands. Options available with these commands are
included in Section 7, along with more examples.
In the OPEN command example below, the configuration is switched to the one
associated with $RDNS, a running DNS name manager process.
OPEN $RDNS
To switch to a configuration that is currently in a stopped state, use the SELECT
command. The following command switches to the current configuration file to
$ENGIN2.DNS.CONFIG:
SELECT DNSCONF $ENGIN2.DNS.CONFIG
Using Configuration Files
From Remote Systems
It is not necessary that your current name manager and DNSCOM be running on the
same system. It is also not necessary that your current name manager execute
DNSCOM commands. The following commands allow you to designate a node other
than the one where your current name manager is running or to designate a
configuration other than the current one for processing a command.
ALTER
COPY
DELETE
INFO
LIST
RESTORE
STATUS
STOP