IBM Books

Quick Beginnings for DB2 Extended Enterprise Edition for UNIX

Binding Database Utilities

You must bind the database utilities (import, export, reorg, the command line processor, and DB2 CLI) 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 of DB2, you must bind the utilities once for each operating system/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. Each file is specific to a server.

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


  1. 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.

  2. Binding may take a few minutes to complete.

  3. To bind to databases that reside on OS/390, MVS, VM, or AS/400, refer to the DB2 Connect User's Guide for instructions.

  4. If you have bind 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 ]