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

HCP2629I The virtual machine is placed in CP
mode due to a SIGP stop from CPU nn.
Explanation: The processor with the address nn has
issued a SIGP stop order to the virtual CPU on which
the message is displayed.
System Action: System operation continues. The
virtual CPU is placed in hard stop state. The virtual
machine continues operation if there are any operational
virtual CPUs.
User Response: If it is determined that this action is
the result of an error, IPL the virtual machine again or
issue a BEGIN CPU command to start the stopped
virtual processor.
Note: This message is informational only and issued as
a result of a virtual processor’s action. This
action may be normal for your virtual machine
and may not require a response.
Programmer Response: Determine why the virtual
CPU issued the signal processor instruction and take
appropriate action.
HCP2630I The virtual machine is placed in CP
mode due to a SIGP stop and store
status from CPU nn.
Explanation: The virtual CPU with the address nn has
issued a SIGP stop and store status order to the virtual
CPU on which the message is displayed.
System Action: System operation continues. The
virtual CPU is placed in hard stop state. The virtual
machine continues operation if there are any operational
virtual CPUs.
User Response: If it is determined that this action is
the result of an error, IPL the virtual machine again or
issue a BEGIN CPU command to start the stopped
virtual processor.
Note: This message is informational only and issued as
a result of a virtual processor’s action. This
action may be normal for your virtual machine
and may not require a response.
Programmer Response: Determine why the virtual
CPU issued the signal processor instruction and take
appropriate action.
HCP2631I 370ACCOM has been set off due to a
SIGP set architecture from CPU
cpuaddr
Explanation: The CPU identified in the message
issued a SIGP instruction with the set architecture order
code. This caused the virtual machine to be placed into
z/Architecture mode, which is not compatible with
370ACCOM mode.
System Action: The 370ACCOM facility is set off.
User Response: The virtual machine can either have
370ACCOM turned on or it can be in z/Architecture
mode, but not both. The virtual machine is now in
z/Architecture mode with 370ACCOM set off. If that is
what is required, there is nothing to do. If the program
running in the virtual machine requires 370ACCOM,
then the virtual machine must be taken out of
z/Architecture mode and a SET 370ACCOM ON
command must be issued to put it back into that state.
HCP2632E A virtual machine in z/Architecture
mode may not have 370ACCOM on
Explanation: A SET 370ACCOM ON command was
issued in an attempt to place the user in 370ACCOM
mode, but the virtual machine was in z/Architecture
mode, which is not compatible with 370ACCOM mode.
System Action: The command is rejected.
User Response: The virtual machine can either have
370ACCOM turned on or it can be in z/Architecture
mode, but not both. The virtual machine is now in
z/Architecture mode with 370ACCOM set off. If that is
what is required, there is nothing to do. If the program
running in the virtual machine requires 370ACCOM, the
virtual machine must first be taken out of z/Architecture
mode and then a SET 370ACCOM ON command must
be issued to put it back into that state.
HCP2700I The variations of this message are
explained below.
MESSAGES:
v System gateway gateid identified.
Explanation: The system gateway successfully been
identified on the local z/VM system.
System Action: System processing continues.
Operator Response: None.
v No system gateway identified.
Explanation: The system gateway has not been
identified on the local z/VM system.
System Action: System processing continues.
Operator Response: If NOSYSGAT was coded in
the SYSID MACRO entry for the local z/VM system
then no action is necessary. Otherwise, ensure there
is an entry in the SYSID MACRO for the local z/VM
system or a DEFAULT is specified in the SYSID
MACRO. For more information, refer to the z/VM: CP
Planning and Administration book.
HCP2701I Link rdev went down.
Explanation: This is a response to either a
DEACTIVE ISLINK command or a failure for the link
group to receive a response from the other end of this
link. When the link group cannot get a response, this
could mean one of the following:
v There is a malfunction.
HCP2629I HCP2701I
Chapter 3. System Messages 295