Re: Sharing new stuff?

--------------------------------<snip>-----------------------------

>  
>
> Hi mainframe people,
>
> I have been working on a non-full screen Fortran "Simple Star Trek" 
> program...
>
> It is almost done.
>
> What is the best/accepted/common way to publish a large body of code?
>
> Many things seem to come as JCL file and tape image.
>
> Currently I am compiling from my own fortran PDS to my own loadlib 
> (.load) pds.
>
>
> Ron.
>
------------------------------<unsnip>------------------------------
Ron, without XMIT/RECEIVE capabilities, here's what I'd do:

1. Point the Hercules 00D unit at a PC file.

2. Use IEBGENER to send your source and JCL to SYSOUT=B

3. Issue the Operator command "$spun1" to "punch" the source into the PC 
file designated by 00D. When complete, issue the command "$ppun1".

4. On your PC, build a README.TXT file that describes this process.

5. ZIP the file from 00D and insert the README.TXT file into the archive 
as well.

Did you get the JCL file(s) I sent you previously? I sent directions for 
you to load those files into MVS and those directions should be included 
in the README.TXT file as well.

You can use this same methodology for any card-image file. IND$FILE is a 
fairly old mechanism but it works REASONABLY well. But it olny handles a 
sequential file, not a PDS. To find out if you have it, on the TSO 
command prompt, type "IND$FILE" and hit enter. You'll get either a NOT 
FOUND message, meaning you don't have it, or some other form of error 
message, indicating that it's present but that you improperly invoked 
it. Most tn3270 clients have facilities for doing the file transfer if 
IND$FILE is present.

Rick <mailto:[email protected]?subject=Sharing%20new%20stuff?> 
<mailto:[email protected]?subject=Sharing%20new%20stuff?>