Re: Anyone using Triggers to enforce data validation & business rules?

I've just added a COMMON requirement on this. ID=316.

My suggested workaround goes something like this:
Provide a way for triggers to interact with the database so that a simple
update(e) recordFormat;
// get the error message details
if %error();
select;
when %status()='01023'; // Error in trigger program before write
// Retrieve trigger information from File information data structure or
some similar item.
select;
when TriggerError='USR0001'; // On hand < shipping qty
// process accordingly.
dsply TriggerErrorData; // Msg data from TriggerError

See "Table 2. Exception/Error Codes" at
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzasd/stacod9.htm?lang=en

But when you come right down to it, we already have this capability. It's
simply a matter of encapsulating Buck's recent post into a service program
and exporting the functions TriggerError and TriggerErrorData.

But perhaps an update to some other database feedback area and using that
instead would be more 'standard' for other database tools like iNav's Run
SQL Scripts and whatnot.

Rob Berendt