buck,

no - this is the only pgm in the entire jobstream that uses these files...
they are only referenced in the declare cursor statement...

could there be some actgrp situation going on from pgms upstream that have
called this pgm?

Jay

On Fri, Oct 26, 2018 at 2:00 PM Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 10/26/2018 1:06 PM, Jay Vaughn 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?

I'm guessing that you're seeing pseudo-closed files. Is there something
like a CPYF, SAVOBJ, or something else that's trying to get an implicit
*EXCL lock on one of the files in the SQL cursor? If so, have a look at
ALCOBJ ... CONFLICT(*RQSRLS)

--
--buck

http://wiki.midrange.com
Your updates make it better!

--
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-2020 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].