FTSS$_ZONEHALT, Zone Halt fault detected on zone [zone_id]
Facility: FTSS
Explanation: A single zone of a Duplex system has been halted. This can be
caused by a user command on the system console or by a system error.
User Action: If the Halt was caused by a user command on the system
console, a START/ZONE command must be executed to restore the zone to
service. If the Halt was not caused by a user command, the system error log
should be examined for entries which correspond to the zone halt error. These
entries will identify an FRU.
FTSS$_ZONEUNSYNC, Zone [zone_id] is unsynchable
Facility: FTSS
Explanation: When a zone completes diagnostics with failure and reports
this status to the zone running the operating system, this message is
generated. The zone with the failure will not be automatically resynchronized
by FTSS.
User Action: The system error log should be examined for the entry which
corresponds to the unsynchable event. This entry will indicate an FRU.
4.6.2.1 Deconfiguration Messages
The following messages can be passed to OPCOM and the system error log file
by the FTSS$SERVER at the request of EHS. Each message corresponds to a
deconfiguration activity performed by EHS. Each message contains information
(through FAO arguments) that identifies the entity deconfigured by EHS.
FTSS$_DECONFIG_ATMIO, I/O expansion subsystem on I/O attachment
module in slot [slot_id], zone [zone_id] has been removed from service
Facility: FTSS
Explanation: Due to one or more system errors, the I/O expansion
subsystem on the indicated I/O ATM and its associated Interface modules
have been removed from service.
User Action: The system error log should be examined for entries which
correspond to the removal of the I/O expansion subsystem. These entries will
indicate an FRU.
FTSS$_DECONFIG_CPUMOD, CPU module in slot [slot_id], zone [zone_id] has
been removed from service
Facility: FTSS
Explanation: Due to one or more system errors, the indicated CPU module
has been removed from service. In some cases, the CPU may be automatically
resynchronized by FTSS when it successfully completes the execution of
diagnostics.
User Action: If the CPU is automatically resynchronized by FTSS after
completing diagnostics, no action is required on the part of the user. If the
CPU is not automatically resynchronized, the system error log should be
examined for entries which relate to the removal of the CPU. These entries
will indicate an FRU.
Error Handling and Analysis 4–49