IT26868: MQ client fails to connect to queue manager using the second IP address in CONNAME with client using CCDT

APAR status

• Closed as program error.

Error description

• When a Client Channel Definition Table (CCDT) is used to provide
  client connectivity for an MQ client to queue manager, the
  CONNAME in the CCDT has 2 addresses for fail over purposes. The
  MQ client can fail to connect to the Queue Manager using 2nd IP
  address in CONNAME using CCDT.
  
  The MQ client error log only shows an error attempting to
  connect to the first address in CONNAME, so it appears to not be
  trying to connect to the 2nd address.
  
  MQ client error log shows:
  AMQ9202E: Remote host '[first address of CCDT]' not available,
  retry later.
  
  A Failure Data Capture (FDC) record will be generated with the
  following information:
  
    Vendor          :- IBM
    OS Version      :- Microsoft Windows NT 6.2.9200.0
    Command Line    :- SimpleQueueBrowser ....
    Exception       :- System.Exception
    Source          :- Instance :
  IBM.XMS.Client.WMQ.WmqSessionParent
  Connection :  Wmqconnection@115000AcknowledgeMode :
  AutoAcknowledgeAsyncPutCounter :
  IBM.XMS.Client.WMQ.WmqSession+AsyncPutCounterdidRecovAsyncPut :
  Falsehelper :
  IBM.XMS.Client.WMQ.WmqConsumerOwnerShadowinSyncpoint :
  FalseQueueManagerName : QM1::Close()
    Caller          :- XN008003
    Assembly        :- mscorlib, Version=2.0.0.0, Culture=neutral,
  PublicKeyToken=xyz12344321
    Loaded From     :- Global Assembly Cache
    Location        :-
  C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorlib.dll
  
  This issue does not affect the Java client.
  
  Issue is only observed when the Queue Manager at the first
  address is not available but the QM at 2nd address is.
  
  If the CONNAME is altered to reverse the order of the addresses,
  the first address (which failed before as the second address)
  functions correctly.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users using CCDT with multiple connection names and adding the
  MQCNO_USE_CD_SELECTION option in the connection options of
  MQCONNX.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  A coding error in MQ client caused the connection to fail when
  multiple connection names were provided in the CCDT along with
  MQCNO_USE_CD_SELECTION option being used in connection options
  of MQCONNX.
  

Problem conclusion

• MQ client code has been modified such that the connection to
  queue manager succeeds when multiple connection names are
  provided in the CCDT.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.1 CD    9.1.3
  v9.1 LTS   9.1.0.3
  
  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

  IBM MQ BASE M/P

• Fixed component ID

  5724H7261

Applicable component levels

• R905 PSY

     UP