Re: Files left open even though they were closed?

["Brad Stone" <brad@xxxxxxxxxxxx>]

On Thu, 13 Nov 2003 08:34:44 -0500
 Hans Boldt <boldt@xxxxxxxxxx> wrote:
> Let's see if I understand this: A CGI request invokes a
> program that sets up the library list, which then calls
> RPG program PGMA which processes the file, right? Smells
> like a library list issue to me somehow. Perhaps the
> curlib is set to the PRODLIB? Or perhaps PRODLIB is in
> the system libl?
> 
> Cheers! Hans
> 

You got it.  :)  It's NOT a library list problem.  If I
view the job attributes and open files, it shows that the
file opened is still open in PRODLIB.

- CGI program sets library list to PRODLIB (and others)
- CGI program calls PGM A 
- PGM A opens ITEMPF in PRODLIB (since it's in the library
list) and does it's thing.
- PGM A ends (sets on LR) and returns control to CGI
program
- CGI program resets library list (removes PRODLIB).
- CGI program ends.

Now, if I go and look at the job that ran the CGI program,
I see that file ITEMPF is still open, and it is the ITEMPF
file from PRODLIB.

Now, if I run the CGI program again, this time in "test
mode" and add TESTLIB to the library list instead of
PRODLIB, ITEMPF in PRODLIB is used simply because it's
still open (ODP wasn't removed?) instead of the file in
TESTLIB.

So, for some reason these jobs are leaving ODPs out there
and the files are still open according to the system.

Someone mentioned on another list it could be because of
blocking and that if I used BLOCK(*NO) on the F-spec it
should help.  But to me, this is a major flaw in how the
ODPs are used and "held open".