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 24 on panel DSNTIPB |
| DSNZPxxx: | DSN6SPRM ABIND |
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.
Tip: 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. For details, see Rebind old plans and packages in Db2 12 to avoid disruptive autobinds in Db2 13.
Important: Apply APAR PI87675 to remove the possibility of
repeating automatic remigration binds.
- COEXIST or YES
-
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 Db2 11 runs in Db2 13.
- In release coexistence or fallback, a package or plan that was last bound on Db2 13 runs again on Db2 12. After the automatic bind, the package or plan continues to run without automatic binds, even if it runs again on Db2 13. Packages and plans continue to run on Db2 13 as bound on Db2 12. The plan or package does not use any new features that Db2 13 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 13 attempts to run on Db2 12.