DISABLE HCD

Authorization

Privilege Class: B

Purpose

Use the DISAble HCD command to disable the I/O-configuration capabilities of HCM and HCD for the rest of the current IML of your machine, transferring I/O configuration control to the applicable CP operator commands.

With HCM and HCD disabled, the hardware I/O configuration can be changed with the CP dynamic-I/O-configuration commands SET DYNamic_i/o, SET CONFIGmode, DEFine CHPID, DEFine CNTLUNIT, DEFine DEVice, MODify CHPID, MODify CNTLUNIT, MODify DEVice, DELete CHPID, DELete CNTLUNIT, DELete DEVice, Set IOCDS_active, and Set TOKen.

Additionally, with HCM and HCD disabled, the VM software I/O configuration can be changed with the CP operator commands Set RDEVice, DELete RDEVice, Set EDEVice, DELete EDEVice, Set DEVices, and Set HOTIO.

Operands

NOFORCE: can be specified to cause the command to be rejected if, as part of disabling HCM and HCD and enabling the CP dynamic-I/O-configuration commands, a VM configuration token cannot be established. The inability to establish a VM configuration token in the machine means that the CP dynamic-I/O-configuration commands cannot be used. Therefore the NOFORCE operand leaves the HCM and HCD capability intact if the CP dynamic-I/O-configuration commands cannot be made effective.
FORCE: can be specified to force execution of the command even though a VM configuration token cannot be established. In this case HCM and HCD are disabled from making I/O-configuration changes, and in addition the VM dynamic-I/O-configuration commands remain disabled. No hardware I/O-configuration changes are possible without a re-IML of your machine (thereby taking down all logical partitions if the machine is logically partitioned). Software I/O-configuration changes can still be made, however, using the applicable CP operator commands.

Usage Notes

Once your machine is IMLed with HCM and HCD in control of the I/O configuration, the DISAble HCD command is a one-way escape mechanism to take control away from HCM and HCD and attempt to give it to the CP operator commands.
Note that once HCM and HCD are disabled, there is no way to re-enable them without re-IMLing your machine (thereby taking down all logical partitions if the machine is logically partitioned).
If HCM and HCD are currently disabled for hardware dynamic-I/O-configuration, this command does not attempt to establish a VM configuration token in the machine. No attempt is made to change the token (which would allow the use of the CP-dynamic-I/O-configuration commands) because “ownership” of the existing configuration token is uncertain and it is not known whether HCM and HCD were ever used to dynamically change the machine configuration. In this case, whether FORCE or NOFORCE is specified, the command is executed and HCM and HCD are disabled. Even though the machine I/O configuration cannot be changed by any means in this case without a re-IML of your machine,, there is still the capability to dynamically change the software I/O configuration using CP operator commands.
If HCM and HCD are currently enabled for hardware dynamic-I/O-configuration when this command is issued and the configuration token is successfully changed to a VM configuration token, the SET DYNamic_i/o ON command can be issued to enable the use of the CP dynamic-I/O-configuration commands.

Responses

Response 1:

When the DISAble HCD command is issued and the VM/HCD service virtual machine does not exist or is not being used to control the I/O configuration, the following response will be issued:

disable hcd 
HCD is not active
Ready;

Response 2:

When the DISAble HCD command is issued and the VM/HCD service virtual machine is enabled for hardware I/O-configuration changes, the following response is issued when the configuration token is successfully changed to a VM token in the machine:

disable hcd force       
HCD was successfully disabled
Ready;

Response 3:

When the DISAble HCD command is issued and the VM/HCD service virtual machine is not enabled for hardware I/O-configuration changes, the following informational-message and command-response combination is issued:

disable hcd                                                  
HCPCCY654302I HCD is now disabled, but a VM configuration token   
HCPCCY654302I was not established because HCD was not enabled for 
HCPCCY654302I dynamic hardware changes.                           
Command complete.                                                 
Ready;

Response 4:

When the DISAble HCD FORCE command is issued and the VM/HCD service virtual machine is enabled for hardware I/O-configuration changes, the following informational-message and command-response combination is issued if the machine will not enter configuration mode to change the current configuration token to a VM configuration token:

disable hcd force                                             
HCPCCY654301I HCD is now disabled, but the machine would not enter 
HCPCCY654301I configuration mode to allow a VM configuration token 
HCPCCY654301I to be established.                                   
Command complete.                                                  
Ready;

Response 5:

When the DISAble HCD command is issued and CP is in the process of updating the I/O configuration for the VM/HCD service virtual machine, the following response will be issued:

disable hcd                                                       
HCD is currently updating the I/O configuration and cannot be disabled.
Ready;

Messages

HCP002E Invalid operand - operand
HCP003E Invalid option - command contains extra option(s) starting with option
HCP6544E Disable HCD command failed. The machine would not enter configuration mode to allow a VM configuration token to be established.