Novell NETWARE 6-DOCUMENTATION Manual page 2876

computer. Server performance might be poor, because a loaded NLM is
probably malfunctioning.
Read the Additional Information part of the abend message to learn which
NLM might be causing the problem. At a convenient time, shut down the
server and restart it. Examine the ABEND.LOG file for more information
about the source of the problem.
You can submit the ABEND.LOG file the the abend log database (http://
abend.provo.novell.com/index.html) at Novell to help you troubleshoot
the abend.
S=Return the running process to a safe state and
update the ABEND.LOG file
Like the previous option, this option appears if the abend was hardware-
detected—that is, detected by the processor. All hardware-detected
abends have the words processor exception in the abend message.
These abends include page faults, protection faults, and invalid op codes,
stack overflows, double faults, etc. When this option is listed, the server
has determined that it can return the process to a safe state.
When you execute this option, the server returns the running process to a
safe state and updates the ABEND.LOG file, but it does not shut down
the server. In most cases, the server completely recovers and no further
action is necessary.
Y=Copy diagnostic image to disk
Execute this option to perform a core dump that can be examined to
determine the cause of an abend. For information on core dumps, see
"Creating a Core Dump" on page 112.
X=Restart
This option appears only if DOS has been removed. Execute this option
if you want to restart the server.
If DOS has been removed, the server will not create or update an
ABEND.LOG file.
X=Update ABEND.LOG and then exit
Execute this option if you want to shut down the server and exit to DOS.
If you power off the server without first executing one of the S or R
options to resolve the abend, the server will not update the ABEND.LOG
file.
Troubleshooting the NetWare Server 119