Installation and Configuration Supplement

Binding Database Utilities

You must bind the database utilities (import, export, reorg, the command line processor) and DB2 CLI bind files to each database before they can be used with that database. In a network environment, if you are using multiple clients that run on different operating systems or are at different versions or service levels of DB2, you must bind the utilities once for each operating system and DB2-version combination.

Binding a utility creates a package, which is an object that includes all of the information that is needed to process specific SQL statements from a single source file.

The bind files are grouped together in different .lst files in the bnd directory, under the installation directory (typically sqllib\win on Windows 3.x systems and sqllib for OS/2, and Windows 32-bit operating systems). Each file is specific to a server.

How you bind the database utilities to a database depends on your workstation's operating system:

On OS/2 and Windows 32-bit operating systems, you can use the Client Configuration Assistant by performing the following steps:

step  1.
Start the Client Configuration Assistant (CCA).
step  2.
Select the database to which you want to bind the utilities.
step  3.
Click on the Bind push button.
step  4.
Select the Bind DB2 Utilities radio button.
step  5.
Click on the Continue push button.
step  6.
Enter a user ID and password to connect to the database. The user ID must have the authority to bind new packages against the database.
step  7.
Select the utilities you want to bind and click on OK.

On all operating systems, you can use the command line processor by performing the following steps:

step  1.
Change to the bnd directory in the install path. For example:

For UNIX platforms
INSTHOME/sqllib/bnd
For all other platforms
x:\sqllib\bnd, where x: is the drive where you installed DB2

step  2.
Connect to the database using the command:
connect to database_alias

where database_alias is the name of the database to which you want to connect.
step  3.
Enter the following commands in the Command Center or the command line processor:
"bind @db2ubind.lst messages bind.msg grant public" "bind @db2cli.lst messages clibind.msg grant public"

In this example, bind.msg and clibind.msg are the output message files, and EXECUTE and BINDADD privileges are granted to public.
step  4.
Reset the connection to the database by entering the following command:
connect reset

For more information on the bind command, refer to the Command Reference.

Notes:

The db2ubind.lst file contains the list of bind (.bnd) files required to create the packages for the database utilities. The db2cli.lst file contains the list of bind (.bnd) files required to create packages for the DB2 CLI and the DB2 ODBC driver.
Binding may take a few minutes to complete.
To bind to databases that reside on OS/390, MVS, VM, or AS/400, refer to the DB2 Connect User's Guide for instructions.
If you have BINDADD authority, the first time you use the DB2 CLI or ODBC driver, the DB2 CLI packages will be bound automatically.

If the applications that you are using require binding to the database, you can use the Client Configuration Assistant's Bind facility, or the command line processor, to perform the bind action.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]

step 1.	Start the Client Configuration Assistant (CCA).
step 2.	Select the database to which you want to bind the utilities.
step 3.	Click on the Bind push button.
step 4.	Select the Bind DB2 Utilities radio button.
step 5.	Click on the Continue push button.
step 6.	Enter a user ID and password to connect to the database. The user ID must have the authority to bind new packages against the database.
step 7.	Select the utilities you want to bind and click on OK.