| Author |
Message
|
| skrv |
 Posted: Fri Aug 23, 2013 5:35 am Post subject: Can we have different SHORTRTY and LONGRTY values for chann |
 |
|
Centurion
Joined: 26 Oct 2012
Posts: 118
|
Hi,
Can we have different SHORTRTY and LONGRTY values for cluster channels in the same cluster?
Scenario: We have 2 full repository queue managers which host 30 odd clusters at ABC data center.
There are 2 partial queue managers at XYZ data center which are part of cluster 123.
Now MQ admins at XYZ data center want to increase the SHORTRTY and LONGRTY values for their 2 qmgrs, as their channels are retrying when there is some network issues.
We at ABC data center don't want to increase these values for our full repositories as it hosts several other clusters other than 123, and we don't want to disrupt anything as it's working fine.
So our question is can MQ admins at XYZ data center go ahead and increase SHORTRTY and LONGRTY values for their CLUSRCVR and CLUSSDR channels, and we don't change these values, and there won't be any issue?
currently these 2 para meter values are same at both data centers.
thanks in advance for your time. |
|
| Back to top |
|
 |
| JosephGramig |
| Posted: Fri Aug 23, 2013 5:45 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
OK, I guess you glossed over the part in the WMQ Information Center (IC) where it tells you that the definition of a CLUSSDR will be overridden by the matching CLUSRCVR. So, it is fine for the PR Qmgr to change its CLUSRCVR which will be reflected by the auto CLUSSDR at the FR (which will be specific for this PR Qmgr).
Having said that, no matter how you define the CLUSSDR at the PR that points to the FR, it will be overridden by an auto CLUSSDR that matches the FR's CLUSRCVR definition (if it works in the first place).
Can you work it out from here? |
|
| Back to top |
|
|
| skrv |
| Posted: Fri Aug 23, 2013 6:06 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2012
Posts: 118
|
So even if PR changes these values for their CLUSRCVR chaannels it won't address their channel retry then.
to address their channel retry, these values needs to be changed at full repositories right? |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Fri Aug 23, 2013 6:54 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
The PR defines a CLUSRCVR that points to itself for the cluster in question. This definition will cause auto CLUSSDRs that match it to be created at the FRs and any other PR that is accessing a cluster object hosted at this PR (which should not have any explicit CLUSSDR pointing to a PR).
So for a PR for each cluster it should have:
- One CLUSRCVR pointed to itself (named <ClusName>.<QmgrName>)
- One CLUSSDR pointed to one FR (named <ClusName>.<FR_QmgrName>)
If you have more channels than this, you have a "cluster mess up".
So it is explicit CLUSSDRs that get overridden by auto defined CLUSSDRs. |
|
| Back to top |
|
|
| skrv |
| Posted: Fri Aug 23, 2013 7:01 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2012
Posts: 118
|
thanks for your reply.
let me be more clear....
PR has 1 CLUSSDR and 1 CLUSRCVR tp FR.
PR has channel retry issues (their CLUSSDR channel to my FR retries time to time) and they want to increase SHORTRTY and LONGRTY values for thier CLUSSDR and CLUSRCVR channels to address this retry issue.
So my question is - by increasing SHORTRTY and LONGRTY values on PR CLUSSDR and CLUSRCVR channels, does it address their CLUSSDR retry issue?
We don't want to change any values on FR CLUSSDR and CLUSRCVR channels |
|
| Back to top |
|
|
| skrv |
| Posted: Fri Aug 23, 2013 7:22 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2012
Posts: 118
|
| if the PR has manually defined CLUSSDR channel to FR, then if we change the SHORTRTY and LONGTRY values of this manually defined CLUSSDR channel then it should take these changed values right? and not the CLUSRCVR properties of the FR for it's CLUSDR channel to FR? |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Fri Aug 23, 2013 8:56 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
If the PR changes almost any value of the explicitly (manually) defined CLUSSDR channel to the FR, it will not take effect because it automatically defined a CLUSSDR channel to the FR from the definition of that FRs CLUSRCVR to be used at all time (except on the initial joining of the cluster and a "refresh cluster(bla) repos(yes)" command).
Do you not believe the IC?
This was the second hit in a search of the words "automatic clusrcvr" in the IC. So, try searching for the answer... |
|
| Back to top |
|
|
| skrv |
| Posted: Fri Aug 23, 2013 9:01 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2012
Posts: 118
|
| thanks for the confirmation. |
|
| Back to top |
|
|
|
|
