Runs the BIND PACKAGE command and closes the window. Available when the required fields are complete.

Cancels any changes and closes the notebook.

Displays the BIND PACKAGE command that would be generated by your choices in this window. Available when the required fields are complete.

Opens the Build JCL dialog. Available when the required fields are complete.

Displays a list of locations to select from.

Specify the name of a location where the package binds and where the description of the package resides, or use the browse button to display a list of locations to select from. When binding an existing package, this field is pre-filled and cannot be edited. When binding a new package, the default value is blank, in which case the local DBMS will be used.

Displays a list of collections to select from.

Specify the name of the collection containing the package that you want to bind, or use the browse button to display a list of collections to select from. When binding an existing package, this field is pre-filled and cannot be edited.

Select to include a database request module (DBRM) in the package.

Specify the library of which a DBRM is a member, or use the browse button to display a list of libraries to select from. When binding an existing package, this field is pre-filled and cannot be edited.

Opens a window from which you can select from a list of libraries.

Specify a library member that contains a database request module (DBRM) that you want to include in the package, or use the browse button to display a list of library member names to select from. When binding an existing package, this field is pre-filled and cannot be edited.

Opens a window from which you can select from a list of library members.

Select to copy an existing package.

Displays a list of packages to select from.

Specify the name of the collection containing the package to copy.

Specify whether to use COMPOSITE or COMMAND bind options for the new package.

Specify the name of a package to copy.

Specify the version of a package to copy.

Optional. Specify whether to use COMPOSITE or COMMAND bind options for the new package:

COMPOSITE
Options that you do not specify when binding are copied from the SYSPACKAGE catalog table row that describes the source package to be copied.
COMMAND
For options that you do not specify, the DB2-defined or server-defined BIND values are used, depending on whether you're creating a local or a remote copy.

Optional. Select YES or NO to indicate if you want to obtain EXPLAIN output for SQL statements in the package, or in the member list of the plan:

NO
Explain output is not obtained.
YES
Explain output is obtained.

Optional. Select the level of message flagging (FLAG option). Choose the types of messages to report:

Optional. Select whether any OBJECT NOT FOUND or NOT AUTHORIZED errors found during bind or rebind should be re-checked at run time:

RUN
The bind will still succeed if OBJECT NOT FOUND or NOT AUTHORIZED errors occur during the bind or rebind.
BIND
The bind will not succeed if OBJECT NOT FOUND or NOT AUTHORIZED errors occur during the bind or rebind.

Optional. Select to specify that SQL errors will not halt the binding process. Any invalid SQL statements will cause errors when the application is run.

Select to replace an existing package (ACTION(REPLACE) option).

Select to replace a specific version of the package.

Specify the package version to replace (REPLVER option).

Select to add this package as a new package (ACTION(ADD) option). An error will occur if a package exists with the same name.

Optional. Specify whether immediate writes will be done for updates made to group buffer pool dependent page sets or partitions:

NO
Normal write activity. Updated pages that are group buffer pool dependent are written at or before phase one of commit or at the end of abort for rolled back transactions.
PH1
Updated pages that are group buffer pool dependent are written at or before phase one of commit.
YES
Updated pages that are group buffer pool dependent are written when the buffer update completes.

Optional. Specify whether or not data currency is required for read-only and ambiguous cursors when the isolation level of cursor stability is in effect:

YES
Data currency is required. This option disables block fetching for distributed, ambiguous cursors.
NO
Data currency is not required.

Optional. Specify the degree to which the application should be isolated from the effects of other applications that are running:

Not specified
Use the value for this option that is set for the package.
RR
Repeatable Read
RS
Read Stability
CS
Cursor Stability
UR
Uncommitted Read
NC
No Commit

Optional. Specify when to release resources that a program uses:

Not specified
Use the value for this option that is set for the package.
COMMIT
Release resources at each commit point.
DEALLOCATE
Release resources only when the application terminates.

Optional. Select a value for the DYNAMICRULES option, which determines how dynamic SQL statements will be processed (DYNAMICRULES option):

Not specified
Use the value for this option that is set for the plan.
RUN
Use run behavior.
BIND
Use bind behavior.
DEFINEBIND
Use define behavior or bind behavior.
DEFINERUN
Use define behavior or run behavior.
INVOKEBIND
Use invoke behavior or bind behavior.
INVOKERUN
Use invoke behavior or run behavior.

Optional. Specify whether to determine an access path at run time for host variables, parameter markers and special registers (REOPT(VARS) option). The options available depend on the subsystem that you are connecting to:

NO
Determine an access path at run time.
YES
Do not determine an access path at run time.
NONE
Do not determine an access path at run time.
ONCE
Re-optimize the access path the first time the application is run.
ALWAYS
Re-optimize the access path every time the application is run.

Optional. Specify whether or not the preparation of SQL statements that refer to remote objects should be deferred or processed immediately (DEFER(PREPARE) option).

Not specified
Use the value for this option that is set for the plan.
NO
Preparation of SQL statements is not deferred.
YES
Preparation of SQL statements is deferred. Dynamic statements are prepared when DB2 encounters a statement of the type EXECUTE, OPEN, OR DESCRIBE that refers to the dynamic statement.

Optional. Specify whether or not dynamic SQL statements should be kept after commit points (KEEPDYNAMIC option).

NO
Dynamic SQL statements are not kept after each commit point.
YES
Dynamic SQL statements are kept after each commit point.

Optional. Specify the degree of parallel processing for the execution of static SQL statements (DEGREE option):

1
No parallel processing
Any
Execution of a statement can involve parallel processing using a degree determined by the database manager.

Optional. Specify whether query optimization hints are used for static SQL statements. Choose Normal optimization to specify that DB2 does not use optimization hints for static SQL statements, or specify an optimization hint of up to 128 characters (up to 8 characters for version 7 and earlier). To edit this field, optimization hints must be enabled on your system. To enable optimization hints, specify YES in the OPTIMIZATION HINTS field of the installation panel DSNTIP4.

Optional. Select the type of encoding used by the package, or type in a valid ccsid. The ccsid option is valid if you specified ccsid as the value on the install panel DSNTIPF as the system EBCDIC ccsid.

Displays a list of qualifiers to select from.

Optional. Enter an implicit qualifier to use for unqualified names of tables, views, indexes, and aliases contained in the package, or use the browse button to display a list qualifiers to select from.

Displays a list of schemas to select from.

Moves the selected schema from the Available schemas list to the Selected schemas list.

Moves all of the schemas in the Available schemas list to the Selected schemas list.

Moves the selected schema from the Selected schemas list to the Available schemas list.

Moves all of the schemas in the Selected schemas list to the Available schemas list.

Displays a list of schemas that have been selected from the Available schemas list.

Moves the selected schema one position higher in the list.

Moves the selected schema one position lower in the list.

Opens the Manage Schema window from which you can create, change or remove schemas.

Optional. Specify which protocol to use when connecting to a remote site that is identified by a three-part name statement:

DRDA
Three-part name statements in the plan or package are converted to DRDA protocol.
PRIVATE
Three-part name statement are not converted to DRDA protocol.

Displays a list of authorization IDs to select from.

Optional. Specify an authorization ID as the owner of the package (OWNER option). You can use the browse button to display a list of authorization IDs.

List of connection types that will be disabled for the package.

Moves the selected connection type from the disabled list to the enabled list.

Moves all of the connection types from the disabled list to the enabled list.

Moves the selected connection type from the enabled list to the disabled list.

Moves all of the connection types from the enabled list to the disabled list.

List of connection types that will be enabled for the package.

Optional. Specify one or more IDs of DL/I batch connections enabled for the package (DLIBATCH(connection-name, ...) option). Separate the connection IDs by commas.

Optional. Specify one or more node names of CICS VTAM nodes enabled for the package (CICS(applid,...) option). Separate the node names by commas.

Optional. Specify one or more IDs of IMS BMP connections enabled for the package. (IMSBMP(imsid,...) option). Separate multiple IDs with commas.

Optional. Specify one or more IDs of IMS MPP connections enabled for the package. (IMSMPP(imsid,...) option). Separate multiple IDs with commas.

Optional. Specify one or more location names or logical unit names (LUNAMES) identifying the remote connections enabled for the package (REMOTE(connection-name,...,<luname>,...) option). Separate the connection names and LUNAMES by commas.