z/VM: System Messages and Codes Š CP - z/VM - IBM

HCP601I HCP632E
HCP601I type rdev A CHANNEL CONTROL
CHECK OCCURRED
Explanation: A channel control check occurred on a
channel associated with device type rdev.
This message is displayed in conjunction with other
messages that provide information about channel
command word, sense, user ID, and other variables
when necessary.
System Action: System operation continues.
Operator Response: Probable hardware error. If the
problem persists, call your system support personnel.
HCP602I type rdev AN INTERFACE CONTROL
CHECK OCCURRED
Explanation: An interface control check occurred on a
channel associated with device type rdev.
This message is displayed in conjunction with other
messages that provide information about channel
command word, sense, user ID, and other variables
when necessary.
System Action: System operation continues.
Operator Response: This is probably a hardware
error. If the problem persists, call your system support
personnel.
HCP603W CHANNEL ERROR; RESTART SYSTEM
Explanation: A channel check condition occurred from
which the channel check handler could not recover.
System Action: The system enters a wait state (wait
state code = 603).
Operator Response: There is a hardware error.
Restart the system. Call your system support personnel.
To restart, clear storage and IPL the z/VM system,
specifying a CKPT start.
HCP604I CONFIGURATION ALERT FACILITY
TEMPORARY ERROR ON CHANNEL
PATH xxxx
Explanation: While attempting to service a request
from a device, the channel subsystem could not
associate a valid subchannel with that device. xxxx is
the channel path identifier.
System Action: System operation continues.
Operator Response: If the problem continues call
your system support personnel.
190 z/VM: System Messages and Codes — CP
HCP610I CHECK-STOP ON CPU nn
Explanation: Processor nn has entered the
check-stop state, but another processor continues
functioning. A check-stop is similar to a severe machine
check, but in addition, the processor comes to a halt.
(This message is issued from another processor.)
System Action: The system may or may not be able
to continue normal operation, running on the remaining
processor. It depends on what the system was doing at
the time of the error. Watch for further error messages
to follow this one immediately. If normal system
operation continues, the check-stopped processor will
be varied offline. If system termination is necessary, the
automatic software re-IPL may or may not occur
afterwards.
Operator Response: Contact your system support
personnel. If the system continues normal operation, the
operator may consider varying the failed processor back
online, using the CP VARY command. The check-stop
may have been an isolated event that will not repeat
itself. However, there is a risk in varying the failed
processor back online because the error may repeat
itself. And if the error does repeat, there is no guarantee
that the error will again occur at a point where normal
operation can continue; the system might terminate the
next time.
HCP630E The TOD-clock could not be
synchronized due to a processor
controller failure.
Explanation: TOD clock synchronization failed
because a processor physical vary offline or
deconfiguration failed.
System Action: System continues in single processor
mode with TOD synchronization check disabled.
User Response: Since the TOD clocks have not been
synchronized, varying any offline processors online may
cause TOD clock sync checks to recur. Contact your
IBM Support Center personnel for software support.
HCP632E A system shutdown is recommended
due to a processor controller failure.
Explanation: A service processor damage machine
check has occurred, which indicates the processor
controller has failed. The following functions are no
longer operational:
v SIGP for certain reset and console function orders
v Processing of machine checks (other than the
present “service processor damage”)
v Processor controller request process.
The only recovery is to re-IML the processor complex,
which will clear main storage.
System Action: Attempt to keep the system running,