Initial definition of I/O configuration data

Edit online
Before installing the CPC, you can create an IOCP input file on an existing system. The service representative uses this input file during the installation of the new CPC unless you are upgrading a CPC and were able to write an IOCDS in preparation of the upgrade. To prepare an input file, follow these steps:
  1. Determine, from your physical plan, the I/O configuration requirements that must be met to install the CPC.
  2. Prepare an input file of IOCP statements that define your I/O configuration and system requirements. The service representative uses this file when installing the CPC. For a sample input file containing IOCP statements, see Figure 1.
  3. Check the IOCP statement input by running the IOCP command under ZCMS. Code NOWRTCDS in the IOCP command. Running this command checks the syntax of the IOCP statements and checks the configuration reports for the wanted configuration data.
    Note: When you perform an initial program load (IPL) of VM, VM creates its software I/O configuration by sensing the devices in the hardware I/O configuration. If all the devices return all of the information VM needs, VM completes its software I/O configuration. If not, you must specify this information in the system configuration file. Ensure that this information corresponds to the information you code in the IOCP statements. Figure 2 contains sample SYSTEM CONFIG statements that correspond to some of the IOCP statements in Figure 1.
  4. If there are any errors in the IOCP statements, correct the errors and rerun IOCP (Step 3).
  5. Analyze the IOCP configuration reports (produced in Step 3) to ensure that the I/O configuration you want is defined. If necessary, revise the IOCP statements and rerun IOCP.
  6. If you are upgrading to a CPC whose SYSTEM= value supports IOCDS generation option NOCHKCPC, write the IOCDS for the new CPC on your current CPC using NOCHKCPC. See Machine rules to determine which CPCs can write an IOCDS in preparation for an upgrade and which CPCs can have an IOCDS written to them by ICP IOCP. This method is the preferred method for writing the initial IOCDS when upgrading a CPC. All users must have privilege class C to write an IOCDS and privilege class B to write a dynamic-capable IOCDS. Inform the service representative which IOCDS to use after the upgrade. Skip Step 7.

    If you are upgrading to a CPC whose SYSTEM= value does not support parameter NOCHKCPC or if this installation is a new installation, continue with Step 7.

  7. Download the input file to USB flash memory drive. If the file is too large to fit, compress it using a zip-compatible program. Source from a USB flash memory drive must be in VFAT or DOS file format or have been compressed. Instead of a USB flash memory drive, an uncompressed IOCP source file can be imported to the SE from an FTP location by the service representative.
    Note: During the physical installation of the CPC, the service representative uses your validated input file (with the stand-alone version of IOCP) to configure and test the I/O configuration for the new CPC. See Creating an IOCDS in a new CPC for an example using the stand-alone version of IOCP.