Novell Netware ABEND.LOG files capture abnormal endings (aka abends), which are the equivalent of the Windows Blue Screen of Death. ABEND.LOGs typically contain a few lines of useful information for us consultant types, while the majority of the data is memory and stack contents, which probably only makes sense to developer types.
The ABENDLogFilter utility will parse the ABEND.LOG file, searching out and displaying the information that can be most readily used to troubleshoot abends. Since the ABEND.LOG file is appended from top down, normally you have to start at the bottom of the log file and search up to find the most recent abend data.
This utility reverses the order of the ABEND.LOG and displays the most recent abend first, along with a brief summary. Here’s my most recent entry on one of my servers:
ABEND.LOG for: GROUPWISE1
TOTAL ABENDS: 9
DATE RANGE: Wednesday, June 6, 2007 11:29:50.531 am
Sunday, July 22, 2007 5:09:42.958 am
TIP: Enter CTRL+F, and find string “::ABEND” to skip to each subsequent ABEND occurrence
Date of ABEND: Sunday, July 22, 2007 5:09:42.958 am
ABEND Reason: Abend 2 on P00: Server-5.70.06: Page Fault Processor Exception (Error code 00000000)
Running process: Server 00:21 Process
Interrupted process: N/A
Thread Owned by NLM: SERVER.NLM
Stack: -90C4A440 (NCPIP.NLM|limboWork+0)
Additional Information: The CPU encountered a problem executing code in NCPIP.NLM
The problem may be in that module or in data passed to that module by a process owned by SERVER.NLM.
The original ABEND.LOG contents are displayed at the bottom of the summary file, most recent listed first.
I found this utility to make finding pertinent information in the ABEND.LOG file much easier. Check it out if you haven’t done so, it’s a free Cool Tool.