| 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 |
Due to some accedental file ownership problems I have a case where I
apparently created an alarm rule but did not have access to the MIR
files. Now that I have fixed my file ownership problem I cannot clean
up the problem (nor can I figure out where the data is stored).
I now get the following response (this is all I saw from the FCL when
using a command file;
(attempt to delete old instance of the alarm)
MCC 0 ALARMS RULE NSSG_LINE_usage
AT 20-DEC-1990 11:35:36
Entity did not exist.
(attempt to create new instance of the alarm)
MCC 0 ALARMS RULE NSSG_LINE_usage
AT 20-DEC-1990 11:35:38
Attempt to create duplicate entity rejected.
Any suggestions on how I can fix my problem so I can continue?
s/rob
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 574.1 | Yup, you found a whole in our logic | TOOK::ORENSTEIN | Thu Dec 20 1990 17:25 | 32 | |
Hi Rob,
You found a bug.
ALARMS maintains 2 MIR files -- one for the rule instances and one for
the rule attributes. It looks like you were able to create the rule
instance OK, but couldn't write the attributes to the attribute MIR
because of incorrect file protections.
When ALARMS deletes a rule, it is first deleted out of the attribute
MIR and then out of the instance MIR. Since the attributes were never
written because of you orignal file protections, the DELETE directive
responds that the entity did not exist without tyring to delete the
isntance.
When ALARMS creates a rule, the instance MIR is first checked to see if
already exists. Since you were able to write the rule instance to the
MIR, the CREATE directive responds that the entity already exists.
The logic has a whole, which you, unfortunately, found before we could
get the next version of ALARMS out to you. We have fixed ALARMS so
that the DELETE will always try to delete BOTH the instance and the
attributes. This means it will clean-up.
In the mean time I can only suggest that you delete the MIR files and
start again. If you have some rules in the MIR that you can SHOW, then
you can run the MCC_ALARMS_EXTRACT_RULES program to create a DCL
command procedure that will help you recreate your rules in your fresh
MIR.
Sorry for the inconvenience, aud...
| |||||
| 574.2 | NSSG::R_SPENCE | Nets don't fail me now... | Fri Dec 21 1990 12:57 | 3 | |
Thanks very much (for fixing it in next baselevel).
s/rob
| |||||