×
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.
On 07-Nov-2015 13:07 -0600, midrange wrote:
<<SNIPped about writing a program to import the data>>
If you are not comfortable with that, build a native file with one
field for xx,xxx bytes (bigger than any possible record, and then
CPYFRMIMPF FROMSTMF('/XXXF/YYYYYY/ABCDEBU.TXT')
TOFILE(FLATFILE) MBROPT(*REPLACE) +
RCDDLM(*CRLF) RPLNULLVAL(*FLDDFT)
May have to adjust for whatever record delimiter.
Then push each record into correct data structure (if fixed width
columns).
The DB Import feature [the Copy From Import File (CPYFRMIMPF)
command] is used to copy data into a /described/ file, not into a flat
file. So it seems, the above invocation surely will be of little help
for the scenario of the OP?; i.e. presumably having the effect of either
1) merely copying the first field of delimited data into the
[effectively one field of the] flat-file, or 2) effecting what is
essentially the same as what a Copy To Stream File (CPYTOSTMF) for which
the effect is little more than a straight-up copy of the /records/ with
the only transformation other than CCSID translation, but the import
feature will not even do the xlate because a flat-file is defined as *HEX.
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.
midrange.com
