DB2 UDB 8.1.2 client: problem with SQLGetFunctions

[Bob Hairgrove]

Hello,

We have a problem with ODBC access involving API support. Our customer
has DB2 UDB 7.2.9 running as server on Windows NT. For clients with
UDB 7.1.1, there is no problem. For clients running 8.1.2, however,
not all API functions seem to be supported.

In our ODBC code, we call SQLGetFunctions with argument
SQL_API_ODBC3_ALL_FUNCTIONS and test for the following API support
(sorry about line wrapping here):
================
bool API_all = ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLBINDCOL ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLBINDPARAMETER ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLCOLATTRIBUTE ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLDESCRIBECOL ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLDISCONNECT ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLEXECDIRECT ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLEXECUTE ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLFETCHSCROLL ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLFREEHANDLE ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLGETCONNECTATTR ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLGETDESCFIELD ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLGETINFO ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLGETSTMTATTR ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLGETTYPEINFO ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLNUMPARAMS ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLNUMRESULTCOLS ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLPREPARE ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLROWCOUNT ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLSETCONNECTATTR ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLSETENVATTR ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLSETPOS ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLSETSTMTATTR ) == SQL_TRUE );

if ( !API_all )
throw XSqlException ( support_missing );
================

These are very basic APIs which our ODBC classes expect all the
databases to support ... we have never encountered this problem before
and were wondering if it is a problem with the client configuration?

Thanks.

[PM \(pm3iinc-nospam\)]

You may need db2jdbcbind for a downlevel server.
http://publib.boulder.ibm.com/infoce...help/index.jsp
search: db2jdbcbind

Not sure it will solve the problem though.

PM
"Bob Hairgrove" <bo**********@yahoo.com> a écrit dans le message de
news:67**************************@posting.google.c om...

Hello,

We have a problem with ODBC access involving API support. Our customer
has DB2 UDB 7.2.9 running as server on Windows NT. For clients with
UDB 7.1.1, there is no problem. For clients running 8.1.2, however,
not all API functions seem to be supported.

In our ODBC code, we call SQLGetFunctions with argument
SQL_API_ODBC3_ALL_FUNCTIONS and test for the following API support
(sorry about line wrapping here):
================
bool API_all = ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLBINDCOL ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLBINDPARAMETER ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLCOLATTRIBUTE ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLDESCRIBECOL ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLDISCONNECT ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLEXECDIRECT ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLEXECUTE ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLFETCHSCROLL ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLFREEHANDLE ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLGETCONNECTATTR ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLGETDESCFIELD ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLGETINFO ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLGETSTMTATTR ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLGETTYPEINFO ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLNUMPARAMS ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLNUMRESULTCOLS ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLPREPARE ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLROWCOUNT ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLSETCONNECTATTR ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLSETENVATTR ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLSETPOS ) == SQL_TRUE )
&& ( SQL_FUNC_EXISTS ( Supported_Functions,
SQL_API_SQLSETSTMTATTR ) == SQL_TRUE );

if ( !API_all )
throw XSqlException ( support_missing );
================

These are very basic APIs which our ODBC classes expect all the
databases to support ... we have never encountered this problem before
and were wondering if it is a problem with the client configuration?

Thanks.

[Bob Hairgrove]

"PM \(pm3iinc-nospam\)" <PM(pm3iinc-nospam)@sympatico.ca> wrote in message news:<98*********************@news20.bellglobal.co m>...

You may need db2jdbcbind for a downlevel server.
http://publib.boulder.ibm.com/infoce...help/index.jsp
search: db2jdbcbind

Not sure it will solve the problem though.

We aren't using Java, but C++ and ODBC (our own C++ wrapper classes
around the ODBC C API functions, no COM etc.)

It seems that the driver is reporting no support for SQLGetDescRec()
and SQLSetPos(). Apparently, as I stated in my first post, the OLDER
driver does support SQLSetPos (at least the customer said "it works").

Why would 7.x support it and 8.1.2 not?? SQLSetPos has been in the
specs since ODBC 1.0. (The server, BTW is running 7.something). We can
live without SQLGetDescRec, but dropping SQLSetPos from the wrapper
classes is plain silly. We implemented lots of things with that
function and it would entail a complete re-write of the classes.

Any help would be greatly appreciated.

Bob