IBM Support

PK98483: KO2XSYS2+20FA ABEND0C4-4 HIGH CPU KO2ONAFB+117E ABEND0C2

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Program check LOOP ABEND0C4-4 KO2XSYS2+20FA (at PK73189 level)
    on a 5870700C (Load) instruction with R7 bad.  Omegamon was
    accessing the DB2 RMVT without first checking if z/OS DB2 was
    active.
    This occured with AUTODETECT=Y was used.  No data was displayed
    in the TEP workspaces.  Omegamon recovered from this ABEND and
    continued to drive the same code which kept ABENDing resulting
    in high CPU.
    INSPECT showed:
    -ICPU  TCB(*) HOT
     +<.:  %CPU UTILIZATION (TCB)
    |----+---20---+---40---+---60---+---80---+---100
     +  55 009C8848 KO2ACONB  98.72
    |===========================================>
    The LOOP shows up in SYSTRACE with repetitive PROGRAM CHECK
    entries and the unit of work being driven with a DSP entry for
    KO2ORCVB.  The PROGRAM CHECK can occur in KO2XSYSA (DB2 R910)
    as well as KO2XSYS2 (DB2 R810).
    Also corrected in this APAR is
    Dump Title: OMEGAMON II FOR DB2: COMPID=5655OPE00, JOB=OMEGDB2 ,
                 LMOD=KOBAS510#L, CSECT=UNKNOWN , OFFSET=00D7A4
    ABEND0C2 when a 0B11 (BSM) instruction executes in KO2ONAFB+117E
    (at PK74788 level) resulting in the PSW of 077D1000 00C4411C,
    SYSTRACE showing
     008620C8 *PGM    002 077D1000 00C4411C  00040002 00000000
                                                      00104000
    Prior to the BSM executing, R1 contaied 3BC44118 and because the
    high order bit is off, the resuting AMODE of the PSW after the
    BSM is executed is 24-bit mode.  Location 00C44118 contained
    80C45458 -- a SSM (Set System Mask) instruction which is a
    privileged instruction.  This caused the ABEND0C2.  This code
    is part of the IFNODB2 routine driven if Omegamon discovers that
    z/OS DB2 is no longer operational.
    The real problem is caused because KO2ORCVB drives this routine
    from it ESPIE, an ESPIE that gets control as a result of a
    PROGRAM CHECK.  The IFNODB2 routine does not expect to be driven
    from an ESPIE and as a result of this uses an incorrect base
    register and ABENDs.  In this instance an ABEND0C2 occurred, but
    the result of this failure can be unpredictable.  ABEND0C4 and
    other ABENDs are possible.  The end result of this PROGRAM CHECK
    loop is high CPU.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component                           *
    *                 - OMEGAMON Server                            *
    *                 - Common Collector                           *
    *                 - Classic Interface                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Intermittent HIGH CPU condition when    *
    *                      connected to a Remote DB2 subsystem.    *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    ****************************************************************
    PROBLEM SUMMARY:
    1. Common collector connection to a remote DB2 causes
       High CPU conditions.
    2. DB2 subsystem "not active" condition causes error
       recovery loop.
    
    PROBLEM CONCLUSION:
    1. Common Collector will not establish a remote
       DB2 connection.
    2. Correct the IFNODB2 process to properly handle a DB2 SSN
       which is currently terminating.
    

Problem conclusion

  • 1. Common Collector will not establish a remote
       DB2 connection.
    2. Correct the IFNODB2 process to properly handle a DB2 SSN
       which is currently terminating.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PK98483

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    410

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-10-13

  • Closed date

    2009-12-23

  • Last modified date

    2010-02-17

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

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

    PM03898 UK53147

Modules/Macros

  • KO2DATA  KO2HSVPB KO2LCAPB KO2OCMCB KO2OINTB
    KO2ORCVB KO2OSNEC KO2OSNEF KO2OSNPB
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R410 PSY UK53147

       UP09/12/29 P F912

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":"410","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":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
17 February 2010