Identifying server requirements
At the time of publication, z/OS 3.2 is supported on the
following IBM® Z servers:
IBM
z17® — All models, including ME1 (machine type 9175)
- IBM z16® — All models, including A01 (machine type 3931) and A02 (machine type 3932)
- IBM z15® — All models, including T01 (machine type 8561) and T02 (machine type 8562)

z/OS® uses particular machine facilities on these servers, depending on the z/OS release. Table 1 lists the machine facilities that are required for each release of z/OS. A program that runs on a particular z/OS release can use the facilities that are identified for that release. These facilities cannot be disabled on the z/OS system, for example, by using the LOADxx MACHMIG statement (as described in z/OS MVS Initialization and Tuning Reference).
Though additional machine facilities might be available on a server, it does not mean that z/OS supports those facilities. Usage of any machine facilities that are not listed in Table 1 should be investigated by your program developer to ensure that the facility is supported by the z/OS release, server level, and operating environments, such as zPDT® and z/VM®, if z/OS is run as a guest. For your reference, Table 1 includes earlier releases of z/OS to help show a progression of required machine facilities over time.
Notice that Table 1 lists the STFLE bit for a particular facility. The STFLE bit is a machine instruction that indicates which facilities are installed. Its results are mapped in the IHAFACL macro.
| z/OS release level | Minimum required z/VM level for that z/OS release | Minimum server level | Exploitable machine facilities |
|---|---|---|---|
| z/OS V2R1 | z/VM 6.2, at z/OS V2R1 general availability. Increased to z/VM 6.4 on 31 December 2016, due to the end of service date. |
Z9 EC or z9® BC | Base z/Architecture® mode, plus the following
extensions (by STFLE bit):
|
| z/OS V2R2 | z/VM 6.3, at z/OS V2R2 general availability. Increased to z/VM 6.4 on 31 December 2017, due to the end of service date. |
Z10 EC or z10 BC | All previously required machine facilities, plus the following extensions (by STFLE bit):
|
| z/OS V2R3 | z/VM 6.3, at z/OS V2R3 general availability. Increased to z/VM 6.4 on 31 December 2017, due to the end of service date. |
zEC12 or zBC12 | All previously required machine facilities, plus the following extensions (by STFLE bit):
|
| z/OS V2R4 | z/VM 6.4, at z/OS V2R4 general availability. | zEC12 or zBC12 | All previously required machine facilities, plus the following extensions (by STFLE bit):
|
| z/OS V2R5 | z/VM 7.1, at z/OS V2R5 general availability. | z13 or z13s | All previously required machine facilities, plus the following extensions (by STFLE bit):
|
| z/OS 3.1 | z/VM 7.2, at z/OS 3.1 general availability. | z14 or z14s | All previously required machine facilities, plus the following extensions (by STFLE bit):
|
z/OS 3.2
![]() |
z/VM 7.2, at z/OS 3.1 general availability.![]() |
z15![]() |
All previously required machine facilities, plus the following extensions (by STFLE bit):
![]() |
Processor configurations by z/OS release
The IBM
z17 (machine type 9175) has one model: the ME1, with five
feature codes to represent the processor capacity. The feature codes are Max43, Max90, Max136,
Max183, and Max208 with (respectively) 43, 90, 136, 183, and 208 processors. This system is
configurable as a one-to-four 19-inch frame system.
When running on the IBM
z17, z/OS releases
3.2,
3.1, 2.5, and 2.4 can support up to 208 processors, which are configurable as general-purpose
processors (CPs), ICFs, zIIPs, IFLs, or standard SAPs. The sum of CPs and zIIPs configured in a
single z/OS LPAR cannot exceed: - 208 per z/OS LPAR in non-SMT mode
- 128 cores / 256 threads per z/OS LPAR in SMT mode.

- Machine type 3931 (Model A01), with five feature codes to represent the processor capacity. The feature codes are 0667, 0668, 0668, 0669, and 0670 with (respectively) 39, 82, 125, 168, and 200 processors. This system is configurable as a one-to-four 19-inch frame system.
- Machine type 3932 (Model A02 or AGZ), with four feature codes to represent the processor capacity. The feature codes are 0672, 0673, 0674, and 0675 with (respectively) 5, 16, 32, and 68 processors. This system is configurable as a single-frame or rack-mount system.
3.2,
3.1, 2.5, 2.4, 2.3, and 2.2 can support up to 200 processors, which are
configurable as general-purpose processors (CPs), ICFs, zIIPs, IFLs, or optional SAPs. The sum of
CPs and zIIPs configured in a single z/OS LPAR cannot exceed: - 200 on z/OS 2.2 or later in non-SMT mode.
- 128 cores / 256 threads on z/OS 2.2 or later in SMT mode.
- Up to 68 processors configurable as CPs, zIIPs, IFLs, ICFs, or optional SAPs.
- The sum of CPs and zIIPs configured in a single z/OS LPAR cannot exceed 68 on z/OS 2.2 or later (in either SMT or non-SMT mode).
- Model T01 (machine type 8561), with five feature codes to represent the processor capacity. The feature codes are Max34, Max71, Max108, Max145, and Max190 with (respectively) 34, 71, 108, 145, and 190. This system is configurable as a one-to-four 19-inch frames system.
- Model T02 (machine type 8562), with five CPC size features (one or two drawers). The system is configurable as a 19-inch frame system.
3.2,
3.1, 2.5, 2.4, 2.3, 2.2, and 2.1
support up to 190 processors, which are configurable as general-purpose processors (CPs), zIIPs,
IFLs, ICFs, or optional SAPs. The sum of CPs and zIIPs configured in a single z/OS LPAR cannot
exceed: - 190 on z/OS 2.1 or later in non-SMT mode
- 128 on z/OS 2.1 or later in SMT mode.
For the IBM z15 model T02 (machine type 8562), the z/OS
releases
3.2,
3.1, 2.5, 2.4, 2.3, 2.2, and 2.1 support
up to 65 processors, which are configurable as CPs, zIIPs, IFLs, ICFs, or optional SAPs. The sum of
CPs and zIIPs configured in a single z/OS LPAR cannot exceed 65 on z/OS 2.1 or later (in either SMT
or non-SMT mode).
- The
IBM
z17
, IBM
z16, IBM
z15, servers do not support the IBM
zEnterprise® Application Assist Processor (zAAP). - The Coupling Facility level (CFLEVEL) has hardware and software requirements. For more information, see Coupling Facility Level (CFLEVEL) Considerations.