Conference azur::mcc

6121.0. "Chipcom MIB version 4.0 compile problem" by KAOFS::J_VORSTAND () Fri Sep 23 1994 11:07

    
    Hi,
    
    
    	I've been having a problem compiling a chipcom MIB for MCC. When I
    run the procedure MCC_TCPIP_MTU.COM, and supply the name of an older
    chipcom MIB (CHIPCOM_HUB30_MIBDEF.TXT), I do not have any problems
    compiling this MIB, but when I use the CHIPCOM_HUB40_MIBDEF.COM, the
    compile seems to stop short, creates a process dump, and advises
    looking into the CHIPCOM_HUB40_MIBDEF.LIS file for any problems.
    
    	After examining the CHIPCOM_HUB40_MIBDEF.LIS file, I have found NO
    strange occurrences/problems. In order to clarify what has occurred, I
    will include my attempt into this note. 
    
    
    FM1_SYSTEM> define MCC_SPECIFIC dsa2:[mcc]
    FM1_SYSTEM> define MCC_SYSTEM dsa2:[mcc]
    FM1_SYSTEM> define MCC_common dsa2:[mcc]
    
    
    FM1_SYSTEM> dir *40*
    
    Directory DSA2:[MCC]
    
    CHIPCOM_HUB40_MIBDEF.COM;4
       
    Total of 1 file, 55 blocks.
    ^@FM1_SYSTEM> @MCC_TCPIP_MTU.COM;<CR>
    
    Welcome to the DECmcc TCP/IP MIB Translator Utility driver procedure
    V1.3.0
    
      23-SEP-1994 09:35:24
    
    This procedure operates in a 2 phased manner --
    Phase 1 translates a MIB definition into a management specification.
    Phase 2 (as an option) translates the management specification into a
      dictionary loadable file and updates the DECmcc data dictionary.
    
    Phase 1 -- Enter name(s) of file(s) to translate
      (separate multiple files by commas): CHIPCOM_HUB40_MIBDEF.COM<CR>
    
    Phase 1 -- (prune option):
      You have the option to PRUNE the entity model tree created by the
        MIB Translator.
      Pruning will cause child entities without attributes to be discarded.
    Do you want to PRUNE the entity model tree? (Y/N) [N]: <CR>
    
    Phase 1 -- (help generation option):
    Do you want to build HELP text from the mib ? (Y/N) [N]: y<CR>
    
    Phase 2 -- Do you want to update the DECmcc data dictionary? (Y/N) [N]:
    y<CR>
    
    Issuing following command:
      $ MTU = "$ SYS$SYSTEM:MCC_TCPIP_MTU.EXE"
    
                                       * * *
    
    (Now processing file # 1 out of a list of 1 file(s) ...)
    
    Beginning Phase 1 for file DSA2:[MCC]CHIPCOM_HUB40_MIBDEF.COM;
    
      23-SEP-1994 09:35:44
    Now starting to run the MIB Translator ...
    This may take approximately 1-5 minutes.
    Issuing following command:
      $ MTU DSA2:[MCC]CHIPCOM_HUB40_MIBDEF.COM; -h
    
    %SYSTEM-F-ACCVIO, access violation, reason mask=05, virtual
    address=6F506594, P
    
      Improperly handled condition, image exit forced.
    
            Signal arguments              Stack contents
    
            Number = 00000005                00000000
            Name   = 0000000C                207C0000
                     00000005                7FEB7E68
                     6F506594                7FEB7E2C
                     0019F651                0014F4A2
                     0BC00009                00000003
                                             00324030
                                             00000003
                                             0019507C
                                             0013FA6C
    
            Register dump
    
            R0 = 07000230  R1 = 7FEB7CAC  R2 = 00000230  R3 = 6F506365
            R4 = FFFFFDD0  R5 = 00000002  R6 = 00000000  R7 = 7FEB7E6C
            R8 = 00000003  R9 = 00000A80  R10= 00000000  R11= 00323B10
            AP = 7FEB7C70  FP = 7FEB7C30  SP = 7FEB7CAC  PC = 0019F651
            PSL= 0BC00009
    
    An error occurred while running the MIB Translator.
    Check file CHIPCOM_HUB40_MIBDEF.LIS,
      if it exists, for any further information.
    Files CHIPCOM_HUB40_MIBDEF.MS and CHIPCOM_HUB40_MIBDEF_ENUM.MS
      may also have been created; delete these files, as appropriate.
    
      23-SEP-1994 09:36:57
    
    Procedure terminated in error.
    
    
    I would post the CHIPCOM_HUB40_MIBDEF.LIS, but its over 1000 blocks
    long, and I did not find anything indicating an error condition.
    
    Something I find curious also, the *30* MIB was a .txt file, and the 
    *40* MIB is a .com file... Have I overlooked something ? 
    
    Any insight to this problem would be greatly appreciated. If any
    additional information is required, pls let me know.
    
    Thanks in Advance
    
    JoeV / ITU / OMS
    
    
    
    
    

    
    
    The possibility that this might not be the preferred method of
    resolving this problem had occurred to me, and if this is the case
    any suggestion as to an alternate approach would be welcomed.
    
    This is an issue now, since the implementation date has already 
    arrived. Chipcom does not know what the problem might be, I've 
    already received another copy of their MIB, and tried that with 
    exactly the same results.
    
    Perhaps someone can comment on whether or not using the 3.0 MIB would
    be sufficient, as I have seen that there are a few problems with the
    fiber piece of it ?
    
    
    
    Thanks.
    
    jv / FMC

    
    Guy,
    
    	
    	Thank you very much for the assistance which you provided in
    resolving the Chipcom MIB problem. Your suggestion regarding trying 
    the new MCC_TCPIP_MTU.COM; resolved the problem. After copying this 
    new executable, from  "EVTAI1:: (47.183)", everything compiled just fine. 
    I did not make any other edits or changes to the MIB after sending it 
    to you.
    
    	Thanks very much,
    
    	JoeV / ITU