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>1917E H<strong>CP</strong>1999E<br />

<strong>System</strong> Action: The file is not dumped, <strong>and</strong> comm<strong>and</strong><br />

processing continues.<br />

Note: This message is written in the SPXTAPE<br />

comm<strong>and</strong> summary log only; it is not displayed.<br />

The SET IMSG comm<strong>and</strong> has no effect on the<br />

issuing of this message.<br />

User Response: If it is important for the specified file<br />

to be dumped, you must determine the reason why it<br />

was not dumped. If possible, correct the condition. Then<br />

enter the SPXTAPE DUMP comm<strong>and</strong> with the<br />

appropriate file selection criteria. Many of these<br />

conditions can be avoided if you use SPXTAPE DUMP<br />

when all or most other users are not logged on.<br />

v If the file was open, you must contact the owner of<br />

the file to close it. This is often a temporary condition,<br />

<strong>and</strong> the file may be already closed by the time you<br />

check. However, open console files fall into this<br />

category, <strong>and</strong> these files will not close unless the<br />

owner logs off or stops spooling the console.<br />

v If the file was in use, either it will be out of that status<br />

by the time you check or you will have to contact the<br />

owner of the file to close it.<br />

v If the file is a class W system trace file, have the<br />

owner use the TRSAVE comm<strong>and</strong> to turn off the<br />

tracing.<br />

v If the file is a secure saved segment, you are not<br />

authorized to dump the file. Only the user who<br />

created the file can dump it.<br />

v If the security authorization for the file failed, you do<br />

not have the security authorization required to dump<br />

the file. You must either obtain the necessary<br />

authorization or have someone who has the<br />

authorization dump the file.<br />

v If the file was locked on another system in the CSE<br />

complex, it cannot be dumped.<br />

H<strong>CP</strong>1917E Tape device(s) {rdev[-rdev]|vdev[-vdev]}<br />

attached MULTIUSER.<br />

Explanation: The comm<strong>and</strong> entered cannot operate<br />

on a tape drive attached MULTIUSER.<br />

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

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

User Response: Use the <strong>CP</strong> QUERY TAPES<br />

comm<strong>and</strong> to determine which tape devices specified on<br />

the original comm<strong>and</strong> are attached MULTIUSER. Use<br />

the <strong>CP</strong> DETACH comm<strong>and</strong> to detach the tape devices<br />

attached MULTIUSER. If necessary, use the <strong>CP</strong><br />

ATTACH comm<strong>and</strong> (without the MULTIUSER option) to<br />

reattach the tape devices. Then reenter the original<br />

comm<strong>and</strong> that failed.<br />

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

H<strong>CP</strong>1920E Minidisk cache not enabled for system.<br />

Explanation: The minidisk cache is not in use for this<br />

system. The minidisk cache must be set on (enabled)<br />

for the system in order to change or query cache<br />

settings for a real device, for a minidisk, or for a user<br />

ID.<br />

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

User Response: Enable the system for minidisk<br />

caching <strong>and</strong> enter the comm<strong>and</strong> again.<br />

H<strong>CP</strong>1921E Cache settings could not be<br />

{changed|queried} for {rdev code<br />

cc|userid vdev code cc|rdev-rdev| userid<br />

vdev-vdev|system code cc}<br />

Explanation: An error occurred that prevented the<br />

SET MDCACHE or QUERY MDCACHE comm<strong>and</strong> from<br />

being processed. If a code is not specified in the<br />

message, then the comm<strong>and</strong> could not be performed on<br />

any of the specified devices in the requested range. The<br />

specific error could be different for each of the devices<br />

in the range, but will be one of the reasons listed below<br />

for each device. The variables in this message are as<br />

follows:<br />

rdev The real device specified in the comm<strong>and</strong><br />

userid vdev<br />

The user ID <strong>and</strong> virtual device specified in the<br />

comm<strong>and</strong><br />

cc A code indicating the specific error that<br />

occurred:<br />

4 Specified device is not attached to the<br />

system or not a cacheable device<br />

type.<br />

8 Specified device does not exist.<br />

12 Information could not be obtained<br />

from the directory.<br />

16 Specified user ID is not in the<br />

directory.<br />

20 Not enough system storage available<br />

to initialize the cache.<br />

24 The minidisk is on an FBA device <strong>and</strong><br />

either does not start on or does not<br />

end at a full page boundary.<br />

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

User Response: Refer to the code to determine the<br />

error. Correct any errors <strong>and</strong> retry the comm<strong>and</strong>.<br />

H<strong>CP</strong>1999E The assign was not reset on rdev<br />

because {it is not a tape that supports<br />

assign|a time_out condition occurred}<br />

Explanation: The reset comm<strong>and</strong> was entered to<br />

reset the assign on a device that is either not a tape

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

Saved successfully!

Ooh no, something went wrong!