Re: Size of Service Program

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

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?