× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I really doubt there's a single pat answer to this question (other than "it depends.") There's simply too many variables involved... The size of the code is only one, the number of modules is another, the number of open files, and the amount of memory used would all come into play.

Would you rather have a "big bang" (all loading work done at once) or a "gradual spread" (same amount of loading, or maybe more, spread out over a longer time.)? Based on the way your application works, how many of the routines would end up being activated if they were all split into separate *SRVPGMs? Would they all be activated anyway? If so, would they all be activated at the same time?

It's certainly not a straightforward question, and therefore there isn't a straightforward answer.


On 11/8/2010 10:25 AM, Robert Mullis wrote:
My source is divided by applications, A/P, POS, etc. Within each
application, there is a service program with all the reusable procedures
for that application. Recently when adding new procedures to the
service program in a particular application, I noticed that this service
program was getting large, object size and also the number of procedures
it contained. I have never read anywhere that the larger the size of a
service program became, the poorer it performed. Is there a theoretical
size limit when a service program's performance becomes affected?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.