See information about the latest product version
mqsilist command - Windows, Linux, and UNIX systems
Use the mqsilist command to list information about one or more brokers and their deployed resources.
Syntax
>>-mqsilist--+----------------------------------+---------------> +- -a -----------------------------+ '-| brokerSpec |--+--------------+-' '- -e --egName-' >--+-------------------+--+-----------------------+--+------+---> '- -d --detailLevel-' '- -k --applicationName-' '- -r -' >--+---------------------+--+-------------------+---------------> '- -v --traceFileName-' '- -w --timeoutSecs-' >--+-------------------+--------------------------------------->< '- -y --libraryName-' brokerSpec |--+- brokerName ----------------+------------------------------| +- -n --brokerFileName--------+ | .-------------------------. | | V | | '-----+- -i --ipAddress-+---+-' +- -p --port------+ '- -q --qMgr------'
If you specify this command with no parameters, a summary is returned for broker that you have created in the current installation on this computer.
The current installation is associated with the command console that you have opened (on Windows), or the mqsiprofile that is active (on Linux and UNIX systems).
Parameters
- brokerSpec
- (Required) You must specify at least one parameter
to identify the target broker for this command, in one of the following
forms:
- brokerName
- This parameter identifies the name of a locally defined broker. You cannot use this option if the broker is on a remote computer.
- -n brokerFileName
- This parameter identifies the name of a file that contains the
connection details for a local or remote broker.
Use this option if multiple users want to connect to the same broker, or if you are using advanced connection parameters such as SSL.
To create this file, right-click the broker in the WebSphere® Message Broker Explorer and select Export *.broker file. When prompted, navigate to the location in which you want to save the file and enter the file name; the extension .broker is appended automatically when you click Save. Include the location (path) and file name when you specify this parameter. You must ensure that the location is accessible when you run this command.
If you want to run a command that uses SSL to administer a remote broker over a secured channel, you must specify the keystore and truststore password for the connection using the IBM_JAVA_OPTIONS environment variable. See Resolving problems when running commands for further information.
- -i ipAddress, -p port, -q qMgr
- These parameters identify the connection details for the broker.
Use this option for connections to remote brokers that do not require advanced connection parameters.
If you choose this option, you must specify at least one of these three parameters; the order in which you specify them is insignificant. You cannot specify each parameter more than once.
Parameters that you omit assume default values:
- -i ipAddress: The host name or the IP address of the computer on which the broker is running. If you do not specify this parameter, a value that represents the local computer is used.
- -p port: The TCP port on which the broker's queue manager is listening. If you do not specify this parameter, the value 1414 is used.
- -q qMgr: The name of the broker's queue manager. If you do not specify this parameter, a value that represents the default queue manager on the local computer is used.
- -a
- (Optional) List all the brokers installed on the local computer,
in all installations.
If you specify this option on a computer on which you have installed versions earlier than Version 7.0, only brokers are listed for those versions, if they exist; the level of detail corresponds to -d 0 for these earlier brokers, even if you have specified (or allowed to default) a different level of detail on this command. If you want to view information about other components that you have created in earlier versions, you must use the corresponding version of the mqsilist command.
You cannot use this option to list information about remote brokers and their resources.
- -d detailLevel
- (Optional) Specify the level of detail to be returned; the default
value is 1.
- 0 returns only broker name and the names of their associated queue managers (this information is the same as the detail provided in previous versions). This list of local brokers is returned without connecting to a queue manager, and remote broker options are not supported.
Note that while they are starting, execution groups might report a PID of 0.
- 1 returns a one line summary of each resource.
- 2 returns detailed information about each resource.
- 0 returns only broker name and the names of their associated queue managers (this information is the same as the detail provided in previous versions). This list of local brokers is returned without connecting to a queue manager, and remote broker options are not supported.
- -e egName
- (Optional) Selects an execution group within a broker.
Specify the label of the execution group for which you want to list message flows. The command returns a list
of message flows assigned to the specified
execution group within the broker.
The specified broker must be active for message flow information to be returned.
- -k applicationOrServiceName
- (Optional) This parameter lists the deployed objects that are configured for an application or a service. When you use this parameter, you must also specify an execution group by using the -e parameter.
- -r
- (Optional) Run the command recursively; display information about subcomponents.
- -v traceFileName
- (Optional) This parameter sends internal debug trace information to the specified file.
- -w timeoutSecs
- (Optional) This parameter specifies the time in seconds that the utility waits to ensure that the command completed; the default value is 60.
- -y libraryName
- (Optional) This parameter lists the deployed objects that are configured for a library. When you use this parameter, you must also specify an execution group by using the -e parameter. You can also use the -k parameter with this parameter to list the contents of a specific library in the application specified by the -k parameter.
Examples
mqsilist -d0
BIP8099I: Broker: MB8BROKER - MB8QMGR
BIP8099I: Broker: test - testqm
BIP8071I: Successful command completion.
mqsilist MB8BROKER -e default -k myApplication
mqsilist MB8BROKER -e default -k myApplication -y myEGLibrary
mqsilist MB8BROKER -e default -k myApplication -d2
mqsilist MB8BROKER -e default -k myApplication -r
mqsilist MB8BROKER
BIP1286I: Execution group 'ello' on broker 'MB8BROKER' is running.
BIP8071I: Successful command completion.
mqsilist -a -r -d2
BIP1280I: The number of runtime installations on this machine is '1'.
7.0.0.0 : C:\Program Files\IBM\MQSI\7.0
===================================
BIP1284I: Broker 'MB7BROKER' on queue manager 'MB7QMGR' is running.
Broker version: '7000' (build 'S000-L90708')
Platform: 'Microsoft Windows'
Process ID: '3116'
Short description: ''
Long description: ''
-----------------------------------
BIP1286I: Execution group 'ello' on broker 'MB7BROKER' is running.
Number of message flows that are enabled to run: '2'.
Number of applications that are enabled to run: '1'.
Process ID: '4220'
UUID: '45ef67ac-2201-0000-0080-f364270ba85e'
Short description: ''
Long description: ''
--------
BIP1288I: Message flow 'simpleflow' on execution group 'ello' is running.
Additional thread instances: '0'
Deployed: '24/07/09 16:37' in Bar file 'C:\Documents and Settings\Matt\My Documents\BAR Files\test.bar'
Last edited: '08/08/07 17:42'
User-defined property names:
Keywords:
Author = 'Matt'
Information = 'This flow simply removes messages from SYSTEM.DEFAULT.LOCAL.QUEUE'
Usage = 'This usage is buried inside the CMF'
VERSION = 'v1.1'
--------
BIP1288I: Message flow 'MyApplicationFlow' on execution group 'ello' is running.
Additional thread instances: '0'
Deployed: '27/07/09 20:15' in Bar file 'C:\Documents and Settings\Matt\My Documents\BAR Files\overridden.bar'
Last edited: '12/06/07 17:06'
User-defined property names:
Keywords:
--------
BIP1290I: File 'Swift_2002_MT103.dictionary' is deployed to execution group 'ello'.
Deployed: '27/07/09 16:47' in Bar file 'C:\Documents and Settings\Matt\My Documents\BAR Files\SWIFT.bar'
Last edited: '06/09/05 15:17'.
Keywords:
===================================
BIP1285I: Broker 'test' on queue manager 'testqm' is stopped.
Start the broker for more information.
BIP8071I: Successful command completion.
BIP1280I: The number of runtime installations on this machine is '1'.
7.0.0.0 : C:\Program Files\IBM\MQSI\7.0
===================================
BIP1292I: Broker 'MIBROKER1' is a multi-instance broker .
The broker instance is running in Standby-mode on multi-instance
Queue manager ‘MIQMGR1'
More information will be available when the broker instance is active.
BIP8071I: Successful command completion
BIP1280I: The number of runtime installations on this machine is '1'.
7.0.0.0 : C:\Program Files\IBM\MQSI\7.0
===================================
BIP1293I: Broker 'MIBROKER1' is a multi instance broker .
The broker instance is active and running on multi-instance
Queue manager ‘MIQMGR1'
-----------------------------------
BIP1286I: Execution group 'default' on broker 'MIBROKER1' is running.
Number of message flows that are enabled to run: '1'.
Number of applications that are enabled to run: '1'.
Process ID: '4876'
UUID: '45ef7be4-2203-0000-0080-b764270fa96c'
Short description: ''
Long description: ''
--------
BIP1288I: Message flow 'jmsflow' on execution group 'default' is running.
Additional thread instances: '0'
Deployed: '26/09/09 18:21' in Bar file 'C:\Documents and Settings\JDoe\My Documents\
BAR Files\test.bar'
Last edited: '24/09/09 12:16'
User-defined property names:
Keywords:
Author = 'JDoe'
Information = 'This flow runs a simple jms scenario'
Usage = 'Takes JMS input and writes to an MQOutput node'
VERSION = 'v2.3'
--------
BIP8071I: Successful command completion.
BIP1296I: Broker 'HABK1' is a multi-instance broker that will be started as a WebSphere MQ service.
Multi-instance queue manager 'HAQM1' is stopped.
BIP1298I: Broker 'BK3' will be started as a WebSphere MQ service.
Queue manager 'QM3' is stopped.