× 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.



Yeah, CPYFRMIMPF is one of the most buggiest IBM command I've ever
encounter.

<rob@xxxxxxxxx> wrote in message
news:<mailman.14413.1222779203.2545.rpg400-l@xxxxxxxxxxxx>...
Let's not assume that IBM can write their command programs any faster
than
your average RPG programmer. Using Scott's IFS tutorial has shown me
that
we can often blow the socks off of IBM. His IFS stuff is much faster
than
CPYTOIMPF or CPYFRMIMPF. Then again, if you ran either of those
commands
underneath debug you would see some intense SQL going on.

Then again, there's not just speed, but granularity to consider. What

happens, if on record 2,125,432 if there's a constraint violation or
some
such thing? With RPG your write fails, you write it to an exception
report instead, and maybe a file to be reposted. (Well, as long as
you're
not like some clowns who assume that any write violation means that
the
record exists and you try an UPDATE instead.)

Another thing to consider, if the source files can be read in key
order,
you may not get the blocking on the output to the summary file, but
the
summary file will then be in key order. Well, if you really want to
ensure output in key order, perhaps some matching records logic,
either by
cycle or by hand. That might help the speed of using the summary file

afterwards. Then again, that could easily be fixed by RGZPFM
keyfile(...)
to sort the file afterwards. But if it is one of those 24x7 files...

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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.