Use the Bind Packages page to specify that the Packages Wizard will bind the packages. You can skip this step if you have already bound packages on this database server for the current version of QMF for Windows. The QMF for Windows packages refer to the set of objects that the product uses.
Different packages are bound on the database server depending on the type of connectivity that will be used to access the database server.
DRDA WITH TCP/IP OR SNA CONNECTIVITY
The following packages are bound for servers with DRDA using TCP/IP or SNA connectivity:
Package includes the dynamic SQL used during installation to check for database object existence.
Package includes the dynamic user SQL run with RR isolation level. End users require EXECUTE authority to run the package.
Package includes the dynamic user SQL run with RS isolation level. End users require EXECUTE authority to run the package.
Package includes the dynamic user SQL run with CS isolation level. End users require EXECUTE authority to run the package.
Package includes the dynamic user SQL run with UR isolation level. End users require EXECUTE authority to run the package.
Package includes the dynamic user SQL run with NC isolation level. End users require EXECUTE authority to run the package.
Package includes internal SQL for QMF for Windows. End users require EXECUTE authority to run the package.
Package includes internal SQL for QMF for Windows. End users require EXECUTE authority to run the package. This package is bound only if this server hosts a catalog.
Package includes internal SQL for QMF for Windows administrative functions. This package is bound only if this server hosts a catalog.
Package includes internal SQL for retrieving LOB values. End users require EXECUTE authority to run the package.
Package includes internal SQL for QMF for Windows. End users require EXECUTE authority to run the package. This package is bound only if this server hosts a catalog.
Package includes internal SQL for Report Center. End users require EXECUTE authority to run the package. This package is bound only if this server hosts a catalog.
CLI CONNECTIVITY
The following packages are bound for servers with CLI connectivity:
Package includes internal SQL for QMF for Windows. End users require EXECUTE authority to run the package.
Package includes internal SQL for QMF for Windows. End users require EXECUTE authority to run the package. This package is bound only if this server hosts a catalog.
Package includes internal SQL for QMF for Windows administrative functions. This package is bound only if this server hosts a catalog.
Package includes internal SQL for retrieving LOB values. End users require EXECUTE authority to run the package.
Package includes internal SQL for QMF for Windows. End users require EXECUTE authority to run the package. This package is bound only if this server hosts a catalog.
Package includes internal SQL for Report Center. End users require EXECUTE authority to run the package. This package is bound only if this server hosts a catalog.
Do not bind the packages
Select this radio button to continue through the Packages Wizard without binding the QMF for Windows packages. Choose this option if you have already bound the QMF for Windows packages for this database server and there are no changes.
Bind the packages
Select this radio button to bind the QMF for Windows packages for this database server.
Replace existing packages
This option is available if you selected the Bind the packages option. When this check box is checked, all QMF for Windows packages that exist on this database server with the specified collection ID will be replaced with the newly bound packages.
Keep existing authorizations on packages
This option is available if you selected the Bind the packages option. When you check this check box, the authorizations on the QMF for Windows packages that exist on this database server with the specified collection ID are maintained.
The actual set of privileges required to bind packages depends on the type and version of the database server, the configuration of the database server, and whether the package exists.
The table privileges also vary by whether a QMF catalog is created at the server. Therefore, privileges differ based on the privileges that are always required and privileges that are required if you create a QMF catalog.
The following table describes what privileges are required to act on each of the QMF tables:
If one of your primary authorization IDs does not have these privileges but one of your secondary authorization IDs does, specify the secondary authorization ID as the Owner ID for the packages.
About secondary authorization IDs: Many companies using DB2 UDB for z/OS use a security scheme featuring RACF and DB2 so that when a user signs on to DB2 with a user ID and password, the user is limited to setting the current SQLID to a secondary authorization ID maintained by RACF. The secondary ID is the owner of all the tables and queries. Some users share the same secondary ID and can gain access to the same data and objects.
QMF for Windows is not granted access to this set of secondary authorization IDs when the Object List is created. Instead, it has its own table, RDBI.AUTHID_TABLE that must be populated by the DBA so users can see all familiar tables in the list.
Binding packages opens a connection to the database server. The status line indicates the progress of the bind operation. If errors occur while binding packages, correct them, then repeat the bind. A few errors are described below.
SQL -204 error
An SQL code of -204 indicates that a required table does not exist. Click Create Objects... to create it.
SQL -551 or -552 error
An SQL code of -551 or -552 indicates that the authorization ID on the bind (your user ID or owner ID) is missing at least one authority required to bind the packages (create database objects at the selected database server). See "Required Table Authorities" for more information.