×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Thanks for the tip, Charles. The message returned from the Java sample
provided in the redbook suggests that users "refer to the joblog" for
additional information - suggesting that the real error might be buried
there ;-)
I gather that client applications need a streamlined interface for
recovering and reporting errors from triggers. Maybe a generic procedure
that scans the job log for a specific error ID - say TRG0001. Clients evoke
that procedure to get the real message?
Reporting generic SQL state and codes is not very helpful ;-)
Nathan.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
