Re: %error handling

Brian Lewis wrote:

I made an interactive program to maintain these files. If something
goes wrong on an insert or an update, it's most likely because they
tried to add a record with a duplicate key, or one of the field values
was rejected by a trigger program. I want to show them some informative
message that helps them understand why it didn't work. Right now, that's
seeming absurdly difficult to do.

For the trigger-program cases, your trigger programs are probably
already issuing an escape message; that can be as communicative as you
want.  Or the trigger program could issue any number of diagnostic
messages before it issues more generic escape message.

For the constraint errors, you could retrieve the constraint information
from the file; DSPFD TYPE(*CST) OUTPUT(*OUTFILE), and build a (fairly)
nice description of the error.