DB2 package

A DB2® package that exists on the DB2 database or that pureQuery is proposing that you create.
What happens when you select a DB2 package in the SQL Outline view
The properties of the DB2 package that are specifically relevant to pureQuery appear in the Properties view. These properties are:
Collection ID
The collection in which the package is located.
Consistency Token
The timestamp for when the package was created.
Root Package Name
The root name that you specified for all of the packages that contain the same set of SQL statements. For example, you might have created one package for each of the isolation levels. Each package would contain the same SQL statements, but the name of each would be the root name and a number that indicates the isolation level.
Version ID
The version that you specified or that was generated automatically for the package.
What happens when you double-click a DB2 package in the SQL Outline view
If the DB2 package exists on the connected database, the full set of properties of the table appear in the Properties view.
In the Data Source Explorer, the workbench highlights the packages that exist for all of the isolation levels that were specified in the Default.bindProps file when you started the bind operation.

The SQL Outline view is indifferent to isolation levels for DB2 packages. It displays packages by their root name only.

What options appear when you right-click a DB2 package in the SQL Outline view
Bind
For DB2 data sources: Runs the StaticBinder utility to bind the SQL statements in the package. Before you select this option, in the Default.bindProps file for your Java™ project specify bind options for the annotated-method interface, implementation class for such an interface, or the pureQueryXML file in which the SQL statements are located.

Besides binding the package, the workbench displays in the Console view the command that it sends to the StaticBinder utility. You can copy the command if you want to run it from a command line with the StaticBinder utility at a later time.

For information about using the Default.bindProps file in your project, see these topics:
Show in Data Source Explorer
Causes the workbench to highlight in the Data Source Explorer the packages that exist for all of the isolation levels that were specified in the Default.bindProps file when you started the bind operation.

Feedback