Re: Importing fencepost-delimited ASCII data -- 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.

CPYFROMIMPF

or roll your own using the IFS API's.

If the files are as clean as you say, and this is a one-time process,
I'd stick with CPYFRMIMPF.

Charles

On Fri, Jan 15, 2010 at 2:49 PM, James H. H. Lampert
<jamesl@xxxxxxxxxxxxxxxxx> wrote:

It appears that I may soon find myself having to import a whole file of
fencepost-delimited ASCII data into DB2/400 files.

The file formats are known, in fact we have files that *should* be in
the target format.

The ASCII stream files appear to start with a line of field names.
Fields are delimited with ASCII fenceposts ('|', hex 7C), and records
are delimited by CRLF (hex 0D0A).

Two of the files are over a gigabyte; the third is over 300 megabytes.

Any suggestions on the most painless way to deal with this mess?

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

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.