Now you'll identify the abended module. This command will show you the running process at the time of the abend and the current stack pointer and stack limit. Include this module name and the stack values on your abend information sheet. You've passed the halfway point now. The next step is to gather the current stack.
Type dds at the debugger command prompt to display the stack contents.
This will also show the module names, function names and offsets. The last step in manually creating your abend log is to find out what modules are loaded during the abend. You now have a completed abend log worksheet that can be used in the same way the generated abend.log file is used in determining the cause of a server abend. This NLM is a free utility from Novell that will allow you to generate many different types of abends and become more familiar with the abend.log. It creates real exceptions to trigger an abend and, as mentioned previously, puts the server into a critical state.