Re: Workaround for 32767-byte and 32767-element limits?

On 10/9/06, James H H Lampert <jamesl@xxxxxxxxxxx> wrote:

So it's not a matter of allocating the memory; that's
already being done in the calling program. The issue is
accessing it. Somebody mentioned pointers; can anybody
point me to some information on how that's done from RPG?

Some of the IBM APIs work similarly.

An example:

QUSLJOBS (list jobs) loads up a userspace with variably configured
date. The first x bytes are header data, which contain the information
used to access the detail data. The data is all in a user space, but
there really isn't any difference between data in a user space and
data in a contiguous stretch of heap storage; both can be accessed
using pointer based variables.

A *very* simple example of processing information returned by
the QUSLJOBS API can be found at:

http://pando.org/downloads/cp0300r.txt

HTH,

Chris
--
chris@xxxxxxxxx
www.brilligware.com
Home of MineSweeper5250