[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

988.0. "MCC-E-INVALID IDENT" by EISSRC::CATALANO (Steve) Sat May 04 1991 13:05

I am working with a customer to set up a DECmcc evaluation......
We have run into various problems in installing DECmcc......

Currently we have upgraded to BMS 1.1. We are issuing the following
command:

REGISTER NODE 4 EMALNR_NF:DNA_NODE.GEMINI SYNONYM=GEMINI

and getting the following error message:

MCC-E-INVALID IDENT INVALID ENTITY IDENTIFIER

We have had Colorado dial into the system and take a look and they tell us
that everything looks OK.....

FYI...One (of several) problems we did run into while installing the 1.0 version
of EMA was that the version of DNS 1.1a we had installed did not work it and 
caused the installation to fail....We did go back to DNS 1.0 and it did work....
However when we intalled BMS 1.1 we also reinstalled DNS 1.1a.....this may 
nothing to do with the problem.....Colorado tells us it should be
OK....then again it may.....

Thanks in advance for your help....
Steve C....
T.RTitleUserPersonal
Name
DateLines
988.1register node errorCSC32::E_SMITHSun May 05 1991 01:327
    The correct syntax of the command should be:
    REGISTER NODE4 EMALNR_NF:DNA_NODE.GEMINI SYNONYM=GEMINI
    
    Notice -no space between node and 4 -node4
    
    Also according to the pre-requisit software list handed out in
    the v1.1ft training DNS should be V1.1.
988.2BSYBEE::EGOLFJohn C. Egolf LKG2-2/T02 x226-7874Sun May 05 1991 13:144
	.1 is right.

	NODE 	=	DECnet/OSI (DECnet Phase V)
	NODE4	=	DECnet Phase IV
988.3See topic 652.* on Non-default NamespaceTRM::KWAKMon May 06 1991 13:349
    Re: .0
    
    Caution:
        When you specify the Namespace ("EMALNR_NF:") in the Register
    	command AND the namespace is different from your system's default
    	namespace, you're writting information into two different namespaces.
    
        Please see topic 652.* on the use of Non-default Namespace.
    
988.4Question on full name specNSSG::R_SPENCENets don't fail me now...Tue May 07 1991 14:537
    Is there also a dot needed between the namespace colon and the first
    part of the name?
    
    eg; TEST_NS:.DNA_NODE.GEORGE vs TEST_NS:DNA_NODE.GEORGE
    
    s/rob
    
988.5Dots and more dotsCLAUDI::PETERSFri May 10 1991 19:192
Rob, the leading dot is not required so TEST_NS:DNA_NODE.WHATEVER
is just fine.  /cp