DB2 10.5 for Linux, UNIX, and Windows

IBM Data Server Provider for .NET enhancements and features

List of IBM® Data Server Provider for .NET enhancements and new features that are included in the DB2® Version 10.5 base product and its fix packs. Each fix pack for a release is cumulative; that is, a particular fix pack contains the enhancements and new features that were included in previous fix packs.

DB2 V10.5 FP5: Support for Microsoft Entity Framework 6.0 features

The IBM Data Server Provider for .NET supports the Entity Framework 6.0 features that are related to the Database First approach. For more information, see Microsoft Entity Framework 6.0 support.

DB2 V10.5 FP5: Enhancements for connections to DB2 for z/OS servers

The DB2 Version 10.5 Fix Pack 5 product includes the following enhancements to IBM Data Server Provider for .NET that are specific to connections to DB2 for z/OS® servers:

DB2 V10.5 FP5: Support for the SSLServerCertificate keyword and the SSLServerCertificate property

You can now establish SSL connection using a self-signed certificate or a certificate authority (CA) certificate by setting the SSLServerCertificate keyword or the SSLServerCertificate property. By setting the SSLServerCertificate keyword or the SSLServerCertificate property, you avoid having to set the SSLClientKeystoredb keyword with the SSLClientKeystoreDBPassword or SSLClientKeyStash keyword. See SSLServerCertificate IBM data server driver configuration keyword.

DB2 Cancun Release: Enhancements to the seamless automatic client reroute feature

You can now specify the detectReadonlyTxn keyword to help ensure seamless failover with the automatic client reroute feature for read-only transactions when you connect to DB2 for Linux, UNIX, and Windows servers or DB2 for z/OS Version 11 in new function mode (NFM). For more information, see Configuration of Sysplex workload balancing and automatic client reroute for applications other than Java™.

DB2 Cancun Release: Support for Microsoft SQL Server Reporting Services (SSRS)

You can now specify the DB2 (IBM Data Server Provider for .NET) embedded SQL connection type in the SSRS application. For more information, see Provider support for the Microsoft SQL Server Reporting Services.

DB2 Cancun Release: Enhancements for connections to DB2 for i servers

The IBM Data Server Provider for .NET now supports the ConcurrentAccessResolution keyword for use in connections to DB2 for i V7R1 and later servers. For more information, see ConcurrentAccessResolution IBM data server driver configuration keyword.

DB2 Cancun Release: New value for the ClientWorkstationName keyword

You can now specify the 'NODEFAULT' value for the ClientWorkstationName keyword to prevent a domain name server (DNS) lookup when the client workstation value is not required. For more information, see ClientWorkstationName IBM data server driver configuration keyword.

DB2 Cancun Release: Support for the DB2Connection.BatchCommandTimeout property

You can use the DB2Connection.BatchCommandTimeout property to set the command timeout value when you enable chaining in a DB2Connection object. For more information, see DB2Connection.BatchCommandTimeout property.

FP2: Enhancements for connections to DB2 for z/OS servers

The Version 10.5 Fix Pack 2 includes the following enhancements to IBM Data Server Provider for .NET that are specific to connections to DB2 for z/OS servers:
  • You can now call a stored procedure with array input arguments on a DB2 for z/OS Version 11 server in new function mode (NFM). For more information, see Calling stored procedures from an application using the IBM Data Server Provider for .NET.
  • The IBM Data Server Provider for .NET performs the implicit commit operation when an application calls a stored procedure on DB2 for z/OS servers. By implicitly performing the commit operation on DB2 for z/OS servers, extra network traffic to the server is avoided. The following conditions must be met for the implicit commit operation to be performed:
    • The connected database server must be a DB2 for z/OS Version 11 server in NFM.
    • The autocommit behavior must be enabled when the stored procedure is called.
    • There cannot be any open result sets when the stored procedure completes the execution.
    For more information, see Calling stored procedures from .NET applications.
  • The default values of the CommitOnEOF keyword and the DB2Command.CommitOnEOF property are TRUE only when you connect to DB2 for z/OS Version 9 and later servers. For more information, see DB2Command.CommitOnEOF property.
  • You can now specify the client correlation token information when you connect to the DB2 for z/OS Version 11 server in NFM. You can specify client correlation token information by using any of the following methods:
    • Setting the DB2ConnectionStringBuilder.ClientCorrelationToken property
    • Setting the DB2Connection Class.ClientCorrelationToken property
    • Setting the ClientCorrelationToken IBM data server driver configuration keyword
    For more information, see DB2ConnectionStringBuilder properties and DB2Connection properties.The global variables in the IBM data server driver configuration file are supported by the DB2 for z/OS Version 11 server in NFM. To connect to the DB2 for z/OS server, you must set the CURRENT APPLICATION COMPATIBILITY special register to V11R1. For more information, see IBM data server driver configuration file structure.

FP2: Support for the CurrentFunctionPath property and keyword

The IBM Data Server Provider for .NET supports the CurrentFunctionPath property and keyword to list one or more schema names that can be used to resolve unqualified function and stored procedure names. You can use the following method to set the CurrentFunctionPath property or keyword.

FP2: Support for SQL codes with the RetryParameterBindingOnError keyword in the IBM data server driver configuration file

The IBM Data Server Provider for .NET supports the listing of SQL codes by using the RetryParameterBindingOnError keyword in the IBM data server driver configuration file. For more information, seeRetryParameterBindingOnError IBM data server driver configuration keyword.

Version 10.5: Support for Microsoft Entity Framework 5.0 features

The IBM Data Server Provider for .NET supports the following Microsoft Entity Framework 5.0 features with the use of the IBM Database Add-Ins for Visual Studio product:
  • Enum support
  • Multiple diagrams per model
  • Batch import of stored procedures
For more information, see Microsoft Entity Framework 5.0 support.

Version 10.5: Support for session global variables

You can now specify session global variables in the IBM data server driver configuration file. The following conditions apply to the use of session global variables:
  • The database server must be a DB2 for Linux, UNIX, and Windows server.
  • You must specify the session global variables in the <sessionglobalvariables> subsection in the IBM data server driver configuration file.
  • Before you connect to the database server, you must create the session global variables.
For more information, see IBM data server driver configuration file structure.

Version 10.5: Change in the number of supported characters for client information keywords and properties

The size limit of the client information keywords and properties is enhanced:
  • You can now specify up to 255 characters for the following client information keywords in the IBM data server driver configuration file:
    • ClientAccountingString
    • ClientApplicationName
    • ClientWorkstationName
    For more information, see IBM data server driver configuration keywords for client information.
  • You can now specify up to 128 characters for the ClientUserID IBM data server driver configuration keyword. For more information, see IBM data server driver configuration keywords for client information.
  • You can now specify up to 255 characters for the following DB2ConnectionStringBuilder client information properties:
    • DB2ConnectionStringBuilder.ClientAccountingString
    • DB2ConnectionStringBuilder.ClientApplicationName
    • DB2ConnectionStringBuilder.ClientWorkstationName
    For more information, see DB2ConnectionStringBuilder properties.
  • You can now specify up to 128 characters for the DB2ConnectionStringBuilder.ClientUserID client property. For more information, see DB2ConnectionStringBuilder properties.
  • You can now specify up to 255 characters for the following DB2Connection client information properties:
    • DB2Connection.ClientAccountingInformation
    • DB2Connection.ClientApplicationInformation
    • DB2Connection.ClientWorkStation
    For more information, see DB2Connection properties.
  • You can now specify up to 128 characters for the DB2Connection.ClientUser property. For more information, see DB2Connection properties.