| Author |
Message
|
| Cogito-Ergo-Sum |
 Posted: Fri Feb 10, 2006 10:45 am Post subject: RFHUTILC could not connect to Queue manager. |
 |
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
Hi,
I hope, I have the right forum. I have also searched the fora for any hints but have failed in getting a helpful link.
When I am trying to connect to a Queue Manager defined on IBM Websphere MQ V6.0 on my desktop, using rfhutilc on my laptop, I get a message,
| Quote: |
| 2059 Queue manager not available [Connect] - may not be started |
What could be the reason? Where do I begin?
For MQSERVER environment variable, on the laptop, I have used the client connection channel (defined on desktop), TCP, the IP address and port number of the Queue manager. This value of MQSERVER is also present in desktop.
When I am using rfhutil on desktop I am able to connect to the same queue manager successfully.
Both machines are on WinXP.
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Feb 10, 2006 10:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
First, make sure that the MQSERVER variable is actually in effect for rfhutilc.
The easiest way to do this is start a command shell, confirm the variable is set, and then start rfhutilc.
Then confirm that the variable is correct, using amqscnxc.
Then look for errors in the client install directory, and then errors on the server.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Fri Feb 10, 2006 11:22 am Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
| Quote: |
| First, make sure that the MQSERVER variable is actually in effect for rfhutilc. |
This is confirmed.
| Quote: |
The easiest way to do this is start a command shell, confirm the variable is set, and then start rfhutilc.
|
RFHUTILC comes up.
| Quote: |
| Then confirm that the variable is correct, using amqscnxc. |
I am getting RC as 2059, MQRC_Q_MGR_NOT_AVAILABLE.
I am unable to locate the log file under IH03 folder where I had unzipped the IH03 support pac.
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Fri Feb 10, 2006 11:23 am Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
Also, even though I have tried starting SYSTEM.DEF.SVRCONN, it always remains in an inactive status. Could this be a reason....?
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
|
| KramJ |
| Posted: Fri Feb 10, 2006 11:30 am Post subject: |
|
|
Voyager
Joined: 09 Jan 2006
Posts: 80
Location: Atlanta
|
| Do you have the listener running on the queue manager, listening on the correct port? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Feb 10, 2006 11:33 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Cogito-Ergo-Sum wrote: |
| I am unable to locate the log file under IH03 folder where I had unzipped the IH03 support pac. |
I meant in the MQ client installation folder, not the IH03 folder.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Fri Feb 10, 2006 11:37 am Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
| Quote: |
| Do you have the listener running on the queue manager, listening on the correct port? |
When I defined the queue manager, I gave the port as 1416 whereas the LISTENER.TCP is listening at 1414. If I give port number as 1414 as the port number for MQSERVER on my laptop, I get a 'Not authorized' message.
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
|
| JT |
| Posted: Fri Feb 10, 2006 11:51 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| Also, even though I have tried starting SYSTEM.DEF.SVRCONN, it always remains in an inactive status. Could this be a reason....? |
No, stop doing it, it's pointless. The channel will go active when you successfully connect to the queue manager.
| Quote: |
| I get a 'Not authorized' message. |
Good, now at least you're connected to the queue manager. Since this error has been previously discussed, ad nauseam, search this site for '2035', and heed the advice. |
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Fri Feb 10, 2006 12:16 pm Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
Here is what I have in the log:
| Quote: |
2/11/2006 01:32:31
AMQ9202: Remote host 'mycomputer (n.n.n.n) (1416)' not available, retry
later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'nsubrahm
(n.n.n.n) (1416)' 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
10061 (X'274D'). 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 'mycomputer (n.n.n.n) (1416)' was not running. If this is the case,
perform the relevant operations to start the TCP/IP listening program, and try
again. |
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Feb 10, 2006 12:19 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
That tells you what you found out with amqscnx - you aren't using the right port.
When you switched to using the port that the listener was using, then you got a different error - which was MQRC_NOT_AUTHORIZED.
So now you have to figure out how to set mq authorities so that your user can connect to the queue manager and the queue and can put and get from the right queues.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Sat Feb 11, 2006 12:45 am Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
jefflowery,
I have gone through the System Administrator chapter in the MQ Clients manual. One of the reasons as suggested in the manual seems to be the issue with a userid having the @ symbol. In my case, it is NOT so.
I am checking the threads in this forum wrt 2035 MQRC now.
Thanks to everyone who responded.
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
|
|
|
