3.2 Volumes
With VSE/ESA and the RVA, the subsystem volumes can be defined in different emulation modes. This makes the RVA absolutely adaptable to your needs.
The following device type emulations are supported with the RVA:
∙
∙
3380 model J, K, and KE (KE is a 3380K compatible device with the same number of cylinders (1770) as a 3380E).
3390 models 1, 2, and 3
3.3 Host Connection
Host connectivity options include parallel and/or ESCON attachment. Extended connectivity parallel channel configurations of up to 32 channels are available and supported without bus and tag output connections. The bus and tag outputs are internally terminated, so the RVA must physically be the last in a
The physical channel configuration must match the definitions in the I/O configuration data set (IOCDS). The physical connections on the CPU and the RVA must reflect the statements in the IOCDS. Mistakes can go undetected until later maintenance actions cause unnecessary impact. The channel configuration should be planned such that the impact of a single component failure is minimized. For an IOCDS example, refer to Appendix D, ªIOCDS Exampleº on page 63.
3.3.1 VSE/ESA Input/Output Configuration Program
Support for the
Before you install VSE/ESA natively (not under VM/ESA or an LPAR), make sure that you have fully configured your system through IOCP. Starting with VSE/ESA 1.3, the VSE/ESA IOCP is automatically installed during initial installation of VSE/ESA. You can use the IOCP batch program to create a new IOCDS when you change the hardware configuration. You can use the IOCP batch program to define and validate the IOCP macro instructions if you prepare for the installation of a new processor. Use skeleton SKIOCPCN (available in VSE/ICCF library 59) as a base for configuration changes.
An IOCDS must be generated for the hardware the first time through the
For more information about IOCP, refer to the processor′s IOCP manual and to the IOCP User′s Guide and ESCON