Re: SQLRPGLE - can I have two cursors open at the same time?

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 04/18/2019
04:45:24 PM:

On Thu, Apr 18, 2019 at 3:39 PM Michael Schutte <mschutte369@xxxxxxxxx>
wrote:

The positioning of your fetch is important.
When you get to the bottom EndDo and go back to the top, the SQLCODE

being

checked with be from your c2 fetch, not the c1. So you may exit out
prematurely.

Personally, I do primary fetches with my next fetch right before the

end.

fetch c1
Dow sqlcode = 0
open c2
fetch c2
dow sqlcode = 0
fetch c2
enddo
close c2
fetch c1
enddo

This is why priming reads are a good habit.

I don't like "priming" reads. Why? It is bad programming
practice to have the same code that does the same thing in more than one
place in your program. There are multiple ways to avoid "priming" reads.

One is to have custom (separate) SQLSTATE or SQLCODE variables for
separate tables. The only way I know to do this is to use GET
DIAGNOSTICS. But, perhaps Birgitta knows of another way.

Another way is to use a procedure to perform the fetch, check the
result, and return a Boolean for the DO loop condition. For example, see
the following psuedo-code:

open c1
dow fetch_c1_is_good()
open c2
Dow fetch_c2_is_good()
...
enddo
close c2
Enddo
close c1

Sincerely,

Dave Clark