How about ditching CPYF in favor of an SQL statement?


On Fri, Apr 27, 2012 at 3:23 PM, David Gibbs <david@xxxxxxxxxxxx> wrote:
On 4/26/2012 5:03 PM, CRPence wrote:
The CPYF utility has some bit of "optimizer" logic whereby one means
 of copy is chosen over another.  One part of the logic, at least for
the FromFile, is whether there are any locks on the data; i.e. no
data locks follows one path, any data locks [beyond its own] and
another path is followed.  If no locks, the CPYF escalates its locks
[beyond just *SHRRD] to use a more aggressive approach to effect the
copy data activity.  Similar logic may exist for the TOFILE.?

Is there any way to defeat that logic?

This particular problem I'm working on is REALLY tough ... as it's a mater of timing and I haven't been able to actually reproduce it in the lab.



IBM i on Power - For when you can't afford to be out of business

I'm riding on the American Diabetes Association Tour de Cure to
raise money for diabetes research! To sponsor me, visit
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

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-2021 by 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.