Re: Alternative to CPYF that doesn't apply a lock

Hi Francis

Thanks for the prompt reply. A quick RPG program won't do this time, the program is part of a utility we have that allows records to be duplicated in any of the database files with new values. For example, copying all G/L accounts for Company 001 and creating new records for Company 002.

All the best

Jonathan


Francis Lapeyre wrote:

I had a similar problem, and just wrote a quickie RPG program that reads the
source file and writes to the destination. If you have unique keys on the
destination file or any of its logicals, be sure to program for the
possibility.


On Wed, Feb 27, 2008 at 8:26 AM, Jonathan Mason <
jonathan.mason@xxxxxxxxxxxxxxxx> wrote:

Hi List

We have a program that makes use of the CPYF command to copy data from a
work file in QTEMP to a corresponding file in our data library.
Depending on the file being used there can be upwards to 100,000 records
being copied which is starting to cause a problem as the CPYF applies a
lock to the file being copied into.

The help text describes the restriction as:

o During the time a CPYF request is run, the file specified for
the To file (TOFILE) parameter may be locked (similar to an
*EXCL lock with no timeout) so that no access is possible.

Because the file is locked this is causing other programs to fail
CPF4128 and RPG1216 errors. I am thinking about putting in a change to
use an SQL insert instead of the CPYF and was wondering if anybody knows
whether or not using SQL would apply a lock to the receiving file.

Thanks in advance

Jonathan

--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.