[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

2084.0. "Notify/Alarm global wildcarding" by FACVAX::WOODCOCK () Mon Jan 13 1992 11:17

Hello,

Alarms now state they support the global wildcard. So I created an alarm
with an expression of (occurs(node4 * circuit * circuit down circuit fault)).
This worked ok and the rule was created, I then enabled it (from FCL) and
received a window from IMPM stating MCC Routine Error: %MCC-E-INV_ENTITY,
invalid entity structure. Does or will Notifications support the same
wildcard as Alarms??? Or is this a bug??? It doesn't seem appropriate to
offer it on one module but not the other.

kind regards,
brad...

T.R	Title	User	Personal Name	Date	Lines
2084.1	one wildcard per command?	TOOK::CALLANDER	MCC = My Constant Companion	`Fri Jan 17 1992 10:48`	3
	I will check with Audrey, but I thought they support only one wildcard per command; but I could be way off on this one.
2084.2	rule should work, now why doesn't it?	TOOK::CALLANDER	MCC = My Constant Companion	`Fri Jan 17 1992 15:13`	3
	Audrey says the rule should work. We are looking at the dumps now to see what we can figure out.
2084.3	We need more info	TOOK::ORENSTEIN		`Mon Jan 20 1992 08:55`	10
	Just to let you know what's up.... We did try out your senerio here and had no problems with it. We created the same rule, gnerated the same event and got our icon to highlight on our map. We'll keep out eyes open for any problems, but if you see anything else or have more info please let us know. aud...
2084.4	it does work...now	FACVAX::WOODCOCK		`Mon Jan 20 1992 10:19`	15
	Hi, I just re-tried enabling the rule and all looks well now (I hate it when that happens). But for clarity sake this is what I did initially in exact sequence. I had a map up and running with a generic notify for the top domain. I then brought up an FCL window and created the rule for the same top domain. I then enabled the rule from FCL and got the error message from a pop-up IMPM window. I hadn't re-tried to enable the rule until this morning so a simple exit and re-entry into the map may have cleared the prob. The system has also been rebooted since the initial error. But for now I'm content with knowing it at least works, if it happens again I'll stick in another reply to this note. kind regards, brad...