Starting Stopping message flows IIB

Starting Stopping message flows IIB listed below for reference (considering IBM Integration Bus v9.0.0.0)

Starting a message flow

mqsistartmsgflow command can be used for the following purposes:

To start a specific message flow in an integration server
To start all message flows in the integration server
To start a specific integration server
To start all integration servers
To start a message flow in a specific application or library or both
To start all message flows in a specific application or library or both
To start a specific application
To start all applications

mqsistartmsgflow command usage

mqsistartmsgflow <broker name> <attributes>

Where attributes are,

-e integrationServerName
The name of the integration server for which to start message flows. You must specify either -e or -g.
-g
The specified message flow or flows are started on all integration servers on the specified broker. You must specify either -e or -g.
-j
All message flows in the specified integration server are started.
-k applicationName
The name of an application to which to target a start request.
-m flowName
The name of the message flow being started.
-v traceFileName
This parameter sends internal debug trace information to the specified file.
-w timeoutSecs
This parameter specifies the time in seconds that the utility waits to ensure that the command completed; the default value is 60.
-y libraryName
The name of a library to which to target a start request.
-z
The -z parameter indicates that all applications in an integration server are to be started.

mqsistartmsgflow command examples (as mentioned in IBM Knowledge Center)

Start a named message flow that you have deployed to integration server eg1 on the broker IB9NODE:
mqsistartmsgflow IB9NODE -e eg1 -m simpleflow

Ensure that all message flows are running on the local broker IB9NODE:
mqsistartmsgflow IB9NODE -g -j

Start the message flow myFlow1 in the application myApplication in the default integration server:
mqsistartmsgflow IB9NODE -e default -k myApplication -m myFlow1

Start the message flow myFlow1 in the library myLibrary, which is referenced by the application myApplication, in the default integration server:
mqsistartmsgflow IB9NODE -e default -k myApplication -y myLibrary -m myFlow1

Start all message flows and start all applications in the default integration server:
mqsistartmsgflow IB9NODE -e default -z -j

Stopping a message flow

mqsistopmsgflow command can be used for the following purposes:

To stop a specific message flow in an integration server
To stop all message flows in the integration server
To stop a specific integration server
To stop all integration servers
To stop a message flow in a specific application or library or both
To stop all message flows in a specific application or library or both
To stop a specific application
To stop all applications

mqsistopmsgflow command usage

mqsistopmsgflow <broker name> <attributes>

Attributes are,
-e integrationServerName
The name of the integration server for which to stop message flows. You must specify either -e or -g.
-f
Used with the –m, –e, and –k parameters to force the named message flow to stop within the named integration server or the named application.
-g
The specified message flow or flows are stopped on all integration servers on the specified broker. You must specify either -e or -g.
-j
All message flows in the specified integration server are stopped; the integration server is not stopped.
-k applicationName
The name of an application to which to target a stop request.
-m flowName
The name of the message flow being stopped.
-v traceFileName
This parameter sends internal debug trace information to the specified file.
-w timeoutSecs
This parameter specifies the time in seconds that the utility waits to ensure that the command completed; the default value is 60.
-y libraryName
The name of a library to which to target a stop request.
-z
The -z parameter indicates that all applications in an integration server are to be stopped.

mqsistopmsgflow command examples

Stop a named integration server on broker IB9NODE:
mqsistopmsgflow IB9NODE -e eg2

Stop all integration server processes on the local broker IB9NODE:
mqsistopmsgflow IB9NODE -g

Stop the message flow myFlow1 in the application myApplication in the default integration server:
mqsistopmsgflow IB9NODE -e default -k myApplication -m myFlow1

Stop the message flow myFlow1 in the default integration server and restart the default integration server:
mqsistopmsgflow IB9NODE -e default -m myFlow1 -f restartExecutionGroup

Stop the message flow myFlow1 in the library myLibrary, which is referenced by the application myApplication, in the default integration server:
mqsistopmsgflow IB9NODE -e default -k myApplication -y myLibrary -m myFlow1

Stop all message flows and stop all applications in the default integration server:
mqsistopmsgflow IB9NODE -e default -z -j

Message Flow related IIB v9.0 knowledge center link here and Command reference here