Conference azur::mcc

	Bill,

	There are  many  combinations  of  things you could do.  Let me
	suggest the following...

	I'm assuming you are using V1.1 now.

   1.	Copy the BSYBEE::DUA0:[PUBLIC]MCC_DUMP_NS.COM

	and execute it  (@...).    This will read all the global entity
	and reference data out  of  DECdns  and  create a registeration
	command file to be loaded once you update to V1.2.

   2.	Install the latest BL of DECmcc pointed to in note 3.*
	or if you really need  the TS AM and/or the ELM products *now*,
	install the EFT version of V1.2.    During installation, select
	local MIR.


   3.	Now you can execute the com file  and  all  your  entities  and
	reference data will be re-loaded.

------

	If you want to go back to DECdns,  you can do a simpilar thing,
	use the com file to read the data out  of the local MIR, switch
	to  DECdns,  run the program specified in the release notes  to
	convert  V1.1  SNMP  objects in the DNS MIR to V1.2 format  and
	re-run  the  com  file to re-load any new objects you loaded in
	the local  mir.  I would personnaly re-install DECdns if it was
	my personal name  space.    Of course you can't do it if you're
	sharing somebody elses.

	Clear?  Or did I loose you?

	JCE

   

    No, you didn't lose me.  It all makes sense if I had V1.1 installed
    previously on this machine but, I don't.
    
    
    This is the situation.  At the time of my base note I had not installed
    V1.2.  Now it is installed and working  on an easynet production system
    using the local MIR instead of DECdns.  I would have used DECdns
    except -
    
    	 - I assume that using the DEC namespace is still restricted and
           the bridge, snmp, etc directories are not in place, and
    	   I would not be able to add/delete  objects as I please.
    
    	 - Installing the DECdns server and using a private namespace on a 
    	   system that is using DECdfs for access to the DEC namespace 
           apparently causes problems for DECdfs.
         
    If I can get around the DECdfs problems I would eventually like to
    install the DECdns server and use a private namespace.  Is there
    anything that I can do to make this an easy conversion?  I plan on
    creating a structure that places global classes in their own
    directories and not adding everything at the root level.  I assume that 
    this would be a step in the right direction.
    
    This kind of information would also help in the future when we have
    DECmcc installations that have been using a local MIR and then want to
    convert to DECdns.  
    
    Thanks for any direction,
    Bill
    
    

| Installing the DECdns server and using a private namespace on a
| system that is using DECdfs for access to the DEC namespace
| apparently causes problems for DECdfs.

    Yup it does.  If you point at your private server none of your DFS
    disks will be seen.

| If I can get around the DECdfs problems I would eventually like to
| install the DECdns server and use a private namespace.  Is there
| anything that I can do to make this an easy conversion?

    Yes, there is a way around this.  We've been running in an enviroment
    like this.  What you need to do is modify your DFS$SYSTARTUP.COM and
    prefix the disk names with "DEC:".  Then in your DNS$DEFAULT_FILE.DAT,
    make sure your private namespace is first, then add the corporate
    namespaces with the nickname = DEC.  After that everything should work
    fine.  Here is what our DNS$DEFAULT_FILE.DAT looks like.  (DEGABA is
    our private namespace for MCC.)

 namespace nickname=DEGABA_NS
 namespace uid=aa000400c2df20a5a9a64d539400
 clearinghouse name=degaba_ch
 clearinghouse uid=aa000400c2df404feea64d539400
 clearinghouse address=aa-00-04-00-c2-df
 namespace nickname=DEC
 namespace uid=aa000400de11a0aaf96f56de8e00
 clearinghouse name=tay.tayns1_ch
 clearinghouse uid=aa000400de11e01090121e159300
 clearinghouse address=aa-00-04-00-06-dc
 namespace nickname=DEC
 namespace uid=aa000400de11a0aaf96f56de8e00
 clearinghouse name=tay.tayns2_ch
 clearinghouse uid=aa000400de11a01b821022159300
 clearinghouse address=aa-00-04-00-49-dc
 namespace nickname=DEC
 namespace uid=aa000400de11a0aaf96f56de8e00
 clearinghouse name=lkg.lkgns2_ch
 clearinghouse uid=aa000400de11c06b042aa9139300
 clearinghouse address=aa-00-04-00-2a-10

    There is a couple of more things that you need to do to move between
    namespaces (note that it doesn't really matter whether it is DNS to
    DNS, DNS to Local, Local to DNS etc).
    
    In general
      1	Use the MCC_DUMP_DNS procedure mentioned earlier
      -	From the FCL (if you have lots of Sync lines)
    		SHOW NODE4 * LINE * LINE SPEED, TO FILE = filename
      -	If moving to another system, copy the map files over
      2	Run my CONVERT_MCC_MAPS.COM (found in
    		NETS::USER$NETS:[MCC011.S-KIT]
    		to normalize the mapfile names since the UIDs in them
    		will no longer relate to the associated domains in the
    		new namespace
      -	Optionally edit the registration file created by MCC_DUMP_DNS
    	 to adjust case of names etc.
      3	Execute the registrations
      -	Use the output from the FCL output to determine what line speeds
    	 to set for any sync lines you may have.
    
    Note that there is only really 3 steps but there are some other things
    you may want to do as well.
    
       
    s/rob