Hi Rob,

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


Fun stuff, although I had some problems with his example due to ccsid differences.

*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

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].