Fixes are available
APAR status
Closed as program error.
Error description
The XMS .NET application connects to a WMQ queue manager in unmanaged mode by setting queue manager name as "*". The create session call tries to connect to a different queue manager, which results in a 2058 (MQRC_Q_MGR_NAME_ERROR) for create session and MQRC 2018 (MQRC_HCONN_ERROR) at create requester. The following exceptions can be seen in the XMS.NET trace: 00000001 d UOW= source= org=IBM prod=WebSphere component= Message Service Client for .NET thread=?1 : 0? MQException CompCode: 2 Reason: 2058 00000001 X UOW=source=IBM.XMS.Client.WMQ.WmqMessageProducer org=IBM prod=WebSphere component=Message Service Client for .NET thread=?1 : 0?IBM.XMS.IllegalStateException: Failed to open MQ queue Sample.Request.XMS attempted to perform an MQOPEN, but WebSphere MQ reported an error. Use the linked exception to determine the cause of this error. Check that the specified queue and queue manager are defined correctly. Linked Exception : CompCode: 2, Reason: 2018
Local fix
Problem summary
**************************************************************** USERS AFFECTED: XMS .NET 2.0 users connecting to WMQ in CCDT mode. Platforms affected: Windows **************************************************************** PROBLEM SUMMARY: XMS .NET client issues a connect call to the server, but the channel name used for this call differs than the one used for the create connection call. Which results in create session trying to connect to different queue manager. So the successive create objects call goes to different queue manager which results in the 2018 and 2058 exceptions.
Problem conclusion
NMQI code is modified such that the channel details are given back through the connect options along with additional validation. So that the XMS .NET client code, can use the same channel name for the create connection and create session call. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v7.0 Platform Fix Pack 7.0.1.9 -------- -------------------- Windows U200337 v7.1 Platform Fix Pack 7.1.0.2 -------- -------------------- Windows 7.1.0.2 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 number
IC82032
Reported component name
WMQ WINDOWS V7
Reported component ID
5724H7220
Reported release
701
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-03-14
Closed date
2012-04-18
Last modified date
2012-04-18
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
R701 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023