IBM Support

PM55740: ASYNCHRONOUS CONSUMER FAILS WITH MQRC_CALL_IN_PROGRESS (2219) ORHANGS AFTER EXECUTING MQCTL TO SUSPEND OR RESUME CONSUMER THREAD

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The customer reported the following error:
    I have a COBOL batch application.  The applications use the
    asynchronous message consumer . Sometime the MQ API "SUSPEND
    gets rc 2219, sometimes the application hangs.
    .
    The change team found that there is a problem with the
    Asynchronous Consumer, where the main and consumer threads hang
    or the main receives unexpected MQRC_CALL_IN_PROGRESS (2219)
    after executing MQCTL to suspend or resume the consumer thread.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ Version 7          *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Applications using MQ asynchronous      *
    *                      consume hang waiting indefinitely or    *
    *                      fail with unexpected reason code        *
    *                      MQRC_CALL_IN_PROGRESS (2219).           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Applications using MQ asynchronous consume can experience a loss
    of the synchronization between the main and the callback threads
    causing one of the following conditions:
    
    1- MQCTL calls fail with reason code MQRC_CALL_IN_PROGRESS
    (2219).
    2- Application hangs with the main and callback threads in
    permanent wait.
    

Problem conclusion

  • Asynchronous consume support modules have been fixed to use
    additional serialization and to do more detailed checks of state
    flags after the wait macros that control the interactions
    between the main and callback threads.
    100Y
    CSQBLB1
    CSQBLB1X
    CSQBLB16
    CSQBLB2
    CSQBLB2X
    CSQBLB26
    CSQBLB3
    CSQBLB3X
    CSQBLB36
    CSQBLB4X
    CSQBLB46
    CSQBLB5X
    CSQBLB56
    CSQBMCSM
    CSQBSRV
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM55740

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-01-11

  • Closed date

    2012-08-15

  • Last modified date

    2016-02-15

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

    PM54114

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

    UK81098

Modules/Macros

  • CSQBLB1  CSQBLB1X CSQBLB16 CSQBLB2  CSQBLB2X
    CSQBLB26 CSQBLB3  CSQBLB3X CSQBLB36 CSQBLB4X CSQBLB46 CSQBLB5X
    CSQBLB56 CSQBMCSM CSQBSRV
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R100 PSY UK81098

       UP12/09/20 P F209

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
15 February 2016