| Author | Message | 
		
		  | bduncan | 
			  
				|  Posted: Wed Aug 08, 2001 3:42 pm    Post subject: |   |  | 
		
		  | Padawan
 
 
 Joined: 11 Apr 2001Posts: 1554
 Location: Silicon Valley
 
 | 
			  
				| So I've always been under the impression that one should issue the endmqm command with the -w parameter to wait for the queue manager to completely quiesce. I thought you would only resort to the -i and -p parameters if that failed. Now I've noticed that all of our unix queue managers have a script that is called during the rc shutdown sequence that issue a "endmqm -i" command. I was going to recommend changing it to the -w parameter, but then I thought, since this script is only being called when the actual machine is being shut down, and we have had problems where -w simply hangs forever forcing us to try another paramter (which in this case would stop the machine from shutting down, possibly while nobody is watching), maybe -i isn't such a bad idea? Any thoughts? 
 
 _________________
 Brandon Duncan
 IBM Certified MQSeries Specialist
 MQSeries.net forum moderator
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | pal | 
			  
				|  Posted: Wed Aug 15, 2001 1:06 pm    Post subject: |   |  | 
		
		  | Apprentice
 
 
 Joined: 14 Aug 2001Posts: 35
 
 
 | 
			  
				| The -i should work as long as the applications using the queue manager(s) don't care that their incomplete units of work may get rolled back the next time these queue manager(s) are started. 
 I would guess since the machine is going down that there are other more serious issues to worry about than some MQ transactions getting rolled back
  |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | kolban | 
			  
				|  Posted: Wed Aug 15, 2001 7:39 pm    Post subject: |   |  | 
		
		  |  Grand Master
 
 
 Joined: 22 May 2001Posts: 1072
 Location: Fort Worth, TX, USA
 
 | 
			  
				| Additionally, it is excellent practice to add the MQ_FAIL_IF_QUEICING (sp) option to each MQ API call.  This results in an error condition being reported back to the application if the request to cleanly end the queue manager has been submitted.  This is the way to programatically cause applications to cleanly terminate if they are currently connected to the queue manager. |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | chanduy9 | 
			  
				|  Posted: Thu Jul 10, 2003 5:34 am    Post subject: what apps are conntected??? |   |  | 
		
		  | Disciple
 
 
 Joined: 28 Nov 2001Posts: 177
 Location: USA
 
 | 
			  
				| Hi, 
 How do we know what applications are connected to the QMGR.  If I grep on amqzlaa0 it is showing instances, but I want to know who are connected to the QMGR.
 
 Thanks in Advance,
 Chandra.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | bduncan | 
			  
				|  Posted: Thu Jul 10, 2003 9:45 am    Post subject: |   |  | 
		
		  | Padawan
 
 
 Joined: 11 Apr 2001Posts: 1554
 Location: Silicon Valley
 
 | 
			  
				| You can only get this information if you are using MQ v5.3. Otherwise you can only get the number of applications connected by looking at the IPPROCs and OPPROCs of each queue. _________________
 Brandon Duncan
 IBM Certified MQSeries Specialist
 MQSeries.net forum moderator
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | chanduy9 | 
			  
				|  Posted: Thu Jul 10, 2003 10:13 am    Post subject: |   |  | 
		
		  | Disciple
 
 
 Joined: 28 Nov 2001Posts: 177
 Location: USA
 
 | 
			  
				| Hi, 
 I am using MQ 5.3 on AIX. How to see who connected to the QMGR.
 
 Thanks,
 Chandra.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | bduncan | 
			  
				|  Posted: Thu Jul 10, 2003 4:39 pm    Post subject: |   |  | 
		
		  | Padawan
 
 
 Joined: 11 Apr 2001Posts: 1554
 Location: Silicon Valley
 
 | 
			  
				| See your other post on this topic. _________________
 Brandon Duncan
 IBM Certified MQSeries Specialist
 MQSeries.net forum moderator
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  |  |