| Author |
Message
|
| genius_in_making |
 Posted: Tue Apr 25, 2006 11:22 pm Post subject: queue manager port number on AIX |
 |
|
Novice
Joined: 23 Feb 2006
Posts: 14
|
Hi All,
Our WMQ server is running on AIX. Now I want to find out the
port number of one particular queue manager running on AIX.
Kindly help |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Apr 26, 2006 12:01 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Check the attributes of the listeners associated with the queue manager.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Apr 26, 2006 2:12 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
What version of MQ?
If V6... "DISPLAY LSSTATUS(*) ALL"
If v5.3, you need to use "netstat".
_________________
-wayne |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Apr 26, 2006 3:28 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| wschutz wrote: |
What version of MQ?
If V6... "DISPLAY LSSTATUS(*) ALL"
If v5.3, you need to use "netstat". |
netstat -an will tell you if there is a process listening on a specific port. It won't tell you what that process is.
Or if using runmqlsr :
| Code: |
| ps -ef | grep runmqlsr |
if using inetd the information needs to be gathered from different sources:
/etc/inetd.conf
/etc/services
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Kateel |
| Posted: Wed May 03, 2006 1:12 pm Post subject: |
|
|
Novice
Joined: 01 May 2006
Posts: 17
|
Wayne,
I guess lsstatus lists only MQ defined ports(runmqlsr). Is there anyway we can check TCP ports as well using this command? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed May 03, 2006 3:25 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
There's no such thing as an "mq defined port". LSStatus shows you the status of MQ listeners, including the port they are using. These ports can be TCP/IP ports or LU6.2 ports or any other transport that the MQ listeners support.
Almost all of the other posts in this thread contain the word "netstat". I guess you don't know what that is - but it's not an MQ command. Most people consider "google" to be a good way to find out about stuff they don't know about, and I bet if you used "google" to ask about 'netstat', you'd get information yourself.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Kateel |
| Posted: Thu May 04, 2006 4:46 am Post subject: |
|
|
Novice
Joined: 01 May 2006
Posts: 17
|
Thanks Jeff,
Please correct me if i am wrong,
A MQ listener port can be setup using 2 ways. 1 using runmqlsr and 2 using TCP ports(inetd.conf and services in UNIX).
I guess TCP ports are more reliable from admin's point of view. But when we are using multiple QMs we can't differntiate between which port belongs to what. There is noway to know by checking in the QM box (/etc/services and /etc/inetd.conf files says nothing about this). And the listener port assumes that anything coming to it will explicitly specify the desstination QM as well.
And LSSTATUS doesnot list TCP ports. It can only be checked using /etc/services file. |
|
| Back to top |
|
|
| vennela |
| Posted: Thu May 04, 2006 4:57 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Kateel wrote: |
| And LSSTATUS doesnot list TCP ports. |
I haven't tried that command but I'll believe you that it will not list the inetd listeners.
With 5.3 and above, it is recommended to use runmqlsr.
| Kateel wrote: |
| It can only be checked using /etc/services file. |
I know atleast two other ways (not being a root) on AIX -- lsof and rmsock.
I am pretty sure there are many more. |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Thu May 04, 2006 5:24 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
| Kateel wrote: |
Thanks Jeff,
Please correct me if i am wrong,
A MQ listener port can be setup using 2 ways. 1 using runmqlsr and 2 using TCP ports(inetd.conf and services in UNIX). |
They both use TCP/IP ports. RUNMQLSR is a started program which is bound to a specific port. INETD listens to multiple ports and starts a program when traffic arrives on that port (ie. amqcrsta).
| Quote: |
| I guess TCP ports are more reliable from admin's point of view. |
Who? Which Admin? IBM strongly recommends the use of RUNMQLSR over INETD as of MQ v5.3.
| Quote: |
| But when we are using multiple QMs we can't differntiate between which port belongs to what. There is noway to know by checking in the QM box (/etc/services and /etc/inetd.conf files says nothing about this). And the listener port assumes that anything coming to it will explicitly specify the desstination QM as well. |
I'm not sure I understand this. Whichever you use, you should be able to tell which queue manager has which port.
INETD (assuming you've named your entries beginning with MQSeries):
/etc>more /etc/inetd.conf | grep MQSeries
MQSeries stream tcp nowait mqm /usr/mqm/bin/amqcrsta amqcrsta -m <qmgr_name>
MQSeries2 stream tcp nowait mqm /usr/mqm/bin/amqcrsta amqcrsta -m <qmgr_name2>
/etc>more /etc/services | grep MQSeries
MQSeries 1414/tcp # MQSeries listener for qmgr_name
MQSeries2 1415/tcp # MQSeries listener for qmgr_name2
RUNMQLSR:
mqm:/home/mqm> ps -fe | grep runmqlsr
mqm 13049 1 0 May 01 ? 0:00 /usr/mqm/bin/runmqlsr -t tcp -p1427 -b64 -m qmgr_name
mqm 13083 1 0 May 01 ? 0:00 /opt/mqm/bin/runmqlsr -t tcp -p1431 -b64 -m qmgr_name2
| Quote: |
| And LSSTATUS doesnot list TCP ports. It can only be checked using /etc/services file. |
DIS LSSTATUS will only dis listeners that are either a) defined to MQ using the DEFINE LISTENER command or b) started using RUNMQLSR. But it will show you the port.
AMQ8631: Display listener status details.
LISTENER(LISTENER.TCP) STATUS(RUNNING)
PID(3964) STARTDA(2006-05-04)
STARTTI(08.12.31) DESCR( )
TRPTYPE(TCP) CONTROL(QMGR)
IPADDR(*) PORT(1414)
BACKLOG(100)
Steve |
|
| Back to top |
|
|
|
|
