Re: Copying a CSV file to iSeries as bar delim flat file

+1

IMHO, in the case of the CPYTOIMPF/CPYFRMIMPF command "enhancements",
IBM forgot their long-standing promise to the AS/400 - iSeries - System i - Power community,
which was always represented to me as:

'We will preserve your investment in your existing software'

Which I always took to mean that for the most part, you don't experience the pain that software developers on other platforms (particularly Windows) experience when migrating your software to a new release/version of the O/S.

i.e., you don't have to rewrite your code every time IBM comes out with a new release.

- sjl


Rob wrote:

(as if Rob could avoid piping in...)

No, you're just dealing with the "enhancements" IBM keeps adding to
CPY...IMPF over the last several releases. They keep changing how they
handle CCSID and what not. You have to read the Memo To Users for each
release if for no other reason than to keep up with how they change the
workings of this. Many have abandoned the CPY...IMPF commands and have
resorted to processing stream files directly from RPG. One reason is
because of IBM's monkeying around with it. Another reason is because it's
faster than IBM's command. A big reason is that you have better control
of the granularity. For example, if you do a CPYFRMIMPF to a DB2 file and
row 3124 dies because the item number in column 4 is larger than the item
number column in your database (been there, seen that) it can be a real
peach trying to track that down. If, however, you roll your own you can
customize your exception report to your hearts content.

See also:
http://www.scottklement.com/rpg/ifs.html

But if you insist on hacking on that log perhaps someone can offer some
suggestions as to what CCSID your stream file should be and what CCSID
your DB2 file should be.


Rob Berendt