IBM Support

PK68423: OMPE SERVER HIGH STORAGE USE BELOW THE LINE TERMINATE AT END OF MEMORY RESULTING IN ABENDS80A OR ABENDS878

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When DB2 is unable to respond to collect calls, the collect call
    will time out. This will redrive connect calls between the agent
    and the OMPE server. The TCB for the collect call that timed out
    effectively is orphaned. Below the line storage in the OMPE
    server task will be consumed and the task may encounter storage
    related abends; 80A, 878...
    
    Evidence of this can be noted by numerous occurrences of the
    below messages
    
    RKLVLOG
    2008.183 01:26:20.54 KLVFL003 ALL PENDING NAF RECORDS HAVE BEEN
    WRITTEN
    2008.183 01:54:32.57
    (0000-DF37D833:kdpd5api,487,"d5api_collect") KO2I1001W
    Connection to OMPE Server CANSO2   for DB2 PB21
    2008.183 01:54:32.57 Return=00000018 Reason=00000028
    2008.183 01:54:32.57 (0001-DF37D833:kdp05agt,374,"ProcessAVT")
    Error in d5api() for kdp05agt, rc = 24
    
    and JOBLOG will show numerous
    KO2I0189I AGENT CANSD5   CONNECTING TO OM CANSO2   VERSION V410
    BY REQUEST - DB2 PB21
    
    The agent task may also experience abend
    CT/ENGINE ABEND S0C4 U0000 (NO RETRY) AT 9EDC6926 (KDPAGENT.D5TM
    RXIT+A)
    

Local fix

  • Cycle the OMPE server task.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component                           *
    *                 - OMEGAMON Server                            *
    *                 - PE Server                                  *
    *                 - Common Collector                           *
    *                 - Tivoli Enterprise Monitoring Agent         *
    ****************************************************************
    * PROBLEM DESCRIPTION: When DB2 is unavailable to service an   *
    *                      agent data collection request (via the  *
    *                      OMPE Server) within the COMMCOLL STIMER *
    *                      time period, S878 and S80A abends can   *
    *                      occur within the OMPE server and other  *
    *                      address spaces.  Eventually, the LPAR   *
    *                      may have to be IPL'd.                   *
    *                                                              *
    *                      Also, "Error 4 getting AVT pointer for  *
    *                      DB2" messages in RKLVLOG when DB2       *
    *                      system(s) that a situation is           *
    *                      distributed to are not operational.     *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    ****************************************************************
    PROBLEM SUMMARY:
    If a DB2 system is incapable of honoring requests for data
    within the time period specified by COMMCOLL STIMER, the
    connection between the agent and OMPE server for that DB2
    system can get broken and re-established many times, as
    indicated in the RKLVLOG.  Some system storage and private
    storage within OMPE server becomes exhausted, resulting in
    S878 and S80A abends within the OMPE server and other
    address spaces.
    
    Also, numerous "Error 4 getting AVT pointer for DB2"
    messages in RKLVLOG when DB2 system(s) that a situation is
    distributed to are not operational.
    
    PROBLEM CONCLUSION:
    Allow the agent / OMPE server connection to remain intact after
    a data collection time-out.
    
    Change print of "Error 4 getting AVT pointer for DB2" messages
    in RKLVLOG such that when KBB_RAS1=ERROR, they do not show.
    They will show when KBB_RAS1=ALL.
    
    KEYWORDS:
    ABENDS0C4 ABENDS878 ABENDS80A COMMCOLL STIMER
    KDPAGENT D5API PROCESSAVT KO2I1001W TIMEOUT
    

Problem conclusion

  • PROBLEM CONCLUSION:
    Allow the agent / OMPE server connection to remain intact after
    a data collection time-out.
    
    Change print of "Error 4 getting AVT pointer for DB2" messages
    in RKLVLOG such that when KBB_RAS1=ERROR, they do not show.
    They will show when KBB_RAS1=ALL.
    
    KEYWORDS:
    ABENDS0C4 ABENDS878 ABENDS80A COMMCOLL STIMER
    KDPAGENT D5API PROCESSAVT KO2I1001W TIMEOUT
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PK68423

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    410

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2008-07-01

  • Closed date

    2008-08-18

  • Last modified date

    2017-02-04

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

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

    UK39014 014PC3Ÿ 014PC3Ÿ

Modules/Macros

  •    KD5AGENT KD5ATC00 KD5AUTO1 KO2ACONB KO2AINIB
    KO2APC2A KO2APC2S KO2APC22 KO2APC3A KO2APC3S KO2APC32
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R410 PSY UK39014

       UP08/08/19 P F808 Ž

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.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410"}]

Document Information

Modified date:
30 March 2021