IBM Support

PI47653: KO2Z662I OM00 V520 COMMON ROUTING TABLE TASK WAIT-PEINIT ISSUED MANY TIMES. HIGH CPU IN COLLECTOR.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • High volume of messages
    05.40.49 STC20017 KO2Z662I OM00 V520 Common routing table task
    Wait-PEinit AUTOTIME=0005 ROUT=1892D000
    over a very short period. Message issued over 30 times with the
    same time stamp.
    
    Issue is caused by AUTODETECT=N in (OMPEMSTR) and no specific
    DB2 subsystems specified in (OMPEMSTS) by coding DB2SSID=dbid
    

Local fix

  • Set AUTODETECT=Y in (OMPEMSTR) or specify a DB2 to monitor in
    (OMPEMSTS) via DB2SSID=dbid
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component                           *
    *                 - OMEGAMON collector                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Collector loops issuing KO2Z662I        *
    *                      OM00 V520 COMMON ROUTING TABLE TASK     *
    *                      WAIT-PEINIT.  High CPU.                 *
    ****************************************************************
    * RECOMMENDATION: Check parameters for which DB2s are to be    *
    *                 monitored.  Apply this PTF.                  *
    ****************************************************************
    PROBLEM SUMMARY:
    When AUTODETECT=NO and no specific DB2s are to be monitored,
    the collector will repeatedly issue KO2Z662I messages and use
    a lot of CPU.
    
    PROBLEM CONCLUSION:
    Wait between issuing KO2Z662I messages and change the status
    in the message to indicate we're waiting for DB2s to monitor
    via a modify command:  F cccccccc,F PESERVER,S dddd
    
    KEYWORDS:
    HIGH CPU KO2Z662I AUTODETECT
    

Problem conclusion

  • Wait between issuing KO2Z662I messages and change the status
    in the message to indicate we're waiting for DB2s to monitor
    via a modify command:  F cccccccc,F PESERVER,S dddd
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI47653

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    520

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-08-26

  • Closed date

    2015-11-26

  • Last modified date

    2017-02-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UI33337

Modules/Macros

  • KO2ZROU
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R520 PSY UI33337

       UP15/12/01 P F511

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
01 February 2017