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

Reply via email to