IBM Support

PM94961: When eXtremememory is enabled the mapglobalindex api may return incorrect data after map has been cleared.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When clearing a map with eXtremeMemory enabled, it's possible
    that not all data will be cleared from the associated global
    index.  This could cause subsequent queries on the
    MapGlobalIndex API to return incorrect data.
    
    In particular the findPartitions method on MapGlobalIndex may
    return partitions which don't actually contain data matching
    the indexed attribute.  If the customer is using the results
    of findPartitions to run map agents, their implementation
    should be tolerant of the agent running on partitions which no
    longer container entries matching the provided attributes.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of global indexing on maps that have  *
    *                  IBM                                         *
    *                  eXtremeMemory enabled.                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: The MapGlobalIndex API returns          *
    *                      incorrect                               *
    *                      data after a map has been cleared.      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a map with eXtremeMemory enabled is cleared, all data might
    not be cleared from the associated global index.
    This problem causes subsequent queries on the MapGlobalIndex API
    to return incorrect data. The findPartitions
    method on the MapGlobalIndex interface returns partitions that
    do not contain data that matches the indexed attribute.
    

Problem conclusion

  • A fix is provided so that the MapGlobalIndex API behaves as
    expected after the map has been cleared.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM94961

  • Reported component name

    WS EXTREME SCAL

  • Reported component ID

    5724X6702

  • Reported release

    860

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-08-12

  • Closed date

    2013-08-21

  • Last modified date

    2013-08-21

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

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

Fix information

  • Fixed component name

    WS EXTREME SCAL

  • Fixed component ID

    5724X6702

Applicable component levels

  • R860 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"860","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
21 August 2013