[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

4334.0. "DECdns changes in T1.3.0?" by ANDRIS::putnins () Mon Jan 04 1993 19:53

In the process of upgrading several DECmcc systems that share a DECdns
instance repository, I've discovered a situation where V1.1 and V1.2
systems cannot retrieve information stored by a T1.3.0 system.

I'm starting with a VMS system running DECmcc V1.1 (system A).  This
system is also a DECdns server.  The second system (B) runs ULTRIX 4.2,
DECnet/OSI 5.1, and DECmcc V1.2.3, and uses system A's nameserver.  I
installed DECmcc T1.3.0 on a third system (C) running VMS, and using
A's nameserver.  This worked fine - I was able to open the existing
domains, etc.

Next I decided to restructure the namespace, and move the nameserver
from system A to C.  I used the MCC_DUMP_NS.COM procedure to extract
the entire instance repository, created a new clearinghouse on C and
used DECmcc T1.3.0 on system C to set up and reload the namespace.

Now only system C works.  On both system A and B I get the message
"invalid entity structure" whenever I try to open a domain that has any
members.

Have there been any changes in the way DECdns is used in the new
version?  Is there something I can do to recover from this disaster
short of rebuilding the entire namespace from the V1.2 system?

	- Andy
T.RTitleUserPersonal
Name
DateLines
4334.1DECmcc V1.1 cannot read V1.3 informationTRM::KWAKTue Jan 05 1993 14:4524
    
    RE: .0
    
    Thanks for finding the problem.
    
    There were some changes in storing AESs in ILV-format in T1.3.
    This change prevents DECmcc V1.1 users from seeing entities in DECdns
    which are registered using DECmcc T1.3.
                             
    The users who have to stay with DECmcc V1.1, we suggest that the
    domains and other entities (e.g. Vitalink AM) should be created/registered
    using V1.1. In other words, do not use domains created by DECmcc T1.3.
    
    To summarize compatibilities among different versions of DECmcc:
    	1. DECmcc V1.3 (or T1.3) can access V1.3, V1.2, and V1.1
     	   information.
    	2. DECmcc V1.2 can access V1.3, V1.2, and V1.1 information.
    	3. DECmcc V1.1 can access V1.2, and V1.1 information, but cannot
    	   access V1.3 information in DECdns.
    
    
    William
    
    P.S. This restriction will be included in the Field Test Release Notes.