Default language.

Use multiple options modules


Except for BMCSORT, you can create additional options modules for the BMC products for Db2. These additional modules allow you to use different option values for different executions of the product. For example, you might use the default installation options module for most jobs but create another options module with customized values to accommodate special situations.

You can specify separate prdDOPD1 modules for each SSID by using a unique name for each module. To create a unique name for each module, you must change the name in the prd$OPTS member of your installation library. For a list of the default prd$OPTS member names, see Installation-options-jobs-and-modules. The Installation System prompts you for the names. You can assign names that identify the SSIDs on which you are installing the product.

To use a particular options module, you can specify the name of the options module in the EXEC statement of your batch job. For more information, see the documentation for a specific product.

You do not need to specify different plan names or object names for subsequent products or SSID systems. When you start the product through the Installation System’s ISPF interface, the unique name of the installation options module for each SSID is passed to the product. Unlike the other installation options parameters, the plan names are used directly by the product. If you must specify different plan-name values for each Db2 subsystem, you need multiple installation options modules.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

Installation System