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

User Response: None.
HCP6719W System initialization cancelled at
operator’s request; system restart
halted.
Explanation: You receive this message in response to
a STOP command, or in response three invalid
responses from the system operator to prompts
HCP6717A or HCP6738A.
System Action: CP loads a disabled wait immediately
after issuing this message.
User Response: None.
HCP6720I No items found to satisfy selection
criteria.
Explanation: You entered one of the CP LOCATE or
CP LOCATEVM commands asking CP to locate
information that it cannot find. For example, if you
entered CP LOCATE CPREAL 0-1ff DATA XYZ, and CP
could not find any occurrences of the string XYZ in
locations X'0000' through X'01FF', you would receive
this message.
System Action: The CP LOCATE or CP LOCATEVM
command completes; system operation continues.
User Response: None.
HCP6721E Device rdev was marked not accepted
on the DEVICES statement in the
system configuration file or on a Set
DEVICES command
Explanation: You entered a CP SET RDEVICE
command or CP SET EDEVICE command to define a
new device that was marked as an unacceptable device
number on either a:
v DEVICES statement in the system configuration file
v CP SET DEVICES command.
System Action: CP ignores the request to define the
real device control block (RDEV). For the CP SET
RDEVICE command, processing for any other device
numbers specified on that command continues.
User Response: You can either:
v Enter the SET RDEVICE or SET EDEVICE command
again and specify a device number that was marked
as an acceptable device number.
v Change the unacceptable device number to an
acceptable device number (using the ACCEPTED
operand of the SET DEVICES command) and enter
the SET RDEVICE or SET EDEVICE command
again.
HCP6722I The variations of this message are
explained below.
MESSAGES:
v Created RDEV for device rdev.
v Characteristics of device rdev were set as
requested.
Explanation: You entered a CP SET RDEVICE
command that causes CP to create a new real device
block (RDEV), or to modify an existing RDEV for an
offline device. You will receive one of the above
messages for each device number affected by a CP
SET RDEVICE command. You will also receive a
message that summarizes the changes caused by the
CP SET RDEVICE command.
System Action: System operation continues.
User Response: None.
HCP6723E Requested parm disk not found in
allocation map.
Explanation: You issued a CP SHUTDOWN REIPL
command with the EXTENT option to specify a parm
disk extent that does not exist in the allocation map of
the IPL volume.
System Action: CP ignores the CP SHUTDOWN
command; normal processing continues.
User Response: If you want to shut down and re-IPL
the system with a parm disk different from the one the
system is currently using, enter the CP SHUTDOWN
REIPL command with a valid parm disk extent number,
or specify a parm disk by using the MDISK option.
HCP6724E REQUESTED PARM DISK VOLUME IS
INVALID.
Explanation: You used the PDVOL option on the
stand-alone loader to pass to CP the real device
address of the volume that contains the parm disk you
want CP to access. This message tells you that there is
no device at the specified address, or that the device at
the specified device address is not a supported DASD.
System Action: CP loads a disabled wait state and
cancels the IPL.
User Response: Re-IPL the system and specify a
valid address on the PDVOL option, or IPL without
specifying the PDVOL option at all.
HCP6725E {XLINK|XSPOOL} system ID nnnnnnnn
is a duplicate -- statement ignored.
Explanation: You specified a system ID on one of the
following statements in the system configuration file:
v XSPOOL_SYSTEM,
v XLINK_SYSTEM_INCLUDE, or
v XLINK_SYSTEM_EXCLUDE,
HCP6719W HCP6725E
Chapter 3. System Messages 391