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.

Example<br />

The user may display the status of comm<strong>and</strong>s that he has issued that have not yet<br />

completed by issuing the QUERY PENDING COMMANDS comm<strong>and</strong>s. QUERY<br />

PENDING COMMANDS causes the following response to be displayed for each<br />

pending <strong>CP</strong> comm<strong>and</strong>:<br />

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

The user may display the status of ALL comm<strong>and</strong>s that are pending for a device by<br />

issuing the QUERY PENDING COMMANDS ALLUSERS comm<strong>and</strong>. The<br />

ALLUSERS option causes one of the following responses to be displayed for each<br />

pending <strong>CP</strong> comm<strong>and</strong>:<br />

Comm<strong>and</strong> pending for userid: comm<strong>and</strong> details<br />

or<br />

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

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

is the usual response associated with the successful completion of this<br />

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

userid<br />

is the ID of the user who issued the comm<strong>and</strong> if the comm<strong>and</strong> was not issued<br />

by the issuer of the QUERY PENDING COMMANDS ALLUSERS comm<strong>and</strong>.<br />

comm<strong>and</strong> details<br />

is the comm<strong>and</strong> <strong>and</strong> options with which this delayed response is associated.<br />

Assume that a class B user, DASDOPER, wants to deactivate the DASD fast write<br />

function for devices 190 through 194 by issuing SET DASDFW DEVICE OFF 190-194.<br />

Since SET DASDFW OFF may produce delayed responses, all of the following<br />

results are possible. Assume that the devices respond as follows:<br />

v 190 - responds immediately as successful<br />

v 191 - delayed response buffer indicates completed successfully<br />

v 192 - delayed response buffer indicates completed with errors<br />

v 193 - delayed response buffer indicates comm<strong>and</strong> failed<br />

v 194 - polling detects that the response was lost.<br />

Note: The operator is informed of all successful operations.<br />

Comm<strong>and</strong> Issuer’s Console (DASDOPER)<br />

SET DASDFW DEVICE OFF 190-194<br />

190 DASD fast write function has been deactivated.<br />

Comm<strong>and</strong> started: SET DASDFW OFF 191.<br />

Comm<strong>and</strong> started: SET DASDFW OFF 192.<br />

Comm<strong>and</strong> started: SET DASDFW OFF 193.<br />

Comm<strong>and</strong><br />

.<br />

started: SET DASDFW OFF 194.<br />

.<br />

QUERY PENDING COMMANDS 190-194<br />

No pending delayed responses exist for 190.<br />

Comm<strong>and</strong> pending: SET DASDFW OFF 191.<br />

Comm<strong>and</strong> pending: SET DASDFW OFF 192.<br />

Comm<strong>and</strong> pending: SET DASDFW OFF 193.<br />

Comm<strong>and</strong><br />

.<br />

pending: SET DASDFW OFF 194.<br />

.<br />

191<br />

.<br />

DASD fast write function has been deactivated.<br />

.<br />

192<br />

.<br />

DASD fast write function has been deactivated.<br />

.<br />

Comm<strong>and</strong><br />

.<br />

failed: SET DASDFW OFF 193.<br />

.<br />

Comm<strong>and</strong> results lost: SET DASDFW OFF 194.<br />

Introduction<br />

Chapter 1. Introduction 9

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

Saved successfully!

Ooh no, something went wrong!