| Author |
Message
|
| User100 |
 Posted: Thu Jan 20, 2011 2:34 am Post subject: using MQ Channel Table |
 |
|
Novice
Joined: 10 Jan 2011
Posts: 13
Location: Berlin, Germany
|
Hey there,
I'd like to build Client Channel Definition Table to connect the application to more than one qmgr.
QMGRS are L90G and L91G, which are clustered.
So till now we have defined a SVRCONN channel named CLIENT.FOR.CCC.F.01 on each qmgr (same name!)
Now I am defining a CLNTCONN on L90G to build a channel table...
def chl(CLIENT.FOR.CCC.F.01) CHLTYPE(CLNTCONN) CONNAME('x.x.x.x(1418)') QMNAME(L90G) TRPTYPE(TCP) MAXMSGL(104857600)
but the name of the channel on L91G could not be the same? How do I do that or do I have to choose different names for different qmgrs?
second one must be then ...(command on L90G?! to get only one channel table)
def chl(CLIENT.FOR.CCC.F.02) CHLTYPE(CLNTCONN) CONNAME('y.y.y.y(1418)') QMNAME(L91G) TRPTYPE(TCP) MAXMSGL(104857600)
what do you guess? |
|
| Back to top |
|
 |
| exerk |
| Posted: Thu Jan 20, 2011 2:41 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
I don't guess. I read the manuals and other sources of information such as THIS...
...and clients aren't aware of whether a queue manager is clustered, or not.
_________________
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 |
|
|
| User100 |
| Posted: Thu Jan 20, 2011 2:55 am Post subject: |
|
|
Novice
Joined: 10 Jan 2011
Posts: 13
Location: Berlin, Germany
|
Sorry but I don't understand what do want to tell me?
The big question is what can I do to have connections to more than one qmgr in one channel definition table where the name of the channel should be the same to each qmgr? |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Jan 20, 2011 3:04 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| It's not an issue to use the same channel name for different Qmgrs in CCDT. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Jan 20, 2011 3:19 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| User100 wrote: |
Sorry but I don't understand what do want to tell me?
The big question is what can I do to have connections to more than one qmgr in one channel definition table where the name of the channel should be the same to each qmgr? |
Try clicking on the link in my post 
_________________
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 |
|
|
| santnmq |
| Posted: Thu Jan 20, 2011 4:16 am Post subject: |
|
|
Centurion
Joined: 11 Jan 2011
Posts: 125
|
| do you want to use one channel table file for multiple clients on the same machine to connect to the server ? |
|
| Back to top |
|
|
| User100 |
| Posted: Thu Jan 20, 2011 5:23 am Post subject: |
|
|
Novice
Joined: 10 Jan 2011
Posts: 13
Location: Berlin, Germany
|
No it is one application server that should be able to connect in first step to 2 different qmgrs which are configured identically.
I've got a question more...
what is about the MCAUSER that I define on a SVRCONN channel.. this parameter do not exist for CLNTCONN's |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Jan 20, 2011 5:31 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
MCAUSER is an queue manager side override to the MQ connection userid (if any) that is supplied by the application program.
The value in MCAUSER can also be overridden by a security exit such as BlockIP2. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jan 20, 2011 5:37 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| User100 wrote: |
Sorry but I don't understand what do want to tell me?
The big question is what can I do to have connections to more than one qmgr in one channel definition table where the name of the channel should be the same to each qmgr? |
Read the client manual and the corresponding chapters about a client channel table. This is not how it works!
What are you trying to achieve? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jan 20, 2011 5:49 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Why do you care what the name of the channel is? |
|
| Back to top |
|
|
| User100 |
| Posted: Thu Jan 20, 2011 6:01 am Post subject: |
|
|
Novice
Joined: 10 Jan 2011
Posts: 13
Location: Berlin, Germany
|
I have red the manual but I have not found the critical points of the questions I am thinkting about 
You are right, the channel name does not play a role.
But till now (we are using SVRCONN channels, one for each app-server) we are able to disconnect a single server by stopping the regarding client channel
CLNTCONN is completely new for me, so I have to practice..
Sorry |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Jan 20, 2011 8:22 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Stopping a svrconn channel should not be necessary.
Why are you doing that? |
|
| Back to top |
|
|
|
|
