× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



>>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

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.