Figure 1 shows an example of an mqs.ini file for IBM® i.Figure 1. Example of an IBM MQ configuration file
#***********************************************************************#
#* Module Name: mqs.ini *#
#* Type : IBM MQ Configuration File *#
#* Function : Define IBM MQ resources for the node *#
#* *#
#***********************************************************************#
#* Notes : *#
#* 1) This is an example IBM MQ configuration file *#
#* *#
#***********************************************************************#
AllQueueManagers:
#***********************************************************************#
#* The path to the qmgrs directory, within which queue manager data *#
#* is stored *#
#***********************************************************************#
DefaultPrefix=/QIBM/UserData/mqm
QueueManager:
Name=saturn.queue.manager
Prefix=/QIBM/UserData/mqm
Library=QMSATURN.Q
Directory=saturn!queue!manager
QueueManager:
Name=pluto.queue.manager
Prefix=/QIBM/UserData/mqm
Library=QMPLUTO.QU
Directory=pluto!queue!manager
DefaultQueueManager:
Name=saturn.queue.manager
Figure 2 shows how groups of attributes might be arranged in a queue
manager configuration file for IBM i.Figure 2. Example queue manager configuration file
From IBM MQ Version 9.0.5, this is an example
queue manager configuration
file:
#*******************************************************************#
#* Module Name: qm.ini *#
#* Type : IBM 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 *#
#* *#
#*******************************************************************#
Log:
LogPath=QMSATURN.Q
LogReceiverSize=65536
CHANNELS:
MaxChannels = 20 ; Maximum number of channels allowed.
; Default is 100.
MaxActiveChannels = 10 ; Maximum number of channels allowed to be
; active at any time. The default is the
; value of MaxChannels.
TCP: ; TCP/IP entries.
KeepAlive = Yes ; Switch KeepAlive on.
SvrSndBuffSize=20000 ; Size in bytes of the TCP/IP send buffer for each
; channel instance. Default is 32768.
SvrRcvBuffSize=20000 ; Size in bytes of the TCP/IP receive buffer for each
; channel instance. Default is 32768.
Connect_Timeout=10000 ; Number of seconds before an attempt to connect the
; channel instance times out. Default is zero (no timeout).
QMErrorLog:
ErrorLogSize = 262144
ExcludeMessage = 7234
SuppressMessage = 9001,9002,9202
SuppressInterval = 30
TuningParameters:
ImplSyncOpenOutput=2
For IBM MQ Version 9.0.4 and earlier,
and LTS, this is an example configuration
file:
#*******************************************************************#
#* Module Name: qm.ini *#
#* Type : IBM 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 *#
#* *#
#*******************************************************************#
Log:
LogPath=QMSATURN.Q
LogReceiverSize=65536
CHANNELS:
MaxChannels = 20 ; Maximum number of channels allowed.
; Default is 100.
MaxActiveChannels = 10 ; Maximum number of channels allowed to be
; active at any time. The default is the
; value of MaxChannels.
TCP: ; TCP/IP entries.
KeepAlive = Yes ; Switch KeepAlive on.
SvrSndBuffSize=20000 ; Size in bytes of the TCP/IP send buffer for each
; channel instance. Default is 32768.
SvrRcvBuffSize=20000 ; Size in bytes of the TCP/IP receive buffer for each
; channel instance. Default is 32768.
Connect_Timeout=10000 ; Number of seconds before an attempt to connect the
; channel instance times out. Default is zero (no timeout).
QMErrorLog:
ErrorLogSize = 262144
ExcludeMessage = 7234
SuppressMessage = 9001,9002,9202
SuppressInterval = 30
Note:
IBM MQ on the node uses the default locations for
queue managers and the journals.
The queue manager saturn.queue.manager is the default queue manager for the node. The directory
for files associated with this queue manager has been automatically transformed into a valid file
name for the file system.
Because the IBM MQ configuration file is used to
locate the data associated with queue managers, a nonexistent or incorrect configuration file can
cause some or all IBM MQ commands to fail. Also,
applications cannot connect to a queue manager that is not defined in the IBM MQ configuration file.