×
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.
... this won't help for messages coming from non DB2 databases. SQLCODE is
vendor specific and very diffrent for diffrent databases. Even SQLSTATE
differs from SQL dialect to dialect. Accessing MSSQL (or other databases
from) DB2/400
the middleware (in the OP message ArdGate) has to map the SQLSTATE coming
from MSSQL (or any other database) to a SQLCODE in DB2/400 flavour. In this
case SQLSTATE 08S03 is coming from the JDBC Driver and the SQLCODE is
derived from the SQLSTATE (and the knowledge inside ArdGate where the
problem happened).
D*B
<Sam>
FWIW: You can use the "*SQL message finder*" at
https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_71/rzas2/rzas2finder.htm
(Or Google "sql message finder")
Pick your correct release at the top left.
SQLCODE -30060 gives SQ30060 User is not authorized to relational database
&1.
If relational database &1 is DB2 for IBM i, a user exit program denied
access to the user, or a failure in the user exit program occurred.
SQLSTATE 08S03 comes up as not found. Maybe a user generated code>
</Sam>
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
