RE: SQL cursor closed but not closed

SQL does not normally close access paths until either the program ends
or the activation group ends for performance reasons. There are compile
options that control this and I think there was a recent discussion that
went into a lot of the details on this.

Matt

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of David Foxwell
Sent: Wednesday, October 24, 2007 8:56 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: SQL cursor closed but not closed

I don't understand what's happening here:

I have a subfile that is charged by a SQL FETCH statement. The subfile
contains the list of relations of a client, family members, etc. Its
charged completely everytime the subile is displayed.

If I stop the program (debug) while the SF is being charged, I can do
DSPJOB and see that my file is open with a format name like FORMAT0001.
When EXEC SQL CLOSE C1 is executed, I see that the file is closed.

I press option 5 enter to view a subfile record.
On returning to the subfile page, the whole thing is cleared and
recharged.

Now when EXEC SQL CLOSE C1 is executed, I see that the file is still
open.

Anyone know why?