| 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 |
Hi,
I have a question regarding static vs dynamic domains. My understanding
was that static domains did not propagate notifications to superior
domains, but nevertheless could handle receive notifications.
If I have the following :
Domain root
!
+----------------------------+
! !
Domain "d_static" domain "d_dynamic"
! !
+--------------+ +--------------+
! ! ! !
entity X rule stat_x entity y rule dyn_y
If rule dyn_y fires, I expect entity y and domain d_dynamic icons to
change color to reflect the severity of the rule and this is what
happens.
If rule stat_x fires, I expected entity x icon to change color, but not
domain d_static. Is this the expected behaviour ? If so, I must have
misse something because in practice, neither changes color, yet
notifications arrive in the notifications services window.
Can anyone help ?
Thanks, Philippe.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4928.1 | Anyone there ? Please answer me.... | EVTIS9::ROGGEBAND | While my guitar gently weeps | Mon May 03 1993 09:59 | 1 |
| 4928.3 | Reposting .2 with different word-wrapping | TNPUBS::JONG | Steve | Wed May 05 1993 14:02 | 38 |
[I was interested in this reply, but I had trouble reading it. I have
taken the liberty of reposting it with a more appropriate format--sfj]
Philippe,
I would expect to see the results that you saw in the map window.
I'll try to explain the reasons why, but I also have questions about
what you are doing in the notification services window.
First, two points. (1) A 'domain' is not static or dynamic, a 'domain
member' can be a static or dynamic member of another domain. (2)
Notification is established for the top level domain which you opened
in the map window. So, notifications are established for domain "root"
and all nested dynamic subdomains.
Since domain "d_static" is a static member of the domain "root",
notification is not established for domain "d_static". Even if you
know that there are rules firing for domain "d_static", no color
changes will occur. The notification structures are not built for
domain "d_static" (starting from domain "root").
If you were to create a new map window and open domain "d_static" as
the top level domain, and enable notification for domain "d_static" and
all dynamic subdomains, you would then see color changes on entity "X"
in domain "d_static in the new map window.
So, notification is specific to the top level domain where you started.
Static domain members simply block all color changes below that point.
Static domain members were intended to be used mainly for ease of
navigation.
I don't understand your statement "yet notifications arrive in the
notification services window". When I duplicated the scenario above, I
saw occurrences in the notification services window **only** after I
opened domain "d_static" as the top level domain in a new map window.
If that doesn't match what you've seen, let me know.
-Dave
| |||||
| 4928.4 | please post notify commands | GOSTE::CALLANDER | Tue May 11 1993 13:41 | 4 | |
for a clearer understanding, as Steve has requested, a copy of the
notify commands you are running would also make it clearer as to
what is happening. Because to see notification in both the Y and
the X branches at least 2 seperate notify commands are required.
| |||||