| Author |
Message
|
| jeevan |
 Posted: Tue Oct 15, 2013 7:58 pm Post subject: RESOLVED-amqsputc is failing in mq 7.5 |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
I am getting 2058 while using amqsputc in MQ 7.5. When I tested a while back I remember getting 2035 which was obvious but I am not sure why I am getting 2058 this time.
I have not missed anything in general
Defined MQSERVER variable
Confirmed that the Listener is running
I am runnign this test from the same server the qmgr is ( for test only)
Disabled chlauth ( which probably was not necessary as I was not getting 2035).
What else could it be?
Env: I am running mq 7.5 on centos
Last edited by jeevan on Thu Oct 17, 2013 11:43 am; edited 4 times in total |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Oct 15, 2013 8:16 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
Have you ever run amqsputc successfully before ? What has changed?
What did you set mqserver to? What other env variables?
What 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. |
|
| Back to top |
|
|
| jeevan |
| Posted: Tue Oct 15, 2013 8:24 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| bruce2359 wrote: |
Have you ever run amqsputc successfully before ?
Yes, definitely. but have not done in MQ 75.
What has changed?
seems I need to define mqchltab variable which in earlier version defining MQSERVER was enough.
What did you set mqserver to?
Yes
What other env variables? I have not but seems I have to define MQCHLTAB and probably MQCHLLIB.
What platform? |
The actual environment is Redhat, but I am testing this in CentOs6.4 to produce the problem. I was thinking that the issue was caused by some other thing such as firewall or network but it seems to me that it is mostly the variable setup.
Last edited by jeevan on Wed Oct 16, 2013 6:19 am; edited 1 time in total |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Oct 15, 2013 9:43 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jeevan wrote: |
Yes, definitely. but have not done in MQ 75.
What has changed? |
Client connections in 7.5 are subject to extra security out of the box and no ID in the mqm group will work unless the needed chlauth records have been created.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Wed Oct 16, 2013 3:18 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
Just a guess but I believe the TCP in the MQServer environment variable is still case sensitive. You have definitely typed it in upper case right ?
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| jeevan |
| Posted: Wed Oct 16, 2013 3:25 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| PaulClarke wrote: |
Just a guess but I believe the TCP in the MQServer environment variable is still case sensitive. You have definitely typed it in upper case right ?
I think the issue is not the definition, in mq7.5 the client connection has changed. Based on the error in log, it seems that I have to create channel table and define MQCHLTAB AND MQCHLLIB variables.
Cheers,
Paul. |
I also thought so and redefined the MQSERVER with tcp in lower case, still same result.
I came across this site where it seems we can use TCP probably in upper case ( and lower case also may work)
http://pic.dhe.ibm.com/infocenter/wmqv7/v7r5/index.jsp
Last edited by jeevan on Wed Oct 16, 2013 5:29 am; edited 1 time in total |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Oct 16, 2013 3:43 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Nothing about MQ 7.5 will require that you use MQCHL* variables instead of MQSERVER.
You say you've disabled chlauth on the remote server - which is not a good idea but it does at least eliminate chlauth rules as the source of the problem. In much the same way that burning down the house eliminates an insect infestation.
You don't say if you've tested amqscnxc to see if you get a different error message. It would allow you to find out if the problem is in how you are specifying the connection information, or if it's more related to what you are trying to do. |
|
| Back to top |
|
|
| jeevan |
| Posted: Wed Oct 16, 2013 5:09 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| mqjeff wrote: |
Nothing about MQ 7.5 will require that you use MQCHL* variables instead of MQSERVER.
You say you've disabled chlauth on the remote server - which is not a good idea but it does at least eliminate chlauth rules as the source of the problem. In much the same way that burning down the house eliminates an insect infestation.
You don't say if you've tested amqscnxc to see if you get a different error message. It would allow you to find out if the problem is in how you are specifying the connection information, or if it's more related to what you are trying to do. |
I did not say it requies, I said, the error log in /var/mqm/errior says that.
I disabled the chlauth, just because when I did a test while ago, when actually MQ 7.1 was out, I got 2035 and it was due to the chlauth. This time, though I did not get 2035, I just disabled the chlauth thinking whether it is causing the issue.
MQ 7.5 info center still says to disable chlauth.
http://pic.dhe.ibm.com/infocenter/wmqv7/v7r5/index.jsp |
|
| Back to top |
|
|
| hughson |
| Posted: Wed Oct 16, 2013 7:33 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
You don't tell us a couple of important pieces of information.
- The name of your queue manager
- The command you used to invoke amqsputc
Something else that could be wrong when you get a 2058 MQRC_Q_MGR_NAME_ERROR is that the queue manager name might be wrong.
For example, if I set my MQSERVER environment variable up to point at my queue manager called QM1 and then invoke
I get a 2058.
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Oct 16, 2013 8:07 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
Exactly and precisely, what did you set (export) MQSERVER to? Copy/paste the entire conversation here.
Did you unset the MQCHL* environment variables?
_________________
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 |
|
|
| jeevan |
| Posted: Wed Oct 16, 2013 9:41 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| hughson wrote: |
You don't tell us a couple of important pieces of information.
- The name of your queue manager
- The command you used to invoke amqsputc
Something else that could be wrong when you get a 2058 MQRC_Q_MGR_NAME_ERROR is that the queue manager name might be wrong.
For example, if I set my MQSERVER environment variable up to point at my queue manager called QM1 and then invoke
I get a 2058.
Cheers
Morag |
I can guarantee, there is no mistake in definition of MQSERVER and QMGR name.
I have a way to tell that.
1. I defined listener at 1421
netstat -an|grep 1421
it shows it is listening
I even did this in order to confirm it
telnet localhsot 1421 and it works
2. Define a local queue called TEST.QAL
3. did amqsput TEST.QL TEST
TEST is the name of the qmgr and it worked. But when I did
amqsputc TEST.QL TEST, I got a 2058 error and the /var/mqm/error log tells that I might have missed MQCHLLIB and MQCHLTAB variable. I know when I needed these so I have not definied them.
Last edited by jeevan on Wed Oct 16, 2013 11:27 am; edited 2 times in total |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Oct 16, 2013 9:49 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Show setting the MQSERVER definition.
Show using amqscnxc with no options specified relying on that MQSERVER definition.
Show amqscnxc making a successful connection specifying the -c and -x parameters.
This will almost surely highlight the problem.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Oct 16, 2013 11:08 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
| jeevan wrote: |
I can guarantee, there is no mistake in definition of MQSERVER and QMGR name.
I have a way to tell that. |
Is there some reason you won't share the details of your environment variables? A single typographical error can result in the same error r/c.
_________________
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 |
|
|
| jeevan |
| Posted: Wed Oct 16, 2013 11:12 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| bruce2359 wrote: |
| jeevan wrote: |
I can guarantee, there is no mistake in definition of MQSERVER and QMGR name.
I have a way to tell that. |
Is there some reason you won't share the details of your environment variables? A single typographical error can result in the same error r/c. |
I can do that. Now, I am in office and can not share the real one. I have created a scenario at my laptop which I can share this evening.
Thanks |
|
| Back to top |
|
|
| jeevan |
| Posted: Wed Oct 16, 2013 2:35 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| jeevan wrote: |
| bruce2359 wrote: |
| jeevan wrote: |
I can guarantee, there is no mistake in definition of MQSERVER and QMGR name.
I have a way to tell that. |
Is there some reason you won't share the details of your environment variables? A single typographical error can result in the same error r/c. |
I can do that. Now, I am in office and can not share the real one. I have created a scenario at my laptop which I can share this evening.
Thanks |
I am really sorry folks, I just missed the export after I set the MQSERVER variable.
I did not post the setting I do not know how i can upload a document. Being in my virtual box and i have not been able to set the cut and past, I can not grab the text. I can cut the screen but I do not know how to upload a file here.
Anyway, thanks a lot for the insight.
When I enabled the chlauth, now I am getting 2035, which I know why and how to tackle it.
thanks
[/img] |
|
| Back to top |
|
|
|
|
