Table of Contents (exploded view)
Abstract for HCD Planning
Summary of changes
Summary of changes
Summary of changes
z/OS Version 2 Release 1 summary of changes
Introduction
What an I/O configuration is
I/O configuration definition process
Defining an I/O configuration to the software
Hardware Configuration Definition (HCD)
Input/output definition file (IODF)
Unit information module (UIM)
Unit control block (UCB)
Eligible device table (EDT)
Defining a D/R Site Operating System (OS) configuration
Defining an I/O configuration to the hardware
I/O configuration program (IOCP)
Input/output configuration data set (IOCDS)
Hardware system area (HSA)
Ensuring that the software and hardware definitions match
Changing hardware and software I/O configuration definitions
Making software-only dynamic changes
Making both hardware and software dynamic changes
Using HCD I/O Autoconfiguration for automatic discovery of FICON connected DASD and tape control units and devices
Using HCM for I/O definition
Using CHPID Mapping Tool for assigning physical hardware attributes to CHPIDs
Planning your I/O configuration definition
Components of an I/O configuration
Logical channel subsystems
Logical partitions
Logical control units for I/O devices
Channel path numbering
Selection of the path to access an I/O device
Making decisions about your configuration
IBM zSeries and System z platform considerations
Defining operating system data
Defining switch data
Defining processor, PCIe-based functions,logical channel subsystem, partitions, channel path data, and subchannel sets
Defining multiple subchannel sets
Defining control unit data
Defining I/O device data
Deciding about JES3 initialization stream checker data
Understanding a sysplex configuration
Defining coupling facility components in a sysplex
Defining Server Time Protocol (STP) links in a sysplex
Reconfiguration of coupling facility receiver CHPIDs
Reconfiguring coupling facility peer CHPIDs
Managing IOCDSs and IPL attributes across a sysplex
Using automatic tape switching
Preparing for automatic tape switching
Deciding how to use automatically switchable devices
Operational considerations for automatic tape switching
Defining shared channel paths
Considerations for sharing channel paths
Defining logical partition access to a channel path
Processors communicating through shared ESCON or FICON channel paths
Using ESCON CTC connections
Using FICON CTC connections
Considerations for CTC connections, based on FICON channels
Defining dynamically managed channel paths
Defining spanned channel paths
Considerations for spanning channel paths
Creating over-defined channel paths
FICON channels
Channel path definitions
Dynamic activation
Migrating to FICON channels
Migrating from CNC to FCV channel paths
Migration from CNC or FCV to FC channel paths on the control unit
Open Systems Adapter Channels
Defining special devices and special secondary devices
Defining a special device (3390S)
Defining a special secondary device (3390D)
Defining a special FBA device (FBA)
Defining IQD CHPIDs and device types
Defining PCIe based functions (RoCE and zEDC)
Specifying an I/O device number
Replicating I/O device numbers
I/O device numbers for a parallel access volume
Workload manager and dynamic alias management
HyperPAV based dynamic PAV alias management
Specifying I/O device parameters and features
Defining whether an I/O device will be dynamic
Device support for dynamic configuration
Redefining the dynamic parameter for an I/O device
Defining a tape device as automatically switchable
Defining the location of an I/O device's unit control block (UCB)
Deciding whether to define above 16 megabyte UCBs
Case 1
Case 2
Case 3
Case 4
Case 5
Defining an above 16 megabyte UCB
Defining allocation preferences
Understanding I/O device allocation in z/OS
Indicating a specific device for allocation
Specifying a generic device type for allocation
Specifying an esoteric device group for allocation
Required esoteric device groups
Specifying order in an esoteric with the device preference table
Advantages of specifying an esoteric device group
Holding or releasing resources while a job waits
Device preference table's effect on UNIT=AFF request
Defining device allocation in HCD
Defining esoteric device groups in an EDT using HCD
Changing the device preference table order
Defining devices as virtual I/O (VIO) eligible
EDTs for dynamic configuration
Primary and secondary EDTs
Considerations for esoteric tokens
Migrating to subchannel sets
Example of migrating devices between subchannel sets
Device number alignment
Numbering schemes
Compacting or rolling reuse of addresses
Pairing addresses
Filling the device number ranges
Using HCD to move alias devices into a different subchannel set and closing the gaps in the device number range
Specifying an I/O configuration at IPL
Defining your initial I/O configuration
IODF processing at IPL
IODF statement in the LOADxx member
Search order for the LOADxx member and IODF
Specifying the IODF high-level qualifier
Specifying the IODF suffix
Specifying an operating system configuration ID
Specifying the EDT identifier
Using your initial I/O configuration with special secondary (3390D) devices for reIPL
Defining your I/O configuration for reIPL
Dynamically changing an I/O configuration
Changing or upgrading your processor configuration
Considerations when changing a support level of an existing processor
Considerations when upgrading an existing processor to a new processor type
Actions to change your configuration dynamically
Dynamically changing an I/O configuration in hardware
Dynamic I/O configuration considerations
Ensuring that you activate the correct IODF in step 1
Dynamic deletion of I/O hardware components requires FORCE
Dynamic deletion of I/O and coupling facility hardware components
Dynamic activation in a sysplex that includes a uniprocessor
Example of deleting an I/O device in LPAR mode
Dynamically adding and removing logical partitions to the I/O configuration
Dynamically changing an I/O configuration in a sysplex
Dynamically changing an I/O configuration in an HMC-attached processor control network
Dynamically changing component definitions
Making dynamic changes to I/O devices
Dynamically adding I/O devices
Dynamically deleting I/O devices
Dynamically changing I/O devices
Limitations on dynamic changes to I/O devices
Console devices
Considerations for z/OS installed products
Making dynamic changes to channel paths
Dynamically adding channel paths
Dynamically deleting channel paths
Dynamically changing channel paths
Making dynamic changes to control units
Dynamically adding control units
Dynamically deleting control units
Dynamically changing control units
Making changes to coupling facility devices and control units
Making the first channel path connection for a coupling facility
Making subsequent channel path connections for a coupling facility
Breaking a channel path connection that is not the last connection to a coupling facility
Breaking the last channel path connection to a coupling facility
Dynamic I/O configuration in a multiple LCSS environment
Testing dynamic activation
Recovery during dynamic configuration
Recovering LPAR mode dynamic configuration changes
Recovering original LPAR mode I/O configuration without system reset
Continuing LPAR mode I/O configuration changes without system reset
Recovering original LPAR mode I/O configuration with system reset
Continuing LPAR mode I/O configuration changes with system reset
Using HCM to migrate to supported system z processors with multiple channel subsystems
Configurations with logical definitions only
Configurations including physical definitions
Configuration and recovery scenarios
Migration of the CTC configuration from ESCON channel paths to FICON channel paths
Recovery of lost synchronization between Hardware System Area (HSA) and the active I/O configuration
Trademarks