On Wednesday 28 November 2001 20:31, James Rich wrote:
> On Wed, 28 Nov 2001, Brendan Bispham wrote:
> > I'm trying to get an snmp apis converted to RPG, but there's far too many
> > pointers involved for my liking...
>
> I'm just curious - why do you want to do this in RPG?  Surely SNMP stuff
> is more easily handled in C.  C handles pointers well and RPG does not -
> what is your motivation?
>

James,
I started with the C examples but got compilation errors. These two, for
starters, since they seem identical to both the V3R2 and V5R1 manuals.

Are they easy? are they manual errors? ccsid errors? I dont know, so I moved
onto RPG...

----------------------------------
.05   141    25 |      if ( i > 100 /* MAX_NUM... */ )
\keyword{return(-2002);                                     |    141
0002.06 ===========>
......................................a.......b...................................................
0002.07 *=ERROR===========> a - CZM0401 The character is not valid.

0002.08 *=ERROR===========> b - CZM0347 Syntax error: possible missing ';' or
','.
0002.09   142       |                           /* Return if you exceed
maximum varbinds.  */                          |    142
-------------------------------------------------------------
0001.22    67       |int AddVarbind(snmppdu **pdu, char * oid, value v,
unsigned                                       |     67
0001.23 ===========>
..........................................a.......................................................
0001.24 *=ERROR===========> a - CZM0350 Syntax error.
0001.25    68       |char pdu_type, unsigned char asn_type)
                                         |     68

-----------------------------




This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].