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.

drive or a tape drive that does not support assign, or<br />

the unassign I/O timed out.<br />

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

Operator Response: None.<br />

H<strong>CP</strong>2000E The reserve was not reset on rdev<br />

because it is not a shared DASD.<br />

Explanation: You identified a real device that was not<br />

defined as a SHARED full-pack minidisk when you<br />

entered the RESET RESERVE (ON) rdev comm<strong>and</strong>.<br />

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

Operator Response: Enter the <strong>CP</strong> QUERY DASD<br />

RESERVE comm<strong>and</strong> to determine the reserve status of<br />

the devices in your configuration.<br />

H<strong>CP</strong>2001E The reserve was not reset on DASD<br />

rdev because it was not reserved.<br />

Explanation: You entered the RESET RESERVE (ON)<br />

rdev comm<strong>and</strong>, specifying a device (type rdev) that is<br />

not currently reserved by <strong>CP</strong>.<br />

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

User Response: Enter the <strong>CP</strong> QUERY DASD<br />

RESERVE comm<strong>and</strong> to determine the reserve status of<br />

the devices in your configuration.<br />

H<strong>CP</strong>2002I Reserved device vdev is<br />

unconditionally reserved by userid’s<br />

vdev.<br />

Explanation: The virtual device vdev that a user had<br />

in RESERVE status has received an UNCONDITIONAL<br />

RESERVED request from the specified user’s virtual<br />

device. In this case, the first user loses the device. Data<br />

integrity may be affected with a possible loss of some<br />

information.<br />

<strong>System</strong> Action: The RESERVE to the specified virtual<br />

device is reset. The specified user now has the virtual<br />

device reserved.<br />

User Response: None.<br />

H<strong>CP</strong>2003E Shared not set for type rdev; not a<br />

shared device.<br />

Explanation: You issued a SET SHARED comm<strong>and</strong><br />

against a device (type rdev) that is not defined as a<br />

full-pack minidisk. Only shared full-pack minidisk<br />

devices may be identified as shared by the SET<br />

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

<strong>System</strong> Action: <strong>System</strong> operation continues, but the<br />

device cannot be shared because it cannot be defined<br />

as a full-pack minidisk, <strong>and</strong> does not support concurrent<br />

virtual reserve/release.<br />

User Response: Inform your support personnel that<br />

the device cannot be shared between virtual <strong>and</strong> real<br />

systems as currently defined.<br />

H<strong>CP</strong>2004E Shared not set for type rdev; does not<br />

support reserve/release.<br />

Explanation: You attempted to identify the device<br />

(type rdev) as shared, either with the SHARED=YES<br />

option in the RDEVICE statement in H<strong>CP</strong>RIO or with<br />

the SET SHARED comm<strong>and</strong>. However, the device does<br />

not support hardware reserve/release CCWs <strong>and</strong> cannot<br />

be shared between multiple real <strong>and</strong> virtual systems.<br />

<strong>System</strong> Action: <strong>System</strong> operation continues but the<br />

device does not support concurrent virtual <strong>and</strong> real<br />

reserve/release.<br />

User Response: Inform your support personnel that<br />

the device does not support reserve/release CCWs.<br />

H<strong>CP</strong>2005I Reserve pending on DASD rdev for<br />

user userid<br />

Explanation: A missing interrupt was detected<br />

because of an outst<strong>and</strong>ing reserve request for the<br />

device rdev.<br />

The userid variable in the message identifies the system<br />

for which <strong>CP</strong> is trying to obtain the reserve.<br />

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

User Response: None.<br />

H<strong>CP</strong>2000E H<strong>CP</strong>2007E<br />

H<strong>CP</strong>2006E Shared not set for DASD rdev; device<br />

not online.<br />

Explanation: You entered the SET SHARED<br />

comm<strong>and</strong> for device rdev, but the device is not online.<br />

Sharing will only be set ON or OFF for online devices.<br />

<strong>System</strong> Action: <strong>System</strong> operation continues, but the<br />

device does not support concurrent virtual <strong>and</strong> real<br />

reserve/release.<br />

Operator Response: Vary the device online with the<br />

VARY ON comm<strong>and</strong>; then reenter the SET SHARED<br />

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

H<strong>CP</strong>2007E Shared not set for DASD rdev;<br />

WRKALLEG is ON for user userid,<br />

minidisk vdev.<br />

Explanation: You entered a SET SHARED comm<strong>and</strong><br />

against a real device that had an associated virtual<br />

device with WRKALLEG ON. SET WRKALLEG ON <strong>and</strong><br />

SET SHARED are incompatible. Use SET SHARED for<br />

sharing real devices; use SET WRKALLEG for sharing<br />

virtual devices.<br />

<strong>System</strong> Action: <strong>System</strong> operation continues, but the<br />

device cannot be shared because virtual working<br />

allegiance has been specified on one of the minidisks<br />

associated with the real device.<br />

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

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

Saved successfully!

Ooh no, something went wrong!