IBM Support

IT20611: AMQ8077 errors are not generated after enabling ClusterQueueAccessControl=RQMName

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After enabling ClusterQueueAccessControl=RQMName, when a PUT
    results in a 2035, AMQ8077 errors are not generated.
    
    Example 1:-
    --------------
    Attempt to put to a clustered queue on another queue manager in
    the cluster with no local OAM permission other than +connect and
    +inq on the qmgr itself and no local QALIAS defined.
    
    Command: amqsput TEST.CQL QM1
    
    ClusterQueueAccessControl=Xmitq set in QM.ini file
    Result: AMQ8077 error reported against the
    SYSTEM.CLUSTER.TRANSMIT.QUEUE
    
    ClusterQueueAccessControl=RQMName set in QM.ini file
    Result: no AMQ8077 produced
    Expected Result: AMQ8077 against TEST.CQL (the clustered queue
    on another queue manager)
    
    Example 2:-
    --------------
    Attempt to put to a queue on another queue manager in the
    cluster targeting the other clustered queue manager directly
    with no local OAM permission other than +connect and +inq on the
    qmgr itself.
    
    Command: amqsput TEST.CQL QM1 8208 0 QM2
    
    ClusterQueueAccessControl=Xmitq set in QM.ini file
    Result: AMQ8077 against the SYSTEM.CLUSTER.TRANSMIT.QUEUE
    
    ClusterQueueAccessControl=RQMName
    Result: no AMQ8077 produced
    Expected Result: AMQ8077 against QM2 (the other queue manager in
    the cluster)
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    MQ clustering users who are putting message to clustered queue
    and who have enabled ClusterQueueAccessControl=RQMName
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A coding error in the MQ queue manager meant that an AMQ8077
    error wasn't reported during a MQPUT to a clustered queue on
    another queue manager, when OAM permissions were inadequate,
    when ClusterQueueAccessControl was set to RQMName.
    

Problem conclusion

  • The MQ queue manager code was modified to report AMQ8077 error
    as appropriate.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.5       7.5.0.9
    v8.0       8.0.0.8
    v9.0 CD    9.0.4
    v9.0 LTS   9.0.0.3
    
    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

    IT20611

  • Reported component name

    WEBSPHERE MQ 7.

  • Reported component ID

    5724H7240

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-05-16

  • Closed date

    2017-10-26

  • Last modified date

    2017-10-26

  • 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

    WEBSPHERE MQ 7.

  • Fixed component ID

    5724H7240

Applicable component levels

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

Document Information

Modified date:
26 October 2017