Re: CRTCSVF vs CPYTOIMPF

Hi Rob,

You might want to take a look at Scott Klement's article in System iNetwork for 08/14/2008:

http://systeminetwork.com/article/write-your-own-custom-csv-export-utility-without-apis

Fun stuff, although I had some minor problems getting his example to work due to ccsid differences, and to my ignorance of QShell scripting syntax.

*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /

rob@xxxxxxxxx wrote:

I'll just stick with processing the IFS directly. One of the problems we were having was a feed file into BPCS. And, on occasion, some clown on the shop floor would enter a part into the PC based mixing package that had a 16 character item number. Which, earlier versions of BPCS only supported 15 characters. Well, when one did a CPYFRMIMPF it would hurl and it was very time consuming to find the error. Now we can post the successful ones into the posting file and leave the unsuccessful ones. The unsuccessful ones then go into a report to be handled manually.

Once you've done an IFS program, using Scott Klement's handy tutorial, it's a good tool to have in your belt.

The SQL utilized in CPYFRMIMPF and CPYTOIMPF (run them in debug!) was bizarre and probably one of the performance killers of those commands.
Those commands belong to the database team.

Rob Berendt