ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » RUNMQDLQ - MQRC 2026

Post new topic  Reply to topic
 RUNMQDLQ - MQRC 2026 « View previous topic :: View next topic » 
Author Message
vsathyan
PostPosted: Mon Feb 16, 2015 10:21 am    Post subject: RUNMQDLQ - MQRC 2026 Reply with quote

Centurion

Joined: 10 Mar 2014
Posts: 121

When we try to reprocess the messages from dlq, we get MQRC 2026. Have any one faced this issue?

The dlq handler starts and stops immediately. We do not see any errors when we process the dlq handler. But an FDC is generated with the above mentioned reason code.

02/16/2015 12:10:59 PM AMQ8708: Dead-letter queue handler started to process INPUTQ(SYSTEM.DEAD.LETTER.QUEUE).
02/16/2015 12:10:59 PM AMQ8709: Dead-letter queue handler ending.

FDC details
Probe Description :- AMQ8767: Unexpected error while getting message from |
| dead-letter queue: CompCode = 2 Reason = 2026. 

WebSphere MQ 7.5.0.2, Linux, 64 bit.

Any inputs / advise? Thanks in advance.
Please note : No broker involved. Only WebSphere MQ.
Back to top
View user's profile Send private message
PaulClarke
PostPosted: Mon Feb 16, 2015 10:34 am    Post subject: Reply with quote

Grand Master

Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand

It sounds as though the first message on the DLQ has been put on in an incorrect format. Often when a message is read with an incorrect format the correct response is to put it to the DLQ. However, you are reading the DLQ itself then you are a little stuck. The only two choices are probably to discard the message, which is hazardous, or to the end the program and have the user sort it out. I suspect that is what the DLQ handler is hoping you will do.

Try browsing the message on the DLQ with something that can format the messages. Naturally I would use MO71. See whether it looks ok and has the right Format, CCSID and Encoding values. Might even be worth moving the first message to a different queue if you want to get your DLQ handler up and running again.

Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com
Back to top
View user's profile Send private message Visit poster's website
vsathyan
PostPosted: Mon Feb 16, 2015 11:56 am    Post subject: Reply with quote

Centurion

Joined: 10 Mar 2014
Posts: 121

Thanks very much Paul, for your valuable advise.
MO71 saved our day. This was in production.

All messages succesfully processed from dlq using MO71.
Back to top
View user's profile Send private message
PaulClarke
PostPosted: Mon Feb 16, 2015 12:12 pm    Post subject: Reply with quote

Grand Master

Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand

Great, glad to hear it.
_________________
Paul Clarke
MQGem Software
www.mqgem.com
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » RUNMQDLQ - MQRC 2026
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.