RE: Calling a Procedure

Use the Static keyword on the data's declaration so it persists across multiple calls to the procedure.
In addition you may want other Static variables so you know the state of the procedure (such as in knowing if this is the first time the procedure was called, remembering that eof was hit, etc).

I did something similar to this, except I had the cursor read in a number of records and let the procedure remember which record in the array it's currently at and if it should fetch more records or not.

Kurt Anderson
Sr. Programmer/Analyst - Application Development, Service Delivery Platform

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert J. Mullis
Sent: Friday, July 24, 2015 11:52 AM
To: 'RPG programming on the IBM i (AS/400 and iSeries)' <rpg400-l@xxxxxxxxxxxx>
Subject: Calling a Procedure



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.