You must adhere to rules when you provide names or identifiers for the components and resources in your integration node environment.
$ | % | ' (apostrophe) | " (quotation mark) |
- (dash) | _ (underscore) | @ | ~ (tilde) |
! | ( | ) | (space) |
= | [ | ] | & |
# | + | , (comma) | . (dot) |
. (dot) | % | - (dash) | _ (underscore) |
@ | ~ (tilde) | ! | = |
[ | ] | & | # |
+ | , (comma) | (space) |
If you expect to trace the operation of an integration server, restrict the name of the integration server to include only the valid alphabetic and numeric characters listed. The trace commands do not support the use of special characters for an integration server 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 integration servers.
On Windows platforms, integration node names are not case-sensitive. For example, integration node names inode1 and INODE1 refer to the same integration node.
On Linux and UNIX systems, integration node names are case sensitive. For example, integration node names inode1 and INODE1 refer to different integration nodes.
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.