IBM 990 - Manual (Page 128)

116 IBM
^
zSeries 990 Technical Guide
IBM z990 CHPID Mapping Tool (CMT)
The z990 CHPID Mapping Tool provides a mechanism to map CHPIDs onto PCHIDs as
required on a z990. Additional enhancements have been built into the CMT to cater for the
new requirements of the z; it provides the best availability recommendations for the installed
z990 features and defined configuration.
For further details on the CMT, refer to 4.2.1, “z990 configuration management” on page 116
for a brief introduction, and to IBM
^
zSeries Connectivity Handbook, SG24-5444, for
a comprehensive explanation.
4.2.1 z990 configuration management
The architectural enhancements of the z990 enforce a new approach to configuration
management. Every CHPID is mapped to a PCHID; it is mandatory that every CHPID has a
PCHID associated with it. For internal channels, such as IC links, and HiperSockets, CHPIDs
are not assigned a PCHID.
The z990 does not have default CHPIDs assigned to channel ports as part of the initial
configuration process. CHPIDs are assigned to physical channel path identifiers (PCHIDs) in
the IOCP input file. It is the customer’s responsibility to perform these assignments by using
the HCD/IOCP definitions or by importing the output of the CHPID Mapping Tool.
It is recommended that the CMT be used for all new build z990 configurations, or when
upgrading from a z900. It can also be used as part of standard hardware changes to your
installed z990.
The Channel Mapping Tool takes input from two sources:
1. The Configuration Report file (CFreport) produced by the IBM order tool (e-Config) can be
obtained from your IBM representative, or the Hardware Configuration File produced by
IBM manufacturing can be obtained from IBM Resource Link.
2. An IOCP statement file.
The following output is produced by the CMT:
Tailored reports. All reports should be saved for reference. The Port Report sorted by
CHPID number and location should be supplied to your IBM hardware service
representative for the z990 installation.
An IOCP input file with PCHIDs mapped to CHPIDs. This IOCP input file can then be
migrated back into HCD from which a production IODF can be built.
The configuration management process is reflected in Figure 4-5 on page 117.
Important: When an IOCP statement file is exported from a Validated Work IODF using
HCD, it must be imported back to HCD for the process to be valid. The IOCP file cannot be
used directly by the IOCP program.