[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

5952.0. "ACCVIO during WELLFLEET mib translation" by PADNOM::BOURBOTTE () Tue Apr 19 1994 12:40

	Hello,

	I'm trying to translate a new WELLFLEET mib, and I get a "yacc stack
overflow" message follow by a ACCVIO.

	The versions are:

	VMS 5.5-2
	DECmcc 1.3
	image name: "MCC_TCPIP_MTU"
        image file identification: "MCCMTU X1.2.3"
        link date/time:  1-SEP-1993 13:59:40.47
        linker identification: "05-09"


	Can somebody help me to fix the pb?
	The WELLFLEET mib is located at EVTISA::WELLFLEET_MIBDEF.TXT (47.175)

	Any help appreciated,


	ERIC
PS:
	You can find bellow the full ACCVIO message:

  $ MTU SYS$COMMON:[MCC]WELLFLEET_MIBDEF.TXT;
yacc stack overflow
%SYSTEM-F-ACCVIO, access violation, reason mask=05, virtual address=7265746E, PC
=001A3651, PSL=0BC00009
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           001A3651  001A3651
                                                           001532F6  001532F6
                                                           00153750  00153750
                                                           00153750  00153750
                                                           00153750  00153750
                                                           00153750  00153750
                                                           00153DF0  00153DF0
                                                           0014EAF3  0014EAF3
An error occurred while running the MIB Translator.
Check file WELLFLEET_MIBDEF.LIS,
  if it exists, for any further information.
Files WELLFLEET_MIBDEF.MS and WELLFLEET_MIBDEF_ENUM.MS
  may also have been created; delete these files, as appropriate.

  19-APR-1994 16:17:25

Procedure terminated in error.
T.RTitleUserPersonal
Name
DateLines
5952.1File a CLDSCCA::daveAhh, but fortunately, I have the key to escape reality.Tue Apr 19 1994 19:122
If this is a customer problem, file a CLD.

5952.2CLD number?UTRTSC::BEEKMANTon Beekman - NL/MCS - 7838-2345Thu Apr 28 1994 06:443
    
    I have the same problem, did anybody else already file a CLD?
    
5952.3File it anywaySCCA::daveAhh, but fortunately, I have the key to escape reality.Thu Apr 28 1994 11:547
File a CLD anyway.  It help product management
know what problems affect more customers and
adds priority in terms of getting it fixed.

A problem that has only one CLD is much less likely
to get looked at than a problem that has 3 or 4 CLD's.

5952.4CSC32::M_EVANSstepford specialistThu Apr 28 1994 14:536
    I am having the problem and will be filing an IPMT case on this.  If
    anyone has other CLD's or IPMT's I can reference I would appreciate
    this.  I have reproduced the problem on my system as well, and have the
    mib and the updated msl and mtu files.  
    
    Meg
5952.5A somewhat more direct hintSCCA::daveAhh, but fortunately, I have the key to escape reality.Fri Apr 29 1994 16:495
I guess its time for the more direct hint.

Those who filed CLD's on this problem have been given a
workarround.  No CLD, no workarround.