IBM zSeries 800 Installation Manual

Also see for 800: Parts manual Product overview

Contents

″NOCHKCPC″ execution parameter option in IOCP, and write your new IOCDS tothe Support Element prior to the upgrade. This eliminates saving the IOCP sourceto a diskette and running Stand-alone IOCP during the install. Simply tell the installteam which IOCDS (A0-A3) you have pre-written with the new configuration.If you are installing a new processor, transfer the IOCP statements for yourconfiguration to a diskette. If necessary, the IOCP input file can be compressedusing a zip-compatible program. When the new system arrives, give the diskettecontaining the IOCP input statements to the install team.If you are installing a new processor, instead of using a diskette you can remotelywrite the IOCDS from an HCD that is running on an installed CPC in the sameHMC cluster. Inform the install team that plans are in place to use the ″Build andmanage S/390 microprocessor IOCDSs″ option in HCD to write the IOCDS.VSE/ESA™Develop the IOCP statements necessary to define your configuration and use thelevel of the ICP IOCP program that supports the new processor to verify the inputstatements. You do not need to initially assign PCHID values to the channel pathsin your configuration. You can use the CHPID Mapping Tool, available fromResource Link, to aid you in assigning PCHIDs to CHPIDs. The CHPID MappingTool updates the IOCP input and assigns PCHIDs to the CHPIDs.If upgrading from a 2064 z900 model at EC J10638 or later, use the″CHECKCPC=NO″ execution parameter option in IOCP, and write your new IOCDSto the Support Element prior to the upgrade. This eliminates saving the IOCPsource to a diskette and running Stand-alone IOCP during the install. Simply tell theinstall team which IOCDS (A0-A3) you have pre-written with the new configuration.If you are installing a new processor, transfer the IOCP statements for yourconfiguration to a diskette. If necessary, the IOCP input file can be compressedusing a zip-compatible program. When the new system arrives, give the diskettecontaining the IOCP input statements to the install team.OS/390 and z/OS HCDDevelop the configuration using HCD. You do not need to initially assign PCHIDvalues to the channel paths in your configuration. You can use the CHPID MappingTool, available from Resource Link, to aid you in assigning PCHIDs to CHPIDs.Build an IOCP input data set from a validated work IODF and use this as input tothe CHPID Mapping Tool. The CHPID Mapping Tool updates the IOCP input andassigns PCHIDs to the CHPIDs. Migrate the modified IOCP input file back into HCDafter PCHID numbers have been added to the file by the CHPID Mapping Tool. AnIOCDS can then be written in preparation for an upgrade using a production IODF.Note: An IOCP input file that was created by HCD without PCHIDs must bemigrated back into HCD after PCHID numbers have been added to the fileby the CHPID Mapping Tool. An IOCDS can then be written from aproduction IODF or IOCP statements can be built for the install diskette.If upgrading from a 2064 z900 model at EC J10638 or later, use the ″Write IOCDSin Preparation for an Upgrade″ option in HCD from a production IODF and writeyour new IOCDS to the Support Element prior to the upgrade. This eliminatessaving the IOCP source to a diskette and running Stand-alone IOCP during theinstall. Simply tell the install team which IOCDS (A0-A3) you have pre-written withthe new configuration.Level 04a, June 21, 2004Chapter 6. Cabling and Connectivity 6-21