I think I understand your point but since the Windows/NT MQExplorer gives you all by displaying a panel that also has a tab (Cluster) where is one can see this does make things a little easier. In a large MQ environment with many Qmgrs I look to find any and all ways that might save me a command or two. I thought my suggestion might have aided the art of discovery. Thanx for your note. BB.
> -----Original Message----- > From: Wyatt, T. Rob [SMTP:[EMAIL PROTECTED]] > Sent: Monday, November 18, 2002 3:27 PM > To: [EMAIL PROTECTED] > Subject: Re: dis qmgr all > > The thing that primarily makes a QMgr "belong" to a cluster is the > presence > of CLUSSDR and CLUSRCVR channels. If the QMgr successfully connects to a > repository via these channels, it is then enrolled in a cluster. > > The DIS QMGR command displays the attributes of a QMgr object. The only > QMgr attributes that pertain to clusters are the cluster exit and repos > attributes. The absence or presence of data in these fields does not > indicate much of anything about the QMgr's enrollment in a cluster. You > can > put a value in the REPOS attribute that matches an existing cluster but > without the channels, it is not a member of the cluster. Alternatively, > the > REPOS attribute may be blank and the QMgr is participating in a cluster, > just not as a repository. So inquiring *just* on the QMgr object does not > give any definitive answers about cluster membership. > > My take on this is that the DIS * commands inquire on a particular object > or > class of objects (dis qmgr, dis q, dis chl, etc.). Determination of a > QMgr's enrollment and status in a cluster requires several commands on > different object types - check for cluster channels, check for repository > hosting, check for known and hosted cluster objects, etc. In this > respect, > the DIS QMGR is an atomic command whereas DIS CLUSQMGR is a compound > command. I think the consistency lies in keeping a full set of atomic > commands that inquire strictly on their own object or type, and adding > compound commands like DIS CLUSQMGR as needed. If this is indeed the > model > IBM is following, I wouldn't expect to see this functionality added to DIS > QMGR *unless* they add an attribute to the QMgr object that explicitly > indicates cluster membership. > > -- T.Rob > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Monday, November 18, 2002 12:42 PM > To: [EMAIL PROTECTED] > Subject: dis qmgr all > > > How come when I do the above command uder MQSC i don't see what the fact > that Qmgr belongs to a cluster? I know that if you do a 'dis clusqmgr(*) I > can see it but wouldn't it be convenient to see it both places. I can see > it > via the MQExplorer. Is this not inconsistent?? BB. > > Bruce Barclay > Cell: 613-794-8423 > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
