Skip to main content

WebSphere MQ Dumps and FFSTs are written to the following locations - Middleware News

WebSphere MQ Dumps and FFSTs are written to the following locations - Middleware News


Directions for finding WebSphere MQ Dump and FFST records.

Resolving the problem

Dumps and FFST records contain important information that can be used in problem solving. If you have a WebSphere MQ problem, you may receive Dumps and FFSTs, that record details related to the failure.
Select one of the following platforms to find the location of the MQ Dumps and FFSTs:

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


HP NSS

FFSTs are located in the following directory:

/var/mqm/errors

These errors are normally severe, unrecoverable errors, and indicate either a configuration problem with the system or a WebSphere MQ internal error.


The files are named AMQccppppp.nn.FDC, where cc is the number of the CPU in which the process that reported the error was running, ppppp is the process identification number (PIN) of the process that reported the error, and nn is a sequence number, normally 0.



i5/OS

FFSTs are located in the following directory:

/QIBM/UserData/mqm/errors

The files are named AMQnnnnnnnn_mm.FDC, where: nnnnnnnn is the process id reporting the error, and mm is a sequence number, normally 0.


OpenVMS

FFSTs are located in the following directory:

MQS_ROOT:[MQM.ERRORS]AMQ.FDC
Where PID is the process id of the MQ process which generated the FFST.

These errors are normally severe, unrecoverable errors and indicate either a configuration problem with the system or a WebSphere MQ internal error.



UNIX and Linux

FFSTs are located in the following directory:

/var/mqm/errors

The files are named AMQnnnnnnnn_mm.FDC, where: nnnnnnnn Is the process id reporting the error mm Is a sequence number, normally 0


VSE

Dumps are normally stored by z/VSE in the VSE dump library.



Windows

FFSTs are located in the following directory:

c:\Program Files\IBM\WebSphere MQ\errors

The files are named AMQnnnnnnnn_mm.FDC, where: nnnnnnnn Is the process id reporting the error mm Is a sequence number, normally 0

Note: This is the default directory path, however it may have been changed at install time.



z/OS

Dumps are located in the system dump data set.

Example of a dump title:

CSQ1,ABN=5C6-00E20016,U=SYSOPR ,C=R3600.701.MMC -CSQMTRG2,M=CSQGFRCV, LOC=CSQSLD1 .CSQSVSTK+0000057AF
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

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

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