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

LCK006
Explanation: The count of requests enqueued and
waiting to obtain a lock (or LKWRD, DESCRIBED BY
HCPLKWRD COPY) would have exceeded the
maximum.
User Response: Examine the dump and the trace
table and try to determine why the count would have
exceeded the maximum. Register R4 point to the
LKWRD and LKWDQLEN is the count field within the
LKWRD. Contact your IBM support personnel.
LCK007
Explanation: A request was made to obtain a
VMDPTIL lock in shared mode for a ″bump″ share, but
the prerequisite dispatch share of the VMDPTIL
lockword was not held.
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.
LCK008
Explanation: A request was made to release a
VMDPTIL lock in shared mode for a ″bump″ share, but
either the lock is not held in shared mode at all, or none
of the shares held are bump shares.
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.
LCK009
Explanation: A request to obtain a host share of the
IPTE interlock has timed out.
User Response: Examine the dump and the trace
table and try to determine why the request timed out.
Register 4 points to the IPTE-interlock doubleword.
Contact your IBM support personnel.
LCK010
Explanation: An attempt to release a host share of
the IPTE interlock failed for one of the following
reasons:
v The lock was not held.
v The lock was not held by the host.
User Response: Examine the dump and the trace
table and try to determine what happened. Register 4
points to the IPTE-interlock doubleword. Bit 0 indicates
whether the lock is held or not. Bits 1–31 contain the
host share count. Bits 32–63 contain the guest share
count. Contact your IBM support personnel.
LCK011
Explanation: The IPTE interlock was found to be in an
incorrect state. The lock may be invalid for one of the
following reasons:
v The lock was not held, but the host and/or guest
share count was non-zero.
v The lock was held and both the host and guest share
count were non-zero.
User Response: Examine the dump and try to
determine how the incorrect value was stored in the
IPTE-interlock doubleword pointed to by Register 4. Bit
0 indicates whether the lock is held or not. Bits 1–31
contain the host share count. Bits 32–63 contain the
guest share count. Contact your IBM support personnel.
LCK012
Explanation: A request to obtain a host share of the
IPTE interlock exceeded the maximum.
User Response: Examine the dump and the trace
table and try to determine why the count exceeded the
maximum. Register 4 points to the IPTE-interlock
doubleword. Contact your IBM support personnel.
LCK017
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 in R11 has a zero
value for the VMDDFRWK field.
See the description of DFR017 for possible reasons
why this may have occurred.
LDA001
Explanation: (soft abend) CP is unable to return the
LDDBK; HCPLDARE input error. At least one of the
following was specified incorrectly:
v The LDDBK had an incorrect value in the
LDDLDNUM field
LCK006 LDA001
v The specified logical device (LDDLDNUM) does not
exist
v The LDDBK passed on input is not the LDDBK that is
in the logical display device data structure
(HVMTABLE-located in module HCPLDA).
User Response: R1 points to the LDDBK passed on
input. Determine the condition that caused the abend.
(See ″Explanation″ for a list of conditions.) Locate the
caller of HCPLDARE and determine how this condition
occurred. Check to make sure the preceding call to
HCPLDAFE was successful (a return code of zero in
R15) for this device, or that two successive calls to
HCPLDARE for the same device were not made.
Chapter 2. System Codes 69