4.6 FTSS Event Reporting Interface
The EHS externalizes events by reporting them to the event reporting interface
(ERI). The ERI, in turn, passes notification of the event to the FTSS$SERVER
process. The server reports the event in one of three ways:
1.
Generating messages that are sent to the operator console.
2.
Entering additional information into the system error log.
3.
Reporting the event to an external mailbox which can be read by a user
application.
4.6.1 Event Reporting Interface Routines
The EHS reports events by calling the following ERI routines located in the
FTSS$CORE image.
FTSS$ZONE_AVAILABLE is called to report the availability of the other zone
or CPU. This occurs when the IZC notifies the EHS that the zone has completed
diagnostics and is available for use. A message code is added by the EHS and
results in an OPCOM message and an error log being generated by the server.
FTSS$ERROR_REPORT is called by the EHS when a FRU is identified as the
error source. This can occur as a result of a hardware or software detected
failure. In this call the EHS passes error information through ERI to the server
process. The server generates the appropriate messages to the operator console
and user applications, and makes entries in the error log.
4.6.2 Error Event Messages
The following messages are passed to OPCOM and the system error log by
the server. Each message corresponds to an EHS error event and contains
information that identifies the FRU.
FTSS$_CABLEGONE, cross-link cable fault detected
Facility: FTSS
Explanation: The crosslink cable has been isolated as the cause of a system
failure. One zone will be removed from service by the operating system. For
transient failures, the error will be compared to its error rate threshold.
If the threshold is not exceeded, the zone will be resynchronized when it
completes diagnostics.
User Action: If the zone is automatically resynchronized, no action
is required on the part of the user. If the zone is not automatically
resynchronized, the system error log should be examined for entries which
correspond to the cross-link cable failure. These entries will identify an FRU.
FTSS$_CLOCK_END, Clock fault end action complete
Facility: FTSS
Explanation: Error processing for a clock fault has been completed and the
zone is available to be resynchronized.
User Action: If the zone is automatically resynchronized by FTSS, then no
action is needed on the part of the user. If the zone is not resynchronized,
the system error log should be examined for entries which correspond to clock
fault. These error logs will identify an FRU.
4–40 Error Handling and Analysis