In Figure 1, the layout is representative of IBM MQ after a queue manager has been in use for some time. The
actual structure that we have depends on which operations have occurred on the queue manager.Figure 1. Default directory structure (UNIX) after a
queue manager has been started
/var/mqm/
The /var/mqm directory contains configuration files and output directories
that apply to an IBM MQ installation as a whole, and not
to an individual queue manager.
/var/mqm/qmgrs/qmname/ contains directories and files for
a queue manager. The directory is locked for exclusive access by the active queue manager instance.
The directory path is directly modifiable in the mqs.ini file, or by using the
md option of the crtmqm command.
Other directories used by IBM MQ, such as @ipcc, to be modified only by IBM MQ.
userdata/
Can be used to store the persistent state of applications (can
be used by RDQM when moving queue managers to different nodes - see Storing persistent application
status.)
DataPath\autocfg
Used for automatic configuration
/var/mqm/log/qmname/
/var/mqm/log/qmname/ contains the queue manager log files. The directory is locked for exclusive access by
the active queue manager instance. The directory path is modifiable in the
qm.ini file, or by using the ld option of the
crtmqm command.
Directory or file name
Contents
amqhlctl.lfh
Log control file.
active/
This directory contains the log files numbered S0000000.LOG, S0000001.LOG,
S0000002.LOG, and so on.
/opt/mqm
/opt/mqm is, by default, the installation directory on most platforms. See
Disk space requirements on Multiplatforms for more information on the amount of space that we need for the
installation directory on the platform, or platforms, that your enterprise uses.