Skip to Content

Starting and stopping BMC AMI Storage components

All BMC AMI Storage components are started, controlled, and managed with the BMC AMI Storage common component SVOS address space.

Related topic

Using-BMC-AMI-Storage-operator-services

All 

BMC AMI Storage

 components are started within this common address space. The SVOS address space also controls the connection to the

BMC AMI Ops Infrastructure

 CAS and, in 

BMC AMI Ops

terminology, is the PAS for 

BMC AMI Storage

.

When the BMC AMI Storage 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 BMC AMI OpsI 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.

Success

Tip

You can run the StopX37/II product without the BMC AMI Ops 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*

BMC AMI Storage Reporting 8.2