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

MDT003 MNI002
MDT003
Explanation: The RDEV scan initiated by
HCPMDTXM is expected to return the address of the
next RDEV, but it is returning the same RDEV or
previous RDEV with respect to the input RDEV. This
abend prevents the multiple missing interrupt recovery
task from being stacked for a single device.
User Response: Register 2 contains the input RDEV.
Verify that it is a valid RDEV. Examine the dump and
determine why the RDEV scan returned an incorrect
RDEV in R1.
MEO001
Explanation: (soft abend) HCPMEO received an
unexpected return code from the channel subsystem.
User Response: Contact your IBM support personnel.
MEP001
Explanation: (soft abend) HCPMEP received an
unexpected return code from the channel subsystem.
User Response: Contact your IBM support personnel.
MFC001
Explanation: (soft abend) While attempting to acquire
the Coupling Facility Configuration (CFC) lock to
perform a coupling configuration change, the CFC lock
was destroyed and the requested Coupling Facility
configuration change was not performed.
User Response: Examine the internal trace table and
storage dump to determine what CP task destroyed the
Coupling Facility Configuration lock and contact your
IBM support personnel.
MFH001
Explanation: (hard abend) CP was in the process of
formatting a response to a user’s console when it
detected that output buffer it was using to hold the
response has overflowed. An overlay of system storage
has occurred.
User Response: Contact your IBM support personnel.
MFJ001
Explanation: (soft abend) A data transfer was
requested to expanded storage on behalf of the
Coupling Facility (CF) Service Machine. The z/VM CF
Service Machine does not support expanded storage
data transfers.
User Response: Remove expanded storage from the
CF Service Machine virtual configuration.
76 z/VM: System Messages and Codes — CP
MFN001
Explanation: (soft abend) CP has detected an internal
error while loading a file from the processor controller
into main storage. In the dump, register 0 will contain a
unique ID of the failing code and register 1 will contain
the reason code for the failure.
A MFN001 ABEND is most likely to occur when logging
on with (X)AUTOLOG or restarting a CF Service
Machine with the RESTART MSGPROC commands.
During the start up of a CF Service Machine, the
Coupling Facility Control Code (Licensed Internal Code)
is loaded from the processor controller into the CF
Service Machine’s virtual storage. The logic within CP
that performs the load function encountered an
unexpected condition and has terminated the load
process.
User Response: Contact your IBM support personnel.
MFR001
Explanation: (hard abend) Unable to terminate an
active file load from the processor controller. CP storage
may be compromised.
User Response: Contact your IBM support personnel.
MNI001
Explanation: (soft abend) An error has been detected
by the *MONITOR CP system service in response to an
IUCV function that *MONITOR initiated.
All Monitor-related activities are terminated and the
IUCV path between any connected virtual machine, and
the *MONITOR CP System Service has been severed.
User Response: Register 1 points to the IPARML
control block. Field IPRCODE contains the return code
from IUCV indicating the nature of the problem. The
meaning of this return code can be found in z/VM: CP
Programming Services under ″IUCV functions.″ If you
cannot determine the error, contact your IBM support
personnel. The Monitor may be restarted by following
normal startup procedures.
MNI002
Explanation: (soft abend) An unexpected return code
was received from a call to either HCPNSMRN or
HCPNSMSN.
All Monitor-related activities are terminated, and the
IUCV path between any connected virtual machine and
the *MONITOR CP System Service has been severed.
User Response: Register 15 contains the return code
received. Examine the return code and determine the
problem. If you cannot determine the error, contact your
IBM support personnel. The monitor may be restarted
by following normal startup procedures.