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.

SET RDEVICE DASD<br />

Usage Notes<br />

Examples<br />

Responses<br />

Messages<br />

OFF<br />

(the default if the SHARED YES option is specified.) Tells <strong>CP</strong> to not cache<br />

data on the real device in the minidisk cache.<br />

DFLTOFF<br />

tells <strong>CP</strong> to not cache data on the real device in the minidisk cache except<br />

for minidisks for whom caching is specifically enabled via the MINIOPT<br />

MDC directory statement or the SET MDCACHE MDISK ON comm<strong>and</strong>.<br />

SENSed<br />

tells <strong>CP</strong> to use the information returned from a sense ID request to determine<br />

the characteristics of this DASD. If omitted, the default is SENSED.<br />

NOTSENSed<br />

tells <strong>CP</strong> not to use the information returned from a sense ID request to<br />

determine the characteristics of this DASD.<br />

1. Not all DASD types are eligible for caching in the minidisk cache. If you specify<br />

MDC DFLTON or MDC DFLTOFF for a device that is not cache eligible, data on<br />

that device will not be cached.<br />

Example 1:<br />

To specify a shared DASD with minidisk caching off at device number 0410, enter<br />

the following SET RDEVICE comm<strong>and</strong>:<br />

set rdevice 0410 type dasd shared yes<br />

Example 2:<br />

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

To define a non-shared DASD at device number 500 with minidisk caching enabled<br />

on a device only for those minidisks that have specifically enabled caching, use the<br />

following SET RDEVICE comm<strong>and</strong>:<br />

set rdevice 500 type dasd mdc dfltoff<br />

After <strong>CP</strong> has issued a message for each device address affected by a SET<br />

RDEVICE comm<strong>and</strong>, the following summary response is displayed:<br />

xxx RDEV(s) specified; yyy RDEV(s) changed; zzz RDEV(s) created<br />

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

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

H<strong>CP</strong>6000E The range of device numbers cannot<br />

exceed 256.<br />

H<strong>CP</strong>6704E Missing token at end of line<br />

H<strong>CP</strong>6706E Invalid address range - range<br />

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

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

Saved successfully!

Ooh no, something went wrong!