Re: Best way of using Service programs.

On 2/14/06, albartell <albartell@xxxxxxxxx> wrote:
> What was Turnover's reason for not using Binding Directories.
>
> I myself am a big fan of Binding Directories because it eases compiling, and
> as long as you don't fully qualify the binding directory entries you should
> be fine when you deploy them to another machine and place them in a
> different library than that of the dev machine (learned that one the hard
> way :-)

it is likely I dont know what I am talking about, but I have yet to
learn about binding directories because I have not had the need to use
them.  What is the value add compared to organizing your procedures in
a limited number of service programs and then specifying that list of
service programs on the CRTPGM and CRTSRVPGM commands?  I have a
custom build CL for each service program and use the BNDSRVPGM parm to
list the service programs there. Kind of the same thing in the build
CL program that creates all the programs of an application.

Signature violations is what used to confuse me. Once I learned that
*PRV signature support was not worth using and the do's and dont's or
organizing your binding source exports alphabetically, I have not had
much trouble with my service programs.

-Steve