| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2532.1 | Very Strange indeed | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Wed Mar 11 1992 13:43 | 11 |
| This certainly is very strange ... !
I'll poke around in the code to see if anything makes sense.
In the mean time, could you try the 'other' Alarms Syntax :
delete domain <domain-name> rule <rule-name>
and let us know if the same problem is encountered ..?
thanks,
/keith
|
| 2532.2 | no difference | OTOOA::DOIRON | Have DECmcc, willing to travel | Wed Mar 11 1992 15:33 | 24 |
|
The problem is the same with either command.......
MCC> delete mcc 0 alarms rule chipcom_primary_power_ok, in domain ottawa
MCC 0 ALARMS RULE chipcom_primary_power_ok
AT 11-MAR-1992 15:30:21
Data base error occurred while deleting rule information.
MIR Status = %MCC-E-NOPARAMLIST, no parameter list
was supplied in this ILV buffer
MCC> delete domain ottawa rule chipcom_primary_power_ok
Domain LOCAL_NS:.ottawa Rule chipcom_primary_power_ok
AT 11-MAR-1992 15:30:48
Data base error while deleting rule information.
MIR Status = %MCC-E-NOPARAMLIST, no parameter list
was supplied in this ILV buffer
Very strange,,,,,
|
| 2532.3 | I'll QAR this | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Wed Mar 11 1992 16:57 | 0 |
| 2532.4 | DELETE alarm MIR corruption | GLDOA::BLOESER | | Thu Jul 09 1992 16:21 | 60 |
|
Re: DECmcc v1.1
VMS 5.4-3
Patches applied - MCCBMS011_PATCH_ALARMS_1
MCCBMS011_PATCH_ALARMS_2
My customer cannot delete a certain alarm rule.
Something like what is described in note #574.1 is happening here.
I suspect that something happened during a CREATE or DELETE to
inhibit normal command execution.
Is deleting some or all of the MIR the only solution ?
MCC> show mcc 0 alarms rule pwnet1_down all attributes, in
domain=.kal_acc.vax
MCC 0 ALARMS RULE pwnet1_down
AT 9-JUL-1992 12:17:49 All Attributes<CR><LF><CR>
NAME = pwnet1_down
State = Disabled
The rule MCC 0 ALARMS RULE pwnet1_down was not enabled,
and therefore has no counters.
MCC> enable mcc 0 alarms rule pwnet1_down, in domain=.kal_acc.vax
MCC 0 ALARMS RULE pwnet1_down
AT 9-JUL-1992 12:18:35
Data base error while reading rule information.
MIR Status = %MCC-E-NOATTREXIST, specified
attribute record does not exist
MCC> show mcc 0 alarms rule pwnet1_down all identifiers, -
in domain=.kal_acc.vax
MCC 0 ALARMS RULE pwnet1_down
AT 9-JUL-1992 12:19:05 Identifiers
Examination of attributes shows:
NAME = pwnet1_down
MCC> show mcc 0 alarms rule pwnet1_down all characteristics, -
in domain=.kal_acc.vax
MCC 0 ALARMS RULE pwnet1_down
AT 9-JUL-1992 12:20:05 Characteristics
Data base error occurred while reading rule information.
MIR Status = %MCC-E-NOATTREXIST, specified
attribute record does not exist
MCC> delete mcc 0 alarms rule pwnet1_down, in domain=.kal_acc.vax
MCC 0 ALARMS RULE pwnet1_down
AT 9-JUL-1992 12:20:47
Data base error occurred while deleting rule information.
MIR Status = %MCC-E-NOENTITY, no corresponding
entity instance exists
MCC>
|
| 2532.5 | Looks like a corruption | BIKINI::KRAUSE | European NewProductEngineer for MCC | Fri Jul 10 1992 04:34 | 28 |
| > Re: DECmcc v1.1
> VMS 5.4-3
> Patches applied - MCCBMS011_PATCH_ALARMS_1
> MCCBMS011_PATCH_ALARMS_2
ALARMS_2 is for VMS 5.5 only ! It adapts the Alarms FM to the new
queue management of VMS 5.5. Should not cause any corruptions on
earlier VMS versions, though. Just the Alarms Fired/Exception
Procedures will not work.
Your problem looks very much like a corruption of the Alarms MIR.
You could try to extract the rules by running
SYS$SYSTEM:MCC_ALARMS_EXTRACT_RULES. If you are lucky this will get
your rules back; at least in text form.
> Is deleting some or all of the MIR the only solution ?
I'm afraid, yes. The files to delete are
MCC_COMMON:MCC_ALARMS_ATTRIBUTE_MIR.DAT and
MCC_COMMON:MCC_ALARMS_INSTANCE_MIR.DAT.
Then execute @SYS$STARTUP:MCC_STARTUP_BMS ENROLL *from the SYSTEM
account*. This will create a new (empty) Alarms MIR. You have to
create all your rules again after that.
Good luck,
*Robert
|