Distributed Name Service (DNS) Management Operations Manual

Ambiguous Names (Error 1034)
Using DNSCOM
31258 Tandem Computers Incorporated 6–19
DNSCOM_ ALTER LINE4,REFERENT \A.$SPARE1
ERROR 1034 - Ambiguous Name - LINE4
DNSCOM_ INFO LINE4
LINE4 ON \A : ALIAS
COPIED
DOMAIN ALL-NCNS ON \A
OWNER XYZCO
REFERENT \A.$LINE4 : SSOBJECT (LINE IN SNAX)
TYPE COMM-LINE
TYPENUM 1
LINE4 ON \C : ALIAS
COPIED
DOMAIN ALL-NCNS ON \C
OWNER XYZCO
REFERENT \C.$LINE1 : SSOBJECT (LINE IN SNAX)
TYPE COMM-LINE
TYPENUM 1
DNSCOM_ALTER LINE4 ON \A, REFERENT $SPARE
ALIAS LINE4 on \A Altered
DNSCOM_
An alternative approach for this example makes use of the fact that the default system,
as established by the NAMESYS command, affects the DNSCOM treatment of
ambiguous DNS object names.
Originally, the TACL default system name for NAMESYS is passed to DNSCOM in its
startup message. If no system name is passed, the system where the current name
manager is running is assumed. Then, in cases where a name is ambiguous, the
duplicate names are examined. If one of the names is defined on the NAMESYS
system, that name is selected. If the ambiguous name is not defined on the NAMESYS
system, an error is reported.
The alternative approach could be:
DNSCOM_NAMESYS \A
DNSCOM_ALTER LINE4, REFERENT \NCN.$SPARE
ALIAS LINE4 Altered
DNSCOM_
The setting of NAMESYS also affects the format of DNSCOM output, in the following
ways:
DNS object names defined for (or by) the NAMESYS command are displayed
without the ON \ system part. For example, if NAMESYS is set to \A, the name
LINE4 ON \A is displayed as simply LINE4.
Subsystem-object and manager names that are some form of Guardian 90 file
names on the NAMESYS system are displayed in local format. For example, if
NAMESYS is set to \A, the name TERM22 AT \A.$PM is displayed as TERM22
UNDER $PM.