Server abends (abnormal end of a piece of server code) are indicated on the Health Monitor page by a suspect or bad status for the indicator.
To trace sources of server abends:
Under the heading, click the link.
This displays the Profiling and Debug Information page, which shows information about active and suspended threads, their states, the owning NLM program, and execution times.
On the Profiling and Debug Information page, check to see which thread or program has a Suspended by Abend Recovery state and click the thread name link for that thread.
This displays the Thread Information page.
On the Thread Information page, view the field.
This information should tell you what the thread experienced and when. You will also be able to see a listing of Registers, Code Executed, and Stack information that the server was executing at the time the thread suspended.
If the thread was suspended by the Abend Recovery process, the state of the thread at the time of the abend is displayed, along with the reason for the abend and the code that was being executed at the time.
Click the Stack Address value link and perform some basic stack tracing (if you are familiar with interpreting assembly code).
You can use this information to look at the NLM information that is associated with the thread that had the problem. This can help you determine whether the NLM itself is having a problem or whether it is having a problem only when certain other NLM programs are running.
If possible, unload the NLM to see if the problem disappears.