RE: FTP to UNIX

["Murphy, Guy" <murphy@xxxxxxxxxxxxxxxxx>]

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]


        If you use the binary option then the EBCDIC characters in your file
will not be converted to ASCII.  The file the Unix dudes receive will look
like garbage to them.
        To get rid of those pesky CRLF characters use the old Copy to PC
Document command with transform option of *NOTEXT like  this one: CPYTOPCD
FROMFILE(YOURLIB/YOURFILE) TOFLR(YOURFOLDER) TODOC(YOURDOC.TXT)
TRNFMT(*NOTEXT)
        The *NOTEXT option copies the data without adding CRLF characters.
You can then ftp the PC doc you've created with these ftp subcommands:
        namefmt 1
        binary
        put /qdls/yourfolder/yourdoc.txt


Guy Murphy
murphyfa@uiuc.edu
UDIS at the University of Illinois
217-333-8670
http://www.heisercoaching.com


-----Original Message-----
From: Gord Hutchinson [mailto:ghutchinson@tstoverland.com]
Sent: Thursday, October 31, 2002 1:44 PM
To: midrange-l@midrange.com
Subject: Re: FTP to UNIX


On Thu, 31 Oct 2002 19:32:01 +0000, Martin Rowe <martin@dbg400.net> wrote:


>Are you doing ASCII or BINARY transfer? ASCII will add line endings to
>make the file appear as a text file at the other end, and the iSeries
>defaults to Windows style CRLF endings. What does the other end want -
>just LF (standard Unix) or nothing? Either use BINARY (which gets you the
>'nothing'), or maybe do a CPYTOSTMF ENDLINFMT(*LF) to the IFS first and
>then ftp that.
>

Martin,

Thanks.  I am doing an ASCII transfer.  I don't know why I didn't think of
trying BIN (It's the 'nothing' that they want).

I'll give it a shot.

Gord