Distributed Name Service (DNS) Management Programming Manual

Event-Message Descriptions
Event Messages
46958 Tandem Computers Incorporated 6–45
Recommended Action
Check the file or device named in the message. Recovery action is dependent on
which of the problems listed above has occurred:
The name’s type (ALIASTYPE or COMPOSITETYPE) is not defined to the
importing system.
Suppose the following event message is generated at \B:
\B.$ZDNS: ERROR *0022* Replication of LINE46 from \A Failed
DNSTYPE: ALIASTYPE
TYPENAME: LINE
The problem may be resolved as follows:
13> DNSCOM \A
DNSCOM - T9635D00 - (15OCT89) SYSTEM \B
COPYRIGHT TANDEM COMPUTERS INCORPORATED 1987, 1989
Current Configuration File is \B.$SYSTEM.SYSTEM.DNSCONF
name manager \A.$ZDNS Opened
DNSCOM_SELECT DEFINITION ON
DNSCOM_ASSUME ALIASTYPE
Default Name Type is ALIASTYPE
DNSCOM_SET LIKE LINE
DNSCOM_OPEN \B
name manager \B.$ZDNS Opened
DNSCOM_ADD LINE
ALIASTYPE LINE Added
DNSCOM_OPEN \A
name manager \A.$ZDNS Opened
DNSCOM_ENABLE EXPORT \B
The name’s type (ALIASTYPE or COMPOSITETYPE) has incompatible definitions
on the exporting and importing systems.
One of the systems should perform a logical reload. (See “Logical Database
Reload,” earlier in this section.)
The SSTYPE of the name’s referent or one of its components is not defined to the
importing system.
Recovery is the same as for ALIASTYPE or COMPOSITETYPE.
The SSTYPE of the name’s referent or one of its components has incompatible
definitions on the exporting and importing systems.
One of the systems should perform a logical reload.