Re: copy PS into PDS with RPF?

PROC 0 DEBUG
CONTROL MAIN NOPROMPT NOMSG
IF &DEBUG = DEBUG THEN CONTROL MSG CONLIST SYMLIST
ALLOCATE DD(SYSUT1)   DA('HERC01.SEQDATA.DATA')      SHR REUSE
ALLOCATE DD(SYSUT2)   DA('HERC01.JCL.CNTL(SEQDATA)') SHR REUSE
ALLOCATE DD(SYSIN)    DUMMY                              REUSE
ALLOCATE DD(SYSPRINT) DA(*)                              REUSE
CALL 'SYS1.LINKLIB(IEBGENER)'
FREE DD(SYSUT1 SYSUT2 SYSIN SYSPRINT)
EXIT

Assume the above is stored in HERC01.PDS.CLIST(MIKE)

Invoke at READY prompt with:

EX 'HERC01.PDS.CLIST(MIKE)' 'DEBUG'

the DEBUG part is optional.

The above example assumes both datasets pre-exist.

To allocate an output sequential dataset use this instead:

ALLOCATE DD(SYSUT2) DA('HERC01.OUTSEQ.DATA') NEW REUSE     +
                     TRACK SPACE(10 5) DSORG(PS) RECFM(F B) +
                     LRECL(80) BLKSIZE(6160) CATALOG

So yes;  The output can be a sequential dataset.

ScottC

--- In [email protected], Mike Stramba <mikestramba@...>
wrote:
>
> Gerhard,
>
> I've tried to setup CLISTS, with parameters to JCL procedures, and
> haven't been able to figure out the syntax of the parameters / quoting
> brackets etc.
>
> Can you "CLIST" the example below?
>
> thx
>
> Mike
>
> > have the requirement or preference to do it in TSO, the above If
> > can be encapsulated in a CLIST (e.g., define a PROC with an
> > obvious, but unique name, such as COPY, and use either two
> > positional or two keyword parameters for the in and out names).
>
> On 8/7/10, Gerhard Postpischil gerhardp@... wrote:
> > On 8/7/2010 12:08 PM, Mike Stramba wrote:
> >> So
> >> " pds atc01.asm cop lib1.asm(atc) "
> >>
> >> is a lot easier to remember / (type one line) use than :
> >>
> >> ALLOC FI(SYSUT1) DA('input-ps-dataset') SHR
> >> ALLOC FI(SYSUT2) DA('output-pds(membername')) SHR
> >> ALLOC FI(SYSIN) DUMMY
> >> ALLOC FI(SYSPRINT) DA(*)
> >> CALL 'SYS1.LINKLIB(IEBGENER)'
> >
> > As usual, there are a number of distinct ways of doing things.
> > In my case, I have canned JCL for everything I need regularly,
> > and then some. Usually requires changing one or two names. I
> > have the requirement or preference to do it in TSO, the above If
> > can be encapsulated in a CLIST (e.g., define a PROC with an
> > obvious, but unique name, such as COPY, and use either two
> > positional or two keyword parameters for the in and out names).
> >
> >> .. On the other hand, IEBGENER, is "standard", and I assume pds
> >> is an
> >> optional program (is it the 'pds' from the cbt tape?
> >>
> >> E.g. I haven't found 'pds' in TSO while working on OS390 r8 or zos
> >> 1.4 systems, so I guess that's where your "generic" solution will
> >> work. (I'll try it on both).
> >
> > PDS is the greatest thing since sliced bread <G>. Go to
> > www.cbttape.org and download a copy for your OS/390 and later
> > systems before you forget <g>. There's even a version for MVT if
> > you want even older system stuff.
> >
> > Gerhard Postpischil
> > Bradford, VT
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>