× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. July 2013

Re: Activation group quandaries

On 7/24/2013 5:42 PM, Jon Paris wrote:
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.

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.

The SRVPGM is compiled with activation group *CALLER. The external program has activation group *NEW.

When the SRVPGM is running it is in activation group QILE.

When the service program calls the external program I would expect it to create a new activation group. Subsequent invocations of a service program procedure, from the external program, would (I think) load a new copy of the SRVPGM because we are now operating in a *NEW activation group.

david


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.