| Author |
Message
|
| jeevan |
 Posted: Wed Jan 31, 2007 9:52 am Post subject: Missing AMQSPUTC in MQ version 6.0 |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
I am working on MQ6.0 at client place. When I try to put message from client setting( set the mqserver env), but I did not find the AMQSPUTC utility. Can some one please tell me whether this utility is available in the v6 or not? If not, is there any other utility I can use to test message from client to server.
thanks a lot |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Jan 31, 2007 10:04 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It's there, but they probably didn't install it.
It's only installed with the samples.
If they didn't install the samples, you may not have much luck otherwise.
If you're on windows, you can use RHFutilC from IH03.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jeevan |
| Posted: Wed Jan 31, 2007 11:39 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
Jeff,
I fixed that installing client which has not been installed before. However, I am getting 2058 in running
AMQSPUTC Q QMGR
command
I have run listener in the queue manager
i have set up envirnmental variable - MQSERVER
AMQSPUT works fine. when i changed to amqsputc it give 2058. Nothing has been changed.
Also, i can not put message using rfhutil. when i try to write it says, invalid qmgr. as I said all setup is done, listener is running and env variable has been setup.
I would really appreciate your help
thanks |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Wed Jan 31, 2007 11:42 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
There is likely something misconfigured somewhere. I would start with your MQSERVER variable.
Post a bit more info (contents of the server variable, queue manager name, port, etc).
Steve |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jan 31, 2007 11:43 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Make sure you use rfhutilC. It's an easy mistake to make.
Second, in RFHUTILC, enter the contents of MQSERVER as the qmgr name. So, "SYSTEM.DEF.SVRCONN/TCP/hostname(port#)", for example. Then you can check the connectivity by using the "Load Names" button.
2058 means you've connected to a queue manager using the wrong name.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jeevan |
| Posted: Wed Jan 31, 2007 1:01 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
This is exact setup on remote server,
listener is running
command server is running
qmgr is running
( test locally putting message using amqsput and it works fine)
On the client,
set MQSERVER=SYSTEM.DEF.SVRCONN/TCP/192.168.1.110(1429)
when i run rfhutilc and set up
qmgr: remote qmgr
queue: the queue in the remote queue manager
and click write to queue, it gives the following error
15.50.37 2058 Queue manager invalid (Connect)
15.50.36 423 bytes read from file C:\Documents and Settings\xxxxx\Desktop\as400.txt
I would appreciate any insight. I am planning to redo everthing again.
thanks a lot |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jan 31, 2007 1:03 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Again, you should be putting exactly "SYSTEM.DEF.SVRCONN/TCP/192.168.1.110(1429)" into the the Queue Manager field in RFHUTILC.
Then click list names.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Jan 31, 2007 1:04 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| jeevan wrote: |
| I am getting 2058 |
Probably the qmgr name in the MQCONN or MQCONNX call does not match the name of the qmgr listening on the port you specify (1429). |
|
| Back to top |
|
|
| jeevan |
| Posted: Wed Jan 31, 2007 1:20 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| mvic wrote: |
| jeevan wrote: |
| I am getting 2058 |
Probably the qmgr name in the MQCONN or MQCONNX call does not match the name of the qmgr listening on the port you specify (1429). |
No.
Because i use the name from a test file, to avoid the error in typo. Also, it works in
anqsput. So, it seems but it is not that for sure. I am pasting the screen shot soon.
thanks |
|
| Back to top |
|
|
| jeevan |
| Posted: Thu Feb 01, 2007 6:58 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
I fixed it. The problem was there was firewall in one of the computers. I tested pinging and telnet to host port, and it worked. But this morming when tried pinging from otherside, it timed out. So when i checked, there was firewall on.
Thank you for all your inputs and helps |
|
| Back to top |
|
|
| mvic |
| Posted: Thu Feb 01, 2007 7:02 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| jeevan wrote: |
| The problem was there was firewall |
In this case the most usual rc from MQCONN is 2059, so I'm surprised. Anyway, I'm glad you got it working. |
|
| Back to top |
|
|
| jeevan |
| Posted: Thu Feb 01, 2007 7:12 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
Occassionally, i got 2059 too but mostly it was 2058. I am wondering too. I am also able to connect to remote qmgr using rfhutil now.
But to my wonder, i was able to connect through the mqexplorer. Why does not firewall affect qmexplorer connection?
thanks once again, |
|
| Back to top |
|
|
|
|
