A fix is available
APAR status
Closed as program error.
Error description
The customer has started rolling out MQ Client 8.0.0.2 to their Unix servers. The Clients connect to a WebSphere MQ for z/OS V8 QMGR. On the weekend when they take the Mainframe down for maintenance, the Clients generate FDCs as though they are having issues with recognizing the Remote QMGR shutting down. The following to probe IDs in the 2 FDCs for a particular server that always generate FDCs. . Probe Id :- XC076010 Application Name :- MQM Component :- xcsGetMessage . Probe Id :- CO398008 Application Name :- MQM Component :- cciFindConv . The change team has taken a look at the dump from the z/OS CHIN and can see the cause of the FDC issues by cciFindConv on the client side. When the CHIN receives the rfpSAT_END_CONV response from the client it issues an MQCTL which fails with 2202, MQRC_CONNECTION_QUIESCING, and rstSendNotification is again invoked and sends the rfpNC_STREAMING_FAILURE noification once again.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere MQ Version 8 * * Release 0 Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: A Client application connected to a V8 * * z/OS queue manager using SVRCONN * * channels configured with SHARECNV>0, * * can generate FDC files in the client * * side when the CHIN is shutdown while * * the application is running. * * * * FDC reports error rrcE_PROTOCOL_ERROR, * * probe Id CO398008 and error message * * AMQ9504. * **************************************************************** * RECOMMENDATION: * **************************************************************** When the CHIN is shutdown while the client application is executing MQ API calls. These API calls fail with MQRC 2202 (MQRC_CONNECTION_QUIESCING) or MQRC 2009 (MQRC_CONNECTION_BROKEN). The CHIN should notify the client of these failures but if the failure occurs after the channel conversation has ended the CHIN still sends these (unexpected) notifications causing the protocol error reported by the FDC files.
Problem conclusion
The CHIN has been changed to avoid sending notifications to a client after the channel conversations have been ended. 000Y CMQXRSTF
Temporary fix
Comments
APAR Information
APAR number
PI50384
Reported component name
WMQ Z/OS 8
Reported component ID
5655W9700
Reported release
000
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-10-12
Closed date
2016-01-20
Last modified date
2016-03-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI34590
Modules/Macros
CMQXRSTF
Fix information
Fixed component name
WMQ Z/OS 8
Fixed component ID
5655W9700
Applicable component levels
R000 PSY UI34590
UP16/02/03 P F602
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
02 March 2016