JR29115: FED: CANNOT USE ODBC WRAPPER WITH NON-DATADIRECT ODBC DRIVERS ON ZLINUX

DB2 Version 9.5 Fix Pack 3b for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 2a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 2  for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4  for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• If you try to use the ODBC wrapper on zLinux with a
  non-DataDirect ODBC driver, you can get a message similar to
  the following. (The message shown occurs when using the ODBC
  wrapper on zLinux with the IICF ODBC driver.  Using the wrapper
  with other non-DataDirect ODBC drivers on zLinux might produce
  a different message.)
  db2 => create nickname emp2 for
  DATASTORE2."sso1300"."SAKE_222_TABLE102"
  DB21034E  The command was processed as an SQL statement because
  it was not a
  valid Command Line Processor command.  During SQL processing it
  returned:
  SQL1822N  Unexpected error code "HY092" received from data
  source
  "DATASTORE2". Associated text and tokens are "
  SQLSetConnectAttr - Error code:
  x00560081. An incorr".  SQLSTATE=560BD
  The problem is the code in function Odbc_Connection::connect
  (file sqlqg_odbc_connection.C) that calls SQLSetConnectAttr to
  set the DataDirect OEM license file and password.  The code
  begins with these lines:
    +601 #ifdef SQLLinux390
    +602
    +603
    +604 #define SQL_DATADIRECT_OEM_LICENSE_FILE 1041
    +605 #define SQL_DATADIRECT_OEM_PASSWORD 1042
    +606
    +607   /* Options 1041 and 1042 are registered to DataDirect
  Technologies and recognized
    +608      by DataDirect drivers only. */
  
    +612     rc = m_wrapper->m_fpSQLSetConnectAttr(m_hdbc,
    +613
  SQL_DATADIRECT_OEM_LICENSE_FILE,
    +614
  (SQLPOINTER)"DDVM.LIC",
    +615        SQL_NTS);
  Non-DataDirect ODBC drivers will return an error on the
  SQLSetConnectAttr call because they don't recognize the above
  DataDirect connection attributes.
  To fix this, we cannot just remove the above code.  Then the
  wrapper will not work with the IBM WFS-branded DataDirect
  driver.  (I have not tried that, but I assume it won't work
  because we did not specify the license file.  Note that this
  problem currently exists when using the wrapper with the IBM
  WFS-branded DataDirect driver on platforms OTHER THAN zLinux.
  Again, I have not tried that. But I assume it won't work for
  the same reason.)
  The fix for this is probably as follows:
  - Change the error checking so that if we get an error from the
  SQLSetConnectAttr due to the attribute value being invalid,
  then we ignore the error.  This will allow the wrapper to work
  with non-DataDirect ODBC drivers.  (I don't know if we can
  always tell whether the error from SQLSetConnectAttr is due to
  the attribute value being invalid.  Can different ODBC drivers
  return different error codes?  The safest thing might be to log
  the error information in db2diag.log, but otherwise ignore any
  errors.)
  - Remove the #ifdef SQLLinux390/#endif.  This will allow the
  ODBC wrapper to be used with the IBM WFS-branded DataDirect
  driver on platforms other than zLinux.
  The test for this fix should include the following cases:
  - Using the ODBC wrapper with the IBM WFS-branded DataDirect
  ODBC driver.
  - Using the ODBC wrapper with the non-branded DataDirect ODBC
  driver.
  - Using the ODBC wrapper with a non-DataDirect ODBC driver.
  Thanks.
  

Local fix

Problem summary

• Users affected: Users of the ODBC wrapper in InfoSphere
  Federation Server on zLinux
  
  Problem description and summary:
  See error description.
  

Problem conclusion

• Problem was first fixed in Version 9.5, FixPak 2 (s080811).
  This fix should be applied on the federation server.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  IZ20745

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  ODBC WRAPPER

• Fixed component ID

  5724N9707

Applicable component levels

• R950 PSN

     UP