V5.1.0: 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 updates the IBM® Tivoli® OMEGAMON XE for DB2® Performance Expert and Performance Monitor on z/OS Configuration and Customization manual, GH12-6928-00, for Version 5.1.0.

Content

This manual includes the following updates:

  • Update 1: Changed column definitions of ACCOUNTING FILE BUFFER, GENERAL, and PROGRAM tables for MR0927106232 (March 2011)
  • Update 2: Setting a threshold for the elapsed processing time in the PESERVER subtask for PM27781 (April 2011)
  • Update 3: Changed the title of the technote in the "Downloading the program files" sections for PM51661 (November 2011)
  • Update 4: Setting a threshold for the display of timeout notification message FPEV2102W in the PESERVER subtask for PM52466 (December 2011)
  • Update 5: Updated the "Upgrading the Performance Database" section for PM53549 (February 2012)
  • Update 6: 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 7: Added 64-bit support for the Performance Expert Client in PM71185 (September 2012)
  • Update 8: Update relating to subtask commands to the Event Collection Manager in PK90683 (December 2013)
  • Update 9: Technote title changed in instructions for downloading the program files in PI13916 (March 2014)




    Update 1: Changed column definitions of ACCOUNTING FILE BUFFER, GENERAL, and PROGRAM tables for MR0927106232 (March 2011)

    The section "Upgrading the Performance Database" has been updated as follows:

    If you created a Performance Database for the earlier version, you must manually upgrade it for version 5.1.0. No tool is available to perform this function.

    If you created a Performance Database for the earlier version and want to use the data stored in Accounting and Statistics tables in the new version, you must manually upgrade it for version 5.1.0. Perform the following steps:
    •For the Accounting FILE BUFFER, DDF, GENERAL, and PROGRAM tables, for all Accounting SAVE tables, and for the Statistics GENERAL table you have to unload the data from existing tables and load this data into tables created with the new version.
    •For other tables you have to run ALTER statements provided with the new version.


    Update 2: Setting a threshold for the elapsed processing time in the PESERVER subtask for PM27781 (April 2011)

    A new subcommand for the Performance Expert Server subtask is introduced for serviceability purposes and should be used after consultation with IBM support.

    MODIFY command

    Issues a subcommand to the PESERVER subtask.

    F cccccccc,F PESERVER,F db2ssid,option
    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 on which the PESERVER subtask runs.
    Tip: Enter ALL for all of the DB2 subsystems on which the PESERVER subtask runs.
    • option is the subcommand for the PESERVER subtask

    Subcommands for the PESERVER subtask are:

    EPTT= parameter
    Specifies the threshold value for the elapsed processing time in seconds, where:
    • parameter is an integer from 0 to 240

    If EPTT is set to a value greater than 0, the elapsed processing time and threshold are being compared. If the elapsed processing time exceeds the threshold, message FPEV2100W is issued.

    If EPTT is set to 0, the threshold is cleared and the comparison is disabled.

    The MODIFY command can be used to diagnose timeout conditions that are reported during the operation of the monitoring PESERVER subtask. For example, message FPEV2102W reports timeout conditions when data retrieval requests issued by the Classic interface are not completed by the PESERVER subtask within 10 seconds. The MODIFY command sets an internal threshold for the elapsed processing time (EPTT) in the DB2 interface task of the PESERVER subtask. If a call to the DB2 IFI interface does not complete within the specified time:

    • Message FPEV2103I is issued (optional).
    • Message FPEV2100I is issued.
    The control block containing measured elapsed times is dumped to the server log in hexadecimal format for use by IBM support. An SVC dump for the DB2 address spaces of the monitored DB2 subsystem is initiated. The dump will only be taken for the first occurrence of a timeout after EPTT is set. In this case message FPEV2101I is issued to inform the user that a dump was initiated. The dump title is ‘FPEVDB2I - DB2 ADDRESS SPACES FOR db2ssid', where db2ssid is the identifier for the DB2 subsystem. No further dump can be initiated until the PESERVER subtask is recycled.


    Update 3: Changed the title of the technote in the "Downloading the program files" sections for PM51661 (November 2011)

    The title of the technote in the following three "Downloading the program files" sections has changed:

    Downloading the program files of Performance Expert Agent for
    DB2 Connect Monitoring on Windows
    ®
    About this task

    Both, the initial version and later fixes for the program files for Performance Expert Agent for
    DB2 Connect Monitoring are available online. For download instructions, refer to the technote "OMPE: web-based delivery and updates for Windows- and Unix-based components" on the IBM® Software Support website at http://www-01.ibm.com/support/docview.wss?rs=434&uid=swg21371683. If needed, the direct link to the technote is also included in the hold instructions of every Performance Expert Agent PTF on the host. The available program build levels and fix descriptions are documented in the technote.

    Downloading the program files of Performance Expert Agent for
    DB2 Connect Monitoring on UNIX® and Linux
    ®
    About this task

    Both, the initial version and later fixes for the program files for Performance Expert Agent for
    DB2 Connect Monitoring are available online. For download instructions, refer to the technote "OMPE: web-based delivery and updates for Windows- and Unix-based components" on the IBM® Software Support website at http://www-01.ibm.com/support/docview.wss?rs=434&uid=swg21371683. If needed, the direct link to the technote is also included in the hold instructions of every Performance Expert Agent PTF on the host. The available program build levels and fix descriptions are documented in the technote.

    Downloading the program files of Performance Expert Client
    About this task

    Both the initial version and later fixes for the program files for Performance Expert Agent for
    DB2 Connect Monitoring are available online. For download instructions, refer to the technote "OMPE: web-based delivery and updates for Windows- and Unix-based components" on the IBM® Software Support website at http://www-01.ibm.com/support/docview.wss?rs=434&uid=swg21371683. If needed, the direct link to the technote is also included in the hold instructions of every Performance Expert Agent PTF on the host. The available program build levels and fix descriptions are documented in the technote.


    Update 4: Setting up a threshold for the display of timeout notification message FPEV2102W in the PESERVER subtask for PM52466 (December 2011)

    A new subcommand for the Performance Expert Server subtask is introduced to be able
    to control the display of warning message FPEV2102W.

    F cccccccc,F PESERVER,F db2ssid, TONT = parameter
    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 you want to set the
    timeout notify threshold. Specify db2ssidas ALL to set the timeout notify threshold for
    all currently monitored DB2 subsystems

    TONT= parameter
    Specifies the value for the timeout notify threshold in seconds, where:
    • parameter is an integer from 0 to 240

    If TONT is set to a value greater than 0, the time exceeding the internal timeout value and the timeout notify threshold are compared. If the internal timeout value for the elapsed processing time is exceeded by more time than specified in the timeout notify threshold, message FPEV2102W is issued. Otherwise message FPEV2102W is suppressed.

    If TONT is set to 0, the threshold is cleared, the comparison is disabled and message FPEV2102W will be issued for each data retrieval request exceeding the internal timeout value.

    The MODIFY command sets the timeout notify threshold (TONT) in the DB2 interface task of the PESERVER subtask. If a call to the DB2 IFI interface does not complete within the time, which is calculated as internal timeout value plus specified notify threshold time, message FPEV2102W is issued. The current setting for the timeout notify threshold is displayed as part of the response to the DISPLAY MODIFY command (F cccccccc,F PESERVER,F db2ssid,DISPLAY).

    The MODIFY command can be used to suppress the reporting of timeout conditions that are detected during the operation of the monitoring PESERVER subtask. You can suppress message FPEV2102W for systems running at their capacity limit where timeout conditions are expected but extraordinary situations will be reported. For example, message FPEV2102W reports timeout conditions when data retrieval requests issued by the classic interface are not completed by the PESERVER subtask within 10 seconds. If message FPEV2102W displays values up to 8 seconds in phases where limited responsiveness is expected, the timeout notify threshold can be set to 9 seconds to suppress expected messages and to still get alerted in case responsiveness decreases.


    Update 5: Updated the "Upgrading the Performance Database" section for PM53549 (February 2012)

    For tables that require ALTER statements, do the following:

    1. Find the ALTER statements in the DGO*UPDB members of the sample library RKO2SAMP (RTE) where * is A for Accounting, S for Statistics, W for System Parameters, and X for Audit.
    2. Identify the current version of your tables by checking the CREATE parts and the ALTER statements in the DGO*UPDB members that introduced new columns.
    3. Run the ALTER statements that are needed to add the missing columns.
    4. To populate the altered tables with new data, do the following:
    • Use the LOAD parts of the new version and change them as necessary.
    • If you work with Accounting and Statistics SAVE tables, use the SAVE file conversion utility that is shipped with the new version.


    Update 6: 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 7: 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 8: Update rel ating 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 9: 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-6928-00

Original publication date

2010/10/22

Rate this page:

(0 users)Average rating

Document information


More support for:

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

Software version:

5.1.0

Operating system(s):

z/OS

Reference #:

7020076

Modified date:

2014-03-25

Translate my page

Machine Translation

Content navigation