You need to DFDSS or FDR dump the PDSE then transfer it and then restore it to guarantee integrity.
-------------------------------------------------------------------------- Lionel B. Dyck (TRA Contractor) Mainframe Systems Programmer Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI&T Service Delivery & Engineering -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tom Marchant Sent: Friday, September 16, 2016 8:18 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: PDS/E Cobol On Fri, 16 Sep 2016 02:39:15 +0000, Jesse 1 Robinson wrote: >I don't think an 'interim' data set will solve the problem. > >DSN(A) --> DSN(B) --> DSN(C) > >Whether DSN(B) belongs to SYSA or SYSC, there is still the same problem of >crossing sysplex boundaries on one copy or the other. > >The transfer needs to be 'DSN free'. Right. Program objects support new things that cannot be included in a load module. For any such program object, you can't copy it to a PDS. You can copy it to a Unix file, but that doesn't really help thbe situation. -- Tom Marchant ---------------------------------------------------------------------- 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
