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