IBM Support

IT23448: Clarification in the Javadoc for the getProviderMajorVersion() method in class com.ibm.mq.jms.MQConnectionMetaData

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

  • The Javadoc for the IBM MQ classes for JMS method
    com.ibm.mq.jms.MQConnectionMetaData.getProviderMajorVersion()
    does not adequately describe the meaning of the integer value
    returned from the method.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects the users of the IBM MQ classes for JMS.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The Javadoc for the following three methods did not describe the
    purpose of the value which they returned:
    
     - com.ibm.mq.jms.MQConnectionMetaData.getProviderMajorVersion()
     - com.ibm.mq.jms.MQConnectionMetaData.getProviderVersion()
     - com.ibm.mq.jms.MQConnectionMetaData.getProviderMinorVersion()
    
    The Javadoc could have mislead application programmers into
    thinking the methods returned information pertaining to the
    product version of IBM MQ classes for JMS.
    
    These methods are intended to return the mode of operation that
    the JMS application is using as documented in the following
    Knowledge Center page:
    
    https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm
    .mq.con.doc/q123670_.htm
    

Problem conclusion

  • The Javadoc for the following three methods:
    
     - com.ibm.mq.jms.MQConnectionMetaData.getProviderMajorVersion()
     - com.ibm.mq.jms.MQConnectionMetaData.getProviderVersion()
     - com.ibm.mq.jms.MQConnectionMetaData.getProviderMinorVersion()
    
    have been updated to document that the values returned
    correspond to the mode of operation in which the MQ classes for
    JMS are running for the JMS Connection object to which they
    belong.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 CD    9.0.5
    v9.0 LTS   9.0.0.4
    
    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

    IT23448

  • Reported component name

    IBM MQ BASE M/P

  • Reported component ID

    5724H7261

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-12-11

  • Closed date

    2018-02-15

  • Last modified date

    2018-02-15

  • 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

    IBM MQ BASE M/P

  • Fixed component ID

    5724H7261

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 February 2018