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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

VAT003<br />

Explanation: (soft abend) Dynamic Address<br />

Translation (DAT) does not exist in XC mode virtual<br />

machines.<br />

User Response: Examine the dump to see if<br />

<strong>VM</strong>DPSW in the <strong>VM</strong>DBK of the failing user to see if<br />

PSWTRAN is set incorrectly.<br />

VCB001<br />

Explanation: A VCB code passed to the verifiable<br />

control block free storage manager was not valid<br />

(detected on obtain function only).<br />

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

VCB002<br />

Explanation: The address passed to the verifiable<br />

control block free storage manager was not valid<br />

(detected on release function only) because of one of<br />

these reasons:<br />

v The block address exceeds real machine storage<br />

size.<br />

v The block is not contained in a verifiable control block<br />

free storage frame.<br />

v The address of the block is not properly aligned.<br />

v The block already resides on a verifiable control<br />

block free storage available block list.<br />

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

VCB003<br />

Explanation: Verifiable control block free storage<br />

internal damage occurred (detected on release function<br />

only) because of one of these reasons:<br />

v The FRMTE was damaged; the VCB code in the<br />

FRMTE was destroyed.<br />

v The FRMTE should be on the SUBBK FRMTE list,<br />

but it is not.<br />

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

VCH001<br />

Explanation: (soft abend) A nonzero return code was<br />

received from H<strong>CP</strong>PTTMT. An internal programming<br />

error caused H<strong>CP</strong>VCH to pass data in the PTTBK to<br />

H<strong>CP</strong>PTTMT. That module rejected the data as incorrect.<br />

User Response: Examine the SNAPDATA in the soft<br />

abend. The SNAPDATA parameter list contains the<br />

address of the H<strong>CP</strong>PTTBK that was passed to<br />

H<strong>CP</strong>PTTMT. It also contains the address of the DSLBK<br />

that H<strong>CP</strong>VCH was processing when it called<br />

H<strong>CP</strong>PTTBK. When you obtain this information, contact<br />

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

VCR001<br />

Explanation: H<strong>CP</strong>VCR issues this abend if the<br />

console task chain (RDEVCON) has been corrupted<br />

after translating a read for a SNA CCS TTY user.<br />

User Response: A trace table entry (code x’160C’)<br />

has been written that lists the <strong>VM</strong>DBK executing at the<br />

time of the ABEND. R1 contains the address of the<br />

head of the console task chain (RDEVCON). R6<br />

contains the address of the console task (COMBK) that<br />

was built to initiate a read. If the read had not<br />

completed successfully, R1 <strong>and</strong> R6 would be equal. If<br />

the read had completed successfully, the COMCNTL bit<br />

would have been set in the console task pointed to by<br />

R1. Since neither of these conditions are true, the head<br />

of the console task chain has been corrupted. Examine<br />

the storage pointed to by R1 <strong>and</strong> ensure this is a valid<br />

COMBK address. Examine the contents of these<br />

registers <strong>and</strong> the information contained in the trace<br />

table entry to determine why the console task chain has<br />

been corrupted.<br />

VCS001<br />

Explanation: H<strong>CP</strong>VCS issues this abend if the<br />

console task (COMBK) address it is processing does<br />

not represent a write operation for a SNA CCS TTY<br />

user.<br />

User Response: R5 contains the address of the<br />

console task that was found to not be a console write.<br />

R8 contains the RDEV address for the console that is to<br />

be written to. Examine these registers to determine<br />

what type of console task was being processed.<br />

VCS002<br />

Explanation: H<strong>CP</strong>VCS issues this abend if there are<br />

more than two console read tasks active or queued for<br />

a SNA CCS TTY user.<br />

User Response: R8 contains the address of the<br />

RDEV for the SNA CCS TTY console. The RDEV in turn<br />

points to the address of the SNABK that also represents<br />

the console. Examine the SNABK to determine what<br />

reads were queued. A maximum of two reads should<br />

exist; one representing a <strong>CP</strong> read <strong>and</strong> the other<br />

representing a virtual machine read.<br />

VCX001<br />

VAT003 VCX001<br />

Explanation: (soft abend) H<strong>CP</strong>VCX issues this abend<br />

if an inter-user communication vehicle (IUCV) path for<br />

SNA console communication services (SNA CCS) is<br />

found to be incorrect. A path is found to be incorrect if<br />

H<strong>CP</strong>VCX receives a IUCV return code indicating an<br />

incorrect IUCV path ID when issuing an IUCV function<br />

specifying this path.<br />

User Response: R1 contains the address of the<br />

IPARML/IXBLK. The return code is contained in the<br />

IPRCODE field of the IPARML. The path ID of the<br />

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

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

Saved successfully!

Ooh no, something went wrong!