| Author |
Message
|
| girish_tharwani |
 Posted: Wed Mar 18, 2009 5:21 am Post subject: 2059.. what am I doing wrong?? |
 |
|
Voyager
Joined: 01 Aug 2001
Posts: 88
Location: Pune, India
|
Sorry to open another 2059 thread on this forum but I am struggling for hours now and I am sure I am missing something simple which you can spot.
I have a Qmgr running on HP-UX. I have listener running. SVRCONN and CLNTCONN channels defined.
I am logged on with local user id on my windows desktop. This id is part of mqm group on HP-UX. I am issueing a simple MQCONNX call with Qmgr name, CONNAME and channel name. Getting 2059
Telnet to HPUX ip with listener port is successful. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Mar 18, 2009 5:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| leave the qmgr name blank. |
|
| Back to top |
|
|
| girish_tharwani |
| Posted: Wed Mar 18, 2009 5:59 am Post subject: |
|
|
Voyager
Joined: 01 Aug 2001
Posts: 88
Location: Pune, India
|
tried. still 2059
Do I need to set MCAUSR on channel even though my local id on Windows is part of mqm group on HP-UX?
Last edited by girish_tharwani on Wed Mar 18, 2009 6:02 am; edited 1 time in total |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Mar 18, 2009 6:01 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Does the conname include the correct port #? |
|
| Back to top |
|
|
| girish_tharwani |
| Posted: Wed Mar 18, 2009 6:12 am Post subject: |
|
|
Voyager
Joined: 01 Aug 2001
Posts: 88
Location: Pune, India
|
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Mar 18, 2009 6:21 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Are channel names exactly the same in client channel table and on qmgr?
Did you set the environment variables MQCHLLIB and MQCHLTAB on the client? Did you export the client channel table to the client platform?
Post both your CLNTCONN and SVRCONN definitions here.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| girish_tharwani |
| Posted: Wed Mar 18, 2009 6:32 am Post subject: |
|
|
Voyager
Joined: 01 Aug 2001
Posts: 88
Location: Pune, India
|
1 : DISPLAY CHANNEL (CLNTCONNCHNL)
AMQ8414: Display Channel details.
CHANNEL(CLNTCONNCHNL) CHLTYPE(SVRCONN)
ALTDATE(2009-03-1 ALTTIME(18.04.52)
COMPHDR(NONE) COMPMSG(NONE)
DESCR( ) HBINT(300)
KAINT(AUTO) MAXMSGL(4194304)
MCAUSER( ) MONCHL(QMGR)
RCVDATA( ) RCVEXIT( )
SCYDATA( ) SCYEXIT( )
SENDDATA( ) SENDEXIT( )
SSLCAUTH(REQUIRED) SSLCIPH( )
SSLPEER( ) TRPTYPE(TCP)
AMQ8414: Display Channel details.
CHANNEL(CLNTCONNCHNL) CHLTYPE(CLNTCONN)
ALTDATE(2009-03-1 ALTTIME(17.58.07)
COMPHDR(NONE) COMPMSG(NONE)
CONNAME(masked.xyx.com(1414)) DESCR( )
HBINT(300) KAINT(AUTO)
LOCLADDR( ) MAXMSGL(4194304)
MODENAME( ) PASSWORD( )
QMNAME(DCLNTCONN1) RCVDATA( )
RCVEXIT( ) SCYDATA( )
SCYEXIT( ) SENDDATA( )
SENDEXIT( ) SSLCIPH( )
SSLPEER( ) TPNAME( )
TRPTYPE(TCP) USERID( ) |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Mar 18, 2009 6:35 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Post both your CLNTCONN and SVRCONN definitions here.
Also post here your interaction (c: or $ prompt) on the client platform. I want to see you setting (or displaying) the environment variables and you starting the application, and receiving the 2059 rc.
Are channel names exactly the same in client channel table and on qmgr?
Did you set the environment variables MQCHLLIB and MQCHLTAB on the client? Did you export the client channel table to the client platform?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Last edited by bruce2359 on Wed Mar 18, 2009 6:36 am; edited 1 time in total |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Mar 18, 2009 6:36 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
What does amqscnxc report if you give it the same information?
Did you compile your app against the server libraries, or the client libraries? |
|
| Back to top |
|
|
| girish_tharwani |
| Posted: Wed Mar 18, 2009 6:55 am Post subject: |
|
|
Voyager
Joined: 01 Aug 2001
Posts: 88
Location: Pune, India
|
Bruce, I have posted both channel definations. Yes client channel table was exported and environment variables were set.
mqjeff AMXSCNXC is giving same error
Sample AMQSCNXC start
Connecting to queue manager DCLNTCONN1
using the server connection channel CLNTCONNCHNL
on connection name masked(1414).
MQCONNX ended with reason code 2059 |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Mar 18, 2009 7:35 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Did the MQ Administrator run REFRESH SECURITY after adding the user to the mqm group? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Mar 18, 2009 7:37 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
[deleted]
| Quote: |
| Yes client channel table was exported and environment variables were set. |
Everything in MQ and UNIX is case-sensitive.
I asked you to post the interaction from client to server, including the set/export of the environment variables. Many client failures are simple typo errors. If you post the things we ask for, it will help us help you.
What did you name the client channel table on the client platform?
Is it in the exact path that you specified in the MQCHLLIB environment variable?
Is it spelled exactly the same as in the MQCHLTAB environment variable?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| girish_tharwani |
| Posted: Wed Mar 18, 2009 11:32 am Post subject: |
|
|
Voyager
Joined: 01 Aug 2001
Posts: 88
Location: Pune, India
|
Lets eliminate any possiblity of my fingers making a typo by using
AMQSCNXC
/* AMQSCNXC is a sample C program that demonstrates how to use */
/* the MQCNO structure to supply client connection information */
/* on the MQCONNX call. This enables a client MQI application */
/* to provide the definition of its client connection channel */
/* at run-time without using a client channel table or the */
/* MQSERVER environment variable. */
I have masked the dns for this post but believe me I was extra careful
I am logged on to windows box with a local user id which is defined on server (HP-UX) also and is part of mqm group on server machine
C:\>amqscnxc -x *****(1414) -c IBCONN
Sample AMQSCNXC start
Connecting to the default queue manager
using the server connection channel IBCONN
on connection name *****(1414).
MQCONNX ended with reason code 2059
C:\>amqscnxc -x *****(1414) -c IBCONN DCLNTCONN1
Sample AMQSCNXC start
Connecting to queue manager DCLNTCONN1
using the server connection channel IBCONN
on connection name *****(1414).
MQCONNX ended with reason code 2059
but if i log on to the server with that id and run the same program with same parameters, it works..
$ amqscnxc -x "*****(1414)" -c IBCONN
Sample AMQSCNXC start
Connecting to the default queue manager
using the server connection channel IBCONN
on connection name mwdev1.bd.com(1414).
Connection established to queue manager DCLNTCONN1
So what am I missing while trying to create connection from windows desktop.
As amqscnxc is running fine from server machine, I believe channels are defined correctly but here are these one more time
1 : DISPLAY CHANNEL (IBCONN)
AMQ8414: Display Channel details.
CHANNEL(IBCONN) CHLTYPE(SVRCONN)
ALTDATE(2009-03-17) ALTTIME(19.25.59)
COMPHDR(NONE) COMPMSG(NONE)
DESCR( ) HBINT(300)
KAINT(AUTO) MAXMSGL(4194304)
MCAUSER( ) MONCHL(QMGR)
RCVDATA( ) RCVEXIT( )
SCYDATA( ) SCYEXIT( )
SENDDATA( ) SENDEXIT( )
SSLCAUTH(REQUIRED) SSLCIPH( )
SSLPEER( ) TRPTYPE(TCP)
AMQ8414: Display Channel details.
CHANNEL(IBCONN) CHLTYPE(CLNTCONN)
ALTDATE(2009-03-17) ALTTIME(19.32.53)
COMPHDR(NONE) COMPMSG(NONE)
CONNAME(*****(1414)) DESCR( )
HBINT(300) KAINT(AUTO)
LOCLADDR( ) MAXMSGL(4194304)
MODENAME( ) PASSWORD( )
QMNAME(DCLNTCONN1) RCVDATA( )
RCVEXIT( ) SCYDATA( )
SCYEXIT( ) SENDDATA( )
SENDEXIT( ) SSLCIPH( )
SSLPEER( ) TPNAME( )
TRPTYPE(TCP) USERID( )
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Mar 18, 2009 11:35 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
but if i log on to the server with that id and run the same program with same parameters, it works..
$ amqscnxc -x "*****(1414)" -c IBCONN
Sample AMQSCNXC start
Connecting to the default queue manager
using the server connection channel IBCONN
on connection name mwdev1.bd.com(1414).
Connection established to queue manager DCLNTCONN1 |
The connection worked because the qmgr was the default qmgr.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Last edited by bruce2359 on Wed Mar 18, 2009 11:36 am; edited 1 time in total |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Mar 18, 2009 11:35 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Test connection with a known program like RFHUTILC (support pac IH03).
If it works, then your code is wrong.
If it doesn't work, then your environment is wrong. |
|
| Back to top |
|
|
|
|
