Åke Olsson wrote:
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 really so?
Is there in that case another better way to dynamically switch
triggers on and off?
You could have the triggers check a *DTAARA that controls whether they
are to actually do anything, or just quick-out.
Or you could use something a fellow list member recommends, a "trigger
Or you could even combine the two ideas.