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

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.

Date: Wed, 20 Aug 2014 14:15:32 -0500
From: rpg400-l@xxxxxxxxxxxxxxxx
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Why would a file in a service program get closed?

I'm not sure what you mean by "AG boundary issue".

It's not possible for part of a program to run in a different activation
group from another part of the same program. So an open instance could
not cross activation group boundaries...

Unless you're calling the program recursively and somehow expecting the
new activation to have the same open file as an earlier activation (this
doesn't seem likely.)

Can you explain your theory about actgrp boundaries? I'm not sure that
I even understand what the theory is.


On 8/20/2014 1:13 PM, Roger Harman wrote:

I'm still leaning towards an AG boundary issue. Changing the top
level CLLE to AG *NEW and everything downstream to *CALLER seems to
have resolved it.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.