[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

395.0. "INV_ENTITY, setup of Phase IV nodes" by OSLACT::BJORN ("Where's the ice bears in Oslo, Norway??") Tue Oct 09 1990 08:37

T.RTitleUserPersonal
Name
DateLines
395.1Having the same problemBRSIS6::BUTTIENSRoger ButtiensWed Oct 10 1990 06:3022
I seem to suffer from the same problem.  (MCCBMSX011 and VMS 5.3-2)

In the iconic map PM and in the FCL PM I receive the message

                          MCC Routine Error = %MCC-E-INV_ENTITY, invalid
    			  		      entity structure

when registering a NODE4. 
(In FCL :  register node4 .dna_node.brsis6 synonym brsis6)


I do not think this is due to DNS, since the clearinghouse is accessed properly
and I am only experiencing these registration problem with object type NODE4.
However, someone else here in Brussels has been using the same kits and with his
director there is no problem at all if you try to register a NODE4.

What has gone wrong or is different?
Any hints of where to start looking ?  Or where to look for other information ?

/Roger.
  
395.2Found !!!BRSIS6::BUTTIENSRoger ButtiensWed Oct 10 1990 09:3220
Running the BASIC setup for DNS is not enough.

You also have to run option 1 in the the MCC_DNS_SETUP.COM procedure
in MCC_COMMON.  At least ...  after running this I succeeded in registering
a NODE4 object.

It takes some time, since it creates additional directories in the namespace.
If you do not have them, the DNS directory structure is incomplete.  Probabely
that is why MCC complains about an invalid entity structure.

I wonder why the MCC kit cannot do this.   You don't need DNS$control to 
create Namespace directories.  Perhaps this could be made transparant for the
installer by the use of a special image, only needed at installation time,
that checks & creates a correct namespace structure.   The image should make
use of the DNS Clerk, just as other MCC images do.   I suppose this will be done
later on, but that it has been postponed, since there are alternative ways to
do it (DNS$CONTROL).

/Roger.

395.3Problems are solvedOSLACT::BJORNOnce againWed Oct 10 1990 11:5016
395.4I'm getting a different error message...AKOV11::COLLINSMon Oct 15 1990 13:2321
After reading the previous replys, I ran MCC_DNS_BASIC_SETUP AND MCC_DNS_SETUP,
in that order, and I am still getting the following error:


Node4 AKO588_NS:.dna_node.[node name]
AT 15-OCT-1990 10:16:11



The requested operation cannot be completed
		      MCC Service Error = Internal error in DECnet Phase IV AM.


Now, this is fine, but I can't an error log file to try and find the problem with
the DECnet Phase IV AM!!!!


Does anyone have any idea what I have done wrong, or forgotten to do??


Norm
395.5more info pleaseGOSTE::CALLANDERMon Oct 15 1990 17:168
    
    Is this on a show command or on a register?
    
    
    Also, can you do a show all identifiers on the node that you
    are specifying?
    
    
395.6this is a register command AKOV14::COLLINSTue Oct 16 1990 13:095
This error is from a register commond. But I can't do a show of any system. The 
error says that the entity is not registered.


Norm
395.7directories not thatGOSTE::CALLANDERTue Oct 23 1990 14:046
    it looks like you didn't run option 1 in dns_setup. If you check
    your name space my guess is that dna_node doesn't exist and that
    is why you can't register (I believe .2 or .3 points this out).
    
    jill