AutoMaint
AutoMaint Strategy
The automatic BER analysis (AutoBER) provides a reference code (see: “Refer-
ence Code Structure” on page 11-21). It identifies, either the faulty FRU(s), the
software/microcode errors, or other error causes (for example, CP sysgen).
This reference code is sent both to the network console through alert and to the
MOSS console through alarm. When the host operator receives it within the alert,
the NetView panels or the
Problem Determination Guide (PDG) for alarm, may ask
him to contact the HCS/HSC, and to give them the reference code.
If NetView is not available, once the alert is received on VTAM it is logged on the
LOGREC disk. In this case, the customer must consult the alarm displayed at the
MOSS console.
The reference code is put in the header of the analyzed BER on disk, and:
If an alarm must be generated, the reference code is appended to:
– The alarm on disk, and
– The alarm on the console.
If an alert must be generated, the reference code is provided as one of the
variable data.
Note: If alarms can always be generated when applicable, alerts need to have a
CP loaded and operational to be transmitted from MOSS to NetView
through NCP and VTAM. Then, it is not unusual to have some alarms with
no alert.
In addition, for some specific cases, only a panel hexadecimal error code is
available. Customers have to use the PDG, service personnel will refer to
the MIP.
Using the ELD function, CEs and customers can have access to the complete list
of alarms, BERs, reference code in the BER file itself, through the MOSS console.
In case of alarm, the CE can log specific information, which will be kept by the
system (alarm).
This type of information can be useful to keep a history file of CE interventions.
The different alarms are identified through a two-digit hexadecimal value called the
alarm number. When existing, related alert always carries this number through a
field called Product Alert Reference Code, not to be confused with the Automain
Reference Code which appears in alert through a field called IBM 3745 Reference
Code.
Alerts on NetView screens are generally self explanatory. Code points transmitted
in Generic Alerts are translated by NetView into understandable text, except
product variable data which is displayed as specified in alert. Then if the PDG
gives the list of alerts with their contents, it is only for information to customers so
11-16
IBM 3745 Models 130, 150, 160, 170, and 17A: Hardware Maintenance Reference
Summary of Contents for 3745 Series
Page 2: ......
Page 12: ...x IBM 3745 Models 130 150 160 170 and 17A Hardware Maintenance Reference ...
Page 14: ...xii IBM 3745 Models 130 150 160 170 and 17A Hardware Maintenance Reference ...
Page 18: ...xvi IBM 3745 Models 130 150 160 170 and 17A Hardware Maintenance Reference ...
Page 21: ...3745 Models 130 150 160 and 170 Data Flow Chapter 1 General Information 1 3 ...
Page 149: ...For RACs 241 to 244 ERR bits Data received from the adapter Chapter 3 Buses 3 57 ...
Page 166: ...4 14 IBM 3745 Models 130 150 160 170 and 17A Hardware Maintenance Reference ...
Page 169: ...Chapter 4 Transmission Subsystem TSS 4 17 ...
Page 322: ...6 28 IBM 3745 Models 130 150 160 170 and 17A Hardware Maintenance Reference ...
Page 348: ...7 26 IBM 3745 Models 130 150 160 170 and 17A Hardware Maintenance Reference ...
Page 625: ...The ESS in 3745 Models 130 150 160 and 170 Data Flow Chapter 12 Ethernet Subsystem ESS 12 3 ...
Page 674: ...X 6 IBM 3745 Models 130 150 160 170 and 17A Hardware Maintenance Reference ...
Page 708: ......
Page 711: ......
Page 712: ...IBM Part Number 03F5010 Printed in Denmark by IBM Danmark A S ð3F5ð1ð SY33 2ð66 4 ...