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

Obtain the fix for this APAR.

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 8 *
  *                 Release 0 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.
  

Temporary fix

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

Comments

APAR Information

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

  PI24838

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

  UI22898

Modules/Macros

• CSQXRRMF
  

Fix information

• Fixed component name

  WMQ Z/OS 8

• Fixed component ID

  5655W9700

Applicable component levels

• R000 PSY UI22898

     UP15/01/29 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.