IBM Support

PH06223: IMS DEPENDENT REGIONS HANG AFTER MQ MEMTERM'ED S40D DUE TO S052 RETURN CODE 212 RC212 END OF MEMORY PROCESSING.

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • MQ applications hang after MQ queue manager MEMTERM'ed
    with S40D. This is due to an S052 RC212 abend in end-of-memory
    processing for the queue-maanger address space, due to CSQVATRM
    passing an invalid LX value to LXFRE. This abend means that the
    rest of queue-manager end-of-memory processing, which includes
    abending any application tasks (e.g. a TCB in an IMS dependent
    region), does not take place, hence the hang.
    
    Other symptoms can include CSQVATRM looping during recovery
    processing, causing a leak of SP 231 K7 ECSA storage.
    AD'DL SYMPTOM
    CSQVATRM DEPLETES BTL CSA IF EXECUTED IN ASID 1 ( CSQYGRA1 )
    

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: Abend S052 occurs when the queue        *
    *                      manager is terminated at EOM, leading   *
    *                      to unpredictable behaviour, that can    *
    *                      include applications connected to the   *
    *                      queue manager hanging.                  *
    ****************************************************************
    When the queue manager is terminated at end of memory, CSQVATRM
    is called to clean up queue manager resources, including freeing
    any non-system LX's established by the queue manager.
    However, as CSQVATRM is running in asid 1 in this situation,
    rather than the qmgr asid, the LXFRE request abends S052.
    A subsequent error in the recovery processing for CSQVATRM
    prevents the recovery processing completing, causing the clean
    up to be terminated prematurely.
    Depending on the current state of connections to the qmgr, and
    internal tasks, the skipped processing can lead to further
    errors, such as applications (e.g. batch, IMS, CICS) hanging.
    

Problem conclusion

  • CSQVATRM is changed to only attempt to free the LX's if running
    in the qmgr asid.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH06223

  • Reported component name

    IBM MQ Z/OS V9

  • Reported component ID

    5655MQ900

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-12-06

  • Closed date

    2019-01-14

  • Last modified date

    2019-04-10

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

    PI83520

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

    UI60649 UI60650

Modules/Macros

  • CSQVATRM
    

Fix information

  • Fixed component name

    IBM MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R000 PSY UI60649

       UP19/01/26 P F901 ¢

  • R100 PSY UI60650

       UP19/01/26 P F901 ¢

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.



Document information

More support for: IBM MQ

Software version: 9.0

Reference #: PH06223

Modified date: 10 April 2019