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 |
Good day, I'm trying to do the following: From a local/remote nodes, I use MCC_EVC_SEND to send events to a data collector. Notification of these events work beautifully (except for an occasional "Network partner exited" error... that's another story...). Now, what I need is to trigger a command procedure from these events collected by the data collector. I read earlier notes implying that I need to create an OCCURS rule to detect the events. So, I did an OCCURS rule with: EXPRESSION = (occurs (Collector * Any Event)) which fires as expected. Here's my problem: The OCCURS alarm rule doesn't give me: 1. Easily identified target entity (it's always = Collector). 2. Original severity (the one displayed in the notification window) Notification *does* give me the info I need. Is there any way that I can trigger command procedures from notification? Or can I make the alarms "smarter" somehow? I know I could stuff all the info I need in the text field of MCC_EVC_SEND, but is there a better way? Thanks, Ed
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
3784.1 | try file 'p8 | CTHQ::WOODCOCK | Tue Sep 22 1992 16:45 | 21 | |
Hi Ed, The info you are looking for (I think) isn't directly in any symbols passed into the procedure. It is most likely in the tmp file stored with the alarm. The tmp file name is passed as p8. So as a test fire the alarm with the following procedure: $ show sym p1 . . . . . $ show sym p8 $ type 'p8 $ exit Hopefully the info you require is in the 'p8 file. best regards, brad... |