IBM Support

PH06033: MQ Z/OS: APPLICATION HUNG WHEN ASYNC CONSUMER IS USED WITH A QSG

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • MQ z/OS
    application hung when async consumer is used with a QSG
    
    There is an issue with the way the async consumer is set up
    when the application is connected to a QSG and there is more
    than one member available on the LPAR.
    
    When an async consumer is established, a new thread is created
    which is where the callback processing will run.
    This additional thread needs to be connected to the same qmgr as
    the application thread, so that it can use the queue handle
    which  it has already been opened.
    If the application thread is connected using the QSG name, the
    connect
    logic for the async thread is incorrectly connected using the
    QSG name.
    If there are two or more members of the QSG on the same LPAR,
    this means
    that the async thread can end up connected to a different qmgr
    from the
    application thread.
    

Local fix

  • na
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
    *                 Release 0 Modification 0 and Release 1       *
    *                 Modification 0.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: MQ Z/OS: APPLICATION HUNG WHEN ASYNC    *
    *                      CONSUMER IS USED WITH A QSG             *
    ****************************************************************
    When an async consumer is established, a new thread is created
    which is where callback processing will run. This additional
    thread needs to be connected to the same qmgr as the application
    thread, so it can use the queue handle which has already been
    opened.
    If the application thread is connected using the QSG name,
    the  connect logic for the async thread is incorrectly
    connecting using the QSG name.
    If there are two or more members of the QSG on the same LPAR,
    this means that the async thread can end up connected to a
    different qmgr from the application thread.
    

Problem conclusion

  • The CSQBCON module has been updated with corrective conditional
    logic to ensure the application threads connect appropriately.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH06033

  • Reported component name

    IBM MQ Z/OS V9

  • Reported component ID

    5655MQ900

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-12-04

  • Closed date

    2019-06-25

  • Last modified date

    2019-08-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PH06227 UI63846 UI63847

Modules/Macros

  • CSQBCON
    

Fix information

  • Fixed component name

    IBM MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R000 PSY UI63846

       UP19/08/01 P F907

  • R100 PSY UI63847

       UP19/08/01 P F907

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"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:
01 August 2019