[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

3188.0. "Alarm rule in IMPM and FCL" by MQOSWS::F_MONETTE (Montreal Sales Support) Tue Jun 16 1992 09:36

Here is my question:

I'am using DECmcc v1.2 and I realize that if I define for example 50
alarm rules in a .com file and start it, I'am not able to see the 
status of these alarms from the IMPM, it's seems that there is no 
relation between alarm from FCL and IMPM. This is not very useful.

what happen if I have 500 alarm rules to define, do I have to start it
one by one from IMPM ? . I want to be able to see the status from IMPM
of each alarm even if I started them from FCL or batch mode.

It has to be a way to do this or I'll be hard to say to the customer 
that he has to start one by one each alarm every time he has to start
DECmcc


Any help will be appreciate
Thank you
F. Monette
T.RTitleUserPersonal
Name		DateLines
3188.1One at a time isn't necessaryTOOK::HOAGDave Hoag NSM MaintenanceTue Jun 16 1992 14:2617
                                   
      The answer may be to enable all the alarms via IMPM and only use the
    FCL interface to create the alarms. This is easily done if they are all
    in the same domain, and will have to be repeated if you have the rules
    split amongst multiple domains.
    
       Open the domain that has the alarms you want to enable.
    
       FILE->VIEW->RULE
    
       EDIT->SELECT ALL
    
       OPERATIONS->ENABLE...   START ALL
    
    This should enable all the rules in your chosen domain.
    
    - Dave Hoag
3188.2It is easier than that to start rulesTOOK::A_MOORETue Jun 16 1992 14:4016
It is easier than that to start rules, but maybe not apparent.  
It can be done with mouse clicks.

 1. 	Run the fcl command procedure to create domain foo rule bar etc.
 
 2.	Bring up the domain foo, and select Rule View on mb2 menu.

 3. 	Pull down edit to select all rules

 4.	Pull down operations to enable all the rules with a start all button on
	the management window that pops up.


Al Moore

.
3188.3why instead of how toTOOK::CALLANDERMCC = My Constant CompanionWed Jul 15 1992 12:5119
    now that you know how to start them all from the map, the reason
    why you need to:
    
    (on VMS) the alarms that are enabled run within the process where
    the enable command was entered. This process does NOT share information
    with other users/processes as to the status of the rules it is running.
    That is why you do not see the status across the system/multiple
    processes.  As to the rule fired events, the reason you DO see
    those is because the event manager is a system wide service and
    delivers to any mcc process requesting the events. On VMS this 
    can be real confusing. Please note that there was an assets tool
    (in Europe) the was written to alleviate the user visible problems
    in the paradigm. The tool is called VAX DETMCC/VMS and allows
    you to strat an mcc process detached for runing your rules and
    for reconnecting to the process to view the current status of
    those rules.
    
    jill