| Author | Message | 
		
		  | Blomman | 
			  
				|  Posted: Tue Oct 31, 2006 9:08 am    Post subject: Delete remote queue? |   |  | 
		
		  | Master
 
 
 Joined: 31 Oct 2006Posts: 230
 
 
 | 
			  
				| Hi all! 
 My first post here, please be gentle!
 
 One simple question, how do u delete a remote queue??
 
 I have one on my broker and it was defined wrong from the begining when it was created then and i tried to change some parameters on the queue but that didnt fix my problem. So i wanted to delete the queue and recreate it. But i couldnt do that got something like "Object open blabla...".
 
 So my solution was to create a new queue for my purpose, but the "old" one i s still in my broker....How to delete it???? Whitout stopping the broker or remote qmanagers. I have disconnected the flow aswell but i still cant delete the queue.
 
 /Blomman
 
 p.s yes i have searched the forum.
  |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | jefflowrey | 
			  
				|  Posted: Tue Oct 31, 2006 9:36 am    Post subject: |   |  | 
		
		  | Grand Poobah
 
 
 Joined: 16 Oct 2002Posts: 19981
 
 
 | 
			  
				| You can, in MQ v6, force any connections to the queue to close. 
 In MQ v5.x, I don't think you can do this for bindings connections.
 _________________
 I am *not* the model of the modern major general.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | kevinf2349 | 
			  
				|  Posted: Tue Oct 31, 2006 9:36 am    Post subject: |   |  | 
		
		  |  Grand Master
 
 
 Joined: 28 Feb 2003Posts: 1311
 Location: USA
 
 | 
			  
				| 
   
	| Quote: |  
	| how do u delete a remote queue?? |  
 You don't.
 
 You can delete the remote queue definition from your local queue manager, but to delete the actual queue itself you need to access the queue manager that owns the local queue and delete it from there.
 
 
 Hope this helps
 
 edit : I stand corrected....looks like you can in Version 6
  |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | Blomman | 
			  
				|  Posted: Tue Oct 31, 2006 11:34 am    Post subject: |   |  | 
		
		  | Master
 
 
 Joined: 31 Oct 2006Posts: 230
 
 
 | 
			  
				| Thx! 
 I have tried to do that but still i cant,remove the remote Q.
 
 /Blomman
 
 
 
 
   
	| kevinf2349 wrote: |  
	| 
   
	| Quote: |  
	| how do u delete a remote queue?? |  
 You don't.
 
 You can delete the remote queue definition from your local queue manager, but to delete the actual queue itself you need to access the queue manager that owns the local queue and delete it from there.
 
 
 Hope this helps
 
 edit : I stand corrected....looks like you can in Version 6
  |  |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | Blomman | 
			  
				|  Posted: Tue Oct 31, 2006 11:36 am    Post subject: |   |  | 
		
		  | Master
 
 
 Joined: 31 Oct 2006Posts: 230
 
 
 | 
			  
				| Hi yes i figured out that v6 had an -force option for this, but im running v5.3. 
 /Blomman
 
 
   
	| jefflowrey wrote: |  
	| You can, in MQ v6, force any connections to the queue to close. 
 In MQ v5.x, I don't think you can do this for bindings connections.
 |  |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | jefflowrey | 
			  
				|  Posted: Tue Oct 31, 2006 11:40 am    Post subject: |   |  | 
		
		  | Grand Poobah
 
 
 Joined: 16 Oct 2002Posts: 19981
 
 
 | 
			  
				| If you're running v5.3, I don't think you can close any open handles on the queue, so I don't think you can do what you want to do. 
 You should still be able to use dis qstatus() type handle to find out who has an open handle on the queue, though.
 _________________
 I am *not* the model of the modern major general.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | Blomman | 
			  
				|  Posted: Tue Oct 31, 2006 2:05 pm    Post subject: |   |  | 
		
		  | Master
 
 
 Joined: 31 Oct 2006Posts: 230
 
 
 | 
			  
				| 
   
	| jefflowrey wrote: |  
	| If you're running v5.3, I don't think you can close any open handles on the queue, so I don't think you can do what you want to do. 
 You should still be able to use dis qstatus() type handle to find out who has an open handle on the queue, though.
 |  
 Hi again!
 
 I have tryed dis qstatus() type handle and it work only for local qs?
 I just got "Queue couldnt be found..."
 
 Thx for all the input!
 
 /Blomman
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | wschutz | 
			  
				|  Posted: Tue Oct 31, 2006 2:29 pm    Post subject: |   |  | 
		
		  |  Jedi Knight
 
 
 Joined: 02 Jun 2005Posts: 3316
 Location: IBM (retired)
 
 | 
			  
				| You might try issuing an ALTER QR(name) PUT(DISABLED) FORCE which should break the connection and prevent the broker from reconnecting ... then you should be able to delete the definition.
 _________________
 -wayne
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | Nigelg | 
			  
				|  Posted: Wed Nov 01, 2006 1:13 am    Post subject: |   |  | 
		
		  | Grand Master
 
 
 Joined: 02 Aug 2004Posts: 1046
 
 
 | 
			  
				| To find out which app has a remote queue open, do a DIS QS on the XMITQ defined in the remote queue. _________________
 MQSeries.net helps those who help themselves..
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | Blomman | 
			  
				|  Posted: Wed Nov 01, 2006 6:14 am    Post subject: |   |  | 
		
		  | Master
 
 
 Joined: 31 Oct 2006Posts: 230
 
 
 | 
			  
				| 
   
	| Nigelg wrote: |  
	| To find out which app has a remote queue open, do a DIS QS on the XMITQ defined in the remote queue. |  
 XMITQ is that the same as transmission queue?
 
 /Blomman
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | Vitor | 
			  
				|  Posted: Wed Nov 01, 2006 6:17 am    Post subject: |   |  | 
		
		  |  Grand High Poobah
 
 
 Joined: 11 Nov 2005Posts: 26093
 Location: Texas, USA
 
 | 
			  
				| XMITQ is a standard/common/often used shorthand for transmission queue. Taken from the USAGE attribute.  _________________
 Honesty is the best policy.
 Insanity is the best defence.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | Blomman | 
			  
				|  Posted: Wed Nov 01, 2006 6:21 am    Post subject: |   |  | 
		
		  | Master
 
 
 Joined: 31 Oct 2006Posts: 230
 
 
 | 
			  
				| 
   
	| wschutz wrote: |  
	| You might try issuing an ALTER QR(name) PUT(DISABLED) FORCE which should break the connection and prevent the broker from reconnecting ... then you should be able to delete the definition.
 |  
 Didnt work, the QR i want to delete is actually on the broker.
 I runned the command and i got  something like "q has been changed" but stil it says "Object is open".
 
 /Blomman
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | Blomman | 
			  
				|  Posted: Wed Nov 01, 2006 6:29 am    Post subject: |   |  | 
		
		  | Master
 
 
 Joined: 31 Oct 2006Posts: 230
 
 
 | 
			  
				| 
   
	| Vitor wrote: |  
	| XMITQ is a standard/common/often used shorthand for transmission queue. Taken from the USAGE attribute.  |  
 Ok thx i figured it out while posting...
   I do a dis  chstatus(XMITQ....).
 And i can se OPPRCC(9), ok i have other remote queues using this transmissionQ..
 Maybe thats the problem..?
 
 /Blomman
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | Vitor | 
			  
				|  Posted: Wed Nov 01, 2006 6:39 am    Post subject: |   |  | 
		
		  |  Grand High Poobah
 
 
 Joined: 11 Nov 2005Posts: 26093
 Location: Texas, USA
 
 | 
			  
				| It's actually 9 processes with the queue open rather than other queues, but that's a little pedantic   
 It certainly is why you're getting "Object is open" messages.
 
 You could try doing a DISPLAY QSTATUS to find the pid of the processes that are holding the queue and from them, work out what needs to be done to get them off. I recommend caution....
   
 I think you might need to schedule some downtime for the broker, close it and then have a go at this queue (I understand that this is not your preferred scenario).
 _________________
 Honesty is the best policy.
 Insanity is the best defence.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | Blomman | 
			  
				|  Posted: Wed Nov 01, 2006 7:34 am    Post subject: |   |  | 
		
		  | Master
 
 
 Joined: 31 Oct 2006Posts: 230
 
 
 | 
			  
				| Okidoki! 
 But how do i se the pids using DISPLAY QSTATUS??
 Ok my first thought was to schedule a stop for the broker.. As u said.
   
 /Blomman
 
 
 
   
	| Vitor wrote: |  
	| I You could try doing a DISPLAY QSTATUS to find the pid of the processes that are holding the queue and from them, work out what needs to be done to get them off. I recommend caution....
   
 |  |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  |  |