PK42686: DAPICOMM CHAIN BROKEN

APAR status

• Closed as program error.

Error description

• The storage backing the DAPICOMMM control block is being
  freed but the pointer to that storage is not being removed
  from the DAPICOMM chain.  This is causing various AbEnds in
  different CSects.
  SYMPTOMS:
  
  
  
  
  S0C4 RC11 KO2AINIB +x'091A'
  S0C4 RC10 KO2AINIB +x'3662' followed by S602
  S0C4 RC11 KO2ACONB +x'E13A'
  S402 PERCOLATED TO D5API MODULE KO2ACONB
  S23E RC08
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   Tivoli Enterprise Monitoring Agent       *
  ****************************************************************
  * PROBLEM DESCRIPTION: ABEND0C4 RC11 in KO2AINIB or ABEND0C4   *
  *                      RC11 in KO2ACONB or ABEND402            *
  *                      PERCOLATED TO D5API MODULE KO2ACONB     *
  *                      in OMPE Server(CLASSIC) address space   *
  *                      after DAPICOMM freed by agent.          *
  *                      The problem can also manifest as        *
  *                      excessive CPU in the OMPE Server        *
  *                      address space.                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  An internal control block was not removed from a chain after
  being freed. Subsequent traversal of the chain caused an
  ABEND0C4, an ABEND402, or a tight CPU loop due to a circular
  chain.
  

Problem conclusion

• Ensure control block is removed from the chain before it's
  freed.
  
  KEYWORDS: ABEND0C4 KDPAGENT.@112880+428 ABENDS32E KO2I1001W
            D5DCON CANCEL KO2AINIB KO2ACONB ABEND402 D5API
            DAPICOMM HIGH CPU
  

Temporary fix

Comments

APAR Information

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

  PK40810

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

Modules/Macros

•    DUMM3KO2
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels