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.

H<strong>CP</strong>6186I H<strong>CP</strong>6207E<br />

message <strong>and</strong> the TRSOURCE comm<strong>and</strong>s that produce<br />

this error message.<br />

H<strong>CP</strong>6186I {Range xxxxxxxx-xxxxxxxx of | DCSS or<br />

DSS associated with} ASIT asit,<br />

spaceid spaceid was previously<br />

dumped; it will not be dumped again.<br />

Explanation: The storage was dumped by a previous<br />

<strong>VM</strong>DUMP comm<strong>and</strong> in continuous mode.<br />

<strong>System</strong> Action: Comm<strong>and</strong> processing continues. The<br />

specified storage is not dumped a second time.<br />

User Response: If you specified the range incorrectly,<br />

enter another <strong>VM</strong>DUMP comm<strong>and</strong> with the intended<br />

range.<br />

H<strong>CP</strong>6187E A soft abend occurred during <strong>VM</strong>DUMP<br />

processing.<br />

Explanation: A soft abend occurred some time during<br />

<strong>VM</strong>DUMP processing. The <strong>VM</strong>DUMP file has been<br />

purged. Refer to the soft abend dump for information<br />

about why the failure occurred.<br />

<strong>System</strong> Action: After the soft abend, the system<br />

attempts to recover all resources allocated for <strong>VM</strong>DUMP<br />

processing <strong>and</strong> attempts to destroy the <strong>VM</strong>DUMP file. A<br />

soft abend dump is created to aid in problem<br />

determination.<br />

User Response: Examine the soft abend dump to<br />

determine the cause of the error. Contact your system<br />

support personnel to correct the problem.<br />

H<strong>CP</strong>6189I <strong>VM</strong>DUMP comm<strong>and</strong> is unable to add<br />

more data to the current virtual<br />

machine dump.<br />

Explanation: This <strong>VM</strong>DUMP comm<strong>and</strong> or DIAGNOSE<br />

code X'94' cannot be added to the current <strong>VM</strong>DUMP file<br />

because:<br />

v Either you have requested dumps from more than<br />

200 different address spaces<br />

v Or you have requested dumps from a particular<br />

address space more than 900 times.<br />

<strong>System</strong> Action: Comm<strong>and</strong> processing continues.<br />

User Response: Close the current <strong>VM</strong>DUMP file <strong>and</strong><br />

open another one. If you received this message for the<br />

second reason, specify more than one address range<br />

on each <strong>VM</strong>DUMP or DIAGNOSE code X'94' request.<br />

H<strong>CP</strong>6190E <strong>VM</strong>DUMP processing is unable to<br />

complete due to a paging error.<br />

Explanation: A paging error has occurred on a virtual<br />

page containing virtual machine dump information.<br />

<strong>System</strong> Action: The system closes the virtual<br />

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

machine dump file. Comm<strong>and</strong> processing ends; system<br />

operation continues.<br />

User Response: None.<br />

H<strong>CP</strong>6191I Storage range xxxxxxxx-xxxxxxxx is<br />

unaddressable <strong>and</strong> will not be dumped.<br />

Explanation: The range specified is above guest<br />

storage <strong>and</strong> does not fall within a discontiguous saved<br />

segment.<br />

<strong>System</strong> Action: Comm<strong>and</strong> processing continues. The<br />

unaddressable range is not dumped.<br />

User Response: If you specified the range incorrectly,<br />

enter another <strong>VM</strong>DUMP comm<strong>and</strong> with the intended<br />

range.<br />

H<strong>CP</strong>6202E The {spool|temporary disk|directory}<br />

cylinders were ignored on system<br />

volume volid.<br />

Explanation: A volume attached to the system<br />

contains space allocated as a type not supported for<br />

that device type. The variables in this message are as<br />

follows:<br />

type The allocation type specified in the allocation<br />

map. It will be DIRECTORY, SPOOL, or<br />

TEMPORARY DISK. PERM <strong>and</strong> PAGE are the<br />

only types recognized on these devices.<br />

volid The <strong>CP</strong> volume label of the DASD on which<br />

<strong>CP</strong> detected the unsupported space.<br />

The system will only accept 3350s connected to the<br />

3880 caching control unit Models 11 or 21 for PAGE or<br />

PERM space.<br />

<strong>System</strong> Action: The system ignores other types of<br />

space allocated on these device types. The copy of the<br />

allocation map maintained by <strong>CP</strong> will show space<br />

allocated as “type” (other than PAGE <strong>and</strong> PERM)<br />

translated to PERM. The allocation map on the DASD<br />

itself remains unchanged.<br />

Operator Response: No immediate action is required.<br />

However, system support personnel should determine<br />

whether to change the cylinder allocation of the DASD.<br />

H<strong>CP</strong>6207E I/O ERROR; DISK vdev HAS<br />

UNSOLICITED STATUS PENDING<br />

Explanation: The SALIPL comm<strong>and</strong> processor<br />

encountered an I/O error indicating that the specified<br />

device has unsolicited status pending.<br />

<strong>System</strong> Action: The comm<strong>and</strong> is not executed.<br />

<strong>System</strong> operation continues.<br />

User Response: Enter the SALIPL comm<strong>and</strong> again. If<br />

the error persists, contact your system support<br />

personnel.

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

Saved successfully!

Ooh no, something went wrong!