Setting up autonomic management for Db2 for z/OS subsystems

By installing and configuring certain Db2® for z/OS® Tools products, you can automatically detect potential problems and proactively run maintenance utilities for Db2 for z/OS subsystems.

About this task

To enable the complete autonomics capabilities, you install and configure Autonomics Director for Db2 for z/OS, DB2® Automation Tool for z/OS, and Utilities Enhancement Tool for z/OS.

Db2 Automation Tool for z/OS and Autonomics Director for Db2 for z/OS provide the following capabilities for setting up self-management of Db2 for z/OS:

  • Viewing and editing Automation Tool profiles on the Subsystem Autonomics page.
  • Creating real-time statistics (RTS) snapshot job profiles to run RTS snapshots for Automation Tool object profiles.
  • Creating maintenance windows and specifying time intervals.
  • Adding schedules, if Db2 for z/OS administrative task scheduler is set up and running. For details, see Scheduling administrative tasks.
  • Building the autonomic job profile to run evaluations of the objects in the object profile against the exceptions (conditions) in the exception profile.
  • Viewing RTS history data, captured by the snapshot job profiles, on the RTS history charts of the Subsystem Dashboard.
  • Capturing data to populate the dashlets on the Subsystem Dashboard.

Utilities Enhancement Tool for z/OS captures the history of the utilities that have run for all the resources and presents the results in the Utility History widget on the Subsystem Dashboard

Procedure

To set up autonomic management of Db2 for z/OS subsystems, complete the following steps:

  1. Install and customize Autonomics Director for Db2 for z/OS Version 1.6 or higher.
  2. Install and customize Db2 Automation Tool for z/OS Version 4.3 or higher.
    For detailed instructions, see Customizing Db2 Automation Tool for z/OS.
  3. Install and customize Utilities Enhancement Tool for z/OS Version 2.2 or higher.
    The following customizations are required to enable the Data Server Manager autonomic capabilities:

    For detailed instructions, see Preparing to customize Utilities Enhancement Tool for z/OS.

  4. Add a connection to the Db2 for z/OS subsystem.
    For detailed instructions, see Adding database connections.
    After you select Db2 for z/OS as the Data server type, a Tools tab appears.
  5. On the Tools tab, specify the following values:
    Schema
    Specify the schema of the Db2 Automation Tool repository. You can find the value can be found on either the Tools Customizer Product Parameters panel (CCQPPRD) or the Associated Db2 Entries and Parameter Status panel (CCQPDB2)
    Control file
    Specify the name of the Db2 Tools control data set that contains the Db2 Automation Tool configuration parameters. This value can be found on the Tools Customizer Product Parameters panel (CCQPPRD), in the Control file field.
    Subsystem ID
    Specify the 4-character subsystem identifier that Db2 Automation Tool uses. You can find this value on the Customizer Workplace: Db2 Automation Tool panel (CCQPWRK)
    Configuration ID
    Specify the current configuration ID from the CLIST that starts Db2 Automation Tool . It specifies the storage location for Db2 Automation Tool customizations. The default value is ‘HAA’. You can find the value can be found on the Tools Customizer Product Parameters panel (CCQPPRD), in the Configuration ID field.
    Db2 Autonomics Director server host or IP address
    Specify the host name or IP address where the Autonomics Director for Db2 for z/OS server is installed, configured, and running.
    Db2 Autonomics Director HTTP listener port number
    Specify the configured port that the Autonomics Director for Db2 for z/OS server is listening on for incoming HTTP(S) requests. This value should match what is specified in the server configuration file (default file DYXCFGS), under the <web> section.
    Port is configured for TLS or SSL connections
    Specify whether the HTTP listener port is configured to handle secure and encrypted connections as defined by the TLS or SSL protocol. This setting should match what is specified by the <ssl-is-secured> parameter setting in the server configuration file (default file DYXCFGS).