IBM Support

PI88885: 5C6-00D10341 issued from CSQJR103 during disaster recovery with striped active log dataset

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ABN=5C6-00D10341,U=SYSOPR,C=RLMC-CSQJLGR,
    M=CSQJRE01,LOC=CSQJL002.CSQJR103
     When using striped active logs, it is possible that the rewrite
    of a CI does not get mirrored, although the write of the next CI
    is mirrored (same situation as DB2 APAR PI10353/PI15425),
    resulting in the 5C6-00D10341 abend issued by CSQJR103.
    

Local fix

  • Use CSQ1LOGP to determine if the log copy 2 dataset ends at a
    higher RBA than the corresponding log copy 1 dataset. If so,
    copy the log copy 2 dataset over the log copy 1 dataset.
    
    An indication that a log dataset is missing the rewrite of a CI
    is given by the following message towards the end of the
    CSQ1LOGP output:
    
    CSQ1216E LOG READ ERROR, RETCODE=00000004 REASON CODE=00D10063,
             RBA=xxxxxxxxxxxx
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Abend 5C6-00D10341 is issued by         *
    *                      CSQJR103 during queue manager restart,  *
    *                      or when reading a peer queue managers   *
    *                      logs, following abnormal queue manager  *
    *                      termination, or when using a mirrored   *
    *                      copy of the logs.                       *
    *                      The abend is followed by abnormal       *
    *                      queue manager termination 6C6.          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During queue manager startup, log replay detected the
    continuation of a spanned log record without the expected
    initial segment, leading to the queue manager abending
    5C6-00D10341, followed by abnormal queue manager termination 6C6
    with REASON=00D96001.
    
    This situation can occur following abnormal queue manager
    termination, or when starting the queue manager using mirrored
    logs, if the abnormal termination or mirroring operation
    occurred:
    - while writing the last CI to the logs, if the IO operation
      has completed for logcopy2, but not for logcopy1.
    - while writing multiple CI's to the logs, if the logs are
      striped.
    
    Similarly, when reading the logs of a peer queue manager that
    are missing the rewrite of a CI (for example, during peer admin
    rebuild, or groupur processing for an inactive queue manager)
    CSQJR103 abends and the queue manager reading the logs
    terminates.
    

Problem conclusion

  • CSQJW009 has been changed to detect when the last CI contains
    more data in one logcopy than is contained in the other logcopy,
    and to truncate the shorter log prior to the last CI.
    
    CSQJW009 is also changed to perform additional validation of
    striped active logs when locating the end RBA of the logs.
    If this results in a difference between the end RBA of logcopy1
    and logcopy2, the shorter log, containing the missed CI, is
    truncated to ensure the CI is read from the other logcopy.
    
    CSQJR103 is changed to handle a missed CI when reading the
    active logs for a failed peer.
    100Y
    CSQJR103
    CSQJW009
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PI88885

  • 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

    2017-10-16

  • Closed date

    2017-12-20

  • Last modified date

    2018-02-01

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

    PI77705

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

    UI52838

Modules/Macros

  • CSQJR103 CSQJW009
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R100 PSY UI52838

       UP18/01/06 P F801 ¢

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:
01 February 2018