[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

3108.0. "De/Register problems under MCC and DNS On V1.1 MCC " by RDGENG::GARDEN () Mon Jun 01 1992 10:38

I hope someone can answer this question!! I am running MCC V1.1.

I have deregistered an Router ENGR22 using DECNET_DNS_REGISTER before doing 
the same under MCC.

I have tried to register this node under MCC and this is the error that I get
back:-


MCC> register node4 .reo.engr22 synonym engr22

Node4 MCCULT_NS:.reo.engr22
AT  1-JUN-1992 12:15:14
                           

The requested operation cannot be completed
            MCC Unhandled Service Reply = Registration Failed: Duplicate Synonym
MCC> register node4 engr22 synonym engr22

Node4 engr22
AT  1-JUN-1992 12:15:33

The requested operation cannot be completed
                      MCC Routine Error = %MCC-E-INV_DNSIDENT, specified
                                          identifier attribute is not valid for
                                          instance lookup
MCC>

MC DNS$CONTROL

DNS> show obj .engr22 kn attr
 Attribute (Single) ___ DNA$NodeSynonym
 Attribute (Set) ______ DNA$Towers
 Attribute (Set) ______ DNS$ACS
 Attribute (Single) ___ DNS$Class
 Attribute (Single) ___ DNS$ClassVersion
 Attribute (Single) ___ DNS$UID
 Attribute (Single) ___ DNS$UTS

DNS> 
From above it can be seen that the Object .ENGR22 is missing :-

Attribute (Set) ______ MCC_Class
 Attribute (Set) ______ MCC_DOMAIN_LIST
 Attribute (Single) ___ MCC_REGISTRATION_STATE
 Attribute (Single) ___ MCC_UID
 Attribute (Set) ______ MCC_Version

DNS>

I have been told that it looks like ENGR22 is still registered in the MIR. Could
somebody tell me how to deregister the node4 from MCC.

Thanks
Ian Garden
T.RTitleUserPersonal
Name
DateLines
3108.1TOOK::KWAKMon Jun 01 1992 11:0329
    
    RE: .0
    
    I guess that when you deregister ENGR22 using the program 
    DECNET_DNS_REGISTER, the program deleted only the DNS object.
    
    When you register node4 using MCC V1.1, MCC does the following:
    	- creates a DNS object  (e.g. .reo.engr22 )
        - creates a node synonym softlink (e.g. .DNA_NodeSynonym.engr22)
    	  pointing to the DNS object (this info is stored in DNS$LinkTarget
          attribute of the softlink entry)
        - and creates address backtranslation link (DNS softlink) (e.g.
    	  .DNA_BackTranslation.%x49.%x002c.%x??????) pointing to the DNS
    	  object.
    
    If your tool (DECNET_DNS_REGISTER) removes the DNS object only, you
    need to delete the two softlinks before you try to use the node4.
    
    For now, find the old registered name of the "ENGR22", and registered
    the node4 using MCC V1.1, and de-register it using MCC (when you 
    MCC-deregister the node4, MCC will delete two softlinks and the DNS
    object).
    
    If you do not know the old registered name, try the following
    DNS$CONTROL command:
       $ mcr dns$control
       DNS> sho link .dna_nodesynonym.engr22 attr DNS$LinkTarget