IT10380: ALTER CHANNEL COMMAND FAILS ON A VALID CLUSTER SENDER OR RECEIVER CHANNEL

APAR status

• Closed as program error.

Error description

• Alter channel command on an valid channel fails without
  reporting
  any error message. The issue happens if an alter or display
  channel command
  is issued on a non existing channel first  followed by an
  existing
  channel. For example:
  
  ALTER CHANNLE (SYSTEM.DEF.CLUSSDR1) CHLTYPE(CLUSSDR) BATCHLIM(0)
   AMQ8147: WebSphere MQ object SYSTEM.DEF.CLUSSDR1 not found.
  
  First the alter channel command on the non existing channel
  'SYSTEM.DEF.CLUSSDR1'  returns AMQ8147
  
  After that an alter channel command is issued for a valid
  cluster receiver
  channel 'SYSTEM.DEF.CLUSSDR' to change the BATCHLIM attribute,
  however it fails without any error message.
  
  ALTER CHANNLE (SYSTEM.DEF.CLUSSDR) CHLTYPE(CLUSSDR) BATCHLIM(0)
  (No message reported on success or failure of alter command)
  
  runmqsc trace reports MQRCCF_COMMAND_FAILED message:-
  8584.1           :       (03)----{  uscRunCommand
  8584.1           :       Command to be executed: alter channel
  (SYSTEM.DEF.CLUSSDR1) CHLTYPE(CLUSSDR) BATCHLIM(0)
  8584.1           :       (04)-----{  uscRunIT
  ..
  0001D5DA 11:39:23.375320   8584.1       CONN:971532 (05)------}!
  pcmChangeChannel (rc=MQRCCF_COMMAND_FAILED)
  ..
  8584.1           :       (04)-----}! uscRunIT
  (rc=MQRCCF_COMMAND_FAILED)
  8584.1           :       (03)----}! uscRunCommand
  (rc=Unknown(4))
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  MQ Administrators that run alter channel command against cluster
  sender or cluster receiver channels
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The issue happened only if an alter or display channel command
  was issued on a non-existent cluster channel definition first,
  followed by a cluster channel which did exist.
  
  The first alter or display channel command set an internal MQ
  flag to indicate object was not found. The second alter channel
  command failed to reset that flag, which caused the second alter
  channel to fail.
  

Problem conclusion

• MQ code has been modified such that the internal flags are reset
  appropriately in this scenario.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.1       7.1.0.8
  v7.5       7.5.0.6
  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 WINDOWS V7

• Fixed component ID

  5724H7220

Applicable component levels

• R710 PSY

     UP