Re: CPYF question

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Chuck,

The only issue I have with this, is when the destination table is
journalled, there's a huge performance hit if you write to it without
commitment control (unless you have the v5r4+ HA Journal Performance
LICPGM or prior to v5r4 the Journal Caching PPRQ).  If you're writing
lots of records, trying to do them as a single commit transaction can
also be a killer.

At that point, you're better off reading with a cursor and committing
periodically.

The write should be done with either RPG op-codes or via SQL batch inserts.

Granted, many times you're copying data like this for work files which
don't need to journalled.  But if that isn't the case...

Charles Wilt


On Thu, May 7, 2009 at 3:48 PM, CRPence <CRPbottle@xxxxxxxxx> wrote:
>   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