| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| OTMA Bridge DESTINATION CAN NOT BE FOUND OR CREATED |
View previous topic :: View next topic |
| Author |
Message
|
| PeterPotkay |
 Posted: Thu Dec 10, 2020 7:27 am Post subject: OTMA Bridge DESTINATION CAN NOT BE FOUND OR CREATED |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
MQ 9.1 on z/OS. Not sure the IMS version.
The app area is testing the MQ plumbing. We all know the IMS Transaction / TCODE thingie is not yet defined. We expect the transaction to fail. That is not the issue.
My post is asking why we see a reply message.
I have come to expect over the years that when MQ tries to start an IMS transaction and can’t, the message goes to the DLQ on the mainframe QM with a Dead Letter Header that contains the OTMA Sense Code. We see that here. The application’s request message ends up in the dead letter queue with a DLH with reason code 629 (Unrecognised). The MQMD message type is Request. After the DLH I see the IMS Info Header and then the app payload of their request. No questions so far.
BUT, we also see a reply message being sent back to the MQD Reply To Queue and Reply To Queue Manager. Message Type = Reply. Format = MQIMS. There is an IIH header. Short message only 160 bytes. After the IIH header is some stuff including “DFS064 14:11:01 DESTINATION CAN NOT BE FOUN OR CREATED, DEST=xxxxxxx.” I masked the transaction with the xxxxxxx.
My question, finally. Is this expected that the request goes to the DLQ and IMS/OTMA sends back a reply with the details? I don’t why this is surprising to me, it kinda makes sense as I typed it out. I just never noticed a reply message in cases like this. Maybe I never look carefully enough, always target locked as an MQ Admin on the dead letter queue, not paying attention to the app reply queue.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Thu Dec 10, 2020 9:58 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Here is the IBM documentation that confirms the behavior we are seeing.
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.1.0/com.ibm.mq.dev.doc/q023220_.html
If the message cannot be put to the IMS queue, the following action is taken by IBM® MQ:
• If a message cannot be put to IMS because the message is invalid, the message is put to the dead-letter queue, and a message is sent to the system console.
• If the message is valid, but is rejected by IMS, IBM MQ sends an error message to the system console, the message includes the IMS sense code, and the IBM MQ message is put to the dead-letter queue. If the IMS sense code is 001A, IMS sends an IBM MQ message containing the reason for the failure to the reply-to queue.
So, here we have confirmation why sometimes all you have is the request message in the dead letter queue and other times you have both the request message in the dead letter queue AND a reply message from IMS.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
