When running MainView SRM in a Parallel Sysplex environment with shared DASD, what products/components need to run on each LPAR and should any run on just one LPAR of the sysplex.

Knowledge Article

When running MainView SRM in a Parallel Sysplex environment with shared DASD, what products/components need to run on each LPAR and should any run on just one LPAR of the sysplex.
Wanting to run BMC AMI Storage Reporting (formerly known as MainView SRM Reporting) in a Parallel Sysplex environment with shared DASD and need to know what products/components need to run on each LPAR and if any can run on just one LPAR of the sysplex.
BMC AMI Storage Reporting
BMC AMI Storage started task (SVOS) and all products/components running under the MainView SRM umbrella. All versions.
BMC AMI Storage Reporting
BMC AMI Storage started task (SVOS) and all products/components running under the MainView SRM umbrella. All versions.
When a customer runs MainView SRM in a Parallel Sysplex environment and DASD is shared,   
1) Should the MainView SRM (SVOS) STC be started on each LPAR?
2) Should all licensed components/collectors of MainView SRM run on each LPAR of the sysplex or are there some that 
    should run on only one LPAR of the sysplex? 

RECOMMENDATIONS:

In General:
MainView SRM (SVOS) stc is started on every LPAR. 
Primary VTOC SCAN Master file should be on the system running SVSGD.
One VTOC SCAN Master should be shared between all systems. 
Run a VSCAN against the shared one on a single system, daily.
Define Capacity Planning Database (CAPDB) on the same LPAR as SVSGD. 

Allocation:      Start on all LPARs to protect against out of space (and other) conditions.
StopX37/II:     Start on all LPARs to protect against out of space (and other) conditions.

Reporting:
*Space Collector            (SVSGD) –   Run on only one LPAR as the DASD is the same in each.
*Application Collector   (SVSGC) –  Run on every LPAR.  Must use the same data base data set in all.
*Performance Collector(SVSGP)—  Run as an STC on each LPAR and each must have a unique performance database.
*HSM Collector               (SVHSM)— Run on every LPAR.  Data base must be unique to each LPAR.
*ESA (Automation):
Customer should run VOLUME, POOL, and DATA SET automation on the LPAR running the Space Collector (SVSGD). 
Run HSM automation on any LPAR that is running the HSM Collector (SVHSM).


 
BMC AMI Storage Reporting
BMC AMI Storage started task (SVOS) and all products/components running under the MainView SRM umbrella. All versions.
Attachment(s):