IBM® Tools Customizer for z/OS® was introduced to provide a standard, repeatable process for customizing products in the DB2® for z/OS Tools portfolio. Before the introduction of Tools Customizer, each DB2 for z/OS tool followed a unique (non-standard) approach to customization, which required database administrators and systems administrators to learn and follow many different customization processes. Now, DB2 for z/OS tools that are enabled for Tools Customizer all follow a simple and standard customization process. Tools Customizer provides significant benefits, including:
- Simplified customization of multiple tools
- By employing a standard, ISPF panel-driven dialog that includes a robust help system, Tools Customizer simplifies the customization of any tool that is enabled for Tools Customizer.
- Improved up and running
- Tools Customizer's ability to automatically "discover" the customization parameters of previous releases drastically reduces the overhead that is required to manually enter parameter values. Customization templates are provided for each product, which significantly streamlines the customization process. And the list of customization jobs that are generated by Tools Customizer are displayed in a standard job execution sequence.
- Simplified upgrades
- Parameters from previous customizations are saved for future new product releases and DB2 upgrades, which simplifies the task of upgrading from one release to the next.
Currently, Tools Customizer supports only the local LPAR; however, you can propagate customizations to additional LPARs by using either of the two different methods that are described in this article.
How Tools Customizer currently behaves in a multiple-LPAR environment
In a multiple-LPAR environment, Tools Customizer identifies the LPAR that the user is logged on to. 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 a product 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.
The following scenario shows how this situation typically occurs:
- A user starts Tools Customizer on a LPAR and customizes a product.
- The user then sends a copy of the data store to another LPAR or the data store resides on shared DASD that is accessible from another LPAR.
- The user then starts Tools Customizer on a different LPAR to customize or recustomize a product, which causes Tools Customizer to detect a different LPAR than the one in the data store.
- Message CCQD586S is issued to users who subsequently use Tools Customizer on a different LPAR that is using the same data store. The CCQD586S message indicates that the LPAR was changed.
Methods for using Tools Customizer in a multiple-LPAR environment
To customize products running against a DB2 entry on an LPAR where Tools Customizer is not installed, consider using one of the following options:
- Install a single instance of Tools Customizer on a single LPAR
- The following method is appropriate if you intend to reuse the customization values for all the instances of your products on all LPARs.
- Associate all the DB2 entries in this one instance of Tools Customizer. DB2 entries are not checked within Tools Customizer, so the DB2 entries do not have to reside on this LPAR.
- Generate the customization jobs for each DB2 entry.
- Send a copy of 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 an instance of Tools Customizer on each LPAR
- This method is appropriate if you are not concerned with reusing the customization values that were generated and want to start new customizations from scratch.
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.
While only the local LPAR is currently supported by Tools Customizer, the methods described in this article will help you to customize products in your multiple-LPAR environment.
- Participate in the discussion forum.
- See the IBM Tools Customizer for z/OS documentation to learn more about how to customize products by using Tools Customizer.
- In the DB2 for z/OS area on developerWorks, get the resources you need to advance your DB2 skills.
- Get involved in the developerWorks community. Connect with other developerWorks users while exploring the developer-driven blogs, forums, groups, and wikis.