28.12.2012 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

LDC004<br />

Explanation: (soft abend) This is an H<strong>CP</strong>LDCEF<br />

process error; guest page zero cannot be acquired. A<br />

call to H<strong>CP</strong>PZERO to acquire a specified virtual<br />

machine’s guest page zero was not successful.<br />

User Response: Determine the virtual machine<br />

executing at this time <strong>and</strong> why the virtual machine’s<br />

guest page zero could not be fetched.<br />

LDD003<br />

Explanation: (soft abend) This is an H<strong>CP</strong>LSMUU<br />

output error; invalid return code from H<strong>CP</strong>LSMUU.<br />

During logical device present processing, H<strong>CP</strong>LSMUU<br />

returned an incorrect value in R15.<br />

User Response: Examine the value in R15 (through<br />

the trace table) <strong>and</strong> determine how H<strong>CP</strong>LSMUU arrived<br />

at that value.<br />

LDD007<br />

Explanation: (soft abend) This is an H<strong>CP</strong>LSMUS<br />

output error. During logical device status processing,<br />

H<strong>CP</strong>LSMUS returned an incorrect value in R15.<br />

User Response: Examine the value in R15 (using the<br />

trace table) <strong>and</strong> determine how H<strong>CP</strong>LSMUS arrived at<br />

that value.<br />

LDD008<br />

Explanation: (soft abend) This is an LDDBK<br />

information error. Waiting for Read-Buffer <strong>and</strong> waiting<br />

for Read-modified are both set. During logical device<br />

present processing, the logical device was waiting for<br />

both a read-buffer <strong>and</strong> a read-modified (LDDWTNG).<br />

Present processing proceeded with read-buffer<br />

processing if the present was for a read-buffer; present<br />

processing proceeded with read-modified processing if<br />

the present was for a read-modified. At completion of<br />

this logical device present processing, the logical device<br />

is not waiting for a read (buffer or modified).<br />

User Response: Determine if a read-buffer or a<br />

read-modified was attempted <strong>and</strong> if it was successful<br />

(data was moved). Determine how both waiting for<br />

read-buffer <strong>and</strong> waiting for read-modified were set.<br />

Check for previous presents <strong>and</strong>/or reads to this device<br />

which may have failed.<br />

LDE002<br />

Explanation: (soft abend) The system will soft abend<br />

if H<strong>CP</strong>LSMUS returns with a return code that is not 0,<br />

as this is the only valid return code.<br />

User Response: Examine the return code given by<br />

H<strong>CP</strong>LSMUS <strong>and</strong> determine why it issued that return<br />

code.<br />

LDE017<br />

Explanation: The deferred execution counter,<br />

<strong>VM</strong>DDFRWK in the <strong>VM</strong>DBK, was about to become<br />

negative.<br />

User Response: Examine the <strong>CP</strong> trace table <strong>and</strong><br />

storage dump to see why the <strong>VM</strong>DBK pointed to by R11<br />

has a zero value for the <strong>VM</strong>DDFRWK field.<br />

See the description of DFR017 for possible reasons<br />

why this may have occurred.<br />

LDF001<br />

Explanation: Issued during a Diagnose x’2C0’ if the<br />

requested file size exceeds the caller-specified buffer<br />

size.<br />

User Response: Contact your <strong>IBM</strong> support personnel.<br />

LFC001<br />

Explanation: H<strong>CP</strong>LFCRL is called to remove a<br />

Multi-Path Lock Facility (MPLF) RPQ simulation<br />

configuration. The guest is the last user attached to the<br />

configuration. The configuration name must be removed<br />

from the configuration name table that contains a list of<br />

active configurations. However, the configuration name<br />

cannot be found in the table.<br />

User Response: This is most likely a software error.<br />

Possible causes are:<br />

v The configuration name table was corrupted.<br />

v Another process removed the configuration name<br />

without properly locking access to the table.<br />

LFP001<br />

LDC004 LFP001<br />

Explanation: Issued by the H<strong>CP</strong>LFP module. This<br />

module is distributed as object code only. Therefore, no<br />

source program materials are available.<br />

H<strong>CP</strong>LFPSF found a zero <strong>VM</strong>DBK address when<br />

attempting to identify a connected Multi-Path Lock<br />

Facility (MPLF) RPQ user.<br />

User Response: Refer to the z/<strong>VM</strong>: Diagnosis Guide<br />

for information on gathering the documentation you<br />

need to assist <strong>IBM</strong> in diagnosing the problem, then<br />

contact your <strong>IBM</strong> support personnel.<br />

This is most likely a software error. Possible causes are:<br />

v The subsystem connect table was corrupted.<br />

v Another process removed the user from the<br />

configuration without properly locking access to the<br />

user’s configuration block.<br />

Chapter 2. <strong>System</strong> <strong>Codes</strong> 71

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!