Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Storage Allocation 8.1.

Starting and stopping MainView SRM components

All MainView SRM components are started, controlled, and managed with the MainView SRM common component SVOS address space.

All MainView SRM components are started within this common address space. The SVOS address space also controls the connection to the MainView Infrastructure (MVI) CAS and, in MainView terminology, is the PAS for MainView SRM.

When the MainView SRM common PAS, SVOS, is started, the default is to start all licensed components.

The global system parameter BBI3_SSID specifies the CAS subsystem name to which the SVOS PAS should connect. Because the MVI connection occurs during SVOS startup, SVOS will not start if BBI3_SSID is not specified. To update the value of BBI3_SSID, SVOS must be stopped and restarted; it cannot be refreshed. The CAS subsystem name is specified in the SSID parameter on the PARM keyword for the CAS JCL EXEC statement.

Tip

You can run the StopX37/II product without the MainView interface; in that case, SVOS does not require the BBI3_SSID keyword to start. For more information about the keyword, see information about the STOPX37II= keyword of the SMMSYS00 PARMLIB member.



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*