Author |
Message
|
pintrader |
Posted: Mon Sep 22, 2014 3:00 am Post subject: How to use client definition table file |
|
|
Disciple
Joined: 22 Jan 2014 Posts: 164
|
hi
In the docs, it was written that for clients to connect to another QMGR, we can provide the AMQCLCHL.TAB file to clients to use in their applications. But is it really that simple as just transferring the AMQCLCHL.TAB at the @ipcc directory to the respective clients? Do we still need to do something before this.? I ask because the timestamp of this AMQCLCHL.TAB that I have at the QMGR is 2 months ago. I have done a lot of configurations since then. Does MQ update this file as when there are configurations done on it?
thanks |
|
Back to top |
|
 |
exerk |
Posted: Mon Sep 22, 2014 3:22 am Post subject: Re: How to use client definition table file |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
pintrader wrote: |
In the docs, it was written that for clients to connect to another QMGR, we can provide the AMQCLCHL.TAB file to clients to use in their applications... |
Good so far...
pintrader wrote: |
But is it really that simple as just transferring the AMQCLCHL.TAB at the @ipcc directory to the respective clients? |
No...
pintrader wrote: |
Do we still need to do something before this.?... |
Yes...
pintrader wrote: |
I ask because the timestamp of this AMQCLCHL.TAB that I have at the QMGR is 2 months ago. I have done a lot of configurations since then. Does MQ update this file as when there are configurations done on it? |
Yes.
I strongly suggest you read the relevant parts of the KC that deal with how to specify Client connections, e.g. environment variables and (preferably) the mqclient.ini file. _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
zpat |
Posted: Mon Sep 22, 2014 3:52 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
Alternatively use the support pac MO72 to maintain this table. _________________ Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
Back to top |
|
 |
exerk |
Posted: Mon Sep 22, 2014 4:16 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
zpat wrote: |
Alternatively use the support pac MO72 to maintain this table. |
Or, if using IBM MQ v8.0, the runmqsc console in Client-local mode  _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
bruce2359 |
Posted: Mon Sep 22, 2014 4:50 am Post subject: Re: How to use client definition table file |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
exerk wrote: |
pintrader wrote: |
In the docs, it was written that for clients to connect to another QMGR, we can provide the AMQCLCHL.TAB file to clients to use in their applications... |
Good so far...
pintrader wrote: |
But is it really that simple as just transferring the AMQCLCHL.TAB at the @ipcc directory to the respective clients? |
No...
pintrader wrote: |
Do we still need to do something before this.?... |
Yes...
pintrader wrote: |
I ask because the timestamp of this AMQCLCHL.TAB that I have at the QMGR is 2 months ago. I have done a lot of configurations since then. Does MQ update this file as when there are configurations done on it? |
Yes.
I strongly suggest you read the relevant parts of the KC that deal with how to specify Client connections, e.g. environment variables and (preferably) the mqclient.ini file. |
Exactly and precisely, what 'configurations' did you change? Please use MQ terminology, and not 'i changed the network...' which is neither specific nor precise. _________________ 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 |
|
 |
JosephGramig |
Posted: Mon Sep 22, 2014 6:40 am Post subject: |
|
|
 Grand Master
Joined: 09 Feb 2006 Posts: 1244 Location: Gold Coast of Florida, USA
|
The version of the MQ Client matters.
The version of MQ Qmgr that creates the CCDT (Client Connection Definition Table aka AMQCLCHL.TAB) matters. CCDTs build with newer Qmgrs than the client probably won't work.
MO72 has switches to control the version of the CCDT.
MQ V8 in client mode does not have switches to control the version of the CCDT (yet I hope). |
|
Back to top |
|
 |
PeterPotkay |
Posted: Mon Sep 22, 2014 8:47 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
MQSCX from MQGem has the ability to set the version of MQ Client Channel tables, including version 8. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
pintrader |
Posted: Mon Sep 22, 2014 5:27 pm Post subject: |
|
|
Disciple
Joined: 22 Jan 2014 Posts: 164
|
|
Back to top |
|
 |
hughson |
Posted: Tue Sep 23, 2014 2:13 am Post subject: |
|
|
 Padawan
Joined: 09 May 2013 Posts: 1959 Location: Bay of Plenty, New Zealand
|
pintrader wrote: |
Can I ask, if my SVRCONN channel is using SSL, do I create the CLNTCONN also with the same SSL parameters? thanks. |
It must have the same SSLCIPH parameter or they won't be able to connect
They are the same command because they are doing the exact same thing. One is the page telling you how to set up the CLNTCONN and then saying you need this CHLAUTH rule to let it in. The other page is telling you how to set up the SVRCONN and then saying your need this CHLAUTH rule so it can be started. If they were different I would be worried. It is not saying you need two of them, it is just showing you that you need it regardless of what page you read.
Cheers
Morag _________________ Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
Back to top |
|
 |
pintrader |
Posted: Tue Sep 23, 2014 3:50 am Post subject: |
|
|
Disciple
Joined: 22 Jan 2014 Posts: 164
|
hughson wrote: |
pintrader wrote: |
Can I ask, if my SVRCONN channel is using SSL, do I create the CLNTCONN also with the same SSL parameters? thanks. |
It must have the same SSLCIPH parameter or they won't be able to connect
They are the same command because they are doing the exact same thing. One is the page telling you how to set up the CLNTCONN and then saying you need this CHLAUTH rule to let it in. The other page is telling you how to set up the SVRCONN and then saying your need this CHLAUTH rule so it can be started. If they were different I would be worried. It is not saying you need two of them, it is just showing you that you need it regardless of what page you read.
Cheers
Morag |
thanks for the reply. appreciate |
|
Back to top |
|
 |
|