Re: Close SQL Cursor without Ending Module

On 05 Dec 2012 10:47, Michael Ryan wrote:

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.

Instead of trying to close the cursor, what about having the "other jobs that need to access that file" issue an ALCOBJ CONFLICT(*RQSRLS) before whatever [undescribed] but apparently conflicting activity? If the problem is currently that the "other jobs" try to obtain a lock via ALCOBJ without using the request to signal the database\SQL close event, then they might easily change to do so or instead just perform the operation without first doing the allocate [if the function being performed is a database file or member operation that already does that implicitly].