| Author |
Message
|
| mchillin |
 Posted: Mon Sep 10, 2007 1:51 am Post subject: Browse MQ queue via a Message Broker Flow |
 |
|
Novice
Joined: 27 Sep 2006
Posts: 16
|
Is it possible to browse a MQ queue using Message broker flow?
As far as I can see the MQInput and MqGet only allow reading of the queue and there isnt the possibility of browse.
It is important that this particular queue is only accessed via browse and it is monitored and used an alarm system.
I appreciate any advice you can give.
Regards.
Michael. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Sep 10, 2007 1:54 am Post subject: Re: Browse MQ queue via a Message Broker Flow |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mchillin wrote: |
It is important that this particular queue is only accessed via browse and it is monitored and used an alarm system.
|
What requirement are you meeting here? If a message on a queue indicates an event, why is WMB not going to respond to it by reading the message?
WMB is not an ideal monitoring solution. Monitoring software is better at that.
You might fudge it with a custom node, but that's a sledgehammer to crack a nut. Not sure how you'd stop the broker repeatedly browsing the message over and over & soaking resources either sitting here.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mchillin |
| Posted: Mon Sep 10, 2007 2:13 am Post subject: |
|
|
Novice
Joined: 27 Sep 2006
Posts: 16
|
The message that is in the queue indicates that an error has occurred, this idea of browsing this queue is to give information about the error but without interfering with the separate monitoring system, which is already already in place.
An additional problem here being that this runs in z/OS. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Sep 10, 2007 2:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mchillin wrote: |
| The message that is in the queue indicates that an error has occurred, this idea of browsing this queue is to give information about the error but without interfering with the separate monitoring system, which is already already in place. |
So you're monitoring a queue which is already monitored? 
I remain unconvinced this is a good idea, and you'll need custom code to achieve it. Possibly a node, I wouldn't necessarially recommend it.
But it's your system. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Sep 10, 2007 2:55 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mchillin wrote: |
The message that is in the queue indicates that an error has occurred, this idea of browsing this queue is to give information about the error but without interfering with the separate monitoring system, which is already already in place.
An additional problem here being that this runs in z/OS. |
You should capture the error in the flow where it occurs through error handling and take the adequate steps there. There is no need to browse the error queue the way you described.
If there is you need this to be a human task not an automated one...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Sep 10, 2007 2:59 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fjb_saper wrote: |
| You should capture the error in the flow where it occurs through error handling and take the adequate steps there. |
Or wherever the error is occuring - no one's actually said the "alarm" message is added by a failing flow.
But yes, it should be handled by the failing "application" or the existing monitoring.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
