| Author |
Message
|
| troy |
 Posted: Fri Aug 07, 2009 2:23 am Post subject: Changing Full repost QM to Partial repos |
 |
|
Novice
Joined: 07 Jan 2009
Posts: 20
|
Hi,
I want to change FR QM to partial repos in production. The steps I am planning to follow are below -
1. Stop all the manually defined cluster sender channels to the other FR.
2. Delete the above manually defined channels.
3. alter the QMGR attribute by making reposnl attribute as blank.
4. delete the namelist created.
5. Create the manual cluster sender channel to any of the existing FR of the cluster to make it partial repos.
Please let me know if the above steps are fine or any other thing else also need to be taken care of. I want to make sure as it is Production env.
Do I have to take care any thing regarding the autodefined channels from this FR to other partial QMs?
Thanks! |
|
| Back to top |
|
 |
| exerk |
| Posted: Fri Aug 07, 2009 2:55 am Post subject: Re: Changing Full repost QM to Partial repos |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| troy wrote: |
1. Stop all the manually defined cluster sender channels to the other FR.
2. Delete the above manually defined channels. |
Why?
| troy wrote: |
3. alter the QMGR attribute by making reposnl attribute as blank.
4. delete the namelist created. |
Good so far...
| troy wrote: |
| 5. Create the manual cluster sender channel to any of the existing FR of the cluster to make it partial repos. |
Would that be the same one as you deleted in Step 2. ? 
| troy wrote: |
| Please let me know if the above steps are fine or any other thing else also need to be taken care of. I want to make sure as it is Production env. |
Test the procedure in a sand-box environment.
| troy wrote: |
| Do I have to take care any thing regarding the autodefined channels from this FR to other partial QMs? |
Yes!
OK, a few pointers:
1. All PR queue managers, which have explicit CLUSSDR's defined to the FR you are demoting, should have new CLUSSDR's defined, which should be to the other FR, or the new FR - before you demote the FR.
2. The existing CLUSSDR, in the FR being demoted, can remain and so can the name list if it's also used for queues.
3. Test the procedure in a controlled environment, then test it again, and have a fall-back plan (just in case).
_________________
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 |
|
|
| troy |
| Posted: Fri Aug 07, 2009 3:44 am Post subject: |
|
|
Novice
Joined: 07 Jan 2009
Posts: 20
|
Hi exerk,
Thanks for ur response.
Would that be the same one as you deleted in Step 2. ?
response for the above query is below -
Ok, point taken i need not delete the sender channel as even after the QM becomes PR a manually defined sender channel is required to any of the FR.
Thanks again! |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Aug 07, 2009 3:52 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Deleting the Namelist can be counterproductive. If the PR is to be a member of multiple clusters you might need it.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Aug 07, 2009 4:17 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Where's the step to go to every other QM in your cluster, both PRs and FRs, and make sure that their one mandatory explicitly defined CLUSSNDR channel doesn't point at the guy you are about to demote from FR to PR? That should be step 1.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Aug 07, 2009 4:21 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
It's No.1 in my list of pointers 
| exerk wrote: |
| 1. All PR queue managers, which have explicit CLUSSDR's defined to the FR you are demoting, should have new CLUSSDR's defined, which should be to the other FR, or the new FR - before you demote the FR. |
_________________
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 |
|
|
| PeterPotkay |
| Posted: Fri Aug 07, 2009 4:28 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| troy |
| Posted: Fri Aug 07, 2009 5:25 am Post subject: |
|
|
Novice
Joined: 07 Jan 2009
Posts: 20
|
Thanks guys for ur response,
Let me summarize -
1. go to every other QM in your cluster, both PRs and FRs, and make sure that their one mandatory explicitly defined CLUSSNDR channel doesn't point at the guy you are about to demote from FR to PR
2. alter the QMGR attribute by making reposnl attribute as blank.
Thanks! |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Aug 07, 2009 5:33 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| troy wrote: |
Thanks guys for ur response,
Let me summarize -
1. go to every other QM in your cluster, both PRs and FRs, and make sure that their one mandatory explicitly defined CLUSSNDR channel doesn't point at the guy you are about to demote from FR to PR
2. alter the QMGR attribute by making reposnl attribute as blank.
Thanks! |
Correct, and good spot, because I forgot to mention the explicit CLUSSDR on the other FR - doh!
_________________
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 |
|
|
|
|
