Do you have to share the USS file system for Chorus Security and Compliance?

Document ID : KB000011884
Last Modified Date : 14/02/2018
Show Technical Document Details

In the manual CA Chorus for Security and Compliance Management Site Preparation Guide on page 19 it shows a multiple lpar architecture. The Chorus Application Server, which resides in USS, appears to be the common communication vehicle between the lpars. Does this mean that the USS file system must be shared between all lpars that have compliance Manager running?


There are components that run on the USS side of things and mainframe side of things.

The USS file system doesnt have to be shared.

The GUI component is the only portion of the product that runs on the USS side of things. The rest runs on the mainframe.

Usually the GUI is run on one instance of the multiple LPARs/CPUs and communicates to multiple LPARS/CPUs via CA LDAP.

You could run multiple GUIs if you wish, if you need a redundant GUI with the additional cost of directory space and CPU usage.