IBM data server driver configuration file restrictions

There are some restrictions on the use of the IBM® data server driver configuration file.

The following restrictions apply:
  • User level db2dsdriver.cfg support is not applicable for WLB/ACR, Special register section, Session global variables, and LDAP server section. SQLReloadConfig() function and CfgRefreshInterval IBM data server driver configuration keyword is not supported for user level db2dsdriver.cfg file.
    Note: Location of User level db2dsdriver.cfg is: C:\ Users<User Name><cfg_file_name>
  • The configuration file cannot contain multiple database entries with identical values for all the following properties: database name, server name, and port number. In addition, the configuration file cannot contain multiple identical database alias entries.
  • The <dsncollection> entries (alias, name, host, and port) and the <database> entries (name, host, and port) must contain a value.
  • The database keyword in the connection string of a .NET application can be interpreted as DSN alias or the database name. If only the Database keyword is specified in the application connection string, information in the <dsncollection>, <databases>, and <parameters> sections are read in. However, if the Database and Server keywords are specified in the application connection string, only the <databases> and <parameters> sections are read in.
  • If you define multiple keywords on a single line, they are ignored.
  • Only one LDAP (<ldapserver>) section is allowed.
  • The LDAP (<ldapserver>) sections settings are not recognized by .NET and embedded applications.
  • If you define multiple <specialregisters> subsections, all the special register parameters that you define in the <specialregisters> subsections are merged.
  • You cannot use the SQLReloadConfig() function to reload changes to the <specialregisters> subsection.
  • The <specialregisters> subsection has no effect when you connect to the database by using the Command Line Processor (CLP) or an embedded SQL application.
  • You cannot add <specialregisters> subsections by using the db2cli writecfg command.
  • The following special register names are not supported in the <specialregisters> subsection:
    • CURRENT CLIENT_ACCTNG
      The short name of this special register is CLIENT ACCTNG. To set the CLIENT ACCTNG special register, set the ClientAccountingString keyword in the supported section outside the <specialregisters> subsection.
    • CURRENT CLIENT_APPLNAME
      The short name of the special register is CLIENT APPLNAME. To set the CLIENT APPLNAME special register, set the ClientApplicationName keyword in the supported section outside the <specialregisters> subsection.
    • CURRENT CLIENT_CORR_TOKEN
      The short name of the special register is CLIENT CORR_TOKEN. To set the CLIENT CORR_TOKEN special register, set the ClientCorrelationToken keyword in the supported section outside the <specialregisters> subsection.
    • CURRENT CLIENT_PROGRAMID
      The short name of the special register is CLIENT PROGRAMID. To set the CLIENT PROGRAMID special register, set the ProgramID keyword in the supported section outside the <specialregisters> subsection.
    • CURRENT CLIENT_USERID
      The short name of the special register is CLIENT USERID. To set the CLIENT USERID special register, set the ClientUserID keyword in the supported section outside the <specialregisters> subsection.
    • CURRENT CLIENT_WRKSTNNAME
      The short name of the special register is CLIENT WRKSTNNAME. To set the CLIENT WRKSTNNAME special register, set the ClientWorkstationName keyword in the supported section outside the <specialregisters> subsection.
  • You cannot use the following IBM data server driver configuration keywords that are supported by the embedded SQL application when you use the CLP.
    • ClientAccountingString
    • ClientApplicationName
    • ClientCorrelationToken
    • ClientUserID
    • ClientWorkstationName
    • enableDefaultClientInfo
  • If you define multiple <sessionglobalvariables> subsections, all the session global variable parameters in the <sessionglobalvariables> subsections are merged.
  • You cannot use the SQLReloadConfig() function to reload changes to the <sessionglobalvariables> subsection.
  • The <sessionglobalvariables> subsection has no effect unless you are connecting to the database server with the CLI driver or IBM Data Server Provider for .NET.
  • When you connect to Db2® servers, you can specify only session global variables that you created with the CREATE VARIABLE command in the <sessionglobalvariables> subsection.
  • Db2 for IBM i servers do not support the automatic client reroute (ACR) feature. Therefore, there is no automatic replay of the session global variables that are listed in the <sessionglobalvariables> subsection when an application reconnects to a Db2 for IBM i server.