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>1252I Device rdev has been unassigned by<br />

user userid<br />

Explanation: A tape drive that was assigned using the<br />

VARY comm<strong>and</strong> <strong>and</strong> then attached to a user (with or<br />

without the assign option) is found unassigned during<br />

detach processing.<br />

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

Operator Response: Vary off the device, then vary it<br />

back on with the ASSIGN option.<br />

H<strong>CP</strong>1280E The variations of this message are<br />

explained below.<br />

MESSAGES:<br />

v Device vdev not usable; assign lost.<br />

v Device vdev not usable; reserve lost.<br />

v Device vdev not usable; reserve lost by userid as<br />

vdev.<br />

Explanation: A virtual device has been made<br />

unavailable because the operating system has detected<br />

that an assign or reserve to that device has been lost,<br />

<strong>and</strong> the state of the data is unpredictable. This message<br />

is issued to the holder of the assign or reserve.<br />

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

Operator Response: If you were the user that lost the<br />

assign, determine if the data is usable. If it is, the<br />

assign must be re-established in order to safely<br />

continue accessing the data. One way to re-establish<br />

the assign is to detach the device <strong>and</strong> then attach it<br />

again.<br />

H<strong>CP</strong>1281I Path channel to device rdev now offline;<br />

path group ID mismatch.<br />

Explanation: The operating system has detected that<br />

one of the paths to a device has a path group ID that<br />

does not match that which the system uses to access<br />

the device. Since attempts to use this path would result<br />

in “hang” conditions, the system has marked the path<br />

offline.<br />

<strong>System</strong> Action: <strong>System</strong> action continues.<br />

Operator Response: If possible, physically reset the<br />

path <strong>and</strong> then vary it online to that device.<br />

H<strong>CP</strong>1282I Path yy to device xxxx has been forced<br />

offline; a configuration change was<br />

detected.<br />

Explanation: A reset event occurred on this path, <strong>and</strong><br />

<strong>CP</strong> has detected that the channel path has been<br />

reconnected to a different device.<br />

<strong>System</strong> Action: The channel path is logically varied<br />

offline from the device.<br />

Operator Response: Reconnect the channel path to<br />

H<strong>CP</strong>1252I H<strong>CP</strong>1352E<br />

the original device <strong>and</strong> issue the VARY ON PATH<br />

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

H<strong>CP</strong>1283I Path channel to device rdev currently<br />

not responding.<br />

Explanation: The system has detected one of the<br />

paths to a device is currently not responding to system<br />

I/O requests. The system has stopped using this path.<br />

Because this is a multiple path device, the system can<br />

still access the device. However, the loss of the path<br />

may degrade I/O performance.<br />

<strong>System</strong> Action: <strong>System</strong> Action continues. Even<br />

though the path is not being used, the system may<br />

consider the path to be online.<br />

Operator Response: If possible, physically reset the<br />

path. Enter the VARY ONLINE PATH comm<strong>and</strong> to<br />

ensure the system is using this path. If the problem<br />

persists, vary the path offline <strong>and</strong> contact your system<br />

support personnel.<br />

H<strong>CP</strong>1350E Named Saved <strong>System</strong> (NSS) name<br />

cannot be saved because MP users<br />

cannot save a Named Saved <strong>System</strong><br />

(NSS).<br />

Explanation: As a virtual MP user, you cannot save<br />

an NSS.<br />

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

Programmer Response: You must be logged onto a<br />

user ID that is not using virtual MP.<br />

H<strong>CP</strong>1351I LOAD REQUEST TERMINATED;<br />

SEGMENT segment-number WOULD BE<br />

OVERLAID.<br />

Explanation: You tried to load a saved segment that<br />

would cause an overlay of at least one segment of an<br />

existing NSS or saved segment.<br />

<strong>System</strong> Action: <strong>CP</strong> does not load the saved segment.<br />

User Response: Refer to z/<strong>VM</strong>: <strong>CP</strong> Programming<br />

Services for a detailed description of DIAGNOSE X'64'.<br />

H<strong>CP</strong>1352E <strong>System</strong> name cannot be processed.<br />

Explanation: Because of internal errors, the named<br />

saved system specified by name cannot be IPLed, or<br />

the discontiguous saved segment specified by<br />

DIAGNOSE X'64' cannot be loaded.<br />

<strong>System</strong> Action: A soft abend dump has been<br />

generated.<br />

User Response: Reissue the comm<strong>and</strong> <strong>and</strong>, if the<br />

problem persists, contact your system support<br />

personnel.<br />

Programmer Response: Examine the soft abend<br />

dump associated with this failure. Refer to the<br />

Chapter 3. <strong>System</strong> <strong>Messages</strong> 233

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

Saved successfully!

Ooh no, something went wrong!