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

VDE002
Explanation: (soft abend) An incorrect internal error
code was received by HCPVDERR while processing a
VMDUMP command.
The error code was incorrect for one of the following
reasons:
v The value of the error code was 0
v The value was larger than the maximum allowed
v The error code was unexpected while processing a
VMDUMP command (as opposed to while processing
a DIAGNOSE code x’94’).
User Response: Examine the SNAPDATA in the soft
abend. The SNAPDATA parameter list contains the
input error value and the maximum allowable value.
Determine which module called HCPVDERR; this is
recorded in the soft abend dump. When you obtain this
information, contact your IBM support personnel.
VDG001
Explanation: (soft abend) While processing a
DIAGNOSE code x’0D4’ instruction requesting an
alternate ID to be set, CP found the alternate ID
synchronization bits (field VMDALSYN in HCPVMDBK)
in an incorrect state.
System action continues after the abend, and a return
code of 16 is passed back to the issuer of the
DIAGNOSE in the RX register.
User Response: Examine the internal trace table and
storage dump to determine how the VMDALSYN was
set incorrectly. The two incorrect states are:
v VMDALD4O off and VMDALD4L on
v VMDALD4O on and VMDALAPO on
VDI001
Explanation: (soft abend) When the module HCPVDI
calculated the count of I/O requests active for a virtual
machine, the new value would have exceeded the
number of devices defined for that machine.
User Response: If VMDIOACT contains a value equal
to VMDDEVCT, it is likely that the routines that maintain
the active I/O count are defective. Either the field was
not decreased when appropriate, or it was increased
more than once per I/O request. If VMDIOACT exceeds
VMDDEVCT, it is likely that the correct value was
accidentally overlaid. Examine the VDEV blocks for the
virtual machine to determine how many requests were
active at the time of the dump. Examine the system
trace table to determine when the active requests were
started, and what other requests became inactive during
the interval. Analyze the modules that initiated the
requests to insure that the field VMDIOACT was
properly increased. (Module HCPVDI is among these
modules.) Analyze the modules that received control
from the real I/O supervisor when the system terminated
(as the field IORIRA indicated in the appropriate IORBK)
to ensure that VMDIOACT was properly decreased. If
the modules that update the field VMDIOACT contain
correct logic, try to determine how the data in the field
was destroyed.
VFM001
Explanation: The conditions that cause this abend to
occur are:
v The number of doublewords of virtual free storage
requested exceeded the maximum allowable request
size.
v A control block of an incorrect length was returned to
CP’s Virtual Free Storage Manager.
User Response: Depending upon the reason for this
abend, take one of the following respective actions:
v Examine the SAVBK to determine the CP module
obtaining the storage. Check for an error in
calculating the size of the block, or for a modification
to a stored block size for variable size blocks.
v At the time of the abend, General Purpose Register
(GPR) 0 contains what should be a valid request size
in doublewords. It (GPR0) was obtained from the
returned control block’s header record. The control
block header is addressed by AR5/GPR5. Examine
the control block header to determine why the length
is incorrect. It may be that the header has been
overlaid. If this is the case, the user of the control
block immediately in front of the control block being
returned probably caused the error.
GPR14 points to the address (in HCPVFM) where CP
detected the error.
VFM002
VDE002 VFM002
Explanation: The conditions that cause this abend to
occur are:
v The count of doublewords in use (PCTDWUSE) for
the PCTE of the control block being returned has
gone negative.
v The PCTE of the control block being returned was
not chained on the SUBBK queue and CP expected it
to be chained there.
User Response: Depending upon the reason for this
abend, take one of the following respective actions:
v At the time of the abend the PCTE is addressed by
AR9/GPR9. Examine the PCTE to determine why the
count of doublewords went negative.
v At the time of the abend the PCTE is addressed by
AR9/GPR9, and the SUBBK is addressed by
AR5/GPR5. Examine the SUBBK, PCTE, and the
PCTE queue (anchored at SUBANCH) to determine
why the queue has become damaged.
Chapter 2. System Codes 121