Skip to main content

How do Zowe and z/OSMF Relate?

IBM Senior Technical Staff Member Gary Puchkoff on how Zowe and z/OSMF relate to one another.

Green box with white outline of a speech bubble that contains the words "Ask the Expert" in capital letters


Q: How do Zowe and z/OSMF relate to one another?

I’m often asked how Zowe and z/OSMF are related. To start, z/OSMF is a component of z/OS* for versions 2.2 and up. It’s designed to be configured and running in one instance in every Sysplex that you run. And even if you run a single system rather than a Sysplex, we would still expect to have z/OSMF running in there. z/OSMF provides both APIs and JavaScript* technology-based applications that are in direct support of the z/OS OS. Starting with z/OS 2.3, some z/OS components depend on z/OSMF capabilities like cloud provisioning and management. The OS has future work dependent on z/OSMF as well.

Zowe is an open-source framework for both APIs and JavaScript applications, and it’s designed to leverage z/OSMF services. It exposes z/OSMF REST APIs for jobs, datasets, files and consoles as well as our workflows, and Zowe is dependent on z/OSMF to do this. These are capabilities that we ship with the OS, but Zowe’s capabilities are a step above that—providing added value from IBM and other vendors beyond what the OS delivers.

We’re currently developing direct support enhancements for Zowe in z/OSMF. One of these enhancements is to the open API specification (sometimes known as Swagger documentation) for all of our public REST services. We’re also adding enhancements to the configuration of z/OSMF to make it even easier to install for Zowe users. In addition, we’re looking at JSON Web Token support for security to make it easier for z/OSMF and Zowe to interoperate with one another. We may do even more to make it easier for z/OSMF to interoperate with Zowe in the future, but we’re waiting for the technology to mature a bit more.

Delivering the latest technical information to your inbox.