AUTO BIND field (ABIND subsystem parameter)
The ABIND subsystem parameter specifies whether DB2® automatically rebinds packages and plans in certain situations at run time.
| Acceptable values: | YES, NO, COEXIST |
| Default: | YES |
| Update: | option 15 on panel DSNTIPB |
| DSNZPxxx: | DSN6SPRM ABIND |
Tip: Automatic rebinds can improve the availability and administration of packages and
plans, by reducing the need for explicit rebinds. However, automatic binds can also harm performance
because they require access to the DB2
catalog and directory, resource contention might cause them to fail, and they might result in access
path regressions. For best results enable automatic binds by specifying COEXIST in data-sharing
environments and YES in non-data-sharing environments, but also take action to avoid
migration-related automatic binds.
- YES
- Specifies that DB2 automatically
rebinds packages or plans at run time in the following conditions:
- A package runs that is marked invalid (VALID='N' in the SYSIBM.SYSPACKAGE catalog table).
- A package that was last bound in a release earlier than Version 6 Release 1 runs in DB2 10.
- In release coexistence or fallback, a package or plan that was last bound on DB2 10 and it runs again on DB2 9 or Version 8. After the automatic bind, the package or plan can continue to run without automatic binds until it runs on DB2 10 again.
- In release coexistence or during remigration after fallback, a package or plan that was automatically bound on DB2 9 or Version 8 runs again on DB2 10. These automatic binds are called remigration binds.
- COEXIST
- Specifies that no automatic remigration binds occur. DB2 automatically rebinds packages or plans at run
time in the following conditions:
- A package that is marked invalid runs (VALID='N' in the SYSIBM.SYSPACKAGE catalog table).
- A package that was last bound in a release earlier than Version 6 Release 1 runs in DB2 10.
- In release coexistence, the package was last bound on DB2 10 and it runs again on DB2 9 or Version 8. After the automatic bind, the package or plan can continue to run without automatic binds, even if it runs again on DB2 10. Packages and plans continue to run on DB2 10 as bound on DB2 9 or Version 8. The plan or package does not use any new features that DB2 10 introduces.
- NO
- Specifies that no automatic binds occur. If any of the following conditions are true when a
package attempts to run, DB2 issues
SQLCODE -908 SQLSTATE 23510, unless you explicitly rebind the package:
A package is marked invalid (VALID='N' in the SYSIBM.SYSPACKAGE catalog table).
- A package that was last bound (explicitly or automatically) in DB2 10 attempts to run on DB2 9 or Version 8.