You can find out whether rebinding packages after making
changes to your system would change access plans and whether those
changes would slow the execution of your SQL statements.
About this task
Use this option in scenarios such as:
- Identifying packages whose performance can be impacted following DB2® migration from one release to
another. It can help you identify packages that can benefit from REBIND
after migration and packages that should not be rebound
- After running RUNSTATS to identify packages whose performance
can be impacted if a REBIND is performed.
Procedure
To compare access plans for two sets of identical packages
that are in two different collections:
- Before making changes to your system, bind the packages
that you plan to analyze, setting the EXPLAIN option
to YES.
- Make changes to your system that you believe might affect
the access plans for the statements that are in those packages.
- Bind the same packages to a new collection, setting the EXPLAIN option
to YES.
- Create a comparable workload and run
the comparison. A comparable workload is a
workload that you create specifically for the comparison. It a logically
grouping of both the packages that are in the original collection
and the packages that are in the new collection.
- In the Data Source Explorer, connect to the DB2 for z/OS® subsystem on which the collections are
located.
- Right-click the connection and select .
- Click the Manage tab on the left
side of the workflow assistant to open the Manage section.
- On the Manage Workloads page, click
the Create Workload for Comparison icon, which
is at the top of the page and looks like this:

- Follow the steps in the Create Workload for
Comparing Access Plans in Packages wizard.
- On the Comparison History page,
select the comparison and click Review Results.
Results
The
View Comparison Results by Package Summary page
opens. Double-click listed packages to see the comparisons of individual
statements.