| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3436.1 | no wilde cards for change-of | HERON::PATEL_A | LoLo-AQIC-I82Q-B4IP, - LMF | Mon Jul 27 1992 12:24 | 6 |
| my 2cents Timo
>1 change-of rule does not support global or child entities
rules with global wild cards and statistc attributes not allowed
Amrit
|
| 3436.2 | documentation error? | CLARID::HOFSTEE | Take a RISC, buy a VAX | Tue Jul 28 1992 05:00 | 15 |
|
> >1 change-of rule does not support global or child entities
> rules with global wild cards and statistc attributes not allowed
If this is true, than there is a mistake in the documentation, since it is
stated in the alarms/notification doc on page 5-12 that deals with the
change_of rule :'Variable definitions (that is, entity , attribute,value,value)
are the same as those specified for the comparison alarm expression. You can
also employ the wildcard designation (*)'
And what about the other issues?
Com'on Amrit, you should know now that you followed the training :):)
Timo
|
| 3436.3 | see rel notes sec 4.8.3 for q's 1 & 2 | HERON::PATEL_A | LoLo-AQIC-I82Q-B4IP, - LMF | Tue Jul 28 1992 06:19 | 14 |
|
If only a one week training on such a product (mega yeas dev) made us
all into instant gurus ;-) ...
for 1 and 2 see rel notes
besides I am reading from the release notes section 4.8.3 page 4-21 -
the only training you need for that is the "speed reading"
yr Q 3 is more tricky... leave this to those really in the know
Amrit
|
| 3436.4 | Change-of does not support wildcards in the ENTITY SPECIFICATION | MOLAR::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Tue Jul 28 1992 08:58 | 38 |
| RE: .2
From Alarms & Notifications v1.2 Manual (bookreader):
----------------------------------------------------------
Change Of Rule: Detecting Changes in an Attributes' Value
:
:
EXPRESSION = (CHANGE_OF( entity_attribute,value_1,value_2 ),schedule_time)
Variable definitions (that is, entity, attribute, and value) are the same
as those specified for the comparison alarm expression. You can
also employ the wildcard designation (*).
----------------------------------------------------------
I'm not sure what this is trying to say, but v1.2 Alarms does NOT support
a global or child wildcard in the entity specification for the Change-Of
Function. It is our hope to get this functionality into the next release
of Alarms.
The *only* wildcarding allowed in the Change-Of function is the the second
and third arguments: value_1 and value_2 ...
Value_1 Value_2 Description
------- ------- -----------------------------
value value Change from Value_1 to Value_2
value * Change from Value_1 to anything
* value Change from anything to Value_2
* * Change from anything to anything
For example, if you used wildcards for both value_1 and value_2, this
tells alarms "if the entity-attribute ever changes value, let me know"
/keith
|
| 3436.5 | when are they expanded? | CLARID::HOFSTEE | Take a RISC, buy a VAX | Wed Jul 29 1992 05:42 | 18 |
|
thanks for the pointers. The release notes indeed clear up things. It seems
to come down on:
'You can use wildcards in ALL rule types for ALL global entities and ALL
childentities, EXCEPT for the change_of rule type and the expression rule
type in combination with a statistic attribute'
Is that correct?
leaves the last question: When are the wildcards translated into real
global/child entities? On every evaluation of the rule in a domain?
When the rule is created?
Thanks
Timo
|
| 3436.6 | Global Wildcards expanded during *each* Rule Evaluation | MOLAR::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Wed Jul 29 1992 12:51 | 28 |
| RE: .5
Timo,
> 'You can use wildcards in ALL rule types for ALL global entities and ALL
> childentities, EXCEPT for the change_of rule type and the expression rule
> type in combination with a statistic attribute'
>
> Is that correct?
Yes - this is correct
> leaves the last question: When are the wildcards translated into real
> global/child entities? On every evaluation of the rule in a domain?
> When the rule is created?
Alarms expands a Global Wildcard for *each* evaluation by calling the
Domain FM with "show domain <x> member *, select list = <global-entity>
So Alarms will pick up changes made to the Domain without the need to
disable/enable the rule.
Note: The Domain "select list" construct is only available from the
programming interface; that is, not from the FCL or Iconic-map.
/keith
|
| 3436.7 | and what about child entities | CLARID::HOFSTEE | Take a RISC, buy a VAX | Thu Jul 30 1992 06:12 | 14 |
|
Just one more question:
The previous replies talked about GLOBAL wildcard entities. What about child
entities?
IF I specify : NODE4 ABC LINE *,
will this be expanded in the same way as explained in the previous reply, eg.
every time the rule is evaluated?
Thanks
Timo
|
| 3436.8 | The DECnet AM will expand the Line wildcard | MOLAR::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Thu Jul 30 1992 10:55 | 14 |
|
Timo,
> IF I specify : NODE4 ABC LINE *,
>
> will this be expanded in the same way as explained in the previous
> reply, eg. every time the rule is evaluated?
The Alarms FM does not expand the child wildcard - this will be done
by the Management Module which alarms calls; in your case the DECnet
Line child entity ... and I 'assume' that the MM will expand the child
entity for each evaluation
/keith
|