Rebind Plan panel
The Rebind Plan panel is the first of two panels that you use to rebind a plan. This panel lets you specify options for rebinding the plan.
The following figure shows the rebind plan options.
DSNEBP03 REBIND PLAN SSID: DSN
COMMAND ===>_
Enter plan name(s) to be rebound:
1 PLAN NAME ................. ===> (* to rebind all plans)
2 ADDITIONAL PLANS? ......... ===> NO (Yes to include more plans)
Enter options as desired:
3 CHANGE CURRENT DEFAULTS?... ===> NO (NO or YES)
4 OWNER OF PLAN (AUTHID)..... ===> SAME > (SAME, new OWNER)
5 QUALIFIER ................. ===> SAME > (SAME, new QUALIFIER)
6 CACHESIZE ................. ===> SAME (SAME, or value 0-4096)
7 ENABLE/DISABLE CONNECTIONS? ===> NO (NO or YES)
8 INCLUDE PACKAGE LIST?...... ===> SAME (SAME, NO, or YES)
9 CURRENT SERVER ............ ===> (Location name)
10 INCLUDE PATH? ............. ===> SAME (SAME, DEFAULT, or YES)
- 1 PLAN NAME
- Lets you name the application plan to rebind. You can specify
a name of 1–8 characters, and the first character must be alphabetic.
Do not begin the name with DSN, because it could create name conflicts
with Db2. If there are no errors,
the bind process prepares the plan and enters its description into
the EXPLAIN table.
If you leave this field blank, the bind process occurs but produces no plan.
- 2 ADDITIONAL PLANS?
- Lets you indicate whether to name more plans to rebind. Use YES to specify more plans on an additional panel, described at Panels for entering lists of values. The default is NO.
- 3 CHANGE CURRENT DEFAULTS?
- Lets you indicate whether to change the binding defaults. Use:
- NO (default) to retain the binding defaults of the previous plan.
- YES to change the binding defaults from the previous plan.
- 4 OWNER OF PLAN (AUTHID)
- Lets you change the authorization ID for the plan owner. The owner
must have the required privileges to execute the SQL statements in
the plan. The default is the existing plan owner.
The field is scrollable, and the maximum field length is 128.
- 5 QUALIFIER
- Lets you specify the default schema for all unqualified table names, views, indexes, and aliases in the plan. You can specify a schema name of 1–128 characters, which must conform to the rules for the SQL identifier. The default is the authorization ID. This field is scrollable.
- 6 CACHESIZE
- Lets you specify the size (in bytes) of the authorization cache.
Valid values are in the range 0 to 4096. Values that are not multiples
of 256 round up to the next highest multiple of 256. A value of 0
indicates that Db2 does not
use an authorization cache. The default is the cache size specified
for the previous plan.
Each concurrent user of a plan requires 8 bytes of storage, with an additional 32 bytes for overhead.
- 7 ENABLE/DISABLE CONNECTIONS?
- Lets you specify whether you want to enable and disable system
connections types to use with this plan. This is valid only for rebinding
on your local Db2 system.
Placing YES in this field displays a panel (shown in Figure 1) that lets you specify whether various system connections are valid for this application.
The default is the values used for the previous plan.
- 8 INCLUDE PACKAGE LIST?
- Lets you include a list of collections and packages in the plan.
If you specify YES, a separate panel displays on which you must enter
the package location, collection name, and package name for each package
to include in the plan (see Panels for entering lists of values).
This field can either add a package list to a plan that did not have
one, or replace an existing package list.
You can specify a location name of 1–16 characters, a collection ID of 1–18 characters, and a package ID from 1 to 8 characters. Separate two or more package list parameters with a comma. If you specify a location name, it must be in the catalog table SYSIBM.LOCATIONS. The default location is the package list used for the previous plan.
- 9 CURRENT SERVER
- Lets you specify the initial server to receive and process SQL
statements in this plan. You can specify a name of 1–16 characters,
which you must previously define in the catalog table SYSIBM.LOCATIONS.
If you specify a remote server, Db2 connects to that server when the first SQL statement executes. The default is the name of the local Db2 subsystem.
- 10 INCLUDE PATH?
- Indicates which one of the following actions you want to perform:
- Request that Db2 uses the same schema names as when the plan was bound for resolving unqualified distinct type, user-defined function, and stored procedure names in SQL statements. Choose SAME to perform this action. This is the default.
- Supply a list of schema names that Db2 searches when it resolves unqualified distinct type, user-defined function, and stored procedure names in SQL statements. Choose YES to perform this action.
- Request that Db2 resets the SQL path to SYSIBM, SYSFUN, SYSPROC, and the plan owner. Choose DEFAULT to perform this action.