ZD&T licensing: a product in transition.

IBM Z Development and Test Environment (ZD&T) lets teams run a real z/OS instance on x86 hardware through emulation, so developers and testers can build and validate mainframe applications without consuming capacity on a production Z machine. It ships in editions aimed at different uses: a Personal Edition for a single developer on a laptop or workstation, and an Enterprise Edition for shared, server based development and test. Because it executes z/OS off the frame, its entire licensing model sits outside the MLC and MSU world that governs everything running on a real mainframe.

ZD&T is not an MLC or MSU product, because there is no Z machine and no SCRT report behind it. It is licensed off platform by edition and by capacity or authorized users. The Personal Edition is typically licensed for a single developer install on dedicated hardware, while the Enterprise Edition is licensed for shared and server use, commonly on a Resource Value Unit (RVU) or authorized user basis. The metric and edition you hold determine both your cost and your compliance surface, and they look nothing like the peak driven charges on the production frame, so they need to be read on their own terms.

Status note: IBM also announced it will stop marketing the underlying System z Personal Development Tool (zPDT) as a standalone offering at the end of 2025, with support ending at the end of 2026, and has been steering workloads toward cloud hosted options such as IBM Wazi as a Service. Verify the current position for your entitlement before acting.

The cost drivers for ZD&T are unlike anything on the production frame. The first is the edition and the user or capacity count, since the Enterprise Edition scales with developers and server footprint rather than with a workload peak. The second is sprawl: development and test instances multiply quietly, and idle or forgotten installs keep counting against your entitlement. The third, and now the dominant one, is the product transition itself, because a withdrawn version and a sunsetting emulation base mean that the real cost question is no longer this year's renewal but whether to stay on the current model at all or move development and test to a cloud hosted alternative.

Development and test licensing is loosely governed in many shops, which is exactly where exposure builds. Common traps we see at pattern level:

With the product line in transition, the levers are about the platform decision and right sizing as much as price. The five that pay:

ZD&T is one of the few mainframe products where the alternative is not just credible but increasingly the direction IBM itself points. Cloud hosted development and test, through IBM Wazi as a Service or a hosted on demand z/OS program, removes the local x86 footprint and the install sprawl that drives ZD&T cost, and shifts to a consumption or subscription model. There are also third party and on premises emulation options in the broader market. None of these is automatically cheaper, and a migration carries setup, retraining, and integration work, so the right move is to cost the alternatives against your actual development and test demand and let the numbers, not the deadline, decide.