Re: Close SQL Cursor without Ending Module

Michael,

You may run into a pseudo-open issue with what you want to do. IBM used
to "hold" the cursor partially open after something like 3 opens and
closes. The reason has/had something to do with performance. You may
have to have your program completely end and restart every so often.
Running it in a named or *NEW activation group may help. Then again, IBM
may have fixed this at newer releases of the OS.

Gary

-----Original Message-----

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Michael Ryan
Sent: Wednesday, December 05, 2012 11:48 AM
To: RPG programming on the IBM i / System i
Subject: Close SQL Cursor without Ending Module

Here's what I want to do...declare a cursor, open it, fetch records
from it, and then close it so the file isn't locked. If this was just
RLA RPG, I would do that with the OPEN and CLOSE opcodes. However,
using embedded SQL seems to leave the file open, with problems at
night with other jobs that need to access that file. I have SET
OPTION CLOSQLCSR=*ENDMOD, and that closes it when I end the program.
My problem is that the program isn't ended...someone walks away with the

display up on their screen.

How can I close an SQL cursor without ending the program? CLOSE
<cursor> doesn't seem to work while the program is still active.

Thanks!
--

--
This is the RPG programming on the IBM i / System i (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.