|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
message from cobol to java is changing length |
« View previous topic :: View next topic » |
Author |
Message
|
madalynj |
Posted: Sat Jun 04, 2011 10:48 am Post subject: message from cobol to java is changing length |
|
|
Newbie
Joined: 04 Jun 2011 Posts: 2
|
mainframe cobol program using MQPUT1 is placing a message of 74 character into the queue, the message format is string
java program is reading the queue to get the message a warning reason 2119 is occuring and the message retreived is only 72 characters |
|
Back to top |
|
 |
fjb_saper |
Posted: Sat Jun 04, 2011 11:54 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Quote: |
2119 (0847): MQRC_NOT_CONVERTED
Explanation
An MQGET call was issued with the MQGMO_CONVERT option specified in the GetMsgOpts parameter, but an error occurred during conversion of the data in the message. The message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING.
If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data.
This error may also indicate that a parameter to the data-conversion service is not supported.
Completion Code
MQCC_WARNING
Programmer response
Check that the message data is correctly described by the Format, CodedCharSetId and Encoding parameters that were specified when the message was put. Also check that these values, and the CodedCharSetId and Encoding specified in the MsgDesc parameter on the MQGET call, are supported for queue-manager conversion. If the required conversion is not supported, conversion must be carried out by the application. |
Ok I could just say "I rest my case"....
However there was a technote about the differences between V6 and V7 on treating CCSID conversion, especially in JMS, but AFAIK it also concerns java base.
Upgrade to the latest version V 7.0.1.5 if my memory serves me well it should be fixed there.
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
madalynj |
Posted: Sat Jun 04, 2011 2:08 pm Post subject: |
|
|
Newbie
Joined: 04 Jun 2011 Posts: 2
|
what is the reason for the length of the message changing from 74 to 72 |
|
Back to top |
|
 |
fjb_saper |
Posted: Sat Jun 04, 2011 5:31 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Upgrade to the latest version and if the problem persists open a PMR  _________________ MQ & Broker admin |
|
Back to top |
|
 |
gbaddeley |
Posted: Sun Jun 05, 2011 5:17 pm Post subject: Re: message from cobol to java is changing length |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
madalynj wrote: |
mainframe cobol program using MQPUT1 is placing a message of 74 character into the queue, the message format is string
java program is reading the queue to get the message a warning reason 2119 is occuring and the message retreived is only 72 characters |
What is the length of the message data while the message is sitting on the queue? (use MQ Explorer or a browsing tool to look at it) _________________ Glenn |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|