The handling of channel initialization data depends on your WebSphere MQ platform.
In WebSphere MQ for z/OS without CICS, initialization and configuration information is in the channel initiator parameter module CSQXPARM. You can also put commands in the CSQINPX initialization input data set, which is processed every time you start the channel initiator if you specify the optional DD statement CSQINPX in the channel initiator started task procedure. See WebSphere MQ for z/OS Concepts and Planning Guide for information about both of these.
In WebSphere MQ for z/OS using CICS there is no channel initiator.
On WebSphere(R) MQ for Windows systems, the registry file holds basic configuration information about the WebSphere MQ installation. That is, information relevant to all of the queue managers on the WebSphere MQ system and also information relating to individual queue managers.
On MQSeries for OS/2 Warp, MQSeries for Compaq OpenVMS Alpha, Compaq NonStop Kernel, and WebSphere MQ for iSeries and WebSphere MQ on UNIX systems, there are configuration files to hold basic configuration information about the WebSphere MQ installation.
There are two configuration files: one applies to the machine, the other applies to an individual queue manager.
This holds information relevant to all of the queue managers on the WebSphere MQ system. The file is called MQSINI on Compaq NonStop Kernel and mqs.ini on other platforms. It is fully described in the WebSphere MQ System Administration Guide book for WebSphere MQ for AIX, HP-UX, and Solaris, and MQSeries for OS/2 Warp, and in the WebSphere MQ for iSeries V5.3 System Administration book for iSeries.
The queue manager configuration file holds configuration information relating to one particular queue manager. The file is called QMINI on Compaq NonStop Kernel, and qm.ini on other platforms.
It is created during queue manager creation and may hold configuration information relevant to any aspect of the queue manager. Information held in the file includes details of how the configuration of the log differs from the default in WebSphere MQ configuration file.
The queue manager configuration file is held in the root of the directory tree occupied by the queue manager. On WebSphere MQ for Windows, the information is held in the registry. For example, for the DefaultPath attributes, the queue manager configuration files for a queue manager called QMNAME would be:
For OS/2:
c:\mqm\qmgrs\QMNAME\qm.ini
For UNIX systems:
/var/mqm/qmgrs/QMNAME/qm.ini
For Compaq OpenVMS Alpha:
mqs_root:[mqm.qmgrs.QMNAME]qm.ini
For Compaq NonStop Kernel:
The file is held in the subvolume of the queue manager. For example, the path and name for a configuration file for a queue manager called QMNAME could be $VOLUME.QMNAMED.QMINI.
An excerpt of a qm.ini file follows. It specifies that the TCP/IP listener is to listen on port 2500, the maximum number of current channels is to be 200 and the maximum number of active channels is to be 100.
TCP:
Port=2500
CHANNELS:
MaxChannels=200
MaxActiveChannels=100
In MQSeries V5.2 and WebSphere MQ, you can to specify a range
of TCP/IP ports to be used by an outbound channel. One method is to use
the qm.ini file to specify the start and end of a range of port
values. The example below shows a qm.ini file specifying a range
of channels:
If you specify a value for StrPort or EndPort then you must specify a
value for both. The value of EndPort must always be greater than the
value of StrPort. TCP:
StrPort=2500
EndPort=3000
CHANNELS:
MaxChannels=200
MaxActiveChannels=100
The channel tries to use each of the port values in the range specified. When the connection is successful, the port value is the port that the channel then uses.
For iSeries:
/QIBM/UserData/mqm/qmgrs/QMNAME/qm.ini
For more information about qm.ini files see Appendix C, Configuration file stanzas for distributed queuing.
There is no qm.ini file on VSE/ESA. Instead, use the Configuration main menu on the MQMMCFG panel to configure the queue manager.