Posted: Fri Aug 26, 2016 6:34 am Post subject: Deleted QM and broker displayed in mqsilist command
Centurion
Joined: 16 Oct 2011 Posts: 124 Location: London
Hi Guys,
I have created a test queue manager and a test broker. Later I deleted both. But when I use mqsilist, among with the existing brokers, the delted QM and broker is also displayed
BIP1285I: Broker 'BRK_TESTQM' on queue manager 'TESTQM' is stopped.
When I issued dspmq command, this qm is not displayed either. Did I missed anything while deleteing
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
It would be really nice to know some details.
For example
1) What version of MQSI/WMB/IIB are you using (please include the fixpack)
2) What version of MQ are you using (please include the fixpack)
3) What platform this is. eg Windows 7 64bit.
4) Output from MQSILIST
5) output from mqsideletebroker
At the preset time you post is almost devoid of hard facts. We can only guess the reasons for your problems.
As the saying goes, "The devil in in the Detail."
There is a fantastic document on the IBM website that details the sort of data you would need to collect and collate before IBM would accept a PMR from you. We don't need all that data but is gives you a good idea what sort of thing would help us to help you. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
When mqsilist is used to list Brokers it will primarily use the IIB registry folder to determine which brokers exist at that level. As such it will iterate over each Broker folder in the IIB registry folder and then check it has four basic fields to determine that it is an active broker. For your broker to be showing up in mqsilist means that there is still a registry folder for it that contains the queue manager and FAD level data files. The fact that it has issued the message saying the broker is stopped means that (a) The bipbroker is not running for the broker and (b) the AdminAgentPID file is 0. mqsideletebroker would not have allowed you delete the broker if it was running. So to me this sounds like the mqsideletebroker command did not complete succcessfully. Unfortunately without a trace of the command (or a time machine) it will be difficult to tell whether that was the case.
As indicated in the previous response it would be useful to know what product version this is as IIB V10 is quite different in this area to previous versions. Can you take a look in your work path to see if you have a folder for this broker in the registry and components directories? _________________ Regards
Craig
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