Re: Why would a file in a service program get closed?

Scott,

Imagine this scenario:

1: Program P1 calls the initialization routine
2: Program P1 calls program P2
3: Program P2 calls another routine in the service program that reads
a file
4: Program P1 calls the exit routine

Assuming the service program has *CALLER it opens the files in the
activation group P1 runs in. But it reads the file in the activation group
P2 runs in. So as long as P1 and P2 run in the same activation group
everything is hunky dory. But when they don't, step 3 blows up.

Roger stated 'At this point, I'm thinking I screwed up the named AG.'

Joep Beckeringh

Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>

Re: Why would a file in a service program get closed?

Roger,

Sorry, I'm not understanding your logic. No matter what the activation
group is set to, I don't see why it would close your file, unless you
actually ended the activation group....?

-SK

On 8/20/2014 3:41 PM, Roger Harman wrote:

I know a program won't run different parts in different AG's. No
recursion in this process.

At this point, I'm thinking I screwed up the named AG. Maybe a typo
I didn't see.

I do know that since the change to *NEW/*CALLER all is well.

Mark Waterbury responded offline that the "Allow reinitialization
(ALWRINZ)" parm on CRTSRVPGM default of *NO might have some bearing
on a named AG. Don't know about that (never really looked at it) but
I intend to read up on it.

Sorry I missed you (and the other great presenters) at OCEAN last
month. Now that I'm back working, it just wasn't practical to get
there.