RE: Creating a cursor result set

[Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>]

>>If I leave the cursor open, I can read the entire result set.
>
>Working as designed. 

I'd figured as much.  Thanks for the confirmation!

>>The question: Should I be using CLI instead?  Any opinions on adding a
>>'shutdown' parameter and calling the SP again to close the cursor?
>
>The CLI won't help because the same rules apply. Stored 
>procedures do not close the result set. 

I should have thought this through a bit more before posting.  This makes
perfect sense because:

>The consumer of the result set (i.e., the client that 
>called the stored procedure) is responsible for closing 
>the result set. 

I was thinking only of the server side and not the client.  I was stuck in
thinking that the server session would be left in limbo when the client
closed the connexion.  I need to dig deeper into QSYSWRK to understand when
these server side jobs get cleaned up.

Thanks for the pointers Simon!
  --buck