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

determine the reason for the error by examining the
code for the module that caused the error.
PTF011
Explanation: An attempt to lock the frame specified by
R2 did not take place because the frame was either
offline or on the available list at the time of the lock
attempt.
User Response: Examine the dump to determine
which module attempted to lock the frame. Trace
through CP execution to see why and where the frame
had gone offline or on the available list.
PTF012
Explanation: The total count of locked pages for all
private spaces owned by the user has gone negative.
This value should never be less than zero.
User Response: Contact your IBM support personnel.
PTF013
Explanation: While locking or unlocking the frame
specified in R2, CP determined that the internal ASIT is
invalid. (The internal ASIT describes the space that the
frame belongs to.)
User Response: Examine the dump to determine
which module invoked HCPPTF. Examine the caller to
see why the internal ASIT is invalid. The same internal
ASIT that was used to translate the page should be
used to lock the frame, and then to unlock it. Once
translated, the internal ASIT is supposed to remain
certified and valid until a loss of control.
PTF020
Explanation: An attempt was made to lock or unlock a
frame that is part of the resident CP nucleus.
User Response: Examine the dump and determine
which module used the HCPTRANS macro to call
HCPPTF. If HCPTRANS is in an IBM-supplied CP
nucleus routine, contact your IBM support personnel. If
HCPTRANS is in a vendor-supplied routine, notify the
vendor of the problem.
Starting in z/VM V5R1, the entire CP nucleus is
resident. Previously, part of the CP nucleus was
pageable, and it was necessary to use HCPTRANS to
lock an address before using it. This is no longer
necessary.
PTZ001
Explanation: (soft abend) HCPPTZMS is called to
issue a message or a soft abend, but the number
passed to it is not 410.
User Response: Examine the caller. The only
message number that entry points HCPPTRAN,
HCPPTRAB and HCPPTRHA pass to their callers in
R15 is 410. This is the only message number that
should subsequently be passed to the HCPPTZMS
entry point.
PTZ002
Explanation: (soft abend) HCPPTZMS is called to
issue a message to a guest, but the system VMDBK is
passed. A message cannot be issued to the system.
User Response: Examine the caller. The system
VMDBK should not have been passed to this routine.
PXC001
Explanation: (SNAP dump) On return from
HCPPIDDL, the PID count (VMDPIDCT) is about to
become negative.
User Response: Examine the PID count for the base
VMDBK pointed to by R11. Look at the chain of PXIBKs
that is anchored in the base VMDBK pointed to by R11.
Look in the trace table at the most recent call to and
return from HCPPIDDL and any other PXIBK and PID
manager activity for this virtual configuration.
PXC002
Explanation: (SNAP dump) There is a PXIBK
structure error. Possible problems include the following:
there are no PXIBKs when there should be, the last
PXIBK is not the creation PXIBK, or the PXIBK being
searched for is not on the chain when it should be.
User Response: Examine R9 to determine where the
error has been detected. Determine which reason the
ABEND is being issued for, and why. Review the trace
table to determine what led up to the failure.
PXC003
Explanation: (SNAP dump) On return from
HCPPIDDL, the PID count (VMDPIDCT) is not zero
(and it should be).
User Response: Examine the PID count for the base
VMDBK pointed to by R11. The count is not 0 when it
must be. Look in the trace table at the most recent call
to and return from HCPPIDDL and any other PXIBK and
PID manager activity for this virtual configuration.
PXC004
PTF011 PXC004
Explanation: (SNAP dump) The PSGPXICT field of a
PSGBK was about to become negative.
User Response: Examine the PXIBK chain (anchored
in the VMDPXIBK field of the base VMDBK) to
determine how many PXIBKs’ PXIPSGBK field point to
the PSGBK. Examine the trace table to determine if
other PXIBKs that pointed to this PSGBK have recently
Chapter 2. System Codes 93