Distributed Name Service (DNS) Management Operations Manual

Ambiguous Names (Error 1034)
Using DNSCOM
6–18 31258 Tandem Computers Incorporated
DNSCOM generates a warning message in response to any request to add an element
to a list if that element is already on the list. Similarly, it generates a warning message
in response to a request to delete an element that is not on the specified list.
Directing Output With the
OUT Command
The OUT command directs all output other than operator prompts to a specified
destination. Usually, the destination is a disk file or printer. To use the OUT
command with another DNSCOM command, the OUT command must be enclosed in
slashes (/) as shown in the following example. In this example, output is directed to a
file called USAFILES
INFO /OUT USAFILES/ DNS-TYPES-FILE AT \NEWYORK
For more information on using the OUT command, see the OUT command description
in Section 7. Additionally, refer to Guardian 90 Operating System User’s Guide, which
discusses IN and OUT options in more detail.
Ambiguous Names
(Error 1034)
Certain cases may arise where a partially qualified name is ambiguous. Such cases
include the following:
For subsystem-object type names, when more than one subsystem defines the type
For subsystem-object names, when more than one manager defines the object
For DNS object names, when more than one system defines the name
Regardless of the kind of name, whenever a name in a command is ambiguous,
DNSCOM responds to the command with an error message identifying the name in
error:
ERROR 1034 - Ambiguous name - name
When this occurs, you can use the INFO command to obtain a display of all possible
interpretations of the erroneous name and then correct the command by qualifying the
name to make it unique. The following example displays a session where an error
1034 is received and shows the steps taken to resolve the error. User input is
displayed in boldface type.