Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

SQL0000W message during SQLFetch

119 views
Skip to first unread message

Lonnie Thibodeaux

unread,
Nov 3, 1997, 3:00:00 AM11/3/97
to

I receive the 'SQL000W Statement processing was successful' during the
procesing of a SqlFetch, but I only receive it during processing of certain
result sets (Same statement execution, different WHERE clause conditions).
I don't need to see this message appear during applicaton execution. Why am
I receiving this message?
Anyone know?

--
Lonnie Thibodeaux
Dairyland Computers & Consulting, Inc.

do...@torolab.ibm.com

unread,
Nov 4, 1997, 3:00:00 AM11/4/97
to

During a fetch, we can return some warning indicators even though we
retrieved the row successfully (for example, we will tell you if your
variable is too short to hold a string). I imagine that one or more of
these indicators are being set by your SQLFetch() call so the rc is
SQL_SUCCESS_WITH_INFO rather than SQL_SUCCESS. You should check the SQLSTATE
after the SQL_SUCCESS_WITH_INFO--it probably isn't 00000 and would tell you
what is causing the warning. Also, the CLI/ODBC message will give you more
information than the native error message in this case.

To avoid seeing the message, after the SQLFetch(), don't call your message
processing routine if the rc is SQL_SUCCESS_WITH_INFO. (As far as I can
recall, we don't return any warnings other than these SQL0000W ones during
a fetch.) If you want to be more specific on which warnings you ignore,
if you receive SQL_SUCCESS_WITH_INFO, you can make a call to retrieve the
native error cade (I can't remember the function name) and if the native
error code is 0, ignore the warning.

Hope this helps.
--
___________________________________________________________________________
Doug Doole do...@ca.ibm.com
DB2 Universal Database Development
IBM Toronto Labs

0 new messages