27.12.2012 Views

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - 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.

DETACH<br />

DETACH<br />

Purpose<br />

Usage Notes<br />

Messages<br />

Use the DETACH comm<strong>and</strong>s to detach the following:<br />

v Virtual processors from your virtual machine<br />

v Real devices from the host system<br />

v Logical devices from the host system<br />

v Real devices from your virtual machine<br />

v Logical devices from your virtual machine<br />

v A Virtual Vector Facility from your virtual machine<br />

v Virtual devices from your virtual machine<br />

v Real Exp<strong>and</strong>ed Storage from your virtual machine<br />

v Virtual message processor <strong>and</strong> message devices from your virtual machine<br />

v A <strong>VM</strong> LAN segment from the host system.<br />

(General for DETACH)<br />

1. SET IMSG OFF will suppress the informational messages for DETACH<br />

CRYPTO, DETACH <strong>CP</strong>U, DETACH MSGPROC, DETACH VECTOR, <strong>and</strong><br />

DETACH VDEV. DETACH RDEV <strong>and</strong> DETACH XSTORE are not affected by the<br />

IMSG setting.<br />

2. You cannot be certain that the device or Exp<strong>and</strong>ed Storage capability has been<br />

detached until you receive the appropriate response from the system. If after a<br />

reasonable amount of time you haven’t received the expected response, enter<br />

the QUERY comm<strong>and</strong> to determine the status of the device. Detachment may<br />

be pending or may have been unsuccessful.<br />

3. If you detach a minidisk with this comm<strong>and</strong> without releasing it, CMS implicitly<br />

releases the minidisk. QUERY DISK will not display that minidisk.<br />

4. You can designate a virtual CTCA by device address. If a virtual CTCA is<br />

detached while coupled with another virtual CTCA, the remote device is left in<br />

an un-coupled state, similar to its original condition after the DEFINE comm<strong>and</strong>.<br />

(General for DETACH)<br />

H<strong>CP</strong>002E Invalid oper<strong>and</strong> - oper<strong>and</strong><br />

H<strong>CP</strong>003E Invalid option - {option|comm<strong>and</strong><br />

contains extra option(s) starting with<br />

option}<br />

H<strong>CP</strong>006E Invalid device type vdev<br />

H<strong>CP</strong>007E Invalid userid - userid<br />

H<strong>CP</strong>009E Invalid range - range<br />

H<strong>CP</strong>020E Userid missing or invalid<br />

H<strong>CP</strong>021E A real device number was not supplied<br />

or it is invalid.<br />

232 z/<strong>VM</strong>: <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> <strong>and</strong> <strong>Utilities</strong> <strong>Reference</strong><br />

H<strong>CP</strong>022E A virtual device number was not<br />

supplied or it was invalid.<br />

H<strong>CP</strong>026E Oper<strong>and</strong> missing or invalid<br />

H<strong>CP</strong>040E Device {rdev|vdev|ldev} does not exist<br />

H<strong>CP</strong>045E userid not logged on<br />

H<strong>CP</strong>121E type {rdev|ldev} not attached to<br />

{userid|system}<br />

H<strong>CP</strong>124E DASD rdev in use by nnnnn users<br />

H<strong>CP</strong>143E type rdev in use by system

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

Saved successfully!

Ooh no, something went wrong!