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 | 15.0 | 15.1 |
---|---|---|
CA CCS V15.0 |
YES |
Compatibility/Release | 15.0 | 15.1 |
---|---|---|
JAVA 8 |
YES | NO |
JAVA 11 |
YES | YES |
JAVA 17 |
YES | YES |
Compatibility/Release | 15.0 | 15.1 |
---|---|---|
PE Z/OS |
YES
Info |
YES
Info |
Compatibility/Release | 15.0 | 15.1 |
---|---|---|
ZEC12 |
YES | YES |
z13/z13s |
YES | YES |
z14/z14R1 |
YES | YES |
z15/z15-T02 |
YES | YES |
z16/z16-A02 |
YES | YES |
z17 |
NO | YES |
Compatibility/Release | 15.0 | 15.1 |
---|---|---|
TLS V1R2 |
TBD | YES |
TLS V1R3 |
TBD | YES |
Compatibility/Release | 15.0 | 15.1 |
---|---|---|
VPAT |
TBD | TBD |
Compatibility/Release | 15.0 | 15.1 |
---|---|---|
Z/OS V2R4 |
YES | YES |
z/OS V2R5 |
YES | YES |
Z/OS V3R1 |
YES | YES |
Fix Category: CA.Function.Pervasive.Encryption.z/OS
CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the 00000100 box for externally created user data files such as DBUTLTY BACKUPs and 00000200 EXTRACTs. For user data stored within the databases, we recommend 00000300 using the built-in Datacom encryption capabilities which exploit the 00000400 available crypto co-processors. For complete implementation recommen- 00000500 dations, see CA Datacom documentation or contact the CA Datacom support 00000600 team. 00000700
Fix Category: CA.Function.Pervasive.Encryption.z/OS
Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the 00000100 box for externally created user data files such as DBUTLTY BACKUPs and 00000200 EXTRACTs. For user data stored within the databases, we recommend 00000300 using the built-in Datacom encryption capabilities which exploit the 00000400 available crypto co-processors. For complete implementation recommen- 00000500 dations, see Datacom documentation or contact the Datacom support 00000600 team. 00000700 00000800