| Author |
Message
|
| mrlazy |
 Posted: Wed Jun 21, 2006 10:46 am Post subject: AMQ4036 |
 |
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
Hi all,
When I try to remotely administer a queue manager, I get the AMQ4036 error. We have this queue manager located on AIX machine. It's command server is up and running. The SYSTEM.ADMIN.SVRCONN channel is defined. Is there anything else that I should be looking into?
I was able to remotely administer the other queue managers in the same network, but not this one. |
|
| Back to top |
|
 |
| vennela |
| Posted: Wed Jun 21, 2006 10:48 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
What tool are you using to remotely adminsiter
Can you client connect to that QMGR? |
|
| Back to top |
|
|
| mrlazy |
| Posted: Wed Jun 21, 2006 10:59 am Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
I'm using MQExplorer.
I tried rfhutilc now to check client connection, but the reason code 2059 is being displayed.
I have one question vennela. Do we have to set the authorizations using setmqaut, even for remote administration?(I'm sorry if it's a stupid question!) |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Jun 21, 2006 11:01 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| mrlazy wrote: |
I'm using MQExplorer.
I tried rfhutilc now to check client connection, but the reason code 2059 is being displayed.
|
Is the listener running?
| mrlazy wrote: |
| I have one question vennela. Do we have to set the authorizations using setmqaut, even for remote administration?(I'm sorry if it's a stupid question!) |
Oh yeah |
|
| Back to top |
|
|
| mrlazy |
| Posted: Wed Jun 21, 2006 11:22 am Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
Yes the listener is also running.
The reason why asked about authorizations is because, even though I can access the production queue manager, I don't see my local ID/domain being in the mqm group on remote queue manager.
Can the firewall be an issue in such cases? |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Jun 21, 2006 11:47 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Yes firewall can be an issue |
|
| Back to top |
|
|
| mrlazy |
| Posted: Wed Jun 21, 2006 12:00 pm Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
I asked my AIX administrators about the firewall issue, but they said that when I was able to access another queue manager in this network, I should be able to access even for the one which I'm trying to.
So I guess something from MQ side is missing.
Please let me know anything else that I should be looking into??
Remote QMgr: Up and Running.
Command Server: Up and Running
Listener: Up and running
SYSTEM.ADMIN.SVRCONN chanel defined on remote queue manager. |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Jun 21, 2006 12:34 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
try amqsputc
or
telnet remoteserver portno |
|
| Back to top |
|
|
| mrlazy |
| Posted: Wed Jun 21, 2006 1:01 pm Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
I was able to connect when did "telnet remote server 5010".
I made sure this from AIX admin too. |
|
| Back to top |
|
|
| mrlazy |
| Posted: Thu Jun 22, 2006 6:51 am Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
Vennela,
Do I need change the 'MCA User' attribute for the SVRCONN channel so that I can remotely access the queue manager?
Please help me in this regard. I have been looking into all sorts of documents, but could not figure out why we are unable to access. |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Jun 22, 2006 7:51 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| 2059 is usually not returned for security. It is usually if the listener is not running on that QMGR. |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Jun 22, 2006 8:43 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
try seeing if you can connect with the sample program amqscnxc. Also, have you looked at the MQ logs on the AIX machine?
_________________
-wayne |
|
| Back to top |
|
|
| mrlazy |
| Posted: Thu Jun 22, 2006 8:55 am Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
wschutz,
I tried the sample program, but was not able to connect.
$ amqscnxc -x hostname -c SYSTEM.ADMIN.SVRCONN FMCQM
Sample AMQSCNXC start
Connecting to queue manager FMCQM
using the server connection channel SYSTEM.ADMIN.SVRCONN
on connection name hostname.
MQCONNX ended with reason code 2059
$ mqrc 2059
2059 0x0000080b MQRC_Q_MGR_NOT_AVAILABLE
$ dspmq
QMNAME(FMCQM) STATUS(Running)
$ ps -ef | grep runmqlsr
mqm 254158 688172 0 12:04:07 pts/3 0:00 grep runmqlsr
fmc 573568 1 0 Jun 15 - 0:00 runmqlsr -m FMCQM -t TCP -p 5010
$ netstat -an | grep 5010
tcp4 0 0 *.5010 *.* LISTEN
$ dspmqcsv FMCQM
WebSphere MQ Command Server Status . . : Running
Still the same. What else do you think might be missing from my side?
Last edited by mrlazy on Thu Jun 22, 2006 9:05 am; edited 1 time in total |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Jun 22, 2006 8:57 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| wschutz wrote: |
| Also, have you looked at the MQ logs on the AIX machine? |
_________________
-wayne |
|
| Back to top |
|
|
| mrlazy |
| Posted: Thu Jun 22, 2006 9:08 am Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
I cheked the error logs for FMCQM. I do not see any messages dated today. The last message was yesterday's.
That too because the web-client connection was lost yesterday for some reason.
Heres the only error in FDC error log date today which i beleive might some thing else coz of port number:
06/22/06 11:52:01
AMQ9202: Remote host 'hostname(10.xx.xx.xxx) (1414)' not available, retry
later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'hostname
(10.xx.xx.xxx) (1414)' was not successful. However the error may be a
transitory one and it may be possible to successfully allocate a TCP/IP
conversation later.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
78 (X'4E'). The reason for the failure may be that this host cannot reach the
destination host. It may also be possible that the listening program at host
'hostname(10.xx.xx.xxx) (1414)' was not running. If this is the case,
perform the relevant operations to start the TCP/IP listening program, and try
again.
----- amqccita.c : 973 -------------------------------------------------------- |
|
| Back to top |
|
|
|
|
