mqsistart command - Windows, Linux, and UNIX platforms

The mqsistart command does not start any resources that are associated with the integration node, such as listeners, channels, or channel initiators.

If a queue manager is associated with the integration node (defined by the mqsicreatebroker command), it is not started by the mqsistart command. The mqsistart command checks if the queue manager associated with the integration node is running, and if it is not, returns an error. To start the associated queue manager, use the command line. For more information, see the topics on starting and stopping a queue manager in the WebSphere® MQ documentation.

Successful completion of this command indicates that the Windows service, or Linux® or UNIX daemon started successfully, and that the integration node startup is initiated. Check the Windows system event log or the Linux or UNIX syslog to determine whether the integration node and all related software started successfully, are initially active, and remain in an active state.

All errors that prevented successful start-up that are detected by the integration node are recorded in the log. Continue to monitor the Windows system event log or Linux or UNIX syslog.

integrationNodeName

(Required) Specify the name of the integration node that you want to start.

On Linux and UNIX systems, all names are case-sensitive.