DB2 Connect User's Guide

Rebinding

After you bind your application (and create the package on the host or AS/400 database server), you may find that you need to recreate that package. It is possible to do this without having the original bind file, by using the command line processor REBIND PACKAGE command or corresponding API.

The benefits of using this command are:

• You can take advantage of changes in the system by re-optimizing and building new package sections without having the original bind file.

• You can recreate packages that have been made inoperative or invalid.

• You can recreate packages that have been invalidated by migration.

• You can improve performance by using an explicit rebind rather than using an implicit rebind or a bind.

• You can change characteristics. For example, with DB2 Universal Database for OS/390, you can change the qualifier of unqualified tables for testing or migration purposes.

If you want to modify a program, the bind options, or any owner information, you should use the BIND command. Also, if the package does not exist in the database, or if you want to see all bind errors (not only the first detected error), you should use the BIND command.

To run this command, you need the level of authority required by your host or AS/400 database server. If you are not connected to a database, the command will cause an implicit connect to be done to the default database (if you have connect privileges).

The syntax of the command line processor command is described in the Command Reference.

To find out the package name for a bind file, enter the following command:

  ddcspkgn bindfile.bnd

[ DB2 List of Books | Search the DB2 Books ]