RE: CPYF with mbropt *replace and Triggers

Thank you that is exactly what I needed to here.

Chris Bipes
Director of Information Services
CrossCheck, Inc.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Thursday, August 04, 2016 3:46 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: CPYF with mbropt *replace and Triggers

On 04-Aug-2016 17:33 -0500, Chris Bipes wrote:

Are insert triggers called when you perform a Copy File with Member
Option to Replace?

The help text specifies that change operations do not include
clearing, initializing, moving, applying journal changes, removing
journal changes, or changing end of data operations. Would the copy
file be considered a clear and initialize?

Just to clarify for other readers, that help text reference is for
the Add Physical File Trigger (ADDPFTRG) general help, and the noted
/change operations/ refers to the /I\O operations/ of Insert, Update,
Delete, or Read -- according to the type of trigger being added.

While the specification of *REPLACE for the Member Option (MBROPT)
would indeed effect a clear [for non-fast copy, and AFaIK that is the
required path for a TOFILE with triggers], the remaining effect uses the
database /put/ method which is the /insert/ change-operation; i.e. an
*INSERT trigger would fire for each record\row added to the member that
was previously cleared. Note that if there were a Delete trigger to the
To-File, the clear would be halted\prevented due to an error, and the
Copy File (CPYF) request would fail.