Customize the Xmanager

The Xmanager (the Execution Manager) establishes and provides an execution environment for the
CA Database Management Solutions for DB2 for z/OS
This section describes how to customize the Xmanager. Typically, this customization is performed by a systems programmer or database administrator. The Xmanager security settings are applied by a security administrator.
The Xmanager (Execution Manager) component establishes and provides a secure APF-authorized execution environment for the
CA Database Management Solutions for DB2 for z/OS
. The Xmanager also controls the activation of new product features with Level Set PTFs. Lastly, the Xmanager provides an execution environment for long-running asynchronous processes, like the real-time SQL statistics collection in
The Xmanager executes as a started task in its own address space. Often, a single Xmanager is used by all products and subsystems on a single LPAR. In other cases, an LPAR can have multiple Xmanagers. (For example, if you want to execute different maintenance Level Sets of the products on the same LPAR.) The products and non-Xmanager address spaces that connect to an Xmanager must be running a maintenance Level Set that meets or exceeds the highest active Level Set of that Xmanager.
In a sysplex environment, you can use the coupling facility to connect Xmanagers and provide a distributed communications environment across LPARs. The Xmanagers within the sysplex are organized into one or more groups. The Xmanagers within each group connect to each other. These connections provide access to any Db2 subsystem on any LPAR in the sysplex that is executing z/OS with an active Xmanager.
The Xmanagers in each group must be running a maintenance Level Set that is equal to or higher than the highest active Level Set for that group. Any Xmanager with a lower Level Set is not permitted to start up within the group.
Follow these steps:
  1. Determine the number of Xmanagers per LPAR.
  2. Define the coupling facility list structure.
  3. Allocate the coupling facility list structure.
  4. Create the Xmanager configuration file.
  5. Prepare the Xmanager started task procedure.
  6. Address the Xmanager and Level Set security requirements.
  7. Add the Xmanager ID to the SETUP member.
  8. Assign a dispatching priority or a WLM service class to the Xmanager.
  9. Point the products to the correct Xmanagers.
  10. (Optional) Isolate the CA Detector and
    Subsystem Analyzer
    collections to an Xmanager.
  11. Verify the Xmanager initialization.
The following topics provide detailed instructions for each step.
After you customize the Xmanager, it is ready for use. For information about starting and stopping the Xmanager, and for a list of Xmanager-related modify commands that you can use when Xmanager is running, see Manage the Xmanager Started Task.