To put
this as a problems and not a suggestion or solution as James requested, I
think a fundamental problem is that it is difficult to track messages once
they have been removed from a queue. Thus if an
application puts a message on a local queue and another one has been left
reading messages from a queue, the original developer asks "where's my
message - MQ lost it".
We
have no real way to prove otherwise - even saying "see - the input procs is >
0 so someone read the message" is not conclusive because we also say to
developers when messages build up that input procs > 0 doesn't
prove anything as the input procs only indicates someone has the queue open for
input, not that they're actually doing any MQGETs on it.
Another problem is that when messages expire, we have no way of proving
this has happened either.
Whether IBM provide a solution using the transaction logs or not is an
implementation detail I will leave to them.
Regards
John
Scott
IBM
Certified Specialist - MQSeries
Argos
Ltd
-----Original Message-----
From: Glen Shubert [mailto:[EMAIL PROTECTED]
Sent: 30 April 2004 16:27
To: [EMAIL PROTECTED]
Subject: Re: Message Tracking
From: Glen Shubert [mailto:[EMAIL PROTECTED]
Sent: 30 April 2004 16:27
To: [EMAIL PROTECTED]
Subject: Re: Message Tracking
I fully agree with Frank. As a matter of fact, I had a conversation with IBM about that about 3 weeks ago. I told them that we needed a tool to be able to track messages from the time we received it to the point it left my queue manager. This would include CICS gets/puts, Database time, etc.
Glen Shubert
[EMAIL PROTECTED]
Associate Director
TSYS - MQSeries Technical Support
| "Bright, Frank"
<[EMAIL PROTECTED]> Sent by: MQSeries List <[EMAIL PROTECTED]> 04/30/04 11:11 Please respond to MQSeries List
| To: [EMAIL PROTECTED] cc: Subject: Re: Message Tracking |
I am going to offer another opinion about message tracking.
IBM logs message activity within its own logs for recovery purposes. I just
think the exit you propose is a duplication of the internal MQ logging. IBM
made use of the MQ logs in the creation of the MO12 (MQSeries for OS/390 -
Log extract program) support pac. I believe this capability to track
messages should be built into the product across the platforms.
Thanks
Frank
-----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Gunter
Jeschawitz
Sent: Thursday, April 29, 2004 8:24 AM
To: [EMAIL PROTECTED]
Subject: Re: Message Tracking
I played around with the sample API Exit and installed it for the listener
and I believe you'll get all information needed. It only works for you if
the application use client connection.
This will produce very big log-files so I can't recommend to use it in an
production environment, but in your case it may be acceptable.
Gunter
Instructions for managing your mailing list subscription are provided in the
Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
-----------------------------------------
This e-mail message and any attachments contain confidential information from Medco. If you are not the intended recipient, you are hereby notified that disclosure, printing, copying, distribution, or the taking of any action in reliance on the contents of this electronic information is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender by reply message and then delete the electronic message and any attachments.
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. The information may also constitute a legally privileged confidential communication. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you
**************************************************************
Click here to visit the Argos home page http://www.argos.co.uk
The information contained in this message or any of its attachments may be privileged and/or confidential, and is intended exclusively for the addressee. Unauthorised disclosure, copying or distribution of the contents is strictly prohibited.
The views expressed may not be official policy, but the personal views of the originator.
If you have received this message in error, please advise the sender by using the reply facility in your e-mail software.
All messages sent and received by Argos Ltd are monitored for viruses, high-risk file extensions, and inappropriate content.
