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.

<strong>CP</strong>HX<br />

Messages<br />

Response 2:<br />

If your user ID has class A privileges, you can use the <strong>CP</strong>HX comm<strong>and</strong> to cancel<br />

any of the previously mentioned <strong>CP</strong> comm<strong>and</strong>s issued by other virtual machines.<br />

For example, someone may have requested that a service machine attach a set of<br />

real devices:<br />

sm rscs cp attach 0100-01ff to *<br />

Ready;<br />

An ATTACH comm<strong>and</strong> may take a long time because of hardware problems on a<br />

controller. If you notice that an ATTACH comm<strong>and</strong> is taking an unusually long time,<br />

you can choose to cancel the remainder of the ATTACH comm<strong>and</strong>. If you do, you<br />

see something like this:<br />

cphx rscs<br />

Your request to halt RSCS’s ATTACH comm<strong>and</strong> has been initiated.<br />

Ready;<br />

H<strong>CP</strong>HXC6792I User RSCS’s ATTACH comm<strong>and</strong> halted.<br />

The message that informs you of the successful cancelation of the ATTACH<br />

comm<strong>and</strong> arrives some time after the <strong>CP</strong>HX comm<strong>and</strong> execution completes. The<br />

ATTACH comm<strong>and</strong> processing only recognizes the <strong>CP</strong>HX request when it begins to<br />

attach a new device.<br />

The RSCS virtual machine’s console would reflect the following activity as a result<br />

of the <strong>CP</strong>HX comm<strong>and</strong> execution:<br />

09:01:52<br />

.<br />

Location YORKTOWN(MAINT) executing: <strong>CP</strong> ATTACH 0100-01FF TO *<br />

.<br />

H<strong>CP</strong>HXC6793I User MAINT has halted your ATTACH comm<strong>and</strong>.<br />

H<strong>CP</strong>ATR6790I ATTACH processing halted. The next device<br />

that would have been processed is 0108.<br />

The example above assumes that you are user ID MAINT. The last message<br />

indicates the ATTACH processing had completed processing devices 0100 to 0107<br />

<strong>and</strong> was canceled before it tried to attach device 0108.<br />

<strong>CP</strong> notifies the operator ID of the cancelation by issuing a message like this one to<br />

the operator’s console:<br />

H<strong>CP</strong>HXC6791I User MAINT has halted the ATTACH comm<strong>and</strong> processed<br />

by user RSCS.<br />

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

extra option(s) starting with oper<strong>and</strong><br />

H<strong>CP</strong>020E Userid missing or invalid<br />

H<strong>CP</strong>045E userid not logged on<br />

H<strong>CP</strong>644E Unknown/unauthorized <strong>CP</strong> comm<strong>and</strong>:<br />

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

H<strong>CP</strong>6790I The variations of this message are as<br />

follows:<br />

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

v {ATTACH|VARY} processing halted.<br />

The next device that would have been<br />

processed is rdev.<br />

v {LOCATE|LOCATE<strong>VM</strong>} processing<br />

halted. The next location that would<br />

have been processed is address.<br />

H<strong>CP</strong>6791I User userid has halted the comm<strong>and</strong><br />

comm<strong>and</strong> executed by user userid.<br />

H<strong>CP</strong>6792I User userid’s comm<strong>and</strong> comm<strong>and</strong><br />

halted.

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

Saved successfully!

Ooh no, something went wrong!