| Author | Message | 
		
		  | yshakraj | 
			  
				|  Posted: Wed Dec 18, 2019 3:44 am    Post subject: CCDT file active QM connection details |   |  | 
		
		  |  Voyager
 
 
 Joined: 14 Sep 2011Posts: 91
 
 
 | 
			  
				| Hello All , 
 I have been working on the MUltiInstance MQ set up and shared the CCDT Fiel to the client application team .
 They are able to connect  as well .however we have a requirement to find out which QM is active now , and need to log the host and port number in the client application logs .
 
 I got this - "Which namelist is it that you wish to inquire details of? I don't know of a namelist that lists the multi-instance MQ Queue Manager's addresses and ports. You are getting reason code 2067 (MQRC_SELECTOR_ERROR) because MQCA_NAMELIST_NAME is not a queue manager attribute, it is a namelist attribute. You would need to open the namelist for MQOO_INQUIRE. However, the real question is "Which Namelist?"
 
 from another forum - does anyone can help me identify the MQ object that really holds the connection details .
 
 ps- https://stackoverflow.com/questions/57609994/mq-get-multi-instance-mq-manager-connection-list
 
 Thanks in advance ,
 yshak
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | HubertKleinmanns | 
			  
				|  Posted: Wed Dec 18, 2019 4:53 am    Post subject: |   |  | 
		
		  |  Shaman
 
 
 Joined: 24 Feb 2004Posts: 732
 Location: Germany
 
 | 
			  
				| You could inquire the channel status of your SVRCONN channel and look for the attribute CONNAME. _________________
 Regards
 Hubert
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | fjb_saper | 
			  
				|  Posted: Wed Dec 18, 2019 5:49 am    Post subject: |   |  | 
		
		  |  Grand High Poobah
 
 
 Joined: 18 Nov 2003Posts: 20767
 Location: LI,NY
 
 | 
			  
				| 
   
	| HubertKleinmanns wrote: |  
	| You could inquire the channel status of your SVRCONN channel and look for the attribute CONNAME. |  The conname attribute really only gives you the address you're connecting from. What the OP is after would be the LOCLADDR field that shows the address and port that was connected to, ie the qmgr's IP and the listener port.
 Hope this helps
  _________________
 MQ & Broker admin
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | bruce2359 | 
			  
				|  Posted: Wed Dec 18, 2019 6:38 am    Post subject: Re: CCDT file active QM connection details |   |  | 
		
		  |  Poobah
 
 
 Joined: 05 Jan 2008Posts: 9486
 Location: US: west coast, almost. Otherwise, enroute.
 
 | 
			  
				| 
   
	| yshakraj wrote: |  
	| ... we have a requirement to find out which QM is active now , and need to log the host and port number in the client application logs. |  What do you mean by "active?"
 
 By "active now" do you mean the name of the qmgr the application has successfully connected to?  Or, do you mean the names of the qmgrs that are defined in the CCDT, and which are currently running?
 _________________
 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 |  | 
		
		  |  | 
		
		  | yshakraj | 
			  
				|  Posted: Wed Dec 18, 2019 7:20 am    Post subject: |   |  | 
		
		  |  Voyager
 
 
 Joined: 14 Sep 2011Posts: 91
 
 
 | 
			  
				| Thanks for your response . 
 By "active now" - I meant the current connection from client application to the Queue manager .
 
 basically I am after the connection details like server name and port .
 
 In-case of multi-instance QM - we have two servers one will be active and other one as stand by , so when client application connects to primary if it fails it connect to standby one .So there is a possibility of two connections .
 We need to know which connection is active now from application side .
 
 Client application  use PCF Agent , MQ queuemanager object etc .(not sure this makes sense here...)
 
 Thanks again ,
 yshakraj
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | yshakraj | 
			  
				|  Posted: Wed Dec 18, 2019 7:24 am    Post subject: |   |  | 
		
		  |  Voyager
 
 
 Joined: 14 Sep 2011Posts: 91
 
 
 | 
			  
				| 
   
	| Code: |  
	| ie the qmgr's IP and the listener port
 
 
 |  
 Thats correct
  |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | bruce2359 | 
			  
				|  Posted: Wed Dec 18, 2019 9:39 am    Post subject: |   |  | 
		
		  |  Poobah
 
 
 Joined: 05 Jan 2008Posts: 9486
 Location: US: west coast, almost. Otherwise, enroute.
 
 | 
			  
				| Why the requirement?  What purpose? _________________
 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 |  | 
		
		  |  | 
		
		  | hughson | 
			  
				|  Posted: Wed Dec 18, 2019 2:02 pm    Post subject: |   |  | 
		
		  |  Padawan
 
 
 Joined: 09 May 2013Posts: 1967
 Location: Bay of Plenty, New Zealand
 
 | 
			  
				| You could make use of MQCNO_CD_FOR_OUTPUT_ONLY. This fills in the MQCD structure with the choice made from the CCDT. It was provided so that applications making two connections could guarantee that they both went to the same place, even if a CCDT was in use. However, it also serves to tell the application where the connection was made to. 
 Cheers,
 Morag
 _________________
 Morag Hughson @MoragHughson
 IBM MQ Technical Education Specialist
 Get your IBM MQ training here!
 MQGem Software
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  |  |