| Hmm .. I had very similar problems registering a phase V node with MCC.
Like you the registration was failing with unhelpful error messages, although
the DNS object was being modified to include the MCC* attributes. In our case
the object (and its synonym (and backtranslation)) were already in DNS thanks to
DECnet-Ultrix. We eventually got it to work by removing all evidence of the
node from DNS, and then doing the register. We then had to go back to DNU and
put back the back_translation (as MCC is not directly concerned with this)
and update the towers attribute.
I put it down to the fact that register couldn't deal properly with the case
where node objects were already in the namespace. (However this doesn't match
what you're seeing with your NODE4 register.)
Chris
|
|
If you are trying to register a node4 with the latest release
of MCC (UT1.0.1) and your namespace was set up for a previous
version of MCC then the problem probably has something to
do with changes we made to the structure of the namespace between
releases. For one we changed all $ to _ in the DNS directory structure.
This is documented in the UT1.0.1 release notes. I have included
the relevant section from the release notes at the end of this note.
An error like this:
MCC> Register Node4 .DNA_NODE.CITDEM Synonym CITDEM
Node4 CLAUDI_NS:.DNA_NODE.CITDEM
AT 17-JUL-1990 12:03:46
The requested operation cannot be completed
MCC Routine Error = %DNS-E-UNKNOWNENTRY,
Requested entry
does not exist
means that MCC tried to store a piece of information in a DNS directory
that doesn't exist. With this command four pieces of info get written
into DNS.
1. The object CITDEM is created in the .DNA_NODE directory
2. A link for CITDEM's address is created under the .DNA_BACKTRANSLATION
directory
3. A Unique IDentifier for the node is created in .MCC_UID
4. The phase 4 name (synonym) is created in .DNA_NodeSynonym
So you are probable missing one of these directories.
> The registration commands generate an error message.
> The error messages are not helpful at all in tracking down the problem.
> The message should supply more useful information and it should display
> it in human readable form.
Yes, I agree the error message is not helpful. We are working
to make them better.
Pat
----
1.3 DECDNS CONSIDERATIONS
If you installed the internal or external field test version
of DECmcc, read this section carefully.
Before installing this field test update kit, you must
deregister all entities that you have registered using
previous versions of DECmcc.
Each entity managed by DECmcc now has a Unique IDentifier
(UID) assigned by DECmcc. This allows DECmcc to track
entities across rename operations. Should any of the
identifiers which identify an entity be renamed, the UID will
stay constant, allowing DECmcc to access the entity even if
the entity's name is changed. Because of this, you may not
rename any entity managed by DECmcc using any utility other
than DECmcc.
To keep pace with the Phase IV to Phase V transition effort
and to allow future porting to ULTRIX, we have changed the
names of the namespace directories required. All dollar signs
($) have been removed.
MCC$<class>_Backtranslation ---> MCC_<class>_Backtranslation
MCC$UID ---> MCC_UID
DNA$Backtranslation ---> DNA_Backtranslation
DNA$Node ---> DNA_Node
DNA$NodeSynonym ---> DNA_NodeSynonym
DECmcc is now compliant with the Phase V architected directory
names for IDP and AREA. The construction of the directory
names is
DNA_BackTranslation.%x<IDP>.%x<AREA>.<local address>
SYSTEM CONSIDERATIONS Page 1-4
where
IDP is assigned at DECmcc installation time
AREA is a 4 digit hex number of any area in your
DECnet network
local address is a softlink added as part of the
REGISTER process
Because of these name changes, the external field test update
software will not be able to access entities registered using
the external field test software.
The following directories must be present in the DECdns
namespace:
.DNA_BackTranslation
.DNA_BackTranslation.%x<IDP>
.DNA_BackTranslation.%x<IDP>.%x<AREA>
.MCC_<class>_BackTranslation
.MCC
.MCC_UID
.MCC_IP (optional)
.DNA_Node (optional)
.DNA_NodeSynonym
The command file MCC_DNS_SETUP.COM is included on the kit and
placed in the directory MCC_COMMON to create the proper
directories for all supported entities.
The restriction for wildcard searches has been lifted.
Wildcard operations will now work correctly for entities
stored anywhere in the namespace. Therefore, it is no longer
necessary to place entities directly under the root.
Phase IV nodes now have an identifier of datatype FullName.
This lets you place Phase IV nodes wherever you wish in the
namespace. Phase IV nodes are no longer placed under the
DNA_Node directory automatically. The command file
MCC_NODE4_LOAD.COM is included on the kit and placed in the
directory MCC_COMMON for your convenience. This command file
creates a command file that registers all the nodes in your
NCP database into the namespace under the DECdns directory
.DNA_Node.
|
| I have checked that all the needed directories are in place (and
spelled right) and that I have access to them (the right groups
seem to have the right access) but trying the register again still gets
me the same exact error message. I admit that the first time that I
tried it (several days ago) I didn't have the .MCC_UID directory in
place yet, but even after adding it, the error doesn't change.
I did read the release notes carefully before installing the kit (and
yes, I did try a few things before creating the new MCC specific
directories (.MCC and .MCC_UID ... we already had all the DNA_mumble
directories in place by using the Transition tools). However, even with
a new clean install of DECmcc I still cannot register that node.
s/rob
|