mqsideletebroker command

Use the mqsideletebroker command to delete a named integration node. The command also deletes the queues on the associated queue manager (created when the integration node was created).

Purpose

The mqsideletebroker command:
  • On Windows platforms, stops the service that runs the integration node.
  • Deletes the administrative security queues that are associated with the integration node, if requested.
  • Removes the record for the component in the registry.

If you delete an integration node that has IBM MQ publish/subscribe integration node neighbors, you must also run the clrmqbrk on each of these neighbors. You must identify the integration node that you are deleting on this command.

Select the appropriate link for details of this command on the platform, or platforms, that your enterprise uses:

Usage notes

If you run the command against a component that does not exist (for example, the component has already been deleted, or you mistyped the component name), the command returns with a successful completion message. The command informs you that a component with the specified name is not a known component, but an attempt will be made to delete resources associated with the specified component (in the case where the component has already been deleted.) The command output also advises you what checks to carry out to resolve the issue.

You cannot delete an integration node to which you have an open connection; the command fails.

Occasionally, the command might fail to delete all aspects of an integration node, and can cause subsequent commands to incorrectly report the presence of the integration node or fail in attempts to run against the integration node. In such cases you see error messages, such as for the deleted integration node, IBNODE on Windows: BIP8133E: Unable to write to the selected output file ''C:\ProgramData\IBM\MQSI\ components\IBNODE\overrides/node.conf.yaml''. Some things that you can check after deleting an integration node are:
  • The presence of the integration node's component directory
  • On Windows, the presence of the integration node's service