A fix is available
APAR status
Closed as program error.
Error description
The following messages are seen in MQ joblog: . 14.58.28 CSQ2005I +CSQ1 CSQ2QCP1 ERROR PROCESSING MESSAGE, FEEDBACK=293, XCFGNAME=OTMATI0T XCFMNAME=SI1T TPIPE=CSQ0008F 14.58.28 CSQ2005I +CSQ1 CSQ2QCP1 ERROR PROCESSING MESSAGE, FEEDBACK=293, XCFGNAME=OTMATI0T XCFMNAME=SI1T TPIPE=CSQ0008F 14.58.45 CSQ2005I +CSQ1 CSQ2QCP1 ERROR PROCESSING MESSAGE, FEEDBACK=293, XCFGNAME=OTMATI0T XCFMNAME=SI1T TPIPE=CSQ0008F 14.58.47 CSQ2005I +CSQ1 CSQ2QCP1 ERROR PROCESSING MESSAGE, FEEDBACK=293, XCFGNAME=OTMATI0T XCFMNAME=SI1T TPIPE=CSQ0008F . CSQ2005I with FEEDBACK 293, MQFB_DATA_LENGTH_TOO_BIG, when an IMS reply message longer than 32764 is received by the IMS Bridge (IMS OTMA supports up to 32767 so there is no reason why the MQ IMS Bridge should not do the same).
Local fix
Reducing the size of the message to be no longer than 32764 will prevent the problem from occurring.
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 8 * * Release 0 Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: CSQ2005I is issued with FEEDBACK 293 * * (MQFB_DATA_LENGTH_TOO_BIG) when an IMS * * message containing segments longer than * * 32764 bytes is processed. * * Attempts to convert IMS messages with * * segments longer than 32764 bytes fail * * with MQRC 2110 MQRC_FORMAT_ERROR. * * If the conversion occurred when the * * channel initiator put the message to an * * IMS bridge queue, the conversion * * failure is reported by messages * * CSQX048I 'Unable to convert message for * * xxxx, MQCC=1, MQRC=2110 * * (MQRC_FORMAT_ERROR)' * **************************************************************** * RECOMMENDATION: * **************************************************************** When processing an IMS message, the queue manager checks that the length in the LL bytes for each segment is not more than 32764 bytes, however OTMA can support segments up to 32767 bytes.
Problem conclusion
The MQ IMS bridge and MQ conversion routines are updated to handle IMS messages containing segments of up to 32767 bytes. The WebSphere MQ Version 8 Knowledge Center is updated: WebSphere MQ 8.0.0 IBM MQ Developing applications Application development concepts IMS and IMS Bridge applications on IBM MQ for z/OS Writing IBM MQ-IMS bridge applications How the IBM MQ-IMS bridge deals with messages Message segmentation ( q023290_ ) The statement: "The maximum length of an LLZZ-data segment is defined by IMS/OTMA (32764 bytes)" is changed to: "The maximum length of an LLZZ-data segment is defined by IMS/OTMA (32767 bytes)" 000Y CSQAIMSV CSQAIVS6 CSQ2MTOO CSQ2QCP1
Temporary fix
Comments
APAR Information
APAR number
PI41096
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-05-14
Closed date
2015-07-31
Last modified date
2015-10-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI29910
Modules/Macros
CSQAIMSV CSQAIVS6 CSQ2MTOO CSQ2QCP1
Fix information
Fixed component name
WMQ Z/OS 8
Fixed component ID
5655W9700
Applicable component levels
R000 PSY UI29910
UP15/09/09 P F509
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 October 2015