WebSphere Message Brokers
File: an26100_
Writer: Bill Oppenheimer

Reference topic

This build: July 31, 2007 21:33:56

mqsistartmsgflow command

Supported platforms

Purpose

Use the mqsistartmsgflow command to start message flows.

Syntax

Parameters

-b BrokerName
(Required) The name of the broker on which to start message flows.

If you do not specify the -e and -m flags, all message flows on the broker are started.

-e ExecutionGroupName
(Optional) The name of the execution group on which message flows are started.
-m MsgFlowName
(Optional) The name of the message flow being 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.

-n CfgParameterFileName
(Optional) This parameter specifies the name of a .configmgr file that describes the connection parameters to the Configuration Manager.
The file is in XML, using the .configmgr format that is saved by the workbench; for example:
<?xml version="1.0" encoding="UTF-8"?>
<configmgr crlNameList="" domainName="" host="winmvsd0" listenerPort="2206" 
queueManager="mq06" securityExit="" securityExitJar="" sslCipherSuite="NONE" 
sslDistinguishedNames="" sslKeyStore="" sslTrustStore="" svrconn="SYSTEM.BKR.CONFIG"/>
If you are using this file on z/OS you must remove the statement encoding="UTF-8" from the first line, and remove the value for the host attribute, to leave the statement as:
<?xml version="1.0"?>
<configmgr crlNameList="" domainName="" host="" listenerPort="2206" 
queueManager="mq06" securityExit="" securityExitJar="" sslCipherSuite="NONE" 
sslDistinguishedNames="" sslKeyStore="" sslTrustStore="" svrconn="SYSTEM.BKR.CONFIG"/>

If you do not supply this parameter, you must supply the -i, -p, and -q parameters.

-i IpAddress
(Optional) This parameter specifies the host name or IP address of the Configuration Manager.

If you are using this parameter on z/OS and want to connect to the local host you must set the value to "".

-p Port
(Optional) This parameter is the port number of the Configuration Manager.
-q QMgr
(Optional) This parameter specifies the name of the WebSphere MQ queue manager that the Configuration Manager is using.

If you do not supply the -i, -p, and -q parameters, you must specify the -n parameter.

-w TimeoutValue
(Optional) This parameter is the time in seconds that the utility waits to ensure that the command completed; the default value is 60.
-v TraceFileName
(Optional) This parameter sends internal debug trace information to the specified file.

Authorization

To start message flows you must 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 Broker Toolkit; see ACL permissions for a list of permissions that can be defined in the Configuration Manager.

Responses

This command returns the following responses:
0
(Success) States that the request completed successfully and the state of all message flows has been updated.
2
(Failure) States that at least one message flow can not be put into the correct state for any reason.
98
States that the Configuration Manager cannot be reached.
99
States that the supplied arguments to the utility are not valid.

Examples

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

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:33:56

an26100_ This topic's URL is: