Re: SQL to read CSV file -- 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.

Which is why I suggested using an Open Access Handler to read the CSV directly.

I already posted the links but if you missed them you'll find them in this collection:

https://authory.com/JonParisAndSusanGantner?collection=Open-Access <https://authory.com/JonParisAndSusanGantner?collection=Open-Access>

Jon Paris

On Jun 18, 2021, at 2:15 PM, Justin Taylor <jtaylor.0ab@xxxxxxxxx> wrote:

That would work too, but I'm loathe to create temp work files.

Thanks

date: Fri, 18 Jun 2021 06:24:19 +0200

from: "D*B" <dieter.bender@xxxxxxxxxxxx>
subject: Re: SQL to read CSV file

<Justin>
I'm trying to get SQL to read a CSV file and output the parsed results. I
can read the CSV with QSYS2.IFS_READ, but that only gives one column with
the CSV all ran together. SYSTOOLS.SPLIT will parse a single CSV value,
but I can't get it to take the IFS_READ as input.

Am I just trying to accomplish too much in a single step?

TIA
</Justin>

That's what CPYFRMIMPF is made for!

D*B

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com

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.