Migrate to an IBM zEnterprise EC12 or IBM zEnterprise BC12 server

Description

An IBM zEnterprise EC12 (zEC12) and IBM zEnterprise BC12 (zBC12) server can include the following in a zEnterprise environment:
  • IBM zEnterprise EC12 server Central Processing Complex (CPC) or IBM zEnterprise BC12 server CPC
  • zEnterprise BladeCenter Extension (zBX) Model 003 with its integrated optimizers or select IBM blades
  • zEnterprise Unified Resource Manager (Unified Resource Manager)

The zEC12 and zBC12 are distinct from the earlier zEnterprise and other servers. In this publication, the IBM zEnterprise EC12 server is referred to as the model zEC12 server and the IBM zEnterprise BC12 server is referred to as the model zBC12 server.

In a Parallel Sysplex you can include the following servers:
  • zEC12 and zBC12 servers
  • zEnterprise servers (z196 or z114)
  • z10 EC and z10 BC servers.

The specific zEC12 and zBC12 functions including base support that are used by z/OS depend on the z/OS release. Availability and other restrictions are noted in the "Notes" column. PTFs might be required for many of these functions. See Actions you can take before you order a zEC12 or zBC12 server for information about finding the appropriate PTFs.

Table 1. zEC12 and zBC12 server functions included in the base support for z/OS V2R1 and z/OS V2R2
zEC12 and zBC12 function included in base z/OS support (Y/N) V2R1¹ V2R2¹
Base support Y Y
OSA-Express4S (GbE LX and SX, 1000BASE-T, 10 GbE LR and SR) Y Y
OSA-Express5S (GbE LX and SX, 1000BASE-T, 10 GbE LR and SR) Y Y
FICON Express 8S (CHPID FC) Y Y
High Performance FICON (zHPF) Y Y
Parallel Sysplex InfiniBand (PSIFB) Coupling Link Y Y
CPU measurement facility Y Y
New z/Architecture instructions: XL C/C++ ARCH(10) and TUNE(10) parameters Y Y
Crypto Express3 Toleration (if carried forward) Y Y
IBM zEnterprise Unified Resource Manager Y Y
IBM zEnterprise BladeCenter Extension (zBX) Model 3 Y Y
GRS FICON CTC toleration Y (requires additional PTFs for exploitation)² Y
Notes:
  1. PTFs for base support have a fix category of either:
    • For zEC12: IBM.Device.Server.zEC12-2827
    • For zBC12: IBM.Device.Server.zBC12-2828
  2. PTFs for exploitation have a fix category of either:
    • For zEC12: IBM.Device.Server.zEC12-2827.Exploitation
    • For zBC12: IBM.Device.Server.zEC12-2828.Exploitation
  3. PTFs for zEDC exploitation or software decompression have a fix category (for both zEC12 and zBC12) of IBM.Function.zEDC.
Table 2. Exploitation of zEC12 and zBC12 server functions supported by z/OS V2R1 and z/OS V2R2
zBC12 functional exploitation of z/OS support (Y/N) V2R1² V2R2²
Coupling Facility Control Code (CFCC) Level 18 Y Y
Coupling Facility Control Code (CFCC) Level 19 Y Y
Coupling Facility Control Code (CFCC) Level 19 Coupling thin interrupt support Y Y
Crypto Express4S (#0865) exploitation, including Enterprise Security PKCS #11-Hardware Security Module (HSM), DUKPT for MAC and Data Encryption, Cipher Text Translate CCA Verb, PKDS/TKDS Constraint Relief, Random Number Cache, FIPS on Demand, and Wrapping Keys with Strong Keys Y Y
Crypto Express4S CCA enhancements, including: Export TDES key under AES transport key, Diversified Key Generation CBC, IPEK, RKX key wrapping method, and Integration of UDX into CCA Y (requires the Cryptographic Support for z/OS V1R13-z/OS V2R1 web deliverable (FMID HCR77A1) . Y
Crypto Express4S: EP11 enhancements when the Crypto Express4S PCIe adapter is configured as an EP11 coprocessor, including: (PKCS #11 v2.1 PSS, EP11 Key agreement algorithms, and Offload Generation of Domain Parameters) Y (requires the Cryptographic Support for z/OS V1R13-z/OS V2R1 web deliverable (FMID HCR77A1) Y
Crypto Express4S support of greater than 16 Domains Y Y
Flash Express (Storage Class Memory or SCM) Y Y
Pageable 1 MB Large Page Support. Y Y
Dynamic reconfiguration support for Flash Express. Y Y
2 GB Large Page support. Y Y
Optional PLPA/common page data set support. Y Y
10GbE RoCE Express Y Y
Java Exploitation of Transactional Execution (requires Java7 SR3) Y Y
IBM System Advanced Workload Analysis Reporter (IBM zAware) Y Y
New z/Architecture instructions: XL C/C++ ARCH(10) and TUNE(10) parameters Y Y
New z/Architecture Assembler Language instruction mnemonic Y Y
zEDC capability using zEDC Express Y³ (requires the z/OS zEDC software feature to be enabled) Y³ (requires the z/OS zEDC software feature to be enabled)
Notes:
  1. PTFs for base support have a fix category of either:
    • For zEC12: IBM.Device.Server.zEC12-2827
    • For zBC12: IBM.Device.Server.zBC12-2828
  2. PTFs for exploitation have a fix category of either:
    • For zEC12: IBM.Device.Server.zEC12-2827.Exploitation
    • For zBC12: IBM.Device.Server.zEC12-2828.Exploitation
  3. PTFs for zEDC exploitation or software decompression have a fix category (for both zEC12 and zBC12) of IBM.Function.zEDC.

Table 3 provides more details about this migration action. Use this information to plan your changes to the system.

Table 3. Information about this migration action
Element or feature: Multiple.
When change was introduced:
  • IBM zEnterprise EC12, which first shipped September 2012.
  • IBM zEnterprise BC12 (zBC12), which first shipped September 2013.
Applies to migration from: z/OS V2R2, z/OS V2R1, and z/OS V1R13.
Timing: Anytime before you introduce a zEC12 or zBC12 server into your environment.
Is the migration action required? Yes, if you want to run z/OS V2R2, z/OS V2R1 and z/OS V1R13 on a zEC12 or zBC12 server, or if you want to run a Coupling Facility on a zEC12 or zBC12 server. If you will run only a Coupling Facility on a zEC12 or zBC12 system, only the sysplex-related actions are relevant.
Target system hardware requirements:
  • A zEC12 or zBC12
  • Additional hardware required for specific functions.
    • IBM devices previously attached to IBM System z10, z196 and zSeries servers are supported for attachment to zEC12 channels, unless otherwise noted. The subject I/O devices must meet FICON architecture requirements
    • IBM zAware requires the IBM zAware server firmware (FC #0011, #0101, and #0102)
    • Flash Express requires FC #0402
    • zEDC Express requires FC #0420
    • 10 GbE RoCE Express FC #0411
    • Use of IBMWebSphere DataPower Integration Appliance XI50 for zEnterprise (DataPower XI50z) or select IBM BladeCenter PS701 Express blades or IBM BladeCenter HX5 blades requires a zEnterprise BladeCenter Extension (zBX) Model 003
Target system software requirements:
  1. See the list of PTFs in the Software Service Level section of the PSP buckets and use the SMP/E Fix Categories:
    • For zEC12 base support: IBM.Device.Server.zEC12-2827
    • For zBC12 base support: IBM.Device.Server.zBC12-2828
    • For zEC12 exploitation: IBM.Device.Server.zEC12-2827.Exploitation
    • For zBC12 exploitation: IBM.Device.Server.zBC12-2828.Exploitation
    • For zEC12 and zBC12 zEDC exploitation or toleration: IBM.Function.zEDC
  2. See "Support is delivered by service, z/OS features, and web deliverables" described in General recommendations and considerations for a zEC12 or zBC12 server and "Install the necessary z/OS service", as indicated in PSP buckets described in Actions you can take before you order a zEC12 or zBC12 server.
Other system (coexistence or fallback) requirements:
  • It is recommended that you install and run the zEnterprise required service on your existing server. This will enable you to fall back from a hardware perspective, yet maintain your software level.
  • If you have not installed the preconditioning and exploitation PTFs for CFCC Level 17, note that these PTFs are required to be installed throughout your sysplex before implementing CFCC Level 18 or 19.
  • If you plan to implement zEDC, you should install the z/OS toleration PTFs on systems that access data that is compressed using zEDC Express on a zEC12 or zBC12 server.
Restrictions: See Restrictions for a zEC12 or zBC12 server.
System impacts: None.
Related IBM Health Checker for z/OS check: IBM Health Checker for z/OS check, SUP_HiperDispatchCPUConfig, was added to z/OS V1R12 with APAR OA30476. This check verifies that HiperDispatch is enabled on a z196 or later system.

Steps to take

Follow the General recommendations and considerations for a zEC12 or zBC12 server, adhere to the Restrictions for a zEC12 or zBC12 server, and perform the tasks that are described in the following topics.

Reference information

None.

Parent topic: Hardware migration actions