| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Clients/CCDT - Multiple entries with same CLNTCONN CHL Name? |
« View previous topic :: View next topic » |
| Author |
Message
|
| Ross |
 Posted: Tue Sep 25, 2012 11:08 am Post subject: Clients/CCDT - Multiple entries with same CLNTCONN CHL Name? |
 |
|
Centurion
Joined: 15 Jun 2005
Posts: 127
Location: Ireland
|
Hi,
I'm trying to set up a Client Connection Def Table, AMQCLCHL.TAB, but I want it to connect to multiple qmgrs.
I've been doing a rummage around the Clients manual, and the internet, and can't get to the answer, so far!
Can I use the same channel name multiple times? Say i have clustered qmgrs, QM1, QM2, both hosting the same queues.
I want (my developer colleague wants!) to connect to any of the 2 qmgrs using the CCDT. I like the idea of using the same channel name, eg APP.CLNTCONN. But this is an issue when creating the standard file, using something like MO72.
Are there any reasons I shouldn't be doing this?
Maybe it would be simpler to use APP.qmgr.SVRCONN
Any thoughts appreciated.
Thanks. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Sep 25, 2012 11:56 am Post subject: Re: Clients/CCDT - Multiple entries with same CLNTCONN CHL N |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Ross wrote: |
| I've been doing a rummage around the Clients manual, and the internet, and can't get to the answer, so far! |
I'm surprised you didn't find this!
| Ross wrote: |
Can I use the same channel name multiple times? Say i have clustered qmgrs, QM1, QM2, both hosting the same queues.
I want (my developer colleague wants!) to connect to any of the 2 qmgrs using the CCDT. I like the idea of using the same channel name, eg APP.CLNTCONN. |
Both he and you are on a very common track.
| Ross wrote: |
| But this is an issue when creating the standard file, using something like MO72. |
Really? I've not used MO72 myself a lot, but I'm surprised it doesn't support this very common CCDT use case.
| Ross wrote: |
| Are there any reasons I shouldn't be doing this? |
No, and many good reasons why you should.
| Ross wrote: |
| Maybe it would be simpler to use APP.qmgr.SVRCONN |
You could. I'm unconvinced it's that much simpler.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Ross |
| Posted: Tue Sep 25, 2012 1:17 pm Post subject: Re: Clients/CCDT - Multiple entries with same CLNTCONN CHL N |
|
|
Centurion
Joined: 15 Jun 2005
Posts: 127
Location: Ireland
|
| Vitor wrote: |
I'm surprised you didn't find ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzaf.doc/cs12700_.htm this! |
Aha. I had mistakenly looked in V6 Infocenter... Need to update my links. Thanks.
Groups look like they will do the job. Got most of the information, but a bit more research to do... Like can I still specify a qmgr directly! Time to test it I think!
And I have struggled to find in infocenter how to actually create a Group... But I think this is me missing something simple!
| Vitor wrote: |
| Really? I've not used MO72 myself a lot, but I'm surprised it doesn't support this very common CCDT use case. |
I'm sure it will, once i know what to add. Although I'll also probably be able to use Explorer once I know what to add!
| Ross wrote: |
| Maybe it would be simpler to use APP.qmgr.SVRCONN |
| Vitor wrote: |
| You could. I'm unconvinced it's that much simpler. |
I meant simpler, in that I could create them straight away, rather than quicker! I don't want to use the qmgr names in the channels, so happier now.
Thanks for the steer the right way...
Ross. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Sep 25, 2012 7:16 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
the groups are created by setting the same qmgr name on the client channel definition. This is not the real qmgr name! It is used as *qmgr in the client when trying to connect....but no all channel names in the CCDT need to be unique.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Ross |
| Posted: Mon Oct 15, 2012 11:39 am Post subject: |
|
|
Centurion
Joined: 15 Jun 2005
Posts: 127
Location: Ireland
|
Thanks for the help with this.
Got it working.
There is very little info on Qmgr Groups.
So anyway, to use the same channel on a connection to 2 qmgrs, you comma separate the hostnames...
So we have QMGR1 and QMGR2, on lpar1(1414) and lpar1(1415).
We just used QMGR as the qmgrname.
Hostname was "lpar1(1414),lpar2(1415)"
Then called it from the app as *QMGR
The app will connect to QMGR1, and if that goes down, it will connect to QMGR2.
If you have app2, then you can do a separate CCDT in reverse (Or just use the same one).
Thanks for the help. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Oct 15, 2012 1:28 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Ross wrote: |
Thanks for the help with this.
Got it working.
There is very little info on Qmgr Groups.
So anyway, to use the same channel on a connection to 2 qmgrs, you comma separate the hostnames...
So we have QMGR1 and QMGR2, on lpar1(1414) and lpar1(1415).
We just used QMGR as the qmgrname.
Hostname was "lpar1(1414),lpar2(1415)"
Then called it from the app as *QMGR
The app will connect to QMGR1, and if that goes down, it will connect to QMGR2.
If you have app2, then you can do a separate CCDT in reverse (Or just use the same one).
Thanks for the help. |
Not quite how it is supposed to work.
What you doing here is perverting the system.
The conname information with separation of information for multiple destination is supposed to be used only for MULTI-INSTANCE qmgrs.
and thus should not be used for 2 different qmgrs.
Again each channel in the CCDT file needs to be unique.
Qmgr Groups in the CCDT are made up by setting the same qmgr name on the channel.  the client manual in the infocenter 
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Ross |
| Posted: Mon Oct 15, 2012 4:18 pm Post subject: |
|
|
Centurion
Joined: 15 Jun 2005
Posts: 127
Location: Ireland
|
Thanks for the info.
That actually made the most sense so far. Maybe it's because I understand more now!
I had read and re-read the clients manual, but the viewpoint seemed to be from the developer side. I couldn't see anything about how to create a group. Although re-reading, I realised, following your point too. Seems simple now!
"A queue manager group is a set of connections defined in the client channel definition table (CCDT). The set is defined by its members having the same value of the QMNAME attribute in their channel definitions."
Thanks again for the input. Helped fill in the gaps I missed in the manuals!
More testing to do! |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Oct 15, 2012 11:48 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
I have found THIS to be a perfect adjunct to the manual.
_________________
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 |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
