Step 1 : Upgrade to an IBM z15 server

Description:

Description

With the new IBM® z15™ (z15™) server as the infrastructure, your business has the power to optimize digital services delivery, accelerate business innovation, and ultimately improve the bottom line. The z15 can help you adapt to planned or unplanned events while keeping services and operations running smoothly and continuously, on premises or in the cloud.

The z15 ™ uses a 19-inch form factor and industry-standardized power and networking hardware. The system is configurable as a one-to-four 19-inch frame system, which easily aligns with the modern cloud data center.

The IBM z15 Model T02 (z15 T02) is the newest addition to the IBM z15 family. The z15 T02 is designed for clients who do not need the capacity of the larger T01 models.

The IBM z15 family of mainframes includes the following hardware models:

• Model T01 (machine type 8561), with five feature codes to represent the processor capacity. The feature codes are Max34, Max71, Max108, Max145, and Max190 with (respectively) 34, 71, 108, 145, and 190. This system is configurable as a one-to-four 19-inch frame system.
• Model T02 (machine type 8562), with five CPC size features (one or two drawers). The system is configurable as a 19-inch frame system.

In this workflow, references to "z15" pertain to all models of the IBM z15, including the z15 T02, unless otherwise noted.

z/OS base support for specific z15 functions depends on the z/OS release. Not all z15™ functions are available in every z/OS release, as shown in the tables:

• Table 1 lists the z15 functions and indicates whether each function is included in a specific z/OS release (Yes or No), or whether the function requires a PTF (PTF) or a web deliverable (Web). For information about z/OS V2R1 support, see the Table Notes. Information about finding the appropriate PTFs is provided in the workflow step "Actions you can take before you order an IBM z15 server" and its substeps.
• Table 2 shows a summary view of which z15 functions are available for exploitation in each z/OS release. Some functions have upgrade or exploitation considerations. Information about the applicable upgrade actions is provided in the steps and substeps for "Actions you can take before you order an IBM z15 server" and "Actions you can take after installing an IBM z15 server."

Many functions are enabled or disabled, based on the presence or absence of the required hardware and software. If you plan to use new z15 functions, you can install the software and hardware in either order. That is, there is no requirement to install either software or hardware first to use a specific function. However, because of outage windows and testing considerations, you might want to consider installing all of the software and PTFs required for the machine and the functions you plan to use first. Then, upgrade the hardware and, finally, update your customization to use the new functions.

The exploitation of specific z15 server functions depends on the z/OS release. The following table lists the z15 functions and indicates whether each function is exploited by a specific z/OS release (Yes or No), or whether the function requires a PTF (PTF) or a web deliverable (Web). For information about finding the appropriate PTFs, see the workflow step "Actions you can take before you order an IBM z15 server." For more information about z/OS V2R1 support, see the Table Notes.

Web deliverables are available from the z/OS downloads page at z/OS downloads.

The following table provides more details about this upgrade action. Use this information to plan your changes to the system.

Steps to take

Continue your upgrade to the z15 by performing the following steps in this workflow. Each step contains a number of sub-steps.

• "General recommendations and considerations for a z15 server"
• "Restrictions for a z15 server"
• "Actions you can take before you order an IBM z15 server"
• "Actions you can take after installing an IBM z15 server"
• "Accommodate functions for the z15 to be discontinued on future servers"

Reference information

For more information about new functions to exploit, see the IBM z15 Library, which is available online in Resource Link™.

Instructions:

In this portion of the workflow, you submit a job to run the following IBM Health Checker for z/OS health check, which is associated with this upgrade action: IBMRSM,RSM_MINIMUM_REAL.

This check will be activated if it is not already active. If the check is activated, it will be deactivated at the end of the job, so that it remains in the same state as it was found.

If the health check runs without finding exceptions, this workflow step is marked "complete," to indicate that this upgrade action is complete.

If the health check finds an exception, this step is marked "failed." If so, further investigation (and possibly more work) is necessary to complete this upgrade action. If the step is marked "Failed," review the health check output (using your preferred method such as SDSF), and correct any situation as required. Then run this workflow step again to resubmit the health check job. Repeat this process until the health check no longer receives an exception and the step is marked "complete.".

This check is available on the following releases: z/OS V2R1 and z/OS V2R2.

Note: The successful running of this IBM Health Checker for z/OS health check only partially covers this upgrade action. Refer to the upgrade action text for the complete list of steps to take.

Step 2 : General recommendations and considerations for a z15 server

Description:

As you plan your migration to an IBM z15™ server, observe the recommendations and considerations in the steps that follow.

Step 2.1 : Migration actions for IBM servers are cumulative

Description:

Description

If you upgrade to a z15™ server from a z14™ or z14 ZR1 server, and have performed the upgrade actions that are associated with the z14 or z14 ZR1, you have fewer upgrade actions than if you upgrade from an earlier generation server. Thus, if you upgrade from an earlier generation server, you might need to perform more upgrade actions. For example, if you are upgrading from a z13 and z13s server, you should perform the "z14 Upgrade Workflow" or the "Upgrade to an IBM z14 server" steps in the "z/OS V2R4 Upgrade Workflow".

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 2.2 : Support is delivered by service, z/OS features, and web deliverables

Description:

Description

The base support for the z15™ is delivered through service (PTFs). To determine which PTFs are required, obtain the current enhanced HOLDDATA file, either by using the SMP/E RECEIVE ORDER command or by downloading the 2-year file and using the SMP/E RECEIVE command to process it.

Then, use the SMP/E REPORT MISSINGFIX command to identify the missing PTFs on your system for the IBM z15. For example:

				SET BDY(GLOBAL).				REPORT MISSINGFIX ZONES( target_zone)				FIXCAT(IBM.Device.Server.z15*.**).				

The following SMP/E FIXCATs identify the PTF support for the IBM z15:

• For the IBM z15 Model T01 server:
  • FIXCAT for required service is: IBM.Device.Server.z15-8561.RequiredService
  • FIXCAT for recommended service is: IBM.Device.Server.z15-8561.RecommendedService
  • FIXCAT for exploitation is: IBM.Device.Server.z15-8561.Exploitation
• For the IBM z15 Model T02 server:
  • FIXCAT for required service is: IBM.Device.Server.z15T02-8562.RequiredService
  • FIXCAT for recommended service is: IBM.Device.Server.z15T02-8562.RecommendedService
  • FIXCAT for exploitation service is: IBM.Device.Server.z15T02-8562.Exploitation

The RequiredService FIXCATs identify the minimum PTFs that are required to use z/OS on the z15 --- you must install these PTFs. The RecommendedService FIXCATs group the PTFs that the IBM Service organization recommends that you install. The Exploitation FIXCATs include the new functions that are provided on the z15, which you can choose to exploit.

The Preventive Service Planning (PSP) buckets for the z15 servers are identified by an upgrade name and one or more subset names, as follows:

• For the IBM z15 Model T01 server, the PSP Upgrade name is 8561DEVICE, and the z/OS support can be found in Subset 8561/ZOS.
• For the IBM z15 Model T02 server, the PSP Upgrade name is 8562DEVICE, and the z/OS support can be found in Subset 8562/ZOS.

Exploitation of some functions requires a web deliverable. Specifically:

• Exploitation of Crypto Express7S requires the Cryptographic Support for z/OS V2R2 - z/OS V2R4 (FMID HCR77D1) web deliverable.

  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_V2R2-V2R4-HCR77D1

• If you are running z/OS V2R1 and 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 V2R1-z/OS V2R3 web deliverable (FMID HCR77C0) or the Cryptographic Support for z/OS V2R1 - z/OS V2R3 web deliverable (HCR77C1).

  If you are using either of these web deliverables (HCR77C0 or HCR77C1) and sharing keys with other z/OS systems that have a lower level of ICSF, you require the coexistence PTFs identified by the appropriate fix category: IBM.Coexistence.ICSF.z/OS_V2R1-z/OS_V2R3-HCR77C0 or IBM.Coexistence.ICSF.z/OS_V2R1-z/OS_V2R3-HCR77C1.

• If you are running z/OS V2R1 and require Crypto Express5S 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 the Cryptographic Support for z/OS V1R13 - z/OS V2R2 web deliverable (HCR77B1).

  If you are using either of these web deliverables (HCR77B0 or HCR77B1) and sharing keys with other z/OS systems that have a lower level of ICSF, you require the coexistence PTFs identified by the appropriate fix category: IBM.Coexistence.ICSF.z/OS_V1R13-z/OS_V2R1-HCR77B0 or IBM.Coexistence.ICSF.z/OS_V1R13-z/OS_V2R1-HCR77B1.

• To run z/OS V2R1 on a z15™ server, you require IBM Software Support Services for extended z/OS V2R1 support.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 2.3 : Larger coupling facility structure sizes might be necessary

Description:

Description

When you change the coupling facility control code level (CFLEVEL), your coupling facility structure sizes might change.

If, as part of your upgrade to a z15™ server, you change the CFLEVEL, you might have larger structure sizes than you did previously. If your CFLEVEL is identical, structure sizes are not expected to change when you upgrade from a previous server to a newer generation server.

In addition, similar to CFLEVEL 17 and later, ensure that the CF LPAR has at least 512MB of storage. CFLEVEL 24, introduced on the z15, supports the Coupling Facility use of Large Memory to improve availability for larger CF cache structures and data sharing performance with larger DB2 Group Buffer Pools (GBP). This support removes inhibitors to using large CF cache structures, enabling use of Large Memory to scale to larger DB2 Local Buffer Pools (LBP) and Group Buffer Pools (GBP) in data sharing environments.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 2.4 : Use the same software level throughout a sysplex

Description:

Description

Having members of a sysplex at the same software level (other than during brief upgrade periods) is good software management policy.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 2.5 : Migrate hardware and software at different times

Description:

Description

To minimize the amount of change that you experience at one time, do not upgrade your software release level at the same time that you upgrade your hardware.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 2.6 : Use the latest version of SCRT

Description:

Description

As of z/OS V2R3, you do not need to update SCRT because it is included in the z/OS base. If you are running an earlier release of z/OS, and you use SCRT, make sure that SCRT is at the latest level. This is a requirement for sub-capacity pricing.

The latest level of SCRT for releases prior to z/OS V2R3 can be downloaded from the SCRT web site at IBM Z software pricing - Licensing - Sub-capacity licensing.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 3 : Restrictions for a z15 server

Description:

For a description of each restriction, perform the steps that follow.

Step 3.1 : z15 servers in a sysplex

Description:

Description

Be aware of the following considerations:

• A Parallel Sysplex® that contains a z15™ server, either for a z/OS image or a coupling facility (CF) image, can contain only z13 or later servers.
• The z15 requires ICA-SR and CE-LR fanouts. The older HCA3-O or the HCA3-O LR coupling fanouts are not supported on the z15 server.
• Servers such as the z14, z14 ZR1, z13, or z13s, can connect to the z15 by using the Integrated Coupling Adapter Short Reach (ICA SR) and the Coupling Express Long Reach (CE LR) coupling links. Earlier systems, such as the zEC12 and zBC12, do not support ICA SR or CE LR, and therefore cannot have coupling link connectivity to the z15 server.
• If you are running z/OS on any servers earlier than a z13 or z13s, you cannot add a z15 to that sysplex; that is, you will not be able to perform rolling IPLs to introduce a z15 server if you have any of the earlier servers as z/OS images or coupling facility images in the sysplex.
• The earlier servers in the sysplex must be upgraded to z13 or z13s or later to have z15™ servers supported in the sysplex. If you have any z/OS images or coupling facility images on an earlier server, and you intend to introduce a z15 server into that sysplex, you must move those images to a z13 or z13s or later server before introducing the z15 server.
• GRS supports the use of FICON CTCs for Ring configurations. However, if you are currently using ESCON CTCs for GRS ring configurations within a sysplex, consider converting to GRS Star if possible, or using XCF signaling in a GRS ring configuration. XCF sysplex signaling is preferred instead of GRS CTC connections.
• IBM Z® servers that require time synchronization (for example, to support a base or Parallel Sysplex) must be configured in Server Time Protocol (STP) mode. STP is designed to allow multiple servers and coupling facilities to maintain time synchronization with each other, in a coordinated timing network (CTN). STP is a hardware feature of the z15, z14, z14 ZR1, z13, z13s, zEC12, and zBC12. The most recent servers (z15, z14, z14 ZR1, z13, and z13s) can participate only in an STP-only CTN.
• Starting with IBM z15, the IBM Z Hardware Management Appliance (FC #0100) can be ordered to provide HMC/SE functions within the CPC frame, eliminating the need for separate HMCs outside of the frame.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 3.2 : HCD and HCM support for the z15

Description:

Description

As with previous servers, hardware can be defined on any supported operating system and server. However, dynamic activation of new server and new adapter types can be done only on z15™ and future high-end IBM Z® servers. Dynamic activation is supported on z/OS V2R1 and later releases.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 4 : Actions you can take before you order an IBM z15 server

Description:

These are the upgrade 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 z15™ server to make these changes, and the changes do not require the z15™ server once they are made. For example, discontinuing use of hardware that is no longer supported.

Step 4.1 : Review the Large Systems Performance Reference (LSPR)

Description:

Description

The Large Systems Performance Reference (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.

The LSPR is available in IBM Resource Link™ at the following site: Large Systems Performance Reference for IBM Z.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 4.2 : Implement an STP timing network

Description:

Description

This action is needed because Sysplex Timers (9037-002) are not supported on z15™ servers.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 4.3 : Upgrade from unsupported hardware features to newer technology

Description:

Description

This action is needed because specific features are not available on the z15™ server.

The following hardware features are not supported on the z15™ server. They cannot be ordered on the z15 and cannot be carried forward from an upgrade on an earlier server to the z15.

• Host Channel Adapter (HCA) for InfiniBand is no longer supported, including the following features:
  • HCA2-O and HCA2-O LR features
  • HCA3-O and HCA3-O LR features

  Enterprises must upgrade from HCA channels to one of the following coupling links:

  • For high-speed short-range coupling connectivity, the IBM Integrated Coupling Adapter (ICA SR) is a two-port, short-distance coupling fanout that uses a new coupling channel type: CS5. The ICA SR can only be used for coupling connectivity between z15, z14, z14 ZR1, z13, and z13s servers. The ICA SR fanout requires new cabling, and can connect only to another ICA SR.
  • For long-range coupling connectivity, the Coupling Express® Long Reach (CE LR) is a two-port, long-distance coupling adapter that uses a new coupling channel type: CL5. The CE LR can be used only for coupling connectivity between z15, z14, z14 ZR1, z13, and z13s servers.

  The suggested practice is to order ICA SR (#0172) or CE LR (#0433) on the z15™ servers that are used in a Parallel Sysplex to help ensure coupling compatibility with future server generations.

• CHPID type OSN (OSA-Express for NCP) is not supported on the OSA-Express5S GbE LX feature
• OSA-Express4S features
• Crypto Express3 and Crypto Express4S
• InterSystem Channel-3 (ISC-3) coupling links feature
• FICON Express4
• zEDC Express (FC #0420). In the z15, the compression functions are moved into the processor chip, which is referred to as IBM Integrated Accelerator for z Enterprise Data Compression (zEDC). As an integrated part of the z15™ processor chip, the Integrated Accelerator for zEDC does not require the purchase of a hardware feature or usage of I/O slots.
• IBM Flash Express (features #0402 and #0403), which is replaced by IBM Virtual Flash Memory (VFM), starting with the z14. VFM implements Extended Asynchronous Data Mover (EADM) Architecture that uses HSA-like memory instead of Flash card pairs. No application changes are required to change from IBM Flash Express to VFM.
• As of HMC version 2.15.0, new builds of the Hardware Master Console (HMC) and the Support Element (SE) no longer include a CD/DVD drive as part the HMC server hardware. Instead, the HMC provides two options for installing functional updates: USB media and electronic delivery. These solutions are available for:
  • Firmware for the HMC or Support Element
  • eBusiness on Demand (eBoD) records, such as On/Off Capacity on Demand (On/Off CoD)
  • Operating system code, as used for Load from Removable Media or the Server task.

  If you select to use USB media, the appropriate USB Flash Memory Drive Media is provided with the particular feature, using either of the following feature codes:

  • Feature code 0843: USB Load media that can be used for IBM Z operating system code
  • Feature code 0848: USB Backup media that can be used for an HMC or SE Critical Data Backup task.

  If USB media is not acceptable for your environment, choose electronic delivery instead. Order feature code 0846 (No Physical Media Option) and follow the instructions on how to electronically deliver the required content over the network by using any of the following options:

  • Z Remote Support Facility (zRSF)
  • IBM Resource Link
  • FTP/SFTP/FTPS Server connections from the HMC.

  For an electronic only delivery environment, two HMCs are required on every unique network subnet on which an HMC, SE, or TKE workstation is connected.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 4.4 : Carry forward hardware features

Description:

Description

The following hardware features are not orderable on z15™ servers. If they are installed on your existing server at the time of an upgrade to a z15 server, they can be retained or carried forward.

• TKE with/4768 #0080 or #0081
• TKE workstation #0085 and #0086
• HMC #0082, #0083, #0095, #0096
• HMC Rack KMM #0154
• TKE Rack Keyboard/Monitor/Mouse #0156
• Internal Coupling Adapter Short Reach (ICA SR) #0172
• Fanout Airflow PCIe #0174
• FICON Express8S 10KM LX #0409
• FICON Express8S SX #0410
• 10 GbE RoCE Express #0411
• 10 GbE RoCE Express #0412
• OSA-Express5S GbE LX #0413
• OSA-Express5S GbE SX #0414
• OSA-Express5S 10 GbE LR #0415
• OSA-Express5S 10 GbE SR #0416
• OSA-Express5S 1000BASE-T #0417
• FICON Express16S LX #0418
• FICON Express16S SX #0419
• OSA-Express6S GbE LX #0422
• OSA-Express6S GbE SX #0423
• OSA-Express6S 10 GbE LR #0424
• OSA-Express6S 10 GbE SR #0425
• OSA-Express6S 1000BASE-T #0426
• FICON Express16S+ LX #0427
• FICON Express16S+ SX #0428
• OSA-Express7S 25 GbE SR #0429
• 25 GbE RoCE Express2 #0430
• zHyperLink Express #0431
• Coupling Express LR #0433
• Addl smart cards #0884
• TKE Smart Card Reader #0885
• Crypto Express5S #0890
• TKE Smart Card Reader #0891
• NXP Smart Card w/FIPS #0892
• Crypto Express6S #0893
• 512 GB MEM DIMM(5/FEAT) #1631.

For information about supported storage controllers, see the step "Ensure that you are using supported servers, storage controllers, and machine facilities" in the z/OS V2R4 Upgrade Workflow.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 4.5 : Determine the level of cryptographic support you require on a z15 server

Description:

Description

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 V2R4, consider the following:

• If you are using the level of ICSF that is shipped as part of z/OS V2R4 (FMID HCR77D0), you can use most functions of the Crypto Express7S feature on a z15™ server.
• ICSF Web Deliverable HCR77D1 - Cryptographic Support for z/OS V2R2 – z/OS V2R4 (FMID HCR77D1) provides some additional function and also incorporates enhancements that are available in PTFs for the base level of ICSF included in z/OS V2R4. This web deliverable includes support for:
  • Crypto Express7S adapter
  • Ability to use CP Assist for Cryptographic Functions (CPACF) for certain clear key ECC operations
  • CCA Release 5.5 and CCA Release 6.3
  • Coupling Facility Level (CFLEVEL) 24
  • Integrated Accelerator for z Enterprise Data Compression
  • System Recovery Boost
  • IBM Data Privacy Passports
  • IBM Data Privacy for Diagnostics.

  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 that are identified by SMP/E fix category IBM.Coexistence.ICSF.z/OS_V2R2-V2R4-HCR77D1.

• If you require support for more than 16 domains on Crypto Express7S, you must install the PTFs that are identified by the SMP/E fix category for the z15™ server: IBM.Device.Server.z15-8561.Exploitation.

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 z15™ server.
• ICSF Web Deliverable HCR77D1 - Cryptographic Support for z/OS V2R2 – z/OS V2R4 (FMID HCR77D1) provides additional function and enhancements. 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 that are identified by SMP/E fix category IBM.Coexistence.ICSF.z/OS_V2R2-V2R4-HCR77D1.
• 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 that are identified by SMP/E 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 z15™ server.
• ICSF Web Deliverable HCR77D1 - Cryptographic Support for z/OS V2R2 – z/OS V2R4 (FMID HCR77D1) provides additional function and enhancements. 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 that are identified by SMP/E fix category IBM.Coexistence.ICSF.z/OS_V2R2-V2R4-HCR77D1.
• 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.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 4.6 : Install the necessary z/OS service

Description:

Description

IBM recommends that you use the SMP/E REPORT MISSINGFIX command to identify PTFs for the z15™ server that you do not already have installed. To do so, specify IBM.Device.Server.* and IBM.Function.* as the fix categories for the REPORT MISSINGFIX command. This command identifies not only the z15™ support PTFs, but also the PTFs 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 descriptions of 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 z/OS SMP/E 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 z15™ server, exploit its functions and features, and those that IBM recommends that you install if you are using a z15™ server. Also needed are the fix categories for intermediate servers.

• For the IBM z15 Model T01:
  • IBM.Device.Server.z15-8561.RequiredService
  • IBM.Device.Server.z15-8561.Exploitation
  • IBM.Device.Server.z15-8561.RecommendedService
• For the IBM z15 Model T02:
  • IBM.Device.Server.z15T02-8562.RequiredService
  • IBM.Device.Server.z15T02-8562.Exploitation
  • IBM.Device.Server.z15T02-8562.RecommendedService

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

If you choose not to use the Recommended Service fix category for your z15 server, you can, alternatively, find lists of the recommended PTFs in the Preventive Service Planning (PSP) “buckets” for the applicable hardware and software. However, note that using PSP buckets and checking the status of the PTFs listed in them is more time-consuming and potentially error-prone than using REPORT MISSINGFIX with the appropriate fix category:

• For the IBM z15 Model T01, the PSP Upgrade name is 8561DEVICE, and the z/OS support can be found in Subset 8561/ZOS.
• For the IBM z15 Model T02, the PSP Upgrade name is 8562DEVICE, and the z/OS support can be found in Subset 8562/ZOS.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 4.7 : Run the CFSIZER tool

Description:

Description

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 whether you must 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 the following step in the z/OS V2R4 Upgrade Workflow:

• "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, which is an authorized z/OS program that you can use 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.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 4.8 : Prepare for the new machine instruction mnemonics

Description:

Description

The instruction set has been expanded on the z15™ server, as is usual for new servers. Each machine instruction is represented by a mnemonic in Assembler language. It is possible that the new mnemonics can match names that you chose for Assembler macro instructions. If such naming collisions occur, the Assembler default opcode table (UNI) processes new mnemonics as instructions, not as macros, after z15™ required service is 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 your existing Assembler macro instructions to the new machine instructions, to identify any such conflicts or collisions that would occur. The Assembler macro instructions are documented in z/Architecture Principles of Operation. For information about a tool to help in identifying mnemonic conflicts, see the IBM Techdocs web site under Presentations and Tools. 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, use a coding technique that allows the use of a new instruction and a macro with the same name in an assembly, such as HLASM mnemonic tags ( :MAC:ASM).

To help you associate the OPTABLE levels with IBM Z processor generations:

• HLASM APAR PH03536 defines OPTABLE names Z9 through Z14 as synonyms for ZS3 through ZS8.
• HLASM APAR PH00902 adds OPTABLE name Z15 and synonym ZS9.

Similarly, HLASM APAR PH00902 extends the MACHINE option to support various other names, based on short forms of the IBM machine name, such as zEC12 and z990. This APAR adds support for values in the form ARCH-n, to select the table that most closely corresponds to the ARCH(n) option in IBM compilers for C, COBOL, and PL/I. For example, both MACHINE(z15) and MACHINE(ARCH-13) are supported with the installation of HLASM APAR PH00902.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 4.9 : Learn about the HiperDispatch enhancement

Description:

Description

In HiperDispatch processing, changes in LPAR weight can cause I/O enabled vertical-high (Vh) and vertical-medium (Vm) processors to be converted to vertical-low (Vl) processors, and immediately parked by HiperDispatch. That is, the Vh and Vm processors can be pushed to the lowest configured online processors.

Starting with z/OS V2R4, the system resources manager (SRM) component of z/OS reverses the search direction that is used to find processors for I/O enablement. SRM enables processors for I/O interrupts from the lowest configured CPU ID to the highest configured CPU ID. This enhancement keeps Vh or Vm processors enabled for I/O interrupts after processor topology changes.

The HiperDispatch enhancement is included in the z/OS V2R4 base. It can be added to z/OS V2R2 and z/OS V2R3 by installing the PTF for APAR OA55935. It is identified by the following SMP/E fix categories:

• For the IBM z15 Model T01, use fix category IBM.Device.Server.z15-8561.Exploitation
• For the IBM z15 Model T02, use fix category IBM.Device.Server.z15T02-8562.Exploitation

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 4.10 : Learn about the z/OS SLIP enhancements

Description:

Description

The z/OS SLIP command is enhanced to monitor an address or range of addresses for a key change and in response take a memory dump or set a trace. This behavior is supported in z/OS V2R4 running on the z15. No toleration support is required on earlier releases.

To enable the SLIP function, enter the SLIP command with new options, as follows:

SLIP SET[,options],END

To disable the SLIP function, enter the SLIP command with new options, as follows:

SLIP DEL[,options]

For more information, see SLIP command in z/OS MVS System Commands.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 4.11 : Accommodate the changes to default ARCH and TUNE level

Description:

Description

The z15™ supports the new levels ARCH(13) and TUNE(13), which are needed to take advantage of most of the enhanced vector instructions available on the z15™ in z/Architecture mode. ARCH(13) produces code that uses instructions that are available on the z15, such as the following:

• Vector Enhancement Facility 2
• Miscellaneous-Instruction-Extension Facility 3
• Aligned Vector Load/Store Hint instructions
• Limited exploitation of Vector Packed Decimal Enhancement Facility.

Application developers can recompile their applications with the ARCH 13 compiler option to instruct the compiler to generate code that uses the instructions available on the z15. This action can bring performance improvements for applications without requiring any changes to source code.

It is recommended that you upgrade to the IBM z/OS XL C/C++ V2.4.1 web deliverable for IBM z/OS V2.4, which became available on December 13, 2019. This new compiler supports the C11, C++11, and C++14 language standards. It combines the C language (Clang) infrastructure with the existing advanced optimization technology in the IBM XL compilers to exploit the latest z/Architecture, including the IBM z15. The z/OS XL C/C++ V2.4.1 compiler supports English messages and EBCDIC and ASCII execution character sets, and generates AMODE 64 code, making it ideal for z/OS UNIX users who are porting applications from distributed platforms.

The XL C/C++ V2.4.1 web download is available as a no-charge add-on for installations that have enabled the XL C/C++ compiler (an optionally priced feature) on z/OS V2.4 only. It coexists with and does not replace the base XL C/C++ V2.4 compiler. XL C/C++ V2.4 and V2.4.1 compilers are both designed to be used independently and are also serviced and supported independently.

For the latest offerings from the IBM XL C/C++ compiler family on z/OS, see the z/OS downloads page at z/OS downloads.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 4.12 : Upgrade actions for IBM Integrated Accelerator for z Enterprise Data Compression (zEDC)

Description:

Description

In the z15, the compression functions are moved into the processor chip, which is referred to as IBM Integrated Accelerator for z Enterprise Data Compression (zEDC). IBM Integrated Accelerator for zEDC replaces zEDC Express (FC #0420). IBM Integrated Accelerator for zEDC uses industry standard compression formats for file compression that can enable reduction in the size of data, which can save storage space and increase data transfer rates. The z/OS APIs, both authorized and zlib, transparently enable all existing software exploitation on z15, which was already enabled on z14 and earlier with zEDC Express. Support is available on z/OS V2R1, z/OS V2R2, z/OS V2R3, and z/OS V2R4 when running on z15. No toleration support is required.

Data that is compressed with zEDC Express can be decompressed with IBM Integrated Accelerator for zEDC. The software inflate routine is updated to be RFC-compliant. This change allows for fallback so that IBM Integrated Accelerator for zEDC compressed data can be decompressed on z14 and earlier servers.

As with zEDC Express, IBM Integrated Accelerator for zEDC compression supports two types of processing:

• Synchronous processing in problem state, which is requested through the zlib data compression library services
• Asynchronous processing in authorized state, which is requested through the IBM Z authorized compression services.

As was done previously for zEDC, parmlib member IFAPRDxx is used to enable compression. However, with IBM Integrated Accelerator for zEDC compression on the z15, you use IFAPRDxx only for enabling asynchronous processing. It is not required for zlib-based (problem state) uses.

The following example shows a typical IFAPRDxx entry for IBM Integrated Accelerator for zEDC compression, which uses the same format as the zEDC Express. If your IFAPRDxx member already contains this entry, you can retain it on the z15.

PRODUCT OWNER('IBM CORP')				NAME('Z/OS')				FEATURENAME('ZEDC')				ID(5650-ZOS)				VERSION(*)				RELEASE(*)				MOD(*)				STATE(ENABLED)

Before upgrading to the z15, you must install the z/OS zlib PTFs for this support, which are identified by the following SMP/E fix categories:

• For the IBM z15 Model T01, use fix category IBM.Device.Server.z15-8561.RequiredService
• For the IBM z15 Model T02, use fix category IBM.Device.Server.z15T02-8562.RequiredService

Also, you must apply the PTF for APAR OA56143.

Then, relink your applications with the updated zlib data compression library. If the PTFs are not installed, z/OS attempts to find a zEDC device, which is not supported on the z15. If so, no compression or decompression can occur.

The IBM Z Batch Network Analyzer (zBNA) tool is updated to provide usage estimation for IBM Integrated Accelerator for zEDC compression.

For more information about the zBNA tool, see IBM Techdoc PRS5132 at IBM Z Batch Network Analyzer (zBNA) Tool.

In the future, after you have upgraded all servers to the z15™ level (including servers that are used for disaster recovery), and you have installed the related PTFs on all of your z/OS systems, you might have the following clean-up actions to perform:

• In parmlib member IQPPRMxx, the MAXSEGMENTS option is obsolete and therefore ignored. Also, the defaults for DEFMINREQSIZE and INFMINREQSIZE are changed and those values can no longer be updated through parmlib. You can remove these settings from your IQPPRMxx parmlib member.
• Applications that use zlib no longer require READ access to SAF resource FPZ.ACCELERATOR.COMPRESSION in the FACILITY CLASS. You can remove these application authorizations from your external security manager, such as RACF

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 4.13 : Upgrade the I/O Configuration Program (IOCP) for z15

Description:

Description

It is possible carry forward an IOCDS from a z13 or z14, if no new functions are required from the z15. However, to use the new I/O hardware that is available only on the z15, you must apply the required PTFs, which are identified by the following SMP/E fix categories:

• For the IBM z15 Model T01, use fix category IBM.Device.Server.z15-8561.RequiredService
• For the IBM z15 Model T02, use fix category IBM.Device.Server.z15T02-8562.RequiredService

Also, you must apply the PTF for APAR OA56761.

Note that the z15™ I/O hardware includes:

• Increased coupling CHPIDs per CEC from 256 to 384
• Support for increased ICA-SR to 96 and ICP to 64.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 5 : Actions you can take after installing an IBM z15 server

Description:

These are migration actions that you perform only after you have installed the z15™ server. You need a running z15™ server to perform these actions.

For information about PTFs, see the notes for Table 1 in the step "Migrate to an IBM z15 server."

Step 5.1 : FICON Express16SA

Description:

Description

FICON Express16SA supports a link data rate of 16 gigabits per second (Gbps) and auto-negotiation to 8 Gbps for synergy with current generation switches, directors, and storage devices. With support for native FICON, High Performance FICON for z Systems (zHPF), and Fibre Channel Protocol (FCP), the IBM z15™ server is designed to help you to prepare for an end-to-end 16 Gbps infrastructure to meet the lower latency and increased bandwidth demands of your applications.

The FICON Express16SA adapter will work with your existing fiber optic cabling environment, both single mode and multimode optical cables.

Note:FICON Express16SA is not supported on the z15 Model T02 server.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 5.2 : Upgrade to Virtual Flash Memory (VFM)

Description:

Description

Beginning with the IBM z14 server, IBM Virtual Flash Memory (VFM) is the replacement for the Flash Express features (#0402, #0403), which were available on the IBM zEC12 and IBM z13. No application changes are required to change from IBM Flash Express to VFM.

Ensure that you replace your Flash memory with adequate VFM.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 5.3 : Upgrade actions for Hardware Instrumentation Services (HIS)

Description:

Description

New extended and crypto counters and diagnostic samples are added for the z15. If you want to enable them, you must have Hardware Instrumentation Services (HIS) set up on z/OS.

To start or stop collecting extended or crypto counters or diagnostic sampling, enter the command MODIFY HIS.

No toleration support is needed.

If you want to ignore the HIS enhancements, you might need to update your HIS profilers. For more information, see the topic about starting, configuring, and stopping hardware event data collection. in z/OS MVS System Commands.

Note: If you use the CPU Measurement Facility, IBM recommends that your installation collect SMF 113 subtype 1 and 2 records. IBM also recommends that products process SMF 113 subtype 1 records when available because that is where future enhancements are made. If subtype 1 records are not available, products can process subtype 2 records.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 5.4 : Learn about System Recovery Boost

Description:

Description

New for the z15, this enhancement can provide faster operating system IPL, middleware and workload restart and recovery, and planned shutdown. During a boost period that applies during operating system shutdown and following a reIPL or restart, the IBM z15™ can make additional processing capacity available to the system in a variety of ways to help accelerate processing, and apply that same boosted capacity to improve workload throughput and response time and elapsed time during the boost. Enhancements in Geographically Dispersed Parallel Sysplex (GDPS) automation are also designed to provide faster, more efficient, and more highly-parallel orchestration of GDPS automated reconfiguration activities, such as activating or deactivating images, IPLing images, and so on.

System Recovery Boost works by providing additional processor capacity and parallelism during a boost period, using your installation's already-entitled CPUs and zIIPs. System Recovery Boost does this without increasing the four-hour rolling average (4HRA) IBM software billing cost or MSU consumption associated with your workload during this time.

Note: The IBM z15 Model T02 does not provide the System Recovery Boost Upgrade capability to add additional "temporary capacity" zIIP processors. Thus, the z15 Model T02 does not offer System Recovery Boost Upgrade Feature Codes 9930 and 6802.

For more information about System Recovery Boost, see the following books:

• IBM z15 Technical Introduction, SG24-8850
• IBM Z Capacity on Demand User's Guide, SC28-6985-03

These books are included in the IBM z15 Library, which is available online in Resource Link™.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 5.5 : Enable BCPii communications on the support element

Description:

Description

For Support Elements that run on z15, the setting for the “Cross Partition Authority” option is replaced by new security settings on the System Details panel and the Customize Image Profiles panel.

For more information, see the step named "Enable BCPii communications on the support element" in the z/OS V2R4 Upgrade Workflow.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 5.6 : Learn about IBM Integrated Accelerator for z Enterprise Data Compression (zEDC)

Description:

Description

Beginning with the z15, IBM Integrated Accelerator for z Enterprise Data Compression (zEDC) replaces the zEDC Express (FC #0420). As an integrated part of the z15™ processor chip, the Integrated Accelerator for zEDC does not require the purchase of a hardware feature or usage of I/O slots.

No change is required when z/OS is upgraded from a z14 to a z15.

Observe the following differences in processing:

• RMF changes:
  • On earlier IBM Z servers, you used the RMF PCIE report to monitor the usage of zEDC devices. Starting with the z15, you can now monitor compression activity by referring to the I/O Queuing Activity report and the Extended Asynchronous Data Mover (EADM) device summary instead. RMF EADM reporting (SMF 74.10), which was previously known as Storage Class Memory (SCM) Statistics, is enhanced with asynchronous execution information.
  • On the z15, the RMF PCIE report no longer contains any information about compression.
• Synchronous mode compression is not recorded; it is treated as an instruction invocation.
• Asynchronous mode compression is recorded, as follows:
  • SMF30 information is captured
  • In RMF, the EADM device summary provides information about compression.
  • SAP utilization is updated to include time for compression and decompression.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 6 : Accommodate functions for the z15 to be discontinued on future servers

Description:

Note:

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

The steps in this section involve changes in hardware support that could affect your environment. Make the appropriate changes, as needed.

Step 6.1 : Prepaid On/Off Capacity on Demand tokens will not carry forward

Description:

Description

Beginning with IBM z15™, new prepaid On/Off Capacity on Demand (On/Off CoD) temporary CP resource tokens do not carry forward to future systems. On/Off CoD from IBM allows you to enable and disable hardware engines to meet temporary peak business needs. On the IBM Z platform, this hardware offering is available exclusively on supported IBM Z servers. Charges that are related to both hardware and software depend on the duration of the temporary enablement and the capacity enabled.

Beginning with IBM z15 Model T02, prepaid tokens for On/Off Capacity on Demand (On/Off CoD) will expire 5 years after the LICCC expiration date.

Note: IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 6.2 : Prepare for the removal of support for TLS 1.0 and TLS 1.1 for SE, HMC, and OSC

Description:

Description

IBM z15™ is planned to be the last IBM Z server to to support the use of the Transport Layer Security protocol versions 1.0 (TLS 1.0) and version 1.1 (TLS 1.1) for establishing secure connections to the Support Element (SE), Hardware Management Console (HMC), and Open Systems Adapter (OSA) Integrated Console Controller (channel path type OSC).

Note: IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

Instructions:

This information was provided for your understanding and possible further action as dictated by your site policies.

Step 7 : Provide feedback to IBM on your upgrade experience

Description:

IBM would like your feedback on this upgrade experience

Instructions:

In this example step, you generate a feedback summary file by selecting the workflow instance and clicking "Generate Feedback Summary" in the "Action" drop-own menu. The summary is based on the values that were entered previously. This step is optional.

You can edit the file as needed after it is created. If you want to change your answers, you can recreate the file.

When you are ready to send the file to IBM, attach it to an email and sent it to zosmig@us.ibm.com. As you can see in the feedback file, only the information you want to provide will be seen by IBM. No other information is gathered.

Thank you for providing your feedback to IBM.