PM78825: The ObjectMap output format is ignored by the HashIndex find methods when you enable eXtreme data format (XDF).

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 running with XDF (XIO along with a map copy mode that is
    set to COPY_TO_BYTES), the HashIndex findXXXX methods should
    return keys that are based on the KeyOutputFormat
    configuration for the object map. The HashIndex methods are
    currently using the wrong configuration and might return RAW
    keys (SerializedKey) when the application requests NATIVE
    keys (POJO keys) or the reverse, depending on the ObjectMap
    configuration, and the requested output format. The fix
    corrects the behavior so that the key output format from the
    object map is recognized by the HashIndex APIs that return
    keys.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere eXtreme Scale V8.6 users who use  *
    *                  XIO and the COPY_TO_BYTES copy              *
    *                  mode, performing findXXXX methods when the  *
    *                  keyOutputFormat configuration of the        *
    *                  data grid is changed from the default       *
    *                  value.                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: The HashIndex methods are currently     *
    *                      using the wrong configuration and       *
    *                      might return the wrong type of keys.    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    WebSphere eXtreme Scale V8.6 is using
    the OutputFormat setting from the
    base map, instead of the output format
    from the object map as it should.
    

Problem conclusion

  • Code has been updated to use the appropriate OutputFormat
    setting from the object map.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM78825

  • 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

    2012-12-10

  • Closed date

    2013-06-03

  • Last modified date

    2013-06-03

  • 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



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere eXtreme Scale

Software version:

860

Reference #:

PM78825

Modified date:

2013-06-03

Translate my page

Machine Translation

Content navigation