> I don¹t buy it, because sftp is also based on ssh, > yet it does what it¹s documented to do. ...
You're right about SFTP. I had forgotten. Makes me wonder if, under the covers, the z/OS SSH can turn off its translation feecher. > Translating the command on the ssh line is the correct thing to do, > but munging all the data that the command acted on is not. It¹s a huge, > and incorrect, assumption that everything you might want to copy > will be text. Java class files are a prime example. These get > ³scp²ed around commonly in the real world, ... I first encountered OpenVM (the CMS counterpart to USS) in 1995. I was so excited! All the standard Unix tools were there. So I brought in a TAR file of my stuff and cracked it open and found my shell scripts to not work. Weird. Eyeballing one, I was SHOCKED to see garbage, and immediately realized it was ASCII and OVM EBCDIC. I remained in shock for probably 7 months. Took that long before I warmed up again to OE. But now I love it! And I realize that OpenVM and USS *must* be EBCDIC. But yeah, we have a problem. You mention Java class files copied around. For me, a killer is NFS mounting: to translate or not? Might seem easy: If text then translate, or if executable not. But what about directories with mixed content? No easy solution. ... > You can only use the USS scp command to handle text files, and how long has > it been since we only dealt with text files? Back into the 60¹s? If ever? > USS scp is a useless command, because the results will not mirror what you¹d > expect on other Posix compliant systems. What would you expect from Apache on USS? Is it supposed to translate or not? -- R; ---------------------------------------------------------------------- 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
