Actions you can take before you order an IBM z14 server

These are migration actions that you perform on your current system, either because they require the current system or because they are possible on the current system. You do not need the z14™ server to make these changes, and the changes do not require the z14 server once they are made. For example, discontinuing use of hardware that is no longer supported.

You can perform the following migration actions before you order or install a z14 server:
  1. Review the Large Systems Performance Reference (LSPR). LSPR is designed to provide comprehensive z/Architecture® processor capacity ratios for different configurations of central processors (CPs) across a wide variety of system control programs and workload environments.
  2. Review the sysplex configuration in which the z14 server will participate. See Restrictions for a z14 server for a description of the limitations when using z14 server with certain earlier servers in a Parallel Sysplex®.
  3. Implement an STP timing network. This action is needed because Sysplex Timers (9037-002) are not supported on z14 servers.
  4. Migrate from ISC-3 links to the Integrated Coupling Adapter (ICA) links. This action is needed because ISC-3 links are not supported on z14 servers. If desired, you can take this action after you order a z14 server, as you upgrade to the new server.
  5. Migrate from InfiniBand coupling links, if you are ordering a z14 Model ZR1. For connectivity to other systems, the z14 ZR1 requires Integrated Coupling Adapter Short Reach (ICA SR) and the Coupling Express Long Reach (CE LR) coupling links. The z14 ZR1 does not support InfiniBand coupling links.
  6. Migrate from unsupported hardware features to newer technology. This action is needed because specific features are not available on the z14 server. For example, Crypto Express4S and OSA-Express4 are not supported. See Restrictions for a z14 server, Replace unsupported devices and Provide for new device installations.
  7. Determine the level of cryptographic support you require on a z14 server. The level of function that is provided for cryptographic support differs by z/OS® release and the installed ICSF web deliverable. Also, toleration PTFs are available for some cryptographic web deliverables.
    For z/OS V2R3, consider the following:
    • If you are using the level of ICSF that is shipped as part of z/OS V2R3 (FMID HCR77C0), you can use most functions of the Crypto Express6S feature on a z14 server.
    • ICSF Web Deliverable HCR77C1 - Cryptographic Support for z/OS V2R1 - z/OS V2R3 provides some additional function and also incorporates enhancements that are available in PTFs for the base level of ICSF included in z/OS V2R3. The web deliverable includes support for a PCI HSM (“Payment Card Industry Hardware Security Module”) configured CCA coprocessor. Crypto Express6S also introduces the use of X.509 certificates in CCA.
    • If you are using this web deliverable and sharing keys with other z/OS systems that have a lower level of ICSF, you require the coexistence PTFs identified by the following Fix Category: IBM.Coexistence.ICSF.z/OS_V2R1-V2R3-HCR77C1
    For z/OS V2R2, consider the following:
    • If you are using the level of ICSF that is shipped as part of z/OS V2R2 (FMID HCR77B0), you can use most functions of the Crypto Express6S feature on a z14 server.
    • ICSF Web Deliverable HCR77C1 - Cryptographic Support for z/OS V2R1 – z/OS V2R3 provides some additional function and also incorporates enhancements that are available in PTFs for the base level of ICSF included in z/OS V2R2. The web deliverable includes support for a PCI HSM (“Payment Card Industry Hardware Security Module”) configured CCA coprocessor. Crypto Express6S also introduces the use of X.509 certificates in CCA.
    For z/OS V2R1, consider the following:
    • If you are using the level of ICSF that is shipped as part of z/OS V2R1 (FMID HCR77A0), Crypto Express5S is tolerated on a z14 server, which treats Crypto Express5S cryptographic coprocessors and accelerators as Crypto Express4S coprocessors and accelerators. However, you must install the required PTFs identified by the SMP/E fix category:
      • For IBM z14 models M01 through M05, use FIXCAT value IBM.Device.Server.z14-3906.RequiredService
      • For IBM z14 Model ZR1, use FIXCAT value IBM.Device.Server.z14ZR1-3907.RequiredService
    • If you require support for more than 16 domains on Crypto Express5S, you must install the PTFs that are identified by the appropriate fix category for your z14 server (either IBM.Device.Server.z14-3906.Exploitation or IBM.Device.Server.z14ZR1-3907.Exploitation), or install the ICSF Web Deliverable HCR77C1 - Cryptographic Support for z/OS V2R1 – z/OS V2R3, or a later ICSF web deliverable.
    • If you require Crypto Express4S functionality for CCA 4.4 and other EP11 cryptographic enhancement support that includes: RKX Key Export Wrap, UDX simplification, more EP11 algorithms, expanded EMV support, AP Configuration simplification, CTRACE Enhancements, and KDS Key Utilization stats, you must download and install the Cryptographic Support for z/OS V1R13-z/OS V2R1 web deliverable (FMID HCR77A1) or the Enhanced Cryptographic Support for z/OS V1R13-z/OS V2R1 web deliverable (FMID HCR77B0) or a later ICSF web deliverable.
      Note: If you are using the Cryptographic Support for z/OS V1R13-z/OS V2R1 web deliverable (FMID HCR77A1) or a later ICSF web deliverable, and sharing keys with other z/OS systems that have a lower level of ICSF, you require the coexistence PTFs listed here, which are identified by fix category: IBM.Coexistence.ICSF.z/OS_V1R13-z/OS_V2R1-HCR77A1, or the FIXCAT for the ICSF level that you are using.
    • If you require Crypto Express6S exploitation support for the next Generation Coprocessor support or VISA Format Preserving Encryption (FPE), you must download and install the Enhanced Cryptographic Support for z/OS V1R13-z/OS V2R1 web deliverable (FMID HCR77B0) or a later ICSF web deliverable.
      Note: If you are using ICSF Web Deliverable HCR77C1 - Cryptographic Support for z/OS V2R1 – z/OS V2R3, or a later ICSF web deliverable, and sharing keys with other z/OS systems that have a lower level of ICSF, you require the coexistence PTFs listed here, which are identified by fix category: IBM.Coexistence.ICSF.z/OS_V1R13-z/OS_V2R1-HCR77B0, or a later ICSF web deliverable.
  8. Install the necessary z/OS service. IBM recommends that you use the SMP/E REPORT MISSINGFIX command to identify PTFs for the z14 server that you do not already have installed. The simplest way to do that is to specify IBM.Device.Server.* and IBM.Function.* as the fix categories for the REPORT MISSINGFIX command. Doing so will identify not only z14 support PTFs, but those for prior generations of IBM servers that you might need, and those required to enable various functions. Also, REPORT MISSINGFIX creates a batch job for the SMP/E RECEIVE ORDER command that you can use to get any PTFs you do not already have. SMP/E also provides an Explorer function that you can use to find new fix categories that might be of interest. For a description of all the fix categories, see the Values and Descriptions page at IBM Fix Category Values and Descriptions. For more information about the REPORT MISSINGFIX command, see SMP/E for z/OS Commands.
    Here is an example of the SMP/E control statements you can use for REPORT MISSINGFIX: 
    SET BDY(GLOBAL) .

REPORT 
  MISSINGFIX 
  ZONES(target zone)
  FIXCAT(IBM.Device.Server.*
             IBM.Function.*) .
    If you want to use specific fix categories, you can specify the following fix categories either individually or together for the z/OS PTFs that are required to use a z14 server, exploit its functions and features, and those that IBM recommends you install if you are using a z14 server. Also needed are the FIXCATs for intermediate processors.
    • For IBM z14 models M01 through M05:
      • IBM.Device.Server.z14-3906.RequiredService
      • IBM.Device.Server.z14-3906.Exploitation
      • IBM.Device.Server.z14-3906.RecommendedService
    • For IBM z14 Model ZR1:
      • IBM.Device.Server.z14ZR1-3907.RequiredService
      • IBM.Device.Server.z14ZR1-3907.Exploitation
      • IBM.Device.Server.z14ZR1-3907.RecommendedService
    In addition, if you choose to use specific fix categories, your environment might require that you specify one or more of these fix categories:
    • IBM.Function.DataSetEncryption
    • IBM.Function.ParallelSysplexInfiniBandCoupling
    • IBM.Function.PricingInfrastructure
    • IBM.Function.ServerTimeProtocol
    • IBM.Function.UnifiedResourceManager
    • IBM.Function.zEDC
    • IBM.Function.zHighPerformanceFICON
    • IBM.Function.zHyperLink

    If you are exploiting z14 capabilities by installing a web deliverable, additional PTFs might be required. Follow the instructions in the Program Directory that is associated with each web deliverable to identify the required PTFs.

    Another way to find required PTFs is by using Preventive Service Planning (PSP) "buckets." In addition to the applicable hardware PSP buckets, you must also obtain the software PSP buckets. The hardware PSP bucket lists the recommended, required, and exploitation PTFs, and also includes information about the appropriate fix categories that are needed to identify those PTFs. However, using PSP buckets and checking on the status of the PTFs listed in them is more time-consuming and potentially error-prone than using REPORT MISSINGFIX with the appropriate fix categories.1
  9. Run the CFSIZER tool. If you are moving your coupling facilities and the coupling facility structures are on a higher CFLEVEL than they were previously, run the Coupling Facility Structure Sizer (CFSIZER) tool to find out if you have to increase coupling facility structure sizes. Prepare to make the necessary changes to the CFLEVEL as indicated by the tool.

    You can download the CFSIZER tool at Coupling Facility sizer. Also, see Update your CFRM policy with coupling facility structure size changes.

    Note: After you make a coupling facility available on the new hardware, you can run the Sizer utility, an authorized z/OS program to evaluate structure size changes. The Sizer utility is distinct from CFSizer, and should be run after the new hardware (CFLEVEL) is installed, but before any CF LPAR on the new hardware is populated with structures. You can download the Sizer utility at CFSizer Alternate Sizing Techniques.
  10. Prepare for the new machine instruction mnemonics. The instruction set has been expanded on the z14 server, as is usual for new servers. Each machine instruction is represented by a mnemonic in Assembler language. The new mnemonics can be identical to the names you chose for Assembler macro instructions. In the event of such naming collisions, the Assembler's default opcode table (UNI) processes new mnemonics as instructions, not as macros, after z14 required service has been installed. If this occurs, it is likely to cause Assembler error messages and can cause incorrect object code to be generated. If you write programs in Assembler Language, compare the names of Assembler macro instructions that are used to the new machine instructions (documented in the latest z/Architecture Principles of Operation, SA22-7832) to identify any such conflicts or collisions that would occur. Identical names cause Assembler errors or the generation of incorrect object code when you assemble your programs. For information about a tool to help in identifying mnemonic conflicts, see IBM Techdocs. Search for the Techdoc PRS5289.
    If a conflict is identified, take one of these actions:
    • Change the name of your macro instruction.
    • Specify PARM='...OPTABLE(YOP)...' (or some other earlier opcode table).
    • Specify a separate ASMAOPT file containing assembler options such as in the previous method (this method requires no changes to source code or JCL).
    • Add as the first statement of your source program: *PROCESS OPTABLE(YOP) (or some other earlier opcode table).
    • Specify the PROFILE option either in JCL or the ASMAOPT file, and the specified or default member of the SYSLIB data set is copied into the front of the source program.
    • If you must use both a new instruction and a macro with the same name in an assembly, you can use a coding technique that permits both use of a new instruction and a macro with the same name in an assembly such as HLASM mnemonic tags (:MAC :ASM).
  11. Accommodate the changes to default ARCH and TUNE level. Starting with z/OS V2R3, the default ARCH level is changed from ARCH(8) to ARCH(10), and the default TUNE level is changed from TUNE(8) to TUNE(10). The new default levels align with the zEC12; thus, code can run on any server that is supported by z/OS V2R3 without requiring changes to compiler options. However, if you compile programs to be run on processors at lower architecture levels, you must specify the appropriate ARCH and TUNE levels when you compile those programs.

    The z14 supports the new levels ARCH(12) and TUNE(12), which are needed to take advantage of the new z14 instructions, and are intended to provide performance improvements for applications. ARCH(12) produces code that uses instructions that are available on the z14 in z/Architecture mode. The z14 adds instructions for vector programming, including allowing packed decimal operations to be performed in registers rather than memory. TUNE(12) generates code that is executable on all models, but is optimized for the z14.

  12. Update I/O Configuration Program (IOCP) for earlier FICON cards. To continue using FICON Express8S cards, you must specify the new IOCP keyword MIXTYPE.
  13. Use the LOADxx MACHMIG statement to help with migration. In the LOADxx member, you can include the new MACHMIG statement to specify particular z14 hardware facilities that you want to disable during your migration to another processor, z/OS release, or both. You can exclude the following z14 facilities:
    • Hardware-based enhanced-DAT facility (EDAT2)
    • Hardware-based transactional-execution facility (TX)
    • Hardware-based vector registers (VR) in support of SIMD (VEF)
    • Guarded Storage Facility (GSF).

    If you omit the MACHMIG statement, z/OS does not limit its use of the machine facilities.

  14. Decide on the steps to take for your migration to a z14 server. Besides the steps that are listed here, see the following topic for guidance Actions you can take after installing an IBM z14 server.
1
Though it is more time-consuming and error-prone than using REPORT MISSINGFIX with the appropriate fix categories, you can use the Preventive Service Planning (PSP) bucket to obtain the list of required PTFs for the z14 server. PSP buckets are identified by an Upgrade name, and have Subset names, as follows:
  • For IBM z14 models M01 through M05, the z14 PSP Upgrade name is 3906DEVICE, and the z/OS support can be found in Subset 3906/ZOS.
  • For IBM z14 Model ZR1, the z14 PSP Upgrade name is 3907DEVICE, and the z/OS support can be found in Subset 3907/ZOS.