| Author | Message | 
		
		  | hughson | 
			  
				|  Posted: Mon Jun 19, 2017 4:20 pm    Post subject: Trigger Monitor as a SERVICE object on Windows |   |  | 
		
		  |  Padawan
 
 
 Joined: 09 May 2013Posts: 1967
 Location: Bay of Plenty, New Zealand
 
 | 
			  
				| Do you use a SERVICE object to start/stop your Trigger Monitor? 
 Are you on the Windows platform?
 
 I noticed something about this set up the other day that I thought others should be aware of, so I wrote it up.
 
 Running the Trigger Monitor as a SERVICE
 
 Apologies if this has been discussed before and everyone already knows about this, but I thought it worth highlighting in case anyone hadn't seen it.
 
 Cheers,
 Morag
 _________________
 Morag Hughson @MoragHughson
 IBM MQ Technical Education Specialist
 Get your IBM MQ training here!
 MQGem Software
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | fjb_saper | 
			  
				|  Posted: Tue Jun 20, 2017 4:58 am    Post subject: Re: Trigger Monitor as a SERVICE object on Windows |   |  | 
		
		  |  Grand High Poobah
 
 
 Joined: 18 Nov 2003Posts: 20767
 Location: LI,NY
 
 | 
			  
				| 
   
	| hughson wrote: |  
	| Do you use a SERVICE object to start/stop your Trigger Monitor? 
 Are you on the Windows platform?
 
 I noticed something about this set up the other day that I thought others should be aware of, so I wrote it up.
 
 Running the Trigger Monitor as a SERVICE
 
 Apologies if this has been discussed before and everyone already knows about this, but I thought it worth highlighting in case anyone hadn't seen it.
 
 Cheers,
 Morag
 |  Great analysis. Thanks.
 I still go for get inhibiting the initiation queue and enabling it afterwards.
 Nice work around if the stop does not work.
 However it is better to fix it at the source!
  _________________
 MQ & Broker admin
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | hughson | 
			  
				|  Posted: Tue Jun 20, 2017 12:32 pm    Post subject: Re: Trigger Monitor as a SERVICE object on Windows |   |  | 
		
		  |  Padawan
 
 
 Joined: 09 May 2013Posts: 1967
 Location: Bay of Plenty, New Zealand
 
 | 
			  
				| 
   
	| fjb_saper wrote: |  
	| I still go for get inhibiting the initiation queue and enabling it afterwards. |  Indeed! That was always the way to do it prior to the invention of SERVICE objects, and of course still works just fine.
 
 Cheers
 Morag
 _________________
 Morag Hughson @MoragHughson
 IBM MQ Technical Education Specialist
 Get your IBM MQ training here!
 MQGem Software
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | mqjeff | 
			  
				|  Posted: Wed Jun 21, 2017 4:18 am    Post subject: |   |  | 
		
		  | Grand Master
 
 
 Joined: 25 Jun 2008Posts: 17447
 
 
 | 
			  
				| I notice that your startcmd is different than your stopcmd in the service that gives you issues... 
 That is, the startcmd is /bin/ and the stopcmd is /bin64/
 
 Do you have the same issue if they match?
 _________________
 chmod  -R ugo-wx /
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | fjb_saper | 
			  
				|  Posted: Wed Jun 21, 2017 4:42 am    Post subject: |   |  | 
		
		  |  Grand High Poobah
 
 
 Joined: 18 Nov 2003Posts: 20767
 Location: LI,NY
 
 | 
			  
				| 
   
	| mqjeff wrote: |  
	| I notice that your startcmd is different than your stopcmd in the service that gives you issues... 
 That is, the startcmd is /bin/ and the stopcmd is /bin64/
 
 Do you have the same issue if they match?
 |  That was the whole point of her link. Use bin64 on both and no problem.
 Use a mix and you cannot shutdown the service with the stop service command as the relevant pid is the 64 bit one and not the 32 bit one.
  _________________
 MQ & Broker admin
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | mqjeff | 
			  
				|  Posted: Wed Jun 21, 2017 5:04 am    Post subject: |   |  | 
		
		  | Grand Master
 
 
 Joined: 25 Jun 2008Posts: 17447
 
 
 | 
			  
				| 
   
	| fjb_saper wrote: |  
	| 
   
	| mqjeff wrote: |  
	| I notice that your startcmd is different than your stopcmd in the service that gives you issues... 
 That is, the startcmd is /bin/ and the stopcmd is /bin64/
 
 Do you have the same issue if they match?
 |  That was the whole point of her link. Use bin64 on both and no problem.
 Use a mix and you cannot shutdown the service with the stop service command as the relevant pid is the 64 bit one and not the 32 bit one.
  |  
 Ok.
 
 I guess it's a relatively easy istake to make... but scripting every change to a qmgr should make it easier to avoid...
 _________________
 chmod  -R ugo-wx /
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | hughson | 
			  
				|  Posted: Wed Jun 21, 2017 4:07 pm    Post subject: |   |  | 
		
		  |  Padawan
 
 
 Joined: 09 May 2013Posts: 1967
 Location: Bay of Plenty, New Zealand
 
 | 
			  
				| 
   
	| mqjeff wrote: |  
	| I guess it's a relatively easy mistake to make... but scripting every change to a qmgr should make it easier to avoid... |  Agreed. That's why I thought it worth writing about. You might notice to correct the amqsstop program from bin to bin64 when migrating from pre-64-bit queue manager to post-64-bit queue manager, but because runmqtrm exists in both libraries you might not realise that there is a reason to change that too.
 
 I was actually quite surprised to discover that the bin version of runmqtrm wasn't simply a copy of the bin64 program, but is some kind of wrapper thing. Which then results in the problem exhibited. Presumably it was done to avoid some migratory problems, but it actually causes another one.
 
 Now if there was a +MQ_BIN_DIR_PATH+ replaceable insert, then you wouldn't see the problem either!!
   
 Cheers,
 Morag
 _________________
 Morag Hughson @MoragHughson
 IBM MQ Technical Education Specialist
 Get your IBM MQ training here!
 MQGem Software
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | mqjeff | 
			  
				|  Posted: Fri Jun 23, 2017 4:25 am    Post subject: |   |  | 
		
		  | Grand Master
 
 
 Joined: 25 Jun 2008Posts: 17447
 
 
 | 
			  
				| 
   
	| hughson wrote: |  
	| Now if there was a +MQ_BIN_DIR_PATH+ replaceable insert, then you wouldn't see the problem either!!  |  Would it really be that easy to set a sensible default?  It's easy to say "yes, make it 64bit"... but then you'd still have customers that might need to change it...
 
 Plus the difficulty of making that available for changing and
 ensuring that it gets set in the environment that launches servicesmaking it easy for a customer to know about  making sure that it's changeable without a full qmgr restart...  Agus eile leithid
 _________________
 chmod  -R ugo-wx /
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | fjb_saper | 
			  
				|  Posted: Fri Jun 23, 2017 4:41 am    Post subject: |   |  | 
		
		  |  Grand High Poobah
 
 
 Joined: 18 Nov 2003Posts: 20767
 Location: LI,NY
 
 | 
			  
				| 
   
	| mqjeff wrote: |  
	| ensuring that it gets set in the environment that launches servicesmaking it easy for a customer to know about  making sure that it's changeable without a full qmgr restart...  Agus eile leithid
 |  Wow Scottish Gaelic none the less... (and other such [things]) !!!
  _________________
 MQ & Broker admin
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | mqjeff | 
			  
				|  Posted: Fri Jun 23, 2017 4:48 am    Post subject: |   |  | 
		
		  | Grand Master
 
 
 Joined: 25 Jun 2008Posts: 17447
 
 
 | 
			  
				| 
   
	| fjb_saper wrote: |  
	| Wow Scottish Gaelic none the less... (and other such [things]) !!!  |  
   And if I were responding to you, I could have badly put it en francáis
 _________________
 chmod  -R ugo-wx /
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | bruce2359 | 
			  
				|  Posted: Fri Jun 23, 2017 4:53 am    Post subject: |   |  | 
		
		  |  Poobah
 
 
 Joined: 05 Jan 2008Posts: 9486
 Location: US: west coast, almost. Otherwise, enroute.
 
 | 
			  
				| Sic transit gloria mundi. _________________
 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 |  | 
		
		  |  | 
		
		  | mqjeff | 
			  
				|  Posted: Fri Jun 23, 2017 4:58 am    Post subject: |   |  | 
		
		  | Grand Master
 
 
 Joined: 25 Jun 2008Posts: 17447
 
 
 | 
			  
				| 
   
	| bruce2359 wrote: |  
	| Sic transit gloria mundi. |  veni vidi vino
 _________________
 chmod  -R ugo-wx /
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | exerk | 
			  
				|  Posted: Fri Jun 23, 2017 5:05 am    Post subject: |   |  | 
		
		  |  Jedi Council
 
 
 Joined: 02 Nov 2006Posts: 6339
 
 
 | 
			  
				| 
   
	| mqjeff wrote: |  
	| 
   
	| bruce2359 wrote: |  
	| Sic transit gloria mundi. |  veni vidi vino
 |  Dulce et decorum est...
 _________________
 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 |  | 
		
		  |  | 
		
		  | hughson | 
			  
				|  Posted: Fri Jun 23, 2017 3:53 pm    Post subject: |   |  | 
		
		  |  Padawan
 
 
 Joined: 09 May 2013Posts: 1967
 Location: Bay of Plenty, New Zealand
 
 | 
			  
				| 
   
	| mqjeff wrote: |  
	| 
   
	| hughson wrote: |  
	| Now if there was a +MQ_BIN_DIR_PATH+ replaceable insert, then you wouldn't see the problem either!!  |  Would it really be that easy to set a sensible default?  It's easy to say "yes, make it 64bit"... but then you'd still have customers that might need to change it.
 |  Are any of the SERVICE object replaceable inserts changeable today? You don't have to use them of course, you can just type in the path yourself if you want.
 
 And, I guess you can always make up your own one to put in the service.env file.
 
 Cheers,
 Morag
 _________________
 Morag Hughson @MoragHughson
 IBM MQ Technical Education Specialist
 Get your IBM MQ training here!
 MQGem Software
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | mqjeff | 
			  
				|  Posted: Mon Jun 26, 2017 3:57 am    Post subject: |   |  | 
		
		  | Grand Master
 
 
 Joined: 25 Jun 2008Posts: 17447
 
 
 | 
			  
				| 
   
	| hughson wrote: |  
	| Are any of the SERVICE object replaceable inserts changeable today? You don't have to use them of course, you can just type in the path yourself if you want. |  I've no idea if they're changeable or not.  Certainly some of them shouldn't be...
 
 
 
   
	| hughson wrote: |  
	| And, I guess you can always make up your own one to put in the service.env file. |  ... and now I wonder if you could override the base ones this way. But thinking about it, it's probably too late by then. The service launch process has already replaced the +constants+
 _________________
 chmod  -R ugo-wx /
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  |  |