Posted: Mon Apr 21, 2008 10:38 am Post subject: IMS Bridge and DLH Reason Codes
Poobah
Joined: 15 May 2001 Posts: 7722
Whenever the IMS Bridge can't deliver a message to the IMS queue, it puts the MQ message into the DLQ with a relatively generic reason code. In our case the most frequent one is 326. Subtract 300 from that to get 26, which is the hex representation for 1A. Then I have to go look in the output of the CHIN to see what sub code is appended to that 1A to see why the bridge really had a problem. In most cases its either TCODE stopped or TCODE not defined.
The problem is in both cases the DLH RC is 326, so a dead letter handler can't distinguish between the 2 reasons. I would like to replay the messages in the DLQ that are there due to the TCODE being stopped, which is typically only for a short time. Has anyone gotten around this?
Is it a valid enhancement request to ask for the OTMA Bridge to use more specific reason codes when putting to the DLQ? The bridge knows the real reason IMS won't take the message since it can write that sub code to the CHIN's output. How about carrying that detail into the DLH with a more specific RC? _________________ Peter Potkay
Keep Calm and MQ On
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