| Author | 
		  Message
		 | 
		
		  | sam | 
		  
		    
			  
				 Posted: Tue May 21, 2002 12:58 pm    Post subject: Running Trigger Monitor in the background | 
				     | 
			   
			 
		   | 
		
		
		   Acolyte
 
 Joined: 02 Apr 2002 Posts: 52
  
  | 
		  
		    
			  
				On Solaris how do you run the trigger monitor in the background? is it
 
 
runmqtrm -m QmgrName -q InitQ &
 
 Can I run it from runmqsc? 
 
Thanks. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mqonnet | 
		  
		    
			  
				 Posted: Tue May 21, 2002 1:04 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand Master
 
 Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa. 
  | 
		  
		    
			  
				You are right with the command but you cannot run the command from runmqsc.  Runmqsc is an interface for mqsc commands and not for processes.  You need to run it from outside runmqsc, from the prompt.
 
 
Cheers.
 
Kumar _________________ IBM Certified WebSphere MQ V5.3 Developer
 
IBM Certified WebSphere MQ V5.3 Solution Designer
 
IBM Certified WebSphere MQ V5.3 System Administrator | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Ward | 
		  
		    
			  
				 Posted: Wed May 22, 2002 12:58 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Voyager
 
 Joined: 27 Jun 2001 Posts: 98 Location: Europe 
  | 
		  
		    
			  
				Hi,
 
 
If you want the listener to run in the background you'll have to use inetd to start it.  How do you do this ?
 
 
1. edit the /etc/services file and add 
 
 
      MQSeries       1414/tcp      # MQSeries channel 
 
 
use 1414 or any other port number you'd like to use
 
 
2. edit the /etc/inetd.conf and add something like
 
 
      MQSeries stream tcp nowait mqm /opt/mqm/bin/amqcrsta amqcrsta -m MYQUEUEMANAGER
 
 
with MYQUEUEMANAGER the name of your queue manager
 
 
3. recycle the inetd process.  This can be done by killing the running one, it will be started automatically.
 
 
 
Note that you'll need root access to do all this...
 
 
Cheers,
 
 
Ward _________________ IBM Certified Solution Designer -- WebSphere MQ V6.0
 
IBM Certified Solution Developer - WebSphere Message Broker V6.0
 
----------------------------
 
Visit Boat Dimensions | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | sam | 
		  
		    
			  
				 Posted: Wed May 22, 2002 9:34 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Acolyte
 
 Joined: 02 Apr 2002 Posts: 52
  
  | 
		  
		    
			  
				| What is this amqcrsta? is this the listener process? MQSeries/1414? is this the QueueManager which is running or why do you need this in the etc/services file? also I'm I could run the listener through runmqsc using the command start listener. What is the difference between all of them? Thanks. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mrlinux | 
		  
		    
			  
				 Posted: Wed May 22, 2002 9:55 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand Master
 
 Joined: 14 Feb 2002 Posts: 1261 Location: Detroit,MI USA 
  | 
		  
		    
			  
				amqcrsta is the listener process and you can start it either way
 
via inetd or runmqsc or runmqlsr. The differnece's are
 
 
1) inetd will launch seperate process for each channel also if one process fail's it doesnt affect the rest.
 
 
2) runmqlsr or start listener  runs a seperate threrad for each channel, however if it crashes all the rcvr channels come down.
 
 
 
 
 
 However I dont think that was your question,  you are correct on how to run the trigger monitor in the background _________________ Jeff 
 
 
IBM Certified Developer MQSeries
 
IBM Certified Specialist MQSeries
 
IBM Certified Solutions Expert MQSeries | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |