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

REI002
Explanation: (soft abend) HCPREIPB or HCPREIPQ
(which fills in the protect block (HCPPROBK) with error
information when the user is in the protected application
environment) has been called with an option
(ERMALTVM, ERMOPER, or QCNOPER) that the
protected application environment does not support.
User Response: Check the trace table to determine
what module called HCPREI. Input register 2 contains
the option bits specified. If HCPREIPB is called, the
option bits are interpreted according to how
HCPERMSG interprets the options. If HCPREIPQ is
called, the option bits are interpreted according to how
HCPQCNWT interprets the options. Save the dump and
contact your IBM support personnel to diagnose and
correct the problem.
REP001
Explanation: The error recovery procedure called
HCPREP to either end a level of recursion or to obtain
the address of the previous IORBK. The recursive
IORBK pointer (IORPIOR) contained zeros, which
produced the abend. IORPIOR should contain the
address of the IORBK that is one less in the recursive
structure.
User Response: Examine the save area or trace table
entries to determine the calling module. Check R10 to
find out if it is pointing to a valid IORBK. If R10 does
contain the address of the IORBK, and a valid IORBK
does not exist at that address in storage, storage was
probably overlaid. If R10 is not pointing to a valid
IORBK, R10 was probably not set by the requestor.
RER005
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.
RES001
Explanation: (soft abend) A virtual reset was done for
a particular active I/O. However, when the reset was
initiated the I/O request was not found to be active for
the virtual device.
User Response: R10 contains the address of the
IORBK that represents the I/O for which the reset has
been requested. In addition, the VDEV is pointed to by
R6, the RDEV by R8, and the VMDBK by R11.
RES002
Explanation: (hard abend) Virtual device reset
processing is unable to delete or halt a QDIO
subchannel. Prior to deleting the QDIO queues, reset
processing should have terminated all active I/O on the
subchannel. Terminating an Activate-QDIO-Queue
channel program should make a QDIO subchannel
inactive.
If reset processing has detected that the QDIO
subchannel is still active, the system cannot be allowed
to continue. As long as the QDIO queue is active, the
channel subsystem has free rein of all storage assigned
previously by an Establish-QDIO-Queues channel
program.
User Response: Contact your IBM support personnel.
RFC001
Explanation: (soft abend) z/VM deletes a CP volume
from the configuration. Entry point HCPRFCDC
processed a channel report word (CRW) that indicated
that a CP volume had been deleted from the I/O
configuration. The address in register 4 is that of the
CRW; the address in register 8 is that of the real device
(RDEV).
User Response: None.
RFC002
Explanation: (soft abend) The system entered module
HCPRFCET, and there was no DIOBK for the given
RDEV. One possible cause is that there are more
outstanding CRW tasks than accounted for in
DIOCOUNT. If an outstanding task calls HCPRFCET
and if DIOCOUNT decrements to zero, then the DIOBK
is fretted. This assumes there are no more CPEBKs
(CRW tasks) on DIOQUEUE.
Entering HCPRFCET without a DIOBK implies the
counter was previously zero, and therefore, one or more
outstanding tasks is unaccounted for; possibly the one
that made this call to HCPRFCET.
User Response: None.
RRM001
REI002 RRM001
Explanation: (soft abend) HCPGDSIM requested that
CP obtain the real reserve, when CP already holds the
real reserve or has a pending reserve request.
User Response: Determine why HCPGDSIM is not
aware that CP has already obtained or is in the process
of obtaining the real reserve. Verify that the virtual I/O
configuration is correct. It is possible that multiple
minidisk blocks exist.
Chapter 2. System Codes 95