Trigger blocking

Several years ago I implemented a read trigger that is applied to certain files. Specifically, those files where any fields contain data covered by legislative constraints.
The regulations mandate an entry in a log whenever the data is accessed, primarily as a record of the user and the reason for access.
The read trigger is designed to perform as efficiently as possible despite being called frequently, e.g. when a large file is read from start to end, and was implemented without any significant degradation on system performance.

However, there are times when large batch jobs may be exempt from the regulations. As there was no known way to dynamically prevent a trigger from firing, the trigger is designed to abort immediately where there is an exemption.
I would be interested to know if, at V7R1 there may now be a way to essentially override a trigger during a specific application while at the same time remaining operative for other applications.

Peter


#####################################################################################

This correspondence is for the named person's use only. It may contain confidential
or legally privileged information, or both. No confidentiality or privilege is waived
or lost by any mistransmission. If you receive this correspondence in error, please
immediately delete it from your system and notify the sender. You must not disclose,
copy or rely on any part of this correspondence if you are not the intended recipient.
Any views expressed in this message are those of the individual sender, except where
the sender expressly, and with authority, states them to be the views of Veda.
If you need assistance, please contact Veda on either :-
Australia 1300-762-207 or New Zealand +64 9 367 6200