Rebinding an application
You need to rebind an application if you want to change any bind options. You also need to rebind an application when you make changes that affect the plan or package, such as creating an index, but you have not changed the SQL statements.
About this task
In some cases, DB2® automatically rebinds the plan or package for you, depending on the value of the ABIND subsystem parameter. For details, see Automatic rebinds.
The following actions might require that you rebind a package:
- Changing the host language or SQL statements in the application. You must replace the package. Precompile, compile, and link the application program. Then issue a BIND command with the ACTION(REPLACE) option.
- Changing your data attributes in ways that invalidate the package. For details, see Changes that invalidate packages.
- Improving access paths selection after reorganizing data with the REORG utility or collecting database statistics with RUNSTATS or other utilities. For more information, see Maintaining data organization and statistics.
- Enabling DB2 to select an access path that uses a newly created index for access to a table.
- Changing the bind options for a package. If an option that you want to change is not available for the REBIND command, issue the BIND command with ACTION(REPLACE) instead.
- Preparing for migration to a new DB2 release. For more information, see .
- Rebinding a package
You need to rebind a package when you make changes that affect the package but that do not involve changes to the SQL statements. For example, if you create a new index, you need to rebind the package. If you change the SQL, you need to use the BIND PACKAGE command with the ACTION(REPLACE) option. - Rebinding a plan
You need to rebind
a plan when you make a change to one of the attributes of the plan,
such as the package list.
- Rebinding lists of plans and packages
In some situations, you need to rebind a set of plans or packages that cannot be described by using asterisks. For example, if a rebind operation terminates, you can generate a rebind subcommand for each object that was not bound. - Generating lists of REBIND commands
To generate a list of REBIND subcommands for a set of packages that cannot be described, use asterisks, and use information in the DB2 catalog. You can then issue the list of subcommands through DSN. - Automatic rebinds
Automatic rebinds occur when an authorized user runs a package or plan and the runtime structures in the plan or package cannot be used. This situation usually results from changes to the attributes of the data on which the package or plan depends, or changes to the environment in which the package or plan runs.
Parent topic: Preparing an application to run on DB2 for z/OS
Related tasks: