There are some restrictions on the use of the IBM® data server driver configuration file.
The following restrictions apply:
- 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.
- 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 DB2® 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 for Linux, UNIX, and Windows servers,
you can specify only session global variables that you created with
the CREATE VARIABLE command in the <sessionglobalvariables> subsection.
- DB2 for 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 i server.