|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Cluster Recevier Conname change |
« View previous topic :: View next topic » |
Author |
Message
|
cicsprog |
Posted: Tue Mar 30, 2010 1:11 pm Post subject: Cluster Recevier Conname change |
|
|
Partisan
Joined: 27 Jan 2002 Posts: 347
|
I have some old DNS names that reflect an old company name. The powers that be want to rename the DNS to something the reflects the current company name.
So I need to change the CONNAME parameter of Cluster Sender and Receivers to reflect the new DNS name. In addtion, the underlying IP will change.
Depending on what you read from IBM, this change may or may not be all that easy.
http://www-01.ibm.com/support/docview.wss?uid=swg21167844
and this from IBMLink
"Usage
View document
How to move a cluster queue manager from one LPAR to another
Technote (troubleshooting)
Problem(Abstract)
You want to reconfigure your WebSphere MQ cluster setup. You want to move your cluster queue manager (can be partial or full repository queue manager) from one LPAR to another.
Resolving the problem
Assume that you are going to move the Queue Manager XYZ in ClusterA from LPAR A to LPAR B. To do this, perform the following steps:
If there are only 2 full repository qmgrs for this cluster, and both full repository qmgrs are to be moved at once.
See: Problem 4 — 2 full repositories moved at the same time.
If there are only two full repository qmgrs for this cluster, and only one of these is being moved.
The following steps should be used:
1. Suspend queue manager XYZ.
SUSPEND QMGR CLUSTER(clustername)
2. Alter XYZ's CLUSRCVR channel to its new conname.
ALTER CHANNEL(chlname) CHLTYPE(CLUSRCVR) CLUSTER(clustername) CONNAME(new_conname)
3. Stop queue manager XYZ on LPAR A.
4. Re-start queue manager XYZ on LPAR B.
5. Resume queue manager XYZ.
RESUME QMGR CLUSTER(clustername)
6. If qmgr XYZ is a full repository qmgr, alter the conname of any CLUSSDR definitions that point to this qmgr.
ALTER CHANNEL(chlname) CHLTYPE(CLUSSDR) CLUSTER(clustername) CONNAME(new_conname)
If there are more than 2 full repository qmgrs,it would be best to change the full repository qmgr that is being moved, and make it a partial repository before the above steps are carried out. Then set it back to being a full repository qmgr after the above steps have been followed.
Instructions for doing this can be found in:
Task 5: Moving a full repository to another queue manager.
Follow steps 1-3 of Task 5 to change a partial repository to a full.
Follow steps 4-5 of Task 5 to change a full repository to a partial. "
Has anyone done this sort of change? What problems did you encounter and what commands did you have to enter to accomplish?
Thanks!
Last edited by cicsprog on Tue Mar 30, 2010 2:30 pm; edited 1 time in total |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Mar 30, 2010 2:15 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Looks like you're missing the part where you blank out the cluster attributes of the cluster receiver before changing the conname and reinstate them after changing the conname...  _________________ MQ & Broker admin |
|
Back to top |
|
 |
cicsprog |
Posted: Tue Mar 30, 2010 2:29 pm Post subject: |
|
|
Partisan
Joined: 27 Jan 2002 Posts: 347
|
Ya....even though these IBM docs refer to different reasons for changing the conname, they are trying to do what I am. However, the documents differ in the method to accomplish. I even got different answers from IBM L2, Hursley, and IBM Software Engineers.
I think the method you state is the way I'd do it. But, I thought if someone else I had done this, I might get some tips. |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Mar 30, 2010 8:17 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
cicsprog wrote: |
Ya....even though these IBM docs refer to different reasons for changing the conname, they are trying to do what I am. However, the documents differ in the method to accomplish. I even got different answers from IBM L2, Hursley, and IBM Software Engineers.
I think the method you state is the way I'd do it. But, I thought if someone else I had done this, I might get some tips. |
Well I tried it without doing the upper part, about a year ago and it does not come through clean... (gets a little bit messy: easy to handle in a cluster of 10, a nightmare if your cluster size is over 100...). To get the change through clean and propagate it right you should blank out the cluster attributes while changing the conname.  _________________ MQ & Broker admin |
|
Back to top |
|
 |
sumit |
Posted: Wed Mar 31, 2010 7:07 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006 Posts: 398
|
|
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
|
|
|
|