Conference azur::mcc

5289.0. "DECnet events and rules." by MANWRK::KEEN () Thu Jul 01 1993 14:41

Hi,

I'm using

VMS v5.5-2
DECmcc v1.3
Local MIR

I am experiencing the following sequence of events, can anyone help please.

I have an occurs rule monitoring DECnet 0.7, Aborted service request
messages which triggers sometimes. On investigation, I have found that
when the rule does not run, and I double click on the notification of
that event, I get the error "Inconsistency between dictionary and
information returned in outp." after the details section has output
its heading "successfully received events :"

If I use a DECterm with 'reply' on to display the actual DECnet
events, the ones where the rule fires and can be double clicked to
display the full information are of the form :

%%%%%%%%%%%  OPCOM   1-JUL-1993 14:55:30.86  %%%%%%%%%%%
Message from user DECNET on TLOVAX
DECnet event 0.7, aborted service request
From node 62.336 (TLOVAX),  1-JUL-1993 14:55:30.85
Circuit QNA-0, Line open error, Ethernet address = 08-00-2B-16-2F-09

whereas the ones that do not trigger the alarm and fail when double
clicked on, are of the form :

%%%%%%%%%%%  OPCOM   1-JUL-1993 14:55:30.86  %%%%%%%%%%%
Message from user DECNET on TLOVAX
DECnet event 0.7, aborted service request
From node 62.336 (TLOVAX),  1-JUL-1993 14:55:30.85
Circuit QNA-0, Line open error, File open error, Load file
%MOM-E-OPENIN, error opening SYS$COMMON:[MOM$SYSTEM]SH1601ENG.SYS; as
input
-RMS-E-FNF, file not found
Ethernet address = 08-00-2B-16-2F-09

i.e. this type has some further information about the operation. This
extra information appears to stop the base ethernet address being
'attached' to the notification and also stop the rule being activated.

Unless the software (mcc_dna4_evl ?) that processes the DECnet events
expects the ethernet parameter to be at a specific location in the
message, I don't understand why it does not work.

Also, why is the rule not fired, I would have expected to have the
rule failure command file run if the data was wrong, but neither the
success or failure command procs. are run.

Any explanations, assistance greatly appreciated.

Regards,

Graham.

Is there an answer for the problem in .0 ?  I have the same problem with a
notification request for 'aborted service request' events.

The error message output by mcc is

	"inconsistency between dictionary and information returned in outp."

The DECnet event which causes the failure is 

%%%%%%%%%%%%
DECnet event 0.7, aborted service request
From node 10.11 (NMCC01) 18-Oct-1993, 12:45:39.38
Circuit ISA-0, line open error, Line communication error
%SYSTEM-F-TIMEOUT, device timeout
Ethernet address = 08-00-2b-06-9b-78
%%%%%%%%%%%

Using the following DAP command to look at the 'aborted service request' info
in the dictionary gives:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
DAP> show class node4 subclass circuit event ABORTEDSERVICEREQUEST argument REA
SON definition CONSTRUCTOR_DATA_TYPE

   Definition Name = CONSTRUCTOR_DATA_TYPE
   Type = T   Length = 110   Count = 1   Defined = TRUE   Class = S   Usage = IL
V

         (
          1 = (
              0 = %X    526563656976652054696D656F7574 -- "Receive Timeout"
              1 = %X    52656365697665206572726F72 -- "Receive error"
              2 = %X    4C696E65207374617465206368616E6765206279
            20686967686572206C6576656C -- "Line state change by higher level"
	      3 = %X    756E7265636F676E697A65642072657175657374 -- "unrecognize
d request"
              4 = %X    6C696E65206F70656E206572726F72 -- "line open error"
            )         )
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Is the information in the dictionary incomplete i.e. if the event has more text
than 'line open error' or 'Receive error' is this the reason for the failure ?

Is there a fix available, if not when will one be available ?

Regards
Colman