A fix is available
APAR status
Closed as program error.
Error description
lpiSPINotify_BREAKCONN was set even if they use SHARECNV(0) client channel. There is a logic error that is causing us to incorrectly enter the wrong section of code and perform an lpiSPINotify with lpiSPINotify_BREAKCONN even when we should not be doing so. This means that the ACESTOP flag is also incorrectly set on. The incorrect logic performs a bitwise OR check with "|" rather than a boolean OR check with "||" and drives the lpiSPINotify call when it should not. . Additional symptoms and keywords: 2321 0x00000911 MQRC_PARAMETER_MISSING MQ clients using FAP (protocol) level 9 or earlier - MQ V700 or earlier clients - will always fail to connect Also: looking in the CHINIT logs; many CSQX511I (channel started), and CSQX512I (channel no longer active) messages could be seen. - High CPU in CHIN
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM MQ for z/OS Version 9 * * Release 0 Modification 0 and Version 9 * * Release 1 Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: Older versions of the client connecting * * to a V910 queue manager may receive an * * MQRC 2321 (MQRC_PARAMETER_MISSING). * * Older versions of the client connected * * to a V900 queue manager may find their * * connection terminated when a different * * client is connected. * **************************************************************** When trying to connect an older version of the client to a v910 queue manager the client may receive a return code of 2321 (MQRC_PARAMETER_MISSING) which results in the client failing to connect. When there are older versions of the client connected to a v900 queue manager, the connection may get incorrectly terminated when a different client connects.
Problem conclusion
Older versions of the client will now be able to connect into v910 queue managers. Older versions of the client connected to a v900 queue manager will not have their connection terminated when a different client connects.
Temporary fix
Comments
APAR Information
APAR number
PH11610
Reported component name
IBM MQ Z/OS V9
Reported component ID
5655MQ900
Reported release
000
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-04-30
Closed date
2019-06-26
Last modified date
2019-08-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI63879 UI63880
Modules/Macros
CSQXRCSV
Fix information
Fixed component name
IBM MQ Z/OS V9
Fixed component ID
5655MQ900
Applicable component levels
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":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
01 August 2019