I see the same issue here. Batch or interactive.
The SQLRPGLE programs have EXEC SQL CLOSE at the end of the need for the SQL run. I also added EXEC SQL RELEASE ALL

The file stay open until the job ends. For batch jobs, no issue. But for some of the interactives, that's a problem when the user is sitting on the menu with nothing running. They think they are out of the job, but the file is still open.


On October 26, 2018 at 1:06 PM Jay Vaughn <jeffersonvaughn@xxxxxxxxx> wrote:


- so i have an sqlrpgle with a file NOT defined in f-specs
- declare,open,fetch cursor over file
- dow-enddo
- after enddo i have a close cursor

pgm has sql compile options:

exec sql
set option
commit = *NONE,
closqlcsr = *ENDMOD,
datfmt = *ISO;

When I run this pgm interactively it closes the file as it should.
When this job is run in existing jobstreams withing our EOD, these files
are left open.

What could be the difference that is leaving the file open?

Jay
--
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: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].