Upgrading from an IBM System IBM zEnterprise 196 to an IBM zEnterprise EC12
This chapter describes how to upgrade an existing IBM System zEnterprise 196 to an IBM zEnterprise EC12.
You can also upgrade from a IBM System z10 Enterprise Class to an zEC12. However, only examples of upgrading or replacing a z196 are shown in detail. An upgrade includes all frames, cages, support cards, and new I/O features.
Because a wide variety of environments exists, the results achieved in your environment might differ from those described here. Nevertheless, the step-by-step process in this chapter should provide enough information for you to replicate the approach in your own environment.
This chapter includes the following sections:
4.1 Scenario overview
Here is a description of the upgrade scenario.
4.1.1 The configuration process
The ten I/O configuration steps that are described in Chapter 5, “I/O configuration process”, of I/O Configuration Using z/OS HCD and HCM, SG24-7804 are used for the example scenario.
Figure 4-1 shows the general process flow that is followed in the example. The numbered steps are described following the figure.
Figure 4-1 Overall configuration process flow
1. Initiation
a. When planning to migrate to a IBM zEnterprise EC12, the IBM Technical Support team can help you define a configuration design that meets your needs. The configuration is then used during the ordering process.
b. The IBM order for the configuration is created and passed to the manufacturing process.
c. The manufacturing process creates a configuration file that is stored at the IBM Resource Link website. This configuration file describes the hardware being ordered. This data is available for download by the client installation team.
d. A New Order report is created that shows the configuration summary of what is being ordered along with the Customer Control Number (CCN). The CNN can be used to retrieve CFReport (a data file that contains a listing of hardware configuration and changes for a central processor complex (CPC)) from Resource Link.
2. Prerequisites
Ensure that you have the current PSP Bucket installed. Also, run the SMP/E report with fixcat exceptions to determine whether any Program Temporary Fixes (PTFs) must be applied. Ensure that you have the most current physical channel ID (PCHID) report and CCN from your IBM service representative.
3. Design
When you plan your configuration, keep in mind these considerations:
 – Naming standards
 – FICON switch and port redundancy
 – Adequate I/O paths to your devices for performance
 – OSA Channel Path Identifier (CHPID) configuration for network and console communications
 – Coupling facility connections internally and to other systems.
More changes to the way your sysplex receives its time source after that external time reference (ETR) is not supported and only Server Time Protocol (STP) can be used on the zEC12 is required. The zEC12 can be run at Stratum 3 or Stratum 2 when in a mixed Coordinated Timing Network (CTN), or Stratum 1 when in a non-mixed CTN.
4. Define
The existing System z10 EC I/O or zEnterprise 196 configuration is used as a starting point for using Hardware Configuration Definition (HCD). The zEnterprise 196 production input/output definition file (IODF) is used as input to HCD to create a work IODF that becomes the base of the new zEC12 configuration.
When the new zEC12 configuration is added and the obsolete hardware is deleted, a validated version of the configuration is saved in a 2827 validated work IODF.
5. Check
a. From the validated work IODF, create a file that contains the zEC12 IOCP statements. This IOCP statements file is transferred to the workstation used for the CHPID Mapping Tool (CMT). HCM can also be used here to transfer the IOCP deck to and from the CMT.
b. The configuration file that is created by the IBM Manufacturing process in step 1d is downloaded from Resource Link to the CMT workstation.
The CMT uses the input data from the files to map logical channels to physical ones on the new zEC12 hardware.
You might have to make decisions in response to the following situations, among others:
i. Resolving situations in which the limitations on the purchased hardware cause a single point of failure (SPOF). You might must purchase more hardware to resolve some SPoF situations.
ii. Prioritizing certain hardware items over others.
c. After the CMT processing finishes, the IOCP statements contain the physical channels to logical channels assignment that is based on the actual purchased hardware configuration.
The CMT also creates configuration reports to be used by the IBM service representative and the installation team.
The file that contains the updated IOCP statements created by the CMT, which now contains the physical channels assignment, is transferred to the host system.
d. Use HCD, the validated work IODF file created in step 5a, and the IOCP statements updated by the CMT to apply the physical channel assignments created by the CMT to the configuration data in the work IODF.
6. Create
After the physical channel data is migrated into the work IODF, a 2827 production IODF is created and the final IOCP statements can be generated. The installation team uses the configuration data from the 2827 production IODF when the final power-on reset is done, yielding a zEC12 with an I/O configuration ready to be used.
7. Test
IODFs that are modifying existing configurations can be tested in most cases to verify that the IODF is making the intended changes.
8. Available
a. If you are upgrading an existing 2097 or 2817, you might be able to use HCD to write an IOCDS to your system in preparation for the upgrade. If you can write an IOCDS to your current system in preparation for upgrade, do so and let the IBM service representative know which IOCDS to use.
 
Tip: Using the HCD option Write IOCDS in preparation of an upgrade is the preferred method for writing the initial IOCDS when upgrading from a 2097 or a 2817 to a 2827. This scenario uses the HCD option Write IOCDS process.
b. If the 2827 is not network connected to the CPC where HCD is running, or if you are not upgrading or cannot write an IOCDS in preparation for the upgrade, use HCD to produce an IOCP input file. Download this input file to a USB flash drive.
9. Apply
The new production IODF can be applied to the zEC12 in these ways:
 – Using the Power-on Reset process
 – Using the Dynamic IODF Activate process
10. Communicate
It is important to communicate new and changed configurations to operations and the appropriate users and departments.
4.1.2 Migration path considerations
The migration path from a z10 EC or z196 to a zEC12 can be either in the form of a field upgrade to the existing z10 EC or z196, or a replacement (push/pull) of an existing z10 EC or z196 with a new zEC12. Note the following points:
1. A field upgrade means that the existing z10 EC or z196 EC processor serial number is retained during the upgrade.
2. A replacement of the existing z10 EC or z196 by a new zEC12 implies physically removing (push) the z10 EC or z196 and bringing in a new zEC12 (pull) to take its place. The replacement zEC12 has a new serial number that is different from that of the existing z10 EC or z196.
This chapter documents a field upgrade scenario.
4.1.3 Planning considerations
The following I/O features can be ordered for a new zEC12:
•FICON Express8S LX (long wavelength - 10 km)
•FICON Express8S SX (short wavelength)
•OSA-Express4S 10 GbE LR (long reach)
•OSA-Express4S 10 GbE SR (short reach)
•OSA-Express4S GbE LX (long wavelength)
•OSA-Express4S GbE SX (short wavelength)
•OSA-Express4S 1000BASE-T Ethernet
•Crypto Express4S
•Flash Express
The following features cannot be ordered for a zEC12, but if present in a z10 EC server or z196 server, can be carried forward when you upgrade to a zEC12:
•FICON Express8 LX (long wavelength - 10 km)
•FICON Express8 SX (short wavelength)
•FICON Express4 LX (long wavelength - 10 km)
•FICON Express4 SX (short wavelength)
•OSA-Express3 GbE LX (long wavelength)
•OSA-Express3 GbE SX (short wavelength)
•OSA-Express3 10 GbE LR (long reach)
•OSA-Express3 10 GbE SR (short reach)
•OSA-Express3 1000BASE-T Ethernet
•Crypto Express3
•ISC-3 (Peer mode only)
The following features are not supported on a zEC12:
•ESCON (use FICON converter)
•FICON Express2 (LX and SX)
•FICON Express (LX and SX)
•FICON (pre-FICON Express)
•OSA-Express2 10 GbE Long Reach
•OSA-Express
•ICB-2
•ICB-3
•ICB-4
•ISC-3 Links in Compatibility Mode
•Crypto Express2
•PCIXCC and PCICA
•Parallel channels (use FICON and ESCON converters)
Table 4-1 lists the channel types as described in an input/ouput configuration data set (IOCDS) that are supported by the z10 EC, z196, and zEC12.
Table 4-1 Channels, links, and adapters with CHPID type and support
Channels
CHPID Type
2097 support
2817 support
2827 support
ESCON channels:
Connection Channel (ESCON architecture)
Channel to Channel (connects to CNC)
Convert Channel Path (for BL types)
Convert Channel Path (for BY types)
 
CNC
CTC
CVC
CBY
 
YES
YES
YES
YES
 
Up to 240
Up to 240
Up to 240
Up to 240
 
 
No
FICON bridge. A FICON channel that attaches to an ESCON Director Model 5.
FCV
Yes
No
No
FICON native channels that attach to FICON directors or directly to FICON control units:
FICON Express 1 Gb SX and LX
FICON Express 2 Gb SX and LX
FICON Express 4 Gb SX and LX
FICON Express 8 Gb SX and LX
FICON Express 8S Gb SX and LX
 
 
FC
FC
FC
FC
FC
 
 
Yes
Yes
Yes
No
No
 
 
No
No
Carried forward Carried forward Up to 288
Yes
 
 
No
No
Carried forward
Carried forward
Carried forward
Up to 320
FICON channels that attach to Fibre Channel devices, switches, directors, or Fibre-Channel-to-SCSI bridges
FCP
Yes
Yes
Yes
ISC-3 peer mode channels (connects to another CFP)
CFP
Yes
Up to 48
Up to 48 carried forward
ICB-4 peer channels (connects to another ICB-4)
CBP
Yes
No
No
IC peer channels (connects to another ICP)
ICP
Yes
Up to 32
Up to 32
PSIFB 12x InfiniBand host channel adapters (HCA2-O)
PSIFB 12x InfiniBand host channel adapters (HCA3-O)
PSIFB 1x LR InfiniBand host channel adapters (HCA2-O)
PSIFB 1x LR InfiniBand host channel adapters (HCA3-O)
 
 
 
CIB
Yes
 
No
 
Yes
 
No
Up to 32
 
Up to 32
 
Up to 32
 
Up to 48
Up to 32
 
Up to 32
 
Up to 32
 
Up to 64
HiperSocket (IQDIO) channels
IQD
Yes
Up to 32
Up to 32
OSA-Express2 GbE LX/SX
OSD and OSN
Yes
Up to 48 ports carried forward
No
OSA-Express3 GbE LX/SX
OSD and OSN
Yes
Up to 96 ports
Carried forward
OSA Express4S GbE LX/SX
OSD
No
No
Up to 96 ports
OSA-Express2 1000BASE-T
OSE, OSD, OSC, and OSN
Yes
Up to 48 ports carried forward
No
OSA-Express3 1000BASE-T
OSE, OSD, OSC, OSN, and OSM
OSC, OSD, OSE, OSN-yes
 
OSM-no
Up to 96 ports
Up to 96 ports
Carried forward
OSA-Express4S 1000BASE-T
OSE,
OSD,
OSC,
OSN,
and OSM
No
Up to 96 ports
Up to 96 ports
OSA-Express2 10 GbE LR
OSD
Yes
No
No
OSA-Express3 10 GbE LR/SR
OSD and OSX
OSD: Yes
OSX1: No
Up to 48 ports
Carried forward
OSA-Express4S 10 GbE LR/SR
OSD and OSX
No
Up to 48 ports
Up to 48 ports
1 CHPID type OSX is not supported.
Keep the considerations in the following sections in mind when you are planning your configuration.
Coupling links
Only the following Coupling Facility CHPIDs are supported:
•CHPID Type=CFP: ISC-3 links in peer mode (carried forward only)
•CHPID Type=CIB: PSIFB links connecting to an HCA3-O, HCA3-O LR, HCA2-O (carried forward only), and HCA2-O LR (carried forward only)
•CHPID Type=ICP: Internal Coupling links
 
Considerations: Coupling links can be defined as both Coupling and STP links, or STP-only links. The zEC12 is the last server to support ISC-3 features. ISC-3 requires an I/O drawer or I/O cage (carried forward only)
The HMC
The HMC can be displayed either like the current HMC, or as an HMC that can run code to manage an Ensemble. The current HMC is used to manage, monitor, and operate one or more System z servers and their associated logical partitions. An HMC that has ensemble code running is attached to one or more zEnterprise Systems configured as Ensemble members. A particular Ensemble is managed by a pair of HMCs in primary and alternate roles.
The HMC has a global (Ensemble) management function, whereas the Support Element (SE) has local node management responsibility. When tasks are run on the HMC, the commands are sent to one or more SEs, which then issue commands to their CPCs
The zEC12 requires HMC Application V2.12.0 (driver level 12) or later and uses Ethernet only for its network connection. The HMC and the SEs do not have a floppy disk drive, requiring the use of a USB flash memory drive to input and back up client configuration data.
Software support
HCD V1.13 (or HCD V1.10 and later with Preventive Service Planning (PSP) bucket for 2827 DEVICE and PTFs) is required to define and support some of the new features of the zEC12.
Open Systems Adapter-Integrated Console Controller
Support has been withdrawn for the 2074 console controllers. Therefore, consider using OSA-Express3 1000BASE-T or OSA-Express4S 1000BASE-T CHPIDs defined as TYPE=OSC. With these OSA cards, you can set up a console function that is supported by a configuration file defined on the Support Element for that processor.
Fibre Channel Protocol
When you use CHPIDs defined as TYPE=FCP, consider N-Port ID Virtualization (NPIV).
For more information about Fibre Channel Protocol (FCP) CHPIDs and the new WWPN prediction tool to manage them, see 2.1.6, “Worldwide Port Name Prediction Tool” on page 33.
CPC name versus Processor ID
HCD allows you to define different processors (logical) to the same CPC (physical). The Processor ID must be unique within the same IODF, but the CPC name does not. Therefore, the CPC name does not need to match the Processor ID. This is useful when you might have several processor/logical partition/control unit setups that share a physical CPC within the same IODF. Furthermore, the Processor ID is what is defined for the HWNAME parameter in the LOAD member in SYS1.IPLPARM.
The CPC name is coded in HCD Option 1.3 under View Processor Definition in the CPC name field under SNA address, along with a Network name. It is the CPC name, and not the Processor ID, that is displayed on the HMC.
When you view the Network information for a CPC over the HMC, the SNA address is made up of a Network name and CPC name separated by a dot. For example, USIBMSC.SCZP401. These values are defined in the Support Element for the CPC. They must match the values that are set in the IODF so that HCD Option 2.11 can find the CPC to write an IOCDS in the S/390 Microprocessor Cluster List.
Local system name
An extra system name, LSYSTEM, is used to identify the local system name of a server when defining PSIFB type=CIB coupling links.
This data field can be found when you change a CIB-capable processor under HCD Option 1.3.
The LSYSTEM field can be set or changed to any one to eight alphanumeric characters, and also can begin with either an alphabetic or numeric character. All characters are uppercase.
The following rules determine whether, and where, HCD sets the LSYSTEM keyword automatically:
1. If a CIB-capable processor is defined and the CPC name is set but the local system name is not set, HCD defaults the local system name to the CPC name.
2. If a CIB-capable processor that has not yet defined a CPC name is changed to get a CPC name but no local system name, HCD defaults the CPC name to the local system name.
3. If a non-CIB capable processor is changed to a support level that is CIB capable, and the processor has a CPC name set but no local system name, the local system name is defaulted to the CPC name.
4. If the processor definition is changed such that the local system name is explicitly removed, HCD does not do any defaulting.
5. If a processor has a local system name set (whether it has a CPC name or not), any change to the local system name must be done explicitly. There is no implicit name if the CPC name or the support level is changed.
6. During Build Production IODF, a local system name must be set for the processor if the processor has a CIB channel path defined. If this verification fails, an error message is given and the production IODF is not built.
Generally, set the local system name to be the same as the CPC name.
The following are examples of extra keywords in the CHPID statement in an IOCP deck:
AID Adapter ID.
Port HCA port.
CPATH Specifies the CCSID and CHPID on the connecting system.
4.1.4 Miscellaneous Equipment Specification upgrade scenario
This scenario describes the configuration steps to upgrade an existing 2817 processor to a 2827 processor. The following are the key factors:
•HCD requires a new Processor ID for the 2827.
•Generally, keep the same CPC name for the 2827.
•The 2827 processor channels connect to the same switch ports and access the same control unit interfaces.
•The control unit interfaces connect to the same switch ports.
•The starting IODF is the current 2817 production IODF.
•The target IODF is a new 2827 work IODF.
•HCD actions:
 – Migrate updated IOCP statements.
 – Build production IODF.
 – Remote write IODF to IOCDS.
•The HMC actions:
 – Build Reset Profile and point to required IOCDS.
 – Build/verify Image Profiles.
 – Build/verify Load Profiles.
 – Run a power-on reset.
The example here uses a 2817-M32 with a Processor ID of SCZP301 and four channel subsystems (CSSs) (CSS ID=0, CSS ID=1, CSS ID=2, and CSS ID=3). It is being upgraded to a 2827-H43 with a Processor ID of SCZP401. The CPC name SCZP301 and serial number 0B3BD5 are not changed.
The following CHPID types are migrated:
•OSD and OSC
•CTC and CNC
•FC and FCP
•CFP and ICP
•IQD
The following Hardware/CHPID types are not supported and not migrated to the 2827:
•PCIXCC and PCICA
•ICB-4 links
•ICB-3 links
•ICB-2 links
•ISC-3 links in compatibility mode (CHPID types CFS and CFR)
•OSA-Express Token Ring
•FICON Express2 (CHPID type FCV)
•ESCON
Table 4-2 summarizes the migration options and tool requirements. The step-by-step process is documented later.
Table 4-2 2817 I/O configuration migrated to a 2827
2097 or 2817 to 2827
Upgrade an existing 2097 or 2817 to a 2827 (Miscellaneous Equipment Specification upgrade)
Processor ID
Required to change the Processor ID to a new ID
CPC name
Generally should be the same name
Channel to switch port connections
Same ports
Control Unit to switch port connections
Same ports
Starting IODF
Current active production IODF
Target IODF
Create a work IODF
HCD action
Repeat and change (see step 5 on page 160)
CHPID Mapping Tool Program
Optional, but quite useful
CFReport file (CCN)
Required for CMT
IOCP (import from validated work IODF)
Yes
CHPID Mapping Tool actions (PCHID reset)
Yes
CHPID Mapping Tool IOCP Output
Yes
CHPID Mapping Tool Reports
Yes, CHPID and CHPID to CU Report
4.2 Migrating the existing 2817 IODF
The following steps explain how to define the existing I/O configuration to the new 2827 server by using HCD. You then migrate the channel subsystem and logical partitions from the 2097 or 2817 to the 2827 server. Using HCD, the sequence of operations is as follows:
1. Create a work IODF from the current 2817 production IODF.
2. Upgrade the 2817 processor again.
3. Observe the CF link messages for later reference.
4. Delete unsupported items for the repeated 2817.
5. Change the repeated 2817 to a 2827, and delete the 2817.
6. Redefine all CF connections to other processors and any Internal CF required connections.
7. Define any additional CHPIDs, control units, and devices you want to add during the upgrade.
8. Overdefine channel paths where needed.
9. Save the OSA configuration information.
10. Build a 2827 validated work IODF.
11. Create an IOCP statements file and file transfer to your workstation. This step can be performed with HCM.
12. Import CFReport and IOCP statements into the CMT.
13. Perform hardware resolution and PCHID/CHPID availability.
14. Create configuration reports for yourself and the IBM service representative.
15. Import IOCP statements that are updated with PCHIDs back into the validated work IODF.
16. Build the production IODF.
17. Remote write the IOCP to an IOCDS on the processor.
18. Build Reset, Image, and Load Profiles if required.
19. Perform a power-on reset (activate) of the 2827.
4.2.1 Creating the work IODF from the current 2817 production IODF
Use HCD to select the current production IODF that contains the 2817 processor you are upgrading (for example, SYS6.IODF59).
4.2.2 Repeating the 2817 processor upgrade
To upgrade the 2817 processor again, complete the following steps:
1. From the main HCD panel, select Option 1.3. Processor List. Enter r (for repeat) next to the 2817 you want to upgrade and press Enter (Figure 4-2).
Processor List Row 1 of 5 More: >
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more processors, then press Enter. To add, use F11.
/ Proc. ID Type + Model + Mode+ Serial-# + Description
_ ISGSYN 2064 1C7 LPAR __________ z900____________________________
_ ISGS11 2064 1C7 LPAR __________ z900____________________________
_ SCZP101 2094 S18 LPAR 02991E2094 z9______________________________
_ SCZP201 2097 E26 LPAR 01DE502097 z10_____________________________
r SCZP301 2817 M32 LPAR 0B3BD52817 z196____________________________
Figure 4-2 Processor List (repeating processor)
2. The Identify Target IODF panel opens. Perform one of the following actions:
 – To retain all the other processor definitions in the IODF, press Enter.
 – Enter a Target IODF data set name. In this case, only the processor you are repeating is retained in the Target IODF.
3. The Create Work I/O Definition File panel now prompts you to enter the data set name of the Target IODF (for example, SYS6.IODF8A.WORK).
4. The Repeat Processor panel opens (Figure 4-3). Enter the Processor ID of the new 2827 (in this example, SCZP401), leave all the other fields unchanged, and press Enter to continue.
+----------------------------- Repeat Processor ------------------------------+
| |
| |
| Specify or revise the following values. |
| |
| Processor ID . . . . . . . . . SCZP401_ |
| |
| Processor type . . . . . . . : 2817 |
| Processor model . . . . . . : M32 |
| Configuration mode . . . . . : LPAR |
| |
| Serial number . . . . . . . . 0B3BD52817 |
| Description . . . . . . . . . Gryphon |
| |
| Specify SNA address only if part of an S/390 microprocessor cluster: |
| |
| Network name . . . . . . . . . USIBMSC + |
| CPC name . . . . . . . . . . . SCZP301 + |
| |
| Local system name . . . . . . SCZP301 |
| |
+------------------------------------+ |
| New IODF SYS6.IODF8A.WORK defined. | |
+------------------------------------+ ---------------------------------------+
Figure 4-3 Repeat Processor panel
4.2.3 CF Link information messages
At this point, you might receive Severity E, I, or W messages. As shown in Figure 4-4, CBDG441I, Severity I messages are displayed in the example because the CF Link CHPIDs were not copied over to the 2827 definition.
+------------------------------- Message List --------------------------------+
| Save Query Help |
| -------------------------------------------------------------------------- |
| Row 170 of 182 |
| Command ===> ___________________________________________ Scroll ===> CSR |
| |
| Messages are sorted by severity. Select one or more, then press Enter. |
| |
| / Sev Msg. ID Message Text |
| # 3.C4 of processor SCZP301 and channel path 3.C5 of |
| # processor SCZP301 is not copied. |
| _ I CBDG441I The coupling facility connection between channel path |
| # 3.C5 of processor SCZP301 and channel path 3.C4 of |
| # processor SCZP301 is not copied. |
| _ I CBDG441I The coupling facility connection between channel path |
| # 3.C6 of processor SCZP301 and channel path 3.C7 of |
| # processor SCZP301 is not copied. |
| _ I CBDG441I The coupling facility connection between channel path |
| # 3.C7 of processor SCZP301 and channel path 3.C6 of |
| # processor SCZP301 is not copied. |
| _ I CBDG271I Requested action on object SCZP301 successfully |
| # processed. |
| ***************************** Bottom of data ****************************** |
+-----------------------------------------------------------------------------+
Figure 4-4 Message List (CBDG441I)
To resolve this problem, complete the following steps:
1. Scroll down until you reach the end of the messages and see the CBDG271I requested action on object SCZP301 successfully processed message.
2. Press PF3 or PF12 to continue. As shown in Figure 4-5, there is now an extra 2817 processor called SCZP401.
Processor List Row 1 of 6 More: >
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more processors, then press Enter. To add, use F11.
/ Proc. ID Type + Model + Mode+ Serial-# + Description
_ ISGSYN 2064 1C7 LPAR __________ z900
_ ISGS11 2064 1C7 LPAR __________ z900
_ SCZP101 2094 S18 LPAR 02991E2094 z9
_ SCZP201 2097 E26 LPAR 01DE502097 z10
_ SCZP301 2817 M32 LPAR 0B3BD52817 z196
_ SCZP401 2817 M32 LPAR 0B3BD52817 zHelix
Figure 4-5 Processor List (repeated processor)
4.2.4 Changing the 2817 to a 2827 and deleting the 2817
You can either keep the original copy of the 2817 (SCZP301) or delete it from the IODF. In this example, keep it in the IODF for a few more steps.
To change the 2817 to a 2827, complete the following steps:
1. Enter c (for change) next to SCZP401 to change the 2817 to a 2827 and press Enter (Figure 4-6).
2. Make the following updates and press Enter:
 – Update Processor type to 2827.
 – Update Processor model to H43.
 – Update the 2817 part of the serial number to 2827 (that is, 0B3BD52817 to 0B3BD52827).
+------------------------ Change Processor Definition ------------------------+
| |
| |
| Specify or revise the following values. |
| |
| Processor ID . . . . . . . . : SCZP401 |
| Support level: |
| XMP, 2817 support, SS 2, 32 CIB CF LINKS |
| Processor type . . . . . . . . 2827 + |
| Processor model . . . . . . . H43 + |
| Configuration mode . . . . . . LPAR + |
| |
| Serial number . . . . . . . . 0B3BD52827 + |
| Description . . . . . . . . . ZHELIX |
| |
| Specify SNA address only if part of an S/390 microprocessor cluster: |
| |
| Network name . . . . . . . . . USIBMSC + |
| CPC name . . . . . . . . . . . SCZP301 + |
| |
| Local system name . . . . . . SCZP301 |
| |
| |
+-----------------------------------------------------------------------------+
Figure 4-6 Change Processor Definition (changing repeated processor)
c. Press Enter. In the example, the CNC type CHPIDs are deliberately left defined in the processor that is being upgrading to demonstrate the error message received when you upgrade a processor definition with unsupported CHPID types (Figure 4-7).
+------------------------------- Message List --------------------------------+
| Save Query Help |
| -------------------------------------------------------------------------- |
| Row 1 of 34 |
| Command ===> ___________________________________________ Scroll ===> CSR |
| |
| Messages are sorted by severity. Select one or more, then press Enter. |
| |
| / Sev Msg. ID Message Text |
| _ E CBDA154I Channel path type CNC is not supported by channel path |
| # ID 0.30. |
| _ E CBDA440I Operation mode SHR not allowed for channel path 0.30 of |
| # type CNC. |
| _ E CBDA154I Channel path type CNC is not supported by channel path |
| # ID 0.31. |
| _ E CBDA440I Operation mode SHR not allowed for channel path 0.31 of |
| # type CNC. |
| _ E CBDA154I Channel path type CNC is not supported by channel path |
| # ID 0.32. |
| _ E CBDA440I Operation mode SHR not allowed for channel path 0.32 of |
| # type CNC. |
| _ E CBDA154I Channel path type CNC is not supported by channel path |
| # ID 0.33. |
+-----------------------------------------------------------------------------+
+-------------------------------------------------------------+
| The change of processor rules leads to invalid definitions. |
+-------------------------------------------------------------+
Figure 4-7 CBDA154I error message when you change a model with CNC definitions
3. Press PF12 twice to return to the processor list and delete all unsupported CHPID types, and then complete the change processor type step again.
4. Press Enter. The Update Channel Path Identifiers panel opens (Figure 4-8). No changes are made in this example.
+--------------------- Update Channel Path Identifiers ----------------------+
| Row 1 of 105 |
| Command ===> __________________________________________ Scroll ===> CSR |
| |
| Specify any changes to the channel path identifiers in the list below. |
| |
| Processor ID . . . . : SCZP401 zHelix |
| Channel Subsystem ID : 0 |
| |
| CHPID Type Side Until CHPID New CHPID + |
| 00 OSD __ 00 |
| 01 OSC __ 01 |
| 06 OSD __ 06 |
| 08 OSD __ 08 |
| 0A OSM __ 0A |
| 0B OSM __ 0B |
| 0C OSD __ 0C |
| 0D OSC __ 0D |
| 10 OSD __ 10 |
| 11 OSD __ 11 |
| 12 OSD __ 12 |
| 13 OSD __ 13 |
| 18 OSX __ 18 |
+----------------------------------------------------------------------------+
Figure 4-8 Update Channel Path Identifiers (not changed)
Press Enter for each of the Channel Subsystem IDs.
The repeated 2817 processor is successfully changed to a 2827-H43 as shown in Figure 4-9.
------------------------------------------------------------------------------
Processor List Row 1 of 6 More: >
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more processors, then press Enter. To add, use F11.
/ Proc. ID Type + Model + Mode+ Serial-# + Description
_ ISGSYN 2064 1C7 LPAR __________ z900
_ ISGS11 2064 1C7 LPAR __________ z900
_ SCZP101 2094 S18 LPAR 02991E2094 z9
_ SCZP201 2097 E26 LPAR 01DE502097 z10
_ SCZP301 2817 M32 LPAR 0B3BD52817 z196
_ SCZP401 2827 H43 LPAR 0B3DB52827 zHelix
Figure 4-9 Processor List (changed processor)
4.2.5 Deleting the 2817 processor definition
Now that the 2817 has been repeated and changed to a 2827, the original 2817 definition (SCZP301) must be deleted so that the required CF Links can be restored.
To delete the 2817 processor definition, complete the following steps:
1. Enter d (for delete) next to the SCZP301 processor in the Processor List (Figure 4-10).
                                 Processor List Row 1 of 6 More: >
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more processors, then press Enter. To add, use F11.
/ Proc. ID Type + Model + Mode+ Serial-# + Description
_ ISGSYN 2064 1C7 LPAR __________ z900
_ ISGS11 2064 1C7 LPAR __________ z900
_ SCZP101 2094 S18 LPAR 02991E2094 z9
_ SCZP201 2097 E26 LPAR 01DE502097 z10
d SCZP301 2817 M32 LPAR 0B3BD52817 z196
_ SCZP401 2827 H43 LPAR 0B3BD52827 zHelix
Figure 4-10 Processor List (deleting processor)
2. Press Enter to confirm the deletion of the processor (Figure 4-11).
                                 Processor List Row 1 of 5 More: >
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more processors, then press Enter. To add, use F11.
/ Proc. ID Type + Model + Mode+ Serial-# + Description
_ ISGSYN 2064 1C7 LPAR __________ z900
_ ISGS11 2064 1C7 LPAR __________ z900
_ SCZP101 2094 S18 LPAR 02991E2094 z9
_ SCZP201 2097 E26 LPAR 01DE502097 z10
_ SCZP401 2827 H43 LPAR 00B3D52827 zHelix
Figure 4-11 Processor List (processor deleted)
4.2.6 Reconnecting the CF channel paths there were not migrated
Manually redefine the CF Links that you want from the SCZP401 processor to any other processor, along with any wanted Internal Coupling Facility links. To help you with this effort, you can get a CF connection report from the previous production IODF containing the 2817. Alternatively, you can make a note of all CBDG441I error messages that you received in the previous step.
4.2.7 Defining more I/O
Define any additional CHPIDs, control units and devices, channel-to-channel connections (CTCs), and so on, that you might be adding into the 2827 during the upgrade. In the example, because you plan to connect the zEC12 to an IBM zEnterprise BladeCenter® Extension (zBX) in the future, define the new OSA type CHPIDs OSM and OSX. Figure 4-12 shows the new device type=OSA-M connected to control unit type=OSM, which is connected to the new CHPID type=OSM.
                              I/O Device List Row 1 of 2 More:
Command ===> ___________________________________________ Scroll ===> CSR
Select one or more devices, then press Enter. To add, use F11.
Control unit number : 3200 Control unit type . : OSM
----------Device------ --#--- --------Control Unit Numbers + --------
/ Number Type + CSS OS 1--- 2--- 3--- 4--- 5--- 6--- 7--- 8---
_ 3200,15 OSA-M 5 3200 ____ ____ ____ ____ ____ ____ ____
_ 320F OSAD 1 3200 ____ ____ ____ ____ ____ ____ ____
Figure 4-12 OSM I/O Device List sample definition
When you defining CHPID type=OSM, priority queuing must be disabled. Specify Yes in the Will greater than 160 TCP/IP stacks be required for this channel field in the HCD when you are defining or modifying the CHPID definition (Figure 4-13).
+----------- Allow for more than 160 TCP/IP stacks -----------+
| |
| |
| Specify Yes to allow more than 160 TCP/IP stacks, |
| otherwise specify No. Specifying Yes will cause priority |
| queuing to be disabled. |
| |
| Will greater than 160 TCP/IP stacks |
| be required for this channel? . . . Yes |
| |
| |
+-------------------------------------------------------------+
Figure 4-13 OSM allowing more than 160 TCP/IP stacks
Figure 4-14 shows the new device type=OSA-X connected to control unit type=OSX, which is connected to the new CHPID type=OSX.
                             I/O Device List Row 1 of 2 More: >
Command ===> ___________________________________________ Scroll ===> CSR
Select one or more devices, then press Enter. To add, use F11.
Control unit number : 3400 Control unit type . : OSX
----------Device------ --#--- --------Control Unit Numbers + --------
/ Number Type + CSS OS 1--- 2--- 3--- 4--- 5--- 6--- 7--- 8---
_ 3400,254 OSA-X 1 1 3400 ____ ____ ____ ____ ____ ____ ____
_ 34FE OSAD 1 1 3400 ____ ____ ____ ____ ____ ____ ____
Figure 4-14 OSX I/O Device List sample definition
4.2.8 Overdefining channel paths on an XMP processor
Sometimes you might need to define a channel path that is not physically installed on the processor. This path can be useful if you are planning to add more channel cards to the processor in the future and want to have the definitions in the IODF before the hardware is installed.
With HCD, you can overdefine CHPIDs by using an asterisk (*) for the PCHID value. An overdefined CHPID must adhere to all the validation rules, but it is not taken into account by an IOCDS download. Also, it is not included in the IOCP statements, in a CONFIGxx member, or during dynamic activation.
If a control unit contains only CHPIDs with a PCHID value of an asterisk (*), the whole control unit (including any attached devices) is omitted from the configuration to be activated.
When you install the channel path later, edit the CHPID and replace the * with its valid PCHID.
 
Consideration: This configuration is not the case for CFP type CHPIDs, where the CHPIDs have connections to other CFP type CHPIDs. Therefore, HCD only allows you to define CFP type CHPIDs as overdefined if they are unconnected.
Overdefining is now supported for CIB type CHPID definitions.
The 2827 production IODF can then be activated dynamically and the PCHID/CHPID/control unit definitions become available to the operating system.
Figure 4-15 shows what the CHPID/PCHID definitions look like before they are defined as overdefined. Press PF20 (right) in the Channel Path List.
                              Channel Path List Row 1 of 107 More: <
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more channel paths, then press Enter. To add, use F11.
Processor ID : SCZP401 CSS ID : 0
1=OS A01 2=OS A02 3=OS A03 4=OS A04 5=OS A05
6=OS A06 7=OS A07 8=OS A08 9=OS A09 A=OS A0A
B=OS A0B C=CF A0C D=CF A0D E=CF A0E F=CF A0F
PCHID I/O Cluster --------- Partitions 0x -----
/ CHPID AID/P Type+ Mode+ Mng Name + 1 2 3 4 5 6 7 8 9 A B C D E F
_ 5F 271 FC SPAN No ________ a a a a a a a a a a a _ _ _ _
_ 60 1D1 FC SPAN No ________ a a a a a a a a a a a _ _ _ _
_ 61 5C3 FC SPAN No ________ _ _ _ _ _ a _ _ _ a _ _ _ _ _
_ 62 1A3 FC SPAN No ________ _ _ _ _ _ a _ _ _ a _ _ _ _ _
_ 63 553 FC SPAN No ________ a a a a a a a a a a _ _ _ _ _
_ 64 153 FC SPAN No ________ _ _ _ _ _ _ _ a a _ _ _ _ _ _
_ 65 2A3 FC SPAN No ________ _ _ _ _ _ _ _ a a _ _ _ _ _ _
_ 66 243 FC SPAN No ________ _ _ _ _ _ a _ _ _ a _ _ _ _ _
Figure 4-15 Channel Path List (Reserving CHPIDs)
Figure 4-16 shows what the CHPID/PCHID definitions look like after they are defined as overdefined.
                              Channel Path List Row 22 of 109 More: >
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more channel paths, then press Enter. To add, use F11.
Processor ID : SCZP401 CSS ID : 0
1=OS A01 2=OS A02 3=OS A03 4=OS A04 5=OS A05
6=OS A06 7=OS A07 8=OS A08 9=OS A09 A=OS A0A
B=OS A0B C=CF A0C D=CF A0D E=CF A0E F=CF A0F
PCHID I/O Cluster --------- Partitions 0x -----
/ CHPID AID/P Type+ Mode+ Mng Name + 1 2 3 4 5 6 7 8 9 A B C D E F
_ 5F 271 FC SPAN No ________ a a a a a a a a a a a _ _ _ _
_ 60 1D1 FC SPAN No ________ a a a a a a a a a a a _ _ _ _
_ 61 5C3 FC SPAN No ________ _ _ _ _ _ a _ _ _ a _ _ _ _ _
_ 62 *     FC SPAN No ________ _ _ _ _ _ a _ _ _ a _ _ _ _ _
_ 63 *     FC SPAN No ________ a a a a a a a a a a _ _ _ _ _
_ 64 *     FC SPAN No ________ _ _ _ _ _ _ _ a a _ _ _ _ _ _
_ 65 2A3 FC SPAN No ________ _ _ _ _ _ _ _ a a _ _ _ _ _ _
_ 66 243 FC SPAN No ________ _ _ _ _ _ a _ _ _ a _ _ _ _ _
Figure 4-16 Channel Path List (overdefined CHPIDs)
4.3 OSA: Saving and restoring configuration
When you upgrade a z10 EC or z196 to a zEC12, the Open Systems Adapter (OSA) configuration data such the OSA Address Table (OAT) is not migrated automatically. So you must save OSA configuration data on z10 EC or z196 and restore it to zEC12 manually.
This operation depends on the CHPID type that is defined for OSA. If you define OSA as OSE (non-QDIO mode), you must use OSA/SF to save and restore its configuration. For other CHPID types, OSA/SF is not required. If you need to change the port speed or the MAC address, you can configure it from the OSA Advanced Facility through the HMC. The OSA CHPID type and OSA/SF requirements are listed in Table 4-3.
Table 4-3 OSA/SF and OSA CHPID reference
OSA CHPID type
OSA/SF
OSE
Required
OSD
Not required
OSN
Not required
OSC
Not supported
OSX
Not supported
OSM
Not supported
 
Requirement: You must save or import OSA configuration before you upgrade to zEC12.
For more information about OSC channel, see 4.3.2, “Saving and restoring OSA Integrated Console Controller configuration” on page 181.
4.3.1 Saving and restoring OSE channel configuration using OSA/SF
OSA/SF includes a graphical user interface (GUI) and a REXX interface. The OSA/SF GUI runs on Windows and Linux software that have graphics and Java 1.4 support. From a single OSA/SF GUI, you can establish connections to all server images that have OSA/SF running. You can use this setup to have centralized control of OSA-Express features that span server boundaries.
Figure 4-17 shows the OSA/SF configuration.
Figure 4-17 OSA/SF
Using OSA/SF, you can save the OSA-Express2/3/4s OAT and configuration file. For more information about setting up OSA/SF, see Open Systems Adapter-Express Customer’s Guide and Reference, SA22-7935 and OSA-Express Implementation Guide, SG24-5948. If you define OSE channel, this operation is mandatory.
The OSA/SF REXX interface is used in the example environment.
Saving the current OSE channel configuration
You can save following two OSA configuration files with OSA/SF:
OSA Address Table (OAT) This is the SNA device definition, mapping table for TCP/IP. When you define OSE channel, you must save this file.
Configuration File This is the configuration for port speed, local MAC Address, and SNA LLC2 timer. You must save this file if you define the SNA LLC2 timer. Other items can be defined on OSA Advanced Facility.
To save and restore the configurations of your OSA-Express features with the OSA/SF, complete the following steps:
 
Remember: Contents of OSA/SF REXX interface might be different depending on the OSA/SF FMID and APAR level.
Saving OAT with OSA/SF
To save the OAT with OSA/SF, complete these steps:
1. Start OSA/SF REXX interface (typically through execution of IOACMD) to open the menu that is shown in Figure 4-18. Select 6 Get OSA Address Table.
IOACMD: Enter the command to be issued
IOACMD: 0 - End IOACMD
IOACMD: 1 - Clear Debug
IOACMD: 2 - Configure OSA CHPID
IOACMD: 3 - Convert OAT
IOACMD: 4 - Get Configuration File
IOACMD: 5 - Get Debug
IOACMD: 6 - Get OSA Address Table
IOACMD: 7 - Install
IOACMD: 8 - Put OSA Address Table (OSA-2 only)
IOACMD: 9 - Query
IOACMD:10 - Set Parameter
IOACMD:11 - Shutdown (VM only)
IOACMD:12 - Start Managing
IOACMD:13 - Stop Managing
IOACMD:14 - Synchronize (OSA-2 only)
6
Figure 4-18 OSA/SF REXX interface menu
2. Enter the CHPID for the OAT you want to save. In the example, specify 00 for CHPID. (Figure 4-19)
IOACMD: Enter 0 to get help information for GET_OSA_ADDRESS_TABLE
IOACMD: Anything else to continue prompting for parameters
IOACMD: Enter CHPID -OR- 'quit' to end IOACMD
00
 
Figure 4-19 OSA/SF REXX interface GET OAT-1
3. Enter a dataset name to save the OAT file. In the example, specify ‘SYS1.OSASF.OATCHP00 (Figure 4-20).
IOACMD: Enter dataset name (Required input)
IOACMD: -OR-
IOACMD: Enter 'quit' to exit IOACMD
'SYS1.OSASF.OATCHP00'
Figure 4-20 OSA/SF REXX interface GET OAT-2
4. Enter a VOL=SER name for the data set that you specified for OAT. If nothing is specified, the default VOL=SER is used. The default is used in the example as shown in Figure 4-21.
IOACMD: Enter the VOLSER to use for 'SYS1.OSASF.OATCHP00'
IOACMD: Format is either VOLSER or VOLSER(UNIT)
IOACMD:
IOACMD: -OR- hit ENTER to let the system default the VOLSER
IOACMD: -OR- 'quit' to end IOACMD
Figure 4-21 OSA/SF REXX interface GET OAT-3
5. The message shown in Figure 4-22 is displayed. Verify whether OAT data is successfully saved by viewing the output data set.
IOACMD: Calling host OSA/SF...
IOACMD: Back from host OSA/SF...
IOACMD: *******************************
IOAK000I Command completed successfully
IOACMD: *******************************
IOACMD: Processing of GET OSA Address Table complete
IOACMD: *************************************************
IOACMD: Data received is in dataset 'SYS1.OSASF.OATCHP00'
IOACMD: *************************************************
IOACMD: Output complete for Get OSA Address Table
***
Figure 4-22 OSA/SF REXX interface GET OAT-4
Your OAT file should look similar to the sample show in Example 4-1.
Example 4-1 OAT file sample
********************************* Top of Data**********************************
************************************************************************
*** OSA/SF Get OAT output created 12:00:00 on 07/17/2012 ***
*** IOACMD APAR level - OA26486 ***
*** Host APAR level - OA36438. ***
************************************************************************
*** Start of OSA address table for CHPID 00 ***
************************************************************************
* UA(Dev) Mode Port Entry specific information Entry Valid
*************************************************************************
Image 0.1 (A01)
00(0530)* PASSTHRU 00 NO 10.3.1.10 SIU ALL
10.1.1.10
02(0532) SNA 00 SIU ALL
03(0533) N/A N/A CSS
04(0534) N/A N/A CSS
05(0535) N/A N/A CSS
06(0536) N/A N/A CSS
07(0537) N/A N/A CSS
08(0538) N/A N/A CSS
09(0539) N/A N/A CSS
0A(053A) N/A N/A CSS
0B(053B) N/A N/A CSS
0C(053C) N/A N/A CSS
0D(053D) N/A N/A CSS
0E(053E) N/A N/A CSS
Saving the configuration file with OSA/SF
To save the configuration file with OSA/SF, complete these steps:
1. Start OSA/SF REXX interface. Select 4 Get Configuration File. (Figure 4-23)
IOACMD: Enter the command to be issued
IOACMD: 0 - End IOACMD
IOACMD: 1 - Clear Debug
IOACMD: 2 - Configure OSA CHPID
IOACMD: 3 - Convert OAT
IOACMD: 4 - Get Configuration File
IOACMD: 5 - Get Debug
IOACMD: 6 - Get OSA Address Table
IOACMD: 7 - Install
IOACMD: 8 - Put OSA Address Table (OSA-2 only)
IOACMD: 9 - Query
IOACMD:10 - Set Parameter
IOACMD:11 - Shutdown (VM only)
IOACMD:12 - Start Managing
IOACMD:13 - Stop Managing
IOACMD:14 - Synchronize (OSA-2 only)
4
Figure 4-23 OSA/SF REXX Interface GET Config file-1
2. Enter the CHPID for the configuration file you want to save. In the example, specify 00 for CHPID (Figure 4-24).
IOACMD: Enter 0 to get help information for GET_CONFIG
IOACMD: Anything else to continue prompting for parameters
IOACMD: Enter CHPID -OR- 'quit' to end IOACMD
00
Figure 4-24 OSA/SF REXX Interface GET Config file-2
3. Enter a dataset name to save the configuration file. In the example, specify 'SYS1.OSASF.CONFIG00 as shown in Figure 4-25.
IOACMD: Enter dataset name (Required input)
IOACMD: -OR-
IOACMD: Enter 'quit' to exit IOACMD
'SYS1.OSASF.CONFIG00'
Figure 4-25 OSA/SF REXX Interface GET Config file-3
4. The message shown in Figure 4-26 is displayed. Check whether your configuration file is successfully saved.
IOACMD: Calling host OSA/SF...
IOACMD: Back from host OSA/SF...
IOACMD: *******************************
IOAK000I Command completed successfully
IOACMD: *******************************
IOACMD: ************************************************************
IOACMD: Data from Get Configuration File is in 'SYS1.OSASF.CONFIG00'
IOACMD: ************************************************************
IOACMD: Output complete for get configuration file
***
Figure 4-26 OSA/SF REXX Interface GET Config file-4
Your configuration file should be similar to the sample shown in Example 4-2.
Example 4-2 Sample Configuration file
/*======================================================================
/* Ethernet parameters for port 0
/*======================================================================
fenet.0.1 = IBM Default Configuration File /* Configuration name (32-char max
fenet.0.2 = /* User data (32-char max)
fenet.0.3 = /* Port name (8-char max)
/* Data ignored for OSD CHPIDs
fenet.0.4 = 000000000000 /* Local MAC address (12 hex digits)
fenet.0.5 = Auto /* Speed/mode
/* Auto - auto negotiate
/* 10H - 10 Mb, half duplex
/* 10F - 10 Mb, full duplex
/* 100H - 100 Mb, half duplex
/* 100F - 100 Mb, full duplex
/* 1000F - 1000 Mb, full duplex
/* (only valid for 1000Base-T)
/*======================================================================
/* Ethernet parameters for port 1
/*======================================================================
fenet.1.1 = IBM Default Configuration File /* Configuration name (32-char max
fenet.1.2 = /* User data (32-char max)
fenet.1.3 = /* Port name (8-char max)
/* Data ignored for OSD CHPIDs
fenet.1.4 = 000000000000 /* Local MAC address (12 hex digits)
fenet.1.5 = Auto /* Speed/mode
/* Auto - auto negotiate
/* 10H - 10 Mb, half duplex
/* 10F - 10 Mb, full duplex
/* 100H - 100 Mb, half duplex
/* 100F - 100 Mb, full duplex
/* 1000F - 1000 Mb, full duplex
/* (only valid for 1000Base-T)
Editing the OAT and configuration file
You saved current OSA configuration in “Saving the current OSE channel configuration” on page 172. Edit both OAT file and Configuration file for zEC12 as needed. Depending on your configuration for the zEC12, your CHPID or IODEVICE number for OSA might change.
When you edit the OAT and Configuration file, generally use a new default file from OSA. This is especially important if you migrate from OSA-Express2 to OSA-Express4s because the number of ports is changed.
You can get a default OAT and Configuration file using OSA/SF from a newly installed OSA CHPID in “Saving OAT with OSA/SF” on page 173 and “Saving the configuration file with OSA/SF” on page 175. This time, specify the new OSA CHPID number for these operations.
For more information about editing OAT and Configuration file, see Open Systems Adapter-Express Customer’s Guide and Reference, SA22-7935.
Installing and activating the OAT and configuration file using OSA/SF
When you finish editing the OAT and Configuration files, install those files into the OSE channel by using OSA/SF:
1. Start OSA/SF and select 2 Configure OSA CHPID (Figure 4-27).
IOACMD: Enter the command to be issued
IOACMD: 0 - End IOACMD
IOACMD: 1 - Clear Debug
IOACMD: 2 - Configure OSA CHPID
IOACMD: 3 - Convert OAT
IOACMD: 4 - Get Configuration File
IOACMD: 5 - Get Debug
IOACMD: 6 - Get OSA Address Table
IOACMD: 7 - Install
IOACMD: 8 - Put OSA Address Table (OSA-2 only)
IOACMD: 9 - Query
IOACMD:10 - Set Parameter
IOACMD:11 - Shutdown (VM only)
IOACMD:12 - Start Managing
IOACMD:13 - Stop Managing
IOACMD:14 - Synchronize (OSA-2 only)
2
Figure 4-27 OSA/SF REXX Interface Configure OSA CHPID-1
2. The message shown in Figure 4-28 is displayed. Select the appropriate OSA-Express feature to match the OAT and Configuration files. In the example, select 7 configure a non QDIO (OSE) OSA-Express3 Ethernet CHPID (Figure 4-28 on page 178).
IOACMD: Enter 'quit' to end IOACMD
IOACMD: Enter 0 for help
IOACMD: Enter 1 to configure an OSA-2 ATM CHPID
IOACMD: Enter 2 to configure an OSA-2 FDDI, ENTR, fast Ethernet CHPID
IOACMD: Enter 3 to configure an OSA-Express gigabit Ethernet CHPID
IOACMD: Enter 4 to configure an OSA-Express ATM CHPID
IOACMD: Enter 5 to configure an OSA-Express fast Ethernet or
an OSA-Express 1000Base-T Ethernet CHPID
IOACMD: Enter 6 to configure an OSA-Express token ring CHPID
IOACMD: Enter 7 to configure a non QDIO (OSE) OSA-Express3 Ethernet CHPID
IOACMD: Enter a blank line to get a list of valid OSA CHPIDs
7
Figure 4-28 OSA/SF REXX Interface Configure OSA CHPID-2
3. Specify a CHPID to configure the OAT and Configuration files. In the example, specify CHPID for 00 (Figure 4-29).
IOACMD: Enter CHPID -OR- 'quit' to end IOACMD
00
Figure 4-29 OSA/SF REXX Interface Configure OSA CHPID-3
4. On the next step, enter N to Is CHPID 0 of type OSD (QDIO)? and specify the dataset names that contain the OAT and Configuration files. For the example, specify the same data set name that you used for Get OAT and Get Configuration File (Figure 4-30).
IOACMD: Is CHPID 0 of type OSD (QDIO)? (y/N)
n
IOACMD: Enter the name of the configuration file containing
IOACMD: the OSA-Express fast Ethernet/1000Base-T parameters.
IOACMD: -OR-
IOACMD: 'quit' to end IOACMD
'SYS1.OSASF.CONFIG00'
IOACMD: Enter the name of the dataset containing the OAT you
IOACMD: want to put on the OSA
IOACMD: (This should be in the same format returned by Get OAT)
IOACMD: -OR-
IOACMD: Enter 0 to exit this EXEC
'SYS1.OSASF.OAT00'
Figure 4-30 OSA/SF REXX Interface Configure OSA CHPID-4
5. For What action should be taken for this configuration?, enter 1 to set the OAT and Configuration file action for this operation (Figure 4-31).
IOACMD: What action should be taken for this configuration?
IOACMD: 0 - Quit
IOACMD: 1 - Activate
IOACMD: Sets up all the files and transfers the data to the CHPID
IOACMD: If there are any 'in use' OAT entries, 'activate' will fail
IOACMD: 2 - Activate, no Install
IOACMD: Only sets up the files, but does not transfer them to the CHPID
IOACMD: You must issue the Install command at a later time
IOACMD: to complete the activation
1
Figure 4-31 OSA/SF REXX Interface Configure OSA CHPID-5
6. For the next question, enter anything but QUIT. Enter quit only if you want to end the activate processing. Press enter to proceed with the operation. You get a Command completed successfully message several times. After the operation is completed, you get an IOACMD: The Configure OSA command has completed message (Figure 4-32).
IOACMD: What action should be taken for this configuration?
IOACMD: 0 - Quit
IOACMD: 1 - Activate
IOACMD: Sets up all the files and transfers the data to the CHPID
IOACMD: If there are any 'in use' OAT entries, 'activate' will fail
IOACMD: 2 - Activate, no Install
IOACMD: Only sets up the files, but does not transfer them to the CHPID
IOACMD: You must issue the Install command at a later time
IOACMD: to complete the activation
1
IOACMD: To end 'activate' processing, enter 'QUIT'
IOACMD: To proceed with processing, enter anything else
IOACMD: About to issue an OSA/SF Query
IOACMD: Calling host OSA/SF...
IOACMD: Back from host OSA/SF...
IOACMD: *******************************
***
IOAK000I Command completed successfully
IOACMD: *******************************
IOACMD: About to query CHPID 1
IOACMD: Calling host OSA/SF...
IOACMD: Back from host OSA/SF...
IOACMD: *******************************
IOAK000I Command completed successfully
IOACMD: *******************************
IOACMD: About to generate OAT table using SYS1.OSASF.OAT
IOACMD: About to issue put file for IOA.A01.OSASF.IOAFENET.OAT01
IOACMD: Calling host OSA/SF...
IOACMD: Back from host OSA/SF...
IOACMD: *******************************
IOAK000I Command completed successfully
IOACMD: *******************************
.
.
IOACMD:
IOACMD: Output complete for install
IOACMD: The Configure OSA command has completed
 
Figure 4-32 OSA/SF REXX Interface Configure OSA CHPID-6
7. After you completed the Configure OSA CHPID operation, take CHPID OFFLINE from all the LPARs which share OSA CHPID. Without this operation, you might have trouble with OAT configuration.
8. Confirm that the OAT and Configuration file are successfully stored to OSA. To do so, get OAT and Configuration file again or Query OSA CHPID from OSA/SF.
4.3.2 Saving and restoring OSA Integrated Console Controller configuration
If you have an OSA-Express Integrated Console Controller (OSA-ICC) and one or more CHPID types defined as OSC, you can save the existing configuration as a source file and restore it for use into the zEC12. This source file is associated with an OSC channel PCHID. You can save and restore the source file through the OSA Advanced Facility on the HMC.
To save the configurations of your OSA-ICC with OSA Advanced Facility on the HMC, complete the following steps:
Exporting the source file for OSA-ICC using OSA Advanced Facility
Before you export a source file, prepare the USB flash drive that is supported by the HMC, and insert it into the USB port of the HMC. When the flash drive is recognized by the HMC, the panel shown in Figure 4-33 is displayed.
Figure 4-33 OSA Advanced Facilities (removable media inserted)
To export and import the source file, complete the following steps:
1. Log on using SYSPROG authority to the HMC. Select the CPC that contains the OSC CHPIDs for which you want to export the configuration data from Systems Management or Ensemble Management (in the example, SCZP301).
2. If your CPC joins Ensemble management, select Members from Ensemble name. Otherwise, click Systems to expand the list.
3. In the right pane, you see all the servers that are defined to Ensemble or the HMC. Select the CEC you want to access. In this example, select SCZP301, which belongs to the ITSO Ensemble as shown in Figure 4-34.
Figure 4-34 The HMC: Select CEC for OSA Advanced Facilities TASK
4. Click the menu arrow just after the CPC name and use it to expand and select the OSA Advanced Facilities menu (Figure 4-35).
Figure 4-35 The HMC: OSA Advanced Facilities TASK selection
Alternatively, you can access the OSA options the following way:
a. Select the CEC you want to access.
b. Click OSA Advanced Facility from Tasks (Figure 4-36).
Figure 4-36 The HMC: OSA Advanced Facilities TASK selection
5. The OSA Advanced Facilities window opens. Select the Channel ID card that you want to export, and click OK. For the example, select CHPID 05B0 (Figure 4-37).
Figure 4-37 OSA Advanced Facilities PCHID selection
6. Select Card specific advanced facilities and click OK (Figure 4-38).
Figure 4-38 OSA Advanced Facilities Card specific advanced facilities
7. Select Manual configuration options and click OK (Figure 4-39).
Figure 4-39 OSA Advanced Facilities Manual Configuration options
8. Select Export source file and click OK (Figure 4-40).
Figure 4-40 OSA Advanced Facilities Export source file
9. The task requests that a file name to be written onto the installed media device. For the example, enter OSCICCCFG (Figure 4-41). Click OK.
Figure 4-41 OSA Advanced Facilities export file name specification
10. The HMC displays the ACT20421 window, Click OK (Figure 4-42).
Figure 4-42 OSA Advanced Facilities (Insert media)
11. The Select Media Device window opens. Select USB flash drive that you used for exporting the source file, and click OK to proceed (Figure 4-43).
Figure 4-43 OSA Advanced Facilities (Select Media Device)
12. The HMC task writes the source file for the PCHID that was selected onto the media device and displays a message when it completes (Figure 4-44). Click OK.
Figure 4-44 OSA Advanced Facilities OSA-ICC export source file succeeded
13. You can now remove the USB flash memory drive at any time. When you do, the HMC displays a message that advises you that the USB flash drive has been removed (Figure 4-45).
Figure 4-45 OSA Advanced Facilities (removable media removed)
14. Click Cancel to exit all of the OSA Advanced Facilities windows.
Example 4-3 shows a sample of the source file on the USB flash drive.
Example 4-3 OSA-ICC sample source file
<OSC_SERVER>
<OSC_PHYSICAL_PORT0>
HOST_IP= 9.12.4.243
SUBNET_MASK= 255.255.252.0
PORT= 3270
ETHERNET_FRAME= DIX
MTU= 1492
NAME= OSAF300
</OSC_PHYSICAL_PORT0>
 
DEFAULT_GATEWAY= 9.12.4.1
</OSC_SERVER>
<CONFIG_SESSION>
<SESSION1>
CSS= 00 IID= 01 DEVICE= F300
GROUP= "SCC01300"
CONSOLE_TYPE= 2 RESPONSE= OFF READ_TIMEOUT= 60
</SESSION1>
 
<SESSION2>
CSS= 00 IID= 02 DEVICE= F300
GROUP= "SCC02300"
CONSOLE_TYPE= 1 RESPONSE= OFF READ_TIMEOUT= 60
</SESSION2>
............................................
 
............................................
<SESSION16>
CSS= 03 IID= 06 DEVICE= F300
GROUP= "SCC36300"
CONSOLE_TYPE= 2 RESPONSE= OFF READ_TIMEOUT= 60
</SESSION16>
 
</CONFIG_SESSION>
 
Editing the source file for OSA-ICC
When your OSA-ICC configuration for zEC12 such as IODEVICE, CSSID and MIFID of LPARs are changed, you must edit the OSA-ICC source file to match the new configuration. For more information about editing the source file, see OSA-Express Integrated Console Controller User's Guide, SA22-7990, and OSA-Express3 Integrated Console Controller Dual-Port User's Guide, SA23-2266.
Importing the OSA-ICC source file to zEC12 OSC channel
To import the source file and activate the configuration of the OSC-ICC, complete the following steps:
1. Before you importing source file, insert the USB flash drive that contains OSA-ICC source file. When USB flash drive is recognized by the HMC, the window shown in Figure 4-33 on page 181 is displayed.
2. Log on to the HMC and select the CEC you want to operate. Then, Open OSA Advanced Facility.
3. Select the PCHID of the OSC channel to import the source file. For the example, select PCHID 054C on SCZP401 (Figure 4-46).
Figure 4-46 OSA Advanced Facility PCHID selection
4. Select Card specific advanced facilities and click OK (Figure 4-47).
Figure 4-47 OSA Advanced Facility Card specific advanced facilities selection
5. Select Manual configuration options and click OK (Figure 4-48).
Figure 4-48 OSA Advanced Facility manual configuration options
6. The Manual Configuration Options window opens. Select Import source file and click OK (Figure 4-49).
Figure 4-49 OSA Advanced Facility Import source file operation
7. The window shown in Figure 4-50 is displayed. Click OK.
Figure 4-50 OSA Advanced Facility USB device to import source file
8. The Select Media Device window that is shown in Figure 4-43 on page 187 is displayed. Click OK to proceed.
9. The Import Source File window is displayed. Select the name of the source file you want to import on this panel. For the example, select OSCCONFG as the source file to import (Figure 4-51).
Figure 4-51 OSA Advanced Facility import source file selection
10. The window that is shown in Figure 4-52 is displayed when the source file import is complete. You can now remove the USB flash drive.
Figure 4-52 OSA Advanced Facility import file success
Validating the source file and activating the configuration
After you import of the source file, you must validate the source. If no error was found on the source, you can activate the configuration. If an error was found, you must correct the error.
To validate the imported source file, complete the following steps:
1. From the Manual Configuration Options window that is shown in step 6 on page 190, select Validate source file and click OK (Figure 4-53).
Figure 4-53 OSA Advanced Facility Validate Source file
2. If no error was found, the window shown in Figure 4-54 is displayed.
Figure 4-54 OSA Advanced Facility OSA-ICC source validation success
If an error is found, the window shown in Figure 4-55 is displayed. Select Edit source file in the Manual Configuration window, then correct the error and validate the source file again.
Figure 4-55 OSA Advanced Facility OSA-ICC source validation error
3. After you have validate the source file, activate the configuration. To do so, select Activate configuration in Advanced Facilities window (Figure 4-56).
Figure 4-56 OSA Advanced Facility active configuration
4.3.3 Setting OSA parameter using OSA Advanced Facility
If you want to change the port speed or MAC address of an OSA-Express feature, you can change them through OSA Advanced Facility.
 
Restrictions: You can change port speed only on OSA-Express4S 1000Base-T and OSA-Express3 1000 Base-T feature. Other OSA features have no capability to change port speed.
In OSA-Express4S 1000Base-T and OSA-Express3 1000 Base-T, you cannot set port speed to 1000 Mb, Full Duplex like the OSA- Express2. So If you want to set port speed to 1000 Mb, select Auto Negotiate.
Setting the OSA port speed by using Advanced Facility
To change port speed, complete the following steps:
1. Log on to the HMC, then open OSA Advanced Facility and select the PCHID that you want to customize.
2. The Advanced Facility window is displayed. Select Set Card Mode and click OK to proceed (Figure 4-57).
Figure 4-57 OSA Advanced Facility Set Card Mode selection
3. The Set Card Mode or Speed window is displayed (Figure 4-58). Select the correct port speed from the Mode/Speed list. You can set speed of port 0 and 1 individually. Click OK to proceed.
Figure 4-58 OSA Advanced Facility Set Card Mode panel
4. You must disable and enable the port from Advanced Facility Panel or configure CHPID OFFLINE and ONLINE from every LPAR where this OSA is assigned.
Changing OSA MAC address by using Advanced Facility
To change the media access control (MAC) address, complete the following steps:
1. Log on to the HMC, then open OSA Advanced Facility and select the PCHID you want to customize.
2. The Advanced Facility window is displayed. Select Display or Alter MAC address and click OK to proceed (Figure 4-59).
Figure 4-59 OSA Advanced Facility Display or Alter MAC address selection
3. The Display or alter MAC address window is displayed. Set the MAC address that you want and click OK to proceed (Figure 4-60).
Figure 4-60 OSA Advanced Facility Display alter MAC address panel
4.4 HCD: Validating the 2827 work IODF
This section addresses the steps that are needed to validate the 2827 work IODF.
4.4.1 Validating the work IODF
To validate the work IODF, complete the following steps:
1. Select HCD Option 2.12. Build validated work I/O definition file. Review the message list and correct any errors.
2. Press PF3 to continue. The message Requested action successfully processed is displayed.
3. Go to HCD Option 6.4. View I/O Definition File Information and note that the IODF type is now Work—Validated (Figure 4-61).
+---------------- View I/O Definition File Information -----------------+
| |
| |
| IODF name . . . . . . : 'SYS6.IODF8A.WORK' |
| IODF type . . . . . . : Work - Validated |
| IODF version . . . . . : 5 |
| |
| Creation date . . . . : 2012-07-06 |
| Last update . . . . . : 2012-07-06 11:32 |
| |
| Volume serial number . : IODFPK |
| Allocated space . . . : 2504 (Number of 4K blocks) |
| Used space . . . . . . : 1955 (Number of 4K blocks) |
| thereof utilized (%) 88 |
| Activity logging . . . : Yes |
| Multi-user access . . : No |
| Backup IODF name . . . : |
| |
| Description . . . . . : |
| |
| |
| |
| ENTER to continue. |
+-----------------------------------------------------------------------+
Figure 4-61 View I/O Definition File Information (validated work IODF)
4.4.2 Creating the IOCP for the CHPID Mapping Tool
To create the IOCP for the CHPID Mapping Tool, complete the following steps:
Tip: If you are an HCM user, you might prefer to use HCM to create the IOCP statements file and transfer the file to your workstation. You can then start the CHPID Mapping Tool, create an updated IOCP statements file, and transfer the file back to the host.
1. Select HCD Option 2.3. Build IOCP input data set and press Enter (Figure 4-62).
------ Activate or Process Configuration Data ----
Select one of the following tasks.
3 1. Build production I/O definition file
2. Build IOCDS
3. Build IOCP input data set
4. Create JES3 initialization stream data
5. View active configuration
6. Activate or verify configuration
dynamically
7. Activate configuration sysplex-wide
8. *Activate switch configuration
9. *Save switch configuration
10. Build I/O configuration data
11. Build and manage S/390 microprocessor
IOCDSs and IPL attributes
12. Build validated work I/O definition file
Figure 4-62 Activate or Process Configuration Data (Build IOCP for SCZP401)
2. HCD displays the list of available processors. Select the SCZP401 processor by entering a forward slash mark (/) and pressing Enter (Figure 4-63).
-------------------------- Available Processors --------------------------
Row 1 of 5
Command ===> __________________________________________________________
Select one.
Processor ID Type Model Mode Description
ISGSYN 2064 1C7 LPAR z900
ISGS11 2064 1C7 LPAR z900
SCZP101 2094 S18 LPAR z9
SCZP201 2097 E26 LPAR z10
/ SCZP401 2827 H43 LPAR zHelix
Figure 4-63 Available Processors (selecting processor for the IOCP file)
3. HCD displays a panel on which you enter information about the IOCP input data set to be created (Figure 4-64). Complete the following fields:
 – Title1
 – IOCP input data set
 – Enter Yes in the Input to Stand-alone IOCP field.
 – Complete the Job statement information for your installation.
------------------------- Build IOCP Input Data Set --------------------
Specify or revise the following values.
IODF name . . . . . . . . . : 'SYS6.IODF8A.WORK'
Processor ID . . . . . . . : SCZP401
Title1 . IODF8A________________________________________________________
Title2 : SYS6.IODF8A.WORK - 2012-07-06 11:32
IOCP input data set
'SYS6.IODF8A.IOCPIN.SCZP401'____________________________
Input to Stand-alone IOCP? Yes (Yes or No)
Job statement information
//WIOCP JOB (ACCOUNT),'NAME'
//*
//*
//*
//*
//*
Figure 4-64 Build IOCP Input Data Set
4. Press Enter. HCD submits a batch job to create the data set.
5. In TSO, verify that the data set that you created exists and contains IOCP statements (Figure 4-65). The data set is used as input into the CHPID Mapping Tool.
ID MSG1='IODF8A', *
MSG2='SYS6.IODF8A.WORK - 2012-07-06 11:32', *
SYSTEM=(2827,1),LSYSTEM=SCZP301, *
TOK=('SCZP401',00800001B8D72827123203950112202F00000000,*
00000000,'12-07-06','11:32:04','........','........')
RESOURCE PARTITION=((CSS(0),(A0A,A),(A0B,B),(A0C,C),(A0D,D),(A*
0E,E),(A0F,F),(A01,1),(A02,2),(A03,3),(A04,4),(A05,5),(A*
06,6),(A07,7),(A08,8),(A09,9)),(CSS(1),(A1A,A),(A1B,B),(*
A1C,C),(A1D,D),(A1E,E),(A1F,F),(A11,1),(A12,2),(A13,3),(*
A14,4),(A15,5),(A16,6),(A17,7),(A18,8),(A19,9)),(CSS(2),*
(A2A,A),(A2B,B),(A2E,E),(A2F,F),(A21,1),(A22,2),(A23,3),*
(A24,4),(A25,5),(A28,8),(*,6),(*,7),(*,9),(*,C),(*,D)),(*
CSS(3),(A3A,A),(A3B,B),(A3C,C),(A3D,D),(A3E,E),(A3F,F),(*
A31,1),(A33,3),(A34,4),(A35,5),(A36,6),(A37,7),(A38,8),(*
A39,9),(*,2)))
CHPID PATH=(CSS(0,1,2,3),00),SHARED, *
NOTPART=((CSS(0),(A0C,A0D,A0E,A0F),(=)),(CSS(1),(A1B,A1D*
,A1E,A1F),(=)),(CSS(2),(A2E,A2F),(=)),(CSS(3),(A3D,A3E,A*
3F),(=))),PCHID=5A0,TYPE=OSD
CHPID PATH=(CSS(0,1,2,3),01),SHARED, *
NOTPART=((CSS(0),(A0C,A0D,A0E,A0F),(=)),(CSS(1),(A1B,A1D*
,A1E,A1F),(=)),(CSS(2),(A2E,A2F),(=)),(CSS(3),(A3D,A3E,A*
3F),(=))),PCHID=5B0,TYPE=OSC
Figure 4-65 IOCP input data set contents (truncated)
Also, note that part of the TOK statement has been blanked out with dots (Example 4-4).
Example 4-4 IOCP file (TOK statement)
TOK=('SCZP401',00800001B8D72827113204910112188F00000000,*
00000000,'12-07-06','11:32:04','........','........')
These dots ensure that this IOCP file cannot be written to a processor and used for a power-on reset. This precaution is needed because this IOCP file was created from a validated Work IODF and not a production IODF. IOCP files that can be used for a power-on reset can only be generated from Production IODFs.
 
Important: When an IOCP statement file is exported from a Validated Work IODF by 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.
6. Download this IOCP file from TSO to the CMT workstation. Use a workstation file transfer facility such as the one in the IBM Personal Communications Workstation Program, or any equivalent 3270 emulation program. Be sure to use TEXT as the transfer type. In the example, the file is named IODF8AIN.txt.
4.5 CMT: Assigning PCHIDs to CHPIDs
The following steps use the output from the previous set of HCD steps (IOCP) and the 2827 order process (CFReport). Use the CHPID Mapping Tool to assign PCHIDs to each of the CHPIDs for the 2827.
For this process, the CMT must be downloaded. For more information about downloading and installing the CMT, see 2.1.5, “CHPID Mapping Tool” on page 30. If you already have CMT installed, verify that you have the latest updates installed. For more information, see the System z CHPID Mapping Tool User’s Guide, GC28-6900.
Using the CHPID Mapping Tool, complete the following steps:
3. Resolve CHPIDs with a PCHID conflict (4.5.3, “Resolving CHPIDs with PCHID conflict” on page 207).
4. Process the hardware resolution (4.5.4, “Hardware Resolution” on page 208).
6. Set the priority for single-path control units and other control units that override the CHPID Mapping Tool default priorities and Automatic Mapping (4.5.6, “Processing the CU Priority and Automatic Mapping” on page 214).
7. Resolve the CHPIDs that are not connected to control units (4.5.7, “CHPIDs not connected to control units” on page 218).
8. Create the CHPID Mapping Tool reports (4.5.8, “Creating CHPID Mapping Tool reports” on page 219).
9. Create an updated IOCP statements file and transfer it back to the host z/OS image (4.5.9, “Creating an updated IOCP” on page 225).
 
Requirement: When you upgrade from a 2097 or a 2817 to a 2827, you must use the CHPID Mapping Tool level that supports the 2827.
4.5.1 Importing the CFReport file into the CHPID Mapping Tool
To import the CFReport file into the CHPID Mapping Tool, complete the following steps:
1. Start the CMT on your workstation.
2. Right-click the Projects pane, and select New → Select Standard CMT Project (Figure 4-66).
Figure 4-66 Creating a CHPID Mapping Tool Project
3. The New CHPID Mapping Tool Project window opens. Use this window to specify a Project Name and click Next. (Figure 4-67).
Figure 4-67 New CHPID Mapping Tool Project
4. Import the CFReport file into the CHPID Mapping Tool, specify the name in the CFReport File, and click Finish (Figure 4-68).
Figure 4-68 Specifying the CFReport file
 
Remember: If you click Finish but have not selected an IOCP file, you receive the error message shown in Figure 4-69.
Figure 4-69 Message that you did not specify IOCP
The tool displays a window with the progress of reading the CFReport File (Figure 4-70).
Figure 4-70 Reading CFReport window
The information from CFReport file is displayed on the Hardware pane (Figure 4-71).
Figure 4-71 Imported CFReport file
4.5.2 Importing the 2827 IOCP file into the CHPID Mapping Tool
To import the 2827 IOCP file into the CHPID Mapping Tool, complete the following steps:
1. Right-click in the Projects pane and select Import IOCP File (Figure 4-72).
Figure 4-72 Importing the IOCP file
2. Select the IOCP file on your workstation to import into the CHPID Mapping Tool and click Finish (Figure 4-73).
Figure 4-73 Specifying the IOCP file
3. Right-click the IOCP file and select Read Selected IOCP (Figure 4-74).
Figure 4-74 Reading the selected IOCP
You get a message that shows Progress Information (Figure 4-75).
Figure 4-75 Message IOCP reading: Progress Information
4. The CHPID Mapping Tool displays the information from the CFReport file and the IOCP file in the Hardware resolution pane. By default, the Hardware Resolution view includes three tabbed panes (Figure 4-76). The Hardware Resolution view is the middle tabbed pane and the Channel Type Summary pane is the right tabbed pane.
Figure 4-76 Hardware Resolution Imported CFReport file
The Channel Type Summary pane displays a table with helpful information. It summarizes the number of used and available channels for the hardware channel types (used, available, and device count).
In the example, the CHPID Mapping Tool issues the following output:
•HW Resolution view: This window list all of the CHPIDs that have been found and Status column shows the CHPIDs information to be investigated. In the example, investigate the following status:
 – Not compatible Channel Type: The Channel Type that are not compatible with the IOCP input type. PCHID might represent hardware that is not compatible with a CHPID type, or there might be no hardware present at a PCHID.
 – No hardware found: There are more CHPIDs defined than available hardware or AID values, or PCHID values are present that are not found in the hardware.
 – Select at least one channel type: The channel type is not assigned to the current row. The channel type might be assigned to IOCP type.
•Manual mapping CIB CHPIDs: Availability Mapping cannot be used until all CIB CHPIDs are resolved. You can use manual mapping to resolve any CIB CHPIDS, after which the Availability Mapping function is enabled for use.
•Process the CU Priorities and Automatic Mapping:
 – Reset CHPIDs assigned by Automatic Mapping: Checking this option resets all CHPIDs that were processed by prior availability runs in this session.
By default, this option is checked.
 – Reset CHPIDs assigned by Manual Mapping: Checking this option resets CHPIDs that were assigned a PCHID in the Manual window. If this option is not checked, then availability PCHIDs for these CHPIDs are not reset.
By default, this option is clear.
 – Reset CHPIDs assigned by IOCP(Potential re-cabling): If some of the CHPIDs are assigned in the IOCP Input file, selecting this option resets the CHPIDs. Selecting this option might require recabling after availability assignments.
Generally, select this option.
 – Reset CHPIDs assigned by CMT for config files: The CFReport indicates that you are doing an MES/upgrade, and you have channels or CHPIDs (or both) that might have configuration files that are currently associated with them. The MES/upgrade might move some of those channel cards.
Regardless of whether the channels are moving or not, the CHPID Mapping Tool either assigns PCHIDs to the logical CHPID definitions to keep the CHPID definition associated with its current configuration file, or moves the definition to the new location where the channel is moving.
If you reset the CHPID Mapping Tool assignments, back up the configuration file data before the MES, and restore that data to the new location (the PCHID where the affected CHPIDs are assigned) before you use the CHPIDs.
By default, this option is clear.
If none of the options are selected, availability only works on CHPIDs that do not have PCHIDs assigned.
To give the CHPID Mapping Tool the most choices when you use the availability option, select Reset CHPIDs assigned by IOCP.
However, if you select Reset CHPIDs assigned by Automatic Mapping, review the intersects from availability processing carefully to ensure that preserving the prior CHPID-to-PCHID relationship does not cause unacceptable availability.
If you run Reset CHPIDs assigned by IOCP, it will reset any previously mapped CHPID assignments and can result in recabling of the server.
4.5.3 Resolving CHPIDs with PCHID conflict
The CMT displays the CHPIDs with PCHID conflicts (Figure 4-77).
Figure 4-77 CHPIDs with PCHID conflicts
In the first column of every row, the Hardware Resolution pane contains either an X in a red circle or a green check mark. An X indicates an error and a green check mark indicates the tool successfully resolved the specified Channel Type.
The example has these reasons to resolve hardware resolution issues:
•The PCHID channel type changed.
•Defined PCHID is not compatible with the channel path at a particular location.
•There are enough ports in the hardware.
•There is a type mismatch between a CHPID and its associated channel type.
4.5.4 Hardware Resolution
In the example, the CHPID Mapping Tool displays an X in the first column of the Hardware Resolution pane that is related to these error types: No hardware found and FINCON EXP8S 10KM LX is not compatible with OSD (Figure 4-78).
Figure 4-78 Hardware resolution status errors
 
More information: For more information about these error messages, see the System z CHPID Mapping Tool User’s Guide, GC28-6900-00.
Reset Incompatible (Hardware - I/O) Entries
The Channel type that is assigned for the CHPID is not compatible with the IOCP type specified by the IOCP file. For this mismatch, you might receive the following message: Error: Channel_type is not compatible with IOCP_type.
Resolve this problem by resetting the PCHID. In the example, the IOCP type is OSD but the PCHID is associated with an FICON card. You cannot assign the OSD type on the FICON card.
The CHPID Mapping Tool displays the error message in the Status column (Figure 4-79).
Figure 4-79 Channel_type is not compatible with IOCP_type
Select the channel type OSD. The Status is Error: FICON EXP8S is not compatible with OSD. Right-click in the row and select Reset Incompatible (Hardware I/O) Entries to remove the PCHID values for only those rows (Figure 4-80).
Figure 4-80 Channel_Type is not compatible with IOCP_type OSD
The tool replace the X in a red circle with an Attention icon, changes the status message, and removes the PCHIDs information (Figure 4-81).
Figure 4-81 Results of reset are incompatible
The CHPID Mapping Tool now displays messages about any CHPID types that were imported from the IOCP input file (IODF) into the CMT that do not have any associated hardware support in the CFReport file (Figure 4-82). Click OK. The same figure also shows the Channel Type Summary details.
Figure 4-82 Required Hardware unavailable
There are excessive numbers of CHPID types OSD in the example IODF to show how the CHPID Mapping Tool handles this condition. For more information, see 4.2.8, “Overdefining channel paths on an XMP processor” on page 169.
You can use the overdefine option to change the PCHID value to an asterisk (*) in the IODF. Doing so allows you to retain the OSD CHPID definitions in the IODF so you can install OSD CHPIDs in the processor later.
 
Tip: Other CHPID types can also be overdefined by entering an asterisk (*) for the PCHID value. Overdefining is now supported for CIB type CHPID definitions.
Alternatively, you can remove the OSD CHPID definitions from the IODF.
To continue with this example, complete the following steps:
1. Return to the IODF and change the PCHID values for the OSD CHPIDs (or any other CHPIDs that have no supporting hardware in the CFReport) to an asterisk (*).
2. Revalidate the IODF by using HCD Option 2.12.
3. Re-create the IOCP statements file and transfer it to your workstation.
4. Import the IOCP file by right-clicking the Projects panel and selecting Import IOCP File.
 
Tip: If you look at the IOCP statements file now, the OSD CHPIDs have been omitted from the file, but are still defined in the IODF.
Now when you click Reset “Channel-Type is not compatible with IOCP_type”, the CHPID Mapping Tool asks you to resolve some hardware.
Reset “No hardware found” Entries
An X in a red circle in the first column indicates an error, and the Status column provides the information with value of Error: No hardware found (Figure 4-83).
Figure 4-83 Errors: No Hardware found
In the example, select channel type FC and the Status is Error: No Hardware found. Right-click in the row and select Reset “No hardware found” to remove the PCHID values for those rows (Figure 4-84).
Figure 4-84 Resetting No Hardware found entries
The tool replaces the X with an Attention icon, and changes the status message, and removes the PCHID information (Figure 4-85).
Figure 4-85 Results of resetting No hardware found
Reset “Select at least one channel type”
The channel type is not assigned to the current row. Assign a channel type to the IOCP type:
1. Click the Channel Type column in the target row. The tool displays an arrow in the Channel Type column of the target row (Figure 4-86).
Figure 4-86 Resetting Select at least one channel type
2. Click the arrow. The tool displays a list of available and compatible card types for the CHPID as shown in Figure 4-87.
Figure 4-87 Channel Type Selection
There are more two possibilities that need to be Reset that are not shown in the example:
Reset “Required hardware for type IOCP_type not available”
The CHPID Mapping Tool found no hardware for the specified IOCP type. For example: Required hardware for type CIB not available.
You must change IOCP file or obtain more hardware.
Reset “PCHID_1 moved to new channel ID: PCHID_2”
When moving from old hardware to new hardware, for example during a miscellaneous equipment specification (MES), the PCHID value assigned to a feature may change. This message indicates that the IOCP file contains a PCHID value for the old machine that is being removed. The PCHID value is changed from the old machine to the PCHID value for the new machine. For example, PCHID_1 is the first PCHID value representing the old hardware (for example, 1B0) and PCHID_2 is the new value representing the new hardware (for example, 533). In essence, the feature is present in both the old and new hardware, but its location (PCHID) has changed.
This status is an informational message. No hardware resolution is required. The message informs you of the new location so you can change it if you prefer a different assignment.
After you assign all Channel Types, the Manual Mapping button becomes available.
4.5.5 Manual mapping to resolve CIB CHPIDs
Observe that Automatic Mapping is not available. You cannot use Automatic Mapping until all CIB CHPIDs are resolved. You can use manual mapping to resolve this task.
To resolve the CIB CHPIDs, assign the available CHPIDs. Click Manual Mapping (Figure 4-88).
Figure 4-88 Manual Mapping
Ensure that the tool is displaying the Manual Mapping pane in Hardware -> I/O Format (Figure 4-89).
Figure 4-89 Manual Mapping Hardware -> I/O
Click every row that has type HC3 in the Channel Type column. The tool displays the all the available CHPIDs with IOCP type (Figure 4-90).
Figure 4-90 Channel Type of HCA3 and associated CIB type
Select one or more empty check boxes in the I/O Config pane to assign the CHPID. In the Hardware pane, the CHPID number is inserted and in the Assigned By column, it inserts the value Manual.
The Automatic Mapping button becomes available after you assign all the CHPIDs of IOCP type CIB.
4.5.6 Processing the CU Priority and Automatic Mapping
If you are importing an IOCP statements file from a 2097 or 2817 that had CU Priority values defined, review the CU Priority values beforehand. The CHPID Mapping Tool can then perform the availability functions appropriately for a 2827.
You must assign priorities if you want to make some control units more important (in the CMT processing order) than others, or have two (or more) control units that you want the CMT tool to process at the same time.
Perform the first availability function by completing these steps:
1. Click Automatic Mapping.
2. The Reset CHPID Assignments window opens with Reset choices. For the example, select Reset CHPIDs assigned by Automatic Mapping and Reset CHPIDs assigned by IOCP (Figure 4-91).
 
Tip: There is also a fourth choice available only for an upgrade or an MES: Reset CHPIDs assigned by CMT for config files.
Figure 4-91 Reset CHPID Assignments
3. Click OK, and click it again to confirm the reset. (Figure 4-92).
Figure 4-92 Message about resetting all values
The 2827 has different availability rules than 2097 and 2817, so remove all PCHIDs assignments that are still in the IOCP.
4. Click OK. After the CHPID Mapping Tool resets the CHPIDs, it displays a message that indicates the results of the process (Figure 4-93).
Figure 4-93 Message Availability run successfully with no errors
5. Click OK (Figure 4-94).
Figure 4-94 Message Process Intersections run successfully
The following list defines the possible intersects:
C Two or more assigned channels use the same channel card.
S More than half the assigned channels use the same InfiniBand or STI link.
M All assigned channels are supported by the same MBA group.
B More than half the assigned channels are supported by the same MBA Group.
D Assigned channels are on the same daughter card.
The example returned the “B” intersect.
 
Tip: Intersect messages inform you of a potential availability problem detected by the CMT. However, they do not necessarily indicate an error. It is your responsibility to evaluate whether the condition must be corrected.
Find the intersect warnings in the CMT in the Manual Mapping view under the CHPID Groups pane and decide whether they are acceptable or not (Figure 4-95).
Figure 4-95 B Intersect examples
You can now display the results of the channel mapping. You can also sort the report in different ways. For example, you can see how the CHPID Mapping Tool ranked the control units.
Check and set values for items such as OSA-ICC CHPIDs and FCTC CHPIDs to ensure that the CHPID Mapping Tool allocates these CHPIDs with high PCHID availability.
1. Click the CU Priorities. By default, this pane is the center on the top.
2. In the CU Priorities pane, search in the column CU Number for the control units that you want to set a priority for.
3. Type a priority number for the CU in the Priority column for each row. The CHPID Mapping Tool makes more related changes in the CHPID Groups panes. In the example, set the OSC type CU Numbers to priority 333 (Figure 4-96).
Figure 4-96 Set CU Priority
If there are coupling links that are used by a CF image, group those links.
Group each set of CHPIDs going to a different CPC with a common priority. For example, suppose the CF image has four links (CHPIDs 40, 41, 42, and 43) and that 40 and 41 go to one CPC, and 42 and 43 go to a different CPC. In this case, give CHPIDs 40 and 41 one priority and CHPIDs 42 and 43 a different priority. The concept is the same regardless of the number of connecting CPCs or the number of links to each CPC.
Now perform the second availability function by completing these steps:
4. Click Automatic Mapping.
5. The Reset CHPID Assignments window opens with Reset choices. Click Reset CHPIDs assigned by Automatic Mapping.
6. Click OK.
7. In the Hardware resolution pane, as you can see the CHPID and Assigned by columns are no longer blank (Figure 4-97). The CMT has assigned CHPIDs to PCHIDs and placed the Availability value in the Assigned by column, indicating that the CHPID values were assigned based on availability.
Figure 4-97 CHPIDs assigned
The following list defines the possible Assigned by column values:
Manual You made the assignment by using manual mapping.
Automatic You made the assignment by using automatic mapping.
IOCP The IOCP source made the assignment.
Config File The CHPID Mapping Tool forced an assignment because of configuration file requirements.
 
More information: See the CHPID Mapping Tool User’s Guide, GC28-6900-00, page 91, Table 6. Column headings and descriptions of contents.
8. You can now display the results of the channel mapping. You can also sort the report in different ways. For example, to see how the CHPID Mapping Tool ranked the control units, select CU Priorities pane and click the Priority column (Figure 4-98).
Figure 4-98 CU Priorities after assigned priorities
The example illustrates how CU Priority values are represented in the IOCP file.
 
Tip: The control unit priorities are stored in the IOCP output file created by the CMT that gets migrated back into HCD. HCD maintains these priorities and outputs them when it creates another IOCP deck.
They are in the form of commented lines at the end of the IOCP deck, as shown here:
*CMT* VERSION=000
*CMT* CCN=08350359(CFR from ResourceLink)
*CMT* 6000.0=0001,6000.1=0001,6000.2=0001,6000.3=0001,8000.0=0010
*CMT* 8000.1=0010,8000.2=0010,8000.3=0010,8100.0=0010,8100.1=0010
*CMT* 8100.2=0010,8100.3=0010,8200.0=0010,8200.1=0010,8200.2=0010
*CMT* 8200.3=0010,8300.0=0010,8300.1=0010,8300.2=0010,8300.3=0010
*CMT* 8400.0=0010,8400.1=0010,8400.2=0010,8400.3=0010,8500.0=0010
*CMT* 8500.1=0010,8500.2=0010,8500.3=0010,8600.0=0010,8600.1=0010
*CMT* 8600.2=0010,8600.3=0010,C400.0=0020,C400.1=0020,C400.2=0020
*CMT* C400.3=0020,C500.0=0020,C500.1=0020,C500.2=0020,C500.3=0020
*CMT* F300.0=0333,F300.1=0333,F300.2=0333,F300.3=0333,F380.0=0333
*CMT* F380.1=0333,F380.2=0333,F380.3=0333
4.5.7 CHPIDs not connected to control units
In the CPU Priorities window, click in the CU number column. The CHPID Mapping Tool displays, at the end of the list, all CHPIDs defined in the IOCP input that are not connected to control units. All coupling CHPIDs in this list are preceded with an “S” in the CU Number column. All non-coupling CHPIDs are preceded with a “P”.
Figure 4-99 shows a “S” before the CU number.
Figure 4-99 CHPIDs not connected to control units
Review the list for the following reasons:
•You might have forgotten to add a CHPID to a control unit and need to update the IOCP source before you continue in the CMT.
•The unconnected CHPIDs might be extra channels that you are ordering in anticipation of new control units.
•The unconnected CHPIDs might be coupling links that are being used in coupling facility (CF) images (they do not require control units).
If there are extra CHPIDs for anticipated new control units, you might want to group these CHPIDs with a common priority. Having a common priority allows the availability mapping function to pick PCHIDs that can afford your new control unit availability.
4.5.8 Creating CHPID Mapping Tool reports
The CHPID Mapping Tool offers built-in reports, which are available from the top of the window. You can also print the information from the report by clicking Print. Figure 4-100 shows the options to create a Preview Report or Save Report.
Figure 4-100 Preview Report and Save Report buttons
Click Preview Report or Save Report to display choices (a list of types of reports). The choices are the same except Save Report lists there is an extra selection (Figure 4-101).
Figure 4-101 Preview Report and Save Report options
For simplicity, only three reports are described in this example: The CHPID Report, the Port Report, Sorted by Location, and the CHPID to Control Unit Report. However, all built-in reports are printed in the same way.
The person who installs the I/O cables during system installation needs one of these reports. The Port Report, sorted by location, is preferable. The installer can use this report to help with labeling the cables. The labels must include the PCHID or cage/slot/port information before system delivery.
CHPID Report
To create the CHPID report, complete the following steps:
1. Click Preview Report → CHPID Report (Figure 4-102).
Figure 4-102 Select CHPID Report
The CHPID Mapping Tool opens a browser window with the CHPID report (Figure 4-103).
Figure 4-103 CHPID Report
Tip: You can save individual reports as multiple reports in batch.
2. Click Save Report. In the example, click the CHPID Report option and the CHPID Mapping Tool opens a browser window with a wizard for creating a report. Type a File name in the File Name field and the External path. If you want to save the report in HTML, select HTML. The tool selects PDF by default. The window is similar for all type of reports. Click Finish (Figure 4-104).
Figure 4-104 Save CHPID Report
3. The CHPID Report is created by the CHPID Mapping Tool (Figure 4-105).
Figure 4-105 CHPID Report example
At the end of this CHPID report is a list of CHPIDs with modified PCHID/AID assignments. This report is valuable for moving cables (Figure 4-106).
Figure 4-106 List of CHPIDs that have modified PCHID/AID assignments
Port Report, Sorted by Location
To create the Port Report, Sorted by Location, click Preview Report → Port Report → Sorted by Location. The CHPID Mapping Tool opens a browser window with the CHPID to Port Report (Figure 4-107).
Figure 4-107 CHPID to Port Report, Sorted by Location
CHPID to Control Unit Report
This report is created in a similar way to the CHPID Report. Click Preview Report → CHPID to Control Unit Report. The CHPID Mapping Tool opens a browser window with the CHPID to Control Unit Report (Figure 4-108).
Figure 4-108 CHPID to CU Report
4.5.9 Creating an updated IOCP
Create an IOCP statements file that you then import into the IODF by using HCD. This IOCP statements file now has the CHPIDs assigned to PCHIDs.
 
Note: You might prefer to use HCM to transfer the updated IOCP statements file back to the host. However, first run the next step in the CHPID Mapping Tool to create the updated IOCP file.
To create the IOCP, complete the following steps:
1. Select File → Export IOCP (Figure 4-109).
Figure 4-109 Export IOCP option
2. Enter the file name and External Path for the IOCP output file and click Finish (Figure 4-110).
 
Requirement: This file must be uploaded to the z/OS image on which you have the work IODF you used previously to create the IOCP input data set.
Figure 4-110 Export IOCP File
4.6 HCD: Updating the 2827 work IODF with PCHIDs
After you map the CHPIDs to PCHIDs by using the CMT, transfer the information back into HCD, which you can do by completing the following steps:
1. Upload the IOCP file that was created by the CMT (IODF8AO.txt, in the example) to the z/OS image. Use a file transfer facility, such as the one in IBM Personal Communications or an equivalent FTP program. Be sure to use TEXT as the transfer type.
In the updated IOCP statements file, note that the CMT has left a reference to the CCN. Also, note the CU Priority values added for the OSC control units.
 
Remember: Control unit priorities are stored in the IOCP output file created by CMT that is migrated back into HCD. HCD maintains these priorities and outputs them when it creates another IOCP deck. They are in the form of commented lines at the end of the IOCP deck (Example 4-5).
Example 4-5 Updated IOCP statements file (with CMT statements)
*CMT* VERSION=000
*CMT* CCN=08350359(CFR from ResourceLink)
*CMT* 6000.0=0001,6000.1=0001,6000.2=0001,6000.3=0001,8000.0=0010
*CMT* 8000.1=0010,8000.2=0010,8000.3=0010,8100.0=0010,8100.1=0010
*CMT* 8100.2=0010,8100.3=0010,8200.0=0010,8200.1=0010,8200.2=0010
*CMT* 8200.3=0010,8300.0=0010,8300.1=0010,8300.2=0010,8300.3=0010
*CMT* 8400.0=0010,8400.1=0010,8400.2=0010,8400.3=0010,8500.0=0010
*CMT* 8500.1=0010,8500.2=0010,8500.3=0010,8600.0=0010,8600.1=0010
*CMT* 8600.2=0010,8600.3=0010,C400.0=0020,C400.1=0020,C400.2=0020
*CMT* C400.3=0020,C500.0=0020,C500.1=0020,C500.2=0020,C500.3=0020
*CMT* F300.0=0333,F300.1=0333,F300.2=0333,F300.3=0333,F380.0=0333
*CMT* F380.1=0333,F380.2=0333,F380.3=0333
******************************** Bottom of Data **********************
2. From the HCD main panel (Figure 4-111), enter the work IODF name used. Select Option 5. Migrate configuration data.
                        Hardware Configuration
Select one of the following.
5_ 0. Edit profile options and policies
1. Define, modify, or view configuration data
2. Activate or process configuration data
3. Print or compare configuration data
4. Create or view graphical configuration report
5. Migrate configuration data
6. Maintain I/O definition files
7. Query supported hardware and installed UIMs
8. Getting started with this dialog
9. What's new in this release
For options 1 to 5, specify the name of the IODF to be used.
I/O definition file . . . 'SYS6.IODF8A.WORK' +
Figure 4-111 Main menu: Migrate configuration data
3. From the Migrate Configuration Data panel (Figure 4-112), select Option 1. Migrate IOCP/OS data and press Enter.
----------- Migrate Configuration Data -----
Select one of the following tasks.
1_ 1. Migrate IOCP/OS data
2. *Migrate switch configuration data
 
Figure 4-112 Migrate Configuration Data
4. On the Migrate IOCP Data panel (Figure 4-113), competed the following fields and then press Enter:
Processor ID Use the same ID used to create the IOCP input deck.
OS configuration ID This is the OS configuration that is associated with the processor.
IOCP only input data set This is the data set name that was specified when the iocpout.txt file was uploaded to z/OS
Processing mode Select Option 2 to save the results of the migration. (Before using Option 2, however, try to migrate using Option 1 to validate the operation.)
Migrate options Select Option 3 for PCHIDS. Only the PCHIDs are migrated into the work IODF.
-------------------- Migrate IOCP / MVSCP / HCPRIO Data -------------------
Specify or revise the following values.
Processor ID . . . . . . . . . . . . SCZP401 + CSS ID . . . . . . _ +
OS configuration ID . . . . . . . . L06RMVS1  +
Combined IOCP/MVSCP input data set . _____________________________________
IOCP only input data set . . . . . . 'SYS6.IODF8A.IOCPOUT.SCZ401'
MVSCP only or HCPRIO input data set _____________________________________
Associated with processor ________ +
partition ________ +
Processing mode . . . . . . . . . . 2 1. Validate
2. Save
Migrate options . . . . . . . . . . 3 1. Complete
2. Incremental
3. PCHIDs
MACLIB used . . . . . . . 'SYS1.MACLIB'
Volume serial number . . . ______ + (if not cataloged)
Figure 4-113 Migrate IOCP / MVSCP / HCPRIO Data
5. HCD displays any errors or warning messages as a result of the migration action. The example did not produce any messages other than the one indicating that the migration was successful (Figure 4-114).
The work IODF now contains both the CHPID definitions and the mapping to PCHIDs that was done by using the CMT.
-------------------------- Migration Message List ---------------------------
Query Help
--------------------------------------------------------------------------
Row 1 of 2
Command ===> ___________________________________________ Scroll ===> CSR
Messages are sorted by severity. Select one or more, then press Enter.
/ Statement Orig Sev Message Text
_ I I/O configuration successfully written to the IODF
# SYS6.IODF8A.WORK.
***************************** Bottom of data *****************************
Figure 4-114 Migration Message List
6. Press PF3. You should receive the following message:
IOCP/Operating system deck migration processing complete, return code = 0.
7. Press PF3 again to continue.
4.7 HCD: Building the 2827 production IODF
To use the definitions updated in HCD, create a 2827 production IODF from your work IODF. Then remotely or locally write the IODF to the 2827 IOCDS by using Write IOCDS in preparation for the upgrade.
To build the production IODF, complete the following steps:
1. From the HCD main panel, select Option 2. Activate or process configuration data (Figure 4-115).
                        z/OS V1.13 HCD
Command ===> ______________________________________________________
Hardware Configuration
Select one of the following.
2 0. Edit profile options and policies
1. Define, modify, or view configuration data
2. Activate or process configuration data
3. Print or compare configuration data
4. Create or view graphical configuration report
5. Migrate configuration data
6. Maintain I/O definition files
7. Query supported hardware and installed UIMs
8. Getting started with this dialog
9. What's new in this release
For options 1 to 5, specify the name of the IODF to be used.
I/O definition file . . . 'SYS6.IODF8A.WORK' +
Figure 4-115 Main menu: Selecting activate or process configuration data
2. HCD displays the Activate or Process Configuration Data panel. Select Option 1. Build production I/O definition file and press Enter (Figure 4-116).
----- Activate or Process Configuration Data -----
Select one of the following tasks.
1_ 1. Build production I/O definition file
2. Build IOCDS
3. Build IOCP input data set
4. Create JES3 initialization stream data
5. View active configuration
6. Activate or verify configuration
dynamically
7. Activate configuration sysplex-wide
8. *Activate switch configuration
9. *Save switch configuration
10. Build I/O configuration data
11. Build and manage S/390 microprocessor
IOCDSs and IPL attributes
12. Build validated work I/O definition file
 
Figure 4-116 Activate or Process Configuration Data: Selecting Build production IODF
3. HCD displays the Message List panel (Figure 4-117). Verify that you have only severity W warning messages and that they are normal for the configuration. Correct any other messages and try to build the production IODF again. Continue this process until you have no messages that indicate problems.
------------------------------- Message List -------------------------------
Save Query Help
--------------------------------------------------------------------------
                                                                Row 1 of 377
Command ===> ___________________________________________ Scroll ===> CSR
Messages are sorted by severity. Select one or more, then press Enter.
/ Sev Msg. ID Message Text
_ W CBDG081I Following 3 operating system configurations of type MVS
# have no console devices defined: ALLDEV, LABSERV1,
# L06RMVS1
_ W CBDA857I No channel paths attached to partition A09 of processor
# SCZP201.0.
_ W CBDG542I The following CIB channel paths of processor SCZP201
# connect the same HCA port 09.2 with different target HCA
# ports: 0.93, 0.CD
_ W CBDG542I The following CIB channel paths of processor SCZP201
# connect the same HCA port 1B.1 with different target HCA
# ports: 0.9C, 0.CF
_ W CBDG542I The following CIB channel paths of processor SCZP201
# connect the same HCA port 1B.1 with different target HCA
# ports: 0.9D, 0.CF
Figure 4-117 Message List (building Production IODF)
4. Press PF3 to continue.
5. HCD displays the Build Production I/O Definition File panel. Complete the Production IODF name and Volume serial number fields, and press Enter (Figure 4-118).
-------------- Build Production I/O Definition File ------------
Specify the following values, and choose how to continue.
Work IODF name . . . : 'SYS6.IODF8A.WORK'
Production IODF name . 'SYS6.IODF8A'_______________________
Volume serial number . IODFPK +
Continue using as current IODF:
2 1. The work IODF in use at present
2. The new production IODF specified above
Figure 4-118 Build Production I/O Definition File
6. HCD displays the Define Descriptor Fields panel (Figure 4-119). Press Enter to accept the descriptor fields that are selected by HCD or enter your selection, and then press Enter.
-------------------- Define Descriptor Fields --------------
Specify or revise the following values.
Production IODF name . : 'SYS6.IODF8A'
Descriptor field 1 . . . SYS6
Descriptor field 2 . . . IODF8A
Figure 4-119 Define Descriptor Fields
7. HCD displays the following message that indicates that the production IODF was successfully created:
Production IODF SYS6.IODF8A created.
Proceed to the next section to implement the configuration on the 2817 in preparation for its upgrade to a 2827.
4.8 HCD: Loading the 2827 processor IOCDS
You now have a production IODF, which is SYS6.IODF8A. Now update the IOCDS on the server that you want to upgrade (for example, SCZP301 to SCZP401). The IOCDS will be available for power-on reset after the processor is upgraded.
To update the IOCDS by using HCD Option 2.11, complete the following steps:
1. From the HCD main panel, select Option 2. Activate or process configuration data (Figure 4-120). Verify that the IODF is the production one created in 4.7, “HCD: Building the 2827 production IODF” on page 230 and press Enter.
                        z/OS V1.13 HCD
Command ===> ________________________________________________________
Hardware Configuration
Select one of the following.
2 0. Edit profile options and policies
1. Define, modify, or view configuration data
2. Activate or process configuration data
3. Print or compare configuration data
4. Create or view graphical configuration report
5. Migrate configuration data
6. Maintain I/O definition files
7. Query supported hardware and installed UIMs
8. Getting started with this dialog
9. What's new in this release
For options 1 to 5, specify the name of the IODF to be used.
I/O definition file . . . 'SYS6.IODF8A' +
 
Figure 4-120 Main menu: Select Activate or Process Configuration Data
2. The Activate or Process Configuration Data panel opens (Figure 4-121). Select Option 11. Build and manage S/390 microprocessor IOCDSs and IPL attributes, and press Enter.
 
----- Activate or Process Configuration Data -----
Select one of the following tasks.
11 1. Build production I/O definition file
2. Build IOCDS
3. Build IOCP input data set
4. Create JES3 initialization stream data
5. View active configuration
6. Activate or verify configuration
dynamically
7. Activate configuration sysplex-wide
8. *Activate switch configuration
9. *Save switch configuration
10. Build I/O configuration data
11. Build and manage S/390 microprocessor
IOCDSs and IPL attributes
12. Build validated work I/O definition file
Figure 4-121 Activate or Process Configuration Data: Select Build IOCDSs
This example assumes that you have connectivity to the 2097 or 2817 that is being upgraded over the the HMC local network to create an IOCDS.
If the server being upgraded is not accessible from the HMC LAN, create an IOCP file from HCD and then create a stand-alone IOCP. You can do so by using the same process that you used to create an IOCP file for the CMT.
 
Tip: The Support Element can now read an IOCP file that is in .zip format.
3. The S/390 Microprocessor Cluster List panel opens (Figure 4-122). Select the 2097 or 2817 being upgraded from the list by typing a forward slash (/) to update one of its IOCDSs and then pressing Enter.
                      S/390 Microprocessor Cluster List Row 1 of 4
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more CPCs, then press Enter.
--------------CPC-------------- IODF
/ SNA Address Type Model Processor ID
_ USIBMSC.SCZP101 2094 S18 SCZP101
_ USIBMSC.SCZP201 2097 E26 SCZP201
/ USIBMSC.SCZP301 2817 M32 SCZP401
******************************* Bottom of data ********************************
Figure 4-122 S/390 Microprocessor Cluster List
4. The Actions on selected CPCs panel is displayed (Figure 4-123). Select Option 1. Work with IOCDSs and press Enter.
----------------- Actions on selected CPCs --------
Select by number or action code and press Enter.
1_ 1. Work with IOCDSs . . . . . . . . . . (s)
2. Work with IPL attributes . . . . . . (i)
3. Select other processor configuration (p)
Figure 4-123 Actions on selected CPCs: Work with IOCDSs
5. The IOCDS List panel is displayed(Figure 4-124). Select the IOCDS that you want to update for the 2097 or 2817 upgrade by typing a forward slash (/) and pressing Enter.
                                 IOCDS List Row 1 of 4 More: >
Command ===> _______________________________________________ Scroll ===> CSR
Select one or a group of IOCDSs, then press Enter.
-----Token Match----- Write
/ IOCDS Name Type Status IOCDS/HSA IOCDS/Proc. Protect
/ A0.SCZP401 IODF78 LPAR Alternate Yes No No
_ A1.SCZP401 IODF79 LPAR Alternate Yes No No
_ A2.SCZP401 IODF00 LPAR POR Yes No Yes-POR
_ A3.SCZP401 IODF77 LPAR Alternate No No No
******************************* Bottom of data ********************************
Figure 4-124 IOCDS List
6. The Actions on selected IOCDSs panel opens (Figure 4-125). Select Option 1. Update IOCDS and press Enter.
---------------- Actions on selected IOCDSs ---------
Select by number or action code and press Enter.
1_ 1. Update IOCDS . . . . . . . . . . . . (u)
2. Switch IOCDS . . . . . . . . . . . . (s)
3. Enable write protection . . . . . . (e)
4. Disable write protection . . . . . . (w)
Figure 4-125 Actions on selected IOCDSs
7. The Build IOCDSs panel opens (Figure 4-126). Verify that all the information is correct. Complete the Title1 field, set Write IOCDS in preparation of upgrade to Yes, and press Enter.
 
------------------------------- Build IOCDSs --------------------------------
Row 1 of 1
Command ===> ___________________________________________ Scroll ===> CSR
Specify or revise the following values.
IODF name . . . . . . . . . : 'SYS6.IODF8A'
Title1 . IODF8A__________________________________________________________
Title2 : SYS6.IODF8A - 2012-07-20 15:57
Write IOCDS in
IOCDS Switch IOCDS preparation of upgrade
A0.SCZP401 No Yes
***************************** Bottom of data ******************************
Figure 4-126 Build IOCDSs
 
Tip: Specifying Yes in the Write IOCDS in preparation of upgrade field is only required when you are upgrading the existing hardware and want to write the IOCDS for a 2827 from the existing hardware. The Yes value permits the writing of an IOCDS that contains information that the current hardware does not recognize.
8. Because Yes was specified for the Write IOCDS in preparation of upgrade field, HCD now displays a confirmation panel (Figure 4-127). Press Enter to continue.
------------------------------- Build IOCDSs --------------------------------
---------- Confirm Write IOCDS in preparation of processor upgrade ----------
Row 1 of 1
Command ===> ___________________________________________ Scroll ===> CSR
Scroll forward to view the complete list of IOCDSs which will be written
regardless of processor type in preparation of a processor upgrade. Press
F3 or F12 to cancel, press ENTER to confirm the write request.
The processor receiving the IOCDS(s) must be a CMOS processor.
You will not be able to perform a POR using the new IOCDS until your
processor has been upgraded. Do not make the new IOCDS the active one on
your processor. Do not activate any I/O configuration changes in the IODF
until your processor has been upgraded. Keep the old processor definition
in an IODF until after the upgrade.
IOCDS
A0.SCZP401
***************************** Bottom of data ******************************
Figure 4-127 Build IOCDSs (Confirm Write IOCDS)
9. The Job Statement Information panel is displayed (Figure 4-128). Enter the job statements as required by the installation and press Enter. HCD submits the job to update the IOCDS.
 
Tip: Route the job to run on the image to which you are logged on. In that way, you know that the image can “see” the new 2827 to update its IOCDS.
------------------------- Job Statement Information -------------------
 
Specify or revise the job statement information.
Job statement information  
//WIOCP JOB (ACCOUNT),'NAME'
//*
//*
//*
Figure 4-128 Job Statement Information
10. Verify the job output to ensure that the IOCDS was written without error and to the correct IOCDS. You should receive the following message:
ICP057I IOCP JOB WIOCP SUCCESSFUL. LEVEL A0 IOCDS REPLACED.
11. Now if you return to HCD Option 2.11 and view the IOCDS, you note that the SNA Address remains at USIBMSC.SCZP201 (Figure 4-129).
  Goto Query Help
------------------------------------------------------------------------------
S/390 Microprocessor Cluster List Row 1 of 4
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more CPCs, then press Enter.
--------------CPC-------------- IODF
/ SNA Address Type Model Processor ID
_ USIBMSC.SCZP101 2094 S18 SCZP101
_ USIBMSC.SCZP201 2097 E26 SCZP201
s USIBMSC.SCZP301 2817 M32 SCZP401
******************************* Bottom of data ********************************
Figure 4-129 IOCDS with upgrade IODF
12. Also, when you select USIBMSC.SCZP301, notice that IOCDS A0 (which you wrote the upgrade IODF to) has a status of invalid (Figure 4-130).This error occurs because you specified Yes for the Write IOCDS in preparation for upgrade field, and the IOCDS contains IOCP statements and code relevant only for a 2827 processor.
The status switches when this processor is upgraded to a 2827. The 2827 IOCDS status changes to Alternate and the 2097 or 2817 IOCDSs changes to Invalid.
 
Tip: Generally, rewrite the IOCDS written in preparation for the upgrade at your earliest convenience. Subsequent MESs might cause an IOCDS written in preparation for an upgrade to become invalid.
******************************* Bottom of data ********************************
Goto Query Help
------------------------------------------------------------------------------
IOCDS List Row 1 of 4 More: >
Command ===> _______________________________________________ Scroll ===> CSR
Select one or a group of IOCDSs, then press Enter.
-----Token Match----- Write
/ IOCDS Name Type Status IOCDS/HSA IOCDS/Proc. Protect
_ A0.SCZP401 IODF8A LPAR Invalid No Yes No
_ A1.SCZP401 IODF79 LPAR Alternate Yes No No
_ A2.SCZP401 IODF00 LPAR POR Yes No Yes-POR
_ A3.SCZP401 IODF77 LPAR Alternate No No No
******************************* Bottom of data ********************************
Figure 4-130 IOCDS showing status
4.9 The HMC: Steps for profile activation
This section addresses the steps for activating profiles.
4.9.1 Building the Reset Profile and pointing to required IOCDS
Now that the IODF is written to an IOCDS, a Reset (power-on reset) Profile must be built to point to that IOCDS. This Reset Profile is used to power-on reset the 2827 after it is upgraded.
To build the Reset Profile, complete the following steps:
1. Log on using SYSPROG authority to the HMC workstation supplied with the 2827, or use a remote web browser and select the 2097 or 2817 that you are upgrading.
 
Explanation: Use HMC V2.12.0 because your HMC is usually upgraded before the upgrade of the 2097 or 2817.
2. Under Systems Management, click Systems to expand the list, or under Ensemble Management, click Members to expand the list.
3. Under Systems or Members, click the system to select it (in this example, SCZP301).
4. On the Tasks pad, click Operational Customization to expand it, and select Customize/Delete Activation Profiles.
5. Select the “Last Used” Reset Profile and select Customize profile.
6. Save this “Last Used” profile with a new Profile name to be referred to when the power-on reset is required (for example, SCZP301T) (Figure 4-131).
Figure 4-131 Customize Activation Profiles (Saving current reset profile with a different name)
7. Select the new profile (SCZP301T) and click Customize profile.
8. Click the IOCDS that you updated in the previous step (for example, IOCDS-A0). The window that is shown in Figure 4-132 opens.
Figure 4-132 Activation Profiles: Message ACTB0PDL
Depending on the circumstances, you might want to select Yes or No. You might also want to review the Partition Activation List.
9. Click Yes and note the status of the Reset Profile now (Figure 4-133).
Figure 4-133 Activation Profiles (New ‘Not Valid’ IOCDS selected)
10. If you click any of the profile tabs (General or Storage, for example), the ACTB0PE2 message opens as shown in Figure 4-134.
Figure 4-134 Activation Profiles: Message ACTB0PE2
11. Click No to continue working with the new IOCDS or Yes to return to the previous window.
12. Click Save.
13. Click OK. Review the items in the following sections.
Building/Verifying the Image Profiles
While still in the Reset Profile, you can now review the Image Profile attributes.
Building/Verifying the Load Profiles
Go through the Load (IPL) Profiles for this 2094 or 2097 and verify that you are satisfied with all the IPL and LOADPARM parameters defined for the Images that will run on the 2827.
Building/Verifying the Load Members in SYS#.IPLPARM
You might require more Load Members defined in SYS#.IPLPARM after the processor is upgraded to the 2827.
If you used the HWNAME parameter to point to the Processor ID, update the parameter to point to the new Processor ID. In this example, the parameter is changed from SCZP301 to SCZP401.
Server Time Protocol configuration
Review the Server Time Protocol (STP) configuration to ensure that the correct External Time Source has been configured and you are connected to the correct Coordinated Time Network.
For more information about setting up your STP environment, see Chapter 8, “Server Time Protocol Setup” on page 463.
4.9.2 Performing a power-on reset of the 2827
When the 2097 or 2817 processor is upgraded to a 2827, the IBM service representative runs a power-on reset (POR) with a Diagnostic IOCDS.
After this POR is complete and the IBM service representative is satisfied with the state of the processor, the service representative hands the processor over to you. You then run another power-on reset using the Reset Profile created in 4.9.1, “Building the Reset Profile and pointing to required IOCDS” on page 239.
 
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.17.184.90