The
following example describes the steps that you can use to initially
define and check the I/O configuration data to prepare for the installation
of a new CPC. The example suggests that you develop a card-image input
file (consisting of IOCP statements) and check the input file on an
existing system. The service representative uses this input file to
generate the I/O configuration data 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. Use this input deck to generate new
I/O configuration data after
changing your I/O configuration.
- Determine, from your physical plan, the I/O configuration requirements
that you must meet to install the CPC.
- Prepare an input file (containing IOCP statements) that defines
your I/O configuration. Using this file, run IOCP as described in
the following steps. (Lists of statement input shows a list
of a typical IOCP input file containing IOCP statements.)
- Run IOCP with JCL statements to
validate the IOCP statements.
In the PARM parameter of the EXEC
statement, use the WRTCDS=NO option. This option checks the syntax
of the IOCP statements and checks the configuration reports for the
wanted configuration data.
- If there are any errors in the IOCP statements, correct the errors
and rerun IOCP (Step 3).
- Analyze the IOCP configuration reports (produced in Step 3)
to ensure that you have defined I/O configuration that you want.
If necessary, revise the IOCP statements and rerun IOCP.
- If you are upgrading to a CPC whose SYSTEM= value supports execution
parameter CHECKCPC=NO, write the IOCDS for the new CPC on your current
CPC using CHECKCPC=NO. See Machine rules to
determine which CPCs can write an IOCDS in preparation for an upgrade
and which CPCs can have ICPIOCP write an IOCDS to them. Inform the
service representative which IOCDS to use after the upgrade.
This method is the preferred method for writing the initial
IOCDS when upgrading a CPC. Skip Step 7.
If you are upgrading to a CPC whose SYSTEM=value does
not support execution parameter CHECKCPC=NO or if this installation is
a new installation, continue with Step 7.
- To save the validated input file the service representative to use during
installation of the CPC, 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 a 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.