Conference azur::mcc

This question has been asked at least 20 times in this notes file.

You have two MCC processes running:
  o  One in batch mode which is executing the enabled rules
  o  One in interactive mode (FCL or IMPM) doing the Show counter/status

The process which is executing the enabled rules maintains the Counter
and Status attributes -- This is process private data.

The Interactive process (unfortunatly) can not "see" the Counter and
Status attribute data from the other process.

This was a design trade-off for Alarms in anticipation of Distributed
MCC.  Distributed MCC would allow the interactive show directive to call
the detached (batch) process to collect the process private data and
display it.

To the best of my knowledge this restriction will continue for v1.2

(I've created a new Keyword "ALARMS ENABLED RULES" which may help in the
future to find related notes)

Keith Roberts
DECmcc Toolkit Team (Ex-Alarms Team member)

    Does anyone know of a way to enable all domain rules from the IMPM?
                                                   

    No.
    
    I wouldn't bother since it is easy enough to do it from the FCL either
    as an interactive job or in batch. For my system I frequently just
    have a DECterm lying around with the FCL in it and I enable all alarms
    that I care about (could be all) from it.
    
    s/rob

    That is what I do, also.  I like it that way, and that is how I wanted
    to do it for those groups that would be managing/monitoring various
    aspects of the network; however, it is important to be able to see
    ***from the Iconic Map*** what the status of a rule is and how many
    times it has fired (SHOW STATUS & COUNTERS).  The only way this can be
    accomplished is to enable each rule individually ( >>> 5 button clicks
    in 3 windows for each rule <<< ).
    
    My customer plans to use DECmcc along with many other network tools to
    manage their network.  Most groups will care only about using the IMPM
    and will EXPECT to see rule status from that PM, not from FCL.
    
    To eliminate confusion as to whether or not a rule is really ENABLED
    and functioning properly, this capability must be present at a minimum. 
    Better still would be to have all processes determine rule
    status/counters.                                              

RE: .2

>> Does anyone know of a way to enable all domain rules from the IMPM?

I beleive that for v1.2 - the Alarms team has added wildcarding to the
Enable directive.  This would enable all rules of a specified domain.

RE: .4

When Alarms was written, we expected that there would a background process
created for each domain and that distributed MCC would allow data requests
to cross those process boundaries to collect the data.  We do not have
distributed MCC today, and (probably) will not provide such functionality
within Alarms.  We're waiting for distributed MCC.

Keith

For V1.2, the Iconic Map does not support wildcarding of the Enable directive.
Each rule must be enabled individually using the Management Window. The wildcard
functionality was traded off.

Verna

    I understand that everything can't be done at once, but my customers
    have commented that they are "working with an unfinished product".  I
    have shown them ways around it, but they still shake their heads.  What
    a customer perceives is important.  Would it be possible, at least, to
    make it easier to enable alarms with fewer clicks/windows?  
    
    See 578.51

    Of course it is an unfinished product. So is VMS. It is esentially a
    version 1 product too. It will, like any other product, take a few
    revisions to begin to mature.
    
    BTW, if y'all have suggestions about how alarms should work from the
    iconic map, please post em. Could be useful for next release (after
    1.2).
    
    I realize that your customer really wants to see the alarms status on
    the iconic map but can't you convince them to use the FCL to see them?
    Since you have a workstation you can have a DECterm with the FCL at
    the same time as the map and use it for managing alarms for now.
    
    s/rob
    

Please note that Verna's response was related to the IMPM supporting the
wildcard. At last check in V1.2 you would be able to enable domain x rule *
from the FCL to simplify that command procedure of your.s

But will the "with category=  " also be supported while enabling rules??
This allows the user to filter what to turn on or off, simply turning on
ALL rules for a given domain might not be the total solution (at least not
for us).

brad...

    not for now at least. We put a quickie in to make with only
    work on show until we have more time to review some of the side effects
    that have been noticed. Sorry.