| Author |
Message
|
| samimohd |
 Posted: Sun Jun 16, 2002 1:19 pm Post subject: Urgent - Message flow onlt processes small Idocs from SAP |
 |
|
Novice
Joined: 25 Mar 2002
Posts: 21
|
I have a message flow which will processes small Idocs but if an Idoc of bigger size ( 11 MB) is sent accross, this message ends in the dead letter q with the the reason code 65536.
All the traces (service, user) show nothing unusual. Even the trace node in the message flow does'nt write any exceptions.
Whay can be the reason. Can any one help me here !
We have MQ R/3 link for SAP, MQSI 2.0.2 broker on AIX.
Sami. |
|
| Back to top |
|
 |
| CodeCraft |
| Posted: Sun Jun 16, 2002 1:53 pm Post subject: |
|
|
Disciple
Joined: 05 Sep 2001
Posts: 195
|
Check what's in the syslog and the AMQERRxx.LOG for the queue manager. Is it possible that the queues and/or channels have a 4mb or 10mb limit set for the message size and this is why you're 11mb message is blowing it?
P.S. IBM Dublin now have an excellent IDOC solution for WMQI 2.1 which parses IDOCs according to their hierarchical content, and, has a discovery tool which creates MRM message definitions directly from attachment to the SAP system. |
|
| Back to top |
|
|
| Tibor |
| Posted: Sun Jun 16, 2002 10:21 pm Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| CodeCraft wrote: |
| P.S. IBM Dublin now have an excellent IDOC solution for WMQI 2.1 which parses IDOCs according to their hierarchical content, and, has a discovery tool which creates MRM message definitions directly from attachment to the SAP system. |
This is a new release of IDOC parser or just a re-compiling the older version ? I was testing it and there was some problems - it was very-very slow on large messages.
How can I test it?  |
|
| Back to top |
|
|
| CodeCraft |
| Posted: Mon Jun 17, 2002 4:13 am Post subject: |
|
|
Disciple
Joined: 05 Sep 2001
Posts: 195
|
| Have you got the free support pack or the later fee based offering? |
|
| Back to top |
|
|
| Tibor |
| Posted: Mon Jun 17, 2002 10:11 pm Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| CodeCraft wrote: |
| Have you got the free support pack or the later fee based offering? |
I tested the supportpac only (it's free but no a freeware...  ) |
|
| Back to top |
|
|
| chanduy9 |
| Posted: Tue Jul 30, 2002 11:35 am Post subject: support pac# |
|
|
Disciple
Joined: 28 Nov 2001
Posts: 177
Location: USA
|
Hi,
Can you tell me the support pack number.
Thanks in advance.
Chandra. |
|
| Back to top |
|
|
| Tibor |
| Posted: Wed Jul 31, 2002 2:25 am Post subject: Re: support pac# |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| chanduy9 wrote: |
Can you tell me the support pack number.
|
This is an 'obsolete' supportpac, because IBM is thinking about more profit...  But if you need it I can send you.
Warning, there are some restrictions:
- v2.1 not supported
- only AIX and NT binaries |
|
| Back to top |
|
|
| chanduy9 |
| Posted: Thu Aug 08, 2002 3:49 pm Post subject: |
|
|
Disciple
Joined: 28 Nov 2001
Posts: 177
Location: USA
|
Hi,
Please send it to me....
Thanks,
Chandra. |
|
| Back to top |
|
|
| jhalstead |
| Posted: Fri Aug 09, 2002 12:22 am Post subject: |
|
|
Master
Joined: 16 Aug 2001
Posts: 258
Location: London
|
samimohd.
Getting back on to your problem!
I have also experienced this problem, when a smallish input message was being reformatted into IDoc format (using NEONRules node). Is this the node you are using?
I'm pretty sure that there is a hard coded maximum buffer size built in to this. If you are using NEONRules of something similar in your flows this would be worth investigating. ..
Obviously the maximum msg length advice still stands!
Jamie |
|
| Back to top |
|
|
| chanduy9 |
| Posted: Fri Aug 09, 2002 5:10 am Post subject: I am not using NEON |
|
|
Disciple
Joined: 28 Nov 2001
Posts: 177
Location: USA
|
Hi,
I am not using NEON...i am using WMQI2.1. There are no NEON nodes..my question is how to built IDoc from MRM/XML.
Thanks in advance,
Chandra. |
|
| Back to top |
|
|
|
|
