Conference azur::mcc

2903.0. "ODS mib doesn't compile on T1.2.7" by YOSMTE::SIMMONS_KE (KF0JX-Network Consultant) Thu Apr 30 1992 18:21

I am trying to compile a private MIB from ODS. I get an error while running the
MTU on their mib file...

Now starting to run the MIB Translator ...
This may take approximately 1-5 minutes.
Issuing following command:
  $ MTU DECMCC$DKB0:[MCC]ODS_MIBDEF.TXT;
syntax error
Line 1871
An error occurred while running the MIB Translator.
Check file ODS_MIBDEF.LIS, if it exists, for any further information.
Files ODS_MIBDEF.MS and ODS_MIBDEF_ENUM.MS may also have been created;
  delete these files, as appropriate.

  30-APR-1992 09:36:22

Procedure terminated in error.
-----------------

ODS_MIBDEF.LIS
   .
   .
   .
1869    adminPrivilege OBJECT-TYPE

1870            SYNTAX  INTEGER {
1871                            read-only
Syntax error at line 1871

The beggining of their mib looks like this...


-- ODS ENC Enterprise Specific MIB (August 20, 1991)

-- In additIn addition to the ODS MIB, the ENC agent also
-- supports several objects under enterprises.23.

ODS-ENC-MIB DEFINITIONS ::= BEGIN

IMPORTS
        enterprises, NetworkAddress, IpAddress, Counter, Gauge,
                TimeTicks FROM RFC-1155-SMI
        snmp FROM RFC-1158 ;

DisplayString ::= OCTET STRING
PhysAddress ::= OCTET STRING

ods                             OBJECT IDENTIFIER ::= { enterprises 50 }

enc                             OBJECT IDENTIFIER ::= { ods 1 }
enBridge                OBJECT IDENTIFIER ::= { ods 2 }
tokenRing               OBJECT IDENTIFIER ::= { ods 3 }
trBridge                OBJECT IDENTIFIER ::= { ods 4 }

           -----------------------------
	The section that produces the syntax error is...

adminPrivilege OBJECT-TYPE
        SYNTAX  INTEGER {
----------------------> read-only(1),
                        read-write(2),
                        super-user(3)
                }
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
                        "The access privilege afforded the community name
                        used in the requesting PDU.  This value allows a
                        network manager to easily determine its ability
                        to read and write protected objects."
        ::= { encAdmin 9 }

           ------------------------
	If I remove the items in the '{}' it gets past this point and fails at
another object that has the same info inside the '{}' i.e. read-only(1)...

	I have talked with ODS and they can not find a reason for the problem.
They say their MIB compiles on HP, SUN, UNIX, etc. They asked if the DEC MTU
was a MOSEY-like compiler.

Kevin

	"read-only" is a keyword and used in the ACCESS clause. What you
	can do is change it to "read_only" or "readonly" and it should translate
	fine.

adminPrivilege OBJECT-TYPE
        SYNTAX  INTEGER {
----------------------> read_only(1),
                        read_write(2),
                        super_user(3)
                }
        ACCESS  read-only
        STATUS  mandatory

    That took care of the problem. Thank You. Now the question is why did
    it fail on this translator/compiler ( is that the proper terminology?) 
    and not on others, as the vendor claims?
    
    
    Kevin