One option is to use a CL program for your trigger that accepts and
passes the record buffer to a called program. Then you could change
the called program to terminate immediately without ever having
to change the CL trigger program.
Not sure how efficient this would be with large volumes of
record changes...but its seems like it would work ;-) We currently
use the CL trigger trick to allow us to make changes to the
called program without deactivation...
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Åke Olsson
Sent: Thursday, October 04, 2012 10:44 AM
Subject: Triggers - enabling and disabling
We have to set up triggering for a bunch of files (15 files
in 30 instances). I can live with having to find a spot when
the system is down to add the tiggers.
But we would like to turn on and off the activation of
triggers more or less at will. Status *ENABLED and *DISABLED
should work nicely.
The problem is that this operation seems to require private
access to the file almost as much as ADDPFTRG does - is that
Is there in that case another better way to dynamically
switch triggers on and off?
Med vänlig hälsning / Best regards
Åke H Olsson
Box 433 SE 551 16 Jönköping Sweden visit: Brunnsgatan 11
phone: +46 (0)36 342976 mobile: +46 (0)705 482976 fax: +46
(0)36 34 29 29
The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is
not authorized and may be unlawful.