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

HCP912W HCP954I
HCP912W System recovery failure; volid volid not
mounted
Explanation: A volume necessary for checkpointing
the system is not mounted. The volid refers to the
volume ID of the volume that is not mounted.
When CP issues this message, the volid should be the
volume ID specified on either the SYSCKP or SYSWRM
parameters of the SYSRES macro in HCPSYS, or the
CHECKPOINT or WARMSTART operands of the
SYSTEM_RESIDENCE statement in the SYSTEM
CONFIG file.
The warm start data indicates spool files are allocated
on a system volume, and that volume is not mounted.
The possible causes are:
v The volume is not mounted.
v The allocation record (record 4 for CKD or blocks 3-4
for FBA) is missing or not valid.
v The volume is not in the CP OWNED VOLUME LIST.
v A non-CP formatted volume was specified in the
SYSTEM_RESIDENCE statement for the
CHECKPOINT or WARMSTART operands’ volid.
System Action: The system enters a disabled wait
state (wait state code = 912).
Operator Response: Mount the specified volume
required for CP warm start and IPL the system again. If
this is unsuccessful, you may IPL the system again and
specify a COLD or FORCE start.
Programmer Response: Ensure the volume is CP
formatted and in the CP OWNED VOLUME LIST. Verify
the correct volid resides in the SYSTEM CONFIG file or
the SYSRES macroinstruction if one was specified.
HCP951I {CP|USER} VOLID volid NOT MOUNTED
Explanation: You may have to mount and make ready
the specified volume.
System Action: System processing continues.
Operator Response: If you receive this message for a
CP volume required for spooling, you may not be able
to warm start successfully. If the specified volume
contains spool files and you want to warm start, you
should invoke a shutdown in response to the prompt for
type of start. Make sure that the specified volume is
mounted and ready before loading CP again, then
proceed with the warm start.
If you receive this message for a user volume, you can
mount and ready the volume and attach it to the system
during normal system operation. Users who are already
logged on will have to issue the LINK command if they
want to access a minidisk defined on that volume.
218 z/VM: System Messages and Codes — CP
HCP952I nnnnM SYSTEM STORAGE
Explanation: During the system IPL procedure, the
message indicates the amount of real storage. The size
of real storage is calculated as the minimum storage at
system generation time and configured real storage; for
more information, refer to QUERY STORAGE in z/VM:
CP Commands and Utilities Reference.
System Action: The system continues normal
operation.
Operator Response: No explicit action is necessary
because this message is presented to the operator for
informational purposes only. If the amount of storage
differs from what is expected, the operator should
request the System Programmer to verify normal
system operation is in effect.
HCP953E CP is unable to allocate system DASD
dump space.
Explanation: CP was unable to find enough disk
space to hold a possible CP abend dump. This could
occur if you did not use ICKDSF or the CPFMTXA utility
on DASD, or did not specify a valid DASD address in
the SET DUMP command.
System Action: The system continues normal
operation.
Operator Response: No action on the part of the
operator is necessary. The system dump has been set
to the default of the system printer. If you issued a
successful SET DUMP command with a DASD address,
and later issued another SET DUMP command that was
not successful, message HCP953E may appear. The
default device would then be the DASD specified in the
previously successful SET DUMP command. The
operator may change the dump to another printer or
tape drive. If spool space becomes available, you may
also be able to try the dump again. Use ICKDSF or the
CPFMTXA utility to check the format of the system
volume. See z/VM: System Operation for additional
information.
HCP954I DASD rdev2 VOLID volid IS A
DUPLICATE OF DASD rdev1
Explanation: During the system IPL procedure, the
system detected duplicate volume identifiers on two
DASD volumes. DASD rdev1 contains a volume
identifier volid identical to DASD rdev2.
System Action: System operation continues. DASD
rdev2 is not attached.
Operator Response: Verify that the volume mounted
on DASD rdev1 is the one to be used by the system. If
it is not, CP may perform incorrect allocation on the
volume specified. Shut down the system and remove
the incorrectly labeled volume that is a duplicate. This
message usually occurs after a system restart when
users have mounted volumes with labels identical to