Preparing for a new z14 ZR1
This chapter describes the following scenarios when preparing for a z14 ZR1 server installation:
•Upgrading an existing IBM Z server (z13s) to a z14 ZR1 server and maintaining an existing serial number.
•Installing a new z14 ZR1 server.
Our examples show upgrading from an existing z13s or installing a new z14 ZR1 only. An upgrade includes a new frame, new drawers (CPC and PCIe+ I/O drawers), and new or carry-forward I/O features.
Because many environments exists, the results that are achieved in your environment might differ from those that are described here.
This chapter includes the following topics:
•3.2, “Upgrading a z13s to a z14 ZR1: Maintaining existing serial number (Frame roll MES)” on page 33
3.1 Hardware features
This section describes the channel (CHPID) types and hardware features for a z14 ZR1.
CHPID type HYL is new for 3907.
The following hardware features are new or available for order with a 3907:
•FC #0427 - FICON Express16S+ LX
•FC #0428 - FICON Express16S+ SX
•FC #0422 - OSA-Express6S GbE LX
•FC #0423 - OSA-Express6S GbE SX
•FC #0424 - OSA-Express6S 10 GbE LR
•FC #0425 - OSA-Express6S 10 GbE SR
•FC #0426 - OSA-Express6S 1000BASE-T Ethernet
•FC #0412 - RoCE Express2 10 GbE
•FC #0893 - Crypto Express6S
•FC #0433 - Coupling Express LR
•FC #0431 - zHyperLink Express
•FC #0614 - IBM Virtual Flash Memory (VFM)
•FC #0172 - Integrated Coupling Adapter SR
•FC #0901 - Regional Crypto Enablement (RCE)
The following CHPID types are migrated (carry forward):
•FC and FCP
•OSC, OSD, OSM, and OSX
•CL5, CS5, and ICP
•IQD
The following hardware features can be migrated to the 3907:
•FC #0418 - FICON Express16S LX
•FC #0419 - FICON Express16S SX
•FC #0409 - FICON Express8S LX
•FC #0410 - FICON Express8S SX
•FC #0413 - OSA-Express5S GbE LX
•FC #0414 - OSA-Express5S GbE SX
•FC #0415 - OSA-Express5S 10 GbE LR
•FC #0416 - OSA-Express5S 10 GbE SR
•FC #0417 - OSA-Express5S 1000BASE-T Ethernet
•FC #0411 - RoCE Express 10 Gbe SR
•FC #0420 - zEDC Express
•FC #0890 - Crypto Express5S
•FC #0172 - Integrated Coupling Adapter SR
•FC #0901 - Regional Crypto Enablement (RCE)
The following CHPID types are not migrated (no carry forward):
•CIB
•OSN
The following hardware features cannot be ordered nor carried forward for an upgrade to 3907:
•FC #3325 - FICON Express8 LX
•FC #3326 - FICON Express8 SX
•FC #0865 - Crypto Express4S
•FC #0403 - Flash Express
•FC #0402 - Flash Express
•FC #0170 - HCA3-O 1x LR IFB
•FC #0171 - HCA3-O 12x IFB
•IBM zAware Firmware
•STP Mixed CTN
3.2 Upgrading a z13s to a z14 ZR1: Maintaining existing serial number (Frame roll MES)
This section describes the steps to upgrade a z13s server that is defined in your IODF to a z14 ZR1 server and maintaining the system serial number.
3.2.1 Scenario overview
This scenario describes the configuration steps to upgrade a 2965 (z13s) CPC to a 3907 (z14 ZR1) CPC. Consider the following key factors:
•Hardware configuration definition (HCD) requires a new CPC (processor) ID for the 3907.
•Keep the same CPC name for the 3907 (this is optional, the CPC name can be changed).
•The 3907 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 2965 production I/O definition file (IODF).
•The target IODF is a new 3907 work IODF.
•HCD actions:
– Migrate updated IOCP statements.
– Build production IODF.
– Remote write IODF to input/output configuration data set (IOCDS).
•The HMC actions:
– Build the Reset Profile and point to required IOCDS.
– Build/verify the Image Profiles.
– Build/verify the Load Profiles.
– Perform a power-on reset.
The example uses a 2965-N20 with a Processor ID of LEPUS with three CSSs (CSS ID=0 to CSS ID=2). This system is replaced with a 3907-ZR1 with a Processor ID of MUSCA2 and three CSSes.
The CPC name LEPUS and serial number are not changed.
The migration options and tool requirements are listed in Table 3-1. For more information about the process steps, see “HCD: Migrating the existing 2965 IODF” on page 34.
Table 3-1 2965 I/O configuration migrated to a 3907
|
2965 to 3907
|
Upgrade existing 2965 to a 3907 (MES 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
|
|
CHPID Mapping Tool Program
|
Optional, but good for verifying configuration
|
|
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
|
HCD: Migrating the existing 2965 IODF
The following steps describe how to upgrade an existing 2965 Processor in your IODF to the new 3907 Processor using HCD. Then, migrate the I/O configuration and logical partitions from the 2965 to the 3907. Using HCD, the sequence includes the following steps:
3.2.2 Creating the work IODF from the current 2965 production IODF
HCD is the tool that is used to make a work IODF, but first we start from the current production IODF that contains the 2965 processor we are upgrading (in our example, SYS6.IODF78).
3.2.3 Repeating the 2965 processor to be replaced
To repeat the 2965 processor in HCD, complete the following steps:
1. From the main HCD panel, select option 1.3. Processor List.
2. In the Processor List (see Figure 3-1 on page 35), enter r (for repeat) next to the 2965 that you want to upgrade and press Enter.
|
Processor List Row 1 of 3 More:
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more processors, then press Enter. To add, use F11.
/ Proc. ID Type + Model + Mode+ Serial-# + Description
_ CETUS 3906 M03 LPAR 0EE0F73906 Cetus
r LEPUS 2965 N20 LPAR 0BB4B72965 Lepus
_ MUSCA 3907 ZR1 LPAR 007A883907 Musca
|
Figure 3-1 Processor List: Repeating processor
3. The Identify Target IODF panel opens. Do one of the following actions:
– To retain all the other processor definitions in the IODF, press Enter.
– Enter a different target IODF data set name. In this case, only the processor that you are repeating is retained in the target IODF.
4. The Create Work I/O Definition File panel prompts you to enter the data set name of the target IODF (for example, SYS6.IODF79.WORK).
5. The Repeat Processor panel opens (see Figure 3-2). Enter the Processor ID of the new 3907 (in this example, MUSCB), keep all the other fields unchanged, and press Enter.
|
*----------------------------- Repeat Processor ------------------------------*
| |
| |
| Specify or revise the following values. |
| |
| Processor ID . . . . . . . . . MUSCB___ |
| |
| Processor type . . . . . . . : 2965 |
| Processor model . . . . . . : N20 |
| Configuration mode . . . . . : LPAR |
| |
| Serial number . . . . . . . . 0BB4B72965 |
| Description . . . . . . . . . Lepus |
| |
| Specify SNA address only if part of an System z cluster: |
| |
| Network name . . . . . . . . . IBM390PS + |
| CPC name . . . . . . . . . . . LEPUS + |
| |
| Local system name . . . . . . LEPUS |
| |
*------------------------------------* |
| New IODF SYS6.IODF79.WORK defined. | |
*------------------------------------* ---------------------------------------*
|
Figure 3-2 Repeat Processor: Defining a new Processor ID
3.2.4 Coupling Link information messages
You might receive severity messages (E, I, or W). As shown in Figure 3-3, CBDG441I, severity I messages are displayed in the example because the CF Link CHPIDs were not copied to the 3907 definition.
|
*------------------------------- Message List --------------------------------*
| Save Query Help |
| -------------------------------------------------------------------------- |
| Row 24 of 37 |
| Command ===> ___________________________________________ Scroll ===> CSR |
| |
| Messages are sorted by severity. Select one or more, then press Enter. |
| |
| / Sev Msg. ID Message Text |
| # processor MUSCA is not copied. |
| _ I CBDG441I The coupling facility connection between channel path |
| # 1.F4 of processor LEPUS and channel path 0.F5 of |
| # processor LEPUS is not copied. |
| _ I CBDG441I The coupling facility connection between channel path |
| # 1.F5 of processor LEPUS and channel path 0.F4 of |
| # processor LEPUS is not copied. |
| _ I CBDG441I The coupling facility connection between channel path |
| # 1.F6 of processor LEPUS and channel path 0.F7 of |
| # processor LEPUS is not copied. |
| _ I CBDG441I The coupling facility connection between channel path |
| # 1.F7 of processor LEPUS and channel path 0.F6 of |
| # processor LEPUS is not copied. |
| _ I CBDG271I Requested action on object LEPUS successfully processed. |
*-----------------------------------------------------------------------------*
|
Figure 3-3 Message List: Showing CBDG441I
To resolve this issue, complete the following steps:
1. Scroll until you reach the end of the messages and see the CBDG271I requested action on object LEPUS successfully processed message.
2. Press PF3 or PF12 to continue. As shown in Figure 3-4, an extra 2965 processor named MUSCB is available.
|
Processor List Row 1 of 4 More:
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more processors, then press Enter. To add, use F11.
/ Proc. ID Type + Model + Mode+ Serial-# + Description
_ CETUS 3906 M03 LPAR 0EE0F73906 Cetus
_ LEPUS 2965 N20 LPAR 0BB4B72965 Lepus
_ MUSCA 3907 ZR1 LPAR 007A883907 Musca
_ MUSCB 2965 N20 LPAR 0BB4B72965 Lepus
|
Figure 3-4 Processor List: Repeated processor
3.2.5 Deleting any unsupported items in the repeated 2965
If you are upgrading a processor that contains any CHPID types of OSN or CIB, they must be deleted from the IODF before changing the processor type to 3907.
|
Note: z14 ZR1 machine type 3907 does not support any InfiniBand coupling links. Therefore, all CHPIDs of type CIB must be deleted in an IODF for machine type 3907 and, if necessary, replaced with CHPID types CS5 or CL5.
|
To delete no longer supported CHPIDs, complete the following steps:
1. From the Processor List panel, select the newly created MUSCB processor and then press Enter, as shown in Figure 3-5.
|
Processor List Row 1 of 4 More:
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more processors, then press Enter. To add, use F11.
/ Proc. ID Type + Model + Mode+ Serial-# + Description
_ CETUS 3906 M03 LPAR 0EE0F73906 Cetus
_ LEPUS 2965 N20 LPAR 0BB4B72965 Lepus
_ MUSCA 3907 ZR1 LPAR 007A883907 Musca
s MUSCB 2965 N20 LPAR 0BB4B72965 Lepus
|
Figure 3-5 Processor List: Selected processor
|
Channel Subsystem List Row 1 of 3 More:
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more channel subsystems, then press Enter. To add, use F11.
Processor ID . . . : MUSCB Lepus
CSS Devices in SS0 Devices in SS1 Devices in SS2 Devices in SS3
/ ID Maximum + Actual Maximum + Actual Maximum + Actual Maximum + Actual
s 0 65280 14692 65535 480 65535 0 0 0
_ 1 65280 95 65535 0 65535 0 0 0
_ 2 65280 0 65535 0 65535 0 0 0
|
Figure 3-6 Channel Subsystem List: Selected CSS
3. Within the selected Channel Subsystem set a filter, as shown in Figure 3-7.
|
Goto Filter Backup Query Help
----- *-------------------------------------* ------------------------------
| 1 1. Set Filter | t Row 1 of 46 More:
Comma | 2. Clear Filter | ______________ Scroll ===> CSR
| 3. Count rows on (filtered) list |
Selec *-------------------------------------* nter. To add use F11.
Processor ID . . . . : MUSCB Lepus
Configuration mode . : LPAR
Channel Subsystem ID : 0
CHID+ Dyn Entry +
/ CHPID AID/P Type+ Mode+ Sw+ Sw Port Con Mng Description
_ 11 7E0 IQD SHR __ __ __ No IQD for ISM
_ 28 1E4 FC SHR 02 02 13 No fc sw - san64b-b-p19
_ 29 120 FC SHR __ __ __ No 16 Gbps - DS8KSU1 5/4/1 WAS 48
_ 2A 198 FCP SHR __ __ __ No 16 Gbps - SAN1 CLOUD-P12
_ 38 121 FC SHR __ __ __ No 16 Gbps - DS8KSU4 1/4/0 WAS 58
_ 39 1E5 FC SHR __ __ __ No 16 Gbps - DS8KSU4 4/4/0 WAS 5B
_ 3A 199 FCP SHR __ __ __ No 16 Gbps - SAN2 CLOUD-P12
_ 3B 19D FCP SHR __ __ __ No 16 Gbps - SANF48B-2
_ 44 124 FC SPAN 01 01 09 No fctc switch - san64b-a-p9
_ 45 125 FC SPAN 02 02 09 No fctc switch - san64b-b-p9
_ 48 158 FC SHR 01 01 13 No fc sw - san64b-a-p19
|
Figure 3-7 Channel Path List: Set Filter
|
*----------------------- Filter Channel Path List ------------------------*
| |
| |
| Specify or revise the following filter criteria. |
| |
| Channel path type . CIB |
| Operation mode . . . ____ + |
| Managed . . . . . . _ (Y = Yes; N = No) I/O Cluster ________ + |
| Dynamic entry switch __ + |
| Entry switch . . . . __ + |
| CF connected . . . . _ (Y = Connected; N = Not connected) |
| CHID AID/P PCHID/P _____ |
| |
| Description . . . . ________________________________ |
| |
| Partition . . . . . ________ + |
| Connected to CUs . . _ (Y = Connected; N = Not connected) |
| |
| |
| |
| |
*-------------------------------------------------------------------------*
|
Figure 3-8 Filter Channel Path type: Type CIB for channel path type
5. In the next panel, only channel definitions for channel path type CIB are shown. Delete these definitions, as shown in Figure 3-9. Then, press Enter.
|
Channel Path List Filter Mode. More:
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more channel paths, then press Enter. To add use F11.
Processor ID . . . . : MUSCB Lepus
Configuration mode . : LPAR
Channel Subsystem ID : 0
CHID+ Dyn Entry +
/ CHPID AID/P Type+ Mode+ Sw+ Sw Port Con Mng Description
d F6 07/1 CIB SPAN __ __ __ N No Wrap to F7
d F7 07/2 CIB SPAN __ __ __ N No Wrap to F6
|
Figure 3-9 Channel path list: Delete all channel definitions for type CIB
6. Confirm that SPANNED channels are deleted from all accessing channel subsystems by pressing Enter, as shown in Figure 3-10.
|
*--------------------- Confirm Delete Channel Path ---------------------*
| Row 1 of 2 | --
| Command ===> _____________________________________ Scroll ===> CSR |
| |
| Scroll forward to view the complete list of channel paths to be |
| deleted. Press ENTER to confirm delete request. Press F12 to cancel |
| delete request. |
| |
| Processor ID . . . . : MUSCB Lepus |
| Channel Subsystem ID : 0 |
| |
| CHID |
| CHPID Type Mode AID/P |
| F6 CIB SPAN 07/1 |
| F7 CIB SPAN 07/2 |
| ************************** Bottom of data *************************** | **
| |
| |
| |
| |
| |
*--------------------------------------------------------------------------*
| Spanned channel paths are deleted from all accessing channel subsystems. |
*--------------------------------------------------------------------------*
|
Figure 3-10 Confirm Delete Channel Path panel
3.2.6 Changing the M/T 2965 to 3907 and deleting the 2965
You can keep the original copy of the 2965 (LEPUS) or delete it from the IODF. In this example, keep it in the IODF for a few more steps.
To change the 2965 to a 3907, complete the following steps:
1. Enter c (for change) next to MUSCB to change the 2965 to a 3907 and press Enter. The Change Process Definition panel opens (see Figure 3-11 on page 41).
2. Make the following updates and press Enter:
– Update Processor type to 3907.
– Update Processor model to ZR1.
– Update the 2965 part of the Serial number to 3907 (that is, 0BB4B72965 to 0BB4B73907).
– Update Description to MUSCB.
– Update Local system name to MUSCB.
|
Note: Because we use HCD to write an IOCDS to this 2965 in preparation for an upgrade, we must leave the Network name and CPC name set to IBM390PS and LEPUS. These settings must be updated in the IODF after the 2965 is upgraded to a 3907.
|
|
*------------------------ Change Processor Definition ------------------------*
| |
| |
| Specify or revise the following values. |
| |
| Processor ID . . . . . . . . : MUSCB |
| Support level: |
| 2965 support, ISM, RCE, UID, CL5 |
| Processor type . . . . . . . . 3907 + |
| Processor model . . . . . . . ZR1 + |
| Configuration mode . . . . . . LPAR + |
| |
| Serial number . . . . . . . . 0BB4B73907 + |
| Description . . . . . . . . . MUSCB |
| |
| Specify SNA address only if part of an System z cluster: |
| |
| Network name . . . . . . . . . IBM390PS + |
| CPC name . . . . . . . . . . . LEPUS + |
| |
| Local system name . . . . . . MUSCB |
| |
| |
*-----------------------------------------------------------------------------*
|
Figure 3-11 Processors: Change Processor Definition panel
3. The Update Channel Path Identifiers panel opens (see Figure 3-12). No changes are made in this example.
|
*--------------------- Update Channel Path Identifiers ----------------------*
| Row 1 of 44 |
| Command ===> __________________________________________ Scroll ===> CSR |
| |
| Specify any changes to the channel path identifiers in the list below. |
| |
| Processor ID . . . . : MUSCB MUSCB |
| Channel Subsystem ID : 0 |
| |
| CHPID Type Side Until CHPID New CHPID + |
| 11 IQD __ 11 |
| 28 FC __ 28 |
| 29 FC __ 29 |
| 2A FCP __ 2A |
| 38 FC __ 38 |
| 39 FC __ 39 |
| 3A FCP __ 3A |
| 3B FCP __ 3B |
| 44 FC __ 44 |
| 45 FC __ 45 |
| 48 FC __ 48 |
| 49 FC __ 49 |
| 4A FC __ 4A |
*----------------------------------------------------------------------------*
|
Figure 3-12 Processors: Update Channel Path Identifiers panel
4. Press Enter for each Channel Subsystem ID.
The repeated 2965 processor is successfully changed to a 3907-ZR1, as shown in Figure 3-13.
|
Processor List Row 1 of 4 More:
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more processors, then press Enter. To add, use F11.
/ Proc. ID Type + Model + Mode+ Serial-# + Description
_ CETUS 3906 M03 LPAR 0EE0F73906 Cetus
_ LEPUS 2965 N20 LPAR 0BB4B72965 Lepus
_ MUSCA 3907 ZR1 LPAR 007A883907 Musca
_ MUSCB 3907 ZR1 LPAR 0BB4B73907 MUSCB
|
Figure 3-13 Processor List: Changed processor
3.2.7 Deleting the 2965 processor definition
Now that the 2965 was repeated and changed to a 3907, the original 2965 definition (LEPUS) must be deleted so that the required CF Links can be restored.
To delete the 2965 processor definition, complete the following steps:
|
Processor List Row 1 of 4 More:
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more processors, then press Enter. To add, use F11.
/ Proc. ID Type + Model + Mode+ Serial-# + Description
_ CETUS 3906 M03 LPAR 0EE0F73906 Cetus
d LEPUS 2965 N20 LPAR 0BB4B72965 Lepus
_ MUSCA 3907 ZR1 LPAR 007A883907 Musca
_ MUSCB 3907 ZR1 LPAR 0BB4B73907 MUSCB
|
Figure 3-14 Processor List: Deleting processor
|
Processor List Row 1 of 3 More:
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more processors, then press Enter. To add, use F11.
/ Proc. ID Type + Model + Mode+ Serial-# + Description
_ CETUS 3906 M03 LPAR 0EE0F73906 Cetus
_ MUSCA 3907 ZR1 LPAR 007A883907 Musca
_ MUSCB 3907 ZR1 LPAR 0BB4B73907 MUSCB
|
Figure 3-15 Processor List: Processor deleted
3.2.8 Reconnecting the CF channel paths that were not migrated
Manually redefine the CF Links that you want from the MUSCB (previously LEPUS) processor to any other processor, along with any Internal Coupling Facility links that you want. To help in this effort, you can get a CF connection report from the previous production IODF containing the 2965. Alternatively, you can make a note of all CBDG441I error messages that you received, as described in 3.2.7, “Deleting the 2965 processor definition” on page 42.
3.3 Saving and restoring OSA configuration data
The three processes for Open Systems Adapter (OSA) cards that you might need to use when upgrading or replacing your processor are described in this section.
3.3.1 Using OSA/SF to save and restore OSE OAT configuration data
For more information about how to save and restore any OSA configuration data such the OSA Address Table (OAT), see 7.3.1, “Saving and restoring OSA-ICC configuration” on page 150.
3.3.2 Exporting and importing OSA-ICC configuration data with OSA Advanced Facilities
For more information about exporting and importing process for OSA-ICC Server and Session configuration data, see 7.3, “Defining a new OSA-ICC configuration by using OSA Advanced facilities” on page 145.
3.3.3 Using OSA Advanced Facilities to set OSA parameters
For more information about the process of changing the OSA port speed or MAC addresses, see 6.3, “Customizing OSA-Express using OSA Advanced facilities” on page 127.
3.4 Installing a new z14 ZR1 into an existing environment
In this section, we describe the steps to add an IBM z14 ZR1 into an existing IBM Z environment.
3.4.1 Scenario overview
This scenario shows configuration steps for defining a new 3907 processor into an existing hardware environment. This process includes the following key considerations:
•HCD requires a new processor ID for the 3907.
•HCD requires a new CPC name for the 3907.
•The 3907 processor connects to new switch ports and new control unit interfaces.
•The control unit interfaces connect to the same switch ports as they did previously.
•The starting IODF is the current 3906/2965 production IODF.
•The target IODF is a new work IODF with a 3907 defined.
•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.
This example defines a new 3907-ZR1 with a Processor ID of MUSCA and with three CSSs (CSS ID=0 to CSS ID=2).
The CPC name of MUSCA and serial number of 02-07A88 are used for the 3907.
The tool requirements are listed in Table 3-2.
Table 3-2 I/O configuration for a new (additional) 3907
|
New (additional) 3907
|
New (additional) 3907 to connect to the new switch ports and same control units to which existing processors connect
|
|
Processor ID
|
Requires a new Processor ID
|
|
CPC name
|
Requires a new CPC name
|
|
Channel to switch port connections
|
Extra ports
|
|
Control Unit to switch port connections
|
Same ports
|
|
Starting IODF
|
Current active production IODF
|
|
Target IODF
|
Create a work IODF
|
|
HCD action
|
Add processor
|
|
CHPID Mapping Tool Program
|
Optional, but good for verifying configuration
|
|
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, CHIPID Report and CHIPID to CU Report
|
HCD: Creating a 3907 IODF
The following steps explain how to define an additional 3907 processor in your existing IODF to the existing I/O configuration by using HCD:
3.4.2 Creating a work IODF from the current production IODF
HCD is the tool that is used to make a work IODF. However, we start from the current production IODF that contains the existing hardware environment that is connected to the new 3907 (for example, SYS6.IODF24).
3.4.3 Adding the new 3907 processor
To add the new 3907 processor, complete the following steps:
1. From the HCD main menu, select option 1.3, Processor List.
2. In the Processor List (Figure 3-16), press PF11, or enter add on the command line to add a processor and press Enter.
|
Processor List Row 1 of 2 More:
Command ===> add____________________________________________ Scroll ===> CSR
Select one or more processors, then press Enter. To add, use F11.
/ Proc. ID Type + Model + Mode+ Serial-# + Description
_ CETUS 3906 M03 LPAR 0EE0F73906 Cetus
_ LEPUS 2965 N20 LPAR 0BB4B72965 Lepus
|
Figure 3-16 Processor List: Adding a processor
The Add Processor panel opens (see Figure 3-17).
|
+------------------------------- Add Processor -------------------------------+
| |
| |
| Specify or revise the following values. |
| |
| Processor ID . . . . . . . . . . ________ |
| Processor type . . . . . . . . . ________ + |
| Processor model . . . . . . . . ________ + |
| Configuration mode . . . . . . . LPAR + |
| Number of channel subsystems . . _ + |
| |
| Serial number . . . . . . . . . __________ |
| Description . . . . . . . . . . ________________________________ |
| |
| Specify SNA address only if part of a System z cluster: |
| |
| Network name . . . . . . . . . . ________ + |
| CPC name . . . . . . . . . . . . ________ + |
| |
| Local system name . . . . . . . ________ |
| F1=Help F2=Split F3=Exit F4=Prompt F5=Reset F9=Swap |
| F12=Cancel |
+-----------------------------------------------------------------------------+
|
Figure 3-17 Add Processor: Data fields to be updated
3. Specify the appropriate values. For example, specify the following values, as shown in Figure 3-18:
– Processor ID : MUSCA
– Processor type: 3907
– Processor model: ZR1
– Number of channel subsystems: Blank for now
– Serial number : 007A883907
– Network name : IBM390PS
– CPC name : MUSCA
– Local System Name: Blank for now
|
*------------------------------- Add Processor -------------------------------*
| |
| |
| Specify or revise the following values. |
| |
| Processor ID . . . . . . . . . . MUSCA |
| Processor type . . . . . . . . . 3907 + |
| Processor model . . . . . . . . ZR1 + |
| Configuration mode . . . . . . . LPAR + |
| Number of channel subsystems . . _ + |
| |
| Serial number . . . . . . . . . 007A883907 |
| Description . . . . . . . . . . ________________________________ |
| |
| Specify SNA address only if part of a System z cluster: |
| |
| Network name . . . . . . . . . . IBM390PS + |
| CPC name . . . . . . . . . . . . MUSCA___ + |
| |
| Local system name . . . . . . . ________ |
| |
| |
*-----------------------------------------------------------------------------*
|
Figure 3-18 Add Processor: Data fields updated
4. Press Enter. The Create Work I/O Definition File panel opens and prompts you to enter the data set name of the target IODF (for example, SYS6.IODF79.WORK).
|
Processor List Row 1 of 3 More:
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more processors, then press Enter. To add, use F11.
/ Proc. ID Type + Model + Mode+ Serial-# + Description
_ CETUS 3906 M03 LPAR 0EE0F73906 Cetus
_ LEPUS 2965 N20 LPAR 0BB4B72965 Lepus
_ MUSCA 3907 ZR1 LPAR 007A883907 ______________________________
******************************* Bottom of data *****************************
*----------------------------------------------------------------*
| Definition of processor MUSCA has been extended to its maximum |
| configuration. |
*----------------------------------------------------------------*
|
Figure 3-19 Processor List: New processor added
The message at the bottom of the panel indicates that the processor definition is extended to its maximum configuration. This message is generated because part of the main storage is allocated as a fixed-size Hardware Systems Area, which is not addressable by application programs. In HCD, when you define as new or redefine a processor as a 3907, HCD automatically defines the maximum configuration of three CSSs and 40 logical partitions.
6. Enter s next to MUSCA and press Enter. The Channel Subsystem List is displayed. Here you can see three channel subsystems (CSS0-CSS2) that are defined with the default MAXDEV values for SS0 of 65280 set by HCD and 65535 set for SS1, and SS2, (see Figure 3-20).
|
Channel Subsystem List Row 1 of 3 More:
Command ===> _______________________________________________ Scroll ===> CSR
Select one or more channel subsystems, then press Enter. To add, use F11.
Processor ID . . . : MUSCA
CSS Devices in SS0 Devices in SS1 Devices in SS2 Devices in SS3
/ ID Maximum + Actual Maximum + Actual Maximum + Actual Maximum + Actual
_ 0 65280 0 65535 0 65535 0 0 0
_ 1 65280 0 65535 0 65535 0 0 0
_ 2 65280 0 65535 0 65535 0 0 0
|
Figure 3-20 Channel Subsystem List: Three subchannel sets
|
Tip: In addition to IPL from subchannel set 0 (SS0), IBM Z server with driver level 93 and above support IPL from subchannel set 1 (SS1), subchannel set 2 (SS2), or subchannel set 3 (SS3). Devices that are used early during IPL processing can now be accessed by using subchannel set 1, subchannel set 2, or subchannel set 3.
This configuration allows the users of Metro Mirror (PPRC) secondary devices that are defined by using the same device number and a new device type (3390D) in an alternative subchannel set to be used for IPL, IODF, and stand-alone memory dump volumes when needed.
IPL from an alternative subchannel set is supported by z/OS V1.13 or later, and V1.12 and V1.11 with program temporary fixes (PTFs). IPL applies to the Fibre Channel connection (FICON) and High Performance FICON for z Systems (zHPF) protocols.
|
3.5 Saving and restoring any OSA configuration data
The three processes for OSA cards that you might need to use when upgrading or replacing your processor are described next.
3.5.1 Using OSA/SF to save and restore OSE OAT configuration data
For more information about how to save and restore any OSA configuration data, such as the OAT, see 7.3.1, “Saving and restoring OSA-ICC configuration” on page 150.
3.5.2 Export and import OSA-ICC configuration data with OSA Advanced Facilities
For more information about the exporting and importing process for OSA-ICC Server and Session configuration data, see 7.3, “Defining a new OSA-ICC configuration by using OSA Advanced facilities” on page 145.
3.5.3 Using OSA Advanced Facilities to set OSA parameters
For more information about the process of changing the OSA port speed or MAC addresses, see 6.3.2, “Setting OSA parameters using OSA Advanced Facilities” on page 136.
3.6 Extra steps and processes
When you are ready to map the PCHIDs from the z14 ZR1 CFR file to the CHPIDs in your exported IODF, see Chapter 4, “Mapping CHIDs to CHPIDs by using the CMT” on page 49.
For more information about defining the I/O configuration for your system, see Chapter 5, “Production IODF and setting up the CPC” on page 85.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.