Directory content
Lists the location and content of IBM MQ directories.
An IBM MQ configuration has three main sets of files and directories:
- Executable, and other read-only files that are only updated when maintenance is applied. For example:
These files are described in Table 1.
- The readme file
- The IBM MQ Explorer plug-in and help files
- License files
- Potentially modifiable files and directories that are not specific to a particular queue manager. These files and directories are described in Table 2.
- Files and directories that are specific to each queue manager on a server. These files and directories are described in Table 3.
Resource directories and files
The resource directories and files contain all the executable code and resources to run a queue manager. The variable, FilePath, in the installation specific IBM MQ configuration registry key, contains the path to the resource directories.
Table 1. Directories and files in the FilePath directory File path Contents FilePath\bin Commands and DLLs FilePath\bin64 Commands and DLLs (64 bit) FilePath\conv Data conversion tables FilePath\doc Wizard help files FilePath\MQExplorer Explorer and Explorer help Eclipse plug-ins FilePath\gskit8 Global security kit FilePath\java Java resources, including JRE FilePath\licenses License information FilePath\Non_IBM_License License information FilePath\properties Used internally FilePath\Tivoli FilePath\tools Development resources and samples FilePath\web Described in IBM MQ Console and REST API installation component file structure for non-editable files. FilePath\Uninst Used internally FilePath\README.TXT Readme file
Directories not specific to a queue manager
Some directories contain files, such as trace files and error logs, that are not specific to a specific queue manager. The DefaultPrefix variable contains the path to these directories. DefaultPrefix is part of the AllQueueManagers stanza.
Table 2. Directories and files in DefaultPrefix directory File path Contents DefaultPrefix\config Used internally DefaultPrefix\conv ccsid_part2.tbl and ccsid.tbl data conversion control file, described in Data conversion DefaultPrefix\errors Non queue manager error logs, AMQERR nn.LOG DefaultPrefix\exits Channel exit programs DefaultPrefix\exits64 Channel exit programs (64 bit) DefaultPrefix\ipc Not used DefaultPrefix\qmgrs Described in Table 3 DefaultPrefix\trace Trace files DefaultPrefix\web Described in IBM MQ Console and REST API installation component file structure for user editable files DefaultPrefix\amqmjpse.txt Used internally
Queue manager directories
When you create a queue manager, a new set of directories, specific to the queue manager, is created.
If you create a queue manager with the -md filepath parameter, the path is stored in the DataPath variable in the queue manager stanza of the mqs.ini file. If you create a queue manager without setting the -md filepath parameter, the queue manager directories are created in the path stored in DefaultPrefix, and the path is copied into the Prefix variable in the queue manager stanza of the mqs.ini file.
Table 3. Directories and files in DataPath and Prefix\qmgrs\QmgrName directories File path Contents DataPath\@ipcc Default location for AMQCLCHL.TAB, the client connection table. DataPath\authinfo Used internally. DataPath\channel DataPath\clntconn DataPath\errors Error logs, AMQERR nn.LOG DataPath\listener Used internally. DataPath\namelist DataPath\plugcomp DataPath\procdef DataPath\qmanager DataPath\queues DataPath\services DataPath\ssl DataPath\startprm DataPath\topic DataPath\active DataPath\active.dat DataPath\amqalchk.fil DataPath\master DataPath\master.dat DataPath\qm.ini Queue manager configuration DataPath\qmstatus.ini Queue manager status Prefix\qmgrs\QmgrName Used internally Prefix\qmgrs\@SYSTEM Not used Prefix\qmgrs\@SYSTEM\errors