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.

If the delimited data is properly formed, then even with no-value delimited data elements, the CPYFRMIMPF should be able to properly import the stream records as database rows\records. The parameter specification of RPLNULLVAL(*FLDDFT) should be specified on the CPYFRMIMPF in order to request replacement of the null values with the field default, for when null values are not supported in the target database file.

Regards, Chuck

James H. H. Lampert wrote:

<<SNIP>>

It looks like unless the customer comes up with a way to do it themselves, I'll be using Scott's methods: CPYFRMIMPF managed to
get 684 good records out of the first 2000 or so (of some 300000)
before it crashed my terminal session with a joblog full of data
mapping errors. So it's clearly a bit more than CPYFRMIMPF can
handle. I think (based on some of the error messages) that it's
interpreting two fenceposts together as a null field (which the
file doesn't allow), rather than a blank (or perhaps zero) one.

Ye vish, that 520 is fast! I've never seen a terminal session
fill its joblog that fast.

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.