Hardware configuration definition (HCD) notes

Edit online
  1. When using HCD to define the I/O configuration for VM, you need not run IOCP directly to define the I/O configuration to the I/O subsystem. However, HCD does run IOCP when it must write an IOCDS. HCD users: Always use HCD (CBDSIOCP EXEC) to write an IOCDS from VM.
  2. When HCD generates an IOCP input source file, it can include comments that HCD uses if the IOCP source file is migrated into HCD. They have special meaning to HCD. These comments begin with *$HCDC$ or *$HCD$. For more information, see z/VM® Dynamic I/O Configuration Planning and Administration, SC24-6044.
  3. When HCD generates an IOCP input source file without PCHIDs, the file must be migrated back into HCD after the IBM Z Connectivity Mapping Tool adds PCHID numbers to the file. HCD can then write an IOCDS or a new IOCP input file can then be created from HCD, which a stand-alone IOCP can use to write an IOCDS.
  4. IOCP warning message ICP065I with return code 4 (RC=4) results when writing an IOCDS if your I/O configuration contains an unsupported function or channel path type for the current EC level of your CPC. This situation in turn results in the following HCD message. 
    CBDA676I   IOCP completed with warning messages for <proc-id>.
    See the IOCP output listing to view any IOCP warning messages.