| Author |
Message
|
| omodarah |
 Posted: Wed Mar 30, 2005 2:02 pm Post subject: API for logging all message deliveries into a repositry |
 |
|
Apprentice
Joined: 09 Sep 2004
Posts: 26
|
Dear all,
Does anyone know of an API/Exit Point Program for the iSeries that will allow us
to log all messages delivered in a specified Queue into a DB2 repository?
We need it to diagnose an anomally with a particular queue.
So for a period we would like to see what messages are arriving in the queue.
Thanks in advance. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Mar 30, 2005 4:20 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Why bother with an exit?
Reroute the messages so that they go into a different queue first, and then write a simple program to move them into the right queue, and insert into the database of your choice.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| hopsala |
| Posted: Thu Mar 31, 2005 12:07 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
In accord with Jeff, I don't know if you have ever done the such, but writing an exit is hard work... (mainly due to poor IBM documentation). Anyway, it would be far better to implement what jeff suggested.
The interesting q here is, what is this "anomaly" you speak of?
(usually such problems arise from the data sent to a specific q, not the queue itself. It is easy to test - reroute msgs to some other queue with different parms and see what happens.) |
|
| Back to top |
|
|
| omodarah |
| Posted: Thu Mar 31, 2005 6:12 am Post subject: |
|
|
Apprentice
Joined: 09 Sep 2004
Posts: 26
|
Jeff/Hopsla,
I considered this option initially but I was concerned about the extra
overhead that would generate for the delivery of a message. I did not
want to cause a bottleneck in the delivery process. As no file access done
at the application level can be as quick as using an exit.
I have written exit programs for other iSeries functions but none for MQ to date. I
will discuss with the client to see if this is an option they are willing to take.
Thanks for the advice. |
|
| Back to top |
|
|
| JLRowe |
| Posted: Thu Mar 31, 2005 6:25 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
| Intercepting the messages is certainly a lot easier than writing an exit, also an exit may be difficult to debug - leading you back to square one. |
|
| Back to top |
|
|
| EddieA |
| Posted: Thu Mar 31, 2005 9:53 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| I did not want to cause a bottleneck in the delivery process |
| Quote: |
| log all messages delivered in a specified Queue into a DB2 repository |
Those 2 quotes seem to be at odds with each other. 
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Mar 31, 2005 5:32 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The other thing about the intercept vs. exit debate is that you can enable and disable an intercept without shutting down the queue manager.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
