Conference azur::mcc

    I assume you are talking about node4 entities.
    
    During DEREGISTER, the DNA4 AM (for node4) DEREGISTER entry point is
    called. In DECmcc V1.1, this entry point tries to "talk" to and verify
    that the node4 is out there before it deregisters what was done during
    registration. In your case, since MYNODE 15.2 is changed to 9.2, 15.2
    is no longer there (but it is still in DNS if you are on VMS). So it
    returns a message saying the node is not accessible.
    
    As I understand, this problem in DNA4 AM will be fixed in V1.2, so that
    you can deregister an unreachable (for any reason) node4 by fullname.
    Basically DNA4 AM does not check reachability for DEREGISTER in V1.2.
    
    For now, the only way to deregister unreachable or non-existent node4
    which was registered before is to go into DNS$CONTROL and manually
    delete it. There are three things you have to delete for node4:
    (take your case MYNODE 15.2 for example, assuming fullname is .MYNODE)
                                                                  
    1.  node4 synonym link                                                
    
    	$ mcr dns$control
        DNS> show link .dna_nodesynonym.mynode attribute DNS$LinkTarget
    		
    		.... verify that the link target is .mynode
    
        DNS> delete link .dna_nodesynonym.mynode
    
    2.  node4 backtranslation
    
        Since the area of old MYNODE is 15, it is hex 000F.
    
    	You have to calculate the address. For 15.2, it is
    
    	    15 * 1024 + 2  =  15362 decimal  or  3C02 hex
    
    	Now reverse 3C02 hex to 023C and append AA000400 hex you get
    
    	    %XAA000400023C
    
        $ mcr dns$control
        DNS> show link .dna_backtranslation.%X49.%X000F.%XAA000400023C
    		attribute DNS$LinkTarget
    
    		.... verify that the link target is .mynode
    
        DNS> delete link .dna_backtranslation.%X49.%X000F.%XAA000400023C
    
	3.  fullname
    
        $ mcr dns$control
    	DNS> show object .MYNODE
    
    		.... verify that the object .mynode is there
    
        DNS> delete object .MYNODE
    

    
    This problem has been fixed for V1.2.
    
    Yep, we did check to make sure that a node4 was really out there and
    really okay before we'd Deregister it.  Not very smart, that.
    
    Your Deregister in V1.1 would still work if you had a node out there
    with the address 15.2.  You may think it is easier to change a node's
    address for a few minutes to do the Deregister than it is to use
    DNS$CONTROL.  We don't do anything with the node4 other than ask it if
    it is out there.  If anyone answers, the Deregister will continue
    happily.
    
    We might have noticed this earlier except that hardware, names, and
    addresses are pretty dear around here and we seldom actually throw
    anything away!  ;-)
    
    Sorry about that.
    
    -Jim Carey
    

    Many months ago, I completely reorganized my namespace.  I had to write
    a command procedure to delete every entry in the namespace since V1.1
    of DNS did not allow the use of a wild card in the DELETE command.  As
    a result of this episode, I became quite familiar with the directories,
    objects, and links in the namespace.
    
    I'm told this is fixed in DNS V2.  
    
    .1 was nicely documented, and .2 let me know that this was
    not something I will have to live with forever.
    
    ONE ADDITIONAL QUESTION:
       What will actually be supported in V1.2 with regard to entity
    registration and deregistration?  I must have the capability to
    register and deregister ANY entity whether I can reach it or not.  This
    is a MUST for my customer.
    
    Thanks,                   
    Dan

    re: .3
    
    In V1.2, there will be quite a few changes with regard to entity
    registration and deregistration. And that is what we called partial
    registration - the capability to register any entity whether it is
    reachable or not for whatever reason.
    
    However, we will not give all the details here for partial registration
    yet. The reason being that this functionality has gone through a few changes
    since. We will post a note here in the future (a few weeks) when
    everything is nailed down concretely to describe all the details and
    changes that affect registration/deregistration.
    
    In short, in V1.2, you will be able to (take node4 for example):
    
     -  register it completely just like what can be done with V1.1
    
     -  just register the fullname of it
    
     -  deregister any entity, whether it was completely registered or
        partially registered.
    
     -  and more (details to be posted in the future)
    
    The good thing about this is you can register an entity even though it
    is not reachable (for whatever reason) or it is still not physically
    there (planning stage) and put it on the Iconic Map and SEE it on the
    map.
    
    Ed