Stop DB2/400 triggers from firing without disabling or removing them

[iamgobi]

We have a need to stop the DB2/400 triggers from getting invoked, but we cannot disable or remove them as jobs would be locking them. FYI, we have code inside the trigger to check a DTAARA and quit action, but even that takes CPU for a big file.

[Rocky]

The only way that I know is for the trigger programs to not do any work, just call a separate program. That program can be written to do nothing based on a certain event - time of day or whatever... or you could replace the program that doesn't do anything but return and then put it back to normal once you want it to return to normal.