Using Tools Customizer in a multiple-LPAR environment

Edit online

Currently, Tools Customizer supports only the local LPAR; however, you can propagate customizations to additional LPARs by using either of two different methods.

About this task

In a multiple-LPAR environment, Tools Customizer identifies the LPAR to which you are logged on. Tools Customizer uses this LPAR name for several different parameter settings, one of which is the data store. When you use the data store during the customization of Db2® Automation Expert that is on a different LPAR, Tools Customizer issues message CCQD586S, which indicates that the product has already been customized based on values from the data store on the first LPAR. This message is issued to prevent the data store from becoming corrupted.

This behavior occurs in the following conditions:

  • Tools Customizer is installed on a DASD device that is shared by multiple LPARs.
  • After a product is customized by using Tools Customizer, the data store is copied to another LPAR.

Procedure

To customize products running against a Db2 subsystem on an LPAR where Tools Customizer is not installed, consider using one of the following methods:
Install one instance of Tools Customizer on one LPAR
If you intend to reuse the customization values for all the instances of your products on all LPARs, use this method.
  1. Associate all the Db2 entries in this one instance of Tools Customizer. The LPARs on which the Db2 subsystems reside do not matter.
  2. Generate the customization jobs for each Db2 entry.
  3. Copy the generated customization jobs to the LPAR to run against the specific Db2 entries. Some LPAR-specific edits might be required. You can make these edits in the customized jobs that you copied. Note that this situation is one of the few situations where you might need to make manual changes to the jobs that are customized by Tools Customizer.
Install one instance of Tools Customizer on each LPAR
If you do not want to reuse previous customization values and you want to start new customizations, use this method.
Important: This method will likely not be the preferred approach for most organizations because most organizations tend to use similar or identical customization values for each product instance on all LPARs.