IBM Support

PK19340: ABEND 106-0C IN OMEGAMON XE PE DATA SERVER WHEN MONITORING MULTIPLE DB2 SUBSYSTEMS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Running the OMEGAMON DB2 Server (Classic O2CI) on an LPAR that
    has 20 DB2 subsystems defined and 12 active results in a large
    number of subtasks running for the DB2PE servers that are
    started as a results of AUTODETECT. Attempts to start additional
    server subtasks or initiate other functions fail due to
    insufficient storage to load modules in to LSQA.
    
    IEW4004I FETCH FOR MODULE DGOVEE00 FROM DDNAME STEPLIB  FAILED
    BECAUSE INSUFFICIENT LSQA STORAGE WAS AVA
    IEW4005I FETCH FOR MODULE DGOVEE00 FROM DDNAME STEPLIB  FAILED
    BECAUSE IEWFETCH ISSUED RC 0C AND REASON
    CSV031I LIBRARY ACCESS FAILED FOR MODULE DGOVEE00, RETURN CODE
    24, REASON CODE 26080021, DDNAME STEPLIB
    CSV028I ABEND106-0C  JOBNAME=CANSO2    STEPNAME=CANSO2
    
    This may lead to abend878, abenda03 and the O2CI task
    terminating.
    

Local fix

  • Locate the OMPEMSTR member, most likely in the RKD2PAR dataset.
    If it is
    not in the RKD2PAR dataset, check the other datasets allocated
    to the
    RKANPAR DD in the step that executes KOBCIRT0
    
    Locate the line that reads
    DB2SSID=(DSN1)
    Change this line to identify the DB2 subssytems to be monitored
    by the
    DB2PE/PM side, for example
    DB2SSID=(DSN1,DSN2,DSN3)
    Add a line to the OMPEMSTR member as follows
    AUTODETECT=NO
    
    This will result in DB2PM/PE data servers only being started for
    the
    selected DB2 subsystems
    
    If during the course of the day it is neccessary to add/remove
    additional DB2 subsystems, modify the OMPEMSTR member as
    indicated above
    to change the DB2 subsys selection, then issue these operator
    commmands
    F o2ci,P PESERVER
    to stop all DB2PE/PM dataservers
    /F o2ci,S PESERVER
    to restart the DB2PM/PE data servers for the new choice of DB2
    subsystems.
    o2ci represents the name of the OMEGAMON DB2 classic address
    space
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM V310            *
    *                 users of component:                          *
    *                 - OMEGAMON Server                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: When MULTIPLE DB2 SUBSYSTEMS shall be   *
    *                      monitored the OMEGAMON XE for DB2 PE    *
    *                      DATA SERVER starts a monitoring         *
    *                      instance for each DB2 subsystem. Some   *
    *                      load modules will be loaded into        *
    *                      storage below the 16 MB line. When      *
    *                      storage is exhausted and a further      *
    *                      instance is to be started to monitor    *
    *                      an additional DB2 subsystem an ABEND    *
    *                      106-0C will occur.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When MULTIPLE DB2 SUBSYSTEMS shall be monitored the OMEGAMON XE
    for DB2 PE DATA SERVER starts a monitoring instance for each
    DB2 subsystem. Some load modules will be loaded into storage
    below the 16 MB line. When storage is exhausted and a further
    instance is to be started to monitor an additional DB2 subsystem
    an ABEND 106-0C will occur.
    

Problem conclusion

  • Whenever possible the load modules will be loaded into storage
    above the 16MB line.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK19340

  • Reported component name

    OM XE DB2PE/PM/

  • Reported component ID

    5655OPE00

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-02-08

  • Closed date

    2006-03-16

  • Last modified date

    2006-04-05

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

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

Modules/Macros

  •    DGOMEXA1 DGOMTX00 DGOVDB2C DGOVDS   DGOVMSTR
    DGOVM000 DGOVSERV DGOVTCPL DGOVTCPS DGOVUSS0 DGOVZMAI HKDB310J
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM/

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R310 PSY UK12662

       UP06/03/22 P F603

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

Document Information

Modified date:
05 April 2006