Mq Error 2119
the fix for this APAR. Subscribe You can track all active APARs for this component. APAR status Closed as program error. Error description MQRC 2119 - MQRC_NOT_CONVERTED after Upgrade to MQ 7.1 It occurs when trying to convert a message with contains an IIH followed by data with format MQIMSVS. CSQAIMS6 is incorrectly setting the ccsid when invoking CSQAXDXI to convert the data following the IIH. Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 * * Release 1 Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: Messages with an IMS information header * * with data following it can cause MQGET * * to return RC 2119, MQRC_NOT_CONVERTED. * * MQGET requests with get message option * * MQGMO_CONVERT set will cause the MQGET * * for messages with an IIH and data * * following to complete with MQCC_WARNING * * (CC 1) and MQRC_NOT_CONVERTED * * (RC 2119). * **************************************************************** * RECOMMENDATION: * **************************************************************** MQGET fails returning MQRC_NOT_CONVERTED with messages containing an IIH followed by extra data, when the MQGET contains the MQGMO_CONVERT option. Messages that start with an IIH, with the IIH.Format set as 'MQIMSVS' and extra data following will cause a MQGET to end with RC 2119 (MQRC_NOT_CONVERTED) and CC 1 (MQCC_WARNING), if the MQGET has MQGMO_CONVERT set. The conversion of the data in the message with the IIH fails to complete successfully, causing the abnormal return code; the message will be removed from the queue. Problem conclusion The conversion of data in messages with an IIH, and IIH.Format set to 'MQIMSVS' has been altered. This ensures extra data following the IIH will be converted successfully, allowing a MQGET to complete successfully. 100Y CSQAIMS6 Temporary fix Comments AP
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support
MQSeries.net Forum Index » General IBM MQ Support » MQ Error Reason Code 2119 MQ Error Reason Code 2119 « View previous topic :: View next topic » Author Message Haunch Posted: Fri Aug 11, 2006 6:33 pm Post subject: MQ Error Reason Code 2119 NewbieJoined: 07 Aug 2006Posts: 5 When using MQ http://www.ibm.com/support/docview.wss?uid=swg1PM76077 Visual Edit the program is returning an error 2119 MQ_RC_CONVERTED. The message type is MQRFH2. Back to top RogerLacroix Posted: Fri Aug 11, 2006 8:51 pm Post subject: Re: MQ Error Reason Code 2119 Jedi KnightJoined: 15 May 2001Posts: 2953Location: London, ON Canada Haunch wrote: When using MQ Visual Edit the program is returning an error 2119 MQ_RC_CONVERTED. The message type is MQRFH2. Hi, In http://www.mqseries.net/phpBB/viewtopic.php?t=31286&sid=90c731b6d077cc177e877b51decffa52 the future, for faster support of Capitalware products, please post your questions in the Capitalware Forum here at mqseries.net http://www.mqseries.net/phpBB2/viewforum.php?f=20 It is probably an invalid CCSID in the RFH2 header. Therefore, the easiest solution is uncheck the 'Convert on Get' click box on the Open Queue window before you open the queue. Hope that helps. Regards, Roger Lacroix Capitalware Inc._________________Capitalware: Transforming tomorrow into today. Connected to MQ! Twitter Back to top Haunch Posted: Mon Aug 14, 2006 12:43 pm Post subject: NewbieJoined: 07 Aug 2006Posts: 5 Roger, I have tried this an the tool is still having issues. The CCSID is 37 and the message is coming from AS/400 running Websphere v5.3. What is really odd is I am able to read other messages from this queue, so I feel that this is not a queue issue, but rather a CCSID issue. Is there any reason why your product would not be able to read a CCSID from an AS/400? Any help would be greatly appreciated. Back to top jefflowrey Posted: Mon Aug 14, 2006 12:45 pm Post subject: Grand PoobahJoined: 16 Oct 2002Posts: 19981 Does the bad message have an MQRV7Client Problem(Abstract) In the queue manager error logs: "AMQ6047: Conversion not supported." From the JMS client these error strings: JMSException: com.ibm.msg.client.jms.DetailedMessageFormatException: JMSWMQ2002: Failed to get a message: MQGET: https://webspheremq.wordpress.com/2012/02/08/amq6047-from-websphere-mq-v7-server-and-jmswmq2002-reason-2119-from-websphere-mq-v7-client/ JMSCMQ0001: reason 2119 (MQRC_NOT_CONVERTED) Symptom If the required conversion support is not available at runtime, then errors of this type may be seen in the queue manager error logs: AMQ6047: Conversion not supported. EXPLANATION: WebSphere MQ is unable to convert string data tagged in CCSID 37 to data in CCSID 1208. ACTION: Check the WebSphere MQ Application Programming Reference Appendix and the appropriate National Language mq error Support publications to see if the CCSIDs are supported by your system. Also exceptions similar to the following may be seen in your JMS application: JMSException: com.ibm.msg.client.jms.DetailedMessageFormatException: JMSWMQ2002: Failed to get a message from destination ‘MYQNAME'. WebSphere MQ classes for JMS attempted to perform an MQGET; however WebSphere MQ reported an error. Use the linked exception to determine the cause of this error. Linked exception: com.ibm.mq.MQException: mq error 2119 JMSCMQ0001: WebSphere MQ call failed with compcode ‘1' (‘MQCC_WARNING') reason ‘2119' (‘MQRC_NOT_CONVERTED'). Cause JMS clients operate on text data in a CCSID of 1208 (UTF-8). When obtaining messages containing text data in a CCSID other than 1208, data conversion of the text is required. WebSphere MQ V6 JMS clients perform the data conversion internally within the Java Virtual Machine (JVM) using facilities provided in the JVM. WebSphere MQ V7 JMS clients that connect to V7 queue managers, do not perform the data conversion internally within the JVM. Instead the data conversion is performed within the server-side message channel agent hosting the SVRCONN channel instance. Resolving the problem When using a WebSphere MQ V7 JMS client with a WebSphere MQ V7 server it becomes necessary to check and ensure that the data conversion activity is supported on the machine where the server runs. Conversion is performed on AIX and HP-UX platforms using data conversion facilities provided by the operating-system vendor. For example on the AIX platform the following fileset is required when getting messages that contain text encoded in CCSID 37:  bos.iconv.ucs.ebcdic  Unicode converters for EBCDIC sets ACTION: Ensure that all of th