Hardware configuration definition (HCD) notes:

Edit online
  1. You do not need to run IOCP directly to define the I/O configuration to the I/O subsystem. However, HCD does run IOCP when it needs to write an IOCDS.
  2. If z/OS is a guest on VM, you cannot write an IOCDS to a CPC that is part of an S/390® microprocessor cluster.
  3. 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/OS® Hardware Configuration Definition User's Guide, SC34-2669.
  4. When HCD generates an IOCP input source file without PCHIDs, the file must be migrated back into HCD after the CHPID 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. Stand-alone IOCP can use this file to write an IOCDS.
  5. 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 the IOCP warning messages.
Use JCL statements to run IOCP. In the EXEC statement, code options in the PARM keyword to direct IOCP to do the following tasks:
  • Generate an IOCDS:
    • Read, validate, and check the syntax of input statements
    • Generate an IOCDS based on the configuration defined in the statements
    • Produce reports of the IOCDS
    • When requested, write the generated IOCDS to the Support Element hard disk.
  • Produce configuration reports: