Bind Package
Go Up to Available object actions by DBMS
The Bind Package Wizard lets you set package parameters, add environments, and set package properties.
This wizard is available for the following platform(s):
To Package Parameters, Add Environments, and Set Package Properties
- Expand an owning schema, right-click Packages, and then select Bind from the context menu.
- The Bind Package wizard opens.
- Use the following table as a guide to understanding and setting options on this wizard before clicking Finish:
| Step | Setting | Task | |
|---|---|---|---|
|
1 |
Location |
Lets you select the name of the location to which you want to connect. | |
|
Collection |
Lets you select the location of the DBMS where the package binds and where the description of the package resides. | ||
|
Would you like to Copy an Existing Package from Another Collection | |||
|
New Package |
(Available only when you select No for the Would you like control.) Lets you select a Package Name and PDS Name. | ||
|
Copy Package |
(Available only when you select Yes for the Would you like control.) Lets you qualify with the following:
| ||
|
2 |
Lets you select a package Owner, a Qualifier (the package creator), an Action of ADD or REPLACE, and the Version of the package. | ||
|
3 |
Isolation |
Determines how far to isolate an application from the effects of other running applications. | |
|
Keep Dynamic |
Specifies that DB2 keeps dynamic SQL statements after commit points. The application does not need to prepare an SQL statement after every commit point. DB2 keeps the dynamic SQL statement until the application process ends, a rollback operation occurs or the application executes an explicit PREPARE statement with the same statement identifier. If the prepared statement cache is active, DB2 keeps a copy of the prepared statement in the cache. If the prepared statement cache is not active, DB2 keeps only the SQL statement string past a commit point. DB2 then implicitly prepares the SQL statement if the application executes an OPEN, EXECUTE, or DESCRIBE operation for that statement. | ||
|
Current Data |
Determines whether to require data currency for read-only and ambiguous cursors when the isolation level of cursor stability is in effect. It also determines whether block fetching can be used for distributed, ambiguous cursors. | ||
|
Degree |
Determines whether to attempt to run a query using parallel processing to maximize performance. Lets you select an option. | ||
|
DB Protocol |
Specifies which protocol to use when connecting to a remote site that is identified by a three-part name statement. | ||
|
Dynamic Rules |
Determines what values apply at run time for the following dynamic SQL attributes:
| ||
|
Release |
| ||
|
Validate |
Determines whether to recheck, at run time, errors found during bind. The option has no effect if all objects and needed privileges exist.
| ||
|
4 |
Explain |
Obtains information about how SQL statements in the package are to execute, and then inserts that information into the table owner.PLAN_TABLE, where owner is the authorization ID of the owner of the plan or package. This option does not obtain information for statements that access remote objects. | |
|
Optimization Hint |
Query optimization hints are used for static SQL. | ||
|
Reoptvars |
Re-determines the access path at run time. | ||
|
Encoding |
Lets you select type of language for the package. | ||
|
Defer Prepare |
Optionally, prepares dynamic SQL statements that refer to remote objects. Lets you choose from DEFER(PREPARE) and NODEFER(PREPARE). | ||
|
Degree |
1 or ANY. | ||
|
Page Writes |
NO, PH1, or YES. | ||
|
Flag |
Lets you select flag for messages to display: all (default), completion, error or warning, and informational. | ||
|
5 |
Use the arrow buttons to move system connections between the Disabled Environments and Enabled Environments lists. | ||