|
Each job certainly gets a new copy Gary - it may even get more if the--
SRVPGM is *CALLER.
David said that the SRVPGM is the one calling the *NEW PGM and I read
it as saying that it was running in QILE and assumed it was specified to do so.
Now that you raise the question I realize that the esteemed Mr. Gibbs
did not provide sufficient information to answer the question definitively.
The number of copies of the SRVPGM will depend upon its AG attribute.
If it is specified as QILE - then as long as there is an active
invocation of the SRVPGM then it will be used. There would however be
a new copy created if the SRVPGM had an AG attribute of *CALLER.
On 2013-07-24, at 5:12 PM, Gary Thompson <gthompson@xxxxxxxxxxx> wrote:
I am very interested in this topic because I don't have a goodmidrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
understanding of service programs and activation groups.
Jon's answer surprises me because I have thought each system i job
receives a "new" copy of a service program, and that activation
groups are "a job within a job", and therefore expected the >new<
activation group of the external RPG program would get a "new"
copy of the service program.
Thanks for the opportunity!
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
Sent: Wednesday, July 24, 2013 2:15 PMactivation group change from QILE to a new activation group?
To: Midrange Systems Technical Discussion
Subject: Re: Activation group quandaries
On 2013-07-24, at 4:08 PM, David Gibbs <david@xxxxxxxxxxxx> wrote:
My questions are:
When the service program calls the external RPG program, should the
new copy of the service program be loaded ... or will it call back
Yes - it will change to *New
When the external program calls back into the service program, will
a
into the original service program that invoked the external program?
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
Original copy should be used.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-lmoment to review the archives at http://archive.midrange.com/midrange-l.
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a
list
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/midrange-l.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact copyright@midrange.com.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.