WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Rules for using commands
Observe the following rules when using the WebSphere® Message Broker commands on distributed systems.
If you are using commands on z/OS®, refer to the section on z/OS commands in Commands.
- Each command must be issued on the system on which the resource to which it relates is defined (or is to be created).
- Each command starts with a primary keyword (the executable command name) followed by one or more blanks.
- Following the primary keyword, flags (parameters) can occur in any order.
- Flags are shown in this book in the form -t, for example. In all cases, the character / can be substituted for the - character.
- If a flag has a corresponding value, its value must follow the flag to which it relates. A flag can be followed by its value directly or can be separated by any number of blanks.
- Flags can be concatenated if they do not have corresponding values,
although the last flag in a concatenated group can have a value
associated with it. For example, the command:
can be entered as:mqsireadlog MB8BROKER -u -e default -o trace.xml -f
where the name of the execution group, default, relates to the -e flag. For clarity, all examples given in this documentation are shown with separate flags and with a space before any associated value.mqsireadlog MB8BROKER -ufedefault -o trace.xml
- Repeated flags are not allowed.
- Strings that contain blanks or special characters must be enclosed
in double quotation marks. For example:
Additionally, you can specify a null, or empty, string with a pair of quotation marks with nothing between: "".mqsireadlog "My Broker" -u -e default -o trace.xml -f
If you are running a command by submitting one of the JCL utilities (see Contents of the broker PDSE), and an argument to one of the parameters contains a blank character, you must replace the blank with the mnemonic   before you submit the JCL. For example, if you are using BIPDPLY to run the mqsideploy command to delete a deployed .jar file that is named my jar.jar from the execution group default, then modify the JCL to contain the following sample:
mqsideploy MB8BROKER -e default -d my jar.jar
- The case sensitivity of primary keywords and parameters depends on the underlying operating system. On Windows platforms, keywords are not case sensitive; mqsistart, mqsiSTART, and MQSISTART are all acceptable. On Linux and UNIX platforms, you must use lowercase; only mqsistart is acceptable.
All WebSphere Message Broker commands have dependencies on WebSphere MQ function. You must ensure that WebSphere MQ is available before issuing these commands.