Characters allowed in commands

There are a few rules you must adhere to when you provide names or identifiers for the components and resources in your broker domain.

The components of the broker domain are:
  • Brokers
  • The Configuration Manager
  • The User Name Server (this component is optional)
The broker resources are:
  • Execution groups
  • Message sets and messages
  • Message flows
  • Topics
The character set that you can use to name brokers, Configuration Managers, execution groups, and message identifiers is as follows:
  • Uppercase A-Z
  • Lowercase a-z
  • Numerics 0-9
  • Any special characters supported by the underlying file system:
    • The following special characters are accepted on Windows platforms:
      $ % ' (apostrophe) ' (quote)
      - (dash) _ (underscore) @ ~ (tilde)
      ! ( ) {
      } [ ] &
      # & + , (comma)
      ; = (space)  
    • The following special characters, with the exception of a space, are accepted on UNIX platforms:
      . (dot) % - (dash) _ (underscore)
      @ ~ (tilde) ! {
      } [ ] &
      # , (comma) = (space)

    In general, you can use characters A through Z, a through z, and 0 through 9, plus any Unicode character with a decimal value greater than 127 (hexadecimal X'7F'), provided that your operating system can recognize the characters chosen.

    If you expect to trace the operation of an execution group, restrict the name of the execution group to include only the valid alphabetic and numeric characters listed. The trace commands do not support the use of special characters for an execution group name.

For all other resources, any characters that are supported by the database configuration are supported.

Broker names, Configuration Manager names, and fixed names (UserNameServer) are not case sensitive on the Windows platforms. For example, broker names Broker1 and BROKER1 refer to the same broker.

On Linux and UNIX systems, broker names and Configuration Manager names are case sensitive, and the examples above would refer to different brokers. You must use UserNameServer as shown.

There are additional rules for naming message service folders within the MQRFH2 header.

Related reference
Message service folders