IBM Support

PI21137: WMQ V7 ON Z/OS: ERROR CSQX526E (MESSAGE SEQUENCE ERROR) ON A SHARED RECEIVER CHANNEL DURING DISASTER RECOVERY TEST

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In the test of disaster recovery cust performed the following
    :
          .
    1/ stop of all qmgrs of the MQ plex in all LPARs
    2/ start of one MSTR on the recovery site at
    3/ perform the recover CFSTRUCT of the structures which comprise
       the structure containing the SYSTEM.QSG.CHANNEL.SYNCQ
    4/ start of the CHIN
    5/ error CSQX526E on a shared receiver channel
    .
    The problem will occur if a queue manager is removed from
    the queue-sharing group and then added back prior to recovering
    the application structure.
    
    
    After applying fix PI11896, the RECOVER CFSTRUCT command or auto
    recovery can generate abend 0C4 in CSQERRPB followed by abend
    5C6-00E20014 in CSQSGMN that causes the queue manager to
    terminate with reason 00C510AB.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ Version 7          *
    *                 Release 0 Modification 1 and                 *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: When using CSQ5PQSG FORCE QMGR command  *
    *                      to remove a queue manager, it does not  *
    *                      issue any warnings when the queue       *
    *                      manager logs or SMDS are required to    *
    *                      recover CF structures in case of        *
    *                      failure.                                *
    *                                                              *
    *                      Also the RECOVER CFSTRUCT command or    *
    *                      auto recovery completes successfully    *
    *                      after it has only partially recovered   *
    *                      the data without issuing any error or   *
    *                      warning message when a queue manager    *
    *                      has been force removed as indicated     *
    *                      above.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    CSQ5PQSG REMOVE QMGR command checks if the logs or the SMDS
    datasets are required to recover structures and prevents the
    queue manager from being removed from the QSG after issuing
    error messages CSQE556E and/or CSQE558E. The CSQ5PQSG FORCE QMGR
    does not check and it does not issue any warning messages.
    
    The RECOVER CFSTRUCT command or the auto recover skip any logs
    required to recover a structure without issuing a warning when
    the logs belong to a queue manager that has either been force
    removed, or has been force removed and added back into the QSG
    and hasn't been restarted. The recover command seems to complete
    normally but the data has been partially recovered.
    

Problem conclusion

  • CSQ5PQSG FORCE QMGR command will issue new warning messages
    CSQU586E and/or CSQU587E when the queue manager logs or SMDS
    are required to recover a CF structure.
    
    RECOVER CFSTRUCT or auto recovery will fail if there are logs
    required to recover the structure but they cannot be accessed
    due to the queue manager having been FORCE removed from the QSG.
    New error messages CSQE161E and CSQE112E are issued to report
    this condition.
    
    ========= DOC Changes for V710 Knowledge Center ===============
    Add the following page to the Knowledge Center for MQ V710:
    
    WebSphere MQ
    > Reference
        > Messages
           > WebSphere MQ for z/OS messages,...
            >  Messages for WebSphere MQ for z/OS
                > Coupling Facility manager messages (CSQE...)
    
    CSQE161E: csect-name QSG state is inconsistent,
    no XCF data for queue manager qmgr-number
    
    Explanation
    
    A RECOVER CFSTRUCT command or automatic structure recovery was
    unable to read all the log data required for recovery as there
    was no XCF data for one of the queue managers in the QSG.
    qmgr_number is the number of the affected queue manager in the
    MQ DB2 tables.
    
    System action
    
    Processing of the command is terminated.
    Automatic recovery of the structure will not be attempted.
    
    System programmer response
    
    If the queue manager with number qmgr-number in the MQ DB2
    tables has been force removed from the QSG and added back into
    the QSG, start the queue manager and issue the RECOVER CFSTRUCT
    command again.
    
    Otherwise, reset the structure to an empty state by issuing the
    RECOVER CFSTRUCT TYPE(PURGE) command.
    
    ==============================================================
    
    Add the following page to the Knowledge Center for MQ V710:
    
    WebSphere MQ
    > Reference
        > Messages
           > WebSphere MQ for z/OS messages,...
            >  Messages for WebSphere MQ for z/OS
                > Utilities messages (CSQU...)
    
    CSQU586I: QMGR qmgr-name entry being removed from QSG qsg-name,
    needed for structure struc-name backup
    
    Explanation
    
    The queue manager named by qmgr-name is being force removed from
    the queue-sharing group named by qsg-name and it has information
    about backups for structure struc-name. (The value shown for
    struc-name is the 12-character name as used by WebSphere MQ, not
    the external name used by z/OS which includes the queue-sharing
    group name.)
    
    If the queue manager qmgr-name is added back to the
    queue-sharing group it will cause an inconsistent state that
    could prevent structure struct-name from being recovered should
    it fail before a structure backup is taken.
    
    If the queue manager is needed for more than one structure,
    this message will be issued for each one.
    
    System action
    
    Queue manager is removed from queue-sharing group and the
    utility program ends with return code 4.
    
    System programmer response
    
    If CF structure struc-name is usable, take a backup of CF
    structure struc-name as soon as possible using another queue
    manager in the queue-sharing group.
    
    Otherwise, if the queue manager qmgr-name is added back to the
    queue-sharing group it should be restarted before recovering
    structure struc-name.
    
    ==============================================================
    
    Add the following page to the Knowledge Center for MQ V710:
    
    WebSphere MQ
    > Reference
        > Messages
           > WebSphere MQ for z/OS messages,...
            >  Messages for WebSphere MQ for z/OS
                > Utilities messages (CSQU...)
    
    CSQU587I: QMGR qmgr-name entry being removed from QSG qsg-name,
    SMDS for structure struc-name is not empty
    
    Explanation
    
    The queue manager named by qmgr-name is being removed from the
    queue-sharing group named by qsg-name while it owns a shared
    message data set for structure struc-name which is not marked as
    empty, so it may still contain current message data. (The value
    shown for struc-name is the 12-character name as used by
    WebSphere MQ, not the external name used by z/OS which includes
    the queue-sharing group name.)
    
    System action
    
    Queue manager is removed from queue-sharing group and the
    utility program ends with return code 4.
    
    Messages on the SMDS for queue manager qmgr-name will remain
    accessible as long as the SMDS is retained.
    
    ========= DOC Changes for V701 Knowledge Center ===============
    Add the following page to the Knowledge Center for MQ V701
    
    WebSphere MQ
    > z/OS Messages and Codes
        > Messages
            > Coupling Facility manager messages (CSQE...)
    
    CSQE112E
        csect-name Unable to recover structure struct-name,
     failed to read required logs.
    
    Explanation
    
        A RECOVER CFSTRUCT command was unable to read the logs
     required to recover a structure.
    
    System action
    
        Processing of the command is terminated.
    
    System programmer response
    
    Check that the logs containing the RBA range indicated in
    message CSQE130I are available, and reissue the command.
    
    Check for any prior errors or abends reporting problems using
    the logs. Issue RECOVER CFSTRUCT(struct-name) to retry structure
    recovery.
    
    ==============================================================
    Add the following page to the Knowledge Center for MQ V701
    
    WebSphere MQ
    > z/OS Messages and Codes
        > Messages
            > Coupling Facility manager messages (CSQE...)
    
    CSQE161E: csect-name QSG state is inconsistent,
    no XCF data for queue manager qmgr-number
    
    Explanation
    
    A RECOVER CFSTRUCT command or automatic structure recovery was
    unable to read all the log data required for recovery as there
    was no XCF data for one of the queue managers in the QSG.
    qmgr_number is the number of the affected queue manager in the
    MQ DB2 tables.
    
    System action
    
    Processing of the command is terminated.
    
    System programmer response
    
    If the queue manager with number qmgr-number in the MQ DB2
    tables has been force removed from the QSG and added back into
    the QSG, start the queue manager and issue the RECOVER CFSTRUCT
    command again.
    
    Otherwise, reset the structure to an empty state by issuing the
    RECOVER CFSTRUCT TYPE(PURGE) command.
    
    ==============================================================
    
    Add the following page to the Knowledge Center for MQ V701:
    
    WebSphere MQ
    > z/OS Messages and Codes
        > Messages
            > Utilities messages (CSQU...)
    
    CSQU586I: QMGR qmgr-name entry being removed from QSG qsg-name,
    needed for structure struc-name backup
    
    Explanation
    
    The queue manager named by qmgr-name is being force removed from
    the queue-sharing group named by qsg-name and it has information
    about backups for structure struc-name. (The value shown for
    struc-name is the 12-character name as used by WebSphere MQ, not
    the external name used by z/OS which includes the queue-sharing
    group name.)
    
    If the queue manager is needed for more than one structure,
    this message will be issued for each one.
    
    System action
    
    Queue manager is removed from queue-sharing group and the
    utility program ends with return code 4.
    
    System programmer response
    
    If CF structure struc-name is usable, take a backup of CF
    structure struc-name as soon as possible using another queue
    manager in the queue-sharing group.
    
    Otherwise, if the queue manager qmgr-name is added back to the
    queue-sharing group it should be restarted before recovering
    structure struc-name.
    
    ==============================================================
    010Y
    011Y
    012Y
    013Y
    014Y
    100Y
    101Y
    102Y
    103Y
    104Y
    105Y
    CSQERCFT
    CSQERCF1
    CSQERRPB
    CSQFEDIC
    CSQFEDIE
    CSQFEDIF
    CSQFEDIK
    CSQFEDIU
    CSQFMTXC
    CSQFMTXE
    CSQFMTXF
    CSQFMTXK
    CSQFMTXU
    CSQFSTXC
    CSQFSTXE
    CSQFSTXF
    CSQFSTXK
    CSQFSTXU
    CSQ5PQSG
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI21137

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    018

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-07-02

  • Closed date

    2014-10-21

  • Last modified date

    2015-02-03

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

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

    PI27603 UI22354 UI22355 UI22356 UI22357 UI22358 UI22359 UI22360
    UI22362 UI22363 UI22364 UI22365

Modules/Macros

  • CSQERCFT CSQERCF1 CSQERRPB CSQFEDIC CSQFEDIE CSQFEDIF CSQFEDIK
    CSQFEDIU CSQFMTXC CSQFMTXE CSQFMTXF CSQFMTXK CSQFMTXU CSQFSTXC
    CSQFSTXE CSQFSTXF CSQFSTXK CSQFSTXU CSQ5PQSG
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R010 PSY UI22354

       UP15/01/18 P F501

  • R011 PSY UI22355

       UP15/01/18 P F501

  • R012 PSY UI22356

       UP15/01/18 P F501

  • R013 PSY UI22357

       UP15/01/18 P F501

  • R014 PSY UI22358

       UP15/01/18 P F501

  • R100 PSY UI22359

       UP15/01/18 P F501

  • R101 PSY UI22360

       UP15/01/18 P F501

  • R102 PSY UI22362

       UP15/01/18 P F501

  • R103 PSY UI22363

       UP15/01/18 P F501

  • R104 PSY UI22364

       UP15/01/18 P F501

  • R105 PSY UI22365

       UP15/01/18 P F501

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.0.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 February 2015