|
Generally, it's pretty simple...
Is a program called repeatedly, such that 100's or 1000's of activation
groups would be created and deleted per second with *NEW?
If so, then don't use *NEW. Use a named activation group, preferably
something like MYCOMPANY or MYAPP rather than QILE.
Now I believe in one of his messages, Jay mentioned this was going to be a
CGI program?
In that case, there's a few more considerations...
https://www.ibm.com/docs/en/i/7.5?topic=programming-cgi-programs-activation-groups
- Named activation groups are required if it's a persistent CGI program.
- *NEW is a good choice to ensure cleanup between calls for stateless
programs. Simplifying the code and helping to protect you against mistakes
in the code.
But realize *NEW does have a cost, if you expect that your stateless CGI
program is going to be called 100's or 1000's of times a second, *NEW may
not be the correct choice. You may need some added complexity to use a
named activation group.
Charles
On Fri, Jul 26, 2024 at 8:43 AM Javier Sanchez <
javiersanchezbarquero@xxxxxxxxx> wrote:
Right Charles, I may have misunderstood. I believe that anyway, if *NEWis
may give you performance issues and other problems and if you don't know
how to use it, better not use it.
Murphy's law, you know! :-)
JS
El vie, 26 jul 2024 a las 8:08, Charles Wilt (<charles.wilt@xxxxxxxxx>)
escribió:
On Thu, Jul 25, 2024 at 6:44 PM Javier Sanchez <
javiersanchezbarquero@xxxxxxxxx> wrote:
Susan Gantner wrote "The 7 Deadly Sins of ILE". She states that it
https://authory.com/JonParisAndSusanGantner/The-Seven-Deadly-Sins-of-ILENOT
advisable to use *NEW for an activation group. Better give a literalname
that identifies an application and the programs that work with it.
You are misunderstanding...
relatedloop,
Third deadly sin: Using *NEW *by default* rather than *by design*.
Using *NEW appropriately , is a very good thing.
Assuming the OP's pgmA is the first pgm being called and is not in a
*NEW is a good choice.list
Charles
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
listquestions.--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
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.