Compatibilities
Product Lifecycle
Fixcat Holddata
Use this page to identify all compatibilities for a given Broadcom product. If maintenance is required:
Launch Mainframe Compatibility Main Page
Other Mainframe Quick Links: Product Lifecycle SearchThe compatibility status for each category are defined as follows:
| TBD | Broadcom is in the process of verifying that the product is compatible. |
| NO | The product is not compatible. |
| YES | The product has been certified and is compatible. |
| N/A | The compatibility is not applicable to the Broadcom product. |
| Compatibility/Release | 11.4 | 12.0 |
|---|---|---|
| JAVA 8 |
YES | |
| JAVA 11 |
YES | |
| JAVA 17 |
YES |
| Compatibility/Release | 11.4 | 12.0 |
|---|---|---|
| JES3+ V1R0 |
YES | YES |
| JES3+ V1R1 |
YES | YES |
| JES3+ V1R2 |
NO | YES |
| JES3+ V1R3 |
NO | YES |
| JES3+ V1R4 |
NO | YES |
| Compatibility/Release | 11.4 | 12.0 |
|---|---|---|
| MFA |
N/A | YES
Info |
| Compatibility/Release | 11.4 | 12.0 |
|---|---|---|
| PCI DSS V3.2 |
NO |
| Compatibility/Release | 11.4 | 12.0 |
|---|---|---|
| PE Z/OS |
TBD
Info |
TBD
Info |
| Compatibility/Release | 11.4 | 12.0 |
|---|---|---|
| ZEC12 |
YES | YES |
| z13/z13s |
YES | YES |
| z14/z14R1 |
YES | YES |
| z15/z15-T02 |
YES | YES |
| z16/z16-A02 |
NO | YES |
| Compatibility/Release | 11.4 | 12.0 |
|---|---|---|
| TLS V1R2 |
YES | YES |
| TLS V1R3 |
YES | YES |
| Compatibility/Release | 11.4 | 12.0 |
|---|---|---|
| VPAT |
TBD | TBD |
| Compatibility/Release | 11.4 | 12.0 |
|---|---|---|
| Z/OS V2R4 |
YES
PTFs |
YES
PTFs |
| z/OS V2R5 |
YES | YES |
| Z/OS V3R1 |
N/A | YES |
Fix Category: CA.Function.Multi-FactorAuthentication
ESP REST API - YES
Intelligent Experience - YES
ESP Workstation - YES
Workload Agent Manager - YES
AAI Integration - N/A
Report Server - N/A
Fix Category: CA.Function.Pervasive.Encryption.z/OS
Most of operational ESP data sets could be encrypted without changing
ESP configuration. The only exception is the following ESP operational
data sets and related utilities:
APPLFILE
CKPT
EXH
NETQUEUE
QUEUE
TRAKFILE
ESP uses EXCP access method for them, and EXCP cannot be used for
encrypted data sets. Therefore those data sets should not be
encrypted.
Fix Category: CA.Function.Pervasive.Encryption.z/OS
Most of operational ESP data sets could be encrypted without changing
ESP configuration. The only exception is the following ESP operational
data sets and related utilities:
APPLFILE
CKPT
EXH
NETQUEUE
QUEUE
TRAKFILE
ESP uses EXCP access method for them, and EXCP cannot be used for
encrypted data sets. Therefore those data sets should not be
encrypted.