APAR status
Closed as program error.
Error description
An MQ client channel connection to the queue manager using SHARECNV(0) breaks after upgrading to MQ 9.1.4 CD or later. The following error following error is recorded in the queue manager error log: ----- amqrmrsa.c : 961 -------------------------------------------------------- 08/10/2020 07:30:50 AM - Process(31738.77467) User(mqm) Program(amqrmppa) Host(xxxxx) Installation(Installation1) VRMF(9.1.5.0) QMgr(TESTQMGR) Time(2020-08-09T23:30:50.283Z) ArithInsert1(41987) ArithInsert2(932) AMQ9541E: CCSID supplied for data conversion not supported.
Local fix
Use a SHARECNV setting greater than 0 on the SVRCONN channel.
Problem summary
**************************************************************** USERS AFFECTED: All MQ distributed users with MQ clients using SHARECNV(0) which connect to an MQ server of the opposite endianness. Platforms affected: AIX, IBM iSeries, Linux on Power, Linux on x86-64, Linux on zSeries, Windows **************************************************************** PROBLEM DESCRIPTION: When a client issues an MQGET with a long wait interval, the queue manager will send a periodic heartbeat flow to the client based on the negotiated HBINT value of the channel. MQ 9.1.4 introduced a problem in which this heartbeat flowed correctly once for a SHARECNV(0) connection, but the queue manager then forgot whether byteswapping was required, for example between a little-endian client and a big-ending queue manager (or vice versa). Any subsequent request from the client was then misinterpreted by the queue manager as having an invalid CCSID value, causing the queue manager to write a message AMQ9541 ("CCSID supplied for data conversion not supported"). The AMQ9541 message included values like CCSID 13059 (the un-byteswapped version of CCSID 819), or CCSID 47108 (the un-byteswapped version of CCSID 1208), or other invalid CCSID values.
Problem conclusion
A code change has been made to ensure the queue manager cannot forget whether a SHARECNV(0) client connection requires byteswapping. As a result of this change, the AMQ9541 message is no longer issued after an MQGET with a long wait interval causes the queue manager to exchange heartbeats with the client. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.2 LTS 9.2.0.6 v9.x CD 9.3.0.0 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
IT33972
Reported component name
IBM MQ BASE MP
Reported component ID
5724H7271
Reported release
915
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-08-20
Closed date
2022-02-03
Last modified date
2022-04-13
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 MP
Fixed component ID
5724H7271
Applicable component levels
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"915"}]
Document Information
Modified date:
14 April 2022