| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2199.1 | comma needed in parameter | ICS::WOODCOCK | | Mon Jan 27 1992 13:37 | 7 |
| >> PARAMETER="EMAWIZ::T_MILTON T_MILTON", -
Shouldn't there be a comma between EMAWIZ::T_MILTON and T_MILTON in the
parameter or is this a typo in the note??
best regards,
brad...
|
| 2199.2 | Not default behaviour | TOOK::ORENSTEIN | | Thu Jan 30 1992 13:22 | 12 |
| .1 Yes, there should be a comma, but this is not the problem the
author is referring to.
.0 The reason you are not notified when the rule is created is that
Notification picks up events that are NOTIFICATION EVENT. The
event generated when a rule is created is a CONFIGURATION EVENT.
You can ask the Notification Services to pick up this event, but
it is not part of its default behaviour.
aud...
|
| 2199.3 | Problems with RULE CREATED alarms rule
| CX3PT2::EMAWIZ::T_MILTON | | Mon Feb 03 1992 12:23 | 41 |
|
> .0 The reason you are not notified when the rule is created is that
> Notification picks up events that are NOTIFICATION EVENT. The
> event generated when a rule is created is a CONFIGURATION EVENT.
>
> You can ask the Notification Services to pick up this event, but
> it is not part of its default behaviour.
>
How do I get Notification Services to pick up Configuration Events?
I did some more testing and found some inconsistent results with
the above response:
If I setup the following rule:
CREATE MCC 0 ALARMS RULE TEST -
PERCEIVED SEVERITY=CRITICAL, -
EXPRESSION=(OCCURS (MCC 0 ALARMS RULE * RULE CREATED )), -
PROCEDURE=MCC_COMMON:MCC_ALARMS_MAIL_ALARM.COM, -
EXCEPTION HANDLER=MCC_COMMON:MCC_ALARMS_MAIL_EXCEPTION.COM, -
CATEGORY="ALARMS RULE HAS BEEN CREATED", -
DESCRIPTION="Rule to test if another alarms rule has been created", -
QUEUE="SYS$BATCH", -
PARAMETER="EMAWIZ::T_MILTON, T_MILTON"
Notice that I leave out domains entirely and chose notificication
to be delivered via mail, then I do get notified of the creation
of an alarms rule.
Is this the correct behavior?
Ted.
|
| 2199.4 | config events on domain rules | TOOK::CALLANDER | MCC = My Constant Companion | Tue Feb 04 1992 16:49 | 43 |
|
to get the configuration alarms on rules in the EFT kit...well
it's broken. Sorry about that, we didn't find out until too late.
The way it will work is:
MCC> notify domain jill events=(any config event), entit list=(domain
jill rule *)
%MCC-S-NOTIFSTART, Notify request 2 started
MCC> create domain jill rule jill2 exp=(node4 goste state=on)
Domain KISHKA_NS:.jill Rule jill2
AT 4-FEB-1992 16:48:05
Rule created and enabled successfully.
MCC>
%%%%%%%%%%%%%% Event, 4-FEB-1992 16:48:08 %%%%%%%%%%%%%% [2]
Domain: KISHKA_NS:.jill Severity:
Indeterminate
Notification Entity: Domain KISHKA_NS:.jill Rule jill2
Event Source: Domain KISHKA_NS:.jill Rule jill2
Event: Rule Created
Expression = (node4 goste state=on)
MCC>
%%%%%%%%%%%%%% Event, 4-FEB-1992 16:48:12 %%%%%%%%%%%%%% [2]
Domain: KISHKA_NS:.jill Severity:
Indeterminate
Notification Entity: Domain KISHKA_NS:.jill Rule jill2
Event Source: Domain KISHKA_NS:.jill Rule jill2
Event: Rule Enabled
Expression = (node4 goste state=on)
MCC> terminate notify 2
MCC>
%MCC-S-NOTIFTERM, notify request 2 terminated by user request
MCC>
|