It looks like the mib2c file was written assuming that MIBs follow the
SMIv2 practice of making INDEX objects not-accessible.

   Objects which are both specified in the INDEX clause of a conceptual
   row and also columnar objects of the same conceptual row are termed
   auxiliary objects.  The MAX-ACCESS clause for auxiliary objects is
   "not-accessible"


  Bill


On Tue, Dec 10, 2013 at 4:50 PM, Dirk Buijsman <dirkjur...@hotmail.com>wrote:

> I generated a C-skeleton using mib2c -c mib2c.table_data.conf MY.MIB.
> A part of the output is the structure:
>
> struct channelTable_entry {
>     /* Index values */
>     char channelName[NNN];
>     size_t channelName_len;
>
>     /* Column values */
>     char channelName[NNN];
>     size_t channelName_len;
>     long count;
>     char message[NNN];
>     size_t message_len;
>     char lastMessageTime[NNN];
>     size_t lastMessageTime_len;
>
>     int   valid;
> };
>
> Obviously this gives a build error due to identical entries. What is the
> reason duplicate fields are generated? I looked a bit into the
> mib2c.table_data.conf file, but could not figure out where "index@"
> originates from.
>
> What causes this?
>
> Thanks,
> Dirk
>
> *    /* Typical data structure for a row entry */*
> *struct ${i}_entry {*
> *    /* Index values */*
> *    @foreach $idx index@*
> *     @if $idx.needlength@*
> *    $idx.decl $idx[NNN];*
> *    size_t ${idx}_len;*
> *     @else@*
> *    $idx.decl $idx;*
> *     @end@*
> *    @end@*
>
> *    /* Column values */*
> *    @foreach $c column@*
> *    @if $c.readable@*
> *     @if $c.needlength@*
> *    $c.decl $c[NNN];*
> *    size_t ${c}_len;*
> *     @else@*
> *    $c.decl $c;*
> *     @end@*
> *     @if $c.settable@*
> *      @if !$c.rowstatus@*
> *       @if $c.needlength@*
> *    $c.decl old_$c[NNN];*
> *    size_t old_${c}_len;*
> *       @else@*
> *    $c.decl old_$c;*
> *       @end@*
> *      @end@*
> *     @end@*
> *    @end@*
> *    @end@*
>
> *    int   valid;*
> *};*
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Net-snmp-users mailing list
> Net-snmp-users@lists.sourceforge.net
> Please see the following page to unsubscribe or change other options:
> https://lists.sourceforge.net/lists/listinfo/net-snmp-users
>
>
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to