DB2 graphic  QMF Version 8

Binding the packages

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.

Package Names

Different packages are bound on the database server depending on the type of connectivity that will be used to access the database server.

Note:
Packages are not bound for ODBC connections because dynamic SQL is used.

DRDA WITH TCP/IP OR SNA CONNECTIVITY

The following packages are bound for servers with DRDA using TCP/IP or SNA connectivity:

CLI CONNECTIVITY

The following packages are bound for servers with CLI connectivity:

Fields

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.

Note:
Your user ID must have the authority to bind packages at the 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.

Note:
This option is recommended if you are binding new QMF for Windows 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.

Note:
This option is recommended if you are binding new QMF for Windows packages.

Privileges required to bind packages

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.

Note:
Refer to your database documentation for more information about the privileges required to bind packages

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:

Table 14. Object Privileges
Table Name Privileges
Q.OBJECT_DATA SELECT, INSERT, UPDATE (except with DB2 UDB for workstation platforms, version 5 or later), DELETE
Q.OBJECT_DIRECTORY SELECT, INSERT, UPDATE, DELETE
Q.OBJECT_REMARKS SELECT (DB2 UDB for workstation platforms, version 5 or later), INSERT, UPDATE, DELETE
Q.OBJ_ACTIVITY_DTL SELECT, INSERT, UPDATE, DELETE
Q.OBJ_ACTIVITY_SUMM SELECT, INSERT, UPDATE, DELETE
Q.RAA_OA_DTL_X SELECT, INSERT, UPDATE, DELETE
Q.RAA_OA_SUMM_X SELECT, INSERT, UPDATE, DELETE
Q.RAA_OBJECT_VIEW SELECT
Q.RAA_OBJECT_VIEW_X SELECT
Q.RAA_OBJ_DATA_X SELECT, INSERT, UPDATE, DELETE
Q.RAA_OBJ_DIR_X SELECT, INSERT, UPDATE, DELETE
Q.RAA_OBJ_REM_X SELECT (DB2 UDB for workstation platforms, version 5 or later), INSERT, UPADTE, DELETE
Q.RAA_SUBTYPE SELECT, INSERT, UPDATE, DELETE
Q.RC_NODE SELECT, INSERT, UPDATE, DELETE
Q.RC_NODE_AUTH SELECT, INSERT, UPDATE, DELETE
RDBI.AUTH_VIEW SELECT
RDBI.CATALOG_DIR_X SELECT, INSERT, DELETE
RDBI.PROFILE_VIEW SELECT, INSERT, UPDATE, DELETE
RDBI.PROFILE_VIEW_X SELECT, INSERT, UPDATE, DELETE
RDBI.RESERVED SELECT
RDBI.RESOURCE_VIEW SELECT, INSERT, UPDATE, DELETE
RDBI.RESOURCE_VIEW_X SELECT, INSERT, UPDATE, DELETE
RDBI.TABLE_VIEW2 SELECT
RDBI.TABLE_VIEW2_X SELECT
RDBI.USER_ADMIN_VIEW SELECT
RDBI.USER_ADMIN_VIEW_X SELECT
RDBI.USER_AUTHID_VIEW SELECT
RDBI.USER_AUTHID_VIEW_X SELECT
SYSCAT.PROCPARMS SELECT (DB2 for workstation platforms, version 5 or later)
SYSCAT.TABAUTH SELECT (DB2 UDB for workstation platforms)
SYSCAT.TABLES SELECT (DB2 UDB for workstation platforms)
SYSIBM.SYSPARMS SELECT (DB2 UDB for z/OS version 6; DB2 UDB for z/OS; and z/OS version 7 and later)
SYSIBM.SYSPROCEDURES SELECT (DB2 for MVS version 4; DB2 for z/OS version 5)
SYSIBM.SYSTABAUTH SELECT (DB2 for MVS; DB2 for z/OS; DB2 UDB for z/OS; DB2 UDB for z/OS; and z/OS)
SYSIBM.SYSTABLES SELECT (DB2 for MVS; DB2 for z/OS; DB2 UDB for z/OS; DB2 UDB for OS/390 and z/OS; DB2 UDB for workstation platforms)
SYSTEM.SYSCATALOG SELECT (Database 2 Server for VSE & VM)
SYSTEM.SYSTABAUTH SELECT(Database 2 Server for VSE & VM)
QSYS2.SYSPARMS SELECT (DB2 for iSeries)
QSYS2.SYSTABLES SELECT (DB2 for iSeries)

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

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.

Note:
If the RDBI_AUTHID_TABLE table is not populated, the users will not see these tables, but they will be able to write SQL queries against those tables.

Errors during bind

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.


Go to the previous page Go to the next page

Downloads | Library | Support | Support Policy | Terms of use | Feedback
Copyright IBM Corporation 1982,2004 Copyright IBM Corporation 1982, 2004
timestamp Last updated: March, 2004