[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

2709.0. "REGISTRATION/DEREGISTRATION PROBLEM W/X1.2.15" by RGNET8::BOUTHIETTE (Feed your lust for life!!) Tue Apr 07 1992 11:48

I have been having problems with registeriong deregistering a node using
DECMCC vX1.2.5 on VMS 5.5. Attached is a log to demonstrate the problem,
can anyone offer assistance. I am using the local "MIR" not DNS...

Thanks,
John B.





$ man/ent

DECmcc (X1.2.15)
MCC> register node4 .dna_node.mro2ac

Node4 LOCAL_NS:.dna_node.mro2ac
 
AT  7-APR-1992 09:24:33 

The entity is already registered with MCC.

MCC> deregister node4 .dna_node.mro2ac

Node4 LOCAL_NS:.dna_node.mro2ac 

AT  7-APR-1992 09:24:40 

The entity Node4 LOCAL_NS:.dna_node.mro2ac  is not registered
                  Not Registered Entity = 

Node4 LOCAL_NS:.dna_node.mro2ac 


MCC> deregister node4 .dna_node.mro2ac

MCC> dir node4 mro2ac

Node4 mro2ac 

AT  7-APR-1992 09:24:53 

The entity Node4 mro2ac  is not registered
                  Not Registered Entity = 
Node4 mro2ac 

T.RTitleUserPersonal
Name
DateLines
2709.1anything yet???RGNET8::BOUTHIETTEFeed your lust for life!!Mon Apr 13 1992 18:223
    Any word on this yet???
    
    Jb.
2709.2The directory name cannot be used as an object nameTRM::KWAKTue Apr 21 1992 10:5921
    
    RE: .0
    
    After examing a dump of the Local MIR repository, it was found that
    there was a bug in the MCC Kernel code.
    
    The problem happend when a Circuit entity ".dna_node.mro2ac.syn-0"
    was registered first, and then a node4 entity ".dna_node.mro2ac"
    was registered. Note that the name ".dna_node.mr02ac" was used as
    a directory name in the Circuit entity AND an object name in the
    Node4 entity.  This is not allowed in DNS because a DNS entry (object,
    directory, or softlink) has to be unique and an existing directory name 
    cannot be used as a new object name. However, the Local MIR codes
    allowed this to happen.                                     
    
    For Field Test update (T1.2.7), a fix was made such that a directory
    name cannot be used as an object name in Local MIR on VMS.
    
    Thanks for finding the problem.
    
    William