[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

3850.0. "Notification requests disappear on startup" by MEOC02::GROGAN (GEE GEE) Thu Oct 01 1992 21:21

Hi,
  I've started teaching DECmcc V1.2 here in SPR and I've run across
a problem with notification requests.

I am running V5.5-1 and the SSB version 1.2 DECmcc BMS. 

We created a number of notify requests, then saved them into a file.
Using the customize option, this file is called at startup. The second request 
in the file checks for any event on a node4 nzomcc entity.
We go through and area router on the Lan to this node, which is also an area
router.

After startup of the notification window, we checked the notification requests,
only to find the first request for the domain is enabled, but the second request
is disabled with an error. The remote node was down at the time, with a 
circuit in synchronizing substate. This wasn't the main concern, the real issue
was that all the subsequent request in the startup file didn't appear at all, 
when we displayed the requests via the iconic map.

Yet if we use the include file option from the iconic map, the second request 
still falls over, but this time all the subsequent rules are visible and 
enabled.

The error message for the request that gets disabled is, 
"no matches found for the entities or rules requested"

The request enables without error if the node is available.

Could someone please answer a few  question I have arising from this 
discovery.

Why does the request not get enabled, does it have to do some checks at startup
time ?

Why does the file bomb out at startup and not when using the include file
option? 

How do I stop my startup notify request file from terminating on an error
and killing of the rest of the requests?

If I didn't go to add another request, I wouldn't have noticed that the others
had disappeared, is there some way of bringing this to the users attention?

Thanks in advance!
T.RTitleUserPersonal
Name
DateLines
3850.1found solution to one problem!MEOC02::GROGANGEE GEEThu Oct 01 1992 22:2016
    Humble pie time!
    
    Sorry, but I did some further checking and my students were running two
    different files. One small one at startup, with two requests and they
    used a larger one at the include option.
    
    So thats why they appeared to disappear at startup and yet work when
    they used the iconic map iclude option.
    
    I've still got the question of why the request bombs out when you start
    it up? What actually happens when you enable the request, does it have
    to check for the entities existence?
    
    Thanks again and sorry for the mistake!
    
    
3850.2more informationMCC1::DITMARSPeteTue Oct 06 1992 13:598
>    I've still got the question of why the request bombs out when you start
>    it up? What actually happens when you enable the request, does it have
>    to check for the entities existence?

Yes, there are checks done at startup time.

Please post the exact notify request and error message you're seeing
if you would like a more informative answer.