Dear MQA,
 
On top your valuable feedback, I would like to seek your advice on how to handle the DLQ message which has expiry time. 
 
Though we have alert message upon items placed on DLQ, we usually find that the item disappeared on DLQ.   We guess the item should have expired before we look at it.   However, we worry whether we have overlooked 'real' problem whose message has expired.
 
Would you mind share your idea/view/tips on tackling such kind of DLQ items?
 
KK
----- Original Message -----
Sent: Wednesday, August 11, 2004 4:39 AM
Subject: Re: DLQ Maintenance

I have all my DLQs monitored. We get an email when the depth goes over 0, a more URGENT EMAIL!!! when the depth goes over 10, and a page when the depth goes over 50.
 
We manually handle the problem. I don't see very many conditions that can be handled automatically. If a queue is missing, I'm not gonna have a script automatically create it. If a queue is PUT_INHIBITED, I assume its for a good reason, and don't want a script automatically enabling it. If a queue is full, OK, maybe it would be nice to have it retry automatically. The assumption here is that the destination queue will have had a chance to go down a bit. I get that behavior by setting the Message Retry values on the channels themselves, and letting them retry after 1 second one more time. If the queue is being serviced, that's enough to keep things going. If the queue is not being serviced, the message only gets hung up for a sec before going to the DLQ. The DLQ handler wouldn't have any more luck at this point anyway.
 
Moving the messages from the DLQ to another queue is just "sweeping the problem under the rug". I don't see the concept of an application specific DLQ that you can move messages to. The DLQ is a QM level entity. If the message can' be delivered, the DLQ is where it belongs.
 
 
 
 
-----Original Message-----
From: Art Schanz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 10, 2004 3:50 PM
To: [EMAIL PROTECTED]
Subject: DLQ Maintenance


Greetings,

  Just a quick survey to see how different shops are handling these issues:

+ How are you handling the 'maintenance' of msgs in the DLQ?  (How long do you keep them, criteria for deletion, etc.)
+ Do you move msgs from System DLQ to Appl-specific DLQs?  Who is managing these DLQs, the appls or the admins?
+ Do you use the DLQ msg handler or another mechanism for DLQ maintenance?  (What about on z/OS - CSQUDLQH?)

Thanks in advance!
 
Cheers,
  Art

Arthur C. Schanz
Operating Systems Programmer I. - Specialist
Federal Reserve Information Technology
AIMS - WebSphere MQ Support
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified Solution Designer - WebSphere MQ V5.3
(804) 697-3889
[EMAIL PROTECTED]


This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If
you are not the intended recipient, please notify the sender
immediately by return email and delete this communication and destroy all copies.

Reply via email to