Novell NETWARE 6-DOCUMENTATION Manual page 2873

Resolving Abends
Understanding What Happens When You Get an Abend
116 Server Operating System Administration Guide
Locked Device Errors
Event Control Block Allocation Errors
Console Command Problems
Keyboard Locking Problems when Copying Files from CD-ROM
The NetWare operating system is very resilient, but errors can occur. Serious
problems are usually accompanied by abend (abnormal end) messages. When
an abend message appears, either NetWare or the CPU has detected a critical
error condition and started the NetWare fault handler. NetWare uses abends to
ensure the integrity of operating system data.
When a server abends, users might not be able to log in to the server,
workstations might not be to read from or write to the server, and an abend
message usually appears on the System Console or Logger screen of the server
console. If the NetWare auto-recovery mechanism is enabled (default),
NetWare might restart the server automatically or suspend the offending
process, depending on the nature of the abend.
If there is no abend message on the console, no ABEND.LOG file in
SYS:SYSTEM, and no number in brackets within the System Console
prompt, but users still can't access the server, see
Communication Problems" on page
console is frozen so that you cannot enter commands, see
Hangs" on page 124.
When the server abends, it displays an abend message similar to the following:
Abend: SERVER-5.xx-message_number message_string
ADDITIONAL INFORMATION: message
The Additional Information section states the probable cause of the abend. It
indicates where the problem occurred and gives the name of any NLM
associated with the abend. This information helps you determine how to
resolve the abend.
The abend message, along with additional information, is saved in the
ABEND.LOG file on drive C:. As soon as the server is restarted, the
ABEND.LOG file is moved to SYS:SYSTEM.
"Monitoring and Resolving
147. If there is no abend message but the
"Server Console