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 |
In testing T1.2.7 on a VMS V5.5 system and talking with another collegue regarding DECmcc as it compares to DCM.....an interesting point came up. Can someone tell me if I am simply missing it and it exists or is it not there and if not will it be and when? The it, is the ability to setup an exceptions or command procedure to execute when a notification event fires similarly to that of Alarms? I've not had much experience with DCM, but apparently the way the customer is using it, they take advantage of the ability to send a message to DECtalk or automatically page someone if an event occurs. This would be very nice feature......any plans? Al
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
2836.1 | Why not OCCURS ? | MCDOUG::MCPHERSON | Save a tree: kill an ISO working group. | Thu Apr 23 1992 14:29 | 14 |
>The it, is the ability to setup an exceptions or command procedure to execute >when a notification event fires similarly to that of Alarms? > >I've not had much experience with DCM, but apparently the way the customer >is using it, they take advantage of the ability to send a message to DECtalk >or automatically page someone if an event occurs. You'll need to either use the OCCURS rule format (created esp. for events) or write your own application that 'listens' for specific events and does whatever things you need it to (not very difficult, since you could just use 'callable mcc' but harder than writing rules...) /doug | |||||
2836.2 | FOUR62::LICAUSE | Al Licause (338-5661) | Fri Apr 24 1992 12:10 | 7 | |
Thanks very much.. I'll have to re-read the rules documentation....wasn't aware that the OCCURS format was for notification events. Al |