IBM Support

PI81406: ABENDS0C4 HIGH CPU USAGE VOLSER FIELD EMPTY DISPLAYING TEP "LOG MANAGER" WORKSPACE KD2VLOGM IN CUA LOGD IN CLASSIC

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DUMP TITLE=OMEGAMON II FOR DB2 DUMP:  TASK=COMMCOLL,ID=V520
    ,MOD=KO2OCNTB,OFFSET=00362E,CODE=S0C4/00000004
    KO2OCNTB +362E IN EXTENDED PRIVATE,0C4/4 abend is in O2OPCN +C8E
    .
    In classic
    R - Resource Manager
    B - Log Manager
    Zoom (PF11) on Primary Active Log
    Log Volser will be blank
    
    DUMP TITLE=OMEGAMON II FOR DB2 DUMP: TASK=COMMCOLL,ID=V530
    ,MOD=KO2XDB2S, OFFSET=0068E0,CODE=S0C4/00000010. This 0C4-10 is
    in O2XSYS +EC0 V530 03/28/16 PI50561 (SWRQ routine), due to an
    input TCB address of 0
    .
    This issue can also lead to the following string of messages
    CI0722: SUBTASK LOOP IDENTIFICATION AND ANALYSIS IN
    PROGRESS
    CI0723: LOOPING COMMON INTERFACE SUBTASK SCHEDULED FOR
    TERMINATION
    CI0724:  ID=COMMCOLL            PROGRAM=KO2AINIB
    CI0985: SUBTASK ID=COMMCOLL FORCIBLY DETACHED
    KO2I0164I D5API COLLECTOR RELEASE COUNTER TBL DB2 D02V ON
    BEHALF OF AGENT OMDP
    
    High CPU usage on Omegamon for DB2 PE classic address
    
    High CPU may appear in module KO2ACONB particularly in CSECTs
    O2STOR
    O2OSPC
    O2ORCV
    O2OPCN
    O2STOB
    O2STOA
    
    Agent task may show a number of these messages
    (0000-C6C40063:kdpd5api,137,"D5API") Data collection error - DB2
     DB2G table DPSYEXC rc=00000024.
    
    Keywords
    ABEND0C4 ABENDS0C4 S0C4 0C4 KO2OCNTB KO2XSYS
    

Local fix

  • Apply PTF when available
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM users of        *
    *                 component                                    *
    *                 - Classic Interface                          *
    *                 - TEP                                        *
    *                 - CUA                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1.ABEND S0C4 in DB2 global              *
    *                        collection routine can happen         *
    *                        while displaying LOGD panel in        *
    *                        Classic, TEP "LOG MANAGER"            *
    *                        workspace, KD2VLOGM CUA panel.        *
    *                      2.High CPU usage while displaying       *
    *                        archived datasets information.        *
    *                      3.Volume serial field is not            *
    *                        displayed on ZLOGD panel in           *
    *                        Classic, TEP "LOG MANAGER"            *
    *                        workspace, KD2VLOGM CUA panel.        *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    ****************************************************************
    1.Abend S0C4 occurred due to incorrect parameters
      supplied to the SWAREQ service request to collect
      active LOG datasets information.
    2.High CPU utilization occurred while processing archived
      datasets data due to incorrect processing code path.
    3.Volume serial field not displayed due to incorrect
      TIOT/JFCB control block values supplied.
    

Problem conclusion

  • 1. Change logic to prevent the abend and High CPU
       usage.
    2. Use correct TIOT/XTIOT entry to locate JFCB block.
    
    Search Keywords:
    KO2OCNTB ABEND0C-04 SWAREQ ZLOGD VOLSER HIGH CPU TEP LOG MANAGER
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI81406

  • 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

    2017-05-10

  • Closed date

    2017-09-07

  • Last modified date

    2018-04-05

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

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

    UI50169 UI50170 UI50171

Modules/Macros

  •    KO2XSYSA KO2XSYSK KO2XSYSS KO2XSYS2 KO2XSY3A
    KO2XSY3K KO2XSY3S KO2XSY32 KO2XSY5A KO2XSY5K KO2XSY5S KO2XSY52
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R520 PSY UI50169

       UP17/09/11 P F709

  • R530 PSY UI50170

       UP17/09/11 P F709

  • R540 PSY UI50171

       UP17/09/11 P F709

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:
05 April 2018