| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem with MQSeries Link for R/3 (invalid Idoc structure) |
« View previous topic :: View next topic » |
| Author |
Message
|
| marnick |
 Posted: Fri Dec 15, 2006 10:34 am Post subject: Problem with MQSeries Link for R/3 (invalid Idoc structure) |
 |
|
Novice
Joined: 26 Oct 2006
Posts: 10
|
Hello:
I need some help, I have a MQSeries Link for R/3 working over AIX Version 5 and MQ version 5.3.
After a refresh of SAP I start to get this error:
IDoc has an invalid structure length. IDoc value="825241632". Expected
value="108".
The server is terminating because an invalid message was received.
The MQSeries Link for R/3 server has ended normally.
The format of the messages is correct (I send to the same SAP with another link over another server without problem).
I restore the file System from a backUp, but I continue with the same problem.
I export this variable SMQ_NO_CHECK_LENGTH=1 and again the same problem javascript:emoticon(' ')
Please if anybody has any hint or suggest I will appreciate.
Thanks in advance.
Martin |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Dec 15, 2006 3:43 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
We had the same problem.
You are taking advantage of a "feature" (read bug) of MQLink that is no longer present in the latest version.
The cure: Format your message and especially your header correctly.
The MQMD needs to contain the format for Sap header (MQSAPH?) and the CCSID and encoding fields on both headers need to be set appropriately. (In cobol we had to explicitely set them. Just using the default did no longer work probably because of the "extra" SAPH header....
Don't forget to set the format on the SAPH header to MQSTR....
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Nigelg |
| Posted: Mon Dec 18, 2006 1:57 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
SMQ_NO_CHECK_LENGTH only has any effect if you have installed a fix to CSD03.
I agree with fjb; the SAP header on the msg is badly formed and does not properly describe the length of the header, so the app which creates the msg should be amended to write the correct value into the StrucLength field.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Dec 18, 2006 4:32 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Nigelg wrote: |
SMQ_NO_CHECK_LENGTH only has any effect if you have installed a fix to CSD03.
I agree with fjb; the SAP header on the msg is badly formed and does not properly describe the length of the header, so the app which creates the msg should be amended to write the correct value into the StrucLength field. |
Nigel: This is the way the feature manifests itself. The StrucLength is most probably correct at 108. What is not correct are the header formats and ccsid and encoding... We ran into this when we upgraded our MQLink for R3.
It is a known "feature" of the earlier version that it lets you get away with a lot of "bad" information on the headers...
They just need to fix their headers to conform to MQ standards...
Enjoy
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
