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

CNF002 DCO001
CNF002
Explanation: (soft abend) While processing a
DIAGNOSE code x’08’ instruction that requested a write
to buffer, CP received a request to write to an address
detected as being incorrect. CP writes no data to the
guest’s storage.
User Response: Examine the trace table to determine
why the address became incorrect (for example, the
address is in a saved segment that was released by the
other side of a virtual MP). R1 contains the address.
CPN001
Explanation: (soft abend) HCPCPN, the VARY
ONLINE device module, received an unrecognized
return code from HCPRDI. HCPRDI is called to attempt
to vary a device online. HCPRDI returns a code
indicating the results of its attempt to bring the device
online.
User Response: Examine the return code in R15 that
HCPRDI sent. See if HCPRDI is returning an incorrect
return code.
CPT001
Explanation: (hard abend) VMDDFRWK, the deferred
work counter in the VMDBK was about to become
negative.
User Response: Examine the CP Trace Table and
storage dump to see why the VMDBK in R10 has a
zero value for the VMDDFRWK field.
CPX001
Explanation: (soft abend) A request to create a list of
multiple-exposure addresses failed because one of the
nonbase device exposure’s RDEV blocks did not exist.
User Response: Check whether you created the I/O
configuration incorrectly at system generation time. If
so, recreate the I/O configuration.
CSG005
Explanation: A VDEV for a virtual card reader does
not point to a valid VSPBK. All simulated virtual card
readers should always have a VSPBK associated with
them.
User Response: Examine the VDEV pointed to by R6,
and the trace table, to see why the VDEV does not
point to a VSPBK. One possibility is that the device is
being detached; if so, the trace table will include an
entry returning the storage occupied by the VSPBK to
free storage.
30 z/VM: System Messages and Codes — CP
CTU001
Explanation: (soft abend) HCPCTU could not find the
CCW (channel control word) that was pointed to by the
SCSW (subchannel status word). Untranslation of the
host channel program was not possible.
User Response: Examine the SNAPLIST data, the
host channel program and HCPCTU to determine the
reason for this abend. The SNAPLIST data contains the
IORBK, VDEV, RDEV, and up to 10 CTRBK control
blocks.
CVT001
Explanation: The time-of-day (TOD) clock is not
working, damaged, or not set, and the timer initialization
has been completed.
User Response: Contact your IBM support personnel
for hardware support to fix the clock.
DBC001
Explanation: An attempt was made to release a read
share of the TCHBK lock (TCHLOCK), but the lock was
held in the exclusive state.
User Response: General Purpose Register (GPR) 2
points to the TCHBK in question.
DBC002
Explanation: A condition code 1 or 3 occurred on an
LRA instruction to get the real address associated with
the virtual address of an MDC cache page. The LRA
processed when attempting to resolve a page fault that
occurred when moving data between the guest address
space and MDC address space. The page fault may
have occurred in either address space.
User Response: General Purpose Register (GPR) 14
points to the virtual MDC cache page address. GPR 2
points to the TCHBK.
DBC003
Explanation: The VMDBK critical process counter
(VMDCTCRT) went negative after subtracting 1. This
occurred while attempting to release the exclusive
BLKIO block lock (BLKLOWN).
User Response: General Purpose Register (GPR) 1
points to the VMDBK in question. GPR 3 points to the
BLKIO block.
DCO001
Explanation: (Hard abend) HCPDCOOV was called to
process a MODIFY COMMAND. While processing the
PRIVCLASS operand, an impossible internal condition
occurred.