IT09196: IBM MQ V8 STOP CHANNEL COMMAND DOES NOT DISABLE A SVRCONN CHANNEL IF IT WAS NOT ACTIVE WHEN THE COMMAND WAS RUN

APAR status

• Closed as program error.

Error description

• The command STOP CHANNEL(chlname) STATUS(STOPPED) disables a
  channel from running until it is re-enabled using the command
  START CHANNEL(chlname).
  
  In IBM MQ V8.0.0.2, this works for SVRCONN channels only if the
  SVRCONN
  was running at the time the command was issued. Then any attempt
  to connect using that SVRCONN channel fails with reason code
  MQRC_CHANNEL_NOT_AVAILABLE (2537) as intended.
  
  However, if the SVRCONN channel was not running at the time of
  the STOP CHANNEL(chlname) STATUS(STOPPED) command, it is not
  disabled and client applications are able to connect over it.
  This is
  different from WebSphere MQ V8.0.0.1 and prior releases.
  

Local fix

• STOP CHANNEL(chlname) STATUS(STOPPED) MODE(TERMINATE) will
  disable the channel, as will running the original STOP CHANNEL
  command twice in a row.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users who try to stop channels that have not been started may be
  affected by this problem
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  An internal status flag was not being set correctly when the
  STOP CHANNEL command was issued. This caused the queue manager
  to fail to check whether the channel was disabled when a client
  connected and incorrectly allowed the channel to start.
  

Problem conclusion

• The internal status flag was correctly set to disabled when the
  STOP CHANNEL command was issued. This meant that the queue
  manager discovered that the channel was disabled and did not
  allow the channel to start.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v8.0       8.0.0.4
  
  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:

Fix information

• Fixed component name

  WMQ BASE MULTIP

• Fixed component ID

  5724H7251

Applicable component levels

• R800 PSY

     UP