Enabling the Product CLISTs
BMC Software, Inc., Confidential and Proprietary Information
Chapter 4 Performing Post-Installation Tasks 4-9
Member BMCDB2CI is generated to support catalog indirection. This
member contains logic for the DOPTs module allocation for indirect access.
When you use BMCDB2CI to update the BMCDB2 CLIST, consider the
following:
• If you have MVS/ESA and TSO/E 2.1 or later, the Install System
automatically updates the BMCDB2 CLIST with BMCDB2CI. The
Install System searches both the JCL output file and the installation file
to apply the updates wherever a copy of BMCDB2 is found. The Install
System prompts you for the location of the BMCDB2 CLIST.
• If you do not have MVS/ESA and TSO/E 2.1 or later, follow the
directions in BMCDB2CI for updating the BMCDB2 CLIST. If you
install CATALOG MANAGER, follow the instructions for modification
of the CATALOG MANAGER plan name.
Because the BMCDB2 CLIST uses the ISPF LIBDEF facility to allocate all
necessary ISPF data sets, you may not need to modify your TSO logon
procedure.
Step 3 Enable BMCDB2 CLIST to use different libraries for an SSID.
If your installation has more than one version of DB2, the Administrative
Products must have separate libraries for each version. Use the following
scenarios as examples for editing the BMCDB2 CLIST.
• In this scenario, CHANGE MANAGER is installed on SSID DB31. The
product libraries have a high-level qualifier of BMC.DB31.*. During the
installation, JCL and the BMCDB2 CLIST are generated into
BMC.DB31.JCL. The table in Figure 4-9 is added to the bottom of the
BMCDB2 CLIST.
Figure 4-9 Adding CHANGE MANAGER to Subsystem DB31
*DATA
*PROD SSID D/I DOPT PLAN APPL COLL_ID NICKNAME
*----|----|-|--------|--------|----|------------------|-----------------
ACM DB31 D ACMDOPD1 CM
vrm
BDF ACMA *
*LIB SSID Data Set Name
*----|----|-------------------------------|
EXIT DB31 'SYS3.DBAP.DSNEXIT' *
LOAD DB31 'SYS2.DB2V31M.DSNLOAD' *
