| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| De-clustering fun question |
« View previous topic :: View next topic » |
| Author |
Message
|
| cicsprog |
 Posted: Tue Mar 30, 2010 9:52 am Post subject: De-clustering fun question |
 |
|
Partisan
Joined: 27 Jan 2002
Posts: 347
|
We are removing two mainframe MQMs from 5 different clusters. Each MQM is a PR or a FR for some of these clusters. A new single cluster will now host all the app queues.
I've issued a SUSPEND to each of the 5 old clusters. As I go about issuing the proper commands to remove these MQMs from the various clusters, will there be a problem since the clusters are currently SUSPENDed? The issue being will the cluster subscription messages flow from the two MQM's leaving the cluster since they are SUSPENDed? |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Mar 30, 2010 11:47 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Huh?
SUSPEND tells the other qmgrs not to use me/my cluster queues as destinations for messages.
Once you have suspended a qmgr, AND all putting/getting apps have MQDISConnected, AND all cluster queues are empty, you are safe to alter the clustered objects on the qmgrs to be removed from the cluster.
Is this what you are asking?
_________________
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 |
|
|
| cicsprog |
| Posted: Tue Mar 30, 2010 12:04 pm Post subject: |
|
|
Partisan
Joined: 27 Jan 2002
Posts: 347
|
Yes...just wanted to make sure the SUSPEND I've done several days before I issue the de-cluster commands won't affect any internal MQM generated messages that may get sent to notify repositories that Q's and MQM's are leaving the cluster. Here's what I have on my slate. MQNA and MQNC are leaving these clusters:
----------------------------------------------------------------------
Declustering activities for Monday in order of execution.
----------------------------------------------------------------------
MQNA
SUSPEND QMGR CLUSTER(VSE/EAST/PRD) MODE(QUIESCE)
SUSPEND QMGR CLUSTER(WHS/PRD) MODE(QUIESCE)
SUSPEND QMGR CLUSTER(NCV/REWARDS/PRD) MODE(QUIESCE)
SUSPEND QMGR CLUSTER(EOI/SIG/PRD) MODE(QUIESCE)
MQNC
SUSPEND QMGR CLUSTER(VSE/EAST/PRD) MODE(QUIESCE)
SUSPEND QMGR CLUSTER(WHS/PRD) MODE(QUIESCE)
SUSPEND QMGR CLUSTER(EOI/SIG/PRD) MODE(QUIESCE)
----------------------------------------------------------------------
Declustering activities for Wednesday in order of execution.
----------------------------------------------------------------------
I don't see a need to RESUME the cluster for a short period of time if the SUSPEND won't affect the remaining de-clustering commands.
MQNA
RESUME QMGR CLUSTER(VSE/EAST/PRD)
RESUME QMGR CLUSTER(WHS/PRD)
RESUME QMGR CLUSTER(NCV/REWARDS/PRD)
RESUME QMGR CLUSTER(EOI/SIG/PRD)
MQNC
RESUME QMGR CLUSTER(VSE/EAST/PRD)
RESUME QMGR CLUSTER(WHS/PRD)
RESUME QMGR CLUSTER(EOI/SIG/PRD)
----------------------------------------------------------------------
MQTB
ALTER CHANNEL(TO.MQNC.00) TYPE(CLUSSDR) CLUSTER(' ')
REFRESH CLUSTER(VSE/EAST/PRD)
DELETE CHANNEL(TO.MQNC.00) TYPE(CLUSSDR)
MQTC
ALTER CHANNEL(TO.MQNC.00) TYPE(CLUSSDR) CLUSTER(' ')
REFRESH CLUSTER(VSE/EAST/PRD)
DELETE CHANNE(TO.MQNC.00) TYPE(CLUSSDR)
----------------------------------------------------------------------
MQNA
ALTER all Q's to remove cluster attributes for:
VSE/EAST/PRD
WHS/PRD
NCV/REWARDS/PRD
EOI/SIG/PRD
MQNC
ALTER all Q's to remove cluster attributes for:
VSE/EAST/PRD
WHS/PRD
NCV/REWARDS/PRD
EOI/SIG/PRD
----------------------------------------------------------------------
MQNA
SUSPEND QMGR CLUSTER(VSE/EAST/PRD)
SUSPEND QMGR CLUSTER(WHS/PRD)
SUSPEND QMGR CLUSTER(NCV/REWARDS/PRD)
SUSPEND QMGR CLUSTER(EOI/SIG/PRD)
ALTER CHANNEL(TO.MQNA.00) TYPE(CLUSRCVR) CLUSNL(' ')
DELETE NAMELIST('MQNANSS.NL.CLUSTERS')
STOP CHANNEL(TO.MQNA.00)
DELETE CHANNEL(TO.MQNA.00) TYPE(CLUSRCVR)
STOP CHANNEL(TO.MQNC.00) TYPE(CLUSSDR)
STOP CHANNEL(TO.MQREPOP2N.00) TYPE(CLUSSDR)
STOP CHANNEL(TO.MQSA.00) TYPE(CLUSSDR)
STOP CHANNEL(TO.MQTA.00) TYPE(CLUSSDR)
STOP CHANNEL(TO.NMPGU1KA.00) TYPE(CLUSSDR)
REFRESH CLUSTER(VSE/EAST/PRD)
REFRESH CLUSTER(WHS/PRD)
REFRESH CLUSTER(NCV/REWARDS/PRD)
REFRESH CLUSTER(EOI/SIG/PRD)
DELETE CHANNEL(TO.MQNC.00) TYPE(CLUSSDR)
DELETE CHANNEL(TO.MQREPOP2N.00) TYPE(CLUSSDR)
DELETE CHANNEL(TO.MQSA.00) TYPE(CLUSSDR)
DELETE CHANNEL(TO.MQTA.00) TYPE(CLUSSDR)
DELETE CHANNEL(TO.NMPGU1KA.00) TYPE(CLUSSDR)
----------------------------------------------------------------------
MQNC
ALTER -
NAMELIST('MQNCNSS.NL.CLUSTERS.WITH.FULL.REPOSITORIES') -
NLTYPE(CLUSTER) -
QSGDISP(QMGR) -
DESCR('MQNC CLUSTERS IN THIS MQM') -
NAMES( -
'FRC/PRD' -
)
MQNC
SUSPEND QMGR CLUSTER(VSE/EAST/PRD)
SUSPEND QMGR CLUSTER(WHS/PRD)
SUSPEND QMGR CLUSTER(EOI/SIG/PRD)
ALTER CHANNEL(TO.MQNC.00) TYPE(CLUSRCVR) CLUSNL(' ')
STOP CHANNEL(TO.MQNC.00)
DELETE CHANNEL(TO.MQNC.00) TYPE(CLUSRCVR)
DELETE NAMELIST('MQNCNSS.NL.CLUSTERS')
STOP CHANNEL(TO.MQREPOP2N.00)
STOP CHANNEL(TO.MQTA.00)
STOP CHANNEL(TO.MQTB.00)
STOP CHANNEL(TO.MQTC.00)
STOP CHANNEL(TO.NMPGU1KA.00)
DELETE CHANNEL(TO.MQREPOP2N.00) TYPE(CLUSSDR)
DELETE CHANNEL(TO.MQTA.00) TYPE(CLUSSDR)
DELETE CHANNEL(TO.MQTB.00) TYPE(CLUSSDR)
DELETE CHANNEL(TO.MQTC.00) TYPE(CLUSSDR)
DELETE CHANNEL(TO.NMPGU1KA.00) TYPE(CLUSSDR)
REFRESH CLUSTER(VSE/EAST/PRD)
REFRESH CLUSTER(WHS/PRD)
REFRESH CLUSTER(EOI/SIG/PRD) |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Mar 30, 2010 12:34 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| We are removing two mainframe MQMs from 5 different clusters. |
All that is really necessary is to SUSPEND the two offending qmgrs, and wait for all cluster-related work to dry up. SUSPEND tells other qmgrs not to use my/my cluster objects.
Next, all that is really necessary is to alter all of the cluster objects on these two offending qmgrs to CLUSTER(''). These qmgrs are now gone from the cluster(s).
You do not need to SUSPEND any other qmgrs, as they will be notified of the SUSPEND status pretty quickly.
There is no need to wait 3 days to do this. SUSPEND command informs other qmgrs pretty darn quickly; and no new MQOPENs will find the cluster queues on susended qmgrs.
_________________
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 |
|
|
| cicsprog |
| Posted: Tue Mar 30, 2010 12:43 pm Post subject: |
|
|
Partisan
Joined: 27 Jan 2002
Posts: 347
|
Ok Bruce.
I actually did the SUSPEND that early for a reason. We have sold a part of the our business. The datacenter where the two MQM's reside goes along with the sale. I reused the existing MQM's but created a new cluster so the new business could reuse the same apps but not use the existing cluster Q's. Once all the app data is moved out of this datacenter, the de-clustering needs to take place to seperate other MQM's in other locations. The SUSPENDs where done so that I could backoff easily should the project this last weekend to spilt the data fail.
Probably TMI, but there was a reason for the madness of issuing the SUSPENDs that far ahead.
Thanks Again. |
|
| 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
|
|
|
|
