Re: Calling a Procedure

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Sure...

Assuming you'll calling from a difference module, make sure the SQL module
is created with CLOSQLCSR(*ENDACTGRP)..

Your calling program would need to look something like so:

open_cur();
dow not done;
  done = fetch_cur();
  //do something
enddo;
close_cur();

You can't and open & fetch in the same procedure.

Note however, the fetching one row at a time is not the best use of SQL.
The above is pretty much using SQL procedurally as a 1 for 1 replacement
for RPG RLA.

Charles

On Fri, Jul 24, 2015 at 11:52 AM, Robert J. Mullis <
robertmullis99@xxxxxxxxxxx> wrote:

> I want to create a module that has one exported procedure in it.  When this
> procedure is initially called, I want to open an embedded SQL cursor and
> read the first record.  On subsequent calls to this procedure, I want to do
> some processing on the record previously read and then read the next
> record.
> I want to repeat this until I hit EOF on the SQL cursor.  Is it possible to
> retain the previous values read from the SQL cursor and have the cursor
> read
> the next record when the procedure is called subsequent times?
>
>
>
> Thanks in advance,
>
> Robert
>
> --
> This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
> mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.