Re: FTP from unix/linux system causing EOL issues -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: FTP from unix/linux system causing EOL issues
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 15 Feb 2023 07:51:34 -0700
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

In PASE:

*tr -d '\r' <input.txt >output.txt*

Ladies and gentlemen, all these problems were solved in the 1970's in Unix.
Get to know your IBM i Unix-like environment!

On Wed, Feb 15, 2023 at 12:30 AM Don Brown via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

After ftp'ing the file directly to a physical file we have a end of line
character of hex 0D

We have added some code to replace the hex 0D with a blank and this has
enabled the file to be processed but I have not been able to find any
other option.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: FTP from unix/linux system causing EOL issues , Roger Harman

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.