T.R | Title | User | Personal Name | Date | Lines |
---|
1438.1 | Yes! I've seen that too. | TOOK::GUERTIN | Don't fight fire with flames | Tue Sep 03 1991 22:32 | 11 |
| I've seen this before when I have had the same notification enabled
twice. Once from the iconic map, and again from FCL. Apparently,
notifications are system-wide (? - I seem to recall they post events to
the Event Manager). This seems to result in the exact same
notification event being picked up twice. It happened to me last
Friday, so this just an educated guess. Could you be doing
notifications from FCL or another Iconic Map? I found the behavior
confusing, since it looked like two notifications at FCL. Then when
I looked closely at the text, I noticed that they were both identical.
-Matt.
|
1438.2 | A nice feeling... | OFFHK::ALLAIN | | Wed Sep 04 1991 10:03 | 10 |
| Hi Matt,
I'm not completly sure, but I believe that it did happen to me with just 1
notification running. I'll check it again just to make sure, and I'll let you
know.
(It's nice to know that someone already had the same problem, I feel better...)
Francois.
|
1438.3 | More info. | OFFHK::ALLAIN | | Wed Sep 04 1991 12:35 | 8 |
| More info:
If I don't clik on OK in the Current Alarms window before receiving the next
one, and displaying it, then I can't get rid of that window anymore!!
That sounds more like a IconicMap problem than like a Alarms problem, doesn't it?
Francois
|
1438.4 | | TOOK::HAO | | Wed Sep 04 1991 14:48 | 17 |
| Francois,
Yes, there was a bug in the Iconic Map regarding the Display Alarms
menu items. There is only supposed to be one DisplayAlarms window
up onscreen at any time. Therefore, we dim out the the menu items
when the DisplayAlarms window is up. Unfortunately, there was one
spot in the code that we missed dimming the menu items. One of the
symptoms that I've seen is that you can't get rid of the window
anymore. The duplicate alarm info MAY be a symptom too. I'm not
sure, but it seems likely, looking at the way the code is written.
I wish I can double-check the duplicate alarm info for you, but I'm
not working out of the Littleton office anymore. And my workstation
is not set up yet.
Christine
|
1438.5 | I recognize those symptoms too!.. | KERNEL::MACLEAN | I CAN and I WILL...But Not today! | Sat Sep 07 1991 12:18 | 16 |
| Hi!,
I have a customer who is also currently seeing the behaviour with
Notification arriving twice and also the problem with one Display
alarms Window remaining when you have had 2 active at one time.
He is sure that the Notification is only enabled from the Map and
not from both the Map & FCL.!
Is it likely that a fix will be produced to workaround the Display
Alarms window problem???
Regards,
Sandie..........
|
1438.6 | patch? | GOSTE::CALLANDER | | Sat Sep 07 1991 12:55 | 2 |
| by a fix you mean a patch?
|
1438.7 | fix=patch | KERNEL::MACLEAN | I CAN and I WILL...But Not today! | Sun Sep 08 1991 07:37 | 1 |
| yes.
|
1438.8 | Multiple notifications from FCL | VCSESU::WADE | | Mon Sep 09 1991 13:29 | 60 |
|
I wonder if this FCL problem is related.
From the documentation, BMS pg. 2-16, "A notification directive runs
continuously, ... until ... you exit the current DECmcc session."
I receive multiple notifications if I start a notification directive in
another session after I've left a prior session without terminating the
notification directive.
*** SESSION 1 ***
$ man/ent
notify domain work_stations entity list = (node4 comms remote node comms),event = (counters zeroed)
!%MCC-S-NOTIFSTART, Notify request 1 started
!
zero node4 comms
!
!Node4 63.367
!AT 9-SEP-1991 11:28:13
!
!Zeroing of Counters completed successfully.
!%%%%%%%%%%%%%% Event, 9-SEP-1991 11:28:14 %%%%%%%%%%%%%%
!Domain: COMMS2_NS:.work_stations Severity: N/A
!Entity: Node4 63.367 Remote Node 63.367
!Remote Node counters
!
exit
*** SESSION 2 ***
$ man/ent
notify domain work_stations entity list = (node4 comms remote node comms),event = (counters zeroed)
!%MCC-S-NOTIFSTART, Notify request 1 started
!
zero node4 comms
!
!Node4 63.367
!AT 9-SEP-1991 11:30:47
!
!Zeroing of Counters completed successfully.
!%%%%%%%%%%%%%% Event, 9-SEP-1991 11:30:47 %%%%%%%%%%%%%%
!Domain: COMMS2_NS:.work_stations Severity: N/A
!Entity: Node4 63.367 Remote Node 63.367
!Remote Node counters
!%%%%%%%%%%%%%% Event, 9-SEP-1991 11:30:47 %%%%%%%%%%%%%%
!Domain: COMMS2_NS:.work_stations Severity: N/A
!Entity: Node4 63.367 Remote Node 63.367
!Remote Node counters
!
exit
!
If I kill the MCC_DNA4_EVL process and restart it, everything is fine.
|
1438.9 | evl problem | GOSTE::CALLANDER | | Fri Nov 08 1991 14:25 | 4 |
| I believe that this has been qared against the dna4 evl already.
I will check.
|