BMC Software, Inc., Confidential and Proprietary Information
7-8 Administrative Products for DB2 Installation Guide
Installation Considerations
If the same naming convention for the collection IDs and plans is used on
both subsystems (such as using the defaults from BMC Software, for
example), then the CHANGE MANAGER product’s catalog to catalog
Compare feature is ready to use.
• If you are not installing the same version and release level of CHANGE
MANAGER on the remote subsystem as you have installed on the local
subsystem, perform the following steps:
1. Install the compare components that are required for the catalog to
catalog Compare feature on the remote subsystem.
A. Edit the ACMC2CO member in the HLQ.CNTL data set.
B. Follow the instructions in the member. The member contains
data definition language (DDL) for execution at the remote
subsystem via DB2I SPUFI.
2. Bind the packages and the plan that are needed for the remote
subsystem.
A. Edit the ACMC2CB member in the HQL.CNTL data set.
B. Follow the instructions in the member.
C. Follow the instructions in ACMC2CG to grant execute on the
collection IDs.
Note: Collection IDs and the compare plan name must be identical
on both DB2 subsystems.
• If the remote subsystem has a version of DB2 that is different from the
version of DB2 that is installed on the local subsystem, use the following
steps as an example for implementing the catalog to catalog Compare
feature:
1. On the subsystem that has DB2 Version 4, install CHANGE
MANAGER version vrmC with DDF active. (The variable vrm
indicates the version, release, and maintenance level.) Use the
collection ID ACMvrmC_D_MAIN and the compare plan name
CMvrmCDC.
2. On the subsystem that has DB2 Version 5, install CHANGE
MANAGER version vrmD with DDF active. Use the collection ID
ACMvrmD_D_MAIN and the compare plan name CMvrmDDC.
