A software update that lets the OLE DB Provider for DB2 that is included in Host Integration Server pass the Client Application Name property to IBM DB2 systems is available

A software update is available for Microsoft Host Integration Server 2004. This software update lets the OLE DB Provider for DB2 that is included in Host Integration Server 2004 pass the Client Application Name property to IBM DB2 systems when the OLE DB Provider for DB2 reuses the connections in the DB2 connection pool. The OLE DB Provider for DB2 was designed to pass the Client Application Name property to IBM DB2 systems in the Exchange Server Attributes (EXCSAT) Distributed Data Management (DDM) command. This occurs while the OLE DB Provider for DB2 initializes the first connection to the IBM DB2 system.

The OLE DB Provider for DB2 supports a Client Application Name 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 in DB2 logs or in system logs.

The OLE DB Provider for DB2 only passes the specified Client Application Name property to an IBM DB2 system when the connection to DB2 is first established. If the OLE DB Provider for DB2 is configured to use connection pooling, the Client Application Name property is not passed to the IBM DB2 system when the OLE DB Provider for DB2 reuses the connections from the connection pool.

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.

Prerequisites

You must have Microsoft Host Integration Server 2004 installed before you apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

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.Note Because of file dependencies, the most recent software update that contains these files may also contain additional files.

Host Integration Server 2004 SP1

A software update is currently not available for Host Integration Server 2004 Service Pack 1 (SP1).

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:

OLE DB Provider for DB2 1.0 SP1

A software update is currently not available for OLE DB Provider for DB2 1.0 SP1.

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

After you apply this hotfix, the OLE DB Provider for DB2 will send the specified Client Application Name property when you use pooled connections by using the following SET command: 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 in DB2 logs or in 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:
  • ~
  • `
  • !
  • @
  • #
  • $
  • %
  • ^
  • &
  • *
  • (
  • )
  • -
  • +
  • =
  • [
  • ]
  • {
  • }
  • :
  • ;
  • "
  • '
  • ,
  • <
  • >
  • ?
  • |
  • \
  • /
  • .
  • 0
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
• 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:
  • ~
  • `
  • !
  • @
  • #
  • $
  • %
  • ^
  • &
  • *
  • (
  • )
  • -
  • +
  • =
  • [
  • ]
  • {
  • }
  • :
  • ;
  • "
  • '
  • ,
  • <
  • >
  • ?
  • |
  • \
  • /
  • .
  • 0
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
• 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:
  • ~
  • `
  • !
  • @
  • #
  • $
  • %
  • ^
  • &
  • *
  • (
  • )
  • -
  • +
  • =
  • [
  • ]
  • {
  • }
  • :
  • ;
  • "
  • '
  • ,
  • <
  • >
  • ?
  • |
  • \
  • /
  • .
  • 0
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
• 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. For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: