[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

4476.0. "Notification problems with x25 event svc failed" by BACHUS::FOLENS () Mon Feb 01 1993 10:55

    I'm running DECmcc v1.2.3
    I've set up notification to receive events from an x25-gateway (DECnet
    phaseV). 
    When I get an event of 'SVC failed' and I look into this event I get
    the following error on my iconic map:
    
    	On the notification window is say's : successfully received events
    
    						SVC failed
    
    	And an DECmcc message: Inconsistency between dictionary and
                                       information returned in outp.
    
    Is this solved in v1.3?
    When you need to disable the dna5_am sink or to delete the process
    mcc_dna5_evl for any reason, you need to disable all the outbound
    streams on all the phaseV nodes that are sending events to
    the MCC station. Is this normal. Also solved in v1.3?
    
    -Geert-

T.R	Title	User	Personal Name	Date	Lines
4476.1	#1 Fixed, and #2 normal	HAYNES::PURRETTA		`Mon Feb 01 1993 11:45`	7
	I just looked at the MSL changes made between v1.2.3 and v1.3 and yes, there were fixes applied to that event arguments. The mcc_dna5_evl is a listener. If you delete the process, the outbound streams either need to be told by disabling them, or you can wait for their disconnect timers to kick in and disconnect themselfs.
4476.2	Other events with same problem.	BACHUS::FOLENS		`Tue Feb 02 1993 03:09`	4
	I found the same problem with an event from the routing layer. Text of the event = PhaseIV translation failure. -Geert-
4476.3	Expect the unexpected (out arg, event arg, exception ...)	BLUMON::SYLOR	Architect = Buzzword Generator	`Sun Mar 07 1993 16:59`	4
	Hmmm, John, was this a case where the V1.2.3 list of args was wrong, or was it that a new arg got added after V1.2.3 shipped? If it was a bug, the error is probably OK, but if it was that you got an arg you didn't expect, MCC should not blink an eye.
4476.4	event argument numbers were wrong	TOOK::PURRETTA		`Mon Mar 08 1993 08:50`	7
	Mark, it was the case where the values assigned to the various arguments were wrong in the MSL. e.g. Argument foo = <nn> : datatype. <nn> was wrong. The AM didn't care, neither does FCL I believe, but the map had a problem when it went to the dictionary and compared what I returned against the MSL definition. The datatypes probably didn't match.