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 | 6.0 |
---|---|
COBOL V4R2 |
YES |
COBOL V5R1 |
YES |
COBOL V5R2 |
YES |
COBOL V6R1 |
YES |
COBOL V6R2 |
YES |
COBOL V6R3 |
YES |
COBOL V6R4 |
YES |
Compatibility/Release | 6.0 |
---|---|
Db2 V11 |
YES
PTFs Info |
Db2 V12 |
YES
Info |
Db2 V13 |
YES
Info |
Compatibility/Release | 6.0 |
---|---|
ZEC12 |
YES
Info |
z13/z13s |
YES
Info |
z14/z14R1 |
YES |
z15/z15-T02 |
YES |
z16/z16-A02 |
YES |
Compatibility/Release | 6.0 |
---|---|
VPAT |
TBD |
Compatibility/Release | 6.0 |
---|---|
Z/OS V2R4 |
YES
PTFs Info |
z/OS V2R5 |
YES
Info |
Z/OS V3R1 |
YES
Info |
Fix Category: CA.TargetSystem-RequiredService.DB2.V11
DB2 11 NFM and CM modes are supported with VISION:Results release 6.0 use of the COPYDB2 feature. APAR RO61720 is required. Data types that are currently supported are documented in the 4.0 VISION:Interface for DB2 with VISION:Results Reference Guide Release pages 6-7 and 6-8. Examples of new, unsupported types include, but are not limited to, BIGINT, XML, and LOB (large objects).sults with DB2 11.
Fix Category: CA.TargetSystem-RequiredService.DB2.V12
DB2 12 NFM and CM modes are supported with VISION:Results release 6.0 use of the COPYDB2 feature. APAR RO61720 is required. Data types that are currently supported are documented in the 4.0 VISION:Interface for DB2 with VISION:Results Reference Guide Release pages 6-7 and 6-8. Examples of new, unsupported types include, but are not limited to, BIGINT, XML, and LOB (large objects).sults with DB2 12.
Fix Category: CA.TargetSystem-RequiredService.DB2.V13
All jobs currently using DB2 require both SDSNLOAD and SDSNEXIT to be part of the STEPLIB and/or JOBLIB if they are not in the LINKLIST. Creating multiple tables in a tablespace will cause a SQLCODE -646 on the second create table. ReBIND packages with the APPLCOMPAT(V12R1M503) parameter and it will allow mutliple tables in a tablespace.
Fix Category: CA.Device.Server.zEC12-2827
The following APARs are required: APAR QO92631 ( S0C2 ABEND UNDER Z/OS 1.9 ) APAR RO05111 ( SC03 ABEND USING PDS PROCESSING DURING A RESTORE ) APAR RO55926 ("UNINITIALIZED OBTAINED STORAGE RESULTS IN ABENDS") APAR RO64756 ( U0299 S0C1 IN FVPF )
Fix Category: CA.Device.Server.z13-2964
The following APARs are required: APAR QO92631 ( S0C2 ABEND UNDER Z/OS 1.9 ) APAR RO05111 ( SC03 ABEND USING PDS PROCESSING DURING A RESTORE ) APAR RO55926 ("UNINITIALIZED OBTAINED STORAGE RESULTS IN ABENDS") APAR RO64756 ( U0299 S0C1 IN FVPF )
Fix Category: CA.TargetSystem-RequiredService.z/OS.V2R4
The following APARs are required: APAR QO92631 ( S0C2 ABEND UNDER Z/OS 1.9 ) APAR RO05111 ( SC03 ABEND USING PDS PROCESSING DURING A RESTORE ) APAR RO55926 ("UNINITIALIZED OBTAINED STORAGE RESULTS IN ABENDS") APAR RO64756 ( U0299 S0C1 IN FVPF )
Fix Category: CA.TargetSystem-RequiredService.z/OS.V2R5
The following APARs are required: APAR QO92631 ( S0C2 ABEND UNDER Z/OS 1.9 ) APAR RO05111 ( SC03 ABEND USING PDS PROCESSING DURING A RESTORE ) APAR RO55926 ("UNINITIALIZED OBTAINED STORAGE RESULTS IN ABENDS") APAR RO64756 ( U0299 S0C1 IN FVPF )
Fix Category: CA.TargetSystem-RequiredService.z/OS.V3R1
The following PTF needs to be installed: LU12806 (PTFs source fixed. Changed SMPE to object module replacement)
This page last updated 21 Dec 2024