If you do not specify the -e and -m flags, all message flows on the broker are started.
You can specify only one message flow in a single command. However, if you do not specify this parameter, all message flows on the execution group or broker are started.
If you specify this flag you must also specify the -e flag.
<?xml version="1.0" encoding="UTF-8"?> <configmgr host="localhost" listenerPort="1414" queueManager="QNAME" securityExit="test.myExit"/>
<?xml version="1.0"?>and remove the value for the host attribute, to leave the statement as:
<configmgr host="" listenerPort="1414" queueManager="QNAME" securityExit="test.myExit"/>
If you are using this file on z/OS and want to connect to the local host you must set the value to "".
If you do not supply the -i, -p, and -q parameters, you must specify the -n parameter.
To start message flows you need to have sufficient authority defined in the Configuration Manager’s access control list.
The permissions required are the same as the permission required to do the equivalent function in the Message Brokers Toolkit; see ACL permissions for a list of permissions that can be defined in the Configuration Manager.
Starts all message flows on broker B1, which is controlled by the Configuration Manager whose connection details are described in cm1.configmgr. Control is returned to the caller when all message flows in the broker are reported as started, or the default time of one minute elapses, whichever is sooner.
mqsistartmsgflow –n cm1.configmgr –b B1
Starts all message flows on broker B1, which is controlled by the Configuration Manager whose connection details are described in cm1.configmgr. Control is returned to the caller when all message flows in the broker are reported as started, or two minutes elapses, whichever is sooner.
mqsistartmsgflow –n cm1.configmgr –b B1 –w 120
Start all message flows on Broker B1, which is controlled by the Configuration Manager. The Configuration Manager is hosted by the queue manager QM1 which is on local host:1414.
mqsistartmsgflow –q QM1 –i localhost –p 1414 –b B1
Enter mqsistartmsgflow to display usage information:
> mqsistartmsgflow BIP1024I: Starts message flows. > Syntax: mqsistartmsgflow (-n cfgParameterFileName | (-i ipAddress -p port -q qMgr)) -b brokerName [-e executionGroupName [-m flowName]] [-w timeoutValue] [-v traceFileName] Command Options: '-n cfgParameterFileName' File containing Configuration Manager connection parameters (.configmgr) '-i ipAddress' IP address or host name of the Configuration Manager '-p port' port number of the Configuration Manager '-q qMgr' queue manager of the Configuration Manager '-b brokerName' name of the broker on which to start message flows '-e executionGroupName' name of the execution group on which to start message flows. If this is not specified, all message flows on the broker will be started. '-m flowName' name of the message flow to start. If this is not specified, all message flows on the execution group will be started. '-w timeoutValue' time to wait (in seconds) for message flows to start (Default=60) '-v traceFileName' send verbose internal trace to the specified file.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
an26100_ |