Re: A question about multi-module SRVPGM

Hi, David:

> David Gibbs wrote:

Mark S. Waterbury wrote:

Also, consider that, the more *MODULEs are bound in a single *SRVPGM, the more likely it may be that some of those *MODULEs refer to procedures in other *SRVPGMs. Unless you use careful planning to identify what *MODULEs refer to what other *MODULEs, and then bind those modules together in a single *SRVPGM, you have this "ripple" effect illustrated above.

This is why I generally recommend one *MODULE per *SRVPGM. That way, you only activate ("load") the ones you actually "need", especially using the V6R1 support for BNDSRVPGM(*ALL *DEFER), which only activates a *SRVPGM when one of its procedures is actually called.

IMO, this starts to make the management of service programs more trouble than their worth. Memory isn't really a problem anymore ... so let the system load extra service programs that aren't needed. Who really cares.

This V6R1 feature is not solely about the amount of virtual storage (memory) required, it also addresses the total amount of time it takes the system to activate each *SRVPGM. The new V6R1 *DEFER option on the CRTSRVPGM and UPDSRVPGM commands tells the system to delay this overhead until the indicated *SRVPGMs are actually needed (e.g., when one of the procedures within this *SRVPGM is actually called by the application.)

For really large applications, the overhead to activate all of the service programs "at once" (at application "start-up" time) can be considerable. V6R1 addresses this with the BNDSRVPGM(*ALL *DEFER) option on CRTSRVPGM and UPDSRVPGM -- this allows the application to start up more quickly, and then only incur the overhead of activating other service programs when and if they are actually needed. If an end user never invokes certain application features, many of that application's service programs might never be needed at all, so why incur the added overhead of always activating all of them?

I always put related service modules into a single service program. That way I don't have to keep track of which service program a specific function is in. I know that the AP function will be in the AP service program. Add to that the likelihood that the service program is probably ALREADY loaded is pretty high, you really don't have a huge memory burden.

That's fine, and said essentially the same thing in another part of one of my earlier replies to this thread.

david

All the best,

Mark