| Author |
Message
|
| cecil |
 Posted: Wed Nov 22, 2006 3:45 pm Post subject: Sporadic 2110 error code |
 |
|
Newbie
Joined: 17 Oct 2006
Posts: 3
Location: SF Bay Area
|
I am using MQ 6.0.1 on both XP and Redhat Linux. The C code I am using has been modeled from amqsgetc.c . Most of the time the put/get works properly, but in the last few days there have been a series of 2110 errors. What is going on?
2110 is a format error. Since we are passing short ASCII strings, we are using the amqsget.c form of:
md = {MQMD_DEFAULT};
for the message descriptor.
I am a noobie to MQ and would appreciate suggestions. |
|
| Back to top |
|
 |
| wschutz |
| Posted: Wed Nov 22, 2006 4:33 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Is the "putting" program setting md.Format to MQFMT_STRING? If you are passing ascii string around, you need to set the format field to tell MQ how to convert the message.....
_________________
-wayne |
|
| Back to top |
|
|
| Nigelg |
| Posted: Thu Nov 23, 2006 1:54 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
Wayne s probably right, you have tried to convert a msg where MQMD.Format is blank.
This is described in the WMQ Messages manual...
| Quote: |
2110 (X'083E')MQRC_FORMAT_ERROR
Explanation:
An MQGET call was issued with the MQGMO_CONVERT option specified in the GetMsgOpts parameter, but the message cannot be converted successfully due to an error associated with the message format. Possible errors include:
The format name in the message is MQFMT_NONE.
A user-written exit with the name specified by the Format field in the message cannot be found.
The message contains data that is not consistent with the format definition.
|
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| cecil |
| Posted: Mon Nov 27, 2006 10:42 am Post subject: |
|
|
Newbie
Joined: 17 Oct 2006
Posts: 3
Location: SF Bay Area
|
Thanks, that seemed to clear it up.  Strange that I was getting the error only sometimes. Most of the messages, >99%, seemed to work fine. |
|
| Back to top |
|
|
| tleichen |
| Posted: Mon Nov 27, 2006 12:31 pm Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
| cecil wrote: |
| Thanks, that seemed to clear it up. Strange that I was getting the error only sometimes. Most of the messages, >99%, seemed to work fine. |
Theoretically, it would seem that any MQGet with convert would have gotten the same warning. Are you sending messages between different platforms? What are the Encoding and CCSIDs of the platform(s) involved? 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
| cecil |
| Posted: Mon Nov 27, 2006 1:52 pm Post subject: |
|
|
Newbie
Joined: 17 Oct 2006
Posts: 3
Location: SF Bay Area
|
I'm using the default CCSID, 65534. Our platforms are XP and various flavors of linux, mostly RedHat. Our MQ server is RedHat Enterprise ES 4 on quad core Xeon's. Our apps are almost all C++. The strings are pure ASCII. Perhaps there was some buffer corruption or similar problems. I noticed the errors tended to group "clusters" of 5-10 and then none for awhile. It is entirely possible that some other thread was stomping on the buffer. We have occassionally had this problem, so it might not be an MQ problem at all!
Thank you very much for your kind observations! I hope to help others in repayment. |
|
| Back to top |
|
|
|
|
