Hi,
Just to clarify the behavior of OpenSSH on z/OS:
- scp treats files as text. Specifically, it assumes all network data is
Latin-1 (ISO8859-1.) This is because scp uses the same "channel" as
remote command execution, for which translation needs to occur. - sftp
treats files as binary (no conversion occurs.) However, as Kirk
mentioned, there is a client side "ascii" subcommand, which basically just
saves you from having to do a separate iconv. In other words, no nl/cr
handling is done.
It's true that OpenSSH's scp on other platforms does not convert data. It
assumes it is communicating with another ASCII platform so it does not do
any translation anywhere. As an EBCDIC platform, we then need to assume
we are communicating with an ASCII platform. There is nothing in the
OpenSSH RFC's which allows declaration/negotiation of the coded character
set of the session data.
Erin Farr
z/OS UNIX System Services Development
----------------------------------------------------------------------
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
