AW: program won't let go of file

Thanks Barbara, Scott and everybody else,

I wasn't aware that there will be a difference in RCLRSC when running a
program in the default activation group compiled with either DFTACTGRP *YES
or *NO.
I always thought storage will not get removed for an ILE program running in
the default activation group, but only get initialized the next time the
program gets called.

In either way I got a lot of trouble with a client who called procedures in
my service programs (OK service programs are not programs! But ...) within
the default activation group. The client didn't want my service program
running in another activation group, which was the original design.
He didn't (want to) understand what activation groups are for ... but the
client is always the king!
I had to let my files open until a procedure which closes the files was
called.
But Instead of calling the close procedure or executing an
RCLACTGRP(MySrvPgm), my client insisted in using RCLRSC to close files.
After RCLRSC the files were closed but the procedures in my service programs
still thought the files were open. There was no way to trap the error,
neither with %OPEN, nor with reopening the file and checking %Error or
%State, nor using %error in composition with the native read/write. The
service program crashed as soon as I tried to write a record. The only
solution I found was creating a wrapper program and binding the module to
this program, which destroyed my complete design.


Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von Barbara Morris
Gesendet: Tuesday, 07. September 2010 19:58
An: rpg400-l@xxxxxxxxxxxx
Betreff: Re: AW: program won't let go of file

This thread has had some confusing messages about LR and activation groups.

I just want to make sure that everyone understands the following:

*For all activation groups, if LR is on in a module when the cycle-main
procedure returns, then the global files will be closed. When the
cycle-main procedure is called again, the module's storage will be
initialized and the files will be opened again.*

The activation group of the program does not affect the behaviour
regarding LR.

With DFTACTGRP(*YES), you get new memory the next time you call the
program. With DFTACTGRP(*NO), you get the same memory the next time you
call the program, and the memory gets initialized again. The effect is
the same, either you have new memory that gets initialized or you have
the same memory that gets initialized.

(Activation groups _do_ affect what happens with RCLRSC.)