| Author | Message | 
		
		  | ankurlodhi | 
			  
				|  Posted: Mon Aug 22, 2011 9:34 am    Post subject: How to check the name of Listeners in MQ 5.3 |   |  | 
		
		  | Master
 
 
 Joined: 19 Oct 2010Posts: 266
 
 
 | 
			  
				| we have an old test box with MQ 5.3, and i dont know how many listeners are existing on that box and what are there names. 
 any suggestions what i can do. cause i have to replicate its channel configuration on 7.0 MQ and need to identify the boxes it is communicating with.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | mqjeff | 
			  
				|  Posted: Mon Aug 22, 2011 9:40 am    Post subject: |   |  | 
		
		  | Grand Master
 
 
 Joined: 25 Jun 2008Posts: 17447
 
 
 | 
			  
				| Listeners don't have names in MQ v5.3.  They are not MQSC or otherwise MQ objects, they are merely standalone programs that were started by runmqlsr. 
 Just use saveqmgr to save the qmgr definitions, and filter/review the channels.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | ankurlodhi | 
			  
				|  Posted: Mon Aug 22, 2011 9:48 am    Post subject: |   |  | 
		
		  | Master
 
 
 Joined: 19 Oct 2010Posts: 266
 
 
 | 
			  
				| that means once after starting the channels and listeners i just have to use saveqmgr.. |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | mqjeff | 
			  
				|  Posted: Mon Aug 22, 2011 9:51 am    Post subject: |   |  | 
		
		  | Grand Master
 
 
 Joined: 25 Jun 2008Posts: 17447
 
 
 | 
			  
				| No. 
 It means you need to make sure the v5.3 qmgr is running and has an active command server.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | exerk | 
			  
				|  Posted: Mon Aug 22, 2011 11:14 am    Post subject: |   |  | 
		
		  |  Jedi Council
 
 
 Joined: 02 Nov 2006Posts: 6339
 
 
 | 
			  
				| If it's Windows then check MQ Services as they'll be defined there, if it's UNIX it will be either as mqjeff states or possibly within inetd (check for WMQ-related entries). _________________
 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 |  | 
		
		  |  | 
		
		  | mqjeff | 
			  
				|  Posted: Mon Aug 22, 2011 11:17 am    Post subject: |   |  | 
		
		  | Grand Master
 
 
 Joined: 25 Jun 2008Posts: 17447
 
 
 | 
			  
				| But mq listeners provide no information about what machines a given queue manager is communicating with. 
 They only describe what ports are in use for receiving MQ traffic.
 
 It is simply and only the channels that tell what other qmgrs are being talked to.  And the only way to get information on these is through PCF or MQSC commands - both of which require the qmgr to be running.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | exerk | 
			  
				|  Posted: Mon Aug 22, 2011 11:32 am    Post subject: |   |  | 
		
		  |  Jedi Council
 
 
 Joined: 02 Nov 2006Posts: 6339
 
 
 | 
			  
				| 
   
	| mqjeff wrote: |  
	| But mq listeners provide no information about what machines a given queue manager is communicating with. |  One of my doh moments again - me shooting from the lip again!
   
 Apologies Jeff, I didn't read the OP properly...
 _________________
 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 |  | 
		
		  |  | 
		
		  | gbaddeley | 
			  
				|  Posted: Mon Aug 22, 2011 8:34 pm    Post subject: Re: How to check the name of Listeners in MQ 5.3 |   |  | 
		
		  |  Jedi Knight
 
 
 Joined: 25 Mar 2003Posts: 2538
 Location: Melbourne, Australia
 
 | 
			  
				| 
   
	| ankurlodhi wrote: |  
	| we have an old test box with MQ 5.3, and i dont know how many listeners are existing on that box and what are there names. 
 any suggestions what i can do. cause i have to replicate its channel configuration on 7.0 MQ and need to identify the boxes it is communicating with.
 |  
 MQ 5.3 on Unix?  ps -ef | grep runmqlsr will display the running listener processes. If there are none running, inetd is being used as the MQ listener instead, so you need to look in /etc/services and /etc/inetd.conf for MQ related config entries.  eg. port range >= 1414 and program name amqcrsta.
 
 Migrate to LISTENER objects in MQ 7 !
 _________________
 Glenn
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | gbaddeley | 
			  
				|  Posted: Mon Aug 22, 2011 8:53 pm    Post subject: Re: How to check the name of Listeners in MQ 5.3 |   |  | 
		
		  |  Jedi Knight
 
 
 Joined: 25 Mar 2003Posts: 2538
 Location: Melbourne, Australia
 
 | 
			  
				| 
   
	| ankurlodhi wrote: |  
	| ...cause i have to replicate its channel configuration on 7.0 MQ and need to identify the boxes it is communicating with. |  Look in the Queue Manager's error logs for channel start / end messages. This will only go back as far as the oldest message in AMQERR03.LOG, which could be a very long time or quite recent.
 _________________
 Glenn
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | luisasettea | 
			  
				|  Posted: Mon Aug 22, 2011 9:34 pm    Post subject: General WebSphere MQ Support |   |  | 
		
		  | Newbie
 
 
 Joined: 22 Aug 2011Posts: 1
 
 
 | 
			  
				| In MQ 5.3 dodges throughout check the name. When can the naming mill stamp after the charge? Why can't in MQ 5.3 transport the ham? A horse paces? Check the name pulps in MQ 5.3 before an admitted water. Check the name quits the percent bottle inside her grandfather. 
 ----------------------------------------------------------------
 
 SPAMMER! - site admin informed and awaiting action.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | ankurlodhi | 
			  
				|  Posted: Tue Aug 23, 2011 10:09 am    Post subject: |   |  | 
		
		  | Master
 
 
 Joined: 19 Oct 2010Posts: 266
 
 
 | 
			  
				| when i tried ps-ef | grep runmqlsr i didn't get any thing 
 so i tried looking it into the /etc inted.conf there i got this can anyone explane what this mean
 
 MQSeries stream tcp nowait mqm /opt/mqm/bin/amqcrsta amqcrsta
 # MDMN_COMMD - SVM Multi Node Communication Daemon
 100422/1      tli     rpc/tcp wait    root    /usr/sbin/rpc.mdcommd   rpc.mdcommd
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | Vitor | 
			  
				|  Posted: Tue Aug 23, 2011 10:23 am    Post subject: |   |  | 
		
		  |  Grand High Poobah
 
 
 Joined: 11 Nov 2005Posts: 26093
 Location: Texas, USA
 
 | 
			  
				| 
   
	| ankurlodhi wrote: |  
	| i got this can anyone explane what this mean |  
 The sys admin for the box can.
 
 I do still wonder what the listeners on this box has to do with it's channel configuration.
 _________________
 Honesty is the best policy.
 Insanity is the best defence.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | exerk | 
			  
				|  Posted: Tue Aug 23, 2011 10:25 am    Post subject: |   |  | 
		
		  |  Jedi Council
 
 
 Joined: 02 Nov 2006Posts: 6339
 
 
 | 
			  
				| OK. Now look in the etc/services file for WMQ-related entries, which should contain the IP Port number. Make sure those entries are not replicated to your WMQ V7.0 server but make use of listener objects. _________________
 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 |  | 
		
		  |  | 
		
		  | ankurlodhi | 
			  
				|  Posted: Tue Aug 23, 2011 10:38 am    Post subject: |   |  | 
		
		  | Master
 
 
 Joined: 19 Oct 2010Posts: 266
 
 
 | 
			  
				| sry i didn't mensioned that it is a solaris box so i used the ps-ef |grep -i mqm  command which gave me the below result
 
 $ ps -ef |grep -i mqm
 mqm 27842 27690  0 14:15:56 pts/2    0:00 grep -i mqm
 mqm 27690 27688  0 13:59:27 pts/2    0:00 -ksh
 mqm 28472 28467  0   Aug 16 ?        0:00 /opt/mqm/bin/amqzdmaa -m Qmanager1
 mqm  7794  7788  0   Jul 19 ?        0:00 /opt/mqm/bin/runmqchi -m Qmanager2
 mqm 28474 28467  0   Aug 16 ?        0:00 amqzlaa0 –m Qmanager1 -fip0
 mqm  7795  7788  0   Jul 19 ?        1:17 amqzlaa0 -m Qmanager2 -fip0
 mqm  7788     1  0   Jul 19 ?        7:33 amqzxma0 -m Qmanager2
 mqm  7804     1  0   Jul 19 ?        0:01 amqpcsea Qmanager2
 mqm  7790  7788  0   Jul 19 ?        0:01 amqhasmx Qmanager2/var/mqm
 mqm 28471 28467  0   Aug 16 ?        0:00 /opt/mqm/bin/amqrrmfa -m -t2332800 -s2592000 -p2592000 -g5184000 -c36
 mqm 27839  7788  0 14:15:21 ?        0:00 amqzlaa0 –m Qmanager2-fip43350
 mqm 28468 28467  0   Aug 16 ?        0:00 /opt/mqm/bin/amqzfuma -m Qmanager1
 mqm 27688 27685  0 13:59:26 ?        0:00 /usr/lib/ssh/sshd
 mqm 28473 28467  0   Aug 16 ?        0:00 /opt/mqm/bin/runmqchi -m Qmanager1     mqm  7791  7788  0   Jul 19 ?        0:02 amqzllp0 –m Qmanager2?
 mqm  7789  7788  0   Jul 19 ?        0:00 /opt/mqm/bin/amqzfuma -m Qmanager2
 mqm  7792  7788  0   Jul 19 ?        0:00 /opt/mqm/bin/amqrrmfa -m Qmanager2-t2332800 -s2592000 -p2592000 -g5184000 -c36
 mqm 28470 28467  0   Aug 16 ?        0:00 amqzllp0 –m Qmanager1?
 mqm 27838   614  1 14:15:19 ?        0:02 amqcrsta
 mqm 28469 28467  0   Aug 16 ?        0:01 amqhasmx Qmanager1/var/mqm
 mqm 28467     1  0   Aug 16 ?        0:05 amqzxma0 -m Qmanager1
 mqm 27841 27690  0 14:15:56 pts/2    0:00 ps -ef
 mqm  7793  7788  0   Jul 19 ?        0:00 /opt/mqm/bin/amqzdmaa -m Qmanager2
 
 
 I have changed the name of queue manager for privicy
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | Vitor | 
			  
				|  Posted: Tue Aug 23, 2011 10:45 am    Post subject: |   |  | 
		
		  |  Grand High Poobah
 
 
 Joined: 11 Nov 2005Posts: 26093
 Location: Texas, USA
 
 | 
			  
				| 
   
	| ankurlodhi wrote: |  
	| sry i didn't mensioned that it is a solaris box so i used the ps-ef |grep -i mqm  command which gave me the below result
 |  
 Ok, I'm now really confused.
 
 a) What has the list of running processes got to do with anything connected to the configuration of the queue manager?
 b) Why the sudden switch from network configuration to active processes?
 c) What has any of this got to do with the question you originally posted?
 _________________
 Honesty is the best policy.
 Insanity is the best defence.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  |  |