Re: A question about multi-module SRVPGM

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.

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.

david