🚀 go-pugleaf

>>>>> "tonij67" == tonij67  <tonij67@hotmail.com> writes:

    tonij67> Wierd problem going on here: I need to transfer files to a
    tonij67> OS/390 machine from a Solaris machine.  I use scp for a whole
    tonij67> lot of transfers every day with no problems so it seems like
    tonij67> the obvious choice. (I am using OpenSSH 4.3p2) We have been
    tonij67> having problems in that every time we send a ZIP file to this
    tonij67> z/os system, they are unable to decompress it.  i.e. its
    tonij67> corrupted.

    tonij67> I can send zip files to every other machine on our network,
    tonij67> and even a few machines on *their* network, all different
    tonij67> platforms.  The only one that has issues is this one OS/390.
    tonij67> I suggested they investigate the verison of SSH they are
    tonij67> running and they told me that scp expects all files to be
    tonij67> text, so the only way for this to work is for us to use sftp
    tonij67> instead of scp.

    tonij67> So I am just scratching my head here...all of the reading I
    tonij67> have done has lead me to believe that scp doesnt even *HAVE*
    tonij67> a text/binary mode, that its always binary.

    tonij67> Anyone have any idea what gives here?

Scp does not behave differently depending on the contents of a file: it
simply transmits the bytes in the same order over an SSH channel.  Since
both the file and the channel are byte-oriented, this is a well-defined
operation.  However: what the server-mode scp on the remote side is going
to do is a different story.  Copying files between different kinds of
filesystems is often *not* a well-defined operation.  If you're copying to
an existing file on a filesystem with forks, do you overwrite one fork
(and which one if there are already more than one?), or do you dump the
data into a new fork?  If you're copying to VMS, which of the 4 or 5 file
types supported by RMS (record management services) do you create?  Etc.
Scp has no way way of communicating or handling these kinds of differnces.
If the OS/390 filesystem has types that don't map well (or obviously) onto
UFS, this may be the problem.  It will come down to what
open()/create()/... in libc on the 390 actually do.

sftp may work better depending on the implementation, because the SFTP
protocol does have a notion of text files as a type and conversion to
handle different host representations.

-- 
  Richard Silverman res@qoxp.net