ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ API Support » MQCONN ended with reason code 2059

Post new topic  Reply to topic Goto page 1, 2, 3, 4  Next
 MQCONN ended with reason code 2059 « View previous topic :: View next topic » 
Author Message
girlinusa2006
PostPosted: Tue May 09, 2006 12:04 pm    Post subject: MQCONN ended with reason code 2059 Reply with quote

Novice

Joined: 09 May 2006
Posts: 24

Hi,

I am doing client/server communication.
On the server side, I have created a channel ( channel1)
define channel(channel1) chltype(svrconn) trptype(tcp)

On the client side, I have defined my
export MQSERVER='CHANNEL1/TCP/112.82.12.136(1414)'
And my MQ listener is listening on port 1414.

When I try to run amqsputc writeQ SERVER_QM, I get the following:
Sample AMQSPUT0 start
MQCONN ended with reason code 2059

When I looked into the AMQERR01.LOG, I see the following:
EXPLANATION:
Channel 'CHANNEL1' cannot start because the remote queue manager is not
currently available.
ACTION:
Either start the remote queue manager, or retry the operation later.

But, my queue manger is running on my server side. Then why i am getting the error?

Thanks
Back to top
View user's profile Send private message
sandiksk
PostPosted: Tue May 09, 2006 12:25 pm    Post subject: Reply with quote

Centurion

Joined: 08 Jun 2005
Posts: 133

I AM not sure if this could be the problem but could you try removing the single quotes in the server variable. Keep it this way.


export MQSERVER=CHANNEL1/TCP/'112.82.12.136(1414)'

As is said i am not 100% sure this could be the problem
Back to top
View user's profile Send private message
girlinusa2006
PostPosted: Tue May 09, 2006 12:27 pm    Post subject: Reply with quote

Novice

Joined: 09 May 2006
Posts: 24

I have tried that also, but that doesn't look like the problem.
Back to top
View user's profile Send private message
sandiksk
PostPosted: Tue May 09, 2006 12:33 pm    Post subject: Reply with quote

Centurion

Joined: 08 Jun 2005
Posts: 133

can you ping the server address from the client and also try telnet to that particular port on the server soo we can be sure that the sereris listning on that port


Also try making the server default Queue Manager(if it is not).


Last edited by sandiksk on Tue May 09, 2006 12:37 pm; edited 1 time in total
Back to top
View user's profile Send private message
girlinusa2006
PostPosted: Tue May 09, 2006 12:36 pm    Post subject: Reply with quote

Novice

Joined: 09 May 2006
Posts: 24

Yes, I can ping that server address and also telnet to that.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue May 09, 2006 12:39 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Are you sure you did "define channel(channel1)" and not "define channel('channel1')"?

Are there errors in the MQ client installation error folder?

Are there errors on the MQ server side?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
girlinusa2006
PostPosted: Tue May 09, 2006 12:45 pm    Post subject: Reply with quote

Novice

Joined: 09 May 2006
Posts: 24

I defined it as:

define channel(channel1) chltype(svrconn) trptype(tcp)

The errors I pasted are from MQ client installation error folder
Back to top
View user's profile Send private message
sandiksk
PostPosted: Tue May 09, 2006 12:46 pm    Post subject: Reply with quote

Centurion

Joined: 08 Jun 2005
Posts: 133

are there any errors on the server side and Any FDCs
Back to top
View user's profile Send private message
girlinusa2006
PostPosted: Tue May 09, 2006 12:49 pm    Post subject: Reply with quote

Novice

Joined: 09 May 2006
Posts: 24

Where are the errors logged for server side? (UNIX)

/var/mqm/errors ...same as client?
Back to top
View user's profile Send private message
sandiksk
PostPosted: Tue May 09, 2006 12:53 pm    Post subject: Reply with quote

Centurion

Joined: 08 Jun 2005
Posts: 133

yes if its an unix server
Try making it the default queue manager ( if not) .
Andwhat i would try is Try doing the trace as specified in the 14th chapter of clients maual. And the last thing i would try would be, other method of doing the clients(ie using the CHLIB and MQCHLTAB variables)
Back to top
View user's profile Send private message
kevinf2349
PostPosted: Tue May 09, 2006 1:10 pm    Post subject: Reply with quote

Grand Master

Joined: 28 Feb 2003
Posts: 1311
Location: USA

Quote:
define channel(channel1) chltype(svrconn) trptype(tcp)


Quote:
export MQSERVER=CHANNEL1/TCP/'112.82.12.136(1414)'


case? CHANNEL1 is not the same as channel1
Back to top
View user's profile Send private message
girlinusa2006
PostPosted: Tue May 09, 2006 1:24 pm    Post subject: Reply with quote

Novice

Joined: 09 May 2006
Posts: 24

I don't think it is case insentive on the channel name. I have tried that.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue May 09, 2006 1:25 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

MQ is always case sensitive on all object names. However, it will also uppercase objects if you have not enclosed them in single quotes - in most cases, as far as I know.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
wschutz
PostPosted: Tue May 09, 2006 3:02 pm    Post subject: Reply with quote

Jedi Knight

Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)

jefflowrey wrote:
MQ is always case sensitive on all object names. However, it will also uppercase objects if you have not enclosed them in single quotes - in most cases, as far as I know.
Yeah, provided we're talking about MQSC.
so: def chl(chl1) == def chl(CHL1)
but: strmqm qm1 != strmqm QM1
_________________
-wayne
Back to top
View user's profile Send private message Send e-mail AIM Address
ma.eyal
PostPosted: Wed May 10, 2006 2:57 am    Post subject: Reply with quote

Novice

Joined: 13 Sep 2005
Posts: 15
Location: Israel

Hello.

What is your client system? Windows? Unix?

I would recommen checking the ccsid.tbl file (in C:\Program Files\IBM\WebSphere MQ\conv\table or in /var/mqm/conv/table).
Make sure that the two default lines at the end of the file are unmarked.

Meaning if you have
Code:
#default      0x1100     500
#default      0x2100     850


Then it should be
Code:
default      0x1100     500
default      0x2100     850


Error 2059 can also occure when there is unmatched conversion tables between the systems.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2, 3, 4  Next Page 1 of 4

MQSeries.net Forum Index » IBM MQ API Support » MQCONN ended with reason code 2059
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.