IC70698: WEBSPHERE MQ V7 AUTO DEFINED SENDER CHANNEL TO PARTIAL REPOSITORY MANAGERS ARE STARTED DURING A REFRESH CLUSTER

WebSphere MQ V7.0 Fix Pack 7.0.1.4
WebSphere MQ V7.0.1 for i5/OS Fix Pack 7.0.1.4

APAR status

• Closed as program error.

Error description

• When a refresh cluster is performed on a WebSphere MQ V7
  partial repository queue manager, auto defined sender channels
  to other queue managers other than full repositories might be
  started even though they were not running before the REFRESH
  CLUSTER command is issued. The local queue manager CLUSRCVR
  will be published using these channels as a result of the
  REFRESH CLUSTER command being issued.
  
  The problem however is not just specific to REFRESH CLUSTER.
  Actions such as restarting the queue manager or the internal
  maintenance cycles being executed which trigger a publication
  to take place, can cause these channels to start.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of WebSphere MQ V7 queue manager clusters using the
  REFRESH CLUSTER command.
  
  Platforms affected:
  All Distributed (iSeries, all Unix and Windows)
  ****************************************************************
  PROBLEM SUMMARY:
  The problem was caused by the addition of code in V7 to handle
  publication of local information for Publish Subscribe clusters
  as well as normal cluster configuration information to
  connected repository queue managers. This additional code
  incorrectly permitted the publication of local information to
  normal clusters based on a false positive check made
  specifically for publish subscribe clusters which included
  partial repository queue managers among the possible
  destination choices. As a result of mistakenly indicating the
  publication is to take place to the partial repository, the
  channel to it was started because it was not already in the
  running state.
  
  The problem can also arise due to the repository maintenance
  routines triggering a publication of the local cluster
  receiver channel.
  

Problem conclusion

• The problem was fixed by removing the code branch that permitted
  the publication to take place for standard clustering based on
  conditions specifically intended for publish subscribe clusters.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
                     v7.0
  Platform           Fix Pack 7.0.1.4
  --------           --------------------
  Windows            U200323
  AIX                U835793
  HP-UX (PA-RISC)    U836458
  HP-UX (Itanium)    U836463
  Solaris (SPARC)    U836459
  Solaris (x86-64)   U836465
  iSeries            tbc_p700_0_1_4
  Linux (x86)        U836460
  Linux (x86-64)     U836464
  Linux (zSeries)    U836461
  Linux (Power)      U836462
  
  The latest available maintenance can be obtained from
  'WebSphere MQ Recommended Fixes'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
  
  If the maintenance level is not yet available, information on
  its planned availability can be found in 'WebSphere MQ
  Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
  ---------------------------------------------------------------
  

Temporary fix

Comments

APAR Information

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

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

  PM21215

Fix information

• Fixed component name

  WMQ WINDOWS V7

• Fixed component ID

  5724H7220

Applicable component levels

• R700 PSY

     UP