IBM Support

IC68557: MQRC_HOBJ_ERROR when using hobj after successful open in the unmanaged .NET client when talking to a V7 queue manager.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An MQRC_HOBJ_ERROR (2019) is produced during an MQ API request
    such as a get/put using the unmanaged .NET client (for example,
    AccessQueue) connected to a V7 queue manager. The object handle
    passed into the API request was previously returned
    successfully from an open API request. The application in
    question has previously established a connection to a V6 queue
    manager.
    

Local fix

  • DO NOT CONNECT TO A V6 QUEUE MANAGER AND THEN CONNECT TO A V7
    QUEUE MANAGER VIA SPI AND ISSUE A MQPUT.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Any users of WebSphere MQ using the unmanaged .NET client to
    interact with queue objects hosted on a V7 queue manager. Note
    the error only occurs if the application has also previously
    connected to a V6 queue manager on the same/different thread.
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM SUMMARY:
    The problem was caused by incorrect error handling within the
    .NET open API request to a V7 queue manager. An error occurred
    during the open request however this was then not passed back
    up the function stack to the caller. This resulted in an
    attempt by the application to use an invalid object handle.
    

Problem conclusion

  • WebSphere MQ was modified to ensure that the correct return
    codes were being passed back to the application, thus
    preventing it from using an invalid object handle in subsequent
    API calls.
    
    APAR IC68558 should also be applied if this error is observed
    as it resolves an MQRC_FUNCTION_NOT_SUPPORTED error which can
    be incurred during 'open' API requests - one possible cause of
    the knock-on 2019 error.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.3
    --------           --------------------
    Windows            U200320
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available, information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC68557

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-05-10

  • Closed date

    2010-05-13

  • Last modified date

    2010-05-13

  • 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

    WMQ WINDOWS V7

  • Fixed component ID

    5724H7220

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
13 May 2010