Re: Database Trigger and Update problems

Hi Rob,

> Then how does one get the program to signal an error to whatever process
> attempts the update be it your RPG application, UPDDTA, C/S application,
> etc?

Sorry, I said "do not use escape messages to do this" and I
didn't specify what I meant by "this."   Please let me clarify...

It's okay to use escape messages to signal errors to the database
routines...  in that case, you're sending to one call stack level before
the program boundary (*PGMBDY, 1).  All this'll do is tell the DB2/400
routines that there's an error -- they don't care what the error is, they
just know that the trigger failed.

It's not okay to use escape messages to send human-readable messages
directly to your own program.   When you do this, you're bypassing the
database routines, effectively killing them, and returning control
directly to your own routines.

The problem is how to pass the error text back from the trigger to your
application if you don't use the text of the escape message...