Re: Importing fencepost-delimited ASCII data

Doesn't appear to be too bad if the data is constraint. Use IFS Api's to
open and read record by record then just a tokenizer to break into
individual strings. I have a tokenizer I wrote if you are interested
although a lot of people have them.

If my experience the trickee part is dealing with missing or bad data.

On Fri, Jan 15, 2010 at 12: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.