RE: SQL vs. traditional I/O?

> From: James Rich
> 
> Can this be restructured in such a way that it doesn't required
opening
> and closing the cursor for every iteration through the loop?

Feel free to tell me how.  If you cannot, you have to leave them in,
because that's what is necessary for a single record fetch.


> That seems
> awful wasteful and could be responsible for a large amount of the
> performance difference.  Maybe SQL is still slower, but it seems like
this
> opening/closing of the cursor needs to be removed from the loop in
order
> to make an appropriate comparison.  If they can't be removed, this
seems
> like another example of the shortcomings of the way SQL is used within
RPG
> more than a problem with SQL itself.

Why is it different in any other language?  To fetch a record, you have
to create a cursor to do so.  Please, show me a better way.


> It is also interesting to consider the differences between SQL and RPG
I/O
> for single record access.  For example, when exactly is the file
pointer
> set for the chain operation?  If another chain immediately follows
that
> fetches the next sequential record, is the file pointer reset before
> reading the file, or does the system know that it is already set to
the
> right spot and just leaves it alone?

There is something to this; I reversed the order on the chain and it
increased the load 60% on the RPG without affecting the SQL.  Still,
that's 6-to-1 for RPG.

Joe