[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

1517.0. "notification and alarms rules problem" by COMICS::MISTRY () Tue Sep 17 1991 14:27

I have a customer with the following problem..

He has set up 6 alarms (via command file) and he uses the FCL mode to enable
and disable the alarms. He then brings up the iconic map with notification
automatically enabled.

If one of the alarms fires then everything is fine, and this is also true if
none of the alarm rules fire. Occasionally however, with no alarms firing up
the iconic map displays the message :

unexpected notification in domain and disables notification.

The customer is running the latest versions of mcc and has the alarms patches.
This problem is intermittant and the customer doesn't appear to have any resource
problems.

Are there any known problems like this and if not is there a logical i can set
which dump the information between the iconic map and the kernel and/or the
interface between the notification fm and the kernel.

Bipin.

T.RTitleUserPersonal
Name
DateLines
1517.1More info...WELCLU::CRIDDLEGraham Criddle, DS Tech Consultant, 853-4015Mon Sep 23 1991 14:5636
    Hi,
    Having originally raised this with Bipin, I have been able to find a
    way to reproduce this 50% (or so) of the time.
    
    This is a VAX 9000 running VMS 5.4-1A
    
    I have an alarm (severity level critical) which always satisifies it's
    test criteria. (It is testing a nodes inactivity timer = 60 which is
    true)
    
    I have a command procedure which does the following:
    
    $ loop:
    $ man/ent
    enab mcc 0 alarm rule critical, in domain uk.hinckley.domain
    show mcc 0 alarms rule critical, in domain uk.hinckley.domain, -
            at start = (+00:00:04)
    exit
    $ goto loop
    
    If I start this procedure running, and then start the IMPM from a
    Fileview window, 50% of the time notifications is disable on the domain
    uk.hinckley.domain with the window popping up as Bipin described in .0
    
    The domain uk.hinckley.domain is a dynamic subdomain of the domain I open
    when starting MCC.
    
    I assume that there is some timing window at IMPM startup during which
    it has enabled notification but is not ready to receive them, or some
    such thing??
    
    Any thoughts/comments?
    
    Rgds,
    Graham
    
1517.2known problemTOOK::HAOMon Sep 23 1991 15:2412
    Graham,
    
    You are correct.  The V1.1 IMPM had problems when alarms are enabled
    before the IMPM is fully up.  This is because the notification and map
    window code access some of the same structures, and those structures
    may not be fully set up by the map code before notification tries to
    use them.
    
    This has been fixed for V1.2.
    
    Christine
    
1517.3Thanks for the update.WELCLU::CRIDDLEGraham Criddle, DS Tech Consultant, 853-4015Tue Sep 24 1991 08:1118
    Hi, Christine...
    
    Many thanks for the reply...
    Is it possible that the same problem occurs some time after the map has
    been setup and in use for some time?
    
    Why I ask is that I am getting exactly the same error condition
    occuring at random times (seemingly) during normal operation. However,
    it was possible to provide a reproducible scenario for the startup
    problem but not for the case where it occurs in 'normal' operation.
    
    If it is likely that I am seeing the same symptoms for a different
    cause, can you think of anyway in which I can gain sufficient
    information to provide analysis of this aspect of the problem?
    
    Rgds,
    Graham
    
1517.4rare but possibleTOOK::HAOTue Sep 24 1991 17:1415
    Another situation where the problem could come up would be when you're
    double-clicking into something that takes a long time, and notification
    was received.  It really depends on the timing.  Most of the time, the
    above will work without problems; however, if the notification was
    received at the time the map code is still building the data structures
    for the new view, the same problems will appear.
    
    So I guess the answer is yes, it may happen even after the IMPM has
    been fully up.  Since the real problem is that we do not have locks on
    these data structures, any situation you can get into where map code
    is modifying data structures that notification code happens to want to
    look at, will be a problem.
    
    Christine
    
1517.5A note about your script...TOOK::ORENSTEINTue Sep 24 1991 17:257
    
    I suggest that you add a DISABLE RULE * to your command procedure.
    The EXIT will abort the rules running and this may leave the event
    manager in a funny state.  The DISABLE will properly clean things
    up.  
    
    aud...
1517.6Many thanks...WELCLU::CRIDDLEGraham Criddle, DS Tech Consultant, 853-4015Wed Sep 25 1991 11:5715
    re .4 
    Thanks, Christine.
    The scenario you describe seems to tie in with what I have seen. I
    guess we wait for 1.2
    
    re .5
    Hi, Aud.
    Thanks for the point about DISABLE. In the procedure I use for
    prodcution work I do have the appropriate DISABLE commands, just did
    not include it in this test procedure.
    
    Thanks to all...
    
    Rgds,
    Graham