[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

3887.0. "Alarm not clearing" by VCSESU::WADE (Bill Wade, VAXc Systems & Support Eng) Fri Oct 09 1992 17:10

    I'm having a problem with receiving alarm clear events from the Iconic
    Map.  I have customized to propagate the latest event.
    
    With this rule -
        	
	!                                                 
	!
    
	Create Domain LOCAL_NS:.site2 Rule OMS_BRDG_SITE2-620_LINE_1_STATE  -
  	Expression   = (CHANGE_OF (BRIDGE bridge.site2-620 LINE 1 
    				PORT MODULE STATE, *,*), AT  EVERY=00:01), -
  	Severity     = Critical, -
  	Description  = "Line has changed state"
	!
    
    I receive the critical events but don't receive the clear event when the
    rule status shows cleared.
             
    Any ideas?
T.RTitleUserPersonal
Name		DateLines
3887.1MCC012_EXT database - QAR #00498VCSESU::WADEBill Wade, VAXc Systems & Support EngWed Oct 14 1992 16:351
3887.2VCSESU::WADEBill Wade, VAXc Systems & Support EngFri Oct 23 1992 14:1116
    
    The documentation states that this works but it doesn't.
    
    Is something unclear in my problem description?  
    
    Has anyone else encountered this problem?
    
    Can I get an answer/status to this QAR?
    
    I know times are tough and I don't want to be a thorn in your side but
    this QAR along with several others are sitting in the MCC012_EXT
    database with no answers!
                              
    Regards,
    Bill
3887.3works as codedMCC1::DITMARSPeteWed Oct 28 1992 13:4431
I am not the developer/maintainer for this module, but
I looked at the code to see what was going on.

Unfortunately, this is working the way the implementor
desired it to work.  I looked at the code and it explicitly
checks to ensure that the rule is a "simple expression"
and not a change_of before generating the "clear" event.

I think this problem needs to be thought through a bit
to see if it makes sense for a change_of alarm to clear.

Is it enough to say "the rule did not fire and therefore
it is now CLEAR" for all the different ways a change_of
alarm can be specified?

change_of	
formats
---------
v1,v2		
*,v
v,*
*,*

Apply it to your own example: if the state goes from
up to down and the rule fires and then the state stays
at down for a polling interval, do you want the rule to
"clear"?

In any case, if the code's behavior does not change for
V1.3, the documentation should be brought in line with
the code's behavior.
3887.4VCSESU::WADEBill Wade, VAXc Systems & Support EngFri Oct 30 1992 09:537
    re .3  Good point.
    
    	We'll have to give some thought to changing our rules to explicitly 
    	check for "Broken" state.
    
    Thanks,
    Bill
3887.5try UNBROKENCTHQ::WOODCOCKSun Nov 01 1992 01:2815
>   <<< Note 3887.4 by VCSESU::WADE "Bill Wade, VAXc Systems & Support Eng" >>>
>
>   re .3  Good point.
>    
>    	We'll have to give some thought to changing our rules to explicitly 
>    	check for "Broken" state.
    
It may be easier to define the UNBROKEN state and have this as a characteristic
of the alarm which defines a CLEAR. This is a much needed feature. CHANGE_OF is
very powerful and with the coming of its wildcarding this should be put into
code. The problem is that CHANGE_OF functions still can't get the color/severity
right for the IMPM.

best regards,
brad...