IBM i Database Trigger Support › CA 2E Model Support › Creating Trigger Functions

Creating Trigger Functions

You can create a Trigger Function by specifying either "Trigger Function" or "TRGFUN" for the Function Type, in exactly the same way that you would create any other CA 2E function. When you enter a Trigger Function using the Action Diagram Editor (ADE), you can include any processing that you would include in any other non-interactive function (including calling any other non-interactive function). You have access to all the *Trigger Control Data and ORF parameters as input-only, and the NRF and return code parameters as input/output.

When you create a Trigger Function (TRGFUN), the CA 2E model automatically creates a file-specific parameter list for the function. The Trigger Router passes the list to the function as follows:

1. Return code.
2. Trigger Control Data structure (from the *Trigger Control Data system file).
3. Old record format (ORF) structure (from the owning file).
4. New record format (NRF) structure (from the owning file).

The Trigger Control Data structure contains fields retrieved from the parameters passed by Data Management to the Trigger Router, as well as some derived fields, as follows:

Note: The *Trigger Job fields are included to allow asynchronous Trigger Function calls to determine the name of the job that actually changed the database file, rather than using the job fields from the Trigger Server. The *Trigger App Program and *Trigger App Library fields allow Trigger Functions to make processing decisions based on the application program that caused the file change. In r 8.1, the *Trigger App Library is not currently used and is passed as blank to the Trigger Function.