[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

611.0. "Renaming Domain problem" by TROU47::SLEE () Thu Jan 10 1991 12:08

    Just recently I experienced  the same symptoms as in notes 352 and
    519. That is when I tried (both Iconic Map or CL) to create a domain,
    I received the "Entity already exists" message, and when I tried
    to delete this domain I got "Entity does not exist".
    
    However, my scenerio leading up to this symptom was different than
    in the other notes. I had a domain already created "CENTRAL_CANADA".
    I wanted to rename this domain to "CANADA". Using the Iconic Map,
    I opened domain CENTRAL_CANADA, and selected SHOW IDENTIFIER option 
    under the OPERATIONS menu. This gave me another window which displayed
    the full-name of my domain. I then selected the CHANGE ENTITY from
    the OPERATIONS menu in this window. It promted me for Enity name
    and I entered "CANADA". This apparently completed.
    
    Understanding my intent, is this a valid method for doing so?
    
    The next thing I did (Iconic Map) was to open domain "CANADA". I
    received "Domain does not exist, do you want to create it". I selected
    yes, and received "already exists". I got the same run-around with
    the FCL as well.   
    
    I grabbed a book on DNS, and went into DNS$CONTROL (the Server is
    also running on my MCC node). I found all the objects in my namespace
    that were created by myself thru MCC. These appeared as follows:
    
    DNS> sho dire . object *
     Object _____ Canada_MCC_EXT000
     Object _____ CGOR01
     Object _____ cthbr1
     Object _____ CTHR01
     Object _____ decnet
     Object _____ decnet_MCC_EXT000
     Object _____ DNA_Registrar
     Object _____ HPO
     Object _____ HPO_MCC_EXT000
     Object _____ Kanata
     Object _____ Kanata_MCC_EXT000
     Object _____ kaobr1
     Object _____ KAOR02
     Object _____ KAOR03
     Object _____ KAOR04
     Object _____ LOO
     Object _____ LOO_MCC_EXT000
     Object _____ MQOR01
     Object _____ OTOR01
     Object _____ TRC
     Object _____ TRC_MCC_EXT000
     Object _____ TRCR01
     Object _____ TROR01
     Object _____ trou77_ch
    
    The domains are stored here using two object names, whereas the
    other global enities (eg. node4 OTOR01, bridge kaobr1) only have
    one.
    
    Can someone explain exactly why this is? Is it because the 
    domain-name_MCC_EXT000 object is used to store cross-reference
    info about domain members?
    
    Anyhow, after I deleted the canada_mcc_ext000 object everything
    worked fine in MCC.
    
    BTW, this is the EFT1.1 kit, and I did not upgrade from a previous
    version.                                               
    
    
    Steve

T.R	Title	User	Date	Lines
611.1		GOSTE::CALLANDER	`Thu Jan 10 1991 15:20`	8
	For a number of reasons, too many to explain, the final V1.1 version of the Domain FM makes use of a new algorythmn that we are hoping corrects all of the "inconsistent" results that people are receiveing. I will pass your note along so that this scenario can be tested against the new FM. Thanks for your input.
611.2		VERNA::V_GILBERT	`Thu Jan 10 1991 17:54`	21
	Steve, I think that your expectation of what "Change Entity" does is not what, in fact, that menu entry in the Management Window actually does. It has NOTHING to do with rename. Rather, it allows the user to select another entity of the same class and level while still in the Management Window (rather than going back to the Map, selecting another entity and operation and creating another Management Window. This is helpful if, for example you want to use a set template that you have typed information into for one entity, for another entity. By selecting Change Entity and entering another instance name, we update the top of the form with the new information. The changes are not made until you press Start Operation for the new entity. Similarly, if you have a Management Window for a show operation on an entity, you may Change Entity to another entity of the same class and level and we will do a show on the new entity. Hope that helps. Verna
611.3	The Namespace is corrupted, What are the steps that caused it?	TOOK::A_MOORE	`Thu Jan 10 1991 18:08`	47
	A healthy domain called Canada should should look like this in DNS: Object _____ Canada Object _____ Canada_MCC_EXT000 . . Object _____ Canada_MCC_EXTnnn The domain_name_MCC_EXTnnn are extensions to store more members in a domain. Up to 3200 members can be stored. If it looks like the example below it is corrupt and you will get the symtoms you described. Object _____ Canada_MCC_EXT000 It is NOT recommened at all to delete mcc objects with DNS$control. But if it ever happens deletion all extension fragments ( i.e. Canada_MCC_EXT000 )will restore the namespace. The CHANGE ENTITY operation does not change the name of a domain. It can not corrupt the namespace. So we still need to find out how did the namespace become corrupted? Could someone have used DNS$Control? ** If Anyone find the set of operations that would corrupt the namespace in this manner please let me know immediately. ** For this version Domains do not allow renaming. Renaming domains, is deep puddle that affects numerous other Management Modules. If there are not any recordings being done by the historian, the recommended method is to copy a domain to temporary domain, delete the orginal and copy it back. Notes 352 and 519 were unrelated problems and not domain bugs . They were problems in communicating how DNS should be setup and that the DNS setup had changed between versions. Just as frustrating. Thanks for writing a complete and clear note.