Zowe has both server and client components, which you can install independently. Download the latest installer to install Zowe on the z/OS server, on your computer, or both. Start your journey with Zowe today!
Install Zowe z/OS components from the convenience build, the SMP/E build, the PSWI build or the containerization build depending on your need.
PAX archive format installed on the z/OS server
SMP/E format installed on the z/OS server
Download the base FMID AZWE002 (based on v2.0.0) first and then apply the PTFs to get the latest version.
The Zowe Portable Software Instance (PSWI) is a new way of z/OS component distribution. The PSWI allows the full installation as you are used to from SMP/E build, but it uses the new standard for mainframe software distribution.
Download the PSWI based on FMID AZWE002
Files to launch Zowe in a container environment like Kubernetes
Install Zowe CLI or Zowe Explorer, a Visual Studio Code extension powered by Zowe CLI.
Install Zowe CLI from the local package or from an npm registry if your computer is connected to the Internet.
Download the Zowe CLI core package and optionally download the plug-ins (CICS, Db2, IMS, MQ, z/OS FTP, and so on) to gain more capabilities.
Download the Zowe Software Development Kits (SDKs) for use in development and automation.
Zowe Explorer V2 enables you to adopt the team configuration file, recently developed by the Zowe CLI Squad, to make profile management more centralized and much simpler.
To download the V2 version of the FTP extension, click Zowe Explorer 2.2.0. Separate downloads are available for Zowe Explorer and Zowe Explorer Extension for FTP.
To install the .vsix files, use Extensions > Install from vsix within VS Code.
Install Zowe z/OS components from the convenience build, the SMP/E build or the containerization build depending on your need.
You can also optionally use the Docker build technical preview to run a subset of the Zowe server-side components outside z/OS. Download and learn more about the build in the technical preview section.
PAX archive format installed on the z/OS server
SMP/E format installed on the z/OS server
Download the base FMID AZWE001 (based on v1.9.0) first and then apply the PTFs to get the latest version.
Files to launch Zowe in a container environment like Kubernetes
Install Zowe CLI or Zowe Explorer, a Visual Studio Code extension powered by Zowe CLI.
Install Zowe CLI from the local package or from an npm registry if your computer is connected to the Internet.
Download the Zowe CLI core package and optionally download the plug-ins (CICS, Db2, IMS, MQ, z/OS FTP, and so on) to gain more capabilities.
Download the Zowe Software Development Kits (SDKs) for use in development and automation.
Installed directly to VSCode within the GUI
Test the latest Zowe features and provide feedback. Technical previews are for testing only and not ready for production.
The Zowe Docker build enables you to run a subset of the Zowe server-side components outside z/OS. The Docker build runs in combination with the convenience or S MP/E build. Learn more about the relationship of the builds in the docs.
You can download the build directly via the tarball, or as a cloud download from Docker Hub. Separate downloads exist for z/Linux ("s390x") and other Linux ("amd64" for intel & amd systems).
Download releases of Zowe V2.x by version number.
| Zowe 2.2.0 (2022-07-25) | z/OS Convenience build | SMP/E PTF UO02049 UO02050 | CLI Core | CLI Plug-ins | Documentation |
| Zowe 2.1.0 (2022-06-13) | z/OS Convenience build | SMP/E PTF UO02047 UO02048 | CLI Core | CLI Plug-ins | Documentation |
| Zowe 2.0.0 (2022-04-27) | z/OS Convenience build | SMP/E FMID AZWE002 | CLI Core | CLI Plug-ins | Documentation |
Download releases of Zowe V1.x by version number.
Zowe version 1.0.0 through 1.8.0 are only available as rollup convenience builds. Zowe version 1.9.0 is the beginning of the Active Long-Term Support (LTS) release and it provides an SMP/E build with an FMID of AZWE001. The SMP/E build is the same content as the Zowe 1.9.0 convenience build. Updates in subsequent releases are made available as co-requisite PTFs as well as in convenience builds. Also, starting in 1.9.0, Zowe CLI core and plug-in packages are distributed separately.
All builds prior to Zowe v1.0.0 are no longer available.
Version timeframe, Active , Maintenance
Zowe v1 conformant extensions / plug-ins are not guaranteed to be compatible with Zowe v2 and therefore may not be operable. In general, plug-ins/extensions which leverage v2 APIs that have known “breaking changes” are at high risk of incompatibility and unpredictable results.
Recommendation: ALL v1 extenders test with the Zowe v2, identify any issues, and disclose results to consumers to clearly indicate backward compatibility status in the extension documentation. If unable to test, clearly document as such.
Zowe v2 conformant (planning to earn conformance) extensions / plug-ins are not guaranteed to be compatible with Zowe v1 LTS. In general, plug-ins / extensions with no known dependency on any newly introduced Zowe v2 functions are at minimum risk.
Recommendation: All v2 extenders test with Zowe v1 LTS, identify any issues, and disclose results to consumers to clearly indicate forward compatibility status in the extension documentation. If unable to test, clearly document as such.
Zowe v1 conformant extensions / plug-ins are likely to require changes to meet Zowe v2 conformance criteria. All extensions (regardless of v1 conformance status) must apply for v2 conformance and satisfy all required v2 testing criteria.
Recommendation: All extenders interested in earning v2 conformance review the v2 conformance criteria, determine if technical changes are necessary, make appropriate modifications and prepare to apply for v2 conformance prior to v2 LTS publication.
Zowe v2 Availability to ExtendersSeveral pre-GA releases of Zowe v2 will be made available to Zowe extenders and the general public prior* to the actual Zowe v2 GA release delivery to allow extenders time to perform Zowe v2 testing with their extensions and disclose their compatibility status. (*dates to-be-determined)
Early Access Conformance CriteriaThe Zowe v2 conformance criteria for all extensions/plugins participating in the conformance program will be made available to all Zowe v1 conformant extenders prior* to the Zowe v2 GA release to give extenders time to adapt to applicable changes. (*dates to-be-determined) Note: See Zowe Support Provider conformance section below for details on v2 Support Provider conformance.
More InformationVisit the Zowe v2 release page at https://zowe.org/vNext.html for comprehensive information related to the V2 release.
Visit the Zowe Artifactory nightly build folder to find the most recent build.
Please note: