Why not build the object code for the open source packages
using the UNIX file system etc. (and makefile, if you like)
and only put your own code which makes these things available
to your onsite callers in PDSes? I believe that there is no need
to put the open source packages into your home grown SCM system.
As there will be no "normal" maintenance to them, this doesn't make
sense, IMO.
This is what we do ...
we then link the open source "object code" to the gateway functions
that make it available to our onsite callers, and only the gateway
functions (which is code of our own) it put into our (also home grown)
SCM systems. (Or: we call the open source objects dynamically, BTW).
The open source code used is of course archived, too, but not in
our SCM system. In the worst case: because it's open source,
you always can retrieve it again from outside ...
Kind regards
Bernd
Am 03.08.2013 10:46, schrieb David Crayford:
IMO, using PDS data sets for open source software packages is going to
be a lot of extra work for you. It doesn't make sense to me but I'm
sure you have your reasons. It's easy to build
PDS load modules from UNIX but if you must you can do so with JCL.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
