Conference azur::mcc

1922.0. "alarms don't work with vms 5.5" by HOO78C::TIMMERMANS () Wed Dec 11 1991 13:31

    After a VMS upgrade to V.5.5 every alarm rule which should run a procedure
is disabled with error status %JBC-I-ITMREMOVED, meaningless items were removed
from request.

MCC> ENABLE MCC 0 ALARMS RULE Byte_Sent__dsv02, in domain control

MCC 0 ALARMS RULE Byte_Sent__dsv02
AT 11-DEC-1991 15:09:44

Normal operation has begun.
MCC> show mcc 0 alarms rule Byte_Sent__dsv02 all att, in domain control

MCC 0 ALARMS RULE Byte_Sent__dsv02
AT 11-DEC-1991 15:09:54 All Attributes

                                   NAME = Byte_Sent__dsv02
                           Disable Time = 11-DEC-1991 15:09:51.04
                        Error Condition = "%JBC-I-ITMREMOVED, meaningless items
                                          were removed from request"
              Result of Last Evaluation = True
                                  State = Disabled
                               Substate = Disabled by error condition
                Time of Last Evaluation = 11-DEC-1991 15:09:44.51
                     Creation Timestamp = 11-DEC-1991 15:09:44.36
                       Evaluation Error = 0
                       Evaluation False = 1
                        Evaluation True = 1
                               Category = "Reachable"
                             Expression = (change_of(station _dsv02 Bytes Sent
                                          ,*,*), at every = 00:00:05)
                     Perceived Severity = clear
                              Procedure = SYS$COMMON:[MCC.ALARMS]ECT_ALARMS_DIFF
                                          ER_ALARM.COM;1
MCC>
                       
There is probably a wrong itemlist definition within the $SNDJBCW call in
the ALARMS FM or the MCC KERNEL. But because it's just an informational
error of the job controller the alarm rule should not be disabled.
                       
Is this a known problem, is this fixed in DECmcc V.1.2????

If more information is needed, please send me a mail.

Adrie Timmermans
CS/EIS Holland             

Yes, this is a known problem, which occured as a result of a change
in the VMS queueing mechanism in V5.5.  It is mostly fixed in the
DECmcc T1.2.* field test kit, and will be completely fixed for
DECmcc V1.2. SSB.

    
    We are also planning to release a patch for the V1.1 version.
    You can expect this in about 2 weeks.
    
    	aud...