Conference azur::mcc

3322.0. "v1.2 alarm exceptions" by CTHQ1::WOODCOCK () Tue Jul 07 1992 15:22

Hi Folks,

8810
vms v5.4-3
dns (private)
mcc v1.2

I just upgraded and seem to having some problems with alarms. I have 12 domains
with an alarm for each with an expression of:

                  node4 * circuit * substate<>none

When the 12 rules are enable I receive several exceptions on two of the domain
rules with the following error:

"Software logic error detected<EOS>%MCC-E-NOPARAMLIST, no parameter list was
 supplied in this ILV"


Initially I got this error with the RULES saved over the install so I deleted
all rules and recreated these 12 with no change (same errors). One note is that
one (or both) of these domains had changes made to them (entities added) from
the t1.2.7 kit. The last kit saw none of these errors.

Side notes: The file MCC_COMMON:MCC_ALARMS_RULES.COM was not created with the
install. I also still do NOT see the node4 name/address coming thru as a 
parameter (did I miss it somewhere???) when the above rule fires an exception.
The install seems to save RECORDs, ALARMS, NOTIFYs, and TARGETs (thanks much).

thanks for any info,
brad...


ps. a quick reply to this note is most appreciated as our (esc) tour schedule
    since moving into our new home is pressing for demo's almost daily!!