In the wild, scp and sftp are binary protocols. Most implementations don't do any conversion for either. The problem is that there isn't anything in the packet specs for these protocols to indicate conversion, codepages, etc.
IBM chose to make sftp binary (but there is a switch in the z/OS sftp client to do conversion) and for scp (on both the z/OS client and server) to always do conversion. IBM's scp and sftp implementations also don't support MVS data sets, JES spool files, etc, etc. For a complete z/OS implementation of SFTP for z/OS, you can use Co:Z SFTP <http://dovetail.com/products/sftp.html> with IBM Ported Tools OpenSSH. Kirk Wolf Dovetailed Technologies http://dovetail.com On Mon, Nov 2, 2015 at 5:12 PM, Paul Gilmartin < [email protected]> wrote: > On Mon, 2 Nov 2015 16:07:13 -0700, Jack J. Woehr wrote: > > > >> What can you cite for your notion of "the original design" > >The -r switch for copying whole directory structures. > > > >Whereas ftp/sftp has always had the binary/text dichotomy, scp has never > had such a switch. > > > >Ergo, it's designed for binary transfer. > > > Did you read the article about Goodman? > > At least the default for ftp has always been to convert from the character > set of > the originating system to that of the receiving system. Scp is merely > agreeing > with the default behavior of ftp. > > Use sftp. > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
