| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| deleting single message from queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| exerk |
 Posted: Fri Mar 01, 2013 11:33 am Post subject: |
 |
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| bruce2359 wrote: |
| You should push this back to the developers, as it is their responsibility to write business-quality code. |
That'll be a first! 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Fri Mar 01, 2013 11:33 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
There is a 3rd possibility. Its possible, perhaps desireable, to have the MQ Admin move / delete 1 or more but not all of the messages out of the queue. Maybe this is a brand new app in DEV and their Poison Message logic is not developed yet and in the interest of progress in the short term, git'er done.
Again, there is no command to do this.
Any capable MQ Admin tool will allow you to do this.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Mar 01, 2013 3:04 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9486
Location: US: west coast, almost. Otherwise, enroute.
|
| PeterPotkay wrote: |
| There is a 3rd possibility. ... Maybe this is a brand new app in DEV and their Poison Message logic is not developed yet ... |
It's been my experience that poison messages are an afterthought.
If/when it's up to me, I would not grant CLEAR QL() even in test, as this would force developers to deal with poison messages early in the design and test phases. One developer argued that he couldn't test his poison message code since there were defective messages in the queue. How absurd is that statement?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| ramires |
| Posted: Fri Mar 01, 2013 5:03 pm Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
After so many answers I believe the best to do is download MO71 supportpac a play with it to see what it can do. Easy interface to use.
_________________
Obrigado / Thanks you |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Mon Mar 04, 2013 11:16 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
| Vitor wrote: |
As administrators you implicitly have all the authority you need as the mqm administrative id can do anything including get messages from queues.
(If you don't have access to the mqm id, please explain how you are an "MQ administrator" and how exactly you perform this role)
What you lack is a tool that can do this. You must either use one of the suggestions here, write your own or have the developers develop one for you. |
I would argue this point as it's not always so cut and dry. It depends largely on the environment. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 04, 2013 12:36 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Toronto_MQ wrote: |
| Vitor wrote: |
As administrators you implicitly have all the authority you need as the mqm administrative id can do anything including get messages from queues.
(If you don't have access to the mqm id, please explain how you are an "MQ administrator" and how exactly you perform this role)
What you lack is a tool that can do this. You must either use one of the suggestions here, write your own or have the developers develop one for you. |
I would argue this point as it's not always so cut and dry. It depends largely on the environment. |
The I repeat my question - how can you "administer" the WMQ estate without access to the mqm id?
On the specific point, the removal of messages: either the OP is an MQ administrator with access via the mqm id to remove messages using one of the methods suggested, or is providing administrative support to the development team via the same id the application runs as.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Mon Mar 04, 2013 12:59 pm Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
| Vitor wrote: |
| Toronto_MQ wrote: |
| Vitor wrote: |
As administrators you implicitly have all the authority you need as the mqm administrative id can do anything including get messages from queues.
(If you don't have access to the mqm id, please explain how you are an "MQ administrator" and how exactly you perform this role)
What you lack is a tool that can do this. You must either use one of the suggestions here, write your own or have the developers develop one for you. |
I would argue this point as it's not always so cut and dry. It depends largely on the environment. |
The I repeat my question - how can you "administer" the WMQ estate without access to the mqm id?
On the specific point, the removal of messages: either the OP is an MQ administrator with access via the mqm id to remove messages using one of the methods suggested, or is providing administrative support to the development team via the same id the application runs as. |
I "administer" all installations here. We run on a wide variety of platforms. And you're mostly right, on the distributed platforms we have access to the mqm group or QMQM/QMQMADM.
However, on z/OS I have the ability to create, alter or delete any objects, and stop/start channels, etc. However, I do not have any access to browse, put or get to/from any application queues. The applicaiton user IDs (or service/batch IDs) have this access, from development to production. If an application needs a message removed from a queue, a queue cleared, the contents of the queue browsed, etc, they have 2 options: run code under their authorized ID to do so; or create a change record and ask operations to do it.
Semantics, perhaps. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 04, 2013 1:10 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Toronto_MQ wrote: |
However, on z/OS I have the ability to create, alter or delete any objects, and stop/start channels, etc. However, I do not have any access to browse, put or get to/from any application queues. The applicaiton user IDs (or service/batch IDs) have this access, from development to production. If an application needs a message removed from a queue, a queue cleared, the contents of the queue browsed, etc, they have 2 options: run code under their authorized ID to do so; or create a change record and ask operations to do it.
Semantics, perhaps. |
Well z/OS uses RACF which does change the model a little; it is semantics that you are the MQ administrator but Ops holds the administrative authority for messages.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Thu Mar 07, 2013 9:20 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
| We find that supportpac MO03 is useful in deleting/manipulating individual messages. |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
