[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

2532.0. "MIR problems with deleting rules" by OTOOA::DOIRON (Have DECmcc, willing to travel) Wed Mar 11 1992 12:00

    I have written several alarm rules for a demo to check the status of
    the power supplies in a chipcom concentrator. In the process of
    debugging, several variations of the rule were tried. The problem is if
    I try to delete the rule from the map using the toolbox global delete
    symbol, that alarm rule is forever ( as far as I can tell ) messed up.
    
    I am in the situation now were alarm rules cannot be removed either by
    the impm or the fcl command. If I create a new rule and then delete it
    from the fcl all is ok.
    
    Attached is the format of the error message. Just for sanity's sake I
    did a 'DAP> rebuild'  last night but nothing has changed.
    
    
$ man/ent
DECmcc (X1.2.15)

MCC> show mcc 0 alarms rule *, in domain ottawa
Using default ALL IDENTIFIERS

MCC 0 ALARMS RULE CHIPCOM_BACKUP_POWER_bad 
AT 11-MAR-1992 08:43:34 Identifiers

Examination of attributes shows:
                                   NAME = CHIPCOM_BACKUP_POWER_bad

MCC 0 ALARMS RULE CHIPCOM_BACKUP_POWER_OK 
AT 11-MAR-1992 08:43:35 Identifiers

Examination of attributes shows:
                                   NAME = CHIPCOM_BACKUP_POWER_OK

MCC 0 ALARMS RULE CHIPCOM_PRIMARY_POWER 
AT 11-MAR-1992 08:43:35 Identifiers

Examination of attributes shows:
                                   NAME = CHIPCOM_PRIMARY_POWER

MCC 0 ALARMS RULE CHIPCOM_PRIMARY_POWER_bad 
AT 11-MAR-1992 08:43:35 Identifiers

Examination of attributes shows:
                                   NAME = CHIPCOM_PRIMARY_POWER_bad

MCC 0 ALARMS RULE CHIPCOM_PRIMARY_POWER_OK 
AT 11-MAR-1992 08:43:35 Identifiers

Examination of attributes shows:
                                   NAME = CHIPCOM_PRIMARY_POWER_OK

MCC 0 ALARMS RULE HOTLINE_RULE1 
AT 11-MAR-1992 08:43:36 Identifiers

Examination of attributes shows:
                                   NAME = HOTLINE_RULE1

MCC 0 ALARMS RULE HOTLINE_RULE2 
AT 11-MAR-1992 08:43:36 Identifiers

Examination of attributes shows:
                                   NAME = HOTLINE_RULE2
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 08:44:29 

Data base error occurred while deleting rule information.
                        MIR Status = %MCC-E-NOPARAMLIST, no parameter list 
                                      was supplied in this ILV buffer
    
    
    Any ideas on how to fix this?
T.RTitleUserPersonal
Name
DateLines
2532.1Very Strange indeedNANOVX::ROBERTSKeith Roberts - DECmcc Toolkit TeamWed Mar 11 1992 16:4311
  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.2no differenceOTOOA::DOIRONHave DECmcc, willing to travelWed Mar 11 1992 18:3324
    
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.3I'll QAR thisNANOVX::ROBERTSKeith Roberts - DECmcc Toolkit TeamWed Mar 11 1992 19:570
2532.4DELETE alarm MIR corruptionGLDOA::BLOESERThu Jul 09 1992 19:2160
    
    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.5Looks like a corruptionBIKINI::KRAUSEEuropean NewProductEngineer for MCCFri Jul 10 1992 07:3428
>    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