IT08625: WEBSPHERE MQ 8.0 USING THE MQSC COMMAND DISPLAY CHSTATUS FAIL WITH AN ERROR AMQ9522, IF ISOLATED BINDINGS IS ENABLED.

APAR status

• Closed as program error.

Error description

• Working with WebSphere MQ Version 8.0.0.2, the MQSC
  command DISPLAY CHSTATUS fails with an error like the below, if
  isolated bindings is enabled:
  .
  AMQ9522: Error accessing the status table
  .
  See the following example, which is showing an extract of a MQ
  trace of process runmqsc:
  ----------------------------------------------------------------
  09:08:59.810422 6685238.1 CONN:1400006 -------}
   xcsReleaseThreadMutexSem rc=OK FunctionTime=7
  09:08:59.810426 6685238.1 CONN:1400006 ------}! xcsInitialize
   rc=xecI_S_FAIL FunctionTime=114
  09:08:59.810430 6685238.1 CONN:1400006 ------{ rrxError
  09:08:59.810436 6685238.1 CONN:1400006 RetCode = 20009522,
   rc1 = 1073766404, rc2 = 0, Comment1 = '', Comment2 = '',
   Comment3= '', File= '/build/slot1/p800_P/src/lib/remote/
   amqrcsta.c', Line= '179'
  09:08:59.810440 6685238.1 CONN:1400006 ------}! rrxError
   rc=rrcE_STATUS_TABLE_ERROR FunctionTime=10
  09:08:59.810444 6685238.1 CONN:1400006 -----}!
   rrxAccessStatusTable rc=rrcE_STATUS_TABLE_ERROR
   FunctionTime=154
  09:08:59.810449 6685238.1 CONN:1400006 -----{
   pcmMapChannelReason
  09:08:59.810465 6685238.1 CONN:1400006 -----}!
   pcmMapChannelReason rc=MQRCCF_CHANNEL_TABLE_ERROR
   FunctionTime=16
  09:08:59.810470 6685238.1 CONN:1400006 -----{
   pcmSendNonDataReplyMsg
  09:08:59.810474 6685238.1 CONN:1400006 ------{ pcmSendReplyMsg
  09:08:59.810479 6685238.1 CONN:1400006 -------{ uscReply
  09:08:59.810483 6685238.1 CONN:1400006 --------{
   uscConvertBadReturn
  09:08:59.810488 6685238.1 CONN:1400006 uscMapMessage
   Command(42) Reason(3062) RetCode(0x20009522)
  ----------------------------------------------------------------
  

Local fix

• Disable ISOATED bindings.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users using runmqsc to connect to queue managers with ISOLATED
  bindings enabled.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  This problem occurred because runmqsc was not able to connect to
  the shared memory set allocated for the channel status table.
  

Problem conclusion

• runmqsc has been modified so that runmqsc can connect to the
  shared memory set allocated for the channel status table.
  
  ---------------------------------------------------------------
  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