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.

DISABLE HCD<br />

►►<br />

DISABLE HCD<br />

Authorization<br />

Purpose<br />

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

Usage Notes<br />

NOFORCE<br />

FORCE<br />

Privilege Class: B<br />

DISABLE HCD<br />

Use the DISAble HCD comm<strong>and</strong> to disable the I/O-configuration capabilities of<br />

HCM <strong>and</strong> HCD for the rest of the current IML of your machine, transferring I/O<br />

configuration control to the applicable <strong>CP</strong> operator comm<strong>and</strong>s.<br />

With HCM <strong>and</strong> HCD disabled, the hardware I/O configuration can be changed with<br />

the <strong>CP</strong> dynamic-I/O-configuration comm<strong>and</strong>s SET DYNamic_i/o, SET<br />

CONFIGmode, DEFine CHPID, DEFine CNTLUNIT, DEFine DEVice, MODify<br />

CHPID, MODify CNTLUNIT, MODify DEVice, DELete CHPID, DELete CNTLUNIT,<br />

DELete DEVice, Set IOCDS_active, <strong>and</strong> Set TOKen.<br />

Additionally, with HCM <strong>and</strong> HCD disabled, the <strong>VM</strong> software I/O configuration can be<br />

changed with the <strong>CP</strong> operator comm<strong>and</strong>s Set RDEVice, DELete RDEVice, Set<br />

EDEVice, DELete EDEVice, Set DEVices, <strong>and</strong> Set HOTIO.<br />

NOFORCE<br />

can be specified to cause the comm<strong>and</strong> to be rejected if, as part of disabling<br />

HCM <strong>and</strong> HCD <strong>and</strong> enabling the <strong>CP</strong> dynamic-I/O-configuration comm<strong>and</strong>s, a<br />

<strong>VM</strong> configuration token cannot be established. The inability to establish a <strong>VM</strong><br />

configuration token in the machine means that the <strong>CP</strong> dynamic-I/O-configuration<br />

comm<strong>and</strong>s cannot be used. Therefore the NOFORCE oper<strong>and</strong> leaves the HCM<br />

<strong>and</strong> HCD capability intact if the <strong>CP</strong> dynamic-I/O-configuration comm<strong>and</strong>s cannot<br />

be made effective.<br />

FORCE<br />

can be specified to force execution of the comm<strong>and</strong> even though a <strong>VM</strong><br />

configuration token cannot be established. In this case HCM <strong>and</strong> HCD are<br />

disabled from making I/O-configuration changes, <strong>and</strong> in addition the <strong>VM</strong><br />

dynamic-I/O-configuration comm<strong>and</strong>s remain disabled. No hardware<br />

I/O-configuration changes are possible without a re-IML of your machine<br />

(thereby taking down all logical partitions if the machine is logically partitioned).<br />

Software I/O-configuration changes can still be made, however, using the<br />

applicable <strong>CP</strong> operator comm<strong>and</strong>s.<br />

1. Once your machine is IMLed with HCM <strong>and</strong> HCD in control of the I/O<br />

configuration, the DISAble HCD comm<strong>and</strong> is a one-way escape mechanism to<br />

take control away from HCM <strong>and</strong> HCD <strong>and</strong> attempt to give it to the <strong>CP</strong> operator<br />

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

►◄<br />

Chapter 2. <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> 271

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

Saved successfully!

Ooh no, something went wrong!