Chapter 5. Migration considerations 107
13.The next step is to merge the PCHID values assigned by the CHPID Mapping Tool with
the IODF being built. This is accomplished with the HCD migration function in HCD option
5.1. If your IODF contains more than one processor definition, then you will need to
identify the correct one in the Processor Id field. The data set that contains the output
from the CHPID Mapping Tool should be specified in the IOCP only input data set field.
The processing mode should be set to 2 (Save) and the migration option should be set to
3 (PCHIDs).
Once the PCHID values assigned by the CHPID Mapping Tool have been merged with the
IODF, it needs to be re-validated with HCD option 2.12.
14.The work IODF can now be used to create a Production IODF with HCD Option 2.1.
15.The hardware and IOCDS now need to be established for the z990 processor.
If this is an upgrade to an existing z900 and this is not part of a microprocessor cluster, a
new option has been created to allow you to write the z990 IOCDS to the existing z900
prior to the hardware being changed. This is known as the IOCDS Save/Restore function.
Initially, the z990 IOCDS is written to the z900 using HCD option 2.2. The IOCDS will be
shown as INVALID. This is then saved to the hard disk of the HMC. Following the
hardware upgrade, the IOCDS can be restored to the Support Element using the same
tool. The status is now changed to VALID and you can tailor your RESET, IMAGE and
LOAD profiles (step 16). Alternatively, this can be performed by standalone IOCP (see
step 15 c).
c. The hardware installation can now be performed.
d. If the new z990 has been connected as part of a microprocessor cluster and has been
defined with the network name and CPC name coded in the processor definition, the
IOCDS can be created on the target machine using HCD option 2.2. If the new z990 is
not part of a microprocessor cluster, the IOCP source statements need to be created
with HCD option 2.3 and transferred to the HMC.
Traditionally this has been done with diskettes; however, some large I/O configurations
may exceed the capacity of a diskette. If this situation should arise, the file should be
transformed into a zip file and stored on a diskette. The diskette can then be used as
input to the stand-alone IOCP program on the z990 for creation of the IOCDS.
16. The Reset, Image and Load profiles for the z990 operational environment can be
customized from the HMC. When the Image profiles are created, care should be taken to
assign the correct
LPAR id to each logical partition. The LPAR id is not the same as the
MIF Image id assigned in the HCD partition definition. The LPAR id is used primarily by
the STSI and STIDP instructions (usually for ISV software licensing) and
also by the
CFRM support
in z/OS for identifying the CFCC partitions.
17. Perform a Power -on Reset (POR) of the z990 server.
18. Images on the z990 server can now be IPLed.
5.3.3 Consolidating a zSeries or S/390 environment onto an installed z990
This process assumes that you have an already established z990 processor operational and
now wish to consolidate another S/390 or zSeries environment onto it. It assumes that the
existing workload is already running in LCSS 0. The procedure that follows documents the
steps you will need to take to move the existing S/390 or z900 workload into LCSS 1. (The
Tip: We recommend that you define and connect your z900 and z990 processors as
part of a microprocessor cluster to allow an IOCDS to be created directly from any
system without the need for manual file transfer.

Get IBM eServer zSeries 990 Technical Introduction now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.