| Author |
Message
|
| pranav_kavi |
 Posted: Tue Nov 15, 2005 8:13 pm Post subject: Windows client communicating with Linux server |
 |
|
Novice
Joined: 15 Nov 2005
Posts: 16
Location: Bangalore
|
hi all.i'm a fresher to MQSeries field.I request help in tackling a 2059 error obtained while connecting a MQClient in Windows platform & MQServer in Linux.The situation is as below:
On SERVER side(Linux):
(ve created a SVRCONN channel-'ourchnl' & listener,'ourmgr' is a queue managr)
runmqlsr -m ourmgr -t TCP -p 7778
On CLIENT side(Windows):
('ourq' is local queue in server under q manager 'ourmgr')
C:\set MQSERVER=ourchnl/TCP/'ip of server(7778)'
C:\amqsputc ourq ourmgr
The o/p:
Sample AMQSPUT0 start
MQCONN ended with reason code 2059
The reason code 2059 stand for MQRC_Q_MGR_NOT_AVAILABLE.Why does this occur when the listener is running on the server side & there exists the required q manager & q on server??
A little amount of help would also be very much appreciated.Thanx in advance.
_________________
kavitha r |
|
| Back to top |
|
 |
| EddieA |
| Posted: Tue Nov 15, 2005 8:59 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Try:
| Quote: |
| C:\set MQSERVER=ourchnl/TCP/ip of server(7778) |
No quotes around the server part.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| pranav_kavi |
| Posted: Tue Nov 15, 2005 9:19 pm Post subject: Windows client communicating with Linux server |
|
|
Novice
Joined: 15 Nov 2005
Posts: 16
Location: Bangalore
|
Thanx but its still not working.I've encountered the reason code 2035 that stands for MQRC_NOT_AUTHORISED.A quick reply to this problem wud be very much appreciated.Thanx!
_________________
kavitha r |
|
| Back to top |
|
|
| EddieA |
| Posted: Tue Nov 15, 2005 11:37 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
That one you can search for. The button's at the top right of the page.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| pranav_kavi |
| Posted: Wed Nov 16, 2005 1:15 am Post subject: Windows client communicating with Linux server |
|
|
Novice
Joined: 15 Nov 2005
Posts: 16
Location: Bangalore
|
 Please can u guide as to which document I need to refer from the documentation tab else please highlight as to how I can change the authorization on a queue manager?Thanx a lot .
_________________
kavitha r |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Nov 16, 2005 1:27 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
See Brandon, the button isn't prominent enough. 
I meant the "Seach" at the top right. That topic has been discussed to death. Although, the documentation is also another good place to start.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| pranav_kavi |
| Posted: Wed Nov 16, 2005 4:08 am Post subject: Windows client communicating with Linux server |
|
|
Novice
Joined: 15 Nov 2005
Posts: 16
Location: Bangalore
|
 Thanx for the previous reply.Looking through the prev posts...i have been able to solve my current problem.
Can you plz clear my doubt-when the environment variable MQSERVER is set on the client,should we also do the copying of AMQCLCHL.TAB file to client and perform the setting of reqd environment variables?
What i mean is should both the methods be performed to enable communication between a cross platform server-client?
Thanx again.
_________________
kavitha r |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Nov 16, 2005 4:10 am Post subject: Re: Windows client communicating with Linux server |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| pranav_kavi wrote: |
What i mean is should both the methods be performed to enable communication between a cross platform server-client?
Thanx again. |
No.
One or the other, not both.
Unless you have different applications running on the same client, that use different methods.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| pranav_kavi |
| Posted: Wed Nov 16, 2005 4:23 am Post subject: Windows client communicating with Linux server |
|
|
Novice
Joined: 15 Nov 2005
Posts: 16
Location: Bangalore
|
Ok,it has also been observed that when the MQSERVER variable is not set and the communication is brought about using .TAB procedure,the purpose is not met,i encounter the reason code 2059 & 2058.
Thank u
_________________
kavitha r |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Nov 16, 2005 5:05 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
You might need to set MQCHLLIB to point to the directory where the AMQCLCHL.TAB file is.
Under what circumstances to you get a 2058 versus a 2059?
_________________
-wayne |
|
| Back to top |
|
|
| pranav_kavi |
| Posted: Wed Nov 16, 2005 8:20 pm Post subject: Windows client communicating with Linux server |
|
|
Novice
Joined: 15 Nov 2005
Posts: 16
Location: Bangalore
|
Thanx...but I'm very much aware of the procedure of using .TAB file.It has come to my notice that this procedure does not work when the client-server is on different platforms(Win-Win,Linux-Linux,Win-Linux,Linux-Win) on different systems, but it works perfectly when the client-server is on the same system.It is then I encounter the 2058/2059 error.
The cross platform client-server purpose is achieved by setting the MQSERVER envt variable on the client.
 Please clear my doubt as to y the error arises while using .TAB method for cross platform client-server commn.
_________________
kavitha r |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Wed Nov 16, 2005 8:56 pm Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| Quote: |
It has come to my notice that this procedure does not work when the client-server is on different platforms(Win-Win,Linux-Linux,Win-Linux,Linux-Win) on different systems, but it works perfectly when the client-server is on the same system.It is then I encounter the 2058/2059 error.
|
Really? It sure works just fine on most platforms (except z/OS) at our shop.
Please post your chllib and chltab definitions. It sounds to me like you don't have the settings pointing to the correct place. |
|
| Back to top |
|
|
| pranav_kavi |
| Posted: Wed Nov 16, 2005 11:01 pm Post subject: Windows client communicating with Linux server |
|
|
Novice
Joined: 15 Nov 2005
Posts: 16
Location: Bangalore
|
Here's wat u asked for,
On the client system(either Win or Linux),the foll. envt variables have been set:
(Considering client to be on WindowsXP & server to be on Linux now,)
set MQCHLLIB=c:
(when the AMQCLCHL.TAB copied frm server m/c is stored on Windows client c: drive)
set MQCHLTAB=AMQCLCHL.TAB
amqsputc.exe qname qmgrname
(qname is queue name in server & qmgrname is queue manager name in server)
The o/p:
Sample AMQPUT0 start
MQCONN ended with reason code 2058
***end***
Plz note that the MQSERVER variable has not been set on the client side in this case .
Thanx again...
_________________
kavitha r |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Nov 17, 2005 3:23 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Are you specifying a QueueManager name on the MQCONN call?
And...if so, does it match an QNAME entry in the channel table (amclchl.tab)?
_________________
-wayne |
|
| Back to top |
|
|
| KeeferG |
| Posted: Thu Nov 17, 2005 8:04 am Post subject: |
|
|
Master
Joined: 15 Oct 2004
Posts: 215
Location: Basingstoke, UK
|
This takes me back to my first ever presentation in Dallas all those years ago.
Racking my brains for where the * comes into the channel table. Something to do with not checking QMGR name on startup of client channel. It will come to me.
_________________
Keith Guttridge
-----------------
Using MQ since 1995 |
|
| Back to top |
|
|
|
|
