Each WebSphere MQ queue, queue manager, namelist, and process object is represented by a file. Because object names are not necessarily valid file names, the queue manager converts the object name into a valid file name where necessary.
The default path to a queue manager directory is as follows:
queue.manager
would be represented as:
queue!manager
This process is referred to as name transformation.
In WebSphere MQ, you can give a queue manager a name containing up to 48 characters.
For example, you could name a queue manager:
QUEUE.MANAGER.ACCOUNTING.SERVICES
However, each queue manager is represented by a file and there are limitations on the maximum length of a file name, and on the characters that can be used in the name. As a result, the names of files representing objects are automatically transformed to meet the requirements of the file system.
The rules governing the transformation of a queue manager name are as follows:
For example, assuming the default prefix and a queue manager with the name queue.manager:
c:\Program Files\IBM\WebSphere MQ\qmgrs\queue!manager
c:\Program Files\IBM\WebSphere MQ\qmgrs\queue!ma
/var/mqm/qmgrs/queue!manager
The transformation algorithm also distinguishes between names that differ only in case on file systems that are not case sensitive.
Object names are not necessarily valid file system names. You might need to transform your object names. The method used is different from that for queue manager names because, although there are only a few queue manager names on each machine, there can be a large number of other objects for each queue manager. Process definitions, queues, and namelists are represented in the file system; channels are not affected by these considerations.
When a new name is generated by the transformation process, there is no simple relationship with the original object name. You can use the dspmqfls command to convert between real and transformed object names.