db2dsdcfgfill - Create configuration file db2dsdriver.cfg

Creates and populates the db2dsdriver.cfg configuration file.

Description

The db2dsdcfgfill command reads in the local database directory information to populate or update the db2dsdriver.cfg configuration file when you have installed one of the following products:

IBM® Data Server Client
IBM Data Server Runtime Client
One of the IBM database server products

Command syntax

Command parameters

-i instance_name

Specifies the name of the database manager instance whose database directory, node directory, and Database Connection Services (DCS) directory are used as input.

You cannot use this parameter with the -p or -migrateCliIniFor.NET parameter.

-p instance_path

Specifies the full path of the database manager instance directory under which the system database directory, node directory, and DCS directory are located.

You cannot use this parameter with the -i or -migrateCliIniFor.NET parameter.

-migrateCliIniFor.NET

Copies certain entries from the db2cli.ini file into the db2dsdriver.cfg file. This parameter is for Microsoft Windows systems only. Only the following keywords are migrated:

Txnisolation
Connecttimeout
Currentschema

The keywords are migrated in the following manner:

Entries in the common section of the db2cli.ini file are copied to the global section of the db2dsdriver.cfg file.
Entries that have a database name, host name, and port information are copied to the database section.
Entries for cataloged databases are copied to the data source name section.

You cannot use this parameter with the -i or -p parameter.

Restriction: For .NET applications and applications that use embedded SQL, the IBM Data Server Client and IBM Data Server Runtime Client can use the db2dsdriver.cfg file to retrieve only Sysplex-related settings.

-db2cliFile db2cli.ini_path

Specifies the full path of the db2cli.ini file. This parameter is for Microsoft Windows systems only.

-o output_path

Specifies the path where the db2dsdcfgfill command creates the db2dsdriver.cfg configuration file.

If you do not specify a value for this parameter and you have a copy of the db2dsdriver.cfg file from Version 9.7 Fix Pack 2 or earlier, that copy is replaced. Otherwise, if you do not specify a value for this parameter, the db2dsdriver.cfg configuration file is created in a directory that depends on your driver type and operating system. For information about the location of the db2dsdriver.cfg file, see the "db2dsdriver configuration file" topic.

-h

Displays usage information.

Usage notes

When you run the db2dsdcfgfill command without the -migrateCliIniFor.NET parameter, if a db2dsdriver.cfg configuration file already exists in the output directory, the existing db2dsdriver.cfg configuration file is overwritten. However, when the -migrateCliIniFor.NET option is used with an existing db2dsdriver.cfg file, it will merge the information into the existing file instead.

The db2dsdcfgfill command indicates Lightweight Directory Access Protocol (LDAP) data source name (DSN) or LDAP database entries with the ladp=1 attribute. Only the database entries in the local database directory that have the LDAP directory entry type can have the ladp=1 attribute. The sample DSN entry in the following db2dsdriver.cfg file is created from the LDAP DSN information with the db2dsdcfgfill command.

<configuration>
<dsncollection>
    <dsn alias="sample" name="sample" host="hotel53.torolab.ibm.com" port="40576 ldap=1/>
</dsncollection>
    <databases>
         <database name="sample" host="hotel53.torolab.ibm.com" port="40576">
         </database>
    </databases>
</configuration>