Queue manager configuration files, qm.ini

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.

[V7.5.0.9 Sep 2018]From IBM® WebSphere® MQ Version 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:

/var/mqm/qmgrs/QMNAME/qm.ini
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:
C:\Program Files\IBM\WebSphere MQ\qmgrs\QMNAME\qm.ini

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 IBM WebSphere MQ for UNIX and Linux systems.

Figure 1. Example queue manager configuration file for IBM WebSphere MQ for UNIX and Linux systems

#* Module Name: qm.ini                                             *#
#* Type       : WebSphere MQ queue manager configuration file      *#
#  Function   : Define the configuration of a single queue manager *#
#*                                                                 *#
#*******************************************************************#
#* Notes      :                                                    *#
#* 1) This file defines the configuration of the queue manager     *#
#*                                                                 *#
#*******************************************************************#

ExitPath:
   ExitsDefaultPath=/var/mqm/exits
   ExitsDefaultPath64=/var/mqm/exits64

Service:
   Name=AuthorizationService
   EntryPoints=13

ServiceComponent:
   Service=AuthorizationService
   Name=MQSeries.UNIX.auth.service
   Module=opt/mqm/bin/amqzfu
   ComponentDataSize=0

Log:
   LogPrimaryFiles=3
   LogSecondaryFiles=2
   LogFilePages=4096
   LogType=CIRCULAR
   LogBufferPages=01
   LogPath=/var/mqm/log/saturn!queue!manager/

AccessMode:
   SecurityGroup=wmq\wmq

XAResourceManager:
   Name=DB2 Resource Manager Bank
   SwitchFile=/usr/bin/db2swit
   XAOpenString=MQBankDB
   XACloseString=
   ThreadOfControl=THREAD

Channels: 2
   MaxChannels=200
   MaxActiveChannels=100
   MQIBindType=STANDARD

AccessMode:
   SecurityGroup=wmq\wmq
TCP:
   KeepAlive = Yes
   SvrSndBuffSize=32768
   SvrRcvBuffSize=32768
   Connect_Timeout=0

QMErrorLog:
   ErrorLogSize=262144
   ExcludeMessage=7234
   SuppressMessage=9001,9002,9202
   SuppressInterval=30

ApiExitLocal:
   Name=ClientApplicationAPIchecker
   Sequence=3
   Function=EntryPoint
   Module=/usr/Dev/ClientAppChecker
   Data=9.20.176.20 
Notes for Figure 1:
  1. The value of zero for LogBufferPages gives a value of 512.
  2. For more information on the Channel stanza, see Initialization and configuration files.
  3. 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.

See Changing configuration information on UNIX, Linux, and Windows systems for information on when your changes take effect.