IBM Support

PI24838: WMQ 710: SUSPEND QMGR CLUSTER MODE(FORCE) COMMAND LEADS TO CSQX053E AND CSQX448E, SNAPDUMP IS CREATED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If the SUSPEND QMGR CLUSTER command with MODE(FORCE) is done
    twice for the same qmgr and cluster, the repository manager is
    stopped and a snapdump is created the following messages are
    written into the chinit joblog:
    
    
     +CSQX053E CSQXFFST Error information recorded in CSQSNAP data
                        set
     +CSQX448E CSQXREPO Repository manager stopping because of
                        errors.  Restart in 600 seconds
     +CSQX449I CSQXREPO Repository manager restarted
    
    CSQSNAP  information:
    
    *                        X...XFFS*
    *rrmRepository...................*
    *MOVR.........B..X...XINS........*
    
    *        ...üFailing message.....*
    *...........2....................*
    *....................qmgr        *
    *                                *
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Issuing a SUSPEND QMGR CLUSTER command  *
    *                      with MODE(FORCE) specified twice        *
    *                      without resuming the queue manager's    *
    *                      membership to the cluster results in    *
    *                      errors with messages CSQX053E and       *
    *                      CSQX448E.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During processing of SUSPEND QMGR CLUSTER MODE(FORCE), cluster
    receiver is stopped. When a subsequent suspend command is
    processed, without the membership being reinstated, the
    processing attempts to stop this channel again. This fails as
    the channel is already in a non-active state with
    rrcW_CHANNEL_NOT_ACTIVE, this is not handled, resulting in the
    produced errors and the repository manager stopping.
    

Problem conclusion

  • Suspend processing has been updated to correctly handle
    rrcW_CHANNEL_NOT_ACTIVE when using MODE(FORCE) parameter.
    100Y
    CSQXRRMF
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PI24838

  • 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

    2014-09-02

  • Closed date

    2014-09-30

  • Last modified date

    2014-11-04

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

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

    IV64755 UI21862 PI26687

Modules/Macros

  • CSQXRRMF
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R100 PSY UI21862

       UP14/10/17 P F410 Ž

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:
04 November 2014