Hi Scott -

>On Thu, 22 Aug 2002, Ken Sims wrote:
> >
> > Reasonable only if you use programs for menus.  We don't, we use display
> > file type *MENUs.  However only in a few special cases are there *NEW
> > programs with another *NEW program downstream, and that is where the called
> > program is not called repeatedly, it is a program that is both a menu
> > option and called by a function key from another program.
> >
>
>I'm sorry, but it's completely reasonable to have the first program called
>by a menu be *NEW, and anything that it calls be *CALLER.
>
>Since you seem very sure that *NEW is hurting performance, I did some
>benchmarks.   Please keep in mind that I work for a small company, and our
>AS/400s are at the low-end of the performance spectrum:

Huh??????????????  Go back and re-read what I said.  I did *NOT* say that
only in a few special cases do we use *NEW.  We use a LOT of *NEW.  I said
only in a few special cases do we use *NEW where that program is called by
another program that is already running in a *NEW activation group.

Ken
Opinions expressed are my own and do not necessarily represent the views of
my employer or anyone in their right mind.



This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 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.