Use the mqsilist command to list information about one or more integration nodes and their deployed resources.
>>-mqsilist-----------------------------------------------------> >--+------------------------------------------------+-----------> '-| brokerSpec |--+----------------------------+-' '- e=--integrationServerName-' >--+-------------------+--+-----------------------+--+------+---> '- d= --detailLevel-' '- k= --applicationName-' '- r= -' >--+---------------------+--+-------------------+---------------> '- v= --traceFileName-' '- w= --timeoutSecs-' >--+-------------------+--------------------------------------->< '- y= --libraryName-' brokerSpec |--+- integrationNodeName ---------+----------------------------| +- n= --integrationNodeFileName-+ +- i= --ipAddress-- -p --port---+ '-+- i= --ipAddress-+-----------' '- p= --port------'
Synonym: l
>>-+-list-+--+--------------------------+--+--------+-----------> '-l ---' '- e=integrationServerName-' '- r=yes-' >--+----------------+------------------------------------------>< '- d=detailLevel-'
If you specify this command with no parameters, a list of the integration servers is displayed.
Use this option if multiple users want to connect to the same integration node, or if you are using advanced connection parameters such as SSL.
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.
If you are connecting to a remote integration node, you can additionally prefix integrationNodeName to explicitly set which integration node to connect to. You cannot use -n integrationNodeFileName in the same command.
Parameters that you omit assume default values:
If you want to connect to a remote host name, provide the security credentials as a URI in the following format: protocol://user:password@hostname. If your password contains URI Reserved characters, you must convert these characters to the percent-encoded format. For more information, see A correct URL and password returns error BIP1939 when you attempt to connect to a remote host name in Resolving problems when running commands.
Note that while they are starting, integration servers might report a PID of 0.
The specified integration node must be active for message flow information to be returned.
In previous versions of IBM® Integration Bus, you might have used the q= parameter for this command to define a connection to a queue manager. A queue manager connection is no longer used to connect to an integration node. The q= parameter is now deprecated, and is ignored if used. If you use the q= parameter, a BIP1922 warning is displayed.
F MQP1BRK,list
BIP1286I
is generated. F MQP1BRK,list e='intserv1'
BIP1288I is
generated. F IBNODE,list e='default' k='myApplication' y='myISLibrary'
For examples of running the command by using BIPLIST, and the responses that are generated, see mqsilist command - Windows, Linux, and UNIX systems.