Re: triggers and clrpfm and such

looking now - thanks Kevin!

Jay

On Tue, Oct 29, 2019 at 1:51 PM Kevin Bucknum <Kevin@xxxxxxxxxxxxxxxxxxx>
wrote:

You could look at QIBM_QCA_CHG_COMMAND

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On
Behalf Of Jay Vaughn
Sent: Tuesday, October 29, 2019 12:46 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: triggers and clrpfm and such

thanks Nathan...

more along the lines of ways to deal with clrpfm without having to get
into the code.
implementing an SQL delete would of course invade the code.

I may be asking for the impossible... why i am asking... to see if such a
way...

Is there a way to build an exit pgm that interfaces with clrpfm that when
it executes it first does a *disable on any trigger and then *enable when
it is done with the clrpfm?

A trigger so to speak on the clrpfm to maintain the current triggers?
:)

good times

Jay

On Tue, Oct 29, 2019 at 1:32 PM Nathan Andelin <nandelin@xxxxxxxxx>
wrote:

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

--
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 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


[https://www.medtronsoftware.com/img/MedtronMinilogo.bmp] Kevin Bucknum
Senior Programmer Analyst
MEDDATA / MEDTRON
120 Innwood Drive
Covington LA 70433
Local: 985-893-2550
Toll Free: 877-893-2550
https://www.medtronsoftware.com



CONFIDENTIALITY NOTICE

This document and any accompanying this email transmission contain
confidential information, belonging to the sender that is legally
privileged. This information is intended only for the use of the
individual or entity named above. The authorized recipient of this
information is prohibited from disclosing this information to any other
party and is required to destroy the information after its stated need has
been fulfilled. If you are not the intended recipient, or the employee of
agent responsible to deliver it to the intended recipient, you are hereby
notified that any disclosure, copying, distribution or action taken in
reliance on the contents of these documents is STRICTLY PROHIBITED. If you
have received this email in error, please notify the sender immediately to
arrange for return or destruction of these documents.
--
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