Conference azur::mcc

 Make sure that the alarm rule has the full registered entity name. For instance
if using the local MIR, preface your entity with local_ns:. and see if that
make a difference.

 Scott

    Well I tried to include the full path for the entity and I came up
    with the same problem.  When I included the domain in the entity, like:
    
    node4 NAME_NS:.domain.node
    
    I got a an exception mail message stating:
    
    Exception:   Software logic error detected
                %MCC-S-SPECIALIZED_EXC, success with management module-specific
                 exception reply
    
    
    When I just added the name space to the entity like:
    
    node4 NAME_NS:.node
    
    It worked like before, sending me mail and NOT notifying the map or
    notification box.
    
    What else to look for????
    

    most likely your problem has to do with the way you created the 
    rule.
    
    Did you happen to use a command like:
    
    	create mcc 0 alarm rule xxx express=(<expression>)
    
    instead of:
    
    	create domain yyy rule xxx express=(<expression>)
    			-or-
    	create mcc 0 alarm rule xxx express=(<expression>), in domain yyy
    
    without the domain information notification will never see the rule
    fire using the default notify command issued from the map. A quick
    way to test this out is to put the mcc entity on your map and see
    if mcc turns a color (alarm and rule are child entities of mcc in
    the first command specificied above).
    
    jill
    

    I created the rule from the map interface via the toolbox.  Is there
    some restrictions there??
    
    

    Well I tried to do it from the FCL and it still does not work.  When
    I show the status of the rule, it shows that it fired several times,
    but NO notification anywhere on the map or in the notification window.
    
    What is wrong with this picture???

    Can anyone help out here?  If not, a pointer to someone who can is
    much appreciated.
    
    Bill

From the Iconic Map: 

       When you do a "Rule View" of the domain, what do you see when you show
       the STATUS and RULE ATTRIBUTES about your rule?

       Check that Notfication is turned on for the domain by going to the
       "File" pull-down menu and pulling down and right to the  
       "Notify Domain =>" option.  Which one is greyed out: "Enable" or
       "Disable" ?

       You may have already answered this in earlier replies, but just in case:
       What version of DECmcc? What platform (VMS or Ultrix?)

       Can you post the EXACT rule here ?

       ./doug

and one more thing:

When you being up the Notifcation Window (from the Application Menu), hit the
"Notify Requests" button.  

Exactly what do you see? 

/doug

    VMS 5.4-3, MCC 1.2.7
    
    
    Status on my rule says:
    
    State 			=		Enabled
    Substate			=		Running
    Time of last evaluation	=		15-JUL-1992 13:15:46.99
    Result of last evaluation	=		True
    Current Severity		=		Intermediate
    Error Entity		=		--NOT RETURNED--
    
    
    Rule attributes shows:
    
    
    Name			=		MINIM_PACKET_RATE
    Expresion			=		NODE4 MINIM PACKET RATE > 5
    						AT EVERY=00:05:00 FOR=00:02:00
    
    Severity			=		Intermediate
    Probable cause		=		Unknown
    State			=		Enabled
    Substate			=		Running
    Time of last evaluation	=		15-JUL-1992 13:15.46.99
    Result of last evaluation	=		True
    Current Seerity		=		intermediate
    Creation timestamp		=		15-JUL-1992 13:14:09.61
    Evaluation error		=		0
    Evaluation true		=		1
    Evaulation False		=		0
    
    
    The results of hitting Notify Requests show a window that states:
    
    Disabled with error .tas-private
    
    
    The NOTIFY DOMAIN pulldown shades out the "ENABLE" option
    
    
    Thanks for any help
    
    Bill

    further info...
    
    I have a small domain with 4 nodes in it.  I can get notification to 
    work in that domain, but not in my main domain.  The "Notify Requests"
    window shows the "good" domain as "enabled".  I guess my main domain
    is broke.  
    
    

While it is possible that you have uncovered something interesting in T1.2.7,
it is more likely that you are encountering problems that have already been
fixed for the SSB kit.

- .1 was a subtle hint by Erik to upgrade, then try again... 

/doug

P.S.  Why didn't you double-click on the error notification that was failing
and look at the error message ? Sometimes they actually give you a hint as to
what's wrong!  ;^)

    The double-click error is:
    
    An error has occured while determining the contents of the domain.
    
    
    I would love to upgrade, but...  Do you guys have AM/FM's that are
    compatible with V1.2 like SNMP, Bridge, Diagnose, TSAM??
    
    If they have been released, I will gladly upgrade.  
    
    Thanks,
    
    Bill
    

The SNMP AM is included in BMS
TCP/IP DA is not ready yet
Bridge and TSAM are produced other organizations, but may arrive shortly

-- Erik

    Well I know that I cannot upgrade, is there a possible work around
    or at least some ideas as to what to try to get this to work?
    
    
    Thanks