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 | 4.5 |
---|---|
ZEC12 |
YES |
z13/z13s |
YES |
z14/z14R1 |
YES |
z15/z15-T02 |
YES |
z16/z16-A02 |
YES |
Compatibility/Release | 4.5 |
---|---|
VPAT |
TBD |
Compatibility/Release | 4.5 |
---|---|
Z/OS V2R4 |
YES |
z/OS V2R5 |
YES
Info |
Z/OS V3R1 |
YES
Info |
Fix Category: CA.TargetSystem-RequiredService.z/OS.V2R5
CREWS requires the use of the system DIAG trap STGINIT(00) for proper operation. If STGINIT(FF) is set, some programs will abend with code S001-4 when writing output to SYSPRINT. If any other value of STGINIT is used, or if STGINIT(xx) is not specified, results are unpredictable. Note that this is not specific to z/OS 2.5 and may occur on earlier releases of the operating system.
Fix Category: CA.TargetSystem-RequiredService.z/OS.V3R1
CREWS requires the use of the system DIAG trap STGINIT(00) for proper operation. If STGINIT(FF) is set, some programs will abend with code S001-4 when writing output to SYSPRINT. If any other value of STGINIT is used, or if STGINIT(xx) is not specified, results are unpredictable. Note that this is not specific to z/OS 3.1 and may occur on earlier releases of the operating system.
This page last updated 17 Dec 2024