| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How to read the FDC logs |
« View previous topic :: View next topic » |
| Author |
Message
|
| sudhaRam |
 Posted: Fri Dec 21, 2007 5:34 am Post subject: How to read the FDC logs |
 |
|
Novice
Joined: 13 Nov 2007
Posts: 12
|
All,
We have MQ Series Ver 5.3 CSD 12 installed in our Windows Server. Since it is off support from IBM we are not gtting any support from IBM whenever an error occurs and we need to read the FDC files. The Management is still under consideration for the upgrade..Can anyone tell me is there any method to read those FDC files other than IBM. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Dec 21, 2007 5:43 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Large parts of the FDC only make sense if you have the source code for MQ in front of you.
You can use the ProbeId and major and minor error codes in the header block to search on IBM's website (or here) for other instances of the same FDC. If you spend some time thinking about it, you can maybe get a bit more information out of the stack trace - but only a bit.
Ask your management how many hours of downtime on a business critical system it will take to cost them more than the migration effort to move to a supported version?
Ask them, as a follow up, how many fewer hours than that will it take before they're all in a panic, and threatening to fire everyone?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JasonE |
| Posted: Wed Jan 02, 2008 2:15 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
For reference, the probe id is usually the perfect search argument except for ones relating to traps, as it uniquely identifies the function and position in the function is occurs.
If one exists, read the comment lines, as that will contain a descriptive help, but aimed at the person looking at the code. Similarly arith1 and arith2 (if shown) show numeric values which could be useful but without the code you wont know what they mean (but if comment says unexpected r/c from operating system call, chances are arith1/2 will contain what the r/c was!). Its also worth browsing the trace history and looking for any obvious bad return codes, as these can lead to fdc's later on!
Finally, if you ever post FDC info in here, post the probe, comment, arith1/2, and the MQ Call stack (first section below the header) |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jan 02, 2008 9:18 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
