IBM Support

PM10618: KO2CDFSA+90C ABENDDC2 RSN0055 IARV64 SHAREMEMOBJ WHEN AGENT AND LOGGED ON USER TRIED TO OBTAIN DDF DATA CONCURRENTLY

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When an AGENT and LOGGED on USER tried to obtain DDF data
    concurrently, ABENDDC2 RSN0055 IARV64 SHAREMEMOBJ KO2CDFSA+90C
    R15 = 71005520.
    From the OMPE STC log:
    KO2I0170U SDC2  ABEND IN MODULE ........ PERCOLATED TO D5API
              MODULE KO2ACONB
    IEA794I SVC DUMP HAS CAPTURED:
    DUMPID=004 REQUESTED BY JOB (OMDB2OD1)
    DUMP TITLE=OMEGAMON II FOR DB2 DUMP:  TASK=COMMCOLL,ID=V410
               ,MOD=UNKNOWN ,OFFSET=      ,CODE=SDC2/71005520
    KO2I0157I D5API COLLECTOR DISCONNECTED FROM DB2 DT11 AS
              REQUESTED BY AGENT OMDB2XD1
    KO2I0154I D5API COLLECTOR CONNECTED TO DB2 DT11 ON BEHALF OF
              AGENT OMDB2XD1
    
    ABENDDC2 rsn71005520 (xx0055xx) because a duplicate UToken
    already exists for the memory object specified for the address
    space.  SYSTRACE shows the following:
    0077E3D0 PC  ...   7        00_41714141 0090E IarV64
    0077E3D0 SSRV 14B  0A804001 00000DC2 71005520 IarV64 ShareMemObj
                                00000000_4623CEB8
                                00000300_A0104580
                                0000000F_D9D8C140 <-- UToken
    0077E3D0 *SVC   D  070C5000 818E07F0 71005520 84000000 84DC2000
    ... with the address 41714140 pointing to KO2CDFSA+90C (at
        PK80926 level).
    A few SYSTRACE entries earlier, the TCB at 007B7118 issued
    007B7118 PC ...    7        00_41714141 0090E IarV64
    007B7118 SSRV 14B  0A804001 00000000 00000000 IarV64 ShareMemObj
                                00000000_44FFC4D0
                                00000300_A0104580
                                0000000F_D9D8C140 <-- UToken
    At the time that the SVC DUMP was generated, TCB 007B7118 had
    yet to issue an IarV64 Detach, meaning the USERTKN of
    0000000F_D9D8C140 was still in use.
    When KO2CDFSA issued the IARV64 REQUEST=SHAREMEMOBJ,
                                    USERTKN=USRTKNS, ...
    it did not check for USERTKN being unique.
    .
    Additional symptom:
    An SVC dump occurred with this dump title:
    Dump Title: OMEGAMON II FOR DB2: COMPID=5655OPE00, JOB=CANSO2  ,
                 LMOD=KO2CDB2A#L, CSECT=#UNKNOWN, OFFSET=012C3E
    ABEND0C4 rc3B occurred in KO2CDFSA+C1E (at R420 PK87445 level)
    on a CLC instruction with DPSBRQAP RQA pointer above the bar.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component:                          *
    *                 -   Tivoli Enterprise Monitoring Agent       *
    *                 -   Classic Interface                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABENDDC2 KO2CDSFA+90C RSN0055 IARV64    *
    *                      SHAREMEMOBJ WHEN AGENT AND LOGGED ON    *
    *                      USER TRIED TO OBTAIN DDF DATA           *
    *                      CONCURRENTLY                            *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    *                                                              *
    ****************************************************************
    PROBLEM SUMMARY:
    WHEN AGENT AND LOGGED ON USER OBTAIN DDF DATA CONCURRENTLY THEY
    CAN TRY TO RECEIVE SHAREMEMOBJ ACCESS WITH THE SAME ID.
    
    PROBLEM CONCLUSION:
    CHANGE LOGIC TO GENERATE THE UNIQUE ID FOR ANY REQUEST OF
    SHAREMEMOBJ.
    

Problem conclusion

  • CHANGE LOGIC TO GENERATE THE UNIQUE ID FOR ANY REQUEST OF
    SHAREMEMOBJ.
    
    KEYWORDS : ABENDDC2 KO2CDSFA+90C RSN0055 IARV64  DDF DATA
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM10618

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    410

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-03-23

  • Closed date

    2010-06-16

  • Last modified date

    2010-09-16

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

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

    UK58000 UK58001

Modules/Macros

  • KO2CDFSA KO2CDFSS KO2CDFS2 KO2XTHSA KO2XTHSS
    KO2XTHS2
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R410 PSY UK58000

       UP10/06/28 P F006

  • R420 PSY UK58001

       UP10/06/28 P F006

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:
16 September 2010