Re: Service programs and QSRVSRC

[Rory Hewitt <roryhewitt@xxxxxxxxx>]

Lim,

I can think of a couple of such cases:

If you're a software vendor, you might well want to use a bind-by-copy
methodology, to ensure that your customers can install the utility programs
and don't need to rely  on other *SRVPGM objects. I've done this myself many
times, to create fully stand-alone programs.

Also, for CGI programs, you'd need to ensure that any required *SRVPGM's are
in the same library as the CGI program itself. If you can't guarantee that,
then a multi-module stand-alone program works very well.

Rory

On Thu, Oct 15, 2009 at 11:08 AM, Lim Hock-Chai <
Lim.Hock-Chai@xxxxxxxxxxxxxxx> wrote:

> Our shop does not use bind-by-copy.  So... Protected level doesn't quite
> apply to our shop.  But I can see that would be useful for others.
>
> I don't ever think of a situation where I would want to create a program
> using multiple *MODULE.  If there are common functions that needed by
> other programs, I put those functions in a service program and bind them
> with the service program.