Novell NETWARE 6-DOCUMENTATION Manual page 2874

Responding to the Abend Manually
You can respond to the abend manually or have the server respond
automatically.
When you respond manually, the server determines the nature of the abend
and displays the appropriate response option on the screen, along with
additional options for bringing down the server or executing a core dump. You
must execute an option to respond to the abend.
When the server responds automatically, it executes the appropriate response
without intervention.
IMPORTANT:
Sometimes an abend (or a faulty NLM program) can cause the
server console to stop functioning. In this case, the abend message is not
displayed and you cannot enter commands at the console prompt.
After a server failure, we recommend turning the power off of the computer and
restarting it rather than just exiting to the DOS prompt, C:\NWSERVER, and typing
SERVER again.
The default method of responding to an abend is automatic. (See
to the Abend Automatically" on page
To respond manually to abends, change the following SET parameter (Error
Handling category) to the value shown:
AUTO RESTART AFTER ABEND = 0
This SET parameter controls what the server does after an abend. See the
online help for a description of each value.
When an abend occurs, the server displays a short list of options appropriate
to the nature of the abend. To respond to the abend, you must execute one of
the options by typing the first letter of the option.
The following options could be displayed. Note that several of the options
have the same first letter (such as R, S, or X). In a given abend situation, the
option list will include only one option for any given first letter.
S=Suspend the running process, update ABEND.LOG,
and attempt to down the server
This option appears if the abend was software-detected— that is, detected
by the network operating system. It is important to save files, shut down
the server, and try to solve the problem that caused the abend. Review the
ABEND.LOG file to help determine the source of the problem.
120.)
Troubleshooting the NetWare Server 117
"Responding