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.

PXI001 REI001<br />

been released. Possible explanations include:<br />

PSGPXICT was not incremented when an additional<br />

PXIBK was created or changed to point to the PSGBK,<br />

or the wrong PSGBK’s PSGPXICT field was<br />

decremented when a PXIBK was deleted or changed to<br />

no longer point to the PSGBK.<br />

PXI001<br />

Explanation: (SNAP dump) Inconsistent response<br />

returned by H<strong>CP</strong>PXDQG: the number of group<br />

members contained in the DGRPM chain is greater than<br />

the group-member count returned in R0.<br />

User Response: Examine the information returned<br />

from H<strong>CP</strong>PXDQG to H<strong>CP</strong>PXIQD. To isolate the source<br />

of the error, examine the trace table to determine<br />

whether H<strong>CP</strong>PXD got its information from H<strong>CP</strong>UDP (<strong>CP</strong><br />

directory) or an external security manager.<br />

PXI002<br />

Explanation: (SNAP dump) Inconsistent response<br />

returned by H<strong>CP</strong>PXDQG: the number of group<br />

members contained in the DGRPM chain is less than<br />

the group-member count returned in R0.<br />

User Response: Examine the information returned<br />

from H<strong>CP</strong>PXDQG to H<strong>CP</strong>PXIQD. To isolate the source<br />

of the error, examine the trace table to determine<br />

whether H<strong>CP</strong>PXD got its information from H<strong>CP</strong>UDP (<strong>CP</strong><br />

directory) or an external security manager.<br />

PXI003<br />

Explanation: (Soft abend) The buffer address being<br />

released is 0. This is the value in R8. It should be the<br />

address of a QPXBK or SPXBK. Diagnose 29C or 2A0<br />

completes with an error.<br />

User Response: Determine how R8 changed from a<br />

valid address to 0.<br />

PZE001<br />

Explanation: The virtual machine was not in<br />

instruction simulation wait when H<strong>CP</strong>PZE was called to<br />

locate the prefix page address of the virtual machine.<br />

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

storage dump to determine why <strong>VM</strong>DSIMWT in the<br />

<strong>VM</strong>DBK is not set before the call to H<strong>CP</strong>PZE.<br />

QDA001<br />

Explanation: (soft abend) An RDEV value is not found<br />

in R8, <strong>and</strong> a <strong>CP</strong>VOL value is not found in R4 when<br />

formatting a response to the Class B comm<strong>and</strong> QUERY<br />

DASD DRAINING.<br />

User Response: Examine the dump <strong>and</strong> determine<br />

why both registers representing RDEV <strong>and</strong> <strong>CP</strong>VOL hold<br />

zero values.<br />

94 z/<strong>VM</strong>: <strong>System</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong> — <strong>CP</strong><br />

QDL001<br />

Explanation: (soft abend) H<strong>CP</strong>QDLDG determined an<br />

error exit that was not valid, which was setup by the<br />

H<strong>CP</strong>SAC macro, was taken during a virtual disk in<br />

storage data move operation. The error exit was driven<br />

by one of the following:<br />

v A protection exception in guest storage<br />

v A virtual disk in storage space address that was not<br />

valid<br />

v An expired virtual disk in storage space I-ASIT.<br />

These errors are believed to be impossible due to move<br />

instruction usage, virtual disk in storage block address<br />

checking, <strong>and</strong> I/O serialization.<br />

User Response: R15 contains the return code that<br />

H<strong>CP</strong>QDLDG will present to its caller. The dump snap<br />

data contains the TSKBK control block that describes in<br />

detail the error that occurred. Examine the <strong>CP</strong> trace<br />

table, the TSKBK, module entry point H<strong>CP</strong>QDLDG, <strong>and</strong><br />

its callers to determine the cause of the failure.<br />

QPR001<br />

Explanation: (soft abend) The PFXTYPE field does<br />

not contain a valid type code. This abend occurred<br />

during the execution of the QUERY PROCESSORS<br />

comm<strong>and</strong>. The PFXTYPE field indicates what the real<br />

processing unit is being used for in the system.<br />

User Response: Examine the dump <strong>and</strong> determine<br />

why there is incorrect information in the PFXTYPE field.<br />

QUE001<br />

Explanation: (soft abend) Occurs when H<strong>CP</strong>QUEEP<br />

finds a queue that is currently in End Processing state<br />

that has already ended processing.<br />

User Response: End Processing completes for the<br />

queue <strong>and</strong> ISFC processing continues.<br />

REI001<br />

Explanation: (soft abend) H<strong>CP</strong>REIPB or H<strong>CP</strong>REIPQ<br />

(which fills in the protect block (H<strong>CP</strong>PROBK) with error<br />

information when the user is in the protected application<br />

environment) was called with a message number that<br />

the protected application environment does not support.<br />

User Response: Check the trace table to determine<br />

what module called H<strong>CP</strong>REI. If H<strong>CP</strong>REIPB was called,<br />

the erroneous message number is in input register 0. If<br />

H<strong>CP</strong>REIPQ was called, input register 3 points to a<br />

parameter list <strong>and</strong> the message number is in the first<br />

word of the parameter list. See the description of<br />

DIAGNOSE code x’B0’ in z/<strong>VM</strong>: <strong>CP</strong> Programming<br />

Services for a list of message numbers recognized in<br />

the protected application environment. Save the dump<br />

<strong>and</strong> contact your <strong>IBM</strong> support personnel for software<br />

support.

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

Saved successfully!

Ooh no, something went wrong!