I think it is yet not available. I would also be interested to know if there are any available.
But the FDC file prints the header info, which is very useful info for admins to learn exactly what caused the issue.
look at Probe section of the FFST report and it helps.
Sometimes it is difficult to know, but MQ and QMgr error logs also help.
+-----------------------------------------------------------------------------+
| |
| IBM MQ First Failure Symptom Report |
| ========================================= |
| |
|
| Vendor :- IBM |
| O/S Registered :- 1 (libmqmcs_r.so) Installed |
| Data Path :- /var/mqm |
| Installation Path :- /opt/mqm |
| Installation Name :- Installation1 (5) |
| License Type :- Production |
| Probe Id :- CO373099 |
|
| Program Name :- amqrmppa |
| Arguments :- -m ABCDT01 |
| Standard Streams :- 0 1 2 |
| Addressing mode :- 64-bit |
| LANG :- en_US.UTF-8 |
| Process :- 7708 |
| Process(Thread) :- 18875 |
| Thread :- 77766 RemoteResponder |
|
| Major Errorcode :- rrcE_PROTOCOL_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ9504 |
| Probe Severity :- 2 |
| Probe Description :- AMQ9504E: A protocol error was detected for channel |
| '????'. |
| FDCSequenceNumber :- 0 |
| Comment1 :- ???? |
| Comment2 :- Detected multiple key resets |
| |
+-----------------------------------------------------------------------------+
------------------------------
om prakash
------------------------------
Original Message:
Sent: Tue October 18, 2022 10:38 AM
From: Emile Kearns
Subject: Analyzing of FDC files
Hi all,
I am back into the MQ space and wanted to know if IBM developed a tool to analyze FDC files already?
If not, what would be the eye catching things one should look for in a FDC file?
------------------------------
Emile Kearns
------------------------------