Re: Re: Sharing new stuff?

On Sat, Jun 5, 2010 at 5:36 PM, kerravon86 <kerravon86-/[email protected]> wrote:

>
>
> --- In [email protected] <turnkey-mvs%40yahoogroups.com>, 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.
>

I guess XMIT is something I have to install.

>
> 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).
>

Actually it's a single fortran source file, I even included
the random number generator as a bunch of comments
for those who aren't set up with a SYS2.FORTLIB

: ^ )

How do I create a tape with just that source on it?
Or dump it to "Cards"?

Right now I can "Print" it, I have the JCL to take
a random FB80 member of a PDS to the printer.




>
> 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)
>
> huh? what is this M4 you speak of?
(The linux pre-processsor?)



> 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.
>
>  
>