Linux Foundation Logo
Zowe Logo

Table of Contents

Latest Announcements Coming changes to the functionality Changes to the Conformance Criteria Office Hours Frequently Asked Questions Frequently Asked Questions - User focused API ML for Users Frequently Asked Questions Frequently Asked Questions - Extender focused Zowe API Mediation Layer Office Hours Zowe Explorers for VSCode Office Hours Zowe App Framework, ZSS Office Hours Zowe System Installation and Configuration Office Hours

Latest Announcements

Zowe v3 is going GA on 2024/03/28

Zowe V2 will have 3 more releases - 2.16 (May 30), 2.17 (July 15), 2.18 (August 30) Zowe V1 will End Support on September 30, 2024 with last patch release planned for October 14th

Learn more about Zowe Extensions V3 Compatibility, Conformance, and Availability Statement on Downloads page

Coming changes to the functionality

**Breaking changes** - The authentication endpoints wont support the route /api/v1/gateway and instead will support only /gateway/api/v1 - Spring Enabler will be updated to Spring Boot 3 and Spring 6 and the Spring Boot 2 and Spring 5 versions won't be supported anymore - Datasets API is archived - Jobs API is archived - Metrics service is archived - IMS API is archived - Java 17 is required for API Mediation Layer to run - z/OSMF in version V2R5 with APAR PH12143 applied - Statically onboarded services needs to do it via modifying the zowe.yaml and adding a directory outside of the zowe to read the files from - Keyrings need to change configuration from safkeyring://// to safkeyring:// - Support access to the zosmf only via /ibmzosmf route. Supporting both created issues for CLI setup **Important updates** - Authentication and Authorization Service is separate service, only one that needs z/OS directly
**Breaking changes** - Update Angular to Version 16 from Version 12 - Remove core-js dependency - Update Webpack to version 5 - Update Typescript to 4.9
**Breaking changes** - Introduce new format for error messages to improve clarity - Remove V1 profile support - IMS CLI extension is archived A comprehensive list of breaking changes made to Zowe CLI and the Zowe Client Node.js SDKs in V3 is available [here]( **Pre-release availability** - V3 pre-release versions are available via [npm]( under the 'next' tag.
**Important Updates** - The Explorer for Intellij is part of the Core. - Work with USS Files - Work with Data Sets - Work with JES Working Sets - Interactive TSO Console
**Breaking changes** - Remove V1 profile support - Remove deprecated items - [Explorer for VSCode]( - Store extension settings in the local storage A comprehensive list of breaking changes made to Zowe Explorer for VS Code in V3 is available [here]( **Important updates** - Store persistent settings in local storage - Compare files in MVS view, the USS view and across the two views **Pre-release availability** - V3 pre-release versions are available via [GitHub releases]( or via the [Open VSX Registry](
**Breaking changes** - Drop the original V2 configuration management, `zowe.useConfigmgr=false`. (Configuration Manager remains as the only supported method of configuring Zowe) **Important updates** - Remove dependency on Node.js for configuration - Introduce ZEN to simplify configuration via UI
**Breaking changes** - Run by default in 64 bit mode, `components.zss.agent.64bit=true`. 31-bit plugins cannot run in 64-bit ZSS, so you need to compile your plugins for the version of ZSS to be used. Only 1 version of ZSS can run at a time.

Changes to the Conformance Criteria (For Extenders)

The final version of V2 Conformance Criteria is published here. Each of the section links to th PDF for the specific criteria.

Zowe API Mediation Layer
The API Mediation Layer related conformance Criteria are [here](
Zowe CLI
The CLI related conformance Criteria are [here](
Zowe Explorer
The Explorer related conformance Criteria are [here](
Zowe Application Framework
The Application Framework related conformance Criteria are [here](
Support Providers
The Support providers related conformance Criteria are [here](

Office Hours

Check out the OMP Calendar for specific time of the V2 office hours.

Consumer Focused Office Hours

Date Topic Link to the meeting Link to the recording Links to the materials
09/06/2024 8AM - 9AM ET Web UI
09/13/2024 8AM - 9AM ET API Mediation Layer
09/20/2024 8AM - 9AM ET CLI & Client Node SDK
09/27/2024 8AM - 9AM ET Explorer (VS Code)
10/04/2024 8AM - 9AM ET Explorer (Intellij)
10/11/2024 8AM - 9AM ET Systems, Install & Packaging
10/18/2024 8AM - 9AM ET Open Office Hours
01/05/2024 8AM - 9AM ET API Mediation Layer Zoom recording Presentation
01/12/2024 8AM - 9AM ET CLI Zoom recording Presentation
01/12/2024 8AM - 9AM ET Node Client SDK Zoom recording Presentation
01/19/2024 8AM - 9AM ET Explorer (VSCode) Zoom recording Presentation
01/26/2024 8AM - 9AM ET Explorer (Intellij) Zoom recording Presentation
02/02/2024 8AM - 9AM ET Web UI Zoom recording Presentation
02/09/2024 8AM - 9AM ET Systems Install & Packaging Zoom recording Presentation

Extender Focused Office Hours

Date Topic Link to the meeting Link to the recording Links to the materials
11/10/2023 8AM - 9AM ET Other SYSTEMS Installation & Packaging & z/OS Zoom recording Presentation
11/03/2023 8AM - 9AM ET Web UI Zoom recording Presentation
10/20/2023 8AM - 9AM ET Explorer (VS Code) Zoom recording Presentation
10/13/2023 8AM - 9AM ET CLI Zoom recording Presentation
10/06/2023 8AM - 9AM ET API Mediation Layer Zoom recording Presentation

Frequently Asked Questions

The current plan is to have Zowe V3 for all projects available as preview by the December 2023

Frequently Asked Questions - Extenders Focused

No, we don't intend to remove the support, but it would be good to figure out some plan to move of them as setting up of passticket configuration shifts the burden to the user's side who need to properly configure the passtickets on their system for every service using them.
We intend to move the configuration for V3 to the currently used gateway configuration space e.g. zowe.components.gateway therefore the configuration that was Zuul specific will be removed and the one that is Spring Cloud Gateway will be added to this space.
The northbound authentication works by accepting the client certificates. The API Mediation Layer then transforms the client certificate to another method of authentication such as JWT token or SAF IDT or passtickets and these needs to be accepted by the southbound services. We currently don't authenticate with client certificate towards the z/OSMF but it's a possibility for future.
The plan is to do so, we just don't know yet how exactly will we do that.
The bypass scheme remains and you still can claim conformance for services that provides only public endpoints that doesn't require authentication.
Yes. Java 17 is required to run the API Mediation Layer in Zowe V3.
Yes, unlike the support for the V1 profiles.
Yes, unless they are among the dropped ones in these lists [CLI]( and [Imperative](
No, it is not possible right now. It is possible to run just one type of plugins as there is the possibility to run only one ZSS.
Angular 16 is most up-to-date. Webpack 5 is most up to date.
It is possible for the Desktop extensions to bring in different versions of React as the desktop is compatible with React but not built on top of React.
ZEN is running on laptop/desktop and connects to z/OS via standard methods.
You will be guided through the different set of pages that relate to the SMP/E installation.
It is a different topic and it is not linked other than by sharing the zwe commands.
No, it is focused on the server side extensions.
Zowe provides the SBOMs with V3 in updated SPDX Formats.

Frequently Asked Questions - Users Focused

The API ML in version 3 supports clients with onboarding enablers from version 2. It also works the other way around the onboarding enablers from version 3 will continue working with Zowe v2
Plain Java Enabler in v2 will work in v3 - you can keep this for 1 - 2 years Using Spring Boot, Java 17 requirement comes from SPRING, recommendation is to MOVE if you are using something from SPRING
The goal is to have one: spring-cloud gateway. The spring-cloud-gateway configuration should move under the component.gateway namespace. We expect to have one cluster od spring cloud gateway ahead of multiple sysplexes and then one cluster on every sysplex. Most of the configuration that was used should remain, new one from Spring Cloud Gateway remains.
It is gone in V3, but nothing should change from the point of view of the user… if we discover that is not true we will plan to deliver a configuration utility to help with this transition
Since one service can have multiple instances, living on different LPARS or different Environments how can clients identify a specific service on a specific system? TODAY - Clients can use the header instance ID to route to a specific instance / get information from specific services via an API on discovery service, but this part is going to be improved in 2Q 2024
It isn't now, but we will work on this functionality in 2Q 2024
It will remain available. The recommendation is through the V3 to move the directory away from Zowe workspace, if it isn't away by now. The zowe.yaml contains parameter specifying where the static definitions directories live components.discovery.alternativeStaticApiDefinitionsDirectories

Older Versions

Are you looking for page with details for the V2 version of Zowe? The page is available here.