| Author |
Message
|
| bath |
 Posted: Tue Nov 23, 2004 8:01 am Post subject: MQCONN ended with reason code 2059 |
 |
|
Apprentice
Joined: 23 Nov 2004
Posts: 29
|
Hello,
please could you help me on this?
I'm new to MQseries and I'm trying to run the amqsputc program from a client machine.
I have installed MQseries server on the second machine.
I have created :
a Queue manager (MQ_a )
a queue (queue_1)
a connection server channel (S_channel)
a client connection (S_channel)
I have copied the file AMQCLCHL.TAB from the server to one directory of my client machine.
I have create two environment variables
MQCHLLIB and MQCHLTAB
my client machine is running windows 2000
my server machine is running windows XP.
i can ping from my client to my server.
but when i run the program
amqsputc queue_1 QM_a
i got an error "MQCONN ended with reason code 2059"
explaning that they may be a TCP/IP error (10060)
any help will be greatly appreciated
thanks
Roland |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Tue Nov 23, 2004 8:23 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Do you have a listener running on the qmgr machine? Try looking at the runmqlsr command. |
|
| Back to top |
|
|
| KeeferG |
| Posted: Tue Nov 23, 2004 8:23 am Post subject: |
|
|
Master
Joined: 15 Oct 2004
Posts: 215
Location: Basingstoke, UK
|
do you have the listener running on your Server on the correct port. Have you tried running the client on the server machine. Often easier to get the client working locally then porting to client machines.
_________________
Keith Guttridge
-----------------
Using MQ since 1995 |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Tue Nov 23, 2004 9:10 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
I assume this is a typo?
| Quote: |
I have created :
a Queue manager (MQ_a )
amqsputc queue_1 QM_a
|
The queue manager names don't match. |
|
| Back to top |
|
|
| bath |
| Posted: Tue Nov 23, 2004 10:05 am Post subject: |
|
|
Apprentice
Joined: 23 Nov 2004
Posts: 29
|
thank you for your answers,
i have done a mistake my queue manager is well QM_a
and i used amqsputc queue_1 QM_a .
I have checked that my listener is running. I think you see this by opening the MQservices window. there is a listener there is running
on port 1885.
i did not set this on the client machine as i copied M..TAB file to the client machine and set the environment variables.
please what about the TCP/IP KeepAlive?
i don't have and QN.ini file
apart the QM_a, queue_1 , S_channel (connection server) and S_channel
(connection client) do i have to create anything in the server machne?
is it related in anyway to MQ_user and MQ_password?
thanks |
|
| Back to top |
|
|
| thravi |
| Posted: Tue Nov 23, 2004 12:12 pm Post subject: |
|
|
Novice
Joined: 16 Jul 2004
Posts: 13
|
| you could try setting MQNOREMPOOL=1 in system environment variables. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Nov 23, 2004 12:23 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Make sure you read the client manual and set the port in your MQ environment variable.
As you are not using port 1414 (default) you need to explicitly set it in the environment or the channel table entry.
Enjoy  |
|
| Back to top |
|
|
| EddieA |
| Posted: Tue Nov 23, 2004 2:26 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| you could try setting MQNOREMPOOL=1 in system environment variables |
That is for a very specific 2059 error, which can be checked by looking at the error logs for a couple of known TCP/IP errors. (I can't remember the exact ones, but a quick search here should reveal them). It should only be set if you are suffering from this problem, not every 2059.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| Nigelg |
| Posted: Wed Nov 24, 2004 12:29 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
| Channel parameters on clients can be set in /var/mqm/qm.ini. |
|
| Back to top |
|
|
| KeeferG |
| Posted: Wed Nov 24, 2004 2:46 am Post subject: |
|
|
Master
Joined: 15 Oct 2004
Posts: 215
Location: Basingstoke, UK
|
You need to specify the port number the queue manager is listening on in your CLNTCONN channel definition and redeploy the AMQCLCHL.TAB file.
It will look something like CONNAME('HOSTNAME(1885)').
Alternatively, make the listener run on port 1414;
_________________
Keith Guttridge
-----------------
Using MQ since 1995 |
|
| Back to top |
|
|
| bath |
| Posted: Wed Nov 24, 2004 2:47 am Post subject: |
|
|
Apprentice
Joined: 23 Nov 2004
Posts: 29
|
thank you for your reply,
but now that you talking about /var/mqm/qm.ini. i wonder if my client installation is well installed. (because i don't have var/mqm/qm.ini)
what i use is macvfrFR.exe the size is 88.363
i install it on windows 2000.
i don't have no entry in start/program. i only have a directory under program files\IBM
with two subdirectories : Source and Websphere MQ.
is this correct?
thanks
roland |
|
| Back to top |
|
|
| Nigelg |
| Posted: Wed Nov 24, 2004 3:03 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
| /var/mqm/qm.ini only applies to UNIX platforms, and it is ont present by default, it has to be created. I do not know the equivalent on Windows. |
|
| Back to top |
|
|
| KeeferG |
| Posted: Wed Nov 24, 2004 3:14 am Post subject: |
|
|
Master
Joined: 15 Oct 2004
Posts: 215
Location: Basingstoke, UK
|
I'm trying to remember what we did for the client code when the ini file got moved into the registry. Don't have access to the code anymore to be able to check.
Im pretty sure you need to create the appropriate registry key. Will see if I can find it
_________________
Keith Guttridge
-----------------
Using MQ since 1995 |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Nov 24, 2004 5:17 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Roland, if it were me, I would first want to prove that my MQClient machine can get to my MQ server, and then worry about the channel tables once connectivity has been proven. Maybe there is nothing wrong with your channel tables and you need to focus somewhere else.
Do the following from a command line. It is the simplest way to see if you can MQ to your QM from you client. It trys a connection to the QM listening on that servername/port#/channelname combination, and returns the QM name.
| Code: |
X:\>SET MQSERVER=YourSVRCONNChannelName/TCP/YourServerName(Port#)
X:\>AMQSCNXC
Sample AMQSCNXC start
Connecting to the default queue manager
with no client connection information specified.
Connection established to queue manager QM1
Sample AMQSCNXC end
X:\>
|
Once that works, you can do the same thing using the MQCHLLIB and MQCHLTAB cariables instead of the MQSERVER.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bath |
| Posted: Wed Nov 24, 2004 9:17 am Post subject: |
|
|
Apprentice
Joined: 23 Nov 2004
Posts: 29
|
thank you
I did this
SET MQSERVER=S_channel/TCP/myservername(1885)
X:\>AMQSCNXC
I got the same result.
MQCONNX ended with reason code 2059.
I wonder if it is not a problem with my client installation?
thanks
roland |
|
| Back to top |
|
|
|
|
