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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Introduction<br />

Table 2. Privilege Classes (continued)<br />

Class User <strong>and</strong> Function<br />

Any <strong>Comm<strong>and</strong>s</strong> belonging to class “Any” are available to any user, regardless of<br />

his privilege class. These comm<strong>and</strong>s are primarily those used to gain access<br />

to, or relinquish access from, the z/<strong>VM</strong> system.<br />

H Reserved for <strong>IBM</strong> use.<br />

I - Z<br />

1 - 6<br />

Delayed Responses to <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong><br />

Classes I through Z are reserved for redefinition through user class<br />

restructure (UCR) by each installation for its own use.<br />

Many <strong>CP</strong> comm<strong>and</strong>s associated with DASD subsystems result in a channel<br />

program being issued to a device or subsystem. In most cases, these operations<br />

complete in a very short time, <strong>and</strong> the comm<strong>and</strong> response is presented to the<br />

operator immediately. However, for 3990 Model 3 or Model 6 subsystems, some of<br />

these operations do not complete immediately. The comm<strong>and</strong> responses associated<br />

with such operations are called delayed responses.<br />

The <strong>CP</strong> comm<strong>and</strong>s that may result in delayed responses are:<br />

v COMMIT<br />

v FLASHCOPY<br />

v SET CACHE ON SUBSYSTEM<br />

v SET CACHE OFF SUBSYSTEM<br />

v SET CACHE OFF DEVICE<br />

v SET CACHEFW OFF<br />

v SET DASDFW OFF<br />

v SET NVS ON<br />

v SET NVS OFF<br />

The responses to these comm<strong>and</strong>s are displayed in the following manner.<br />

If the comm<strong>and</strong> completes immediately, the following response is displayed:<br />

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

If the comm<strong>and</strong> does not complete immediately, the following response is displayed:<br />

Comm<strong>and</strong> started: comm<strong>and</strong> details<br />

If the comm<strong>and</strong> completes successfully, the following response is displayed:<br />

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

If errors occur during the asynchronous processing of the comm<strong>and</strong> that prevent<br />

the successful completion of the comm<strong>and</strong>, the following response is displayed:<br />

Comm<strong>and</strong> failed: comm<strong>and</strong> details<br />

Under certain circumstances, it is possible that a cache storage subsystem will not<br />

notify <strong>CP</strong> when it has completed a comm<strong>and</strong>. When this occurs, the usual<br />

completion responses cannot be generated. Under these circumstances, comm<strong>and</strong><br />

processing is ended after displaying the following response:<br />

Comm<strong>and</strong> results lost: comm<strong>and</strong> details<br />

If the originator of the comm<strong>and</strong> is not the system operator, the following response<br />

may be issued to the system operator when the comm<strong>and</strong> completes.<br />

Normal comm<strong>and</strong> response by userid.<br />

8 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!