Re: Compile and run later

   Well the better choice would have been using a scripting language
such as CLIST.  The problem with COBOL, FORTRAN, and the like is that
they were designed to be used as the batch programming language or used
inside of the OLTP facility called CICS.


   When you compile the COBOL program used the JCL procedure COBUCL and
add at the end an override to store the executable.  Use the JCL
override of, and this creates a new dataset and once created can be
reused by other programs (with modifications).
//LKED.SYSLMOD  DD  DSN=youruid.LINKLIB(pgmname),DISP=(,CATLG,DELETE),
//     UNIT=SYSDA,SPACE=(CYL,(3,,10)),
//     DCB=SYS1.LINKLIB

In the above JCL change the pgmname to whatever you want to call your
program.  Also replace the youruid with your userid.

Once you get to this point done successfully, we'll go on to the next step.

On 05/18/2010 11:22 PM, Ron Hudson wrote:
>
>
>
>
> On Tue, May 18, 2010 at 7:45 PM, scott <[email protected]
> <mailto:[email protected]>> wrote:
>
>      
>
>     What language do you want to use?
>
>     Scott
>
>
> I am better at fortran than any of the others, then Cobol. 
>
> I basically know what an assembler is - and I have the listings of the
> instructions (but none of the 'system calls' or 'i/o routines'. So
> that would
> be the hardest choice.
>
>  
>
>
>
>     On 05/18/2010 10:33 PM, Ron Hudson wrote:
>>     Hey all,
>>
>>     I would like to start creating programs that I can run from a TSO
>>     session, interactively.
>>
>>     I am thinking I need to write the output of the link editor to a
>>     file so it can be run
>>     when needed.
>>
>>     Where do I look for examples of this?
>>
>>     Thanks.
>>
>>     Ron.
>
>
>
>
>