DB2 Version 10.1 for Linux, UNIX, and Windows

IBM data server driver configuration file restrictions

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

The following restrictions apply to the IBM data server driver configuration file:
  • The configuration file cannot contain multiple identical entries for a database with 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, port) must contain a value.
  • If multiple parameters are defined on a single line, they are ignored.
  • Only one LDAP section (<ldapserver>) is allowed in the IBM data server driver configuration file.
  • The LDAP section (<ldapserver>) settings are not recognized by the .NET and embedded applications.
  • If multiple <specialregisters> subsections are defined, all the special register parameters that are defined in various <specialregisters> subsections are merged.
  • The SQLReloadConfig() function cannot be used to reload changes to the <specialregisters> subsection.
  • The <specialregisters> subsection has no effect when you connect to the database with the DB2® command line processor (CLP) or an embedded SQL application.
  • The <specialregisters> subsections cannot be added to the IBM data server driver configuration file with the db2cli writecfg command.
  • The following special register names are not supported in the <specialregisters> subsection:
    • CURRENT CLIENT_ACCTNG
      The short name of the special register is CLIENT ACCTNG. To set the CLIENT ACCTNG special register, set the ClientAccountingString keyword in the supported section outside of 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 of 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 of 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 of 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 of 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 of the <specialregisters> subsection.