Skip to main content

IBM WebSphere MQ error logs - Middleware News

IBM WebSphere MQ error logs - Middleware News



Problem


Directions to find WebSphere MQ and MQSeries error logs.


Note: The MQ error logs are by default located in the following directories, however it may have been changed at install time:
Resolving the problem


The messages that are recorded in the error logs and job logs are the most important information that you can provide when reporting an MQ problem.

Select one of the following platforms to find the location of the MQ error logs:

HP NSS
i5/OS
OpenVMS
UNIX and Linux
VSE
Windows
z/OS


HP NSS
=======

The WebSphere MQ for HP NSS error logs are located in the following directories:


/var/mqm/errors
/var/mqm/qmgrs//errors

The error log files are named; AMQERR01.LOG, AMQERR02.LOG and AMQERR03.LOG.

Notes:

* If the queue manager name is not known then the error message is written to an error log file in the errors subdirectory. For example, if the default prefix is /usr/ibm/wmq/GA/var/mqm, the error message is written to an error log file in the directory /usr/ibm/wmq/GA/var/mqm/errors
* If the queue manager name is known, then the error message is written to an error log file in the queue manager’s errors directory.



i5/OS
=======

The WebSphere MQ for i5/OS error logs are located in the following directories:


/QIBM/UserData/mqm/qmgrs//errors
/QIBM/UserData/mqm/qmgrs/&SYSTEM

The error log files are named; AMQERR01.LOG, AMQERR02.LOG and AMQERR03.LOG.





OpenVMS
======

The WebSphere MQ HP OpenVMS error logs are located in the following directories:


MQS_ROOT:[MQM.ERRORS]AMQERR01.LOG
MQS_ROOT:[MQM.QMGRS.QMgrName.ERRORS]AMQERR01.LOG
MQS_ROOT:[MQM.QMGRS.$SYSTEM.ERRORS]AMQERR01.LOG

The error log files are named; AMQERR01.LOG, AMQERR02.LOG and AMQERR03.LOG.

Notes:

* If an error has occurred with a client application: MQS_ROOT:[MQM.ERRORS]AMQERR01.LOG
* If the queue manager name is known and the queue manager is available: MQS_ROOT:[MQM.QMGRS.QMgrName.ERRORS]AMQERR01.LOG
* If the queue manager is not available: MQS_ROOT:[MQM.QMGRS.$SYSTEM.ERRORS]AMQERR01.LOG


UNIX and Linux
===========

The WebSphere MQ for UNIX error logs are located in the following directories:


/var/mqm/errors
/var/mqm/qmgrs//errors
/var/mqm/qmgrs/@SYSTEM/errors (not used at V6 and higher)

The error log files are named; AMQERR01.LOG, AMQERR02.LOG and AMQERR03.LOG.


VSE
===

MQSeries uses the SYSTEM.LOG queue defined in the global system definition as its primary message log and additional informational messages are output to the VSE console. Typically, these detail starting, stopping, and initializing MQSeries for VSE If the SYSTEM.LOG queue is unavailable, the messages are directed to the CICS CSMT log.

These messages should always be reviewed carefully for any error messages. The type of messages included in the SYSTEM.LOG queue can now be controlled by using the ’Log and Trace Settings’.

Refer to the MQSeries for VSE System Management Guide, “Queue Manager Log and Trace Settings” on page 74 for details. Note that the types of messages put to the SYSTEM.LOG queue can be controlled
using the LOG SETTINGS. When trying to resolve problems, ensure that all messages of all severity are
selected to be logged. You can view the contents of the system log using the Master Terminal transaction (MQMT) option 4 (Browse Queue Records).

Windows
=====

The WebSphere MQ for Windows error logs are located in the following directories. This is the default directory path, however it may have been changed at install time:

c:\Program Files\IBM\WebSphere MQ\errors
c:\Program Files\IBM\WebSphere MQ\qmgrs\\errors
c:\Program Files\IBM\WebSphere MQ\qmgrs\@SYSTEM\errors (not used at V6 and higher)

The error log files are named; AMQERR01.LOG, AMQERR02.LOG and AMQERR03.LOG.


z/OS
===

The WebSphere MQ for OS/390 and z/OS job logs are located in the following:

Syslog
MSTR job log
CHIN job log

The job logs are named; xxxxMSTR, and xxxxCHIN. Where xxxx is the WMQ subsystem identifier (ssid).
Labels:

Comments

Post a Comment

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...
Post a Comment
Read more

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 ...
143 comments
Read more

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...
Post a Comment
Read more