Re: Close SQL Cursor without Ending Module

Because SQL operates at a higher level of abstraction...your program can't
"close" a table as it hasn't opened it! The DB query engine has.

Your program can and does tell the DB it's done with a cursor, but it's up
to the DB to close the tables when it feels it's appropriate.

That 20yr old process that expected all activity to cease at 5pm needs a
little updating. :)

Charles


On Wed, Dec 5, 2012 at 1:30 PM, John Yeung <gallium.arsenide@xxxxxxxxx>wrote:

On Wed, Dec 5, 2012 at 12:51 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

The real problem as Chuck alludes to is the "other" programs that expect
the file to not be in use... While that may have been the case 20yrs

ago,

it is no longer true.

I don't see the "real" problem as being the other programs. If a
program wants to release a file, why shouldn't it be able to?

John
--
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.