Use this page to identify all compatibilities for a given Broadcom product. If maintenance is required:

• A PTF section link appears under compatibility status.
• Use FIXCAT HOLDDATA to aid in identifying maintenance required to support a particular hardware device, software, or function.
• If found, click on the additional information link that appears under the compatibility status.

Launch Mainframe Compatibility Main Page

Other Mainframe Quick Links:

Product Lifecycle Search

The 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.

IBM zEnterprise Compatibility Matrix

Compatibility/Release	1.1
No product found.
ZEC12	YES Info
z13/z13s	YES Info
z14/z14R1	YES
z15/z15-T02	YES
z16/z16-A02	YES

TLS Compatibility Matrix

Compatibility/Release	1.1
No product found.
TLS V1R2	TBD
TLS V1R3	TBD

VPAT Compatibility Matrix

Compatibility/Release	1.1
No product found.
VPAT	TBD

z/OS Compatibility Matrix

Compatibility/Release	1.1
No product found.
Z/OS V2R4	YES
z/OS V2R5	YES
Z/OS V3R1	TBD

Additional Information

• No information found.

• Fix Category: CA.Device.Server.zEC12-2827

   z/OS 2.1, 1.13, 1.12 are supported with CA 7/Smart Console Option        
   release 1.1 genlevel 9808 with LO51334, QO85885, and                     
   QO85889 and RO12125 applied.                                             
  
   HARDWARE/DEVICE COMPATIBILITY:                                           
   There are no known incompatibilities for CA 7/Smart Console Option       
   with z/OS 2.1, 1.13, and 1.12.                                           
  
   SPECIAL INSTRUCTIONS/NOTES:                                              
   Possible workarounds include using NIP messages that appear later        
   in the IPL Lprocess, this may be different for each implementation.      
  
   Starting with z/OS 1.9, the default for ALLOWUSERKEYCSA has changed      
   from YES to NO.  During initialization of CA 7/Smart Console, the        
   following abend will occur:                                              
  
       IEA705I ERROR DURING GETMAIN SYS CODE = B78-5C                       
  
   In order to run CA 7/Smart Console, you will need to specify             
   VSM ALLOWUSERKEYCSA(YES) in your SYS1.PARMLIB(DIAGnn) member.            
  
   You can switch to ALLOWUSERKEYCSA(YES) dynamically if you have           
   another DIAGnn member in SYS1.PARMLIB. To switch, you would enter        
   the following MVS command:                                               
       SET DIAG=yy            (yy is the suffix of the new DIAG member)     
      

• Fix Category: CA.Device.Server.z13-2964

   z/OS 2.1, 1.13, 1.12 are supported with CA 7/Smart Console Option        
   release 1.1 genlevel 9808 with LO51334, QO85885, and                     
   QO85889 and RO12125 applied.                                             
  
   HARDWARE/DEVICE COMPATIBILITY:                                           
   There are no known incompatibilities for CA 7/Smart Console Option       
   with z/OS 2.1, 1.13, and 1.12.                                           
  
   SPECIAL INSTRUCTIONS/NOTES:                                              
   Possible workarounds include using NIP messages that appear later        
   in the IPL Lprocess, this may be different for each implementation.      
  
   Starting with z/OS 1.9, the default for ALLOWUSERKEYCSA has changed      
   from YES to NO.  During initialization of CA 7/Smart Console, the        
   following abend will occur:                                              
  
       IEA705I ERROR DURING GETMAIN SYS CODE = B78-5C                       
  
   In order to run CA 7/Smart Console, you will need to specify             
   VSM ALLOWUSERKEYCSA(YES) in your SYS1.PARMLIB(DIAGnn) member.            
  
   You can switch to ALLOWUSERKEYCSA(YES) dynamically if you have           
   another DIAGnn member in SYS1.PARMLIB. To switch, you would enter        
   the following MVS command:                                               
       SET DIAG=yy            (yy is the suffix of the new DIAG member)     
      

This page last updated 21 Dec 2024