Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: Error message when you access an IBM DB2 table by using the Microsoft ODBC Driver for DB2 that is included with Host Integration Server 2004: �General Error�


View products that this article applies to.

Symptoms

When you use the Microsoft ODBC Driver for DB2 that is included with Microsoft Host Integration Server 2004 to access an IBM DB2 table, you receive an error message that resembles the following:
[Microsoft] [ODBC Driver] General error.
This problem occurs if the following conditions are true:
  • The table contains a TIMESTAMP column.
  • The table is located in an IBM DB2 Universal Database (UDB) for a z/OS Version 8 computer.
  • The z/OS Version 8 computer is operating in Enable New Function Mode (ENFM).

↑ Back to the top


Cause

This problem occurs because the IBM DB2 catalog is converted to Unicode when an IBM DB2 UDB for a z/OS computer is migrated to DB2 UDB for z/OS Version 8 in ENFM. After the DB2 catalog is converted to Unicode, DB2 returns Character Code Set Identifier (CCSID) 367 for DB2 TIMESTAMP data types. CCSID 367 is not recognized as a valid CCSID. Therefore, the data conversion is not successful. This scenario causes the �General error� error message.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Db2oledb.dll6.0.2035.0487,93615-Jun-200623:50x86
Db2oledb.hNot Applicable24,51615-Jun-200623:55Not Applicable
Ddmstr.dll6.0.2035.044,03215-Jun-200623:50x86
Drdaresync.exe6.0.2035.0337,40815-Jun-200623:50x86
Microsoft.hostintegration.dataaccesslibrary.dll6.0.2035.086,01615-Jun-200623:50x86
Microsoft.hostintegration.dataaccesstool.exe6.0.2035.02,703,36015-Jun-200623:51x86
Microsoft.hostintegration.msdb2client.dll6.0.2035.0114,68815-Jun-200623:50x86
Mseidb2c.dll6.0.2035.071,68015-Jun-200623:50x86
Mseidb2d.dll6.0.2035.0435,20015-Jun-200623:50x86
Mseidrda.dll6.0.2035.0695,80815-Jun-200623:51x86

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

This hotfix updates the ODBC Driver for DB2. After you apply this hotfix, the ODBC Driver for DB2 maps CCSID 367 to CCSID 1252. This action corrects the problem that this article describes.

↑ Back to the top


Keywords: KB919011, kbcode, kbfix, kberrmsg, kbpubtypekc, kbqfe, kbhotfixserver, kbautohotfix

↑ Back to the top

Article Info
Article ID : 919011
Revision : 5
Created on : 12/4/2007
Published on : 12/4/2007
Exists online : False
Views : 374