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 |
Hello, I created an alarm via a command procedure. As Alarmprocedure I call the file MCC_COMMON:MCC_ALARMS_PAGER_ALARM.COM. With this we can send alarm Text to a pager (with a pager you can receive messages in our hole country). If I create my alarm rule I say: CREATE MCC 0 ALARM RULE xxxx ,- PROCEDURE = " MCC_COMMON:MCC_ALARMS_PAGER_ALARM",- and so on But after If I do an show mcc 0 alarm rule xxxx , I see PROCEDURE = MCC_COMMON:MCC_ALARMS_PAGER_ALARM,5, you see, with file version number. And now I wonder, do you realy want to do that or is it a bug? Because if you edit your Alarmprocedure during the alarm execution, the alarm failes. Roland
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
1284.1 | precaution .not. bug | TOOK::CALLANDER | Jill Callander DTN 226-5316 | Thu Jul 25 1991 14:42 | 9 |
no this was done as a precautionary measure, so that someone doesn't play with your command procedure and change the expected results. This was actually recommended during one of our "security" reviews. If you really need to change it, and you wrote/own it, you should have sufficient privs to create a new version and then deleted the old, renaming the new to the old version number (just don't do it while the file is in use -- an alarm triggering). | |||||
1284.2 | o.k. it's a feature | ZUR01::SCHNEIDERR | Fri Jul 26 1991 06:52 | 7 | |
Jill, O.K. if you say thats a feature, it must be one. As you wrote, it is possible to change the alarmprocedure and as we all know security features doesn't make it more easy to do some things. Thanks and regards Roland |