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

I think the problem here is you are blaming the interface because it is
not developed enough to handle constraints and/or triggers.
While, yes, UPDDTA has been updated over the years to handle some
rudimentary errors thrown, like:
- duplicate keys on a UNIQUE primary key file
- Date data types
It has not kept up with how to handle constraints and/or triggers.

I just created a simple file with one simple check constraint. The file
also had commitment control set on. UPDDTA totally lost it's mind.
upddta rob/nathan
Ownership of object QDZTD00001 in QTEMP type *FILE changed.
Ownership of object QDZTD00001 in QTEMP type *PGM changed.
Check constraint violation on member NATHAN.
Check constraint violation on member NATHAN.
EXIT DFU and SIGNOFF IMMEDIATELY. To allow data base roll back of data.
CPF502F caused the problem.

Message . . . . : Check constraint violation on member NATHAN.
Cause . . . . . : The operation being performed on member NATHAN file
NATHAN
in library ROB failed. Constraint Q_ROB_NATHAN_MYDATA_00001 prevents
record
number 1 from being inserted or updated because the field value
conflicts
with the check constraint. If the record number is zero, then the error

occurred on an insert operation. The reason code is 1. The reason codes
and
their meanings are as follows:
01 - Violation due to insert or update operation.
Granted, using a better naming convention than default would be best for
check constraints.

CREATE TABLE ROB/NATHAN (
MYDATA CHAR (1 ) NOT NULL WITH DEFAULT,
CHECK (MYDATA >'Z' ))

You could try reporting this to IBM and ask them to update UPDDTA to
support constraints.

If UPDDTA had similar issues with binary columns, date columns, primary
keys, etc would you be blaming it on the database? Or on UPDDTA?

Rob Berendt