Abstract for the z/OS Upgrade Workflow

This information supports z/OS® V2R5 and the IBM® z16™ and IBM z15 servers.

Plan your upgrade to z/OS V2R5

IBM z/OS V2R5 is designed to enable and drive innovative development to support new hybrid cloud and AI business applications. This new release offers easier access and a simplified experience to next-generation systems operators and developers, while providing optimal usage of IBM Z computing power and resources for scale, security, and business continuity.

For more information, see IBM United States Software Announcement 221-057.

z/OS V2R5 Upgrade Workflow

The z/OS V2R5 Upgrade Workflow provides the steps for upgrading your system to z/OS V2R5. Two workflows are provided. Depending on whether you are upgrading from z/OS V2R4 or z/OS V2R3, select the workflow that applies to your upgrade path and open it in z/OSMF to begin the upgrade process. 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).

Now included with z/OS: 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 V2R5 Upgrade Workflow, run the SMP/E REPORT MISSINGFIX command on your z/OS systems and specify a FIXCAT value of "IBM.Coexistence.z/OS.V2R5".

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

Prior levels of the z/OS Upgrade Workflows for z/OS V2R2, V2R3, V2R4, and z14 are available online at the following location: z/OSMF workflows for the z/OS platform

Next, you create the workflow on your z/OS system, as described in Creating the upgrade workflow in z/OSMF.

Introducing the IBM® z16™ Upgrade Workflow

The IBM Z® platform is recognized for its security, resiliency, performance, and scale—relied upon by businesses around the globe for mission-critical workloads and as an essential element of their hybrid cloud infrastructure. IBM® z16™, the first IBM Z system built with the IBM Telum Processor, extends the platform's capabilities and adds new value with innovative technologies that businesses require as they digitally transform their enterprises.

The IBM z16™ 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 z16™ server is one hardware model (A01) and machine type (3931), with five feature codes to represent the processor capacity. The feature codes are 0667, 0668, 0668, 0669, and 0670 with (respectively) 39, 82, 125, 168, and 200 processors.

The IBM z16™ Upgrade Workflow contains the upgrade steps for the IBM z16™ server. These include 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.

The z/OS z16 Upgrade Workflow is provided and maintained with z/OS PTFs that are assigned the following SMP/E fix category (FIXCAT): IBM.Device.Server.z16-3931.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.

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.

As of z/OS V2R4, IBM® no longer provides a z/OS Migration publication. Since z/OS V2R2, the preferred method for learning about migration actions has been the z/OS Upgrade Workflow. Discovering, performing, and verifying many upgrade actions through the z/OSMF Workflows task instead of a more traditional book format allows for a tailored and specific upgrade path that is associated with a particular system. Beginning with z/OS V2R4, IBM provides upgrade tasks in a z/OSMF workflow, as well as a single exported file. By providing the z/OS V2R4 upgrade materials in both formats, users can enjoy the advantages of a z/OSMF workflow and still be able to search, browse, and print in a more traditional format.

Along with the change of format—a workflow instead of a book—is a change in terminology: upgrade instead of migrate. In our industry, the process of replacing software with a newer level is most often referred to as upgrading the software. In contrast, the phrase migrating the software can be taken to mean moving software from one server to another. When you perform the actions that are described in the workflow, you are upgrading z/OS to a newer level of function than the prior release. Thus, upgrade is the appropriate term for what these workflows do.

In z/OS V2R4, the z/OS upgrade workflow is renamed to the z/OS Upgrade Workflow to better identify that each z/OS release contains a higher level of functionality than the prior release. In the workflow, the term upgrade is used in place of migration.

With the removal of the traditional z/OS Migration publication, it is strongly 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 any environment.

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.

To create an upgrade workflow, 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 IBM z16 Upgrade Workflow, enter z16_zOS_Upgrade_Workflow.xml
      • For the IBM z15 Upgrade Workflow, enter z15_zOS_Upgrade_Workflow.xml
      • For the z/OS V2R5 Upgrade Workflow, enter either of the following file names, depending on whether you are upgrading from z/OS V2R3 or z/OS V2R4:
        • zOS_V2.5_from_V2.3_Upgrade_Workflow.xml
        • zOS_V2.5_from_V2.4_Upgrade_Workflow.xml

        For the IBM z16™, IBM z15, and z/OS V2R5 workflows, the workflow definition files reside in file path /usr/lpp/bcp/upgrade after you install the associated PTFs on your z/OS system.

        For earlier workflows, such as the z/OS V2R4 Upgrade Workflow, you must store the workflow definition file and its accompanying files into your file system. Then, enter the fully qualified path name of the file, beginning with the forward slash (/) and including the file name. For example: /Service/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).
      • Let the Access type 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'd like to receive and include your email address for receiving the files. The files range in size from approximately 500 KB to 12 MB.