IBM Support

PI57890: 5C6-00C5105B,U=SYSOPR ,C=R3600.710.CFM LOC=CSQELPLM.CSQEDSS2 LEADING TO ABNORMAL QUEUE MANAGER TERMINATION REASON=00C510AB

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Abend 5C6-00C5105B in CSQEDSS2 occurs during structure recovery,
    leading to abnormal queue manager termination REASON=00C510AB
    DUMP TITLE=CSQ1,ABN=5C6-00C5105B,U=SYSOPR  ,C=R3600.710.CFM -CS
       562
    QEDSS2,M=CSQGFRCV,LOC=CSQELPLM.CSQEDSS2
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Various problems occur following admin  *
    *                      structure failure during queue manager  *
    *                      restart and subsequent application      *
    *                      structure failure.                      *
    *                      When the application structure is       *
    *                      recovered symptoms can include:         *
    *                       - missing messages on shared queues    *
    *                         using the structure                  *
    *                       - messages unexpectedly rolled back    *
    *                         to shared queues using the structure *
    *                      In addition, if messages are being      *
    *                      stored on the structure using SMDS the  *
    *                      following symptoms can also occur:      *
    *                       - 5C6-00C94522 in CSQIMGES when        *
    *                         getting messages from queues on the  *
    *                         the structure                        *
    *                       - 5C6-00C5105B in CSQEDSS2 during      *
    *                         recovery of the structure, followed  *
    *                         by abnormal queue manager            *
    *                         termination with REASON=00C510AB     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During queue manager startup, CSQERADM connected to the admin
    structure and attempted to determine if any recovery was
    required for this queue manager's state as held in the admin
    structure. While this processing was occurring the admin
    structure failed, causing CSQERADM to exit before initialising
    the eSTIM (structure interest map). When the structure was
    automatically recovered, CSQERAD2 rebuilt the queue managers
    state and wrote it into the admin structure, however because the
    eSTIM was not initialised, an incorrect eSTIM was written to the
    admin structure.
    When an application structure subsequently failed and was
    recovered by another queue manager, the queue manager performing
    the structure recovery read the eSTIM from the admin structure
    and used it to determine which queue manager's logs were
    required for the recovery. However the incorrect eSTIM for the
    initial queue manager meant that the logs for that queue
    manager were not read and logged operations from that queue
    manager that affected the structure (e.g. MQPUT and MQGET
    requests for persistent messages on shared queues held in that
    structure) were not replayed, leading to the contents of queues
    on the recovered structure being incorrect.
    In cases where SMDS is used, this incorrect state on the queues
    can lead to multiple messages attempting to reference the same
     SMDS blocks - this is detected when getting the messages
    or when the SMDS spacemap is rebuilt during recovery, leading
    to the 5C6 abends and subsequent queue manager termination.
    

Problem conclusion

  • CSQERADM is changed to always initialise the eSTIM, even if the
    admin structure has failed since CSQERADM connected to it.
    If the structure failure prevents CSQERADM writing the eSTIM to
    the structure, CSQERAD2 will write the initialised control block
    when the structure is available.
    
    MQSMDS/K
    100Y
    CSQERADM
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PI57890

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-02-24

  • Closed date

    2016-04-12

  • Last modified date

    2016-06-02

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

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

    UI36952

Modules/Macros

  • CSQERADM
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R100 PSY UI36952

       UP16/05/04 P F605 ¢

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:
02 June 2016