5.7 Additional options with DB2 triggers If you have additional requirements to handle security in your Content Manager system, you may use DB2 triggers on Content Manager DB2 tables to provide the additional functionalities. Disclaimer: Use DB2 triggers in Content Manager system at your own risk. It is not the responsibility of the IBM DB2 Content Manager Technical Support Team nor the IBM ITSO Redbook Team to provide support for issues related to your DB2 triggers for a Content Manager system. We provide the information here as a possible option only. 5.7.1 DB2 trigger overview You can define a DB2 trigger on a table and specify whether or not it should be invoked before data is inserted, updated, or deleted from the table. The trigger has access to the data DB2 is planning to insert, update, or delete from the table. The trigger has the option to allow or reject the request after evaluating the request. The DB2 trigger is defined much the same way as a UDF. It can be defined with SQL statements directly in the trigger definition or it can call an external program