A queue manager configuration file, qm.ini, contains information
relevant to a specific queue manager.
There is one queue manager configuration file for each queue manager.
The qm.ini file is automatically created when the queue manager with
which it is associated is created.
From IBM®WebSphere® MQVersion 7.5.0, Fix Pack 9, the
strmqm command checks the syntax of the CHANNELS and SSL stanzas in the
qm.ini file before starting the queue manager fully, which makes it much easier
to see what is wrong, and correct it quickly if strmqm finds that the
qm.ini file contains any errors. For more information, see strmqm.
On UNIX and Linux® systems
a qm.ini file is held in the root of the directory tree occupied by
the queue manager. For example, the path and the name for a configuration
file for a queue manager called QMNAME is:
On Windows systems
the location of the qm.ini file is given by the WorkPath specified
in the HKLM\SOFTWARE\IBM\WebSphere MQ key. For example,
the path and the name for a configuration file for a queue manager
called QMNAME is:
The queue manager name can be up to 48 characters in length. However,
this does not guarantee that the name is valid or unique. Therefore,
a directory name is generated based on the queue manager name. This
process is known as name transformation. For a description,
see Understanding WebSphere MQ file names.
Figure 1 shows how groups of attributes
might be arranged in a queue manager configuration file in IBMWebSphere MQ for UNIX and Linux systems.
The maximum number of XAResourceManager stanzas is limited to
255. However, you should use only a small number of stanzas to avoid
transaction performance degradation.
Note: WebSphere MQ in Unix uses configuration files that have a file
extension of .ini, for example, qm.ini. There are some utilities
in WebSphereMQ, such as setmqm, that will make
a temporary backup copy of the files. For example, the file qm.ini
will create a backup copy named qm.ini.bak. A utility will modify
the qm.ini file, store the updated file, then delete the qm.ini.bak
file. If the utility cannot store the qm.ini file, then it restores
the contents of qm.ini from the backup file qm.ini.bak, and then deletes
the qm.ini.bak file.
If there is an existing qm.ini.bak file,
the utility reverts the qm.ini file with the contents of the qm.ini.bak
and deletes the qm.ini.bak file. Therefore, you should not create
backup copies of the *.ini files by using a file extension of .bak,
because these backup files might be deleted by WebSphere MQ utilities.