Conference azur::mcc

1830.0. "Alarm to test MUXserver links??" by KAOFS::BOIVIN (Moi, j'viens du nord!) Tue Nov 19 1991 18:19

Good day,

I'm running TSAM T1.0.1 on VMS V5.4-2 and having a problem creating an
alarm rule to test MUXserver 300 links:

CREATE DOMAIN Joffre_Novacor RULE MUXserver_JM301A_LinkA_Problem -
ALARM FIRED PROCEDURE = MCC_Common:DECALERT_INTERFACE.COM, - 
ALARM EXCEPTION PROCEDURE = MCC_Common:DECALERT_EXCEPTION_INTERFACE.COM, -
Description = "MUXserver link 'A' is experiencing problems", -
Category = "JM301A", -
BATCH QUEUE = "DECmcc$Batch", -
ALARM FIRED PARAMETERS = "IOCOPS", -
Expression_Rule_Format_1 =  -
(Terminal_Server JM301A LINK A Link Status <> "Running", AT EVERY 00:05:00), -
SEVERITY = Critical

The alarm rule is created and enabled without any problems but here's what I
get in the log file from the exception procedure: 


$!++
$! Run the User's Command Procedure
$!--
$ @DISK$USER:[MCC]DECALERT_EXCEPTION_INTERFACE.COM;2 "MCC 0 ALARMS RULE 
MUXserver_JM301A_LinkA_Problem"-          		!rulename
"MUXserver link 'A' is experiencing problems"-          !category
"JM301A"-          					!description
"(Terminal_Server JM301A LINK A Link Status <> "Running",
AT EVERY 00:05:00)"-          				!expression
"19-NOV-1991 15:45:48.25"-          			!time
"Rule could not be evaluated as the attribute was not returned by the Entity."-
          						!dtcrtf or error
"IOCOPS"-         !notification params
"SYS$SCRATCH:MCC_ALARMS_DATA_15454825.DAT"    !file that contains more info about the rule
!

Yet, I can do the following:

	DEChub$ manage/enter
	DECmcc (V1.1.0)

	MCC> Show Terminal_Server JM301A LINK A Link Status

	Terminal_Server KAOIOC_NS:.JM301A Link A
	AT 19-NOV-1991 16:16:52 Status

	                            Link Status = "Running"
	MCC>


What gives? Shouldn't I be able to do this? Thanks
for any insight you can provide.

Ed


PS. I tried using wildcards with not much success. Here's an example:

DEChub$ manage/enter
DECmcc (V1.1.0)

MCC> sho terminal JM301A LINK * Link Status

Terminal_Server KAOIOC_NS:.JM301A Link A
AT 19-NOV-1991 15:34:13 Status

                            Link Status = "Running"
%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FF6CFA69, PC
=0000FF90, PSL=03C00008
%SYSTEM-E-ACCVIO, access violation, reason mask=00, virtual address=0000000A, PC
=0000000A, PSL=0000000F

Good day,

Would anybody have an example of how to test MUXserver links?? I've
tried playing around with the rule in .0 but have had no success yet.

Is alarming against the link status the right idea? or is there a better
method?

Any input is appreciated.

Thanks,

Ed

    
    Hi,
    
    Weve made one work by using a Change of link status rule. We had 
    some problems with some attributes not returned also, but the rule
    worked. It is on a customer site - I will bring it in and put it here.
    
    Rgds,