Re: Open files problem?

Jade,

Of the three possibilities you suggest, I would pick option 2, because it is
the cleanest.  But how about option 4: make the calling program ILE?  That
would seem to be the simplest solution.

As for leaving files open:  Do you ever change your library list from, say,
a production environment to a test environment?  If you ever do, you can
imagine the disaster open files from one environment might cause in the
other.  And if you don't, it is probably still safer not to assume it will
never happen.

Joep Beckeringh


----- Original Message -----
From: "Jade Richtsmeier" <jade.richtsmeier@mcis.cog.mn.us>
To: <RPG400-L@midrange.com>
Sent: Friday, September 14, 2001 4:26 PM
Subject: Open files problem?


> We are going to have the situation of an OPM program calling a series of
ILE
> programs.  The ILE programs are compiled with an activation group of
> *caller, and all is well.  The only problem we have is that there are
files
> opened in service programs that are not be closed when the OPM program is
> exited.
>
> We've come up with three options of handling this:
>
> 1.  Have the OPM program execute a shut down routine that would close all
> files that have been opened.  The problem with this is, how do you know
what
> files have been opened, unless you know all of the details of each file
that
> was opened when a service program was called.
>
> 2.  Use a named activation group when calling the ILE programs, and have
the
> OPM program reclaim the activation group at the end of the process.
>
> 3.  Leave the files open.  What issues are we going to have to deal with
if
> we do this?
>
> Thanks for any and all input!
>
> Jade Richtsmeier, Programmer/Analyst
> Minnesota Counties Information Systems
> 413 SE 7th Avenue
> Grand Rapids, MN 55744
>
> 218.326.0381 Ext. 21
> 218.326.3544 Fax
> jade.richtsmeier@mcis.cog.mn.us