Actually, FTP of a member from z/OS to z/OS were none of the datasets are physically shared should work just fine.
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Lizette Koehler > Sent: Thursday, September 15, 2016 1:27 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: PDS/E Cobol > > I would probably use an interim dataset so that there is no potential for > PDS/E Corruption. > > OP did not indicate the environment or more specifics that Shared Dasd, FTP. > Sounds like they have a process that uses FTP to move programs from one > system to another but using Shared Dasd. I would consider using an interim > dataset to keep PDS/E Corruption to a minimal chance. > > Copy from Original library to interim file FTP interim File Copy from Interim > file to Production Library > > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > > On Behalf Of Paul Gilmartin > > Sent: Thursday, September 15, 2016 10:48 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: PDS/E Cobol > > > > On Thu, 15 Sep 2016 10:26:53 -0700, Lizette Koehler wrote: > > > > >You can use normal utilities to copy a PDS/E member to another place. > > > > > >TRSMAIN, > > >TSO XMIT/RECEIVE > > >IEBCOPY Unload > > > > > May require parallel sysplex. But no need to unload; can IEBCOPY from > > PDSE to PDSE. > > > > >DFDSS Dump/RESTORE > > > > > >If you are using PDS/E Generations, there are some challenges with that. > > > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
