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

On 21-Aug-2014 04:30 -0500, j.beckeringh wrote:

Imagine this scenario:

1: Program P1 calls the initialization routine <ed: of the srvpgm>
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.'

Yet surely that scenario contradicts the claim that "As to the file never being opened - not the case. This occurs a few records into the process so the procedure already executed several times."? As I understand the scenario presented above whereby the AG were setup incorrectly, then the P2 never could have processed "a few records" because the file was never opened [to the AG in which the READ activity runs]; i.e. the first I/O would have failed with the same error status, such that only _zero records_ could have been processed.