|
> From: Joel Cochran
>
> As a general rule in my shop, no programs are created with *CALLER.
> They are created with either *NEW or 'named' depending on the
frequency
> of their use. Service programs, by contrast are always created with
> *CALLER unless there is a specific feature or performance need to use
a
> 'named' activation group.
I look at things a little differently, since I'm an old application
programmer. I separate programs into "top-level" and "subprograms".
Now, for tools, the only reason I have subprograms is because I don't
use service programs, so that situation resolves to yours in the long
run anyway. The tool programs (ones invoked by commands) are
ACTGRP(*NEW), and the subprograms (which -should- grow up to be service
programs someday) are set up as *CALLER.
With application suites, though, it's different. I tend to set up the
main menu as *NEW, and let everything else live in *CALLER. This has
pros and cons, I'd guess, but it prevents a lot of new activation
groups. Of course, for this purpose, I guess a named activation group
("APPL"?) would be just as good.
Joe
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 [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.