Bind Package

From DBArtisan
Jump to: navigation, search

Go Up to Available object actions by DBMS

The Bind Package Wizard lets you set package parameters, add environments, and set package properties.

Platform Availability

To Package Parameters, Add Environments, and Set Package Properties

  1. Expand an owning schema, right-click Packages, and select Bind from the context menu.
    The Bind Package wizard opens.
  2. Use the following table as a guide to understanding and setting options on this wizard:
Step Settings and tasks



Lets you select the name of the location to connect to.


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 if you select No for the Would you like... control)

Lets you select a Package Name and PDS Name.

Copy Package (available if you select Yes for the Would you like... control)

Lets you qualify with the following: Collection - the collection to copy from. Options - COMMAND or COMPOSITE. Package - Lets you select a package. Version - Lets you select a version of the package.


Lets you select a package Owner, a Qualifier (the package creator), an Action of ADD or REPLACE, and the Version of the package.



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.


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: The authorization ID that is used to check authorization

The qualifier that is used for unqualified objects

The source for application programming options that DB2 uses to parse and semantically verify dynamic SQL statements Whether dynamic SQL statements can include GRANT, REVOKE, ALTER, CREATE, DROP, and RENAME statements


Commit - Releases resources at each commit point. Deallocate - Releases resources only when the program terminates.


Determines whether to recheck, at run time, errors found during bind. The option has no effect if all objects and needed privileges exist. Bind - If not all objects or needed privileges exist at bind time, the wizard displays an error messages, and does not bind the package. Run - If not all objects or privileges exist at bind time, the process issues warning messages, but the bind succeeds. DB2 checks existence and authorization again at run time for SQL statements that failed those checks during bind. The checks use the authorization ID of the package owner.



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.


Re-determines the access path at run time.


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).


1 or ANY.

Page Writes

NO, PH1, or YES.


Lets you select flag for messages to display: all (default), completion, error or warning, and informational.


Use the arrow buttons to move system connections between the Disabled Environments and Enabled Environments lists.

3. When ready, click Finish.