| .0> Can DECmcc use node objects which already exist in the namespace ?
Yes, though for MCC to work, it requires additional namespace
attributes. This is accomplished by Registering the node with MCC.
(The software is set up so that if you register with MCC you don't have
to do anything else to DECnet - ie. MCC Register is a superset of the
NCL Register command.)
.0> I assume that it will add specific attributes but in doing so, will it
.0> preserve all attributes which the node object already has ?
Yes.
.0> Are there DECmcc functions which will cause me to lose non-DECmcc specific
.0> attributes ? (How can it delete attributes without deleting the object ?)
None that I'm aware of.
|
| .0> Can DECmcc use node objects which already exist in the namespace ?
>> Yes, though for MCC to work, it requires additional namespace
>> attributes. This is accomplished by Registering the node with MCC.
Just for clarification...
My node object already exists. I THEN register this node with MCC. It will
add the additional namespace attributes to the existing object.
Correct ?
The only danger would appear to be the fact that either NCL or MCC can delete
this node object - this is what needs to be controlled.
regards, pat
|
| Hi Pat,
yes, you are right:
if you perform a 'mcc> REGISTER NODE (or NODE4) .dir.name SYNONYM name',
then DECmcc will simply add some mcc_* attributes, eg mcc_uid,
mcc_class if the objects exists already. If the object does not exist,
then DECmcc tries to create an object as decnet_dns_register would do it.
The problem is actually the DEREGISTER directive and the icons to
remove an entity from a domain. One icon is for removal of an entity from a
domain, the other one removes the entity from the domain AND deregisters
the entity.
Next time in Valbonne ? :-)
Klaus
|