| Author |
Message
|
| jeevan |
 Posted: Fri Feb 10, 2006 7:09 am Post subject: how to read .FDC files |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
can som eone explain exactly what FDC files are and howt o read them.
thanks |
|
| Back to top |
|
 |
| ramires |
| Posted: Fri Feb 10, 2006 8:16 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
it's a text file containing information about MQ when an error happens.
It has a lot of information inside. But sometimes looking to it can give a clue of the error.
But normaly thay are used by IBM support people.
This is part of an FDC I generated doing a telnet to port 1414:
***************************************
...
Date/Time :- Sexta-feira Fevereiro 10 16:12:53 CUT 2006
Host Name :- sgdaqlp11 (AIX 5.2)
PIDS :- 5724H7201
LVLS :- 6.0.0.0
Product Long Name :- WebSphere MQ for AIX
Vendor :- IBM
Probe Id :- CO052000
Application Name :- MQM
Component :- cciTcpReceive
...
...
Probe Type :- MSGAMQ9207
Probe Severity :- 2
Probe Description :- AMQ9207: The data received from host '10
(10.222.222.222)' is not valid.
...
***************************************
Regards |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Fri Feb 10, 2006 8:18 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
FDC stands (I think) for Failure Data Capture. The files are also called FFST (First Failure Support Technology or First Failure Symptom Trace). These files are needed by the IBM support teams, to find out more informations, to solve MQ problems. IBM has tools, to analyse these files, but they are not documented and hard to read for MQ admins.
Nevertheless there are some informations, you can get out of these files, when you read them carefully. For example you'll find the program name, which created the FDC, and sometimes an idea, why. But you need several experiences with reading these files - otherwise send them to you IBM support as part of a PMR (Problem Management Record).
_________________
Regards
Hubert |
|
| Back to top |
|
|
| dgolding |
| Posted: Fri Feb 10, 2006 8:26 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
| ffstsummary is a good (I believe undocumented) tool to get a "flavour" of what is happening on a box. Type /usr/mqm/bin/ffstsummary in the /var/mqm/errors directory. |
|
| Back to top |
|
|
| jeevan |
| Posted: Fri Feb 10, 2006 10:17 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
Thank you for the inside.
jeevan |
|
| Back to top |
|
|
| SAFraser |
| Posted: Thu Feb 16, 2006 9:48 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
Other things that are useful to me in FDC files are the userID and the time stamp. Sometimes I can correlate the time stamp to entries in queue manager logs and system logs
But the MOST IMPORTANT part of that header information is the probe ID. Use it to search this forum as well as searching the IBM site. I have gotten much information in this manner. |
|
| Back to top |
|
|
| nosnhoj |
| Posted: Fri Feb 17, 2006 11:35 am Post subject: |
|
|
Apprentice
Joined: 07 Sep 2005
Posts: 40
Location: Markham On.
|
|
| Back to top |
|
|
|
|
