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

Troubleshooting Java/JMS SSL Configurations - Middleware News

 This document is intended to help diagnose WebSphere MQ V7 Java™ or JMS SSL setup errors. It lists most of the common configuration errors that can cause an SSL connection from a Java/JMS client to a queue manager to fail, and gives the course of action to resolve the problem. In each case the error can be diagnosed by a combination of the error seen in the client log - either a console output, trace file or SystemOut.log file - and the queue manager's error logs. The document is quite long, so the easiest way to find the potential error is to search for one of the errors seen in this list, then filter this list using the error from the opposite end of the channel. All cases here assume that 2-way authentication is being attempted (SSLCAUTH set to REQUIRED on the queue manager's SVRCONN channel). This is the default, and the errors are very similar for 1-way authentication (SSLCAUTH set to OPTIONAL). Symptom Instructions on collecting documentation...

Using telnet to test connectivity between IBM Websphere MQ Client and MQ server - Middleware News

You are having trouble connecting a WebSphere MQ client to a MQ server, receiving errors that you can not connect to the MQ queue manager. One of the first things to determine is if the two machines can communicate, and using the telnet tool is one way to accomplish it. Symptom Receiving errors which state that a queue manager is not found or not available. Connection errors. For example: AMQ9213, AMQ9524, AMQ9202 or AMQ9508 or MQRC =2059 0x0000080b MQRC_Q_MGR_NOT_AVAILABLE. Please note, this is by no means an exclusive list of errors related to this type a problem but just a sample of some of the more common error messages and codes that might occur. Cause One possible cause is that the two machines can not communicate. May be the IP address or hostname was not properly specified by the MQ client. The port number might be incorrect. A queue manager is not running at the desired host. The queue manager could be running, but the corresponding listener is not runnin...

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