Skip to Content

ABIND—Enable automatic rebind

Use the Modify Automatic Rebind panel or the ABIND command to specify whether plans and packages are automatically rebound. To reduce the overhead and catalog contention that is occurring during peak periods, you can change ABIND to NO.

Modify Automatic Rebind panel

DDTG DBI1 Modify Automatic Rebind
Command ===> _________________________________________________________________

 Command: CURRENT
Description . . . . . . . . : ENABLE AUTOMATIC REBIND

Type the new Automatic Rebind Indicator that you wish to change to.
Then press Enter.

Automatic Rebind
Rebind Indicator . . . . . . _______ (YES, NO, COEXIST)

Command syntax and parameters

image2018-12-19_16-46-58.png

Value

Description

DB2ssid

Db2 subsystem ID or the name of the Db2 data sharing group to which the command applies.

opertuneID

OPERTUNE system profile name (if OPERTUNE is running as a started task) or the batch job name (if OPERTUNE is running as a batch job).

YES

Plans and packages are automatically rebound at execution time when a plan or package

  • Is “invalid” (the SYSPLAN or SYSPACKAGE VALID column is N)
  • Was last bound on Db2 v9, but is now running on a previous version)
  • Was last autobound on a previous version of Db2, but is now running on v9
  • Was last bound on Db2 version 8, but is now running on a previous version)
  • Was last autobound on a previous version of Db2, but is now running on version 8

YES is the Db2 default.

NO

Plans and packages are not automatically rebound under any circumstances

Using this option reduces overhead and catalog contention that may occur during peak periods.

COEXIST

Plans and packages in a Db2 Data Sharing coexistence environment are automatically rebound. A plan or package must meet one of the following criteria:

  • Is marked invalid (the SYSPLAN or SYSPACKAGE VALID column is N)
  • Was last bound on a Db2 version 8 subsystem and is now running on a previous version of Db2
    In this case, Db2 performs an autobind on the previous version. The autobind is performed only for the first attempt to run the plan or package on the previous version of Db2.

If COEXIST is specified for a non-Data Sharing Db2 environment, when Db2 is determining whether an autobind can be performed, COEXIST is ignored and the default value (YES) is used instead. YES allows a “previous version to version 8” autobind on version 8 after a previous “version 8 to a previous version” autobind was performed on the previous version. After all Db2 members have been migrated to the same level, COEXIST will be interpreted by Db2 as YES.

  • was last bound on a Db2 version 9 subsystem and is now running on version 8 of Db2
    In this case, Db2 performs an autobind on version 8. The autobind is performed only for the first attempt to run the plan or package on version 8 of Db2.

The value COEXIST is relevant only in a data-sharing environment. If COEXIST is specified for a non-data sharing Db2 environment, when Db2 is determining whether an autobind can be performed, COEXIST is ignored and the default value (YES) is used instead. YES allows a version 8 to version 9 autobind on version 9 after a previous “version 9 to a previous version” autobind was performed on the previous version. After all Db2 members have been migrated to the same level, COEXIST will be interpreted by Db2 as YES.

NORESET

The changes you request remain in effect until the Db2 subsystem is cycled.

Db2 parameter values

Field

Installation panel

CLIST parameter

ZPARM macro

ZPARM parameter

Rebind Indicator

DSNTIPO

ABIND

DSN6SPRM

ABIND



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

OPERTUNE for DB2 12.1