Skip to main content
Directory structure (UNIX systems)

Figure 1 shows the general layout of the data and log directories associated with a specific queue manager. The directories shown apply to the default installation. If you change this, the locations of the files and directories are modified accordingly. For information about the location of the product files, see one of the following:

    WebSphere MQ for AIX® Quick Beginnings
    WebSphere MQ for HP-UX Quick Beginnings
    WebSphere MQ for Solaris Quick Beginnings
    WebSphere MQ for Linux Quick Beginnings

In Figure 1, the layout is representative of WebSphere® MQ after a queue manager has been in use for some time. The actual structure that you have depends on which operations have occurred on the queue manager.
Figure 1. Default directory structure (UNIX systems) after a queue manager has been started
Default directory structure after a queue manager has been started (UNIX systems).

By default, the following directories and files are located in the directory /var/mqm/qmgrs/qmname/ (where qmname is the name of the queue
manager).

Table 1. Default content of a /var/mqm/qmgrs/qmname/ directory on UNIX systemsamqalchk.fil     Checkpoint file containing information about the last checkpoint.

auth/     Contained subdirectories and files associated with authority in WebSphere MQ prior to Version 6.0.

authinfo/     Each WebSphere MQ authentication information definition is associated with a file in this directory. The file name matches the authentication information definition name—subject to certain restrictions; see Understanding WebSphere MQ file names.

channel/     Each WebSphere MQ channel definition is associated with a file in this directory. The file name matches the channel definition name—subject to certain restrictions; see Understanding WebSphere MQ file names.

clntconn/     Each WebSphere MQ client connection channel definition is associated with a file in this directory. The file name matches the client connection channel definition name—subject to certain restrictions; see Understanding WebSphere MQ file names.

dce/     Used for DCE support prior to WebSphere MQ Version 6.0.

errors/     Directory containing FFSTs, client application errors, and operator message files from newest to oldest:

    AMQERR01.LOG
    AMQERR02.LOG
    AMQERR03.LOG

esem/     Directory containing files used internally.

isem/     Directory containing files used internally.

listener/     Each WebSphere MQ listener definition is associated with a file in this directory. The file name matches the listener definition name—subject to certain restrictions; see Understanding WebSphere MQ file names.

msem/     Directory containing files used internally.

namelist/     Each WebSphere MQ namelist definition is associated with a file in this directory. The file name matches the namelist definition name—subject to certain restrictions; see Understanding WebSphere MQ file names.

plugcomp/     Empty directory reserved for use by installable services.

procdef/     Each WebSphere MQ process definition is associated with a file in this directory. The file name matches the process definition name—subject to certain restrictions; see Understanding WebSphere MQ file names.

qmanager/   

QMANAGER
    The queue manager object.
QMQMOBJCAT
    The object catalog containing the list of all WebSphere MQ objects; used internally.

qm.ini     Queue manager configuration file.

queues/     Each queue has a directory in here containing a single file called q.

The file name matches the queue name, subject to certain restrictions; see Understanding WebSphere MQ file names.

services/     Each WebSphere MQ service definition is associated with a file in this directory. The file name matches the service definition name—subject to certain restrictions; see Understanding WebSphere MQ file names.

shmem/     Directory containing files used internally.

spipe/     Used internally by channel processes.

ssem/     Directory containing files used internally.

ssl/     Directory for SSL key database files.

startprm/     Directory containing temporary files used internally.

zsocketapp/     Used internally for isolated bindings.

zsocketEC/     Used internally for isolated bindings.
@ipcc/   

AMQCLCHL.TAB
    Client channel table file.

esem/
    Directory containing files used internally.
isem/
    Directory containing files used internally.
msem/
    Directory containing files used internally.
shmem/
    Directory containing files used internally.
ssem/
    Directory containing files used internally.

@qmpersist   

esem/
    Directory containing files used internally.
isem/
    Directory containing files used internally.
msem/
    Directory containing files used internally.
shmem/
    Directory containing files used internally.
ssem/
    Directory containing files used internally.

@qmpersist   

esem/
    Directory containing files used internally.
isem/
    Directory containing files used internally.
msem/
    Directory containing files used internally.
shmem/
    Directory containing files used internally.
ssem/
    Directory containing files used internally.

@app   

esem/
    Directory containing files used internally.
isem/
    Directory containing files used internally.
msem/
    Directory containing files used internally.
shmem/
    Directory containing files used internally.
ssem/
    Directory containing files used internally.

By default, the following directories and files are found in /var/mqm/log/qmname/ (where qmname is the name of the queue manager).
The following subdirectories and files exist after you have installed WebSphere MQ, created and started a queue manager, and 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, S0000002.LOG, and so on.

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...

Adding SSL certificates to a mixed z/OS and Unix queue manager environment - Middleware News

Adding SSL certificates to a mixed z/OS and Unix queue manager environment - Middleware News 1. Security Considerations IBM advises customers who are using SSL, that the most secure way to do this is to use recognized Certification Authorities to sign their certificates. Ensuring secure transfer of information is the main purpose of SSL. This integrity must be properly observed when setting up SSL. You should always be certain who has signed each of your SSL certificates, who has had and who continues to have access to them. The first secure way to generate certificates is to generate a certificate request, on each system or machine that uses SSL. This request has to be signed by an external Certification Authority before it can be used. Getting certificate requests signed by a CA is secure, because during the signing process at no point do any files contain the certificate's Private Keys. This principle is vital to SSL security. Signing certificates in this way is covered...