[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

1494.0. "install problem wi Phase IV node comm" by NAC::ENGLAND () Thu Sep 12 1991 18:29

    MCC asks you for the name of a Phase IV node, it gives my workstation
    name, TLON, as a default.  I didn't want to use TLON because
    my workstation is a Phase V node and doesn't speak Phase IV.
    So I entered NAC.  The default namespace is the DEC namespace.
    However, I get the error shown below.  I can talk to NAC just fine
    using the DEC namespace (I'm writing this note on NAC logged in from
    my workstation).  Shouldn't this bit be optional? or allow for
    possibility of Phase V?
    
    thx
    
    ben
    
    
    ---------
    Name of DECnet node to register [TLON]: nac
    
    Creating database for DECnet Phase 4 node nac...
    DECmcc (T1.2.1)
    
    
    Node4 LOCAL_NS:.nac
    AT 1991-09-12-19:23:41.937Iinf
    
    The requested operation cannot be completed
                MCC Unhandled Service Reply = Link to Node lost.
     Node4 LOCAL_NS:.nac
    AT 1991-09-12-19:24:08.617Iinf
    
    No such entity: Node4 LOCAL_NS:.nac
                             Unknown Entity = Node4 LOCAL_NS:.nac
    
    
    DECmcc for ULTRIX Configuration Procedure complete
    
    ---------
    
T.RTitleUserPersonal
Name
DateLines
1494.1TOOK::MINTZErik MintzThu Sep 12 1991 18:348
>    Shouldn't this bit be optional?

It is optional

> or allow for possibility of Phase V?

Yes, it should, but no it doesn't.  See page 2-13 of the release notes.

1494.2TOOK::SWISTJim Swist LKG2-2/T2 DTN 226-7102Thu Sep 12 1991 20:1210
    It's also not needed anymore - it was in ut1.2.0 because registration
    of NODE4 also causes registration of that node's lines and circuits,
    whose subentity datatype is SIMPLENAME. In the SQL implementation of
    the MIR, this caused another SQL table to be created (to mimic the
    case semantics of DNS).  That table needed to be owned by root so we
    forced a dummy registration at installation.
    
    The ndbm-mir doesn't have this problem so the whole mess can be
    deleted.
    
1494.3OK, they'll be goneTOOK::MINTZErik MintzThu Sep 12 1991 21:263
OK, this question (and probably some others) will be removed before
the next field test.