Customizing after installation
Deploying products that use the infrastructure components requires careful planning.
This section explains how you can combine infrastructure components into different configurations across LPARs. Although each user's environment is unique, this section attempts to cover a variety of typical situations.
Requirements for each LPAR
Depending on the products that you installed, each LPAR contains the following:
- RTCS started task
- DBC started task
- (Optional) NGLARCH started task
(Depending on the products installed) BMC AMI Command Center (GUD), BMC Subsystem Optimizer for zEnterprise (BRD), LGC, NGL, Db2 Data Collector (DOM), and Logger (MVL) agents defined and running under the
DBC
subsystem
(For
Pool Advisor
only) DOMVARS, PMDHIST, and PMDCVAR data sets.
These data sets are allocated dynamically by the product when it starts. DOMVARS and PMDHIST data sets are unique to the DBC. The PMDCVAR data set is shared across the DBC group.
You can combine the infrastructure components into different configurations across LPARs, depending on whether you are sharing DBC groups and RTCS Subsystem SYSTEM registries.
Examples of deployed environments
A system with non-shared RTCS Subsystem SYSTEM Registry, shared LGC product-specific registry, and shared DBC group name
The following figure illustrates an environment in which different LPARs have different RTCS Subsystem SYSTEM registries but share the LGC product-specific registry and the DBC group name. In this example, both LPARs share:
- Runtime data sets
- LGC product specific registry
- DBC group
- Product option set
The DOM, BRD, and LGC agents and the DBC subsystem, communicate via a Cross-system Coupling Facility (XCF).
A system with shared RTCS Subsystem SYSTEM Registry, shared LGC product-specific registry, and shared DBC group
The following figure illustrates an environment in which different LPARs share:
- Runtime data sets
- RTCS Subsystem SYSTEM Registry
- LGC product-specific registry
- DBC group name
- Product option sets
This example is similar to the Example 1 but shows that the same setup can be achieved by sharing one of the RTCS Subsystem SYSTEM Registry.
A system with non-shared RTCS Subsystem SYSTEM Registry, non-shared LGC product-specific registry, and different DBC group names
The following figure illustrates an environment in which different LPARs have:
- Different runtime data sets
- Different RTCS Subsystem SYSTEM registries
- Different LGC product-specific registries
- Different DBC group names
- Different product option sets
The configuration in the following example enables you to keep your TEST and PROD environment separate. Therefore, none of the agents can communicate via an XCF.
Because the example uses a separate LGC product-specific registry on each LPAR, the names of the BRD, DOM, and GUD option sets might be the same on each LPAR but with a different instances.
Configuring your environment
The configuration that best suits your environment depends on:
- Whether you have RTCS configured. If yes, then whether the RTCS Subsystem SYSTEM Registry is configured as shared or a non-shared Registry.
- The number of DBC groups you want to have in a sysplex.
- Whether you want more than one DBC started tasks running on the same LPAR.