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

It is possible for the second processor to run the
code that releases the lock and decrements
VMDCTCRT before the first processor increments
VMDCTCRT. VMDCTCRT must always be
incremented before another processor can start
processing the code that will do the corresponding
decrement.
v VMDCTCRT was incremented on one VMDBK, then
a VMDBK switch occurred before the corresponding
decrement took place. This may often happen on
task threads that switch between a user VMDBK and
the system VMDBK, or switch between VMDBKs in a
single virtual MP complex.
v A task thread did not properly serialize its
incrementing or decrementing of VMDCTCRT, such
as by using the compare-and-swap instruction.
v When attempting to increment VMDCTCRT on other
than the running VMDBK, the wrong VMDBK was
chosen.
User Response: Examine the CP trace table and
storage dump and try to determine why the base
VMDBK changed from zero to a negative value in the
VMDCTCRT field. R11 points to the dispatched VMDBK.
The field VMDBASE in the dispatched VMDBK points to
the VMDBK containing VMDCTCRT. Contact your IBM
support personnel.
LOC017
Explanation: The deferred execution counter,
VMDDFRWK in the VMDBK, was about to become
negative.
User Response: Examine the CP trace table and
storage dump to see why the VMDBK pointed to by R11
has a zero value for the VMDDFRWK field.
See the description of DFR017 for possible reasons
why this may have occurred.
LOG001
Explanation: (soft abend) During LOGON processing,
CP attempted to rename a skeleton VMDBK’s user ID in
the VMDBK hash table to the name of the user ID that
is logging on and the skeleton VMDBK’s user ID did not
exist in the VMDBK hash table. CP will attempt to
recover by inserting the name of the user ID that is
logging on into the VMDBK hash table.
User Response: There is probably a software
problem. Contact your IBM support personnel to
diagnose and correct the problem.
LOG002
Explanation: CP attempted to rename a skeleton
VMDBK’s user ID in the VMDBK hash table to the
system operator’s user ID. The rename failed because
LOGON processing of the system operator at system
initialization occurred when either the NODIRECT option
was specified or no valid system directory existed.
User Response: There is probably a software
problem. Contact your IBM support personnel to
diagnose and correct the problem.
LTR001
Explanation: While processing the Frame
Last-Translated Count (FRMLTRCT) for a frame table
entry (FRMTE), the function attempted to decrement or
zero the FRMLTRCT count value. However, one of the
following occurred:
v The count was found to already be negative.
v The function was decrementing the count, which
would have made it negative.
v The function was zeroing the count, which would
have caused it to become negative later.
User Response: Inspect the page translation and
frame table available list processing code. Examine the
dump to determine when the count was last changed,
and why the count was being decremented or zeroed
incorrectly.
LTR002
Explanation: The last-translated count for a frame
exceeds the maximum value allowed.
User Response: Contact your IBM support personnel.
LTR003
Explanation: Translation processing found the
FRMLTRCT of the FRMTE for the translated frame to
be already at or above the allowable maximum value
(FRMLTRMX) during a FRMLTRCT increment attempt,
even though FRMTRANS has been held continuously
since FRMLTRCT was last seen to be below
FRMLTRMX.
User Response: Refer to the z/VM: Diagnosis Guide
for information on gathering the documentation you
need to assist IBM in diagnosing the problem, then
contact your IBM support personnel.
MCH001
LOC017 MCH001
Explanation: Control was passed to HCPMCHCS (the
check-stop handler). HCPMCHCS expected R1 to
contain the address of the prefix page of the
check-stopped processor, but the address was not valid.
User Response: Examine the storage dump and
determine how the incorrect address got to be in R1.
Chapter 2. System Codes 73