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

HCP6726E HCP6733E
And an earlier statement of the same type has already
specified that system ID.
System Action: CP ignores the second statement and
continues processing the system configuration file.
User Response: Delete extra statements from the
system configuration file before the next IPL.
HCP6726E Could not find any CP-owned volumes
that met the specified criteria.
Explanation: You will see this message in one of two
cases:
v You entered a CP QUERY CPOWNED DASD
command with a range of real device numbers, and
CP could not find any DASD within this range.
v You entered a CP QUERY CPOWNED VOLUME
command with a volume identifier, and CP could not
find a DASD with the volume identifier you specified.
System Action: System operation continues.
User Response: None.
HCP6727I The variations of this message are
explained below.
MESSAGES:
v Disk fm not accessed.
v No disks accessed.
Explanation: You will see this message in one of two
cases:
v You entered a CP QUERY CPDISK command with a
specific file mode, and CP does not have a disk
accessed in that file mode.
v You entered a CP QUERY CPDISK command without
any other operands, and CP does not have any disks
accessed.
System Action: System operation continues.
User Response: None.
HCP6728E {File|Member} not found.
Explanation: You entered a CP CPLISTFILE
command specifying a file or files that CP cannot find,
or the member or members you requested were not
found in any of the files that matched your request.
System Action: System operation continues.
User Response: Enter the CP QUERY CPDISK
command to find out which minidisks CP has accessed,
and then enter the CP CPLISTFILE command with a
correct file name, file type, and member. In order for the
file to contain members, it must be a CMS partitioned
data set (PDS), such as a TXTLIB.
392 z/VM: System Messages and Codes — CP
HCP6729I No files cached.
Explanation: A CP CACHE command was entered.
One of two conditions exist:
v CP cannot find any files matching the file name, file
type, or file mode you specified on any of the
minidisk it has accessed.
v The file was not cached because it has already been
cached. CPLISTFILE can be used to verify what may
already be cached.
System Action: System operation continues.
User Response: Check the name, type, and mode of
file you want to cache, and reissue the CP CPCACHE
command with correct operands.
HCP6730I CPRELEASE request for disk fm
completed.
Explanation: You entered an asynchronous
CPRELEASE command for the disk that CP had
accessed at the file mode fm, and the disk is now
released.
System Action: System operation continues.
User Response: None.
HCP6731E {CPRELEASE|CPACCESS} request for
mode fm already active.
Explanation: You issued a CPRELEASE or
CPACCESS command for a file mode for which the
same command is already active.
System Action: CP ignores the second command;
system operation continues.
User Response: You can issue a QUERY CPDISK
command to find out which disks CP has accessed
before you try to issue another CPRELEASE or
CPACCESS command.
HCP6732I CPACCESS request for userid’s vdev in
mode fm completed.
Explanation: You issued an asynchronous
CPACCESS command telling CP to access at the file
mode fm the disk that the user userid has accessed at
the virtual device number vdev, and the command has
completed.
System Action: System operation continues.
User Response: None.
HCP6733E The variations of this message are
explained below.
MESSAGES:
v Disk is not a CMS EDF formatted minidisk -- disk
not accessed.