RE: Activation groups

Hi Simonse

Great discussion.  We are having similar problems when a user switches from
1 current library to another and the service programs continue to use the
files from the previous library.

Would it work to create only a "Close" procedure that closes all files used
in the service program and call it whenever you exit the calling program
(via LR or return).

you could then put a %open test a the top of each procedure to open any
files used by the procedure.

Jim

message: 1
date: Mon, 19 Dec 2005 16:20:41 +0100
from: "Simonse, Arco \(CMK\)" <ArcoSimonse@xxxxxxxxxxxxxxxxx>
subject: RE: Activation Groups (was: ILE Recursivity RNX8888)

Hi Birgitta,

> Because the Open and Close procedures are exported, I can
> open or close them whenever I want.
> Normally I let them open (I'd rather end the activation
> group), but there may be some exceptions.

Thanks for your clarification.
Personally I don't like it to keep files open when they are no longer
used. I'm thinking to create a serviceprogram to register
serviceprograms when they are opened (and then do an OpenFiles routine).
When a calling program is ending, it would call an unregister routine
that does a CloseFiles routine voor all registered serviceprograms.
By doing this I would ensure that I never forget to close files. But
maybe it's a little overdone to do such thing?

Best regards,
Arco Simonse
--

*****************************************