RE: Open files after programs ending -- BPCS-L

I think the problems you are having is the way the BPCS As/Set programs are 
compiled.  Most of these now contain embedded SQL which makes the 
open/close of files processing handled by the "Close SQL Cursor" 
(CLOSQLCSR) prompt on the CRTSQLRPG command rather critical.  If it is set 
to *ENDJOB, regardless of how the program ends (LR on or off), the files 
will stay open.  We are on 6.0.04 mixed mode and experience the same 
problem with files being left open.  It would be nice if BPCS would be a 
good citizen and clean up after itself.  I believe in their own morbid way 
BPCS is attempting to improve performance by not re-opening these files.

The OVRDBF SHARE(*YES) will allow you to share and reuse open data paths to 
files and will improve performance as long as it is not taken to a strange 
extreme and proper clean-up actions are taken in the programs.

We have resigned ourselves to perform month-end processing on a 
"restricted" system.  We have "automatted" this as much as possible so it 
runs on Sunday morning at 12:01am.  We are blessed that no users really 
need the system for the approximately 4 hours the BPCS close jobs run.  We 
include in our month-end processing a Reclaim Storage (RCLSTG), and a 
full/complete AS/400 backup.  This is also the only time during the month 
the AS/400 is IPLed.

Regards,

Dwight

-----Original Message-----
From:   fkolmann@revlon.com.au [SMTP:fkolmann@revlon.com.au]
Sent:   Tuesday, September 07, 1999 6:43 PM
To:     BPCS-L@midrange.com
Subject:        Re: Open files after programs ending



DAsmussen@aol.com wrote:

>   In order to speed processing, some of the BPCS API's have been modified 
to
> perform a "return" rather than an "end program".  This leaves files open 
so
> that the resource-intensive process of opening them doesn't have to be
> performed every time the program is called.
>
> Leaving files open in an API is a rather elegant solution -- right up to 
the
> point that programs calling the API never tell it to "end program" and 
close
> the files.

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
call stack.  Otherwise it does no good at all to just do a return, when you 
call
the program next time it will open another ODP on top of the one already 
open.
If a program is called many times u end up with hundreds of ODPs in the 
PAG.
Rather than speed up things the reverse happens, u clog up memory and the 
jobs
still create ODPs on every call.  I have seen evidence of hundreds of files 
open
in BPCS jobs with repeated opens of the same file.  I am puzzled by seeing 
the
number of files increase then decrease as if there was some sort of cleanup
happening.  Just cannot fathom it.



+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---