| 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 |
V1.3 DECmcc on ULTRIX....probably on VMS as well.
When opening a domain in the Iconic map interface, if a mismatch
occurs between the MIR/DNS and the map file, a message is displayed
some thing to the effect " one or more global entities has been
deregistered"....(sorry... doing this from memory).
This turns out to be one of those "Royal Pain" type messages in that
the message only stated that something is missing.....it doesn't tell
the user which entity is being flagged is missing.
1) Is this a significant message in terms of functionality...(i.e.
will it prevent other functions from completing)?
2) If it is not significant why bother displaying it?
3) If it is significant why not try to do a better job of finding
the entity that has been deregistered?
4) If 3=true, then is it possible to compare the contents of the
map file for a missing entity.....(i.e. if the MIR/DNS entry is
has been deregistered, presumably by the FCL interface, and the
entry is still in the map file, then why not try to search the
map file for string indicating or at least guessing at which
entity has caused the error in the first place)?
Al
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4855.1 | Here is how to fix it | TOOK::R_SPENCE | Nets don't fail me now... | Tue Apr 13 1993 15:27 | 16 |
From the Command line do a
MCC> show domain {domain name} member *
and the output listing will show you which members are deregistered.
To clean it up just do a
MCC> delete domain {domain name} member {member name}
No more error message when you open the map.
I agree that it would be good if it told you which members were a
problem. QAR it if it is important to you.
s/rob
| |||||
| 4855.2 | Engineering....please do more when obvious! | LICAUS::LICAUSE | Al Licause (264-4780) | Tue Apr 13 1993 16:04 | 17 |
Rob,
Thanks for the hint.
I'll try to QAR this, as I believe that it is incorrect or "lazy"
behavior.
The simple fact that you can issue the FCL commands as you have
indicated shows that MCC already has knowledge of the specific entities
that it believes have been deregistered.
Perhaps it might be asking too much or making an assumption that the
program should take the action to automatically correct this situation,
but minimally it should notify the user of the specific entities that
it detected rather than just report "some" have been deregistered.
Al
| |||||
| 4855.3 | You can delete member, but not entity. | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Wed Apr 14 1993 13:30 | 14 |
Of course you can delete the member from the domain, but that is not
the problem. The entity cannot be deregistered. This is a problem
similar to the "dangling link" of DNS.
I was asked whether or not this was a big enough issue for resoultion
before shipping V1.3. When I thought it was a domain-based issue, I
said "No".
I now realize I goofed. If William Kwak's "dangling-link-removal"
utility works, I will live with the problem until it is fixed in a
future release. I will generate a CLD to track this.
Regards,
Dan
| |||||