At my current client, we
have a relatively simple implementation with fixed queue definitions, and very
few production modifications. We monitor the queue
(and all objects) using Nastel's Autopilot for
WebSphereMQ.
We do have one vendor
application - Swift Alliance - that insists on placing messages on the DLQ if
there are any applicaiton-level formatting errors in an MQ-received SWIFT
message. Apparently, Swift developers never thought to setup an error
queue of any kind, and they insist on using the system DLQ. In the last 6
months, the only messages that have dropped to the DLQ are Swift rejects.
Dave
Awerbuch
====================
David Awerbuch
MQSeries Specialist
APC Consulting Services Inc.
mailto:[EMAIL PROTECTED]
-----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.
*** Calyon ****************************************************
This message and/or any attachments (the "message") is intended for the sole use of its addressee. If you are not the addressee, please immediately notify the sender and then destroy the message. The unauthorized disclosure, use, dissemination or copying (either whole or partial) of this e-mail, or any information it contains, is prohibited. E-mails are susceptible to alteration and their integrity cannot be guaranteed. As this message and/or any attachments may have been altered without our knowledge, its content is not legally binding on CALYON Corporate and Investment Bank. All rights reserved.
