See information about the latest product version
Characters allowed in object names
You must adhere to rules when you provide names or identifiers for the components and resources in your broker environment.
- Uppercase alphabetic characters A-Z
- Lowercase alphabetic characters a-z
- Numeric characters 0-9
- All special characters supported by the underlying file system:
- Windows platforms:
$ % ' (apostrophe) " (quotation mark) - (dash) _ (underscore) @ ~ (tilde) ! ( ) (space) = [ ] & # + , (comma) - Linux and UNIX platforms:
. (dot) % - (dash) _ (underscore) @ ~ (tilde) ! = [ ] & # + , (comma)
In general, you can use characters A through Z, a through z, and 0 through 9.
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.
If you intend to use WebSphere® MQ File Transfer Edition for managed file transfers, see Preparing the environment for WebSphere MQ File Transfer Edition nodes for information about naming execution groups.
- Windows platforms:
The acceptable character set for configurable service names is identical to the character set for directory names on the file system of the target broker. The names of deployable resources (such as message flows, dictionaries, and JAR files) must consist only of characters that are acceptable in file names on the file systems of both the WebSphere Message Broker Toolkit and the target broker.
On Windows platforms, broker names are not case-sensitive. For example, broker names Broker1 and BROKER1 refer to the same broker.
On Linux and UNIX systems, broker names are case sensitive, and the previous examples refer to different brokers.
On z/OS® systems, you must enclose mixed-case names in quotation marks.
Additional rules are enforced for naming message service folders in the MQRFH2 header.