Overview; Planning The I/O Configuration; Planning Considerations; Hcd Function Support - IBM Z9 Planning Manual

Processor resource/systems manager
Table of Contents

Advertisement

Overview

This chapter describes planning considerations for I/O configuration and for
coupling facility LPs.

Planning the I/O Configuration

This section describes the planning considerations and guidelines for creating an
IOCDS. It assumes you understand the IOCP configuration and coding
requirements described in the Input/Output Configuration Program User's Guide,
SB10-7037.

Planning Considerations

PR/SM is standard on all System z9 models.

Control Program Support

The maximum number of supported devices is limited by the control program. In
planning an I/O configuration, installation management should be aware of the
maximum number of devices supported by the control program run in each LP.
Please see the user's guide for the respective operating systems.

Hardware Configuration Definition (HCD) Support

HCD supports definition of the I/O configuration for an entire installation. It is
required for parallel sysplex and LPAR clusters. A single I/O data file is created for
the installation and used for multiple machines and I/O configuration data sets.
HCD supports:
v Up to 60 logical partitions (LPs) per central processing complex (CPC)
v Coupling facility configurations
v Multiple Image Facility (MIF)
v Dynamic CHPID Management (DCM) channel paths.
v MCSS
v Assigning reserved logical partitions a meaningful name
Table 2-1. HCD Function Support
HCD Function
Define 60 logical partitions?
Define shared channel paths?
Define coupling facility channel paths?
Define dynamically managed channel paths?
Write IOCDSs remotely?
Access I/O devices on shared channel paths?
Use software-only dynamic I/O?
Notes:
1. HCD, running on z/OS allows you to remotely write IOCDSs from one CPC to another
CPC that is powered on, LAN-attached, enabled for remote LIC update, and defined to
the same Hardware Management Console.
2. HCD, running on z/VM, allows you to define coupling facility channel paths or managed
channel paths for a z/OS LP but z/VM does not support coupling facility channel paths
or dynamically managed channel paths for use by z/VM or guest operating systems.
z/OS
z/VM 5.3
Yes
Yes
Yes
Yes (Note 2)
Yes
Yes (Note 2)
Yes (Note 1)
Yes
Yes
Chapter 2. Planning Considerations
Yes
Yes
No
Yes
Yes
2-3

Advertisement

Table of Contents
loading

Table of Contents