RE: sql exec speed. was something else

>> It may not be as fast as Chain/Update,   However,  It
>> may get faster than SETLL/READE.

>When I became a System/38 programmer back in
>the mid '80s I was told repeatedly by senior RPG
>folks that a CHAIN was internally identical to a
>SETLL/READE, as long as you're using the same key.
>
>What's the difference?

SETLL/READE implies that you're going to process records in a set, like all
the items on an invoice.  RPG will still read them one at a time like it
always did (aside: blocking can play a huge factor) but SQL is designed
around the idea of processing the entire set at once.

As always, generalisations about performance without specific examples is
nothing more than a philosophical discussion.  Having said that, the major
performance booster that I've seen is a reduction in I/O.  I can reduce the
number of records I read or reduce the number of fields I read.  Either
technique works with RPG and SQL.

Buck Calabro
Commsoft; Albany, NY
Visit the Midrange archives and FAQ at http://www.midrange.com
"For every complex problem, there is a solution that is simple, neat, and
wrong."
 -- HL Mencken