On Mon, 28 Dec 2015 14:08:37 -0600, Kirk Wolf wrote: > >I'm not sure if an ssh invocation of pax like this works in all cases. >Certainly z/OS to non-z/OS it would not work since, by default, ssh exec >sessions are translated EBCDIC/ASCII and vice versa in the z/OS OpenSSH >implementations. I would have to check, but this seems unlikely to be >binary-clean zOS->zOS. We've argued this before, right? > I don't know that we have much to argue about as long as we agree that EBCDIC creates problems in a predominantly ASCII world.
And in the z/OS -- non-z/OS instance, I deal with the confrontation by adding a suitably crafted iconv in a pipe on the z/OS side. And (only) z/OS pax has elaborate facilities for ASCII<->EBCDIC on the directory side, but not on the archive side. The bad news is that IBM REJected my SR when I reported that when pax converted a file tagged IBM-1047;NL to UTF-8, it converted the NLs to LFs but the tag became UTF-8;NL. Should have been UTF-8;LF. >The good news is that with this APAR: >https://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.foto100/soc4q15.htm > A christmas present. Is it under control of the individual user, or only the administrator: >z/OS V2R2 OpenSSH can now customize which kinds of channels are converted, >using the "ChannelConvert" option and omitting "exec" from the list. >Assuming that you use portable PAX/USTART file formats, you could use this >to send filesystems z/OS<->non-z/OS. > "exec"? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
