Update to the Configuration and Customization manual of IBM Tivoli OMEGAMON for DB2 Performance Expert and Performance Monitor on z/OS (v 4.2.0)

Product documentation


Abstract

This document updates the IBM® Tivoli® OMEGAMON XE for DB2® Performance Expert and Performance Monitor on z/OS Configuration and Customization manual, GC19-2511-00, for Version 4.2.0.

Content

This manual includes the following updates:


  • Update 1: Upgrading the runtime environment in the Configuration Tool (June 2009)
  • Update 2: Upgrading the runtime environment in the Configuration Tool (June 2009)
  • Update 3: Exploiting monitoring profiles (June 2009)
  • Update 4: Upgrading the Tivoli Enterprise Monitoring Agent (June 2009)
  • Update 5: Overview for resubmitting configuration jobs (June 2009)
  • Update 6: Subtask commands to the Near-Term History Data Collector (August 2009)
  • Update 7: Subtask commands to the Event Collection Manager (August 2009)
  • Update 8: Updating Authorizations on data sets for the OMEGAMON Collector started task
    (December 2009)
  • Update 9: Starting Additional DB2 Traces (March 2010)
  • Update 10: Setting a threshold for the elapsed processing time in the PE Server subtask - PM21372 (November 2010)
  • Update 11: Subtask commands to the Near-Term History Data Collector (January 2011)


  • Update 1: Upgrading the runtime environment in the Configuration Tool (June 2009)
    Under step 4, an additional step has been added as a final step.

    s. Copy the OMEGAMON Collector started task that is generated to your &rhilev.&rte.RKD2SAM library to your system PROCLIB, or update your OMEGAMON Collector started task JCL manually as follows:
    Replace

    //O2CI EXEC PGM=KOBCIRT0,REGION=0M,DPRTY=(15,15),TIME=1440

    with


    //O2CI EXEC PGM=KO2ZTOPB,REGION=0M,
    // PARM='/SUB=OMPE',DPRTY=(15,15),TIME=1440

    Note: You can perform migration also by means of batch mode install.

  • Update 2: Upgrading the runtime environment in the Configuration Tool (June 2009)
    Under step 4, two substeps (p and q) have been moved up to follow step n.

    4. Upgrade the runtime environment.
      a. Type a b in the Action field. A batch job is generated. It checks for all of the required libraries in
      the existing runtime environment and creates any that are missing.
      b. Submit the job.
      c. Stop all version 3.1.0 started tasks.
      d. Type an l in the Action field. A batch job is generated. It loads the runtime libraries for the runtime
      environment from the SMP/E target libraries.
      e. Submit the job.
      f. Type a c in the Action field and then select option OMEGAMON XE for DB2 Performance Expert
      on z/OS. The existing ISPF tables are transformed in the background, and for each DB2
      subsystem, a monitoring profile is created.
      g. Optional: Make changes to your configuration. If you want to exploit monitoring profiles, then
      proceed with the steps described in Exploiting monitoring profiles instead of the following steps
      described in this section.
      h. Select option Basic product setup (incl. User interfaces) and then select option Create Runtime
      Members (OMEGAMON Collector/UI). A batch job is generated that creates the runtime
      members.
      i. Type sub and then press Enter to submit the job.
      j. Press F3 until the OMEGAMON XE for DB2 PE on z/OS Main Menu is displayed again.
      k. Select option Configure monitoring profiles and then select option Create profile members. A
      batch job is generated that creates the profile members.
      l. Type sub and then press Enter to submit the job.
      m. Press F3 until the OMEGAMON XE for DB2 PE on z/OS Main Menu is displayed again.
      n. Select option Configure DB2 subsystem monitoring and then select option Create runtime
      members (DB2 related). A batch job is generated that creates the DB2 related runtime members.
      o. Type sub and then press Enter to submit the job.
      p. Press F3 until you return to the RUNTIME ENVIRONMENTS (RTEs) panel.
      q. If you need to allocate additional runtime data sets (for example if you enabled Near-Term
      History or Periodic Exception Processing), the job is created for you. Submit also this job
      ( &rhilev.&rte.RKD2SAM(ALLOCDS). If you configured OMEGAMON Collector to allocate
      additional runtime data sets automatically, the job is submitted automatically.
      r. For each DB2 subsystem you want to monitor, submit the BIND jobs OMBP <ssid> and OMBD
      <ssid>
      where <ssid> is the DB2 subsystem ID. If EXPLAIN is used, for each DB2 subsystem for
      that you want to use EXPLAIN, submit the BIND jobs EXBP <ssid> and EXBD <ssid> where <ssid>
      is the DB2 subsystem ID.e ha For more information, see the Complete the configuration file. Type
      a c in the Action field and then select option 2. Then select option 4.


  • Update 3: Exploiting monitoring profiles (June 2009)
    An additional step has been added after step 15.

    16. Copy the OMEGAMON Collector started task that is generated to your &rhilev.&rte.RKD2SAM library to your system PROCLIB, or update your OMEGAMON Collector started task JCL manually as follows:
    Replace

    //O2CI EXEC PGM=KOBCIRT0,REGION=0M,DPRTY=(15,15),TIME=1440

    with


    //O2CI EXEC PGM=KO2ZTOPB,REGION=0M,
    // PARM='/SUB=OMPE',DPRTY=(15,15),TIME=1440

    Note: You can perform migration also by means of batch mode install.


    • Update 4: Upgrading the Tivoli Enterprise Monitoring Agent (June 2009)
      The final two steps have been deleted.

      The Tivoli Enterprise Monitoring Agent does not require any reconfiguration. However, you must resubmit the configuration job 'Register with local TEMS'.

      About this task

      • The Register with local TEMS step is part of the LOAD job. So you must ensure that you run the LOAD job for the following runtime environments:
        - The runtime environment where the Tivoli Enterprise Monitoring Agent is running.
        - The runtime environment where the Hub Tivoli Enterprise Monitoring Server of the Tivoli
        Enterprise Monitoring Agent is running.
        - The runtime environment where the Primary Tivoli Enterprise Monitoring Server of the Tivoli
        Enterprise Monitoring Agent is running.
        - The runtime environment where the Secondary Tivoli Enterprise Monitoring Server of the Tivoli
        Enterprise Monitoring Agent is running.


    • Update 5: Overview for resubmitting configuration jobs (June 2009)
      A few changes have been made to the first row in Table 7.



    • Update 6: Subtask commands to the Near-Term History Data Collector (August 2009)
      The START command has been modified.


    • Update 7: Subtask commands to the Event Collection Manager (August 2009)
      The START command has been modified.


    • Update 8: Updating Authorizations on data sets for the OMEGAMON Collector started task (December 2009)
      Added two new authorizations on data sets for the OMEGAMON Collector started task in Chapter 3, Prerequisites, Authorization requirements, Table 4.



    • Update 9: Starting Additional DB2 Traces (March 2010)
      Added this new option to the Profile configuration panel. This option allows you to to start additional DB2 traces.

    • Update 10: Setting a threshold for the elapsed processing time in the PE Server subtask - PM21372 (November 2010)
      A new subcommand for the Performance Expert Server subtask is introduced for serviceability purposes and should be used after consultation with IBM support.
      F cccccccc,F PESERVER,F db2ssid, EPTT = 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
      elapsed processing time threshold
      - 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 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 PE server subtask. For example, message FPEV3013E reports
      timeout conditions when data retrieval requests issued by the classic interface are not
      completed by the PE Server subtask within 10 seconds.
      The Modify command sets an internal threshold for the elapsed processing time (EPTT)
      in the DB2 interface task of the PE Server subtask. If a call to the DB2 IFI interface
      does not complete within the specified time:
      - Message FPEV2100W is issued.
      - The control block containing measured elapsed times is dumped to the server log
      in hexadecimal format.
      - 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 PE Server subtask is recycled.


    • Update 11: Subtask commands to the Near-Term History Data Collector (January 2011)
      The START command has been updated as follows:

    Related information

    Tivoli OMEGAMON XE Family

    Publication number

    GC19-2511-00

    Original publication date

    2014/6/30

    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:

    4.2.0

    Operating system(s):

    z/OS

    Reference #:

    7016049

    Modified date:

    2011-01-13

    Translate my page

    Machine Translation

    Content navigation