| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 395.1 | Having the same problem | BRSIS6::BUTTIENS | Roger Buttiens | Wed Oct 10 1990 04:30 | 22 |
|
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.2 | Found !!! | BRSIS6::BUTTIENS | Roger Buttiens | Wed Oct 10 1990 07:32 | 20 |
| 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.3 | Problems are solved | OSLACT::BJORN | Once again | Wed Oct 10 1990 09:50 | 16 |
| Thanks to .-1 for reminding me of the basic setup.
WHen I installed MCCBMSX011, I did run the MCC_DNS_SETUP file. I did NOT run the
MCC_DNS_BASIC_SETUP. That's why I didn't succeed in registering the nodes, even
if I could list them in MCC with the SHOW node4 0 remote *. I'm beginning to
understand how MCC/DNS works.
So, what you have to do after installing the kit is to run MCC_DNS_BASIC_SETUP
and then run MCC_DNS_SETUP in order to register Phase IV nodes and/or create
domains.
Bj�rn Olav Haugom
PS. Shouldn't this be pointed out either in release notes or in the user guide
or any other place in the documentation? I did only see refernces to
MCC_DNS_SETUP
|
| 395.4 | I'm getting a different error message... | AKOV11::COLLINS | | Mon Oct 15 1990 11:23 | 21 |
| 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.5 | more info please | GOSTE::CALLANDER | | Mon Oct 15 1990 15:16 | 8 |
|
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.6 | this is a register command
| AKOV14::COLLINS | | Tue Oct 16 1990 11:09 | 5 |
| 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.7 | directories not that | GOSTE::CALLANDER | | Tue Oct 23 1990 12:04 | 6 |
| 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
|