Conference azur::mcc

Brute force ... use the DNS$Control program and issue a:

DNS> DELETE LINK DNA$NODESYNONYM.nodename

That will remove the synonym softlink from DNS.  You may find that that you 
also have a DNA$BackTranslation softlink.  They are trickier to get rid of.

Again the DNS command is:

DNS> DELETE LINK DNA$BackTranslation.%xIDPvalue.%XAreaNumber.%xNodeID

e.g.

dns> DELETE LINK DNA$BackTranslation.%X5311111111101234.%x0004.%xAA0004009E10

Claud's cookbook for generating the correct backtranslation softlink:

Look at the child directory of the DNA$Backtranslation to find the correct
syntax for the IDPvalue and add the '%x'.   To find the child directory:
DNS> SHOW DIRECTORY DNA$BACKTRANSLATION KNOWN CHILDREN
Normally, there is only one of these, so use it.  Do not use the MCC_IDP logical
it is not padded completely.

The AreaNumber is a 4 digit area number in HEX e.g. area 60 is therefore %x003c.  

The NodeId is your node id in HEX with the DECnet HiOrd value '%xAA000400' prepended. 
The byte order of the node address is swapped.  e.g. node 60.158 is 1024X60+158 or 
61598 in decimal or F09E in HEX, swapping the bytes = 9EF0 and final address is 
%xAA0004009EF0.   Piece of cake right!

Hope that helps, Claudia  

    Claudia
    
    Thanks for your reply.
    DNS reckons that the DNA$NODESYNONYM.nodename link does not exist.
    Indeed, they don't exist for the nodes that I have successfully
    registered (those nodes HAVE been registered since DNS> SHOW OBJECT
    commands show them and I can successfully manage them from DECmcc).
    What am I missing here?
    
    Gary

>   I attempted to register a phase 4 node but didn't put the . before the
>    entity name. This failed of course but now when I attempt to register
>    the node a "Duplicate Synonym" error is produced. I can register other
>    nodes ok. How do I clear this?

Getting the "Duplicate Synonym" error means that there is already
an entity registered with that synonym.  In the following example
the second command would return the "Duplicate Synonym" error.

MCC>REGISTER NODE4 .DNA_NODE.FOO SYNONYM FOO

MCC>REGISTER NODE4 .FOO SYNONYM FOO

To determine what fullname the synonym was registered with
do a directory with the synonym identifier.

MCC>DIR NODE4 FOO

What happens if you try to deregister the node using the
synonym.  For example:

MCC>DEREGISTER NODE4 FOO

Registering a NODE4 without the dot results in an error being
returned, nothing is written to the namespace.  On a successful 
registration the fullname, the synonym and the address are stored.
If the namespace is corrupt then we need to understand how
it got corrupted.  If the namespace is corrupt do you remember
the sequence of events that got it in this state and is it
reproducible??  

The synonyms are stored as links in .DNA_NODESYNONYM the address's
are stored as links in DNA_BACKTRANSLATION.
I noticed in your reply .2 that you looked in DNA$NODESYNONYM.nodename.
The structure of the MCC instance repository changed between 1.0 IFT 
and 1.0 EFT from directories with $ to directories with _
I belive the 1.0 EFT release notes stated that the databases
were incompatible and that the data must be unloaded and reloaded.
If this is the case and you have a node register with 1.0 IFT and
you are trying to register it again with 1.0 EFT or 1.0 SSB or 1.1 FT or
1.1 SSB it is not going to work!

What version of MCC are you using?

If the $ in .2 was a typo could you answer the following 
questions.
What namespace is MCC using?  You can determine this by
doing a directory against a node4 that was registered, the
namespace name is part of the registered name displayed.

What namespace are you using DNS$CONTROL against?
You can determine this by invoking dns$control and doing a
DNS> show nameserver

Pat

Sorry about the $ ... it should be underscore, DNA_xxxx  (Too much old information
in my absent minded mind).   /cp

    It turned out that the nodes I was trying to register were in a DNS
    directory call .dna_node - as I didn't know this my DECmcc commands
    implied that they were in the DNS root directory.