mqsichangebroker command

Use the mqsichangebroker command to change one or more of the configuration parameters of the integration node.

Note: You can use the mqsireportbroker command to report the current values of the configuration parameters of the integration node before you change anything, and to confirm any changes that you made. See mqsireportbroker command for more information.

Supported platforms

Windows
Linux® and UNIX systems
z/OS®. Run this command either as a console command, or by customizing and submitting BIPCHBK; see Contents of the integration node PDSE

Purpose

You can modify the value of many, but not all, of the parameters that you set when you created the integration node. For example, after you change a password, you must run the mqsichangebroker command. You can also use this command to set the UserExitPath property or to enable administrative authority.

You can use the mqsichangebroker command with the -c parameter on WebSphere® Message Broker Version 8.0 in the same way that you did for WebSphere Message Broker Version 6.1.

However, the converter file name must follow the WebSphere Message Broker Version 8.0 form, and the location given must specify the path up to, but not including, the icudt38b component; see Generating a new code page converter for further information.

You must stop the integration node before you issue this command, and restart the integration node for the changes to take effect:

On Windows, Linux, and UNIX systems, use the mqsistop and mqsistart commands to stop and restart the integration node.
On z/OS, you must have started the original integration node control process by using the /S option. You must stop the integration node components using the /F integration node, PC option and start the integration node components again using the /F integration node, SC option.

On Windows systems, Linux, and UNIX systems, use this command to specify whether the integration node can start and stop as a WebSphere MQ service.

Use the -f (function level) parameter to specify functions that become available in IBM Integration Bus fix packs. See the version of the command that is applicable to your enterprise for more information.

In IBM Integration Bus Version 10.0, the -4 integrationRegistryHostName parameter is deprecated. The ability to share an Integration Registry across a multi-instance integration node environment is now available without the need to designate an Integration Registry host name.

When you create a multi-instance integration node, the resources are stored on a shared file system. The user that issues the mqsicreatebroker command must have the correct permissions on the shared file system to create these resources.

For details of this command on the operating system that your enterprise uses, see the appropriate topic:

Authorization

For information about platform-specific authorizations, see the following topics:

If you have enabled integration node administration security, you must also set up the authority that is detailed in Tasks and authorizations for administration security.