Stored procedure-result set: how to deal with EOF? -- MIDRANGE-L

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

When one sets up a stored procedure that returns a result set, one has to 
specify SET RESULT SET .... FOR n ROWS.  If we've read 10 rows, we set 
n=10, etc.  How do we handle end of file: the situation where there are no 
records to return?  ...FOR 0 ROWS is invalid.  The IBM Redbooks don't 
handle this scenario, assuming that there'll always be at least one record 
returned.  We can use another parameter to denote EOF and return a null 
row, but this doesn't seem right.

Any ideas?

Buck Calabro
Commsoft, Albany, NY
mailto:mcalabro@commsoft.net

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.