Conference azur::mcc

No.  Nor is the map able to automatically enable
rules for the domain you've opened.

The "auto enable" argument on the Create Domain Rule
directive only applies to whether the rule is
enabled as part of the create activity.

    I see the automatic enabling of alarm rules as a nice option especially
    when you have a default domain specified and you bring up the Iconic Map.  
    
    We'll be using DECmcc with the VAXcluster MDF product to monitor the 
    DECbridges, DECcontrators and DECservers in the configuration.  The Iconic 
    Map and the notification window will be started automatically but the user 
    will have to manually start all the alarm rules on startup or after a 
    failure.   For our purposes the startup and monitoring should be as 
    automatic as is possible. 
    
    I could create a process that runs a command procedure enabling all the 
    rules for each domain and leave the FCL running.  This will send all
    the alarms to the Iconic Map but the user won't be able to view the
    STATUS, etc. of each rule from the IC.  Any other problems with this?
    
    Any other ideas?
    
    

I've been using the 'batch job' scheme suggested in the manual and it seems
to work good enough...

Lee

    re. .3
    
    I realize that this is a work around but we can't use this method.
    
    Bill

it's an asset that is basically aimed at running
alarms in a background process.

Not what you're asking for... but I thought I'd mention
it.


	Please note that package descriptions are available both in EADC::EADC
	Notes File and in VTX (keyword ASSETS_EUROPE) with option 10.
	*********************************************************************
	Owning Portfolio	: NETWORKS/COMMUNICATIONS/SYSTEMS
	Notes File 		: CLARID::EUR_NETASSETS
	Technical Contact       : CLARID::SUPPORT
	*********************************************************************
	VAX DETMCC/VMS V1.3

	Creates a detached process running DECmcc and communicating to 
	other processes via mailbox and pseudo devices.	

	This version adds three new features (like the qualifier /[NO]LOG), 
	and corrects 7 problems. For more information, please read the 
	Releases Notes at the end of the VAX DetMCC/VMS User's Guide.

	Package type		: PASS
	Release type 		: Update 
	Part number		: Q2-GJD**-** 
	Distribution		: EADC
	
	Support : Standard ASSETS Support 

	I realize it isn't exactly automatic, but the above command is really
    all they need to know to enable all rules in all domains.

	I suppose a customizable alarms startup script might be useful as well
    (similar to Notification Services).

				  Dave McLure
			   (Alarms FM Developer, etc.)

	I should have been a little more specific as to how the user could
    enable alarms in the Iconic Map by mentioning that the previous enable
    command would currently need to be entered using an auxiliary FCL Window.

	To do this, you would simply start up the iconic map, and then choose
    the "DECmcc Command Line (FCL)" choice from the Applications pulldown menu
    of the main map window.  Once the FCL window is up, you could then enter
    the global domain rule enable command I mentioned:

MCC> enable domain * rule *

	...at which point the rules are all enabled and begin firing.
    Depending upon how large the domain heirarchy is, you might then want
    to shrnk the FCL window to an icon and check on it occasionally to
    see how it's doing.  Smaller domain heirarchies will enable fairly
    quickly depending upon whether your namespace is local or not.

	Don't get me wrong, I agree with the idea that some sort of Alarms
    startup procedure would be nice to have as well.  Some people would even
    like to go a bit further and redesign an entirely new Alarms user interface
    as well.  I'll be sure to add this to the list.

	For the meantime, I would offer this as a possible workaround.

				    -davo