Re: Arrays

[Tony Carolla <carolla@xxxxxxxxx>]

<snip>
> SQL definitely is made for stuff like this. It's made to work with sets of
> data. One record at a time, use tradition I/O. Want to grab a bunch of
> records at once, use SQL. Boy, I hope I didn't start another holy war.
</snip>

I am one of the unfortunate ones who doesn't have the proper LPs for
using embedded SQL (I still use RUNSQLSTM at times).  If you are one
of these unlucky few, there are still ways of retrieving a high number
of records quickly.

I often use a method of setting the file cursor (SETLL), then
performing READs, rather than READEs, and monitoring for key changes
manually.  It's a small inconvenience, but not usually that complex. 
This allows me to override the file to SEQONLY(*YES XXXX), and set the
number of records pretty high.  As I understand it, if you use READE,
record blocking is your enemy, not your friend.

But this is a non-traditional way of using traditional techniques.  


-- 
"Enter any 11-digit prime number to continue..."