|   | 
	 
  
    | 
RSS Feed - WebSphere MQ Support
 | 
RSS Feed - Message Broker Support
 |   
 
  
	     | 
	 | 
   
 
  
	|  Windows - runmqtrm (MQ Trigger monitor)  as a service | 
	« View previous topic :: View next topic »  | 
   
  
  	
	  
		
		
		  | Author | 
		  Message
		 |  
		
		  | mehedi | 
		  
		    
			  
				 Posted: Thu Feb 07, 2008 1:04 pm    Post subject: Windows - runmqtrm (MQ Trigger monitor)  as a service | 
				     | 
			   
			 
		   | 
		 
		
		   Centurion
 
 Joined: 11 Nov 2001 Posts: 102 Location: PSTech 
  | 
		  
		    
			  
				On Windows, MQ Trigger monitor as a service using MUSR_MQADMIN  
 
 
The triggered application  contains the following code , 
 
 
dir *.* >> dirlist01.txt
 
set > XOUT
 
cd \
 
cd ftp
 
dir *.* >> dirlist02.txt
 
set > XXOUT
 
exit
 
 
 
When the trigger monitor is run as a service (using the MUSR_MQADMIN userid) , the output files are created in this directory D:\Program Files\IBM\WebSphere MQ. The "cd" command has no effect.
 
 
 
When the trigger monitor is run from the command line  (and therefore with the logged in userid) , the results are as expected. 
 
 
MUSR_MQADMIN  is part of "Administrators", "mqm" and "Users" groups on this machine.
 
Both the userid's belong to all the  same groups on this machine.
 
 
Any idea why it behaves this way ? and how can i get expected results with the trigger monitor running 
 
as a service using the MUSR_MQADMIN userid. | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | fjb_saper | 
		  
		    
			  
				 Posted: Thu Feb 07, 2008 2:08 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		 
		
		    Grand High Poobah
 
 Joined: 18 Nov 2003 Posts: 20768 Location: LI,NY 
  | 
		  
		    
			  
				change your batch application.
 
The first commands should be:
 
rem set drive to run in
 
d:
 
rem set directory to run in
 
cd \path\directory
 
 
Enjoy   _________________ MQ & Broker admin | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | mehedi | 
		  
		    
			  
				 Posted: Mon Feb 11, 2008 8:35 am    Post subject:  | 
				     | 
			   
			 
		   | 
		 
		
		   Centurion
 
 Joined: 11 Nov 2001 Posts: 102 Location: PSTech 
  | 
		  
		    
			  
				Hi , 
 
 
The same code works when the trigger monitor is run 
 
(1) using the MQ support pac and running the trigger monitor as a Windows service using the SYSTEM userid(but can be any)
 
(2) from the command line , using the logged on userid
 
 
It doesn't work when the trigger monitor is run as an MQService . When it runs as a MQService it uses the MUSR_MQADMIN userid
 
 
Thaks
 
 
Mehedi | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | jefflowrey | 
		  
		    
			  
				 Posted: Mon Feb 11, 2008 8:39 am    Post subject:  | 
				     | 
			   
			 
		   | 
		 
		
		   Grand Poobah
 
 Joined: 16 Oct 2002 Posts: 19981
  
  | 
		  
		    
			  
				Because you aren't in the same shell that you think you are.
 
 
Build your batch file to set up your environment fully.  Don't rely on default locations or "default" paths or classpaths. _________________ I am *not* the model of the modern major general. | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | 
		    
		   | 
		 
	   
	 | 
   
 
  
	     | 
	 | 
	Page 1 of 1 | 
   
 
 
 
  
  	
	  
		
		  
 
  | 
		  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
  | 
  		 
	   
	 | 
   
 
  	 | 
	  |