BMC Software, Inc., Confidential and Proprietary Information
1-16 Administrative Products for DB2 Installation Guide
Installation Paths
• allows an interface with other BMC Software products
• allows use of your own VSAM data sets (when supported by the selected
product and when you specify the Custom installation mode)
• allows data migration from a previous release (when you specify the
Custom installation mode)
If you plan to install products on several subsystems that have similar
characteristics, you can use the Multiple SSID installation path. For more
information see “Multiple SSID Installation” on page 1-17.
Considerations
Since the Install System saves the parameter values that you provide in the
first installation, the SSID installation path makes it easier and faster to
generate the installation batch jobs. You change only those parameters that
are different on each DB2 subsystem.
The Install System generates installation batch jobs for the specified
subsystem, but it does not unload data sets from the distribution tape. Instead,
the Install System uses the data sets that were unloaded during the Full
installation to install the software on the specified DB2 subsystem.
Consider the following requirements before you choose the SSID installation
path. For a subsequent installation on a different DB2 subsystem that does
not meet these requirements, use the Full installation path again.
• You can use the SSID installation path only after you complete a Full
installation of the selected product.
• The SSID installation path applies only to those products that can share
BMC Software product libraries.
• The DB2 subsystem that you choose during an SSID installation must
have the same version of DB2 as the Full installation of the selected
product.
• Edit your output JCL data set name in the User Options panel before you
perform a subsequent SSID installation.
Note: For ALTER and CHANGE MANAGER, the SSID installation must
be the same version of DB2 as the Full installation. Each of these
products must also have separate product libraries for each version of
DB2.
