| 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 |
I have created an alarm that triggers on the occurance of a decnet event on a node in domain A. Starting notification services from the map window of domain A, a notify request is automatically created for alarms in domain A. When I enable the alarm from the iconic interface, I receive one notification for every occurance of the event. Fine, this is what I expected. If the same alarm is enabled by other processes, I receive ONE NOTIFICATION PER ENABLING PROCESS for every occurance of the event. Not very smart on a multiuser system. I would suggest a redesign to display only one notification per occurance of the event. Erik B. Christensen.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5949.1 | This is normal behaviour! | BIKINI::KRAUSE | European NewProductEngineer for MCC | Tue Apr 19 1994 06:09 | 14 |
You do NOT need to enable the same alarm rule more than once on a system. Notification will happen on all user interfaces on the same system with the alarm rule running in only one process (e.g. batch). When you enable the rule in two processes, the rule will be executed independently in both processes. Each rule-instance will eventually fire and generate an individual event. Therefore you see two notifications. The two rules don't know of each other! Don't get confused by the rule status. It shows 'enabled' ONLY for the process that actually runs the rule. But, as stated above, this does not affect notification. *Robert | |||||