On Thursday, 02/22/2007 at 08:46 CET, Rob van der Heij <[EMAIL PROTECTED]> wrote: > With the CMS FTP client download the text file from a non-mainframe > server you're slightly better off because the ASCII LF does have an > EBCDIC code point. So when you made a mistake you can sometimes get > out of that by > pipe < bad file a | deblock linend 25 | strip trailing x0d | > good txt a > > In fact, I used to FTP always binary from Linux to VM and did the > translation myself with a pipeline (because the network folks did not > listen and failed to see that STANDARD means wrong in VM TCP/IP). But > that way I got my square brackets and curly braces in proper state to > exchange files.
For an RFC-compliant text mode FTP transfer, use the xlate option for either the client or the server, as appropriate, to control translation. You just need to know the ASCII and EBCDIC code page numbers. Details on the various translation tables are in Chapter 30 of the TCP/IP Planning book. Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- 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
