Stopping a CAS
Because the CAS provides necessary services to PASs and user sessions, a running CAS is essential to the operation of
BMC AMI Ops
products.
Although some functions can be performed without a running CAS, the overall capability and flexibility of the BMC AMI Ops environment is severely diminished when no CAS is running.
However, under certain circumstances you might need to stop a CAS to perform a particular task, such as:
- Updating the maintenance level of BMC AMI Ops components
- Shutting down OMVS to apply system maintenance
- Activating TCP/IP communication
- Changing the libraries that are specified in the CAS JCL
- Restoring the BMC AMI Ops or user libraries that are specified in the CAS JCL
- Changing a CAS runtime parameter that cannot be changed dynamically with a view or MODIFY command
These situations, while infrequent, require that you stop and restart the CAS.
When you stop a CAS, local and cross-system communication is disrupted, which can affect the operation of active PASs. While a CAS is unavailable, data that is only available for display in windows mode will not be available. In addition, because the CAS provides services that are used by PASs for data collection, some data collection might not be performed while the CAS is unavailable.
To stop a CAS
- Verify the procedure name for the CAS that you want to stop.
- (optional) Stop all active PASs that are supported by the CAS.
Issue the STOP command from the operator console:P procname
Or, if the CAS was started with an ID, issue this command:
P id | stepname
The table in CAS-START-command-parameters discusses both of these parameters.
- Look for the following console message that indicates that the CAS has terminated successfully:BBMZA999I SSID( ssid) shutdown complete - CC=0000
Related topic