×
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.
... seems to me, that DB2/400 only is reporting the first field it doesn't
like. creating a view with your SQL statement and fetching into a DS based
on this view would be the cleanest solution. (this would help to decouple
database and application too!!!)
<Buck>
Bottom line: Trust SQLSTATE. Don't trust the messages issued in debug
mode.
</Buck>
DB2/400 is not focussed on SQLSTATE, it's only interested in the vendor
specific SQLCODE and maps this to a SQLSTATE showing to the user. In other
words: the SQL7919 is the originating problem and SQLSTATE is derived from
this.
D*B
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
