The problem with the ³Oh, sftp handles binaries² position is that
1. It does not address scripts already written to use scp which are broken
in relation to zOS and USS.
2. sftp does not support the same command line as scp, and therefore is not
a one-to-one replacement in terms of usage.
The stem is the fact that commands used on the ssh command line need to be
translated before sending them over to the other system, but in terms of
file transfer, this is the only system that alters the data on its way
through; no other Unix system does this. I understand the need for it in
passing commands, but beyond that, it should have left data alone.
Having said that, at this point, there has been new code written that now
depends on the way it works today, so changing it, while making it more
compatible with the rest of the world, is probably not possible. It just
becomes one more reason to avoid USS as a platform. I¹ve never much cared
for zOS anyway, and this just ices the cake, so to speak.
--
.~. Robert P. Nix Mayo Foundation
/V\ RO-OC-1-13 200 First Street SW
/ ( ) \ 507-284-0844 Rochester, MN 55905
^^-^^ -----
"In theory, theory and practice are the same, but
in practice, theory and practice are different."
> From: "McKown, John" <[EMAIL PROTECTED]>
> Reply-To: Linux on 390 Port <[email protected]>
> Date: Tue, 20 Feb 2007 12:34:17 -0600
> To: <[email protected]>
> Conversation: scp question.
> Subject: Re: scp question.
>
>> -----Original Message-----
>> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
>> Behalf Of Malcolm Beattie
>> Sent: Tuesday, February 20, 2007 12:25 PM
>> To: [email protected]
>> Subject: Re: scp question.
>
> <snip>
>
>> Here's some more rather surprising behaviour, using just ssh:
>> thinkpad% echo -n ABC | ssh zos 'od -t x1'
>> 0000000000 C1 C2 C3
>> 0000000003
>> So the three bytes (0x41, 0x42, 0x43) sent by the ssh client end up
>> being read on stdin by od as 0xc1, 0xc2, 0xc3, i.e. converted from
>> ASCII to EBCDIC. There's no scp there, just a stream of bytes to move
>> around.
>>
>> --Malcolm
>
> Erin Farr of IBM has answered the question: "Why?" over on MVS-OE.
>
> <quote>
> sftp treats all files as binary by default so that should work for
> you. There are a handful of places we are forced to be different than
> the
> rest of the world thanks to the nature of handling EBCDIC. The IETF
> SSH
> RFC's and drafts did not have to be concerned with data conversion.
> OpenSSH doesn't doc anything about it because they didn't have to be
> concerned with it either. So, scp calls ssh with an "exec" channel,
> which
> is also used for remote command execution with ssh. The RFCs don't
> allow
> us to convert for one and not the other. Not doing ascii-ebcdic
> conversion
> for remote command execution is the worse of two evils, especially when
> binary transfer is available with sftp. Maybe we need a section in the
> book to better doc these differences.
>
> -Erin
> Unix System Services and Ported Tools Development
> </quote>
>
> --
> John McKown
> Senior Systems Programmer
> HealthMarkets
> Keeping the Promise of Affordable Coverage
> Administrative Services Group
> Information Technology
>
> The information contained in this e-mail message may be privileged
> and/or confidential. It is for intended addressee(s) only. If you are
> not the intended recipient, you are hereby notified that any disclosure,
> reproduction, distribution or other use of this communication is
> strictly prohibited and could, in certain circumstances, be a criminal
> offense. If you have received this e-mail in error, please notify the
> sender by reply and delete this message without copying or disclosing
> it.
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
