IBM Support

IT28539: XMS .NET incorrectly require "get" authority on the target cluster queue for an alias queue

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

  • XMS .NET need not have a "Get access" if the target queue for an
    alias queue is a cluster queue,as it is possible for them to
    query the backout threshold and backout requeue queue name with
    just "inquire" access.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    XMS .NET applications getting messages from an alias queue on a
    queue manager where the target queue for the alias queue is a
    cluster queue.
    
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When the XMS .NET client detect a message on a destination, they
    will perform the following processing to determine whether to
    deliver that message to an application for processing, or move
    it to a backout requeue queue:
    
    - Check the backout count of the message.
    - If the backout count is greater than zero, then:
        - If this is the first message that has been detected which
    has a backout count greater than zero, then:
            - Query the backout threshold (BOTHRESH) and backout
    requeue queue name (BOQNAME) attributes of the queue.
            - Cache the values of the backout threshold and backout
    requeue queue attributes.
        - End if.
        - Compare the backout count of the message to the cached
    value of the backout threshold attribute for the queue.
            - If the backout count is greater than or equal to the
    backout threshold, then:
                - Move the message to the backout requeue queue, if
    one has been specified.
            - Else:
                - Deliver the message to the application.
            - End if.
    - Else:
        - Deliver the message to the application.
    - End if
    
    If XMS .NET application was configured to get messages from an
    alias queue that had a cluster queue as its target, then the XMS
    would open the cluster queue with the following options:
    
    - MQOO_INPUT_AS_Q_DEF
    - MQOO_INQUIRE
    - MQOO_FAIL_IF_QUIESCING.
    
    and then issue an MQINQ API call to get the values of the
    BOTHRESH and BOQNAME properties.
    
    However, the open option:
    
      MQOO_INPUT_AS_Q_DEF
    
    was not required.
    

Problem conclusion

  • XMS .NET client has been updated so that if a XMS application is
    configured to get messages from:
    
    - Either a cluster queue.
    - Or an alias queue, where the target for the alias queue is a
    cluster queue.
    
    then XMS .NET will open the cluster queue with the options:
    - MQOO_INQUIRE
    - MQOO_FAIL_IF_QUIESCING.
    
    in order to get the value of the backout threshold (BOTHRESH)
    and backout requeue queue name (BOQNAME) properties.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.14
    v9.0 LTS   9.0.0.9
    v9.1 LTS   9.1.0.5
    
    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

    IT28539

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-03-21

  • Closed date

    2020-01-14

  • Last modified date

    2020-01-14

  • 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 MP

  • Fixed component ID

    5724H7251

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":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
14 January 2020