Fixes are available
APAR status
Closed as program error.
Error description
A WebSphere MQ .Net application sends a request message to a z/OS queue manager and then tries to get the reply message but gets reason code 2033 (MQRC_NO_MSG_AVAILABLE). This occurs because the request message is not committed on the SYSTEM.COMMAND.INPUT queue on the z/OS queue manager. This only occurs when the .NET client sends messages to a z/OS queue manager. The problem does not occur when sending messages to other platforms. The same issue affects message reads by the .Net application. By default, message reads from queues at a queue manager hosted on z/OS, are performed within syncpoint. ADDITIONAL KEYWORDS: dot net dotnet programmable command format MQPMO_SYNCPOINT MQPMO_NO_SYNCPOINT MQGMO_SYNCPOINT MQGMO_NO_SYNCPOINT host mainframe Windows reply to queue replytoqueue
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users running .Net applications that do not explicitly specify syncpoint options when sending or receiving messages of any type or format. Platforms affected: Windows **************************************************************** PROBLEM SUMMARY: The problem is caused because the WebSphere MQ .Net interfaces did not take into account that the default syncpoint behaviour on z/OS queue managers is different from that on distributed platforms. This problem was addressed originally in APAR IC56327, however a change was made in WebSphere MQ version 7.0.1.0 such that the MQPUT and MQGET functions are now implemented by class MQDestination,where the same error was repeated, rather than MQQueue. Thus the code changed by IC56327 never gets executed at 7.0.1.0.
Problem conclusion
The MQDestination class has been corrected to explicitly specify the syncpoint options to not use syncpoint, where the application has left the option to default. | MDVREGR 7.0-WS-MQ-Windows-RP0001 | | MDVREGR 7.0.1-WS-MQ-Windows-FP0001 | --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v7.0 Platform Fix Pack 7.0.1.2 -------- -------------------- Windows U200316 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
IC64683
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
2009-11-19
Closed date
2009-11-30
Last modified date
2010-04-08
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