Enabling the use of DDF
Catalog Manager
and
Change Manager
can access remote Db2 subsystems using the Db2 Distributed Data Facility (DDF). If you did not enable the use of DDF during the installation of the products, use the following procedure to enable DDF.
- Edit the HLQ.UBMCCNTL member T1S#CDBS:
- Change the following variables to the values that you used when you installed Catalog Manager or Change Manager. To review the values, see the prdINIT5 or prdINIT6 member in the HLQ.JCL library (where prd is the product code). For Change Manager, also review the values for Common SQL in the ACSINIT5 or ACSINIT6 member.
- Replace **AUTHID with the value for the primary or secondary authorization ID.
- Replace **SQLID with the value of the alias qualifier.
- Replace **COLLID with the value of the collection ID.
(
Change Manager
) For the aliases that are prefixed with CAT2 and CAT3, uncomment the SQL statements and add a dash (-). (That is, change *SQL to -SQL.)
(
Change Manager
) If you are executing the worklist for only Change Manager, comment out the BIND statements for the Catalog Manager packages.
- In the last SQL statement, specify to grant EXECUTE authority to PUBLIC or to specific users.
If you are executing the worklist for both Catalog Manager and Change Manager, repeat this step.
- Change the following variables to the values that you used when you installed Catalog Manager or Change Manager. To review the values, see the prdINIT5 or prdINIT6 member in the HLQ.JCL library (where prd is the product code). For Change Manager, also review the values for Common SQL in the ACSINIT5 or ACSINIT6 member.
- Edit the $740INST job to create a single step to execute the T1S#CDBS worklist for Catalog Manager and for Change Manager.
- Edit the BMCDB2 CLIST:
- Edit the control table.
Specify the servers to use with Catalog Manager CONNECT.The same release level of Catalog Managermust be installed on the remote Db2 subsystems and the Db2 subsystem from which you want to connect. The following example shows that when Catalog Manageris invoked on the DB2P subsystem, it can connect with the DB2A, DB2B, and DB2C servers on remote Db2 subsystems. In this example, the unique nicknames combine the server name and SSID.
*PROD SSID S SERVER NAME SSID COLL_ID NICKNAME
*----|----|-|-----------------|----|------------------|------------------------
ACT DB2P S DB2A DB2A ACTvr_D_MAIN DB2PDB2A *
ACT DB2P S DB2B DB2B ACTvr_D_MAIN DB2PDB2B *
ACT DB2P S DB2C DB2C ACTvr_D_MAIN DB2PDB2C *- Press END to exit.
Related topic