IBM Integration Bus, Version 10.0.0.0 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS


Rules for using commands

Observe the following rules when using the IBM® Integration Bus 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:
    mqsireadlog IBNODE -u -e default -o trace.xml -f
    can be entered as:
    mqsireadlog IBNODE -ufedefault -o trace.xml
    where the name of the integration server, 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.
  • Repeated flags are not allowed.
  • Strings that contain blanks or special characters must be enclosed in double quotation marks. For example:
    mqsireadlog "My Integration node" -u -e default -o trace.xml -f
    Additionally, you can specify a null, or empty, string with a pair of quotation marks with nothing between: "".
  • z/OS platformIf you are running a command by submitting one of the JCL utilities (see Contents of the integration node 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 integration server default, then modify the JCL to contain the following sample:
    mqsideploy IIB9BROKER -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 IBM Integration Bus commands have dependencies on WebSphere® MQ function. You must ensure that WebSphere MQ is available before issuing these commands.


an19500_.htm | Last updated 2015-03-27 19:27:04