| Author |
Message
|
| basa_bbc |
 Posted: Fri Mar 26, 2004 3:26 am Post subject: FDC |
 |
|
Apprentice
Joined: 20 Jan 2004
Posts: 35
|
Hi Guys,
I am having lot of problems in production system. i am getting lot of FDC's generated. could any body help me how to analyse the FDC
Any document reference ??
Would really appreciate quick solution |
|
| Back to top |
|
 |
| JasonE |
| Posted: Fri Mar 26, 2004 4:15 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
In order
0. Apply the latest fixpack (5 is very stable and been out months, 6 is relatively new).
1. use ffstsummary (shipped with 5.3) to sort the fdc's by date, and start looking at the oldest one for each 'failure'
2. Search the IBM MySupport website for the 'ProbeIds' and look for apars or documents which help
3. Search here for the same
4. Post the fdc header and callstack and ask for help |
|
| Back to top |
|
|
| basa_bbc |
| Posted: Fri Mar 26, 2004 4:19 am Post subject: FDC |
|
|
Apprentice
Joined: 20 Jan 2004
Posts: 35
|
Hello JasonE,
Thanks for the info. It is really helpful.
could u please help me locating some docs which i can keep as baseline and investigate the FDC myself.
(We have MQ Errors.pdf for MQ error, similarly any doc for FDC on how to analyse it and come to conclusion) |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Mar 26, 2004 4:27 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
FDCs and FFSTs are not documented - they are internal "core dump" files intended for code-level debugging, not casual user troubleshooting.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JasonE |
| Posted: Fri Mar 26, 2004 4:36 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Generally the parts to look at:
1. ProbeID - Useful for searches, last 3 digits are the unique number within the specified function
2. Component - Identified the internal function name where the problem occurred
Both of these are only useful if you have the code to hand (if searches dont find a match!)
But its always worth looking at the comments field as it might give an 'english' reason, arith1 and arith2 may give return codes (eg. operating system ones). When it says something like "Missing log file S000001.log" then it sort of gives the problem away 
But as stated above, they are really designed for internal use |
|
| Back to top |
|
|
|
|
