Re: Sharing new stuff?

--- In [email protected], Ron Hudson <hudson.ra@...> wrote:
>
> What is the best/accepted/common way to publish a 
> large body of code?

If you wish to distribute a large/involved product,
then XMIT is the normal method (and used by SHARE).
GCCMVS is an example of that too.

For what you have, I would be more likely to just
zip up the source code and compile JCL and leave
it at that. People can compile it themselves if
they want, and if there is sufficient demand, it
could be added to TK. (I would do this as ASCII).

Or I would create an M4 file in order to produce a 
single JCL deck with the code inline, and distribute
the JCL file. (ASCII too)

Another option would be the same thing that was
used for initobj - use .rvl for the load module.
(ASCII zip file, but the rvl is a binary file)

For a huge distribution, DFDSS is a possibility
too. That's what I used for SEASIK. (DFDSS dump
is EBCDIC, but zipped up with an ASCII readme).
We have a DFDSS clone - DSSDUMP.

BFN.  Paul.