Open files after programs ending

I posted this to BPCS-L but got no response.
It is really and RPG issue or even an OS400 issue.
So I am posting to this list, maybe someone can help.

Frank Kolmann


I searched the BPCS-L archives and found an old post I put up
with some selected replies.  What I want to know is can I
safely compile AS/SET programs using the CLOSQLCSR(*ENDMOD)
parameter on the compile.

========================================================
MORE DETAIL FOLLOWS

We recently upgraded BPCS from 6.0.04G to 6.1.02.
We also upgraded AS/SET to V8. We had some minor issues with
AS/SET using the V6 repository but in the end it works OK.
The V8 version of AS/SET creates ILE programs and some of the
issues we had with modifying large AS/SET programs have been
addressed.

I am getting more problems than ever with things going wrong
due to files being left open.

The issue I am presently having is the SSA requirement to use
CLOSQLCSR(*ENDACTGRP) on the AS/SET compiles.  It is all well
and good to leave files open with the goal (hope?) that
performance will improve on subsequent reuses of the opens,but

There are however 2 MAJOR CASES where the reuse fails.

1.  Where a progam is closed and an OVRDBF is issued to
    open the file in a different library then the when program
    is called again the previous open is used and
    you get the wrong file.
2.  Where the program is closed, then the library list is changed
    and the program is called again, if the previous open is
    reused again you have the wrong file.

This I believe is really an AS400/OS400 issue caused by the
reuse logic NOT detecting that the object is needed from
a DIFFERENT library.

If Activation Groups were used as designed then closing the
AG will close the 'useless' open files, but BPCS does not use
AGs.

I simply want to know can I use CLOSQLCSR(*ENDMOD) on the BPCS
programs.  I see no reason why not, but I want to avoid jeopardising
our Production system simply because I recompiled programs.

I tried to get this info from OGS without any success.

Regards
Frank Kolmann

PS. I am old enough to be aware to close files properly etc etc
    I dont need instruction on proper coding techniques.
    The issue I have is the OS is keeping files open.

>From: Ata510@xxxxxxx
>Date: Tue, 7 Sep 1999 22:11:20 EDT
>
>There is always the CRTSQLRPG compile option which leaves files open
>betweencalls of the same program within the same user job (whether
>batch orinteractive) - CLOSQLCUR *ENDJOB versus the default of
>*ENDPGM, will leave files 'parially closed' by simple virtue of
>a compile option. In 6.0.04 and more so in 6.1.00 BPCS is compiled
>to take advantage of this. All you have todo in your program is
>make sure you close your cursors properly, so you don'tend up
>re-positioned in the wrong place in a file when you return to it.
>
>Having many ODPs on one job is not the bane of performance as it
>once was on the AS/400, and in fact can actually be an OK thing,
>especially when you do have programs which take advantage of
>re-usable ODPs. You can find out if theprogram is generating
>re-usable ODPs or not by running STRDBG (no program name)
>UPDPROD *YES over a given job with SQL in it, and view the job log
>for SQL messages.
>
>>In a message dated 9/7/99 6:40:44 PM Central Daylight Time,
>>fkolmann@xxxxxxxxxxxxx writes:
>>
>> Am I stupid and/or has something about the AS400 changed.
>> When I code for leaving files open I was under the impression that one
>> needed to use OVRDBF SHARE(*YES) and also have a file opening program
>> at the top of the