× 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.



Mark,

I would certainly give it a try. We do a Bajillion imports using tab-delimited text files from various sources. So many that I have an RPG program that reads a directory and runs CPYFRMIMPF for each matching streamfile. That uses RCDDLM(*ALL) and I rarely have issues.

You could do something similar using Vern's logic - try *ALL, on error then *CRLF, etc.

Maybe I've just been lucky? But I've been using it that way over 10 years with good results. Honestly, the only time it fails is when the source fails to scrub CR and LF from actual data (along with special characters, emojis, and other extraneous crap).

Good luck!

Greg

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of mlazarus
Sent: Thursday, December 14, 2023 7:11 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [EXTERNAL] Detecting *CRLF vs. *LF

Greg,

I seem to recall having some trouble with that option. I'll need to play with it a bit more.

-mark

On 12/14/2023 4:17 PM, Greg Wilburn wrote:
Why not use RCDDLM(*ALL)?

It recognizes either *CRLF or *LF

-----Original Message-----
From: MIDRANGE-L<midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
mlazarus
Sent: Thursday, December 14, 2023 1:00 PM
To: Midrange Systems Technical
Discussion<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] Detecting *CRLF vs. *LF


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.