Re: Size of Service Program

Just to add further to Scott's comment. Will you use the service program in batch, interactive, or both?

If primarily batch then taking the load-all hit for a 30 second batch job is probably not a good use of resources - remember the Activation goes away when the job ends. But if the majority of the work is interactive then in the past I have even forced large Service Programs to load during the sign-on job to get it out of the way.

Some of my clients (those with good source control systems) even had separate sets of Service Programs with associated binding directories - one for batch use and one for interactive. These days you can use the *DEFER option on the CRTSRVPGM and CRTPGM commands. That way you can often use the root program in the sequence to control the loading - thereby achieveing a similar effect.


Jon Paris

www.Partner400.com
www.SystemiDeveloper.com



On Nov 8, 2010, at 2:32 PM, rpg400-l-request@xxxxxxxxxxxx wrote:

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?