Trigger automatic events in your database

A trigger is a set of actions that run automatically when a specified change or read operation is performed on a specified database file. On iSeries™, you define a set of trigger actions in any supported high-level language.

The change operation can be an insert, update, or delete high-level language statement in an application program. The read operation can be a fetch, get, or read high-level language statement in an application program.

You can also use SQL triggers.

• Uses for triggers
  Triggers in the database have several uses.
• Benefits of using triggers in your business
  Triggers offer benefits to your business.
• Create trigger programs
  These topics discuss how to create and work with trigger programs.
• Add triggers
  This topic shows how to add triggers to a database file.
• Display triggers
  The Display File Description (DSPFD) command provides a list of the triggers that are associated with a file. Specify TYPE(*TRG) or TYPE(*ALL) to get this list.
• Remove triggers
  You can remove triggers using the Remove Physical File Trigger (RMVPFTRG) command, the SQL DROP TRIGGER statement, and iSeries Navigator.
• Enable or disable physical file triggers
  You can enable or disable triggers using the Change Physical File Trigger (CHGPFTRG) command and iSeries Navigator.
• Triggers and their relationship to CL commands
  Triggers interact with CL commands in several ways.
• Triggers and their relationship to referential integrity
  A physical file can have both triggers and referential constraints associated with it. The running order among trigger actions and referential constraints depends on the constraints and triggers that are associated with the file.