On Thursday 31 October 2002 6:33 pm, Gord Hutchinson wrote:
> I am FTPing an 80 column file to a partner's (USBank) Unix FTP server.
> They are complaining that after column 80 is a carriage return/line
> feed.  The CR/LF is not imbedded in the data - it is being inserted
> after the end of each 80 column line.  I have been told that this is a
> 'feature' of FTPing between the iSeries and Unix.
>
> I am FTPing the file from the 'normal' QSYS file system.
>
> Is there anything I can do to drop the CR/LF either on the iSeries or
> in FTP?

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.

I have a similar problem where I ftp source code (generated or downloaded
on Windows) to our AS/400 from my Linux box in ASCII mode. The transfer
strips the LFs, but the source member has CRs after the last non-blank
character on each line - it doesn't show up until the SEU syntax checker
complains or the compile fails. Mind you, it's trivial to convert betwenn
ending on a *nix box, so I wonder why they have a problem with it.

Regards, Martin
--
martin@dbg400.net  jamaro@firstlinux.net  http://www.dbg400.net    /"\
DBG/400 - DataBase Generation utilities - AS/400 / iSeries Open    \ /
Source free test environment tools and others (file/spool/misc)     X
Debian GNU/Linux | ASCII Ribbon Campaign against HTML mail & news  / \



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.