RE: Based variables

Hi Ken,

At 12/12/00 12:46 PM -0500, you wrote:
> >  The record length in this case is 148.  I'm expecting (at this time) a
> >maximum of 4000-5000 records.  Minimum is one record.  So I picked an
> >incremental of 500 as a reasonable number.  I'm using a based DS, so I can
> >potentially allocate a little over 113,000 records at one time. Then I'm
> >"shifting around" another DS as a "view" to each iteration of the
> >data.  That should give us plenty of elbow room.
>
>You shouldn't need a DS based over the whole area, just the DS that you
>shift around.  Since the maximum single allocation in the default heap is
>16MB - 64KB, the maximum number of records you can hold is 112,916.  If you
>ever needed more, you could use multiple allocations, it just would take
>some extra coding to switch between allocations as needed.

  How would I load / unload the data?  Here's a simplistic illustration of 
what I'm doing:

FInputFile   IP ...     DISK

D OneRecord             E DS            BASED( OneRecord@ )
D                                       EXTNAME( InputFile )

D EntireBatch             DS            BASED( EntireBatch@ )
D                                       LIKE( OneRecord )

  I'm using OneRecord as my moveable view into the data.  As the file is 
read I ALLOC/REALLOC EntireBatch and position OneRecord accordingly to 
"automatically" populate EntireBatch.

  Do you have a more efficient way of doing this?

  -mark

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---