Re: triggers and clrpfm and such

[Nathan Andelin <nandelin@xxxxxxxxx>]

It's not clear to me what problem you want to solve. Are you asking about a
way to continue using the CLRPFM command to clear files that have triggers?
In that case, some might suggest using an SQL DELETE without a WHERE clause
instead of CLRPFM. Or, are you asking for a way to temporarily "disable"
triggers?


On Tue, Oct 29, 2019 at 1:13 PM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:

> so someone added triggers to our db2 file.
> Of course now any clrpfm will not execute unless they are *disabled first
> for that file right?
>
> So what is the best way to implement a solution for this without having to
> comb through the entire application layer?
>
> Any chance some kind of exit pgm could handle this for us?  Possibly tied
> to such commands like clrpfm... and whatever other command we need to be
> aware of with triggers?
>
> tia
>
> jay
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com