The configuration might only have a subset of these addresses, and the subset
might not be contiguous.
You need to know what CU images you created before you can update the I/O
configuration. Your host system uses the updated I/O information in order to
know what CU images are on the DS8000.
Overview of the input/output configuration program for the
DS8000
The input/output configuration program provides the information needed for the
DS8000 when handling PAVs.
The output that the input/output configuration program (IOCP) generates contains
the I/O definition for the channel subsystem of a System z or S/390 host. It is not
used as input to the I/O definition for the operating system for the System z or
S/390 host. Therefore, you do not need to distinguish between bases and alias
devices in the input to IOCP. However, doing so provides an accurate
representation of the I/O configuration.
The operating system for the System z or S/390 host requires that the
input/output definition file (IODF) that the hardware configuration definition
(HCD) creates, specifies base and alias devices. The operating system dynamically
discovers which base and alias devices are associated with each other. HCD
invokes IOCP to build an IOCDS that identifies the I/O definition for the host
processor.
The VM, z/VM, and VSE operating systems dynamically discover which devices
are bases and aliases and which are associated with each other. The VM and z/VM
operating systems support PAVs for guest usage.
An IOCP example
The following is an IOCP example that defines ESCON and FICON bridge channel
path IDs that you have attached to an ESCON director. This example uses the
storage unit machine number, 2107. HCD users can use the information in the
following IOCP example to determine how to define a storage unit to HCD.
Chapter 8. Optional feature codes for the DS8000 103
To Next Page
Loading...
Need help?
General