| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Deleting explicit CLUSSNDRs |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Mon May 05, 2003 11:45 am Post subject: Deleting explicit CLUSSNDRs |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
Is there any reason I could not delete the CLUSSNDR channels I manually created when I introduced the queue manager to the cluster? I see that dynamic CLUSSNDRs are created anyway, and I assume these are the ones being used. In the interest of having as few MQ objects as possible (the less things there are to look at when there is a problem, the better), I deleted them, even between the two full repositories.
My cluster seems OK. Messages are round robining. New objects are being recognized throughout the cluster. Am I safe?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Tue May 06, 2003 6:54 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
I am going to put them back.
If you read the details for the REFRESH CLUSTER command, it says that if you specify the REPOS YES paramaeter, the manually defined CLUSSNDRs are used. Without them I assume the command would fail.
| Quote: |
The following documents the REPOS option of the REFRESH CLUSTER command.
REPOS
Specifies whether objects representing full repository cluster queue
managers are also refreshed.
NO
The queue manager retains knowledge of all cluster queue
manager and cluster queues marked as locally defined, and all
cluster queue managers that are marked as full repositories. In
addition, if the queue manager is a full repository for the
cluster, it retains knowledge of the other cluster queue
managers in the cluster. Everything else is removed from the
local copy of the repository and rebuilt from the other full
repositories in the cluster. Cluster channels are not stopped
if REPOS(NO) is used, a full repository uses its CLUSSDR
channels to inform the rest of the cluster that it has
completed its refresh.
This is the default.
YES
Specifies that in addition to the REPOS(NO) behavior, objects
representing full repository cluster queue managers are also
refreshed. This option must not be used if the queue manager is
itself a full repository, if it is a full repository, you must
first alter it so that it is not a full repository for the
cluster in question. The full repository location is recovered
from the manually defined CLUSSDR definitions. After the
refresh with REPOS(YES) has been issued, the queue manager can
be altered so that it is once again a full repository, if
required.
On z/OS, N and Y are accepted synonyms of NO and YES.
|
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
