Conference azur::mcc

5026.0. "rules not fired 1.2->1.3 MCC-BMS" by BLG03::ROSSI () Mon May 10 1993 07:25

    Hi,
    	the context is:
    
    			- vax 3100/90 80Mbyte Ram 
    			- vaxstation 4000 VLC
    			- VMS 5.5-2
    			- MCC-BMS 1.3
    			- About 150 notify requests
    			- About 100 rules
    			- About 100 retargeting definitions
    
    Using MCC-BMS version 1.2 we had some occurs rule define in the "main"
    domain (the root domain).
    That domain contains 10 subdomains.
    One of that occurs rules, for example, is defined in this way:
    	- entity: node4 * circuit *    event: circuit up
    This rule is defined in the main domain.
    
    With MCC-BMS version 1.2, when a "circuit up" is coming from a subdomain
    (a node in a subdomain) the rule is fired. 
    
    After the upgrade from 1.2 to 1.3, the rule is not fired. 
    
    Now, with 1.3, is necessary (it seems) to define the same rules in all
    subdomains. In this way the number of rules is multiplied by 10 (10
    subdomains).
    
    Questions:
    
    	- is it possible to have a general rule define once that fires when
    	  an event is coming from a subdomain (as in 1.2) ?
    
    	- Why this change from 1.2 to 1.3 MCC-BMS ?
    
    	- The behaviour of 1.2 was a bug ?
    
    
    Thank in advance
    
    bye
    
    Giuseppe Rossi
    
    
       

I had the same problem (see note 4538.*).

It seems the ability to have a wildcard rule in the top level domain
was a BUG instead of a FEATURE, and it got corrected in V1.3. Now, you
must have rules in each domain. This has been a catastrophe change for me
(see note 4576.*).

Lee

    Thanks for the answer.
    
    	this is a catastrophe!!!
    
    	I think that We may ask about a new feature.... (the previous bug).
    
    	Bye
    
    Giuseppe