RE: SQL/RPG 7.1 Cursor Consumption from one RPG pgm to another

Charles,

I have that defined that way. I am sanitizing my test code to remove real names etc and will post it shortly.

A snippet of the code that creates the cursor:

------------------------

exec sql close cursor1;

exec sql declare cursor1 cursor with return to caller for
SELECT * FROM file WHERE field1 = :parameter;

// open as normal
exec sql open cursor1;
return;

------------------------

steve

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Thursday, July 21, 2011 9:53 AM
To: Midrange Systems Technical Discussion
Subject: Re: SQL/RPG 7.1 Cursor Consumption from one RPG pgm to another

Guessing as I've not looked into that functionality...do you need a
WITH RETURN TO CALLER on the cursor declaration?

Charles

On Thu, Jul 21, 2011 at 10:03 AM, Needles,Stephen J
<SNEEDLES@xxxxxxxxxxxxxxxx> wrote:

I am developing on 7.1 OS.  I am experimenting with the 7.1 ability that allows a SQL cursor generated by a process to be consumed by a different RPG program.

I have succeeded in writing an RPG program that consume the cursor created by an SQL Stored Procedure written in SQL.  But I have not been able to have an RPG program consume the cursor created by another RPG program.  It does not appear to matter if the program that creates the cursor is executed as a stored procedure or an RPG program call of any type.  The result is the same, I can't read the cursor if the cursor was created with a non-SQL stored procedure/process.

I can't find where this scenario is explicitly forbidden, so I figure I might be doing something wrong.  Have any of you been able to do some testing along these lines?


Steve Needles

Northland Insurance

(651) 310-4203


==============================================================================
This communication, including attachments, is confidential, may be subject to legal privileges, and is intended for the sole use of the addressee. Any use, duplication, disclosure or dissemination of this communication, other than by the addressee, is prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy this communication and all copies.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.