Re: copy PS into PDS with RPF?

Rick,

While I thrive on learning new stuff, sometimes I actually want to
*use* a command / utility for something (quasi) useful ;)

My primary goal was to try to assemble a 3270 program.
-- Secondary goal was to copy the source into the pds

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

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

thx

Mike




On 8/7/10, Rick Fochtman <[email protected]> wrote:
> -----------------------------<snip>--------------------------
>
>>
>>
>> Is there an RPF / TSO command to copy a PS into a PDS?
>>
>> I've looked through the RPF menus, tried to use it's copy command, but
>> it said the source was not a PDS.
>>
>> I started up the PDS command from TSO, but dont' see anything.
>>
>> So do I need to do the (dreaded) JCL / + some utility ? ;)
>>
> ----------------------------<unsnip>---------------------------
>  From TSO READY prompt you can do this:
>
> 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)'
>
> or you can do this from batch:
>
> //  job statement
> // EXEC PGM=IEBGENER
> //SYSPRINT DD SYSOUT=*
> //SYSIN        DD  DUMMY
> //SYSUT1     DD  DISP=SHR,DSN=input-ps-dataset
> //SYSUT2     DD  DISP=SHR,DSN=output-pds(membername)
>
> There's no reason to "dread" the utilities; they're your "friends in
> need" and can save a LOT of headaches.  :-)
>
> JCL gets much easier with practice; just learn to treat it as a new
> language and you'll pick it up much faster.
>
> Where most "newbies" get tangled up is in over-specifiying JCL parameters.
>
> I haven't checked lately but if you can find the site
> <www.mvs-training.com>, they publish a book titled "OS.390 MVS JCL Quick
> Reference Guide", by Olivia R. Carmandi (ISBN 1-892559-06-4) that's a
> good learning aid for JCL. If you can't find that link, try going
> through <www.diversifiedsoftware.com> You might also be able to find it
> on AMAZON; it's not expensive but for a newcomer to the world of MVS JCL
> it can be a real lifesaver. Just beware: there are features of OS/390
> and z/OS JCL that aren't available in MVS 3.8.  Like everything else in
> the world of mainframe computing, evolution adds new features and
> changes old ones.
>
> Rick
>