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

PTF001 PTF010
PTF001
Explanation: While locking a frame, the lock function
attempted to take a frame from a user-owned frame list
and determined that the frames on the list were chained
improperly, or it found that the FRMOWNED flag was
off, even though the frame was not yet locked.
User Response: Inspect the process of chaining and
unchaining frames from the user-owned frame list.
Examine the dump and determine which VMDBK owns
this user-owned frame list. VMDFR1ST should point to
the first frame on the list, and VMDFRLST should point
to the last frame on the list. The frame being unchained
at the time of the ABEND may not have been chained
properly when placed on the user-owned frame list.
Another possibility is that the FRMOWNED flag is not
on in the frame table entry. This could indicate that the
frame is on the user-owned frame list by error, and may
not belong to this VMDBK at all. Examine R2 for the
correct input parameters. Examine the field FRMPTE
(R1 points to the FRMPTE). Trace back through
program execution to determine which module was
called with the incorrect input.
PTF003
Explanation: CP cannot lock the frame specified by
R2 because the frame does not contain the last
translated page for the processor on which the lock
request is issued.
User Response: Examine the dump to determine
which module attempted to lock the frame without first
translating the associated page.
PTF004
Explanation: While unlocking a frame, the unlock
function attempted to put a frame on a user-owned
frame list and determined that the frames on the list
were chained improperly.
User Response: Inspect the process of chaining and
unchaining frames from the user-owned frame list.
Examine the dump and determine which VMDBK owns
this user-owned frame list. VMDFR1ST should point to
the first frame on the list, and VMDFRLST should point
to the last frame on the list. The frames between which
this frame was being added may not have been chained
properly when they were put on the user-owned frame
list.
PTF005
Explanation: The frame address specified by R2 was
not valid and was not within addressable storage.
User Response: Examine the dump. Trace back
through system execution to the point where generation
of the erroneous address occurred and determine the
cause of the erroneous address.
92 z/VM: System Messages and Codes — CP
PTF006
Explanation: CP cannot return the frame specified by
R2 to the available list because, in its FRMTE, the
FRMPTE was pointing to a PAGTE that is still valid and
still pointed to this frame.
User Response: Examine the dump to determine
which module attempted to return the frame. Examine
the code to determine why validation of the PAGTE did
not take place.
PTF007
Explanation: While locking or unlocking a frame, the
function attempted to change the ASCCTPLK,
ASCIACCT, or ASCRACCT count for an address space.
However,
v Increasing the count would have made it wrap to zero
v Or decreasing the count would have made it
negative.
User Response: Inspect the process of page
translation and of locking and unlocking frames.
Examine the dump and determine when the count was
last changed. Check for improper operations on the
locked page count or alteration of the ASCBK. Check
for routines that lock using one internal ASIT and unlock
using another internal ASIT.
PTF009
Explanation: CP cannot unlock the frame specified by
R2. The contents of that frame’s frame table entry
(FRMTE) are such that the frame cannot be unlocked.
Examine the dump for the following conditions:
v The page frame was not locked to begin with. This
would occur if the FRMLOCKD bit was 0 and the
frame was chained on the virtual machine’s
user-owned frame list.
v The frame lock count was already zero, but the frame
was still locked.
User Response: Determine which of the above
conditions caused the abend. Inspect the code to see
which module or entry point was responsible for locking
the frame and why the frame was left unlocked. Inspect
the code and the trace table to determine why the frame
lock count is incorrect.
PTF010
Explanation: While adding a frame to the available list
or taking a frame from the available list, CP determined
that the frames on the list were chained improperly.
Otherwise, the count of available frames became
negative.
User Response: Inspect the process of chaining and
unchaining frames on the available list. Examine the
dump for previous manipulations of the available list to
see when and where the error occurred. Then