Re: triggers and clrpfm and such -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Only a Delete trigger will stop a CLRPFM.

Gord

On Tue, 29 Oct 2019 at 13:13, 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

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.