Pinned topic An migrating-alternative for RD&T client-/server-utility
JonathanEosze 0600012D2R3 PostsACCEPTED ANSWER
Re: An migrating-alternative for RD&T client-/server-utility2013-10-06T05:02:01Z in response to JL2013
To copy things between z/OS on RDT (the latest name for RDz-UT), and z/OS not on RDT, you can use any TCP/IP based transfer method. If you are a fan of using ADRDSSU, FTP'ing it from one z/OS image to another, and restoring the dump, then do it. It works just like you would expect when do such a transfer between any 2 z/OS images. And yes ADRDSSU can dump and restore the type of data you have listed. You can specify VOLSERs and/or Dataset names (with wildcards if you want). I've heard other shops say that they needed to make sure DB2, etc, was down before they could perform a copy for various sync issues.
However, you need to have some way of transferring data from one z/OS image to the other. If need be, you could use several hops to get from one to the other, including the Linux server an RDT instance is running on, just like you can use several hops to move files around between Linux or Windows servers.