Added 2026-08-13:
VIO Journaling Deprecation; PLPA and VIO Always Refreshed at IPL
What is being removed or changed
In the z/OS release following z/OS 3.2, VIO Journaling will no longer be supported and consequently, the VIODSN= IEASYSxx system parameter will be ignored. Jobs that can be automatically restarted will no longer be able to use VIO. Additionally, all IPLs will be Cold Start, meaning that VIO and PLPA data will not be retained from the prior IPL, they will always be refreshed across an IPL. The VIODSN=, CLPA and CVIO IEASYSxx parameters will be ignored and message ASA022I will be issued if any of these parameters are used.
Required customer migration or upgrade actions
The migration action consists of the following steps:
(1) Determine whether you are using VIO Journaling and (2) Determine whether you have jobs that need to be restartable.
If the IEASYSxx VIODSN= parameter is either omitted or not equal to IGNORE then it is possible that VIO journaling is being used. Issue DISPLAY IPLINFO,VIODSN to determine the value of the VIODSN= parameter. If the value is not IGNORE, then VIO journaling is enabled. Alternatively, install OA69654 and enable the migration health check ZOSMIG32_NEXT_ASM_VIOJOURNALING.
For (2) look for RD=R or RD=RNC on the JCL JOB or EXEC statements as well as the RESTART=YES and JOURNAL=YES option on JES2 job classes.
To prepare for this change on z/OS 3.1 or 3.2, for (1) specify VIODSN=IGNORE and CLPA to simulate the behavior of future releases. Remove VIODSN=, CVIO, and CLPA parameter specifications after upgrading, as they will be ignored.
For (2), reevaluate whether automatic restart support is still required for affected jobs and use temporary DASD data sets instead of VIO if automatic restart is required.
Why is IBM making this change?
Maintaining VIO Journaling requires additional writes to paging data sets and can result in worse performance than using temporary DASD data sets. IBM is simplifying system behavior and removing an outdated function that can negatively impact performance while preserving support for restartable workloads through alternative approaches.
Links to the relevant documentation
z/OS MVS Initialization and Tuning Guide
z/OS MVS Initialization and Tuning Reference
z/OS DFSMSdfp Storage Administration
z/OS JES2 Initialization and Tuning Guide
z/OS JES2 Initialization and Tuning Reference
Added 2026-07-28:
Removal of Support for BCPii V1
What is being removed or changed
Base Control Program internal interface (BCPii) is a z/OS interface to the IBM Z firmware for platform management. It is available as version 1 (V1) and version 2 (V2). V1 refers to the functionality using HWICONN and similar interfaces, while V2 refers to HWIREST for REST-like access to the Hardware Management Console (HMC) interfaces.
BCPii V1 APIs have had no feature enhancements since BCPii V2 was introduced. BCPii V2 APIs (HWIREST) have been supported since the IBM z15 with z/OS V2.4, with the exception of asynchronous notifications (HWIEVENT).
BCPii V2 was introduced with the IBM z17 and z/OS 3.1 as an additional callable service (HWIREST2), which enables asynchronous notification communications and other enhancements. With the IBM z17 using z/OS 3.1, HWIEVENT services can be fully migrated to BCPii V2 APIs.
IBM intends for the next IBM Z server to be the final server to support BCPii V1. With the server generation that follows the next IBM Z server generation, IBM Z firmware is planned to require BCPii V2 HWIREST, and HWIREST2, if needed, to manage the Central Processor Complex (CPC). BCPii V1 functionality for this future CPC is not planned to be available. Using BCPii V1 such as HWICONN to address this future CPC is planned to result in an error. BCPii V1 can still be used to address older CPCs.
Required customer migration or upgrade actions
Identify applications that use BCPii V1 such as HWICONN. Plan and test migration to BCPii V2 APIs, including HWIREST and HWIREST2 where appropriate. Complete migration before deploying applications on future IBM Z server generations.
Why is IBM making this change?
BCPii V2 provides enhanced capabilities and has been the strategic direction for firmware management since its introduction. With the addition of HWIREST2, all BCPii V1 functions, including asynchronous notification capabilities, can now be supported through the BCPii V2 architecture. Consolidating on BCPii V2 simplifies platform management and allows IBM to focus future enhancements on a single interface.
Links to the relevant documentation
z/OS Statement of Direction AD26-0808
Removal of Support for Software Configuration Library Manager (SCLM)
What is being removed or changed
z/OS 3.2 is planned to be the last release to support Software Configuration Library Manager (SCLM). SCLM is an ISPF-based change control, build automation, and version control solutions for z/OS application development, and was functionally stabilized in 2018.
Required customer migration or upgrade actions
Identify development teams and applications that rely on SCLM. Plan migration to either IBM Developer for z/OS Enterprise Edition (5755-AB5) or Git, which IBM makes available from the IBM Open Enterprise Foundation for z/OS (5655-OEF). Update development processes, training materials, and build procedures to use the selected replacement solution.
Why is IBM making this change?
IBM's strategic direction for application lifecycle management is centered on modern development tools and Git-based workflows. Retiring SCLM allows IBM to focus investment on current development platforms that provide broader ecosystem integration, modern source control capabilities, and support for contemporary development practices.
Links to the relevant documentation
z/OS Statement of Direction AD26-0808
Removal of Support for the IEALIMIT Installation Exit
What is being removed or changed
The IEALIMIT installation exit will no longer be supported in the z/OS release following z/OS 3.2. Originally introduced in the 1970s, IEALIMIT was used to restrict the amount of 24-bit private memory that a job step could use. The same objectives can now be achieved through newer mechanisms such as the REGIONBELOW and REGIONLIMITBELOW parameters in SMFLIMxx and the IEFUSI exit. If a customized IEALIMIT exit is present, it will no longer be invoked.
Required customer migration or upgrade actions
Determine whether your installation has overridden the IBM-supplied IEALIMIT exit. If a customized IEALIMIT exit is in use, replace its functionality with either the SMFLIMxx REGIONBELOW and REGIONLIMITBELOW parameters or the IEFUSI exit. Review and update any operational documentation that references IEALIMIT before upgrading to the next release of z/OS.
To determine whether your installation has overridden the IBM-supplied IEALIMIT exit, use the migration health check ZOSMIG32_NEXT_VSM_IEALIMIT when it becomes available, or examine the IEALIMIT module in the nucleus. If the module contains the IBM-supplied default implementation, no action is required. If a customized version is present, plan to migrate the logic to the SMFLIMxx REGIONBELOW and REGIONLIMITBELOW parameters or the IEFUSI exit.
Why is IBM making this change?
IEALIMIT is an outdated mechanism that has been superseded by newer and more flexible alternatives. SMFLIMxx provides a simpler, configuration-based approach, while IEFUSI offers greater capability by allowing control of additional memory limits beyond those supported by IEALIMIT. Removing IEALIMIT simplifies system management and encourages use of the strategic solutions already available in z/OS.
Links to the relevant documentation
IEALIMIT User Region Size Limit Exit
Deprecation of Automatic Java Installation Symbolic Link Updates for IBM Semeru Runtime for z/OS
What is being removed or changed
IBM Semeru Runtime for z/OS currently creates and updates symbolic links (current and current_64) during SMP/E installation to point to the highest installed Java version. While this behavior continues through Java 25, future releases might no longer automatically create or update these symbolic links. Customers should prepare by explicitly configuring applications to reference specific Java installation paths rather than relying on IBM‑managed symbolic links.
Required customer migration or upgrade actions
Review applications, scripts, JCL, environment variables, and operational procedures that reference the current or current_64 symbolic links. Update these references to point directly to the required Java installation path. Validate application compatibility before Java upgrades and explicitly manage which Java version is used by each application. If symbolic links remain desirable, consider creating and maintaining installation-specific symbolic links under your own administrative control.
Why is IBM making this change?
Automatic updates to shared symbolic links can unintentionally change the Java version used by applications following a Java installation or upgrade. In environments with multiple Java versions installed, applications often require strict control over which Java level they use. IBM is making this change to reduce the risk of unexpected runtime behavior and encourage explicit management of Java version selection.
Links to the relevant documentation
Official deprecation notice in Semeru Runtimes V25 for z/OS documentation
Installing the SDK
Added 2026-06-24:
Memory Reconfiguration (RSU= IEASYSxx Parameter)
What is being removed or changed
IBM is evaluating the future of the RSU= IEASYSxx system parameter, which is used to specify reconfigurable memory for z/OS Memory Reconfiguration. This capability allows memory to be taken offline from one LPAR and brought online in another without requiring an IPL. IBM is considering deprecating the RSU= parameter because reconfigurable memory introduces additional complexity to z/OS memory management and can negatively affect performance. Support for configuring memory offline for unassigned Dedicated Memory and configuring memory online for all memory types would continue.
Required customer migration or upgrade actions
Determine whether your environment uses reconfigurable memory. Enable the RSM_RSU health check and review the results. Review any operational procedures that use the CONFIG STOR command to move memory between LPARs. If reconfigurable memory is in use, IBM is requesting customer feedback on how the capability is used and whether it is required to support dynamic workload management.
If you see the following message during NIP and hardcopy log, there is no need for this upgrade action:
IAR013I NO STORAGE IS RECONFIGURABLE
Why is IBM making this change?
Reconfigurable memory adds complexity to z/OS memory management and can negatively impact performance because the memory must remain movable. IBM is evaluating whether the capability is still needed in modern environments before determining its future direction.
Links to the relevant documentation
Overview of IEASYSxx parameters
Added 2026-05-26:
Removal of Support for the Resource Measurement Facility (RMF) z/OSMF plugin
What is being removed or changed
z/OS 3.2 is planned to be the last release to support the Resource Monitoring z/OSMF plugin.
Access to RMF Monitor III metrics and reports will shift to the RMF for z/OS Grafana plugin, which is now signed by Grafana Labs. Users accessing Grafana dashboards through z/OSMF will instead access them directly via the Grafana plugin.
Required customer migration or upgrade actions
Transition to the RMF for z/OS Grafana plugin for performance monitoring. Update processes to access RMF data through Grafana dashboards. Ensure users are familiar with the new interface and capabilities.
Why is IBM making this change?
The RMF for z/OS Grafana plugin provides richer visualization, greater customization, and a more modern user experience than the z/OSMF plugin. IBM is focusing future investment on Grafana-based monitoring capabilities.
Links to the relevant documentation
Statement of Direction AD26-0529
Removal of Support for the RMF Performance Monitoring (RMF PM) tool
What is being removed or changed
z/OS 3.2 is planned to be the last release to support the RMF Performance Monitoring (RMF PM) tool.
RMF PM has been used to monitor z/OS performance via TCP/IP and visualize sysplex resource data. Equivalent and enhanced capabilities are now available through the RMF for z/OS Grafana plugin.
Required customer migration or upgrade actions
Transition from the RMF PM tool to the RMF for z/OS Grafana plugin. Use the Grafana dashboards that replicate existing RMF PM displays. Import existing dashboards where needed and validate monitoring workflows.
Why is IBM making this change?
The RMF for z/OS Grafana plugin now provides dashboards that replicate and extend RMF PM capabilities. Consolidating performance monitoring around Grafana simplifies the tooling landscape and improves data visualization.
Links to the relevant documentation
Statement of Direction AD26-0529
Added 2026-04-29:
Discontinuance of selected fonts and new support for added fonts
What is being removed or changed
IBM intends that z/OS 3.2 is the last z/OS release that will provide the following fonts:
• Courier and Courier Symbol
• Helvetica and Helvetica Symbols
• Optical Character Recognition - B (OCRB)
• Times New Roman and Times New Roman Symbols
• WorldType
These fonts are provided as part of the z/OS Font Collection, which is a base element of z/OS. IBM intends to deliver a new set of fonts based on the TrueType subset of the IBM Plex family in a future z/OS release, which will include Advanced Function Presentation (AFP) Outline and AFP Raster versions.
Why is IBM making this change?
IBM is modernizing the z/OS font collection by replacing older font families with new fonts based on IBM Plex. This simplifies font maintenance while providing a more current and strategic font offering.
Links to the relevant documentation
z/OS Statement of Direction AD26-0431
Added 2026-04-10:
IXGCNFxx PARMLIB Updates
What is being removed or changed
The following IXGCNFxx parmlib options can no longer be modified in the next release of z/OS:
- MANAGE OFFLOAD USEOFFLOADMIN
- MANAGE STAGING USESTAGINGMIN
The following IXGCNFxx parmlib options can be modified but should not be modified in the next
release of z/OS:
- MONITOR OFFLOAD WARNALLOC
- MONITOR OFFLOAD ACTIONALLOC
- MONITOR OFFLOAD WARNRECALL
- MONITOR OFFLOAD ACTIONRECALL
- MONITOR LSPRIMARY CONSUMPTIONALERT
- MANAGE HYPERWRITE ALLOWUSE
Required customer migration or upgrade actions
This change will be made the next release of z/OS. More information can be made available by requesting in thread below.
Why is IBM making this change?
These IXGCNFxx parameters control behaviors that are now managed more effectively by the system. By removing or discouraging manual tuning of these options, IBM can simplify configuration and reduce the need for administrators to manage settings that provide limited benefit in modern z/OS environments. This change also helps promote more consistent system behavior across installations.
Links to the relevant documentation
Statements and parameters for IXGCNFxx
Added 2026-04-06:
Removal of Support for IBM Cloud Provisioning and Management for z/OSMF
What is being removed or changed
z/OS 3.2 is planned to be the last release to support the z/OSMF IBM Cloud Provisioning and Management plugin and sample Marketplace plugin.
Required customer migration or upgrade actions
Migrate provisioning workflows to Red Hat Ansible Automation Platform using IBM z/OS Ansible collections.
Why is IBM making this change?
IBM is aligning z/OS automation and provisioning with Red Hat Ansible Automation Platform and IBM z/OS Ansible collections. This provides a more consistent automation strategy across enterprise environments and focuses investment on strategic automation technologies.
Links to the relevant documentation
Statement of Direction AD25-1697
Removal of Support for the Common Information Model (CIM) Server
What is being removed or changed
z/OS 3.2 is planned to be the last release to include the CIM server.
Required customer migration or upgrade actions
Identify CIM dependencies and remove or replace them before upgrading beyond z/OS 3.2.
Why is IBM making this change?
Use of CIM-based management has declined as newer management frameworks and APIs have become available. Removing the CIM server reduces platform complexity and maintenance requirements.
Links to the relevant documentation
z/OS 3.2 Announcement - Statement of Direction AD26-0005
Removal of Support for Quick Start and Warm Start IPLs
What is being removed or changed
z/OS 3.2 is planned to be the last release to support quick start and warm start IPLs.
Required customer migration or upgrade actions
Review IPL procedures and validate cold start IPL behavior prior to upgrade.
Why is IBM making this change?
These IPL methods are no longer widely used and add complexity to system initialization processing. Simplifying IPL handling helps improve consistency across z/OS environments.
Links to the relevant documentation
z/OS 3.2 Announcement - Statement of Direction AD26-0005
Removal of Support for LNKLSTxx and IEAAPFxx Parmlib Members
What is being removed or changed
z/OS 3.2 is planned to be the last release to support LNKLSTxx and IEAAPFxx parmlib members.
Required customer migration or upgrade actions
Migrate linklist and APF definitions to PROGxx and validate dynamic updates.
Why is IBM making this change?
The functionality provided by these members has long been available through PROGxx. Consolidating configuration management into a single mechanism simplifies administration and reduces duplicate configuration paths.
Links to the relevant documentation
z/OS 3.2 Announcement - Statement of Direction AD26-0005
Removal of Support for BPXWH2Z Migration Utility
What is being removed or changed
z/OS 3.2 is planned to be the last release of the operating system to support the BPXWH2Z migration utility. This utility was used to migrate data from Hierarchical File System (HFS) data sets to z/OS File System (zFS) data sets. Because HFS data sets have not been mountable since z/OS V2.5, this utility is no longer required.
Required customer migration or upgrade actions
Clients should discontinue use of BPXWH2Z and use the strategic migration utility BPXWMIGF, first introduced in z/OS V2.3. BPXWMIGF supports data migration from HFS to zFS as well as zFS to zFS and should be used for any remaining file system migration needs.
Why is IBM making this change?
Since HFS file systems have not been mountable since z/OS V2.5, BPXWH2Z is no longer needed. IBM is standardizing on BPXWMIGF as the strategic migration utility.
Links to the relevant documentation
z/OS Statement of Direction AD26-0257
Removal of Support for the PAGEDEL DELETE Option
What is being removed or changed
z/OS 3.2 is intended to be the last release to support the DELETE option on the PAGEDEL system command. PAGEDEL DELETE has been functionally superseded by PAGEDEL REPLACE.
Required customer migration or upgrade actions
Customers should transition all usage of PAGEDEL DELETE to PAGEDEL REPLACE. PAGEDEL REPLACE is the long‑recommended alternative and offers benefits such as reduced memory usage and improved processing efficiency.
Why is IBM making this change?
PAGEDEL REPLACE has superseded PAGEDEL DELETE and provides operational advantages. Removing the older option simplifies command processing and encourages use of the preferred implementation.
Links to the relevant documentation
z/OS Statement of Direction AD26-0257