Generated code for "not-accessible" columnar objects

[Frank Fock]

Hi Alex,

First, please do not post any HTML messages on the mailing list, because
the
mailing list archive otherwise becomes unreadable.

To your question. Yes it is an intended behavior, because the "n..." and
"c..."
defines make only sense if there is a C++ object generated for the
object, which
is part of a row. But there no C++ object generated for not-accessible
MIB
objects.

Best regards,
Frank Fock

Alex Finogenov wrote:

>
>
> Frank & Jochen,
>
> I have found that if a columnar object's MAX-ACCESS is
> "not-accessible", the generated header file does not contain either
> n... or c... column ids, while still containing the col... string for
> the object.
>
> For example, in IEEE802.11 MIB, the agentgen generates the following
> #define lines for the dot11AuthenticationAlgorithmsIndex index of the
> dot11AuthenticationAlgoritnmsTable:
>
> #define oidDot11AuthenticationAlgorithmsIndex "1.2.840.10036.1.2.1.1"
> #define colDot11AuthenticationAlgorithmsIndex "1"
>
> but fails to generate the respective
>
> #define nDot11AuthenticationAlgorithmsIndex 0
> #define cDot11AuthenticationAlgorithmsIndex 1
>
> Is this the intended effect of the object's MAX-ACCESS being "not
> accessible", or this is a bug in the agentgen?
>
> Thanks,
> Alex