Can ALL Broadcom products be managed within a single SMP/E "Broadcom Global CSI"

Products

• ACF2 - z/OS

Issue/Introduction

The question is, can ALL Broadcom products be managed within a single "Broadcom Global CSI.  Something like, SMPE.BROADCOM.GLOBAL.CSI, and each product would have its own Target and Distribution zone within that global CSI.

Something like

TACFR14/DACFR14 - TACFR15/DACFR15 - TACFR16/DACFR16

TCA1R10/DCA1R14

 

Environment

Release : 16.0

Component : ACF2 for z/OS

Resolution

Yes in general sites can install Broadcom products a single "Broadcom Global CSI as long as the products are installed in separate target zones within the same CSI. However there are some considerations and recommendations that sites should be aware of, for example: 

It is recommended that Broadcom COMMON SERVICES be installed into separate SMP/E libraries. It is recommended to keep CCS390 separate and allow easier fallback to a previous release if necessary. Broadcom COMMON SERVICES has a huge impact on a system processing, because every Broadcom Solution depends on it In addition, what if something goes wrong with a product, and compromises the entire CSI. Broadcom COMMON SERVICES must always be kept intact.

Also for site that install both ACF2 and Top Secret(although only ACF2 or Top Secret can be active at one time in an lpar), sites should not share the same target and distribution zones when ACF2 and Top Secret are at the same release level. Even though the SAF FMID and modules are the same, the internal code has differences specific to each security product (ACF2 and Top Secret), so sites should not share the same zones.