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

HCPDUNDX pointer fields are not pointing to the exact
beginning of the HCPDVMD or HCPDDEV block. If the
directory page that was read appears to be incorrect,
either the page is not a directory page, or the page has
been altered on the DASD device.
User Response:
1. Ensure that DIRECTXA is at the same service level
as the CP nucleus that is installed and then issue
DIRECTXA to install a new CP directory.
2. Examine the HCPDUNDX pointer fields to ensure
that they contain a valid address of a directory page.
Issue the DDRXA command to examine the entire
CP directory, and issue the DIRECTXA command to
correct the incorrect CP directory.
UDS001
Explanation: (soft abend) The number of DCPU
blocks for this user as specified in DVMDCPUC does
not match the number of DCPU blocks for this user as
chained together in the directory.
User Response: Ensure that the DIRECTXA module
is at the same service level as the CP nucleus and then
issue the DIRECTXA command to create a new
directory.
UDU001
Explanation: (soft abend) Module HCPUDU detected
that it did not read a valid HCPDDEV from the CP
directory. If the directory page that was read appears to
be correct, it is likely that the HCPDUNDX pointer fields
are not pointing to the exact beginning of HCPDDEV
block. If the directory page that was read appears to be
incorrect, either the page is not a directory page or the
page has been altered on the DASD device.
User Response: Examine the HCPDUNDX pointer
fields to ensure that they contain a valid address of a
directory page. Issue the DDRXA command to examine
the entire CP directory, and the DIRECTXA command to
correct the incorrect CP directory.
UIM001
Explanation: The PGMBK’s count of shared users
(PGMSNTCT) is less than zero.
User Response: R2 points to the STLBK. R8 points to
the PGMBK that has a negative PGMSNTCT count. The
PGMVM field points to the VMDBK or SNTBK control
block that owns the PGMBK. R15 points to the place
that detected the need for taking the abend.
UIM002
Explanation: HCPUIMSL cannot release all the
storage for this segment, because non-shared storage
is connected to a shared PGMBK. Only shared storage
should be associated with a shared PGMBK.
User Response: Examine the contents of the dump.
R8 points to the PGMBK. At least one of the page
status table entries (PGSTEs) in the PGMBK is not
marked PGSSHARE. The PGMVM field contains the
owner of this PGMBK, and it should describe an
SNTBK. R15 points to the place that detected the need
for taking the abend.
UIM003
Explanation: An HCPUIM entry point received
incorrect parameters, and one of the following has
occurred:
v The HCPUIMPA routine was called to release storage
for the system address space.
v In the HCPUIMSC routine R0 and R1 contain an
incorrect address range.
v In the HCPUIMSN routine R0 and R1 contain an
incorrect address range, or the system VMDBK was
passed in R11.
User Response: R15 points to the place that detected
the need for taking the abend.
v If the HCPUIMPA routine issued the abend,
determine if the VMDBK in R11 is the system
VMDBK (PFXSYSVM). Find the caller of HCPUIMPA
and determine why the caller passed the system
VMDBK.
v If the HCPUIMSC routine issued the abend, the input
range in R0 and R1 is incorrect. Determine which
range value fails the test:
0
< = R0 < = R1.
v If the HCPUIMSN routine issued the abend, either
R11 equals PFXSYSVM, or the range in R0 and R1
is incorrect. Determine why the system VMDBK was
passed or which range value fails the test:
0