Re: Challenges using service programs, binding directories, etc.

Hi John -

On Tue, 18 Aug 2015 17:10:18 -0400, John Yeung
<gallium.arsenide@xxxxxxxxx> wrote:

Right now, I'm still tethered to PDM/SEU, and I really like just being
able to issue option 14 (with preferably no parameter futzing) to
build anything. I could certainly map a custom PDM option to MAKE and
be just as happy, if not happier (since I imagine I only have to issue
MAKE once for a whole program, not once for potentially each object
that needs to be compiled and linked into that program).

For the *PGMs that use *SRVPGMs, you can make that happen with binding
directories (that can be specified on an H-spec [preferably via a
/copy member IMO]).

For creating the *SRVPGMs, I use PDM option 15 (which creates a
*MODULE) followed by a custom PDM option that calls a CL program that
does a CRTSRVPGM with the parameters the way that I want them.

I used to have to have custom code for my few multi-module service
programs, but IBM added binding directory capability to CRTSRVPGM so
that need went away.

I have my standard binding directory for my *PGMs to access my
*SRVPGMs, and a special binding directory for CRTSRVPGM that contains
the entries needed to build my multi-module *SRVPGMs without the need
to specify all of the modules on the CRTSRVPGM command.

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.