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.

H<strong>CP</strong>6020I H<strong>CP</strong>6025E<br />

<strong>System</strong> Action: The SHUTDOWN comm<strong>and</strong> is<br />

aborted.<br />

Operator Response: Increase the amount of time<br />

allowed for the shutdown process using the WITHIN or<br />

BY options of the SHUTDOWN comm<strong>and</strong>, decrease the<br />

amount of time reserved for <strong>VM</strong> SHUTDOWN using the<br />

SET SHUTDOWNTIME comm<strong>and</strong>, or reduce the<br />

amount of time allowed for guests to terminate using the<br />

SET SIGNAL SHUTDOWNTIME comm<strong>and</strong>.<br />

H<strong>CP</strong>6020I Guests do not have time to shut down<br />

because <strong>VM</strong> SHUTDOWN requires<br />

duration seconds<br />

Explanation: A deactivation function has caused the<br />

processor controller to signal the <strong>VM</strong> system to shut<br />

down. The indicated amount of time is reserved for the<br />

<strong>CP</strong> shutdown process, which is more than the interval<br />

allowed by the deactivation request <strong>and</strong> does not allow<br />

time for guests to terminate.<br />

<strong>System</strong> Action: <strong>System</strong> termination commences<br />

immediately without signalling guests.<br />

Operator Response: Increase the amount of time<br />

specified in the deactivation request, decrease the<br />

amount of time reserved for <strong>CP</strong> SHUTDOWN using the<br />

SET SHUTDOWNTIME comm<strong>and</strong>, or reduce the<br />

amount of time allowed for guests to terminate using the<br />

SET SIGNAL SHUTDOWNTIME comm<strong>and</strong>.<br />

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

explained below.<br />

MESSAGES:<br />

v Incompatible device - userid vdev is a subclass<br />

device.<br />

Explanation: The <strong>CP</strong> COUPLE comm<strong>and</strong> was used<br />

to couple a channel-to-channel adapter (CTCA) to<br />

another CTCA.<br />

userid The owner of the target virtual<br />

channel-to-channel adapter<br />

vdev The virtual address of the target virtual<br />

channel-to-channel adapter<br />

subclass<br />

The specific subclass of the target virtual<br />

channel-to-channel adapter<br />

The specified target virtual channel-to-channel<br />

adapter (userid vdev) has a subclass that is<br />

incompatible with the subclass of your own virtual<br />

channel-to-channel adapter. The error message<br />

includes the subclass of the target<br />

channel-to-channel adapter. The QUERY VIRTUAL<br />

channel-to-channel adapter comm<strong>and</strong> will tell you the<br />

subclass of your own channel-to-channel adapter.<br />

Virtual ESCON ®<br />

devices (defined with subclass<br />

SCTC, BCTC, or CNC) cannot be coupled to virtual<br />

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

3088 devices (defined with subclass CTCA or 3088).<br />

Also, a virtual ESCON connection requires one<br />

controller (SCTC or BCTC) coupled with one<br />

non-control device (the CNC).<br />

v Incompatible device - userid vaddr is a vdevtype<br />

device.<br />

Explanation: The <strong>CP</strong> COUPLE comm<strong>and</strong> was used<br />

to couple a virtual channel-to-channel adapter<br />

(CTCA) to another virtual CTCA.<br />

userid The owner of the target virtual<br />

channel-to-channel adapter<br />

vaddr The virtual address of the target virtual<br />

channel-to-channel adapter<br />

vdevtype<br />

Virtual device type (FCTC)<br />

v Incompatible LAN - ownerid lanname is a lantype<br />

LAN.<br />

Explanation: The <strong>CP</strong> COUPLE comm<strong>and</strong> was used<br />

to couple a simulated network interface card (NIC) to<br />

a <strong>VM</strong> Guest LAN.<br />

ownerid The owner of the target <strong>VM</strong>LAN<br />

segment<br />

lanname The name of the target <strong>VM</strong>LAN<br />

segment<br />

lantype The LANTYPE of the target <strong>VM</strong>LAN<br />

segment<br />

The specified target LAN (ownerid lanname) has a<br />

LANTYPE that is incompatible with the adapter type<br />

of your own simulated NIC. The error message<br />

includes the LANTYPE of the target LAN.<br />

Simulated NIC adapters can only be coupled to<br />

matching LAN types. For example, a HiperSockets<br />

NIC cannot be connected to a QDIO LAN.<br />

<strong>System</strong> Action: The COUPLE operation is not<br />

performed.<br />

User Response: Perform one of the following:<br />

v Issue QUERY CTCA comm<strong>and</strong>s to find appropriate<br />

channel-to-channel devices to connect.<br />

v Issue QUERY NIC <strong>and</strong> QUERY LAN comm<strong>and</strong>s to<br />

find appropriate network adapters <strong>and</strong> LAN segments<br />

to connect.<br />

v Change the definition of one of the virtual devices<br />

(DETACH <strong>and</strong> then DEFINE it with a definition that is<br />

compatible with the target). Then repeat the COUPLE<br />

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

H<strong>CP</strong>6025E Oper<strong>and</strong> {STATUS|STORE<br />

STATUS|RESTART} is invalid because<br />

<strong>CP</strong>U nn is in check-stop state.<br />

Explanation: While the virtual machine was in<br />

check-stop state, the SYSTEM comm<strong>and</strong> was entered<br />

with either the RESTART or STORE STATUS oper<strong>and</strong>,

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

Saved successfully!

Ooh no, something went wrong!