IBM Support

IBM MQ and WebSphere MQ queue manager data and log directories

Technote (FAQ)


Question

Where do IBM MQ and WebSphere MQ store their queue manager data and log files on distributed platforms?

Answer

Every queue manager has one directory in which its configuration and message data (queues) are stored, and a second directory in which its recovery logs are stored. It is possible to specify both directories when creating a new queue manager, but each platform has its own default directories.



Linux and UNIX


The default directories for IBM MQ queue managers and their logs are the same on all Linux and UNIX systems. Each queue manager has an directory named for itself under the qmgrs subdirectory of the data directory, and another directory under the log directory. Both directories may be overridden when creating a new queue manager:

    Queue manager data and log directories


    /var/mqm
    /var/mqm/log


Windows


The queue manager data and log directories are chosen when the first MQ installation is performed on a machine, and they cannot be changed later. For example, if you install IBM MQ V8.0 on a system which has (or once had) earlier WebSphere MQ versions installed, it will continue to use the previous data and log directories. Each queue manager has an directory named for itself under the qmgrs subdirectory of the data directory, and another directory under the log directory. Both directories may be overridden when creating a new queue manager:

    IBM MQ V8.0 queue manager data and log directories


    C:\ProgramData\IBM\MQ
    C:\ProgramData\IBM\MQ\log

    WebSphere MQ V7.5 and earlier queue manager data and log directories


    C:\Program Files (x86)\IBM\WebSphere MQ
    C:\Program Files (x86)\IBM\WebSphere MQ\log



Use the reg.exe program to display the MQ queue manager data and log directories, which are stored in the Windows registry under the WorkPath and LogDefaultPath keys, respectively. The syntax of the reg command differs between 64-bit and 32-bit Windows, so use the command appropriate to your system:

    Determining the MQ data and log directories (64-bit Windows)


    C:\> REG QUERY "HKLM\Software\Wow6432Node\IBM\WebSphere MQ" | FINDSTR /C:WorkPath /C:LogDefaultPath
        WorkPath    REG_SZ    C:\Program Files\IBM\WebSphere MQ
    LogDefaultPath REG_SZ C:\Program Files\IBM\WebSphere MQ\log


    Determining the MQ data and log directories (32-bit Windows)


    C:\> REG QUERY "HKLM\Software\IBM\WebSphere MQ" | FINDSTR /C:WorkPath /C:LogDefaultPath
        WorkPath    REG_SZ    C:\Program Files (x86)\IBM\WebSphere MQ
    LogDefaultPath REG_SZ C:\Program Files (x86)\IBM\WebSphere MQ\log



By default Windows hides the C:\ProgramData directory, although you can change this attribute or use the Control Panel to ensure that the Windows Explorer shows hidden files. You can enter %PROGRAMDATA% in the Windows Explorer location bar and in the Windows Command Prompt to change directories:

    Accessing the IBM MQ V8.0 data directory


    C:\> CD %PROGRAMDATA%\IBM\MQ
    C:\ProgramData\IBM\MQ>


IBM i

The default data directory for IBM MQ queue managers is shown below, but there is no log directory since MQ uses IBM i journaling instead. Each queue manager has a directory named for itself under the qmgrs subdirectory of the data directory. The journal receivers are in the IBM i library for the queue manager, as identified by the /QIBM/UserData/mqm/mqs.ini file. You can view the journal receivers using the WRKLIB command, for example:

    Queue manager data directory


    /QIBM/UserData/mqm

    Example queue manager library


    QueueManager:
    Name=MY.QMGR
    Prefix=/QIBM/UserData/mqm
      Library=QMMY.QMGR
      Directory=MY.QMGR


    ===> WRKLIB LIB(QMMY.QMGR)

    Use option 5 to display the library and see the journal receivers

Document information

More support for: WebSphere MQ
Documentation

Software version: 6.0, 7.0, 7.1, 7.5, 8.0, 9.0

Operating system(s): AIX, HP-UX, IBM i, Linux, Solaris, Windows

Software edition: All Editions

Reference #: 1687392

Modified date: 22 June 2018


Translate this page: