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 MDCACHE<br />

►►<br />

Set<br />

Purpose<br />

MDCache<br />

Oper<strong>and</strong>s<br />

FLUSH<br />

INSert<br />

vdev<br />

vdev-vdev<br />

ON<br />

OFF<br />

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

DIRectory<br />

DRCT<br />

Use SET MDCache to do the following:<br />

v Set global minidisk caching on or off.<br />

v Control minidisk caching at the real device or minidisk level.<br />

v Change a user’s ability to insert data into the cache.<br />

v Specify the maximum <strong>and</strong> minimum amounts of Real <strong>and</strong>/or Exp<strong>and</strong>ed Storage<br />

that can be used by a minidisk cache. The actual size of the minidisk cache<br />

varies <strong>and</strong> is determined dynamically by the paging <strong>and</strong> I/O load.<br />

SYStem<br />

RDEV<br />

MDIsk<br />

There is a hierarchy used to determine if a given virtual I/O will be cached.<br />

These three keywords define which hierarchy level to which the comm<strong>and</strong><br />

pertains.<br />

v The SYSTEM option is the highest level of control of the minidisk cache.<br />

With the SYSTEM option, minidisk caching can be globally turned on<br />

(enabled) or off (disabled) for the entire system via SET MDCACHE<br />

SYSTEM ON <strong>and</strong> SET MDCACHE SYSTEM OFF. If minidisk caching is on at<br />

the system level, it can be further controlled at the real device <strong>and</strong> minidisk<br />

level.<br />

v The RDEV option is the next highest level of control of the cache. If minidisk<br />

caching is on for the system, the installation can change the cache eligibility<br />

for a given real device, <strong>and</strong> hence, all minidisks that reside on that device via<br />

SET MDCACHE RDEV action rdev (or SET MDCACHE RDEV action<br />

rdev-rdev) where action is either DFLTON, DFLTOFF, OFF, or FLUSH.<br />

v The MDISK option is the lowest level of control of the cache. If minidisk<br />

caching is on for the system, the installation can change the cache eligibility<br />

for an active minidisk via SET MDCACHE MDISK action USERID userid<br />

vdev (or SET MDCACHE MDISK action USERID userid vdev-vdev). Note<br />

that for a minidisk to be cached, the system must be enabled for caching, the<br />

real device on which it resides must be set to DFLTON or DFLTOFF for<br />

caching, <strong>and</strong> the minidisk itself must be enabled for caching.<br />

Class G users can use the SET MDCACHE FLUSH vdev (or SET<br />

MDCACHE FLUSH vdev-vdev) to purge the cache of data pertaining to<br />

minidisks defined in their directory.<br />

The duration of cache control at the minidisk level is not permanent when set<br />

by the SET MDCACHE comm<strong>and</strong>. Permanent cache control at the minidisk<br />

level is achieved by the use of the MDC <strong>and</strong> NOMDC options of the<br />

MINIOPT directory control statement. For the SET MDCACHE comm<strong>and</strong> to<br />

be successful for a minidisk, the minidisk must be active (that is, the minidisk<br />

must be linked by at least one user who is logged on the system). If at a<br />

►◄

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

Saved successfully!

Ooh no, something went wrong!