Skip to main content

IBM Websphere MQ Directory structure (Windows systems) - Middleware News

Directory structure (Windows systems)

Table 1 shows the directories found under the root c:\Program Files\IBM\WebSphere MQ\. If you have installed WebSphere® MQ for Windows under a different directory, the root is modified appropriately.

Table 1. WebSphere MQ for Windows directory structure\bin     Contains binary files (commands and DDLs).

\config     Contains configuration information.

\conv     Contains files for data conversion in folder \table.

\errors     Contains the system error log files:

    AMQERR01.LOG
    AMQERR02.LOG
    AMQERR03.LOG

These files contain information related errors that are not associated with a particular queue manager. AMQERR01.LOG contains the most recent error information.

This folder also holds any FFST™ files that are produced.

\exits     Contains channel exit programs.

\licenses     Contains a folder for each national language. Each folder contains license information.

\log     Contains a folder for each queue manager. The following subdirectories and files will exist for each queue manager after you have been using that queue manager for some time.

AMQHLCTL.LFH
    Log control file.
Active
    This directory contains the log files numbered S0000000.LOG, S0000001.LOG, S00000002.LOG, and so on.

\qmgrs     Contains a folder for each queue manager; the contents of these folders are described in Table 2. Also contains the folder \@SYSTEM\errors,

\tivoli     Contains the signature file used by Tivoli®.

\tools     Contains all the WebSphere MQ sample programs. These are described in WebSphere MQ for Windows Quick Beginnings.

\trace     Contains all trace files.

\uninst     Contains files necessary to uninstall WebSphere MQ.

Table 2 shows the directory structure for each queue manager in the
c:\Program Files\IBM\WebSphere MQ\qmgrs\ folder. The queue manager might have been transformed as described in Understanding WebSphere MQ file names.

Table 2. Content of a \queue-manager-name\ folder for WebSphere MQ for Windowsamqalchk.fil     Contains a checkpoint file containing information about the last checkpoint.

\authinfo     Contains a file for each authentication information object.

\channel     Contains a file for each channel object.


\clntconn     Contains a file for each client connection channel object.

\errors     Contains error log files associated with the queue manager:

    AMQERR01.LOG
    AMQERR02.LOG
    AMQERR03.LOG

AMQERR01.LOG contains the most recent error information.

\listener     Contains a file for each listener object.

\namelist     Contains a file for each WebSphere MQ namelist.

\Plugcomp     Directory reserved for use by WebSphere MQ installable services.

\Procdef     Contains a file for each WebSphere MQ process definition. Where possible, the file name matches the associated process definition name, but some characters have to be altered. There might be a directory called @MANGLED here containing process definitions with transformed or mangled names.

\Qmanager     Contains the following files:

Qmanager
    The queue manager object.
QMQMOBJCAT
    The object catalogue containing the list of all WebSphere MQ objects, used internally.
    Note: If you are using a FAT system, this name is transformed and a subdirectory created containing the file with its name transformed.
QAADMIN
    File used internally for controlling authorizations.


\Queues     Each queue has a directory here containing a single file called Q. Where possible, the directory name matches the associated queue name but some characters have to be altered. There might be a directory called @MANGLED here containing queues with transformed or mangled names.

\services     Contains a file for each service object.

\ssl     Contains SSL certificate stores.

\Startprm     Contains temporary files used internally.

Comments

adsrerrapop

Popular posts from this blog

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure

IBM Websphere MQ Reason code list / mq reason codes / websphere mq error codes / mq error messages

Reason code list ================= The following is a list of reason codes, in numeric order, providing detailed information to help you understand them, including: * An explanation of the circumstances that have caused the code to be raised * The associated completion code * Suggested programmer actions in response to the code * 0 (0000) (RC0): MQRC_NONE * 900 (0384) (RC900): MQRC_APPL_FIRST * 999 (03E7) (RC999): MQRC_APPL_LAST * 2001 (07D1) (RC2001): MQRC_ALIAS_BASE_Q_TYPE_ERROR * 2002 (07D2) (RC2002): MQRC_ALREADY_CONNECTED * 2003 (07D3) (RC2003): MQRC_BACKED_OUT * 2004 (07D4) (RC2004): MQRC_BUFFER_ERROR * 2005 (07D5) (RC2005): MQRC_BUFFER_LENGTH_ERROR * 2006 (07D6) (RC2006): MQRC_CHAR_ATTR_LENGTH_ERROR * 2007 (07D7) (RC2007): MQRC_CHAR_ATTRS_ERROR * 2008 (07D8) (RC2008): MQRC_CHAR_ATTRS_TOO_SHORT * 2009 (07D9) (RC2009): MQRC_CONNECTION_BROKEN * 2010 (07DA) (RC2010): MQRC_DATA_LENGTH_ERROR * 2011 (07DB) (RC2011): MQRC_DYNAMIC_Q_NAME_ERROR * 2012 (07DC) (RC201

IBM WebSphere MQ – Common install/uninstall issues for MQ Version on Windows - Middleware News

Creating a log file when you install or uninstall WebSphere MQ WebSphere MQ for Windows is installed using the Microsoft Installer (MSI). If you install the MQ server or client through launchpad , MQPARMS or setup.exe , then a log file is automatically generated in %temp% during installation. Alternatively you can supply parameters on the installation MSI command msiexec to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). If you uninstall through the Windows Add/Remove programs option, no log file is generated. You should either uninstall from the MSI command line and supply parameters to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). For details on how to enable MSI logging, see the following article in the WebSphere MQ product documentation: Advanced installation using msiexec For details on how to enable system-w