Re: CPYF question

In making a final copy as TABLE, as a subset of data from a database file, there would be little reason to move any data anywhere besides directly from the source table to the target table. No FETCH means no array. Just choose an SQL statement that does it all, and avoid any cursor and the additional coding for array & movement of data.

Regards, Chuck

Alan Campin wrote:

I just had to deal with the same situation. CPYF is way slow. I
wrote embedded SQL. Only recommendation would be to map a user
space into an array and write 32766 records at a shot or what
will fit in the user space or use teraspace to allocate the
array. Will be too slow otherwise.

On Thu, May 7, 2009 at 12:52 PM, sjl wrote:

Thanks for the suggestions. The file is the JDE General Ledger
detail (F0911).

How about this solution:

There is not currently a logical file containg the fields
necessary for optimizing the SQL if used, so I'm going to
recommend that we

1) Build either a new logical file or create a SQL index, and 2) Replace the CPYF with an RPGIV program with embedded SQL to
perform the copy, passing the variable values via JDE's Dream
Writer processing options.