Instead of concerning yourself wioth activation groups for this problem, try creating a command for each product that calls the initial program for it.  In the command definition, you can specify a Product Library that is placed on the library list ahead of the Current Library and before any user libraries.  This library is only in the library list for the duration of the command.
The Product Library is also available on MNU objects.
 
Jeff Young
Sr. Programmer Analyst
IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions V5R2 
IBM  Certified Specialist- e(logo) server i5Series Technical Solutions Designer V5R3
IBM  Certified Specialist- e(logo)server i5Series Technical Solutions Implementer V5R3
  
 






________________________________
From: Charles Wilt <charles.wilt@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, January 7, 2009 11:11:53 AM
Subject: Re: ACTGRP

You could leave the code as RPGIV and take advantage of the group jobs.

It'd be interesting to see Scott's thoughts on this, but I think group
jobs might be a better solution than trying to use activation groups.

Charles

On Wed, Jan 7, 2009 at 10:41 AM, David FOXWELL <David.FOXWELL@xxxxxxxxx> wrote:

Well, that's something I hadn't thought of but I've already pushed the CVTRPGSRC button. There's not a whole lot of code to convert. It's not too late however.

But, there must be advantages to using activation groups as opposed to GRPJOB. What are they? In the first instance I'd have 1 job and up to 8 ACTGRP, in the second, 1 main job and 8 GRPJOB.

-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Mark S. Waterbury
Envoyé : mercredi 7 janvier 2009 16:02
À : Midrange Systems Technical Discussion
Objet : Re: ACTGRP

Hi, David:
(
Perhaps trying to use multiple ILE activation groups is the "wrong"
technology to solve this problem? :-o

Since you mentioned that the bulk of the application is OPM, you might want to investigate "group jobs", and the TFRGRPJOB and ENDGRPJOB commands.  Traditionally they are used via an Attention-key exit program that pops up a menu, but you don't have to do it that way.  (I admit this is an "old school" approach, but I think it might just be "the right tool for the job" in this case.)

Since each "group job" is a separate job, as far as OS/400 is concerned, it has its own *LIBL, and its own call stack and its own default activation group (where OPM programs run), etc. -- So then, using the TFRGRPJOB command, and perhaps an ATTN-key menu, you can allow users to "jump" from one group job to another (or, in terms of your application, from one "product" to another.)

Group jobs are a special case of interactive jobs, where only one group job in the group is "active" at a time, and the others are "suspended"
or "swapped out". (Very similar to what products like "Software Carousel" provided in MS-DOS.)

HTH,

Mark

  > David FOXWELL wrote:
Thanks Scott,

I believe you are saying that a named group does not automatically end like a *new group. In that case,when would it end?

Currently I cannot do what I'd like to because the application is mainly OPM. After the first call, files of the previous library list may remain open so even if I change the library list the program will continue to use the files of the original library list.

The idea was that by converting the OPM source and using an activation group, this problem would evaporate with the activation group at the end of the program.

But as the user on each entry can effectively change the library list, I wondered if I could create a named  activation group for each product and keep all my files open between calls.

...(snip)...

--
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.

--
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 thread ...


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.