[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

188.0. "REGISTER/DEREGISTER problems - SERIOUS MCC ERROR" by NSSG::DAVE (Dave Lyons - Networks DCC - 226-5934 - LKG2-1/S4) Wed Jul 18 1990 11:47

FLAME ON:

MCC is the WORST neighbor that DNA ever had.

flame off.

I used Stan's Migration Tool to populate my DNS namespace so I could communicate
from our Phase 5 systems to our Phase 4 systems.  Everything appeared fine.

Next, I ran MCC, and went to register a node that was not running (I thought it
was, but with a network as big as the easynet, who can tell?).

MCC gave me a somewhat useless error message that was not real clear in that
it claimed there was an error and MCC did not register that node.

After getting the node running, I went to register it again, and got another
error message about the node already being registered, so like a logical
person, I deregistered it.

Supprise! Supprise! Supprise!  Not only did MCC remove the attributes that
it had added to an entry it was sharing with DNA, it blew the whole entry
away.  If MCC is going to SHARE objects with other applications, then it
darn well better learn to be a better neighbor.

T.R Title User Personal
Name Date Lines

188.1 There is a reason why de-register works the way it does... KEEL::SAVAGE Peter Savage Thu Jul 19 1990 10:02 11

T.R	Title	User	Personal Name	Date	Lines
188.1	There is a reason why de-register works the way it does...	KEEL::SAVAGE	Peter Savage	`Thu Jul 19 1990 10:02`	11
	Dave, At a phase V woods meeting it was identified that the register and deregister directives were semantically different than NCL. This was considered to be a problem by the phase V community and was changed within MCC accordingly. The reason behind this was to provide consistency between NCL and MCC. Hope this help clarify things. Peter

    Dave,
    
    At a phase V woods meeting it was identified that the register and
    deregister directives were semantically different than NCL.  This
    was considered to be a problem by the phase V community and was
    changed within MCC accordingly.  The reason behind this was to
    provide consistency between NCL and MCC.
    
    Hope this help clarify things.
    
    Peter