Specifications

3.4 Loading Failure
After you load SYSEX, one or two messages appear on the console monitor. If
the only message is the following, loading was successful:
Verifying program loaded correctly
If the error report ‘‘Checksum error detected at load time’’ follows the above
message, the loading failed. Take the following action:
1. Reload the diskette.
2. Reboot. If this fails to correct the loading failure, try a different SYSEX
diskette in case the first diskette is bad.
3. If this load also fails, check for failed memory or a bad load path. A bad
load path occurs when either the diskette drive itself is bad or the cable
to the diskette drive is bad. Section 4.9 provides information on replacing
memory modules.
4. Run the POST tests again for possible further information.
3.5 Error Reports
If SYSEX detects an error condition or a failed FRU, an error report is
displayed on the monitor and written to the error log. By default, SYSEX
stops execution when an error is detected. (Information in the error log can be
displayed using the log command.)
Each error report calls out a FRU. Because there may be more than one of any
type of FRU in the system, additional information is provided to identify which
of the multiple units has failed:
• For modules, the slot number indicates the module which has failed.
• For SIMM failures, the socket number of the failed SIMM is indicated.
• For SCSI storage devices, the bus ID and logical unit number of the device
is indicated. Also, the slot number of the associated adapter is identified.
SCSI devices controlled by an ISA SCSI adapter or an EISA SCSI adapter
are identified by the slot number of the adapter.
3–6 System Exerciser