Conference azur::mcc

    I attempted (with the soon to be released EFT 1.1 kit) to reproduce
    your problem to no avail. Could you please retry when you get the
    new kit. 
    
    	thanks
    	jill
    
    MCC> create mcc 0 alarm rule foo expr=(node4 .dna_node.goste remot
    node 4.507 st
    ate=reachable, at ever ::22)
    
    MCC 0 ALARMS RULE foo
    AT 26-NOV-1990 16:04:44
    
    Entity created successfully.
    MCC> sho node4 .dna_node.goste remo node 4.507 state
    %MCC-W-VERBAMBIG, verb SHO is ambiguous; enter more characters
    MCC> defin sho show
    MCC> sho node4 .dna_node.goste remo node 4.507 state
    
    Node4 4.507 Remote Node 4.507
    AT 26-NOV-1990 16:05:20 Status
    
                                      State = Reachable
    MCC> enable mcc 0 alarm rule foo
    
    MCC 0 ALARMS RULE foo
    AT 26-NOV-1990 16:05:33
    
    Normal operation has begun.
    MCC> getevent mcc 0 alarm rule foo any notif event
    
    MCC 0 ALARMS RULE foo
    AT 26-NOV-1990 16:05:59 NOTIFICATION EVENTS
    
    Alarm Event Received
    Alarm Rule Fired
                                   EVIDENCE = { (          entity =
    Node4 4.507
                                                                   
    Remote Node
                                                                   
    4.507 ,
                                                             data =
    "State =
                                                                   
    Reachable ",
                                                        timestamp =
    26-NOV-1990
                                                                   
    16:05:57.17 ) }
                                 Expression = (node4 .dna_node.goste
    remot node
                                              4.507 state=reachable,
    at ever ::22)
                         Perceived Severity = indeterminate
    MCC> disable mcc 0 alarm rule foo
    
    MCC 0 ALARMS RULE foo
    AT 26-NOV-1990 16:06:23
    
    Normal operation will be terminated.
    MCC> delete mcc 0 alarm rule foo
    
    MCC 0 ALARMS RULE foo
    AT 26-NOV-1990 16:06:26
    
    Enabled rules cannot be deleted.
    MCC>
    
    
    *** I would also suggest that you try using an exception handler
    which can report back to you what caused a rule to terminate, or
    return an error.
    
    jill
    

RE: .0

Hi Dave,

Thanks Dave for pointing out a bug. The reason why you get the 
apparently "false" result is because the Decnet Phase 4 AM has 
two values for state whose external representation is the string
"Reachable". What follows is the MSL definition of their
state attribute:
+-------------------------------------------------------------------------------------------+
|DAP> show class node4 subclass remotenode attribute state definition CONSTRUCTOR_DATA_TYPE |
|                                                                                           |
|   Definition Name = CONSTRUCTOR_DATA_TYPE                                                 |
|   Type = T   Length = 70   Count = 1   Defined = TRUE   Class = S   Usage = ILV           |
|                                                                                           |
|         (                                                                                 |
|          1 = (                                                                            |
|              0 = %X    526561636861626C65 -- "Reachable"                                  |
|              1 = %X    556E726561636861626C65 -- "Unreachable"                            |
|              2 = %X    53687574 -- "Shut"                                                 |
|              3 = %X    52657374726963746564 -- "Restricted"                               |
|              4 = %X    526561636861626C65 -- "Reachable"                                  |
|              5 = %X    556E726561636861626C65 -- "Unreachable"                            |
|            )         )                                                                    |
|                                                                                           |
+-------------------------------------------------------------------------------------------+

To be fair I hav not seen the sources of their MSL. I will talk to Jim Carry (PL DNA4)
to understand why he define the "state " attribute this way. I am not convinced
that is is even allowed. If it is we may have to change Alarms algorithm to
evaluate an expression. 


I know what you are saying. "I don't care what you problem is just do the 
right thing for me!" And I will support your feelings!! Even the EFT kit will
not solve your problem. I do have a work around for you. Make your expression
as follows:

 Expression = (CHANGE_OF( NODE4 .wlort3 REMOTE NODE 41.221 State, *,*), AT EVERY 00:01:00)

Note that the rule will only fire when a change in state attribute takes
place in between to polling points. 

Also in EFT you could use appropriate Event to monitor Reachability status.

Hope the above work around puts you in a reasonably happy State! :-)

							Thanks,

							Anil Navkal
							Alarms PL