Re: Database Trigger and Update problems

> 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...

The escape message you send from the trigger program goes to the DB
routines.  The DB routines send that message as a diagnostic message
back to the trigger program, and it goes in the job log that way.

If you look in the job log you get:
CPF9898 (your escape message)
CPF502B (trigger failed)

Using QMHRCVPM, you can loop through the * message queue in your
update program and scoop these up.  The 502B can tell you which
trigger 'failed', and your escape message (re-issued as a diagnostic)
can tell you why.

update recfmt
if %error
  exsr getmsg
endif

getmsg begsr
loop
  call QMHRCVPM
  if no messages, exit

  when 502B
    save trigger info
  when 9898
    save reason info
    exit
end loop

  --buck