Using Tools Customizer in a multiple-LPAR environment

Tools Customizer (TCz) supports customizations on only the local LPAR. However, you can propagate customizations to additional LPARs.

About this task

In a multiple-LPAR environment, TCz identifies the LPAR to which you are logged on and uses this LPAR name for several parameter settings, including the data store. Therefore, you can use the TCz data store to customize only that LPAR.

Procedure

To customize products that run against Db2® subsystems on multiple LPARs, use one of the following methods:
  • Method 1: Customize a single Db2 subsystem or data sharing group and copy the customization jobs to each LPAR
    1. Customize one Db2 subsystem or member.
      For example, you might customize member DB1S in group DBGS in your sandbox environment.
    2. If you are using data sharing, propagate that customization to the other members in the group:
      1. Copy the customization jobs to the other members.

        For example, copy the jobs for DB1S to member DB2S.

      2. Edit the jobs as needed for the subsystem and LPAR.

        For example, replace the member names. Depending on your environment, you might also need to replace data set names. You can use a REXX exec to do this customization.

      3. Run those jobs.

        Some jobs do not need to be run on every member in a group. Some jobs only need to run once per LPAR or Sysplex. To determine where a job needs to be run, look at the job listings on the Finish Product Customization (CCQPCST) panel. Depending on the values of the SSID and GrpAttch columns, take the following actions for each job:

        Table 1. Actions to take based on information on the Finish Product Customization (CCQPCST) panel
        SSID column value GrpAttch column value Action Comments
        -- -- Run once per LPAR None
        -- A group name Run once per group None
        A member name A group name Run once per member in the group None
        An SSID -- Run once This entry is for a stand-alone Db2 subsystem.
    3. Copy the jobs from the initial customized subsystem or member to all your other subsystems or groups. Then, edit those jobs, preferably with a REXX exec, and run them.
      For example, copy the jobs for DB1S in group DBGS to the members DB1D and DB2D in your development group DBGD, edit those jobs as needed, and run them. Then, copy the jobs for DB1S to the members DB1T and DB2T in your test group DBGT, edit those jobs, and run them. Continue until all groups are customized.
  • Method 2: Generate customization jobs for each Db2 subsystem and copy those jobs to the appropriate LPARs
    1. Associate all Db2 entries in one instance of TCz on one LPAR, regardless of the LPARs on which the Db2 subsystem resides.
    2. Generate customization jobs for each Db2 entry.
    3. Copy the generated customization jobs to the LPAR to run against the specific Db2 entries. You might need to edit these customization jobs for specific LPARs. For example, you might need to edit the data set names. (Otherwise, you generally do not need to make manual changes to the jobs that are customized by TCz.)