Conference azur::mcc

5940.0. "Notifications OK but alarm rules not triggered" by BALZAC::COULON (Even if it works, ask why) Thu Apr 07 1994 06:49

 We have developped an access module to handle network events generated by the
french X.25 public network TRANSPAC. The global entities are network components
(X.25 switches) with LINES as child entities. 

 The problem: when an X.25 switch is done, TRANSPAC generates network events not
only for the global entity (the switch itself) but also for all the lines (up
to 16) connected to the switch. In this case:

 - All these events are correctly notified in the DECmcc notification window
 - The ALARM RULE with the OCCURS clause for the global entity is correctly
   triggered
 - BUT, the ALARM RULE(s) with the OCCURS clause for the child entities (lines)
   are NOT triggered. How is it possible if notifications are there?

 If we simulate the same network events more slowly (!), it works fine (ALARM 
RULE(s) with the OCCURS clause for the child entities (lines) are triggered).

The configuration (VMS):

	----- X.25 ------ X.25 Module ----- Access Module ----- DECmcc

             Events ----- Read event
                          Translate         GETEVENT entry point
                          mcc_event_put       mcc_event_get
                                              return

 Is the communication between the X.25 module and the Access module using 
mcc_event_get/put causing this problem? I read once that it was not the "right"
way to communicate between modules but I can't remember why...

 Regards,

 Serge

> If we simulate the same network events more slowly (!), it works fine (ALARM 

This looks like some kind of overrun in the event manager. I vaguely 
remember that there were problems in this area.

You could try the new Notification FM (in conjunction with the Kernel 
ECO, if you run on VMS) and see if it helps. Look for it in:

	BIKINI::MCC_DISK:[BMS013.*.PATCH]MCC_NOTIFICATION_FM.*

*Robert