| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| CLUSNL |
« View previous topic :: View next topic » |
| Author |
Message
|
| Vitor |
 Posted: Tue Sep 23, 2014 7:46 am Post subject: |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jim wrote: |
| bruce2359 wrote: |
| Are the channels in RUNNING state? |
Nope ..The channel are not running... |
Well that's not going to help is it?
| jim wrote: |
| I know that we can add the qmgr in repos by adding the channel to full qmgr. |
You know wrong. Adding a channel to the full repository queue manager doesn't do anything relevant except that's what you need for a cluster. It certainly doesn't make the queue manager a full repository.
But you thinking that might well help explain why you have cluster channels that are not running.
| jim wrote: |
| My doubt if we define the cluster namelist object and I need to keep the qmgr in partial repository. how to setup. |
You don't keep a queue manager in a partial repository. A queue manager is a partial repository, or it isn't. It's a full repository, or it isn't.
Read the Cluster documentation again. Carefully.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Sep 23, 2014 8:11 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Clustering software is part of every qmgr. A qmgr can be designated as a full repository (FR) by altering some qmgr attributes.
A qmgr that is part of a cluster is a partial repository (PR) unless you have designated it to be an FR. See above.
In order for a qmgr to be a member of a cluster (FR or PR), the qmgr must be fully configured to a full repository. This is accomplished by creating cluster channels CLUSSDR, CLUSRCVR) to and from the FR. The channels must be in RUNNING state for any of this to be functional - to work.
_________________
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 |
|
|
| hughson |
| Posted: Tue Sep 23, 2014 8:16 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
| jim wrote: |
| My doubt if we define the cluster namelist object and I need to keep the qmgr in partial repository mean i will not alter the qmgr reposnl attribute. for this like clustering the cluster namelist should be full repository |
In order to use a namelist of names, you do not have to be a full repository. If your partial queue manager wants to use a namelist, just define the namelist like you had in your original question, and use the name in the CLUSNL attribute of the channels you want to define.
Remember that to add a queue manager into a cluster, you need both a CLUSSDR and a CLUSRCVR with the cluster name mentioned. If you are using a cluster namelist (CLUSNL) instead of a single cluster name (CLUSTER keyword) you still need to make sure that a CLUSSDR and a CLUSRCVR for both clusters is defined.
Perhaps you could post the commands you have used so we can see them. I'd expect to see a DEFINE NAMELIST... and at least two DEFINE CHANNEL commands.
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Sep 23, 2014 8:19 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| bruce2359 wrote: |
Clustering software is part of every qmgr. A qmgr can be designated as a full repository (FR) by altering some qmgr attributes.
A qmgr that is part of a cluster is a partial repository (PR) unless you have designated it to be an FR. See above.
In order for a qmgr to be a member of a cluster (FR or PR), the qmgr must be fully configured to a full repository. This is accomplished by creating cluster channels CLUSSDR, CLUSRCVR) to and from the FR. The channels must be in RUNNING state for any of this to be functional - to work. |
Further more, a queue manager is a member of MORE THAN ONE cluster (either FR or PR) through either of two ways. - More than one set of CLUSSDR/CLUSRCVRs are created, each with CLUSTER property
- At least one set of CLUSSDR/CLUSRCVRs exist and have CLUSNL specified
As previously mentioned, it is more maintainable to use CLUSTER and create several sets of CLUSSDR/CLUSRCVR pairs, than to use one set of channels with CLUSNL.
The advantage of CLUSNL is if a queue manager needs to belong to a changing set of clusters - this week one set, next week a different set. You only have to change one object.
But clusters are hopefully much more stable than that, and the qmgr shouldn't be moving between clusters that quickly. |
|
| Back to top |
|
|
| jim |
| Posted: Tue Sep 23, 2014 8:45 am Post subject: |
|
|
Voyager
Joined: 26 Nov 2013
Posts: 94
|
| hughson wrote: |
| jim wrote: |
| My doubt if we define the cluster namelist object and I need to keep the qmgr in partial repository mean i will not alter the qmgr reposnl attribute. for this like clustering the cluster namelist should be full repository |
In order to use a namelist of names, you do not have to be a full repository. If your partial queue manager wants to use a namelist, just define the namelist like you had in your original question, and use the name in the CLUSNL attribute of the channels you want to define.
Remember that to add a queue manager into a cluster, you need both a CLUSSDR and a CLUSRCVR with the cluster name mentioned. If you are using a cluster namelist (CLUSNL) instead of a single cluster name (CLUSTER keyword) you still need to make sure that a CLUSSDR and a CLUSRCVR for both clusters is defined.
Perhaps you could post the commands you have used so we can see them. I'd expect to see a DEFINE NAMELIST... and at least two DEFINE CHANNEL commands.
Cheers
Morag |
Thanks all !!!
Consider the step up
QM1 & QM2 ---> FUll repos cluster for TESTCLUS
QM3 & QM4----FUll repos cluster for TESTCLUS2
QM3 & QM4 ----> partial repos for cluster TESTCLUS
On QM3---> defined namelist(CLUS12) names(TESTCLUS,TESTCLUS2)
define ql(TEST.QL) clusnl(CLUS12)
The above setup make an sense or not ...
 |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Sep 23, 2014 9:34 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jim wrote: |
| The above setup make an sense or not ... |
Assuming the intention is to make TEST.QL accessable to all 4 queue managers, yes.
Also assuming all the clusters work (e.g. all the channels are defined and running).
How much of a good idea it is remains open to debate.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Sep 23, 2014 9:40 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Is it valid, probably.
Does it make sense? no.
What is your goal?
Consider naming you channels <ClusName>.<TargetQmgrName> which will always make them unique and applicable to only one cluster. Of course, you will need to limit your cluster names and Qmgr names to 9 or fewer characters (because a channel name has a limit of 20). |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
