[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

1438.0. "Iconic Map and Alarms problem" by OFFHK::ALLAIN () Tue Sep 03 1991 18:25

Hi, I've a problem with the Iconic Map and Alarms:

1:
After receiving an alarm, I use Display Selected Alarm operation to see the 
alarm that has been "triggered". I got a window showing all the information.

2:
I DON'T CLICK on OK (that means I keep this window open), and when a 
second alarm comes, I "goto 1" (I display selected alarms), and I see 3 alarms 
in the list: The first one, the first one again, and the second one!!

So, it sounds like the Iconic Map is disturbed when I don't remove the window 
showing the previous alarm before displaying the nex one.

When I simultaneously run the notify commnand from the FCL, I see only 2 alarm
reports. (I don't get the first one duplicated). This is what makes me believe
that the Iconic Map PM may be responsible for this duplication.

Any idea about this? If this is a problem of my code (get/put event), what could
be the reason??



Thanks for any help.

Francois.
T.RTitleUserPersonal
Name
DateLines
1438.1Yes! I've seen that too.TOOK::GUERTINDon't fight fire with flamesWed Sep 04 1991 00:3211
    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.2A nice feeling...OFFHK::ALLAINWed Sep 04 1991 12:0310
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.3More info.OFFHK::ALLAINWed Sep 04 1991 14:358
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.4TOOK::HAOWed Sep 04 1991 16:4817
    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.5I recognize those symptoms too!..KERNEL::MACLEANI CAN and I WILL...But Not today!Sat Sep 07 1991 14:1816
    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.6patch?GOSTE::CALLANDERSat Sep 07 1991 14:552
    by a fix you mean a patch?
    
1438.7fix=patchKERNEL::MACLEANI CAN and I WILL...But Not today!Sun Sep 08 1991 09:371
    yes.
1438.8Multiple notifications from FCLVCSESU::WADEMon Sep 09 1991 15:2960
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.9evl problemGOSTE::CALLANDERFri Nov 08 1991 16:254
    I believe that this has been qared against the dna4 evl already.
    I will check.