V 5.1.1: Update to the Configuration and Customization manual of IBM Tivoli OMEGAMON for DB2 Performance Expert and Performance Monitor on z/OS

Manual


Abstract

This document describes updates to the IBM® Tivoli® OMEGAMON XE for DB2® Performance Expert and Performance Monitor on z/OS Configuration and Customization manual, GH12-6970-00, for Version 5.1.1.

Content

The updates are:

  • Update 1: Updates relating to stored procedure monitoring support in PM67565 (August 2011)
  • Update 2: Added the new subtask "START PARM=(COLD=value)" to Chapter 20, in section "Subtask Commands to the Event Collection Manager" for PM70266 (September 2012)
  • Update 3: Added 64-bit support for the Performance Expert Client in PM71185 (September 2012)
  • Update 4: Update relating to subtask commands to the Event Collection Manager in PK90683 (December 2013)
  • Update 5: Technote title changed in instructions for downloading the program files in PI13916 (March 2014)


Update 1: Updates relating to stored procedure monitoring support in PM67565 (August 2011)

Chapter 4. Prerequisites

The following table lists the DB2 privileges you must grant to the different users and the respective grant jobs that must be submitted.

Table 1. DB2 privileges.

Users
DB2 privileges/grant jobs
End users of Performance Expert Client (including Performance Warehouse Client) or ISPF Monitoring Dialogs OMGP<ssid>
Note: This job contains the following privileges:
    • EXECUTE on PLAN KO2PLAN
    • MONITOR1
    • MONITOR2
    • DISPLAY
    • TRACE
If you want to allow certain users to execute CANCEL THREAD in Thread Activity, then you have to grant those privileges additionally (for example SYSOPR).
End users of DB2 z/OS subsystem/data sharing group in the InfoSphere Optim Performance Manager Web Console To configure InfoSphere Optim Performance Manager:
  • Privileges described in row ‘End users of Performance Expert Client (including Performance Warehouse Client) or ISPF Monitoring Dialogs’.
  • The privilege to connect to the DB2 z/OS subsystem/data sharing group.
  • The necessary privileges to perform CREATE/DROP/ALTER on function or procedure, that is GRANT CREATEIN,DROPIN,ALTERIN ON SCHEMA OPM. The system privilege GRANT BINDADD is also required, as well as the privileges to issue GRANT EXECUTE on all functions and stored procedures on schema OPM.
  • JDBC stored procedures that allow getMetaData() method call have to be installed and configured.
To view static SQL statement text:
  • The SELECT privilege on tables SYSIBM.SYSCOLUMNS, SYSIBM.SYSPACKSTMT, SYSIBM.SYSROUTINES, and SYSIBM.SYSPARMS.

Chapter 20, Operator commands

Subtask commands to Performance Expert Server

You can issue specific subtask commands to the Performance Expert Server subtask (PESERVER). The subtask commands must be preceded by the MODIFY command.


DB2MSGMON=parameter
Starts or stops the DB2 messages collector. This collector shows or hides DB2 messages in the Tivoli Enterprise Portal workspaces. parameter can be one of these values:
Y
Starts the DB2 messages collector, which shows DB2 messages in the Tivoli Enterprise Portal workspaces. The DB2 messages collector is a function of the READA collector support task. If the READA collector support task has not been started, enabling the DB2 messages collector will start the READA collector support task.
N
Stops the DB2 messages collector, which hides DB2 messages in the Tivoli Enterprise Portal workspaces. If the DB2 messages collector is the only function enabled for the READA collector support task, disabling the DB2 messages collector will stop the READA collector support task.


SPMON=parameter
Starts or stops the stored procedure collector. This collector shows or hides stored procedure monitoring data in the IBM InfoSphere® Optim™ Performance Manager dashboards.

parameter can be one of these values:

Y
Starts the stored procedure collector, which shows stored procedure monitoring data in the IBM InfoSphere Optim Performance Manager dashboards. The stored procedure collector is a function of the READA collector support task. If the READA collector support task has not been started, enabling the stored procedure collector will start the READA collector support task.
N
Stops the stored procedure collector, which hides stored procedure monitoring data in the IBM InfoSphere Optim Performance Manager dashboards. If the stored procedure collector is the only function enabled for the READA collector support task, disabling the stored procedure collector will stop the READA collector support task.


RACOPS=parameter
RACOPSIZE=parameter
Changes the size of the OP buffer used by the READA collector support task to retrieve READA data from the monitored DB2 subsystem or data sharing group, where:

  • parameter is an integer between 16 and 64 (representing an OP buffer size in MB)
Note: Changing the OP buffer size will stop and restart the DB2 trace that is currently active for the OP buffer.


RACOPT= parameter
RACOPTHRSHLD= parameter
Changes the threshold of the OP buffer used by the READA collector support task to retrieve READA data from the monitored DB2 subsystem or data sharing group, where:
  • parameter is an integer between 6 and 75 (representing a percentage value)

The OP buffer threshold defines the fill level of the OP buffer that should trigger processing of OP buffer data by the READA collector support task. For example, specifying a OP buffer threshold of 15% causes the READA collector support task to retrieve data from the OP buffer as soon as the OP buffer space is used up to 15%.

Note: Changing the OP buffer size will stop and restart the DB2 trace that is currently active for the OP buffer.


Chapter 11. Configuring basic components on z/OS

Enabling Performance Expert Client support and/or end-to-end SQL and stored procedure monitoring support

If you want to use Performance Expert Client and/or end-to-end SQL and stored procedure monitoring, you must enable Performance Expert Client support and/or end-to-end SQL and stored procedure monitoring support.

About this task
Performance Expert Client is a user interface that supports online monitoring and reporting, Performance Warehouse management, and buffer pool analysis on the workstation. End-to-end SQL monitoring and stored procedure support is a feature that brings new functionality in end-to-end monitoring via the InfoSphere® Optim™ web user interface. With this new functionality, distributed SQL statement execution can be monitored, as well as stored procedures called via DDF, or directly on the Host. You must enable Performance Expert Client support and/or end-to-end SQL and stored procedure monitoring support before you can specify the port information for Performance Expert Client and/or end-to-end SQL and stored procedure monitoring support.

To enable Performance Expert Client support and/or end-to-end SQL and stored procedure monitoring support, complete the following steps:

Procedure

  1. Start the Configuration Tool and navigate to the OMEGAMON XE for DB2 PE on z/OS Main Menu.
  2. Select option Basic product setup (incl. User interfaces) and then press Enter. The Basic Product Setup Menu panel is displayed.
  3. Select option PE Client and end-to-end SQL monitoring and then press Enter. The PE Client support and end-to-end SQL monitoring panel opens.
  4. Type a Y next to Enable Performance Expert Client support and/or Enable end-to-end SQL monitoring and enter your configuration values. Note: To enable end-to-end SQL and stored procedure monitoring support, you must set Enable Performance Expert Client support to Y. For end-to-end SQL and stored procedure monitoring support, set the maximum number of session to at least 12 (the default is 99).
  5. Press Enter until the Basic Product Setup Menu panel is displayed again.

What to do next
After you have enabled Performance Expert Client support and/or end-to-end SQL and stored procedure monitoring support, you must perform the following tasks:

Chapter 12. Configuring monitoring profiles and DB2 subsystems

Specifying the port information for Performance Expert Client and/or end-to-end SQL and stored procedure monitoring

If you want to use Performance Expert Client and/or end-to-end SQL and stored procedure monitoring for some DB2® subsystems, you must specify the Performance Expert Client port information for each DB2 subsystem.

Before you begin
You must enable Performance Expert Client support and/or end-to-end SQL and stored procedure monitoring support before you specify the port information. See Enabling Performance Expert Client support and/or end-to-end SQL and stored procedure monitoring support for more information.

About this task
To specify the port information, perform the following steps:

Procedure

  1. Start the Configuration Tool and navigate to the OMEGAMON XE for DB2 PE on z/OS Main Menu.
  2. Select option Configure DB2 subsystem monitoring and then press Enter. The DB2 subsystem monitoring menu panel is displayed.
  3. Select option Specify port information and then press Enter. The Port information panel is displayed.
  4. Enter the port information for the DB2 subsystems and press Enter.
  5. Press F3 until the OMEGAMON XE for DB2 PE on z/OS Main Menu is displayed again.

What to do next
  1. You must create the runtime members for this DB2 subsystem. See Configuring DB2 subsystem monitoring for detailed instructions.
  2. For Performance Expert Client: After you have added Performance Expert Client support, you must install Performance Expert Client on the workstation. See Installing and configuring Performance Expert Client for more information. For end-to-end SQL and stored procedure monitoring: After you have added end-to-end SQL and stored procedure monitoring support, you must install end-to-end SQL and stored procedure monitoring on the workstation. See Installing and configuring end-to-end SQL and stored procedure monitoring for more information.


Configuring Additional DB2 Traces

You can use the Configuration Tool to configure Additional DB2® Traces.

About this task
To configure Additional DB2 Traces, perform the following steps:

Procedure

  1. Start the Configuration Tool and navigate to the OMEGAMON XE for DB2 PE on z/OS Main Menu.
  2. Select option Configure monitoring profiles and then press Enter. The Configure profiles Menu panel is displayed.
  3. Select option Specify monitoring profile values and then press Enter. The Monitoring profile configuration panel opens.
  4. Type an S next to the profile or profiles that you want to support this component and then press Enter. To add a new profile, specify the new profile ID on the first blank line. The Profile configuration panel opens.
  5. Select option Start Additional DB2 Traces and then press Enter.
  6. Enter your configuration values and press Enter. Note: For end-to-end SQL and stored procedure monitoring support, IFCIDs 318 and 400 are mandatory in order to collect statement cache metrics (IFCID 400 is only applicable for DB2 10 and higher).
  7. Press F3 until you reach the Configure profiles Menu panel again.

C onfiguring Additional Monitoring Features

If you want to enable additional monitoring functions, such as DB2® message monitoring and stored procedure monitoring, you must enable them in the Configuration Tool. DB2 message monitoring is used to show DB2 messages in the Tivoli Enterprise Portal workspaces. Stored procedure monitoring data is used in the InfoSphere Optim Performance Manager dashboards.

About this task
To configure Additional Monitoring Features, perform the following steps:

Procedure
  1. Start the Configuration Tool and navigate to the OMEGAMON XE for DB2 PE on z/OS Main Menu.
  2. Select option Configure monitoring profiles and then press Enter. The Configure profiles Menu panel is displayed.
  3. Select option Specify monitoring profile values and then press Enter. The Monitoring profile configuration panel opens.
  4. Type an S next to the profile or profiles that you want to support this component and then press Enter. To add a new profile, specify the new profile ID on the first blank line. The Profile configuration panel opens.
  5. Select option Start Additional Monitoring Features and then press Enter.
  6. Enter your configuration values and press Enter.
  7. Press F3 until you reach the Configure profiles Menu panel again.


Chapter 15. Installing and configuring components on the workstation


Installing and configuring end-to-end SQL and stored procedure monitoring

In this step, you install and configure end-to-end SQL and stored procedure monitoring on the workstation.

Before you begin

  1. You must add end-to-end SQL and stored procedure monitoring support before installing and configuring end-to-end SQL and stored procedure monitoring. See Enabling Performance Expert Client support and/or end-to-end SQL and stored procedure monitoring support for more information.
  2. You must add port information for end-to-end SQL and stored procedure monitoring before installing and configuring end-to-end SQL and stored procedure monitoring. See Specifying the port information for Performance Expert Client and/or end-to-end SQL and stored procedure monitoring for more information.
  3. You must add additional DB2 traces before installing and configuring end-to-end SQL and stored procedure monitoring. See Starting Additional DB2 Traces for more information.
  4. In order to use stored procedure monitoring, you must enable it separately. See Configuring Additional Monitoring Features for more information.

About this task
Installation and configuration of the InfoSphere® Optim™ Performance Manager including the end-to-end SQL and stored procedure monitoring feature is documented in the InfoSphere Optim Performance Manager Installation Guide, Version 5.1.1 (or higher). For more information on configuring the stored procedure monitoring feature, refer to the InfoSphere Optim Performance Manager Installation Guide, Version 5.1.1.1. For detailed instructions, see the IBM InfoSphere Optim Performance Manager information center.


Update 2: Added the new subtask "START PARM=(COLD=value)" to Chapter 20, in section "Subtask Commands to the Event Collection Manager" for PM70266 (September 2012)

START PARM= (COLD=value)

Specifies if the Event Collection Manager configuration should be restarted. This option should only be used if a DB2 subsystem has been dynamically added to the z/OS LPAR since the Event Collection Manager was started, or under guidance from Level 2 support.

You can specify YES or NO. The default value is NO.

You can use this parameter with the START command for the Event Collection Manager.

F cccccccc,START EVENTMGR,PARM=(COLD=YES)
where:

  • cccccccc is the started task name that you specify for the OMEGAMON Collector during the configuration within the Configuration Tool


Update 3: Added 64-bit support for the Performance Expert Client in PM71185 (September 2012)

Hardware requirements for Performance Expert Client

Performance Expert Client requires the following hardware prerequisites. Review these requirements to ensure that your environment is prepared for installation.

The minimum hardware requirements to install and run Performance Expert Client are:

  • A personal computer with Intel-based processor architecture, 400 MHz Pentium
  • 512 MB RAM
  • 400 MB (Windows 32-bit and 64-bit) disk space in the installation directory for the installation files
  • 350 MB temporary space for running the installation program
  • A high-resolution display unit of 1024 x 768 or higher
  • If you install OMEGAMON XE for DB2 PE, which includes buffer pool object placement, the following free memory for object placement:
  • 60 MB for up to 1000 objects
  • 220 MB for up to 100 000 objects
  • 500 MB for up to 200 000 objects
where objects are table spaces and index spaces.

Recommendation: If you have installed only the minimum requirements, you should not run other applications at the same time.


Installing Performance Expert Client silently by using a response file

A silent installation is an installation that runs without displaying an interface or prompting you for input. You can do silent installations of Performance Expert Client to simplify the process of installing it on multiple computers.

Before you begin
Before you install Performance Expert Client silently, you must first create a response file. A response file is a file that contains the properties and values that drive the installation. You create a response file by running the installation wizard or console mode with the following command-line option: -r response_file_name. When you complete the installation, the information that you entered in the installation wizard or console mode is recorded in the response file. You will use this file to install the product silently on other computers.

Procedure
To install Performance Expert Client silently by using a response file:

  1. From the directory of the installation image for Performance Expert Client, run the following command:
    On Windows 32-bit:
    db2pe.client.*.install-on-win32.exe -i -silent -f response_file_name
    where response_file_name is the name of the response file that you created during a previous installation of the product.
    On Windows 64-bit:
    db2pe.client.*.install-on-win64.exe -i -silent -f response_file_name
    where response_file_name is the name of the response file that you created during a previous installation of the product.
    Note: Run as Administrator.
    The product is installed.
  2. Verify that the installation was successful by checking the db2pecli.log installation log file in the following directory:
    - On Windows: %USERPROFILE% (For example: C:\Documents and Settings\Administrator)
  3. Start Performance Expert Client by running the db2pe script, which is located in the Performance Expert Client installation directory.
  4. On Windows, you can also start the Performance Expert Client from the Windows Start menu.

Update 4: Update relating to subtask commands to the Event Collection Manager in PK90683 (December 2013)

Subtask commands to the Event Collection Manager

You can issue specific subtask commands to the Event Collection Manager subtask (EVENTMGR). The subtask commands must be preceded by the MODIFY command of the OMEGAMON Collector.

Specific subtask commands are:

START DB2=value

Starts the object and volume analysis collectors for one or more DB2® subsystems. The DB2 subsystems are specified by subsystem IDs.

Requirement: If you specify more than one DB2 ID, you must enclose the string in parentheses.

You can use this parameter with the START and MODIFY commands for the Event Collection Manager. Use the MODIFY command if the Event Collection Manager is already started.

F cccccccc,START EVENTMGR
F cccccccc,F EVENTMGR,START DB2=(db2ssid1,db2ssid2,...db2ssidn)
where:

  • cccccccc is the started task name that you specify for the OMEGAMON Collector during the configuration within the Configuration Tool
  • db2ssid is the identifier of the DB2 subsystem for which object and volume analysis collectors should be started



Update 5: Technote title changed in instructions for downloading the program files in PI13916 (March 2014)

In chapter 17, there are three sections explaining how to download the program files of Performance Expert Agent (Windows, UNIX and Linux) and Performance Expert Client. The download instructions are contained in a technote and the title of this technote changed from "OMPE: web-based delivery and updates for Windows- and UNIX-based components" to "OMEGAMON XE for DB2 PE/PM: web-based delivery and updates for Windows- and UNIX-based components."

Publication number

GH12-6970-00

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 Tools for z/OS
IBM Tivoli OMEGAMON XE for DB2 PE / PM / BPA

Software version:

5.1.1

Operating system(s):

z/OS

Reference #:

7035964

Modified date:

2014-03-25

Translate my page

Machine Translation

Content navigation