IBM Support

IT10521: INQUIRING QUEUE NAMES FAILS IN MQ V8 EXPLORER AND TIMES OUT WITH AMQ8416 IN RUNMQSC CLIENT MODE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After applying the following authorities to the user connecting
    with MQ Explorer:
    
    setmqaut -m TESTQMGR -n 'SYSTEM.DEFAULT.MODEL.QUEUE' -t queue -g
    group1 +dsp +get
    setmqaut -m TESTQMGR -n 'SYSTEM.MQEXPLORER.REPLY.MODEL' -t queue
    -g group1 +dsp +get +inq
    setmqaut -m TESTQMGR -n 'SYSTEM.BROKER.CONTROL.QUEUE' -t queue
    -g group1 +put
    setmqaut -m TESTQMGR -n 'SYSTEM.ADMIN.COMMAND.QUEUE' -t queue -g
    group1 +inq +put
    setmqaut -m TESTQMGR -t qmgr -g group1 +connect +dsp +inq
    +setall
    
    Connection to queue manager works fine, but an incomplete
    list of queues is displayed.
    
    If using the RUNMQSC application as a user with these same
    authorities, and connecting to the queue manager in client mode,
    all expected queues can be displayed successfully, however,
    runmqsc then waits for 30 seconds and prints "AMQ8416: MQSC
    timed
    out waiting for a response from the command server".
    

Local fix

  • na
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using MQ Explorer or runmqsc in client mode to query the
    queue names.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    This problem occurred because of incorrect sequence number in
    the PCF reply message
    sent by the command server. The sequence number in the final
    reply message to an Inquire
    Queue command was incorrect if the user issuing the command does
    not have display authority
    over queues in the list. A change to Explorer in 8.0.0.2 added a
    check that the sequence
    number of the final reply should match the number of replies
    received, this change has exposed
    this defect in the command server.
    

Problem conclusion

  • MQ has been modified to correctly set the PCF sequence number.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.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

    IT10521

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-08-11

  • Closed date

    2015-09-30

  • Last modified date

    2015-10-09

  • 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 BASE MULTIP

  • Fixed component ID

    5724H7251

Applicable component levels

  • R800 PSY

       UP

[{"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:
09 October 2015