IBM 3745 Series, Справочник по техническому обслуживанию оборудования

Страница: 421 / 712

BER Type and Identification
BER Type
The first byte of information concerning the event, points to the general area of
BER occurrence:
Table 11-3. BER Types Description
Type Description
01 MOSS-related events or errors (plus events or errors recorded by MOSS when MOSS
takes control of the box, or operations such as CCU hardcheck, scanner errors...
03 Diagnostic error detection (CE option)
04 Power subsystem errors, and events reported to MOSS by the power control
08 Events/errors related to ESS operations
09 Events/errors related to 3746-900 operations
10 Events/errors related to channel adapter operations
11 Events/errors related to transmission subsystem operations
12 Control program exceptions (software errors detected by the hardware)
13 CCU-related events/errors when NCP/PEP has control (excluding CCU hardcheck)
14 IOC bus-related errors, when not possible to attribute them to a specific adapter
15 TRSS events/errors related to token-ring subsystem operations
BER ID
The second byte identifies the category of error or event:
BER Created by the NCP/PEP
bit 0 Probable cause of the error.
OFF The most probable cause is the control program
ON The most probable cause is the hardware or the microcode
bits 1 to 3 Program level that recorded the error/event.
001 Control program level 1
010 " " " 2
011 " " " 3
100 " " " 4
BER Created by the MOSS: When a BER is created by the MOSS, a byte identi-
fies the origin of the error or event.
The complete list of MOSS BER IDs is given in “MOSS BER Type 01 - Summary”
on page 11-33.
Here the ID does not refer to event/error categories as in the NCP/PEP. For
MOSS BERs, the event/error categories are found in another byte, called
'MOSS-CHECK'.
Chapter 11. Error Logging
11-9