Abstract for the z/OS Upgrade Workflow

This information supports z/OS® 3.2, 3.1, and 2.5, and the IBM® z17, IBM z16, and IBM z15 servers.

The following information is provided:

Upgrading to z/OS 3.2

IBM z/OS Release 3.2, the latest release of the IBM flagship mainframe operating system, is designed for hybrid cloud and AI, includes support for IBM z17®, and aims to fuel innovation and growth, secure critical data, simplify IT, and enable automation for operational efficiency. Key features include support for hardware-accelerated AI-infused capabilities throughout the stack, operational AI insights, industry-leading cyber resiliency, support for hybrid cloud application architectures, enhancements to simplify systems management, and improved infrastructure optimization.

For more information, see the IBM announcement: IBM z/OS 3.2 unlocks the value of IBM z17.

Planning information for z/OS 3.2

To help you start planning for z/OS 3.2, see z/OS Planning for Installation.

Introducing the z/OS 3.2 Upgrade Workflow

The z/OS 3.2 Upgrade Workflow provides the steps for upgrading to z/OS 3.2 from your currently supported z/OS system. When you run the workflow in IBM z/OS Management Facility (z/OSMF), you perform the system upgrade as an interactive, step-by-step process. The z/OS 3.2 Upgrade Workflow uses the latest functions in z/OSMF to provide a smooth upgrade experience.

In the workflow, discovery functions run automatically to further streamline your upgrade experience. Only the upgrade actions that apply to your particular system are identified in the z/OSMF user interface (UI).

The z/OS 3.2 Upgrade Workflow is available in a choice of two z/OSMF workflows, depending on your upgrade path — from z/OS 3.1 or z/OS 2.5:
  • zOS3.2_from_zOS3.1_Upgrade_Workflow.xml
  • zOS3.2_from_zOS2.5_Upgrade_Workflow.xml

Depending on whether you are upgrading from z/OS 3.1 or z/OS 2.5, select the workflow that applies to your upgrade path and download it to your system. Then, create the workflow on your z/OS system, as described in Creating the upgrade workflow in z/OSMF.

IBM provides the upgrade workflows as part of the z/OS product. Updates and fixes for the upgrade workflows are delivered through the standard z/OS service process. To obtain the latest PTFs for the z/OS 3.2 Upgrade Workflow, run the SMP/E REPORT MISSINGFIX command on your z/OS systems and specify a FIXCAT value of IBM.Coexistence.z/OS.3.2.

The z/OS 3.2 Upgrade Workflow can be run on z/OS releases 2.5, 3.1, and 3.2.

Introducing the IBM z17 workflow

The IBM Z platform is recognized for its long-standing commitment to delivering best-in-industry security, resiliency, performance, and scalability. IBM Z is relied on for mission-critical workloads and as an essential element of hybrid cloud infrastructures. The newest member of the IBM Z family, IBM z17, continues that commitment and adds value with innovative technologies that can help accelerate the digital transformation journey.

IBM z17 makes more possible, enabling AI where it matters most to drive efficiency, innovation, and better business outcomes. It was fully engineered from the chip through the software stack for AI to optimize mission-critical transaction processing and data-intensive workloads. With this full stack optimization, enhanced AI acceleration capabilities, along with improved I/O density and efficient processor power management, IBM z17 delivers scalable AI inferencing that runs in an energy-efficient compute environment.

The IBM z17 uses a 19-inch form factor and industry-standardized power and networking hardware, which easily aligns with the modern cloud data center.

The IBM z17 platform includes the following hardware model:
  • Model ME1 (machine type 9175), with five feature codes to represent the processor capacity. The feature codes are Max43, Max90, Max136, Max183, and Max208 with (respectively) 43, 90, 136, 183, and 208 processors. This system is configurable as a one-to-four 19-inch frame system.

For more information, see IBM z17 Announcement Letter.

The IBM z17 Upgrade Workflow contains the upgrade steps for the IBM z17 server. The workflow includes considerations, restrictions, and actions to take before and after you receive your server, and a checklist of items that are planned to be discontinued on future servers.

In the workflow, references to "z17" pertain to all processor configurations of the IBM z17, unless otherwise noted.

The IBM z17 Upgrade Workflow is provided and maintained with z/OS PTFs that are assigned to the following SMP/E fix category (FIXCAT).
  • Required service for IBM z17 machine type 9175 (Model ME1):
    • IBM.Device.Server.z17-9175.RequiredService

After the PTFs are installed, you can create the workflow on your z/OS system, as described in Creating the upgrade workflow in z/OSMF.

The z17 Upgrade Workflow can run on z/OS release 2.4 and later.

Upgrading to z/OS 3.1

The z/OS 3.1 Upgrade Workflow is available in a choice of two z/OSMF workflows, depending on your upgrade path — from z/OS 2.5 or z/OS 2.4:
  • zOS3.1_from_zOS2.5_Upgrade_Workflow.xml
  • zOS3.1_from_zOS2.4_Upgrade_Workflow.xml

Depending on whether you are upgrading from z/OS V2R5 or z/OS V2R4, select the workflow that applies to your upgrade path and download it to your system. Then, create the workflow on your z/OS system, as described in Creating the upgrade workflow in z/OSMF.

IBM provides the upgrade workflows as part of the z/OS product. Updates and fixes for the upgrade workflows are delivered through the standard z/OS service process. To obtain the latest PTFs for the z/OS 3.1 Upgrade Workflow, run the SMP/E REPORT MISSINGFIX command on your z/OS systems and specify a FIXCAT value of "IBM.Coexistence.z/OS.3.1".

The z/OS 3.1 Upgrade Workflow can be run on z/OS releases V2R4, V2R5, and 3.1.

A better z/OS upgrade experience with z/OSMF workflows

Using a z/OSMF workflow, you can perform a z/OS upgrade as an interactive, step-by-step process. The z/OS Upgrade Workflow uses the latest functions in z/OSMF to provide a smooth upgrade experience.

It is recommended that you plan for your next upgrade by having z/OSMF ready to use in at least one location in your enterprise. Notice that the exported format of the z/OS upgrade materials that can be read or printed for those without any z/OSMF capabilities is not tailored for your environment.

Discovery functions:

The z/OS Upgrade Workflow includes the following discovery functions:
  • Runs the SMP/E MISSINGFIX report to determine whether any applicable fix category (FIXCAT) APARs should be installed.
  • Discovers which upgrade-related APARs are already installed.
  • Automatically skip steps for which no actions are required if a given APAR is installed.

Workflow structure:

Upgrade actions are sequenced in the order in which you must perform them, rather than grouped by z/OS element. This enhancement makes it easier for you to track your progress at each stage of the upgrade, as follows:

  • Phase 1: Actions to perform before installing z/OS Upgrade actions that you can perform on your existing (old) system so that you have fewer actions to perform after you install the new release of z/OS. You do not need the new level of code to make these changes, and the changes do not require the new level of code to run after they are completed.
  • Phase 2: Actions to perform before the first IPL of z/OS Upgrade actions that you can perform after you have installed the new release of z/OS, but before you IPL it for the first time. These actions require the new release to be installed, but do not require it to be active on your system.
  • Phase 3: Actions to perform after the first IPL of z/OS Upgrade actions that you can perform only after you have IPLed the new release of z/OS. These actions should be performed on the new release of z/OS after it is up and running.

Creating the upgrade workflow in z/OSMF

Your user ID requires at least READ authority to the workflow XML files and the related .txt files.

The workflow definition files reside in file path /usr/lpp/bcp/upgrade after you install the associated PTFs on your z/OS system. You might also find the z/OS V2R5 workflows from earlier installations in that directory.

To create an upgrade workflow on your system, do the following:
  1. In the z/OSMF Desktop, open the Workflows task.
  2. From the Actions menu, select Create Workflow. The Create Workflow dialog is displayed.
    1. Type the name of the workflow definition file that corresponds to the workflow that you want to run:
      • For the z/OS 3.2 Upgrade Workflow, enter either of the following path names, depending on whether you are upgrading from z/OS 3.1 or z/OS 2.5:
        • /usr/lpp/bcp/upgrade/zOS3.2_from_zOS3.1_Upgrade_Workflow.xml
        • /usr/lpp/bcp/upgrade/zOS3.2_from_zOS2.5_Upgrade_Workflow.xml
      • For the IBM z17 Upgrade Workflow, enter /usr/lpp/bcp/upgrade/z17_zOS_Upgrade_Workflow.xml
      • For the z/OS 3.1 Upgrade Workflow, enter either of the following path names, depending on whether you are upgrading from z/OS V2R4 or z/OS V2R5:
        • /usr/lpp/bcp/upgrade/zOS_3.1_from_V2.5_Upgrade_Workflow.xml
        • /usr/lpp/bcp/upgrade/zOS_3.1_from_V2.4_Upgrade_Workflow.xml
      • For the IBM z16® Upgrade Workflow, enter /usr/lpp/bcp/upgrade/z16_zOS_Upgrade_Workflow.xml
    2. For the Workflow variable input file, leave this field blank.
    3. In the System field, specify the system on which you will run the upgrade workflow jobs (the system that you are upgrading).
    4. To continue, click Next.
    5. Complete the following input fields:
      • In the Workflow name field, enter a descriptive name for the workflow.
      • In the Owner user ID field, specify the user ID of the person who will perform the workflow.
      • In the Comments field, you can optionally enter any information that you want to associate with the workflow (up to 500 characters).
      • Allow the Access type to default to Public, or select a different access type (see the online help for details).
      • Select Open workflow on finish.
      • Select Assign all steps to owner user ID if you want all of the steps to be assigned to you on creation of the workflow. Otherwise, leave this checkbox cleared (the default).
      • Click Finish to create the workflow.

Usage tips

  • Use the enhanced discovery functions. Follow the instructions in the first step "Discover z/OS features in use" to allow z/OSMF to skip as many inapplicable steps as possible, thus reducing the number of steps for you to perform. The additional discovery includes the option to skip steps that are empty (which have actions that are shown as "None"). In addition, discovery is enhanced to skip over the hardware server levels that you have already upgraded to.
  • Some upgrade actions have associated health checks. For those steps, the health check is invoked to determine whether the upgrade action is applicable for your system. Read the instructions carefully on the Perform tab before running the health check for important information about each check.
  • For the individual upgrade actions and for the entire upgrade effort, you can optionally provide your feedback to IBM. Follow the instructions that are shown in the workflow. You do not need to provide feedback to complete each step of the workflow.

Exported upgrade workflow files

You can generate an exported file from an active z/OSMF workflow at any time. In the z/OSMF Workflows task, select the action Export Workflow as a Printable Format in the Workflow Steps table to view options for formatting the workflow as a printable document. After selecting the applicable options, click OK to create the output (an HTML file), which opens in a new web browser window. To print the file, select the print function for your web browser.

Although it is recommended that you use the upgrade workflows directly, you might find the following exported HTML files to be suitable for browsing or searching:

The files that are listed here are available as HTML files. To request one, send an email request to zosmig@us.ibm.com. In your email, indicate which exported files you would like to receive and include your email address for receiving the files. The files range in size from approximately 500 KB to 12 MB.