IBM Support

PI14217: OMPELOG TIMESTAMP DOES NOT REFLECT SYSTEM TIME

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • By default OMPELOG is set active. This results in messages that
    go to JESMSGLG and messages that go to SYSPRINT being written to
    the same DD OMPELOG.
    
    The timestamps in the OMPELOG are not adjusted for the local
    system offset to GMT.
    

Local fix

  • The OMPELOG can be turned off by setting
    OMPELOG=INACTIVE
    in member OMPEOPTS of the RKD2PAR and / or RKD2PARU datasets,
    which ever is first in the concatenation
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component                           *
    *                 - OMEGAMON collector                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: OMPELOG timestamp is not adjusted to    *
    *                      local time offset.                      *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    ****************************************************************
    PROBLEM SUMMARY:
    The messages in OMPELOG are prefixed by a date/time string.
    This string contains the value from the hardware clock.
    The hardware clock may be set to a value other than local time.
    
    PROBLEM CONCLUSION:
    Adjust the hardware clock value using the local date and time
    offset. Format the adjusted value for use in the OMPELOG.
    
    KEYWORDS:
    STCK GMT
    

Problem conclusion

  • Adjust the hardware clock value using the local date and time
    offset. Format the adjusted value for use in the OMPELOG.
    
    KEYWORDS:
    STCK GMT
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI14217

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    520

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-03-21

  • Closed date

    2014-06-06

  • Last modified date

    2014-07-01

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

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

    UI18653 UI18654

Modules/Macros

  • KO2ZLOG
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R511 PSY UI18653

       UP14/06/07 P F406

  • R520 PSY UI18654

       UP14/06/07 P F406

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 July 2014