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