IBM Support

PI49332: WMQ EXPIRY TASK CONTROL IS NOT RESTORING THE SASN TO THE QUEUE MANAGER'S ADDRESS SPACE ID(ASID).

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • WMQ EXPIRY TASK CONTROL not restoring the SASN to the
    queue manager address space id.
    .
    This problem occurs if CSQM1P1W is invoked to post an ECB for a
    get-waiter, and the get-waiter address space is terminating.
    
    .
    Additional keywords/symptoms:
    STOP QMGR hang hangs hung shut down shutdown termination
    .
    The 001.YSTPWK01 internal thread is waiting for an expiry task
    thread to end, but it had abended with ABEND058 reason 3C due
    to the SASN not being restored.
    ABENDS058 S058 058 S0058 0000003C RC3C RC0000003C
    ABENDS0D7 S0D7 0D7 S00D7 ABEND0D7
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 8 *
    *                 Release 0 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: A trigger monitor being used for a      *
    *                      queue with trigger first, terminating   *
    *                      during the put of a trigger message due *
    *                      to TriggerInterval expiring, may result *
    *                      in a S058 RC3C abend, followed by the   *
    *                      Queue Manager hanging during a normal   *
    *                      shutdown.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    One of the roles for the expiry processing's expiry tasks is to
    generate a TriggerMessage if applicable if the TriggerInterval
    has expired. However if there is a TriggerMonitor performing a
    MQGET with wait on the initiation queue for the trigger message
    to be put to and the application is terminating during the put ,
    it will attempt to switch to this address space number, however
    this is never restored. This results in a S058 RC3C abend in the
    expiry task.
    
    After the abend in the expiry task, Expiry_Task_count is
    not decremented. This results in the queue manager shutdown
    hanging, waiting for the count to be 0;
    

Problem conclusion

  • The processing for a put of the trigger message has been
    updated to switch back to the original address space after the
    processing in this case. This ensures the abend will not occur,
    resulting in the count being correctly decremented.
    000Y
    CSQM1P1W
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI49332

  • Reported component name

    WMQ Z/OS 8

  • Reported component ID

    5655W9700

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-09-24

  • Closed date

    2015-10-13

  • Last modified date

    2015-12-03

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

    PI45208

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

    UI31980

Modules/Macros

  • CSQM1P1W
    

Fix information

  • Fixed component name

    WMQ Z/OS 8

  • Fixed component ID

    5655W9700

Applicable component levels

  • R000 PSY UI31980

       UP15/11/11 P F511

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":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
03 December 2015