| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Reading BAD messages |
« View previous topic :: View next topic » |
| Author |
Message
|
| Hema30 |
 Posted: Tue Mar 02, 2004 2:13 pm Post subject: Reading BAD messages |
 |
|
Acolyte
Joined: 02 Aug 2003
Posts: 59
|
Hi ,
In our SAP implimentation we use MQ.When there is a problem with the IDOC ,MQSeries puts that IDOC on the BAD message queue.And a script generates a e-mail to inform the support team that a IDOC is gone to the BAD message queue.Now is there a way or utility to read the IDOC number or details about the IDOC why it was sent to BAD message queue??and inform the support team along with the notification???
Thanks
Hema |
|
| Back to top |
|
 |
| kman |
| Posted: Mon Mar 08, 2004 12:38 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
Not that we know of.
How does MQ knows to put the BAD IDOC into the BAD queue? MQ does not know this. It only sends the message to the target queue, or if there is problem there, would send it to DLQ if one is defined. MQ does not care what the message is - BAD or not.
So it must be an application that decide to put to the BAD queue. Or do I get this completely wrong?
If the application decide to put to the BAD queue, then the application can also notify why it put it there. Isn't that so? |
|
| Back to top |
|
|
| bduncan |
| Posted: Mon Mar 08, 2004 1:35 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Kman is right.
It's up to the application that created the message to place enough context either in the message contents or header such that any application retrieving the message from the queue can determine why it was put there, etc...
Remember, MQSeries is (dare I say) simply a transport mechanism. Providing application specific context is outside the scope of the product.
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| KIRANP |
| Posted: Mon Mar 08, 2004 1:47 pm Post subject: HI |
|
|
Acolyte
Joined: 23 Jul 2002
Posts: 51
|
| MQ canot read IDOCs.MQ will be using MQSeries link for R/3. The Inbound server in the MQ Link will read the IDOC info and put the IDOC to BAD message queue if the IDOC is not correct. |
|
| Back to top |
|
|
| JasonE |
| Posted: Mon Mar 08, 2004 2:04 pm Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Note I think that msgs might go to the bad message queue if a communications failure occurs while processing that message. Other causes are lengths not matching and IDOC numbers mismatched, I believe.
As they get put to the bad message queue, a bad message header (documented in the MQLink user guide) is added, which includes the reason code. If you have a specific reason code I can probably tell you what it means (or amqsbcg the bmq, and post up to and including the first few lines of data)
I believe you can strip off the bmh and resubmit if you believe the error is transient.
And just to clarify a previous update, MQLink does know the format of idocs as far as the EDI_DC and EDI_DD sections are concerned, but it doesnt know the contents of the data portion of the edi_dd. |
|
| 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
|
|
|
|
