Destination: CONSOLE (
Warranty : NO
HAL0001 MDEBUG ACTIVE
The master debugger mdebug has been started.
Destination: CONSOLE (
Warranty : NO
HAL0002 MDEBUG INACTIVE
The master debugger mdebug has been stopped.
Destination: CONSOLE (
Warranty : NO
HAL0111 ADMIN RESET GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP
VM2000 has stopped and reset the processor concerned due to a VM2000 command.
Destination: CONSOLE (
Warranty : NO
HAL0112 ADMIN STOP GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP
VM2000 has stopped the processor concerned due to a VM2000 command.
Destination: CONSOLE (
Warranty : NO
HAL0140 HAL ABORT GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP
The HAL on this processor has detected an inconsistency and has terminated the
processing of BS2000 instructions on all processors.
In the SEM execute the action “Generate new diagnostic data" under Hardware -> Server ->
Please notify the Customer Support.
Destination: CONSOLE (
Warranty : NO
HAL0141 HAL ABORT GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP OTHER GP
The HAL on another processor has detected an inconsistency and has terminated the
processing of BS2000 instructions on all processors.
This message is a continuation message of HAL0140.
Destination: CONSOLE (
Warranty : NO
HAL0211 MDEBUG STOP GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP
The master debugging interface has been used by either mdebug or RMAassist to halt the
processing of BS2000 instructions. This may happen as a normal part of IPL processing or
if mdebug is being used to examine the system.
Destination: CONSOLE (
Warranty : NO
HAL0212 MDEBUG STOP GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP BREAK-POINT
A break point set by mdebug has been executed by the given processor. The processing of
BS2000 instructions has been halted.
Destination: CONSOLE (
Warranty : NO
HAL0213 MDEBUG STOP GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP DATA TRAP
The given processor has executed an instruction that has modified a virtual memory
address that is being monitored for modification via mdebug. The processing of BS2000
instructions has been halted.
Destination: CONSOLE (
Warranty : NO
HAL0214 MDEBUG STOP GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP SAVE-STATE
The master debugging interface has been used by either mdebug or RMAassist to halt the
processing of BS2000 instructions in preparation for a new IPL. This always happens as a
normal part of IPL processing.
Destination: CONSOLE (
Warranty : NO
HAL0215 MDEBUG SPIN GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP FW-STOP
The relevant processor has interrupted the execution of BS2000 instructions due to a breakpoint in HAL set by mdebug.
Destination: CONSOLE (
Warranty : NO
HAL0221 MDEBUG START GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP
The master debugging interface has been used by either mdebug or RMAassist to start the
processing of BS2000 instructions. This is not a normal part of IPL processing but the result
of administrator intervention with mdebug or RMAssist.
Destination: CONSOLE (
Warranty : NO
HAL0231 MDEBUG RESET DATABP GPXX
The monitoring for modification of a virtual memory address has been stopped on the
processor concerned.
Destination: CONSOLE (
Warranty : NO
HAL0241 MDEBUG SET DATABP GPXX VVVVVVVVVVVVVVVV
The monitoring for modification of the given virtual memory address has been started on
the processor concerned.
Destination: CONSOLE (
Warranty : NO
HAL0311 BS2000 STOP GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP DISABLED-WAIT
A new PSW has been loaded by the given processor in which the wait bit is set and no
interrupts are enabled. As a result, the processing of BS2000 instructions has been halted.
This may occur as part of a normal system shutdown or may be due to a system crash -
SETS.
If the BS2000 system is no longer running and was not terminated intentionally, please perform a SLED to back up the diagnostic data.
Destination: CONSOLE (
Warranty : NO
HAL0312 BS2000 STOP GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP SIGP
BS2000 stopped the processor concerned using an SIGP instruction. This is a normal
during BS2000 system shutdown or when a CPU is detached, but also occurs in
conjunction with a system crash or SETS.
If the BS2000 system is no longer running and was not terminated intentionally, please
perform a SLED to back up the diagnostic data.
Destination: CONSOLE (
Warranty : NO
HAL0313 BS2000 STOP GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP SIGP RESET
BS2000 has reset the processor concerned using an SIGP instruction.
Destination: CONSOLE (
Warranty : NO
HAL0314 BS2000 STOP GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP SIGP STORE-STATUS
BS2000 used an SIGP instruction to request that diagnostic data about the current state of
the processor concerned be saved.
Destination: CONSOLE (
Warranty : NO
HAL0315 BS2000 STOP GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP START DUMP
The processor concerned has been stopped because a dump IPL has been started by
BS2000 (Crash Restart).
Destination: CONSOLE (
Warranty : NO
HAL0316 BS2000 STOP GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP START IPL
The processor concerned has been stopped because an IPL has been started by BS2000
(Shutdown Restart).
Destination: CONSOLE (
Warranty : NO
HAL0321 BS2000 START GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP SIGP
BS2000 has started the processor concerned with an SIGP instruction.
Destination: CONSOLE (
Warranty : NO
HAL0322 BS2000 START GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP IPL-RESTART
The master debugging interface has been used by either mdebug or RMAassist to start the
processing of BS2000 instructions directly after a new IPL boot block has been loaded. This
is the last step in normal IPL processing.
Destination: CONSOLE (
Warranty : NO
HAL0440 IOD ABORT GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP IOD-ABEND
An error has been recognized by the input/output driver and processing has been
terminated. In the case of a BS2000 restart and a DIPL into the running system, this
message is normal and can be ignored.
Examine the proceeding messages on the BS2000 console for information as to the cause
of the problem.
| ©2019 Fujitsu Technology Solutions GmbH | BS2000 OSD/BC System Messages |