See information about the latest product version
mqsistart command
Use the mqsistart command to start the specified broker if all initial verification tests complete successfully.
Supported platforms
- Windows
- Linux and UNIX systems
- z/OS® as a console command.
Purpose
The mqsistart command:
- On distributed systems, starts the associated queue manager if it is not running.
- Checks that the broker environment is set up correctly; for example, that the installed level of Java™ is supported.
- Verifies that the WebSphere® MQ queues
are defined and accessible.
The command completes these checks, and reports all errors in the system log, or to the command line, or both. If one or more checks fail, the command does not start the component.
- On Linux and UNIX systems, where the mqsisetdbparms command has
been used to associate the datasource with the broker, the mqsistart command:
- Checks broker connectivity to, and
- Performs tests against
If any issues are identified, a warning is reported to the system log and command line. However, this step does not prevent the broker from starting cleanly.
- Checks the publish/subscribe mode (attribute PSMODE) of the queue manager associated with the broker. If the PSMODE is set to DISABLED, it is changed to COMPAT and this is reported to the system log. If the PSMODE is already set to COMPAT or ENABLED, the setting is not changed.
Authorization
- Security requirements for Linux and UNIX platforms
- Security requirements for Windows systems
- Security requirements for z/OS
The broker starts only if the user ID under which it will run is authorized to access both the following locations. On Windows, the user ID is defined by the ServiceUserID specified on mqsicreatebroker; on Linux and UNIX systems, it is the user ID with which you run this command:
- Home directory, where WebSphere Message Broker has been installed.
- Working directory, if specified by the -w flag on the mqsicreatebroker command.