On Wed, 16 May 2018 16:50:43 +0000, Barkow, Eileen wrote: >THANK YOU Lionel! >The TERSE/UNTERSE worked. >Although I think that these utilities should be able to work on their own. > +1
Archivers such as IEBCOPY, ADRDSSU, TRSMAIN, ... should generate portable archives which can be transmitted via conduits independent on the idiosyncrasies of z/OS and its peripheral devices. TRANSMIT and pax get it right. On Wed, 16 May 2018 16:57:30 +0000, Dyck, Lionel B. wrote: >You can easily use TSO Transmit (XMIT) to a dataset thus: > >XMIT x.y DS(input) ODS(xxx.xmit) > >Where x.y is node.userid but that can be anything as it is just going to a >dataset > And, blessedly, RECEIVE verifies or enforces neither the receiving node nor the receiving userid. >-----Original Message----- >From: Barkow, Eileen >Sent: Wednesday, May 16, 2018 11:52 AM > >I was going to try XMIT as a last resort but the TERSE/UNTERSE steps added to >the ADRDSSU jobs worked. >I think that XMIT needs a USERID to send to and there are different userids >involved in each lpar. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
