[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

2432.0. "help with time parameters or alarm rule" by NSCRUE::KEANE (U.S. NIS Service Engineering and Delivery) Wed Feb 26 1992 17:13


   I am looking for some assistance on the proper way to specify some time
parameters for an alarm rule.

   I am looking for the rule to only poll once a day, and I am planning that
the rules will be enabled via batch and will be restarted at midnight each
night.

  If I am looking for the rule to start at noon, should I set it up with
 
start = +12:00

  I assume that this means to start 12 hours after enabling the rule, but when
I tried this before using +8:30 I recieved alarms at 8 and 1/2 hours later and
at 8:30 the next morning.

  Also, what would be appropriate for the "until" parameter in this case?

 Thanks,
 Scott
T.RTitleUserPersonal
Name		DateLines
2432.1one optionICS::WOODCOCKWed Feb 26 1992 18:2138
>   I am looking for the rule to only poll once a day, and I am planning that
> the rules will be enabled via batch and will be restarted at midnight each
> night.

>  If I am looking for the rule to start at noon, should I set it up with
 
>  start = +12:00

Hi Scott,

If you are only looking to poll once a day, and you are going to resubmit
each day, then why not resubmit when you want it to poll and forget the
time qualifier.

Example: 

Rule(s) expressions look like:

expression=(node4 xxx Attribute = <whatever>)  <-- no time qualifier

Command procedure looks like:

$! RULES.COM
$!
$! automatically resubmit the procedure for tomorrow at noon
$!
$ submit/after="TOMORROW +12:00" rules.com  ! <--time syntax is probably not 
$!                                               right but close
$!
$ mana/enter
enable domain xxx rule RULE_1
enable domain xxx rule RULE_2
sp wait 0:1:0                               ! <--give the rules time to fire
exit
$ exit

best regards,
brad...
2432.2NSCRUE::KEANEU.S. NIS Service Engineering and DeliveryWed Feb 26 1992 19:188
Hi Brad,

   The part I left out is that I need this rule to run  in the same process 
context with some other rules and the other rules will be active all the time.

Thanks for the reply.

Scott
2432.3take out the "+"ICS::WOODCOCKFri Feb 28 1992 14:3417
Hi Scott,

I just tried a test rule with an expression like:

node4 bbpk04 circ syn-0 substate <> none,at start 14:25

This seemed to work ok as a quick test. After enabling the rule it
waited until 14:25 before executing. The only quirk I saw is that the
rules current severity was critical before it executed instead of clear.
This shouldn't give you a problem today but the ALARMS team may want to
take note of this.

So try taking out the + and let it run for awhile to see if it works for
you.

best regards,
brad...
2432.4NSCRUE::KEANEU.S. NIS Service Engineering and DeliveryFri Feb 28 1992 15:0111

  Brad,

    Thanks for the reply. I ended up with something similar. It turned out that
I was making the rule more complicated than it needed to be. It's amazing
what happens when you drop something like this and then go back to it after a 
day. Sheds a whole new light on it.

  Thanks again,
  Scott