FIX: OLE DB Provider for DB2 connection pooling feature does not work when an application connects to an IBM DB2 computer

When a consumer application uses OLE DB Provider for DB2 that is included in Microsoft Host Integration Server 2004 and in Microsoft Host Integration Server 2006 to connect to an IBM DB2 computer, the connection pooling feature that OLE DB Provider for DB2 implements does not work. This problem occurs when the following properties are configured in the connection string or in the Universal Data Link (UDL) file that the consumer application uses to connect to the DB2 computer:

• Connection pooling=True
• Client Application Name=<Custom Application Name>

Note This problem also occurs when you use Managed Provider for DB2.

This problem occurs because the connection pooling feature does not work when you use a client application name that is not the default client application name.

Host Integration Server 2004

Service Pack information

To resolve this problem, obtain the latest service pack for Host Integration Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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.

Host Integration Server 2006

To resolve this problem, obtain the latest service pack for Host Integration Server 2006. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft OLE DB Provider for DB2 1.0 with Service Pack 1

A hotfix is currently not available for Microsoft OLE DB Provider for DB2 1.0 with Service Pack 1.

To work around this problem, remove the Client Application Name property from the connection string or from the UDL file that the consumer application uses to initialize the connection to the IBM DB2 computer.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Host Integration Server 2004 Service Pack 1.

After you apply this update, the connection pooling feature functions as expected when the Client Application Name property is used to specify a nondefault client application name.

The Client Application Name property is an optional OLE DB data source initialization property. This property is used to specify a custom application name that the DB2 network client passes to the IBM DB2 computer when the connection is made. When you troubleshoot issues, you can use this value to help determine relevant portions within DB2 logs or system logs. The following lists describe the characteristics of the Client Application Name property when the property is used in different Microsoft programs.

Microsoft OLE DB Provider for DB2

• Property Group: Initialization
• Property Set: DBPROPSET_DBINIT
• Property ID: DBPROP_DB2OLEDB_CLIENTAPPNAME
• Property Description: Client Application Name
• Initialization Keyword: ClientAppName
• Default Value: MSEIDRDA
• Data Links Dialog: All
• Type: VT_BSTR
• Max Length: 18
• Invalid Characters: ~`!@#$%^&*()-+=[]{}:;"',<>?|\/
• Invalid Starting Characters: ~`!@#$%^&*()-+=[]{}:;"',<>?|\/.0123456789
• R/W: R/W
• Required: No

Managed Provider for DB2

• Class: MsDb2Connection
• Property: ClientApplicationName
• Default Value: MSEIDRDA
• Type: String
• Max Length: 18
• Invalid Characters: ~`!@#$%^&*()-+=[]{}:;"',<>?|\/
• Invalid Starting Characters: ~`!@#$%^&*()-+=[]{}:;"',<>?|\/.0123456789
• R/W: R/W
• Required: No

Microsoft Data Access Library

• Class: IConnectionString
• Property: ClientApplicationName
• Default Value: MSEIDRDA
• Type: String
• Max Length: 18
• Invalid Characters: ~`!@#$%^&*()-+=[]{}:;"',<>?|\/
• Invalid Starting Characters: ~`!@#$%^&*()-+=[]{}:;"',<>?|\/.0123456789
• R/W: R/W
• Required: No

Microsoft ODBC Driver for DB2

The Client Application Name property is not supported with the ODBC Driver for DB2.