🚀 go-pugleaf

Bill Todd wrote:

> I have never tried the following but it might work.
> 
> WHEN ANY DO
>   INSERT INTO LOGTBL (ERRORCODE) VALUES (GDSCODE);
> 
> You are correct that there is no way using SQL to get the message text
> that corresponds to an error code. The error messages are not stored
> in a system table.

My needs for purposes of this thread are to process IB Exceptions that
I have created and which are activated during user processing.  I'm not
trying to handle "Harder" errors resulting in SQLCODE errors or IB
errors in this case.  At lease the IB Exception message texts are in
the system tables.  I wish the message text was automatically returned
and available for processing.  And, I wish I didn't have to explicitly
list each Exception I want to handle.  This certainly leaves room for
error.

I'll post to the IBX group to see if anyone knows how to capture what
is displayed to the user during interactive processing.  That must get
something from the Embedded capabilities - although I'm trying to
handle it in a stored procedure.


-- 
Patrick Moloney