[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

4897.0. "Error determining contents of domain!" by LICAUS::LICAUSE (Al Licause (264-4780)) Fri Apr 16 1993 10:25

    Once again I'm having a problem with what DECmcc thinks are botched
    domain contents.
    
    This is V4.3 ULTRIX, DECnet/OSI V5.1 and SSB V1.3 DECmcc.
    
    When attempting to start DECmcc several messages are displayed
    indicating that global entities somewhere may have either been
    deregistered.
    
    I have setup three notification events to three individual Phase V
    routers in a single domain.  All three events are setup to be
    specific to the domain and to the NODE entity but ask for
    event = any event.
    
    All three fail to become enabled, displaying the message "An error
    has occured while determining the contents of the domain."
    
    I have attempted to discover which entity is at fault by using
    FCL to SHOW DOMAIN x MEMBER * as discussed in a previous.  I have
    also QAR'd this as being sloppy and incomplete code.  In any case,
    for this particular domain all entities show as being complete and
    none of them display any information about possible deregistrations.
    
    I have tried to deregister the specific NODE entities and reregister
    them to no avail.  I have looked at the members of the domains
    within this domain and all appears to be fine.
    
    I have done a DIRECTORY DOMAIN n MEMBER * and all members list as
    expected w/o errors.
    
    I am using DNS to a private namespace.  The NODE's are registered in
    the DEC:. namespace but this does not seem to be affecting other such
    domains with similar entities registered in exactly the same manner.
    
    Does any one have any clue as to why this is happening?
    
    Does any one have any clue as to how to fix it?
    
    THIS PRODUCT IS DEFINATELY NOT READY FOR PUBLIC CONSUMPTION!!!
    
    Al
    
T.RTitleUserPersonal
Name
DateLines