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.

<strong>CP</strong>ACCESS<br />

Usage Notes<br />

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

write or stable access exists, <strong>CP</strong> establishes read-only access. If an<br />

exclusive mode access exists, access is denied.<br />

MW<br />

Multiple-write access. <strong>CP</strong> establishes write access in all cases except when<br />

a user has an existing stable or exclusive mode access to the disk.<br />

Note: A stable access means that the user holding the (SR, SW, or SM)<br />

access can be assured that the disk remains stable, unchanged by<br />

others, until the access is released.<br />

R Read-only access. <strong>CP</strong> establishes read access unless a user has an<br />

existing write or exclusive mode access to the disk.<br />

RR<br />

Read-only access. <strong>CP</strong> establishes read access unless a user has an<br />

existing exclusive mode access.<br />

SM<br />

Stable multiple access. <strong>CP</strong> establishes write access unless a user holds a<br />

write, a stable, or an exclusive mode access to this disk. <strong>CP</strong> denies all<br />

requests for write access to a disk with an existing SM mode access.<br />

SR<br />

Stable read-only access. <strong>CP</strong> establishes read access unless a user has an<br />

existing write or exclusive mode access to this disk. <strong>CP</strong> denies all requests<br />

for write access to a disk with an existing SR mode access. SR is the<br />

default.<br />

SW<br />

Stable write access. <strong>CP</strong> establishes write access unless a user has an<br />

existing access (any mode) to this disk. <strong>CP</strong> denies all requests for write<br />

access to a disk with an existing SW mode access.<br />

W Write access. <strong>CP</strong> establishes write access unless a user has an existing<br />

access (any mode) to the disk.<br />

WR<br />

Write access. <strong>CP</strong> establishes write access unless a user has an existing<br />

access (any mode) to the disk. If write access is denied, <strong>CP</strong> establishes<br />

read access unless another user has an existing exclusive mode access for<br />

the disk.<br />

ASYNChronous<br />

tells <strong>CP</strong> to schedule the comm<strong>and</strong> <strong>and</strong> lets you enter other comm<strong>and</strong>s before<br />

the <strong>CP</strong>ACCESS comm<strong>and</strong> completes. When the <strong>CP</strong>ACCESS comm<strong>and</strong><br />

completes, <strong>CP</strong> displays a 1-line response, such as:<br />

<strong>CP</strong>ACCESS request for userid’s vdev in mode mode completed<br />

ASYNCHRONOUS is the default.<br />

SYNChronous<br />

tells <strong>CP</strong> to process the comm<strong>and</strong> immediately <strong>and</strong> does not allow you to enter<br />

any other comm<strong>and</strong>s until the <strong>CP</strong>ACCESS comm<strong>and</strong> completes.<br />

1. Even though <strong>CP</strong> may establish write access to a minidisk (for example, by using<br />

the link mode MW), <strong>CP</strong> itself does not write to the minidisk.<br />

2. When you enter the <strong>CP</strong>ACCESS comm<strong>and</strong> <strong>and</strong> specify a file mode letter that<br />

<strong>CP</strong> is using for another minidisk, <strong>CP</strong> releases the first minidisk <strong>and</strong> accesses<br />

the minidisk you specified.<br />

3. If the specified minidisk contains files that will be used frequently, you should<br />

either:<br />

v Issue the <strong>CP</strong>CACHE comm<strong>and</strong> to cache each file into storage.

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

Saved successfully!

Ooh no, something went wrong!