Novell NETWARE 6-DOCUMENTATION Manual page 3488

SERVER-X-202: Detected user thread hogging the CPU.
Source:
Explanation:
Action:
SERVER-X-286: Invalid resource tag passed to api_name.
Source:
Explanation:
Action:
SERVER-X-312: Invalid resource tag passed to api_name.
Source:
Explanation:
Action:
SERVER-X-276: Invalid screen ID passed to screen manager. Module: name. Code
offset in module: offset.
Source:
Explanation:
SERVER-X-384: This module is using one outdated API call. You should upgrade to a
newer module when it becomes available.
Source:
Possible Cause:
SERVER.EXE
A thread running in a protected address space has not relinquished the CPU,
causing the address space to fault.
How the server responds to the fault depends on whether the Memory
Protection Fault Cleanup parameter is set to On or Off and whether the address
space is restartable. See
in the Server Operating System Administration
abend: review the abend.log file in sys:\system; break into the debugger to
find more information (press Shift + Shift + Alt + Esc); if necessary, perform
a core dump. For more information, see
Operating System Administration
SERVER.EXE
There could be a bug in the NLM, or the NLM might be corrupted.
Contact the NLM vendor.
SERVER.EXE
There could be a bug in the NLM, or the NLM might be corrupted.
Contact the NLM vendor.
SERVER.EXE
See "SERVER-X-6: Invalid screen ID passed to screen manager. Module:
name. Code offset in module: offset." on page
SERVER.EXE
The operating system displays this message whenever an NLM is loaded that
is using old API calls. NetWare renamed some of the APIs as additional
Memory Parameters
Resolving Abends
Guide.
and Managing Server Memory
Guide. Treat the problem as an
in the
535.
SERVER Messages 537
Server