Distributed Name Service (DNS) Management Operations Manual
DNSCOM Interfaces and Operating Modes
Using DNSCOM
6–10 31258 Tandem Computers Incorporated
This is done by including the AT { \system | name manager } parameter in the
command line. See Section 7 for the command syntax for directing commands to
alternate systems or configurations.
The name manager that executes a command is called the command name manager.
The command name manager can be either the current name manager or another
name manager. (See “Switching DNS Configurations” earlier in this section for more
information about the command name manager.
DNSCOM Interfaces
and Operating Modes
You can run DNSCOM interactively, entering individual commands at a DNSCOM
prompt; or DNSCOM can run by reading commands from a command file. In
addition, you can operate DNSCOM in different DNSCOM modes. Commands
available in each mode vary. Interactive operation, command files, and operating
modes are described below.
Interactive Operation To invoke DNSCOM for interactive use, enter the DNSCOM command at your TACL
command interpreter prompt. The general form of the run command to start a
DNSCOM process is:
DNSCOM [ \
system
|
manager
]
The optional \system parameter allows you to specify a Guardian 90 system name in
case you want DNSCOM to open the name manager process on a system that is not
the default system you currently have in effect in your terminal session. The manager
parameter directly specifies which name manager to open.
After you enter this command, DNSCOM replies with its banner display and its first
command prompt, similar to the following:
DNSCOM - T9635D00 - (15DEC91) SYSTEM
system
COPYRIGHT TANDEM COMPUTERS INCORPORATED 1987, 1991
Current configuration file is
config file
Name manager
manager name
opened
DNSCOM_
The first message after the copyright message informs you which DNS configuration
DNSCOM is using; the second indicates the name manager that was opened. This
second message is issued only if the manager is opened successfully. At this time,
your DNSCOM process is running and is communicating with the name manager
process you specified (or defaulted to), assuming that the name manager process is
running.