[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

2339.0. "AUTO ENABLE ALARMS NOT WORKING" by LARVAE::AITKINS_T () Thu Feb 13 1992 07:19

    Hi I have a problemm with alarms.
    
    I have followed the documentation and set up a batch job to enable all
    of my DECmcc alarms and then issue a command to run in the year 2000 so
    the process remains active. My problem is the results are inconsistant.
    somtimes all works fine, other times only alarms on certain entities
    are generated i.e. mail messages arive but the map does not always
    change colour.
    
    1) does the map have to be activated after the bach job has run or will
    an existing process pick up the alarms.
    
    2) If the map is run after the batch job do all of the alarms have to
    be enabled first.
    
    3) Has anyone else had these problems.
    
    I'm running DECmcc V1.1 on a Vaxstation 3100 M76 with !^mb of memory.
    
    
    			Thanks,
    
    
    					TERRY.
T.RTitleUserPersonal
Name
DateLines
2339.1TOOK::R_SPENCENets don't fail me now...Thu Feb 13 1992 13:0111
    I believe that in V1.1 there WAS a timing window when starting both
    the IMPM (enableing notification) and enabling the alarms where things
    sometime didn't work.
    
    ?? Does anyone else remember more detail?
    
    I think that in the case of all alarms enabled, then enableing
    notification , and also the case of having notification enabled and
    then enabling the alarms both work ok.
    
    s/rob
2339.2notify IMPM and batch alarms was a probICS::WOODCOCKSat Feb 15 1992 21:419
>    ?? Does anyone else remember more detail?
    
I remember I couldn't start the map (with notify auto enabled) and a batch
job starting alarms at the same time without some ugly reactions at times. I
ended up with wait statements to allow for pauses so the processes wouldn't
bump into each other.

regards,
brad...
2339.3locking problem in impm alarms structureTOOK::CALLANDERMCC = My Constant CompanionMon Mar 02 1992 12:313
    yup, it was a locking problem that required a rewrite of a major
    section of code, so no batch was doable. sorry.