×
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.
To return a result set from an RPG program, just open the cursor and take
care that no SQL CLOSE gets executed before progam end. Set Result Set is
only necessary if you want to return a multi occurence datastructure (or
array datastructure).
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von Wagner, Linda
Gesendet: Wednesday, July 23, 2008 18:39
An: rpg400-l@xxxxxxxxxxxx
Betreff: Returning result set from external stored procedure
I have an external stored procedure that calls an rpg program that builds a
dynamic select statement and am having a problem getting the result set
back. The stored procedure is defined with "Result sets 1, language rpgle,
reads sql data" and the rpg program is using "set result sets cursor C1" to
return the result set. If I debug the program, the second level message
under "Cursor C1 opened" states the following: The cursor was opened with
result set identifier of 0. If the result set identifier is non-zero, the
result table for this cursor is eligible to be accessed as a stored
procedure result set.
Does anyone know if I'm missing something or have done something
incorrectly? I'm at a loss as to what to try next.
Thanks,
Linda Wagner
As an Amazon Associate we earn from qualifying purchases.
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.