| We are looking into the bug your customer reported.
One case that will cause that problem is as follows:
I have a domain called .ed_10 with three node4 entities
.dna_node.bedtim, .dna_node.wasabi and .dna_node.zayin in it.
MCC> show domain .ed_10 member *
Using default ALL IDENTIFIERS
Domain MCC1_NS:.ed_10 Member MCC1_NS:.dna_node.bedtim
AT 20-JUN-1991 11:03:33 Identifiers
Examination of attributes shows
MemberName = MCC1_NS:.dna_node.bedtim
Domain MCC1_NS:.ed_10 Member MCC1_NS:.dna_node.wasabi
AT 20-JUN-1991 11:03:33 Identifiers
Examination of attributes shows
MemberName = MCC1_NS:.dna_node.wasabi
Domain MCC1_NS:.ed_10 Member MCC1_NS:.dna_node.zayin
AT 20-JUN-1991 11:03:33 Identifiers
Examination of attributes shows
MemberName = MCC1_NS:.dna_node.zayin
Now the first two forms of directory in .0 work and the third form
fails, as described in release notes:
MCC> directory node4 .dna_node.*
Node4 MCC1_NS:.dna_node.bedtim
AT 20-JUN-1991 11:09:07
Directory successful.
Registered Name = MCC1_NS:.dna_node.bedtim
Address = 4.436
Name = BEDTIM
Node4 MCC1_NS:.dna_node.wasabi
AT 20-JUN-1991 11:09:07
Directory successful.
Registered Name = MCC1_NS:.dna_node.wasabi
Address = 4.438
Name = WASABI
Node4 MCC1_NS:.dna_node.zayin
AT 20-JUN-1991 11:09:07
Directory successful.
Registered Name = MCC1_NS:.dna_node.zayin
Address = 63.1019
Name = ZAYIN
MCC> directory node4 *, in domain .ed_10
Node4 MCC1_NS:.dna_node.bedtim
AT 20-JUN-1991 11:09:45
Directory successful.
Registered Name = MCC1_NS:.dna_node.bedtim
Address = 4.436
Name = BEDTIM
Node4 MCC1_NS:.dna_node.wasabi
AT 20-JUN-1991 11:09:45
Directory successful.
Registered Name = MCC1_NS:.dna_node.wasabi
Address = 4.438
Name = WASABI
Node4 MCC1_NS:.dna_node.zayin
AT 20-JUN-1991 11:09:45
Directory successful.
Registered Name = MCC1_NS:.dna_node.zayin
Address = 63.1019
Name = ZAYIN
MCC> directory node4 .dna_node.*, in domain .ed_10
Node4 MCC1_NS:.dna_node.*
AT 20-JUN-1991 11:10:22
The requested operation cannot be completed
MCC Unhandled Service Reply = No such entity: Domain MCC1_NS:.ed_10
Member *
Unknown Entity = Domain MCC1_NS:.ed_10 Member *
Now I go into dns and manually delete object .dna_node.wasabi, as
follows:
$ mcr dns$control
DNS> show object .dna_node.wasabi
Attribute (Single) ___ DNA$NodeSynonym
Attribute (Set) ______ DNA$TOWERS
Attribute (Set) ______ DNS$ACS
Attribute (Single) ___ DNS$Class
Attribute (Single) ___ DNS$ClassVersion
Attribute (Single) ___ DNS$UID
Attribute (Single) ___ DNS$UTS
Attribute (Set) ______ MCC_Class
Attribute (Set) ______ MCC_DOMAIN_LIST
Attribute (Single) ___ MCC_UID
Attribute (Set) ______ MCC_Version
DNS> delete object .dna_node.wasabi
DNS> show object .dna_node.wasabi
%DNS-E-UNKNOWNENTRY, Requested entry does not exist
DNS> exit
Now I re-do the three forms of directory in .0:
MCC> directory node4 .dna_node.*
Node4 MCC1_NS:.dna_node.bedtim
AT 20-JUN-1991 11:14:28
Directory successful.
Registered Name = MCC1_NS:.dna_node.bedtim
Address = 4.436
Name = BEDTIM
Node4 MCC1_NS:.dna_node.zayin
AT 20-JUN-1991 11:14:28
Directory successful.
Registered Name = MCC1_NS:.dna_node.zayin
Address = 63.1019
Name = ZAYIN
MCC> directory node4 *, in domain .ed_10
Node4 *
AT 20-JUN-1991 11:14:46
The requested operation cannot be completed
%MCC-E-NOENTITY, no corresponding entity instance exists
MCC> directory node4 .dna_node.*, in domain .ed_10
Node4 MCC1_NS:.dna_node.bedtim
AT 20-JUN-1991 11:15:33
Directory successful.
Registered Name = MCC1_NS:.dna_node.bedtim
Address = 4.436
Name = BEDTIM
We see that DIRECTORY NODE4 *, IN DOMAIN .ed_10 fails. Since node4
.dna_node.wasabi is deleted manually through dns$control and not via DECmcc,
domain .ed_10 still have information about .dna_node.wasabi even it is deleted.
However this is not handled properly by DOMAIN FM. (CONFIG FM calls DOMAIN FM
when there is a "in domain" qualifier) I understand the above bug will be fixed
in V1.2.
Also somehow under the above conditions, DIRECTORY NODE4 .dna_node.*,
IN DOMAIN .ed_10 gives back one node4 entity. I understand this will also be
fixed in V1.2.
The following shows that .dna_node.wasabi is detected as a deregistered
member in domain .ed_10.
MCC> show domain .ed_10 member *
Using default ALL IDENTIFIERS
Domain MCC1_NS:.ed_10 Member MCC1_NS:.dna_node.bedtim
AT 20-JUN-1991 11:16:16 Identifiers
Examination of attributes shows
MemberName = MCC1_NS:.dna_node.bedtim
Domain MCC1_NS:.ed_10 Member MCC1_NS:.dna_node.bedtim
AT 20-JUN-1991 11:16:23 Identifiers
Detected a deregistered Domain Member. MCC1_NS:.dna_node.wasabi
Domain MCC1_NS:.ed_10 Member MCC1_NS:.dna_node.zayin
AT 20-JUN-1991 11:16:23 Identifiers
Examination of attributes shows
MemberName = MCC1_NS:.dna_node.zayin
One thing you (or your customer) might want to try is to do the command
SHOW DOMAIN domain_name member * and see if there is a detected deregistered
domain member in it. If so, the explanation above is probably the reason for
your problem. Do a DELETE DOMAIN domain_name member member_name to remove the
detected deregistered domain member and try DIR NODE4 *, in domain domain_name
again.
If that still does not explain the problem, could you include the exact
commands and all the output here so we can look into it more.
|