IBM Support

PI79678: WMQ IIB CONNECTION FAILS MQRC 2025 MQRC_MAX_CONNS_LIMIT_REACHED AFTER RRS FAILURE 17/05/23 PTF PECHANGE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • Change Team finds MQRC 2025 ( MQRC_MAX_CONNS_LIMIT_REACHED )
    is returned when IIB attempts to connect to MQ after an RRS
    failure. AMGSIDBC is being incorrected decremented for three
    AGNT control blocks obtained for indoubt URs returned by RRS.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 8 *
    *                 Release 0 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: After application of PTF UI23984, batch *
    *                      applications and IBM Integration Bus    *
    *                      may fail to connect to MQ with the      *
    *                      MQCONN returning MQRC=2025              *
    *                      (MQRC_MAX_CONNS_LIMIT_REACHED) if RRS   *
    *                      is restarted and there are indoubt URs  *
    *                      present.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    APAR PI30141 changed the incrementing and decrementing of the
    internal counts of agents and corrected checks on these values.
    However in this scenario, the count is decremented due to the
    RRS restart but when the AGNT is created for the application
    connecting, the count is not incremented. This results in the
    check for this value failing, resulting in the
    MQRC_MAX_CONNS_LIMIT_REACHED.
    

Problem conclusion

  • The logic during RRS restart has been changed, to not decrement
    the internal count in this case, which results in the bad MQRC.
    000Y
    CSQ3CT30
    CSQ3CT80
    CSQ3ID30
    CSQ3ID80
    CSQ3RRSR
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PI79678

  • Reported component name

    WMQ Z/OS 8

  • Reported component ID

    5655W9700

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-04-10

  • Closed date

    2017-06-14

  • Last modified date

    2017-06-14

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

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

    UI48026

Modules/Macros

  • CSQ3CT30 CSQ3CT80 CSQ3ID30 CSQ3ID80 CSQ3RRSR
    

Fix information

  • Fixed component name

    WMQ Z/OS 8

  • Fixed component ID

    5655W9700

Applicable component levels

  • R000 PSY

       UP



Document information

More support for: WebSphere MQ

Software version: 8.0

Reference #: PI79678

Modified date: 14 June 2017


Translate this page: