IBM Support

PH18752: MQCTL API IS NOT RETURNED TO APPLICATION WHEN SPECIFYING BROWSE NEXT WAIT OPTION WITH 5 SEC INTERVAL FOR SHARED QUEUE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer use MQInput node in the message flow of IBM Integration
    Bus for z/OS V10, and it internally issues MQCB/MQCTL for async
    get with browse next wait (wait interval is 5 sec) option.
    When customer tried to stop the message flow, the stop process
    hangs and is timed out, then BIP4041E is seen in the log.
    This causes IIB Integration Server to hang in termination unless
    MQ QMGR is cancelled.
    

Local fix

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: Callbacks registered by MQCB against    *
    *                      shared queues are not called for        *
    *                      MQRC_NO_MSG_AVAILABLE (MQRC2033) when   *
    *                      browsing for messages and the wait      *
    *                      interval expires.                       *
    ****************************************************************
    When browsing a shared queue, an internal MQGET is redriven
    periodically to check for new messages arriving on the queue.
    If the WaitInterval is found to have expired CSQMGETM redrives
    the internal MQGET again, resetting the WaitInterval, without
    returning control to the adapter for the callback to be driven.
    
    If the callback was started with MQCTL_START_WAIT, this means
    that the calling thread does not receive control back until the
    exit is driven for another reason (for example, a message
    arriving on the queue) and stops the callback.
    

Problem conclusion

  • CSQMGET has been changed to correctly indicate to CSQMGETM
    that the WaitInterval has expired so that the callback will be
    driven for reason MQRC_NO_MSG_AVAILABLE.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH18752

  • 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

    2019-11-01

  • Closed date

    2019-11-12

  • Last modified date

    2019-12-24

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

    PH16448

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

    UI66378 UI66379

Modules/Macros

  • CSQMGET
    

Fix information

  • Fixed component name

    IBM MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R000 PSY UI66378

       UP19/11/27 P F911

  • R100 PSY UI66379

       UP19/11/27 P F911

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:
24 December 2019