|
Replace Version
|
Specifies the new version name for a replacement package. This field is available only when you select the Replace option from the Action drop-down list in the Bind Package dialog box. |
|
Replace Authorization
|
One of the following options:
- Retain uses the SQLID assigned to the existing package on the host.
- Revoke uses the current SQLID specified in the Bind Utility window.
This field is available only when you select the Replace option from the Action drop-down list in the Bind Package dialog box.
|
|
Creation Control
|
One of the following options:
- No Error Allowed does not create a package if an error occurs during the bind process.
- Error Allowed creates a package even if an error occurs during the bind process.
- Check Only executes the bind without creating a package. Use this option to test the bind operation without actually creating a package.
|
|
Existence Checking
|
One of the following options:
- Optional creates a package even if database objects referenced in the DBRM do not exist. Use this option to create a package prior to defining all data objects.
- Required creates a package only if all database objects referenced in the DBRM exist.
|
|
Blocking Protocol
|
One of the following options:
- Single Row returns data one row at a time for all cursors that are read-only or are ambiguous. This option provides maximum control of data transfer.
- Limited Block returns data in blocks (of the size you have specified in the Gateway Profile Utility) for all cursors that are read-only or are ambiguous. This option can improve performance significantly. It provides maximum data-transfer speed. For more information about specifying block size, see your Link Configuration Guide.
- Forced Single Row returns data one row at a time regardless of the read-only status of the cursor.
|
|
Resource Release
|
One of the following options:
- Commit releases database resources after a commit. Provides a high level of concurrency.
- Deallocation releases database resources when the connection is terminated.
|
|
Explain
|
One of the following options:
- No Statements disables the EXPLAIN option to create the package without generating descriptive information.
- All Statements enables the EXPLAIN option to write descriptive information about the package to owner.PLAN_TABLE. This table must exist before you execute the bind.
|
|
Package Owner
|
The AuthID assigned to the package. This DB2 AuthID must have authority to execute all the SQL in the package. |
|
Default Qualifier
|
The AuthID used to complete any unqualified (one-part) table names in the DBRM file. If you leave this field blank, the Bind Utility uses the current SQLID. |
|
Dynamicrules
|
Controls the behavior of dynamic SQL with regard to one part name qualification and permissions checking:
- DYNAMIC RULES RUN: The AuthID used for checking permissions of dynamic SQL statements will be the value of the CURRENT SQLID special register. The default value of the CURRENT SQLID special register is the AuthID of the process. Users with SYSADM authority can change their CURRENT SQLID special register to any value and users with secondary AuthIDs can change their CURRENT SQLID special register to be any of their secondary AuthIDs.
The AuthID used for qualifying one part names of tables, views, etc. will be the value of the CURRENT SQLID special register. As stated above, the special register value can be changed under certain circumstances.
There are no restrictions on commands that can be executed.
- DYNAMIC RULES BIND: The AuthIDs of the package is used for checking permissions of dynamic SQL statements.
The value of the Default Qualifier text box will be used for qualifying one part names of tables, views, etc. If the Default Qualifier text box is left blank, the AuthIDs of the package is used for qualifying one part names of tables, views, etc.
When this option is in effect, you cannot issue the following dynamic SQL statements: ALTER, CREATE, DROP, GRANT, RENAME, and REVOKE.
If left blank, this option defaults to DYNAMIC RULES RUN.
|
