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.

MPC002<br />

Explanation: This module is distributed as object code<br />

only. Therefore, no source program materials are<br />

available.<br />

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

information on gathering the documentation you need to<br />

assist <strong>IBM</strong> in diagnosing the problem, then contact your<br />

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

MPD001<br />

Explanation: (soft abend) A defer type was<br />

encountered that was not valid while stacking MP defer<br />

work.<br />

User Response: Examine the dump. Register 13<br />

points to the SAVBK. Determine why register 0 in the<br />

SAVBK did not point to either the address of<br />

MPD<strong>CP</strong>LOC (“<strong>CP</strong> loss of control” queue) or the address<br />

of MPDLOC (“loss of control” queue). Use the <strong>CP</strong> trace<br />

table to determine which module caused the error.<br />

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

MPF001<br />

Explanation: During the switch master routine<br />

(H<strong>CP</strong>MPFSW), <strong>CP</strong> could not locate the current master<br />

processor prefix page. The system cannot operate<br />

without a master, therefore the system must be<br />

terminated.<br />

User Response: Examine the dump to determine<br />

what happened to the master processor prefix page.<br />

Pay particular attention to any function that may have<br />

manipulated the prefix page cyclic list. Also, examine all<br />

the prefix pages to determine if the PFXTYPE field has<br />

been disturbed inadvertently (this would prevent the<br />

system from identifying which prefix page belonged to<br />

the master processor).<br />

MPR001<br />

Explanation: A processor was selected for recovery<br />

from a malfunction alert, but <strong>CP</strong> could not find the prefix<br />

page that owns the logical processing unit address<br />

(L<strong>CP</strong>UA) of the failing processor. The maintenance of<br />

the PFXMALFM or SYSMALFM field is in error.<br />

User Response: Study the dump to determine what<br />

happened to the prefix page of the processor that<br />

signalled malfunction alert. Module H<strong>CP</strong>MPS is<br />

responsible for maintaining the two fields; module<br />

H<strong>CP</strong>MPR is responsible for assuring that recovery is<br />

performed by only one processor in the configuration,<br />

even though the malfunction alert is broadcast to all<br />

processors.<br />

MPR002<br />

Explanation: The processor that broadcast a<br />

malfunction alert was the master processor, but this<br />

processor (the recovery processor) was unable to<br />

become the master for some reason (condition code 1<br />

returned from a call to H<strong>CP</strong>MPFSW). This processor<br />

should be the only one that has the authority to recover<br />

for the failed master processor. If the recovery<br />

processor cannot take over for the failed master<br />

processor, this means there is no master processor. The<br />

system cannot operate without a master processor, so<br />

the system terminates.<br />

User Response: Study the dump to determine why<br />

the switch master function failed.<br />

MPS001<br />

Explanation: In attempting to VARY ON a processor,<br />

H<strong>CP</strong>MPSON has run out of logical processing unit<br />

addresses (L<strong>CP</strong>UAs) to assign to the new processor.<br />

The L<strong>CP</strong>UA is a 4-byte field with a distinct bit for each<br />

online processor in the configuration. There are 31 bits<br />

available to be assigned. Therefore, if there are no<br />

more L<strong>CP</strong>UAs to assign, the manipulation of the field is<br />

in error.<br />

User Response: The most likely function to mish<strong>and</strong>le<br />

the L<strong>CP</strong>UA field is the VARY OFFLINE/ONLINE<br />

PROCESSOR xx comm<strong>and</strong>. The map of all used<br />

L<strong>CP</strong>UAs is in the SYSL<strong>CP</strong>UA field of the system<br />

common area. There should be a prefix page for each<br />

L<strong>CP</strong>UA mapped in SYSL<strong>CP</strong>UA. H<strong>CP</strong>MPS is the module<br />

that assigns <strong>and</strong> deallocates L<strong>CP</strong>UAs when a processor<br />

is varied online or offline respectively.<br />

MPX001<br />

Explanation: <strong>CP</strong> was performing CCW simulation for<br />

a virtual adapter but could not obtain the required<br />

serialization for the MPC Group. This indicates that the<br />

simulation is in an unexpected internal state.<br />

User Response: Restart the system <strong>and</strong> process the<br />

dump.<br />

MXA001<br />

MPC002 MXA001<br />

Explanation: (soft abend) An error has been detected<br />

by the *MONITOR <strong>CP</strong> system service in response to an<br />

IUCV function that *MONITOR initiated.<br />

All Monitor-related activities are terminated, <strong>and</strong> the<br />

IUCV path between the receiving virtual machine <strong>and</strong><br />

the *MONITOR <strong>CP</strong> <strong>System</strong> Service has been severed.<br />

User Response: Register 1 points to the IPARML<br />

control block. Field IPRCODE contains the return code<br />

from IUCV indicating the nature of the problem. The<br />

meaning of this return code can be found in z/<strong>VM</strong>: <strong>CP</strong><br />

Programming Services under ″IUCV functions.″ If you<br />

cannot determine the error, contact your <strong>IBM</strong> support<br />

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

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

Saved successfully!

Ooh no, something went wrong!