Re: Compile and run later

You can list the members of a pds from the TSO Ready prompt (or option 6 in RPF) with this command:

LISTD dsname MEM

So for instance, here the command:

listd test.load mem

Produces:

 HERC03.TEST.LOAD
 --RECFM-LRECL-BLKSIZE-DSORG
   U     **    19069   PO
 --VOLUMES--
   PUB000
 --MEMBERS--
   LISTM
   TEST01
   UKJUPUT
 READY 

To actually execute the load module, you can use the TSO command

CALL dsname(membername)

But!! if any datasets will be read or written, including SYSIN or SYSPRINT, you will need to allocate each of them before hand using the TSO command ALLOC.

If we're still talking about a FORTRAN program, then you probably
need to do these:

ALLOC DD(sysin) DA(*)
ALLOC DD(sysprint) DA(*)

Plus for each unit number used in a write or read statement, you must allocate something. So if you use unit 6 to print messages, you need something like:

ALLOC DD(ft06f001) DA(*)  [to print to your screen]

or

ALLOC DD(ft06f001) DA(filename) [to print to file 'filename']

Use 'help allocate' for more details about the ALLOC command. It is the TSO equivalent of the DD statement in JCL.

The FREE command (see 'help free') is used to release files from allocation. This happens automatically when you log off in any case.


--- In [email protected], Ron Hudson <hudson.ra@...> wrote:
>
> On Tue, May 18, 2010 at 9:16 PM, scott <svetter@...> wrote:
> 
> >
> >
> //LKED.SYSLMOD  DD  DSN=youruid.LINKLIB(pgmname),DISP=(,CATLG,DELETE),
> > //     UNIT=SYSDA,SPACE=(CYL,(3,,10)),
> > //     DCB=SYS1.LINKLIB
> >
> > I susspected It was something like that - I now have a new PDS (I think
> it's a PDS)
> but I cant 'E' it in RPF menu 3.4 to verify it has a member named "Grid"
> 
>    HUDSON.DATA.DATA           PUB002 10.138 PO   FB      80  3120   1   300
> 299
>    HUDSON.FORT.FORTH          PUB000 10.138 PO   FB      80  3120   1
> 30    5
>    HUDSON.LINKLIB             MVSCAT 10.138 PO   U        0 32760   1
> 45   44
>    HUDSON.PROG.PL1            PUB002 10.133 PO   FB      80  3120   1   150
> 149
> 
> So, How do I run it now?
>