JR26362: DB2 DRIVER FOR ODBC AND CLI FAILS TO CONNECT WHEN USED VIA WINDO WS ODBC DRIVER MANAGER. NO PROMPT FOR USEIRD AND PASSWORD.

DB2 Version 9.1 Fix Pack 4a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 3   for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 4 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 5   for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6   for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 3a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

APAR status

• Closed as program error.

Error description

• DB2 Driver for ODBC and CLI fails to connect when used via
  Windows ODBC Driver Manager. No prompt for useird and password.
  For example, if using Microsoft Excel Spreadsheet and you
  attempt to import external data, the resulting connection
  attempt fails with rc = -1 Internal Error Encountered.
  The application will be unable to access the data server unless
  the APAR fix is applied or the defined work around is used.
  For example, if using Microsoft Excel Spreadsheet and you
  attempt to import external data, the resulting connection
  attempt fails with rc = -1 Internal Error Encountered.
  

Local fix

• Include the userid and password inthe db2cli.ini DSN entry.
  This will eliminate the need to prompt the user for the userid
  and password.
  In order to do this, configure the Datasource as required via
  the ODBC Driver Manager. Then edit the DB2 Driver for ODBC and
  CLI db2cli.ini file. Locate the Datasource name you configured
  and add the following (assume the userid is "myuid" and the
  password is "mypwd".
  UID=myuid
  PWD=mypwd
  In order to locate the proper db2cli.ini file, assume you have
  installed the Db2 Driver for ODBC and CLI in c:\clidriver.
  If you have configured a System DSN then the required file is
  located in c:\clidriver\db2cli.ini.
  If you have configured a User DSN then the required file is
  located in \Documents and Settings \myuid\db2cli.ini .
  If you have configured the DB2 environment variable
  DB2CLIINIPATH, then the db2cli.ini file is located in that
  environment variable value.
  

Problem summary

• Fixed provided.
  

Problem conclusion

• First fixed in Version 9 Fixpak 3.
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  DB2 UDB ESE WIN

• Fixed component ID

  5765F4101

Applicable component levels

• R910 PSY

     UP